Thread: [Etherboot-developers] mini-slamd question
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers
|
From: Timothy L. <tl...@ro...> - 2003-08-22 07:46:50
|
Hi Eric I was working on the rtl8139 driver and it seems to continue to loop. That is, it downloads via mini-slamd, acknowledges, prints 0-20 (an Etherboot rom) and continues to receive again. Any idea why Etherboot would request the file again? Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003 |
|
From: <ebi...@ln...> - 2003-08-22 10:48:03
|
"Timothy Legge" <tl...@ro...> writes: > Hi Eric > > I was working on the rtl8139 driver and it seems to continue to loop. > That is, it downloads via mini-slamd, acknowledges, prints 0-20 (an > Etherboot rom) and continues to receive again. > > Any idea why Etherboot would request the file again? The NACK lists the packets that have not been received so if you are seeing 0-20 it looks like nothing was received. It does look like the communication by the unicast side band channel is working so etherboot is getting the size of the image to download. Good luck finding the unicast enable for the rtl8139. Eric |
|
From: Timothy L. <tl...@ro...> - 2003-08-21 05:52:10
Attachments:
slam.tar.gz
|
> The NACK lists the packets that have not been received so if you > are seeing 0-20 it looks like nothing was received. > > It does look like the communication by the unicast side band > channel is working so etherboot is getting the size of the image > to download. > > Good luck finding the unicast enable for the rtl8139. > I have made some progress. I now receive a lot of UDP checksum errors and retransmissions see attached tar however the Linux kernel boots correctly. Are these retransmissions normal? Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003 |
|
From: <ebi...@ln...> - 2003-08-21 10:47:38
|
"Timothy Legge" <tl...@ro...> writes: > > I have made some progress. I now receive a lot of UDP checksum errors > and retransmissions see attached tar however the Linux kernel boots > correctly. Are these retransmissions normal? The retransmissions are correct behavior of the protocol when packet loss occurs. They are undesirable. There are a couple possible causes of: Kernel with broken multicast support. 2.4.early had this problem. Broken switch. Transmitter that transmits packets faster than the receiver can receive them. (mini-slamd transmits packets as fast as it can...) But my hunch is the packets are getting through just with UDP checksum errors. So I guess the question is what is causing the packets to become corrupt. Eric |
|
From: Timothy L. <tl...@ro...> - 2003-08-21 23:19:17
|
> But my hunch is the packets are getting through just with UDP checksum > errors. So I guess the question is what is causing the packets to > become corrupt. I reviewed a Becker version of rtl8139.c and found the issue. I did it wrong ;-) So, multicast is now confirmed to exist in: Driver Version Confirmed By -------- ---------- ------------------- 3c509 5.3 Tim Legge 3c515 5.2 Tim Legge 3c90x 5.2 Eric Biederman and Tim Legge eepro100 5.2 Eric Biederman and Tim Legge rtl8139 5.3 Tim Legge sundance 5.2 cvs Tim Legge tlan 5.2 cvs Tim Legge For now, I am leaving the code in 5.3. The changes to the drivers are minor and have tested Ok with tftp, but I would feel better if a few people tested it. I don't particularly relish being known as the guy who broke all the drivers in 5.2. Ken, should we #ifdef the multicast code in 5.2 with ALLMULTI? Left on my list are: 1) tulip 2) ns8390 (Are those cards even capable) 2) via-rhine 3) pcnet32 Of those, only the tulip and ns8390 seems to be working correctly (at least for me) in 5.3 so I will need to dig into a couple of them. Did some one report issues with the via-rhine with a rev A3-1 DLink DFE-530TX? And last of all, has anyone else noticed the delay on the list? Tim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003 |
|
From: <ebi...@ln...> - 2003-08-21 23:25:17
|
"Timothy Legge" <tl...@ro...> writes: > > But my hunch is the packets are getting through just with UDP checksum > > errors. So I guess the question is what is causing the packets to > > become corrupt. > > I reviewed a Becker version of rtl8139.c and found the issue. I did it > wrong ;-) Ok. Good because that is what it felt like. > Ken, should we #ifdef the multicast code in 5.2 with ALLMULTI? What I have done is after I have tested it I have simply removed the #ifdef. My intention was for it to go away. In all of the cases I have seen it is harmless to leave it always enabled, and it makes the drivers simpler to maintain if they only do one thing. > And last of all, has anyone else noticed the delay on the list? I have noticed I can have a whole email exchange with you before it shows up the list. Yes. Eric |
