Re: Rescue disk hurts my ethernet card
On Sat, 14 Jun 1997, Hamish Moffatt wrote: :On Thu, Jun 12, 1997 at 04:39:53PM +0200, [EMAIL PROTECTED] wrote: : When I rebooted to linux I noticed several network error [snip] : configuration tool (grrr...). The second case (1.2, Apr 97) : : Am I the only one with such an expirience? I should add that I : :Interesting. I've got quite a few NE2000s and haven't had them :lose their configuration, but I have had quite a few (about :three now) die completely. I'm currently using an WD 8013 in my :PC, which on a couple of occasions has had invalid PROM :states; the DOS driver won't load, and I haven't had the :EtherEZ stuff on hand to reconfigure it. Usually, I boot :Linux and Linux revives it. : :8013 seems to be quite a good card. Better than the NE2000's :I've got. And I bought it for $1.50 Australian out of a junk :basket at a local electronics store; marked no drivers. :Better than the $40 NE2000s. I also bought (for $5) a big :VLB IDE/IO/SCSI card (Adaptec 1520 based), also no drivers. I've had a lot of good luck with SMC 8013s. I also like the 3Com Etherlink IIIs, but they're hard to find cheap. I ran into about 15 8013s that someone was throwing away since they'd upgraded to PCI cards ... not a bad price for me :) At $1.50 they're a great deal ... I also like the two hardware jumpers on the SMC versions for troubleshooting. Cheers, -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
On Thu, 12 Jun 1997, Lee Bradshaw wrote: I had a similar problem with tcpdump. After I saw it referenced in a message here I decided to see what kind of info it would print out. The info on my card (3C509) looked correct, but after running tcpdump, I couldn't connect to any other machines. The light on my hub indicated the card wasn't alive. Rebooting in win95 :^( and then back into debian fixed the problem. While we are lamenting about the rescue disk nuking ethernet cards, I had a DLink-250 that the rescue disk would disable (changed the EEPROM somehow). I forget the exact details but I do know that during boot Linux can FRY (permantly harm) those DE-250 cards, it damages the eeprom in some way that the setup programs will not rewrite it. I forget what I did to fix it, I think I moved the base address. Jason -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
On Thu, 12 Jun 1997, Bruce Perens wrote: The EEPROM getting scrambled is a result of drivers probing for devices on the bus that don't happen to be there, and hitting the network card instead. This happens more with the rescue disk than with a custom kernel because the rescue disk is built for every scsi and ethernet card we could fit in the kernel. If you can tell me about the I/O ports of your network card we can give you magic words to put on the boot command line for that device that reserve its ports and prevent other drivers from touching them. Fraid the reserve boot command did not help this problem, it's EEProm IO ports may not have been in the region I had the card set to or one of the drivers may be ill behaved. I've long since gotten rid of it, now have a RealTek PCI NE2k. I heard of two fried network cards, one was mine and one was a friends, both D-Link DE-250's and both fried by booting the rescue disk. My other De-250 just got disabled during linux's boot, had a bit of a time figuring out why Linux didn't want to use my card till I figured it out. Jason -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
The EEPROM getting scrambled is a result of drivers probing for devices on the bus that don't happen to be there, and hitting the network card instead. This happens more with the rescue disk than with a custom kernel because the rescue disk is built for every scsi and ethernet card we could fit in the kernel. If you can tell me about the I/O ports of your network card we can give you magic words to put on the boot command line for that device that reserve its ports and prevent other drivers from touching them. This isn't strictly a Debian problem - it'll happen to any generic kernel with all of the device drivers built in. Also, well-designed hardware wants you to say the exact right magic words before it makes its EEPROM writable. It doesn't write it for just any random I/O. I'd suggest that others stay away from net cards that exhibit this behavior. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
On Thu, Jun 12, 1997 at 04:39:53PM +0200, [EMAIL PROTECTED] wrote: When I rebooted to linux I noticed several network error messages, and ping showed Network is unreachable. Apparently the rescue disk had confused my WD8013 ethernet card. Then I booted do DOS -- and it complety hang after probing the ethernet card: WD80x3 adress PROM contents are invalid. I did a hard reset, and, look, my ethernet card automagically awoke from paralyzation -- what the hell had happened? I remember that I had similar problems with two cheapo NE2000 clones after installing Debian the first time. One (Debian 1.1, Dec 96) came back to life after consulting the DOS configuration tool (grrr...). The second case (1.2, Apr 97) Am I the only one with such an expirience? I should add that I Interesting. I've got quite a few NE2000s and haven't had them lose their configuration, but I have had quite a few (about three now) die completely. I'm currently using an WD 8013 in my PC, which on a couple of occasions has had invalid PROM states; the DOS driver won't load, and I haven't had the EtherEZ stuff on hand to reconfigure it. Usually, I boot Linux and Linux revives it. 8013 seems to be quite a good card. Better than the NE2000's I've got. And I bought it for $1.50 Australian out of a junk basket at a local electronics store; marked no drivers. Better than the $40 NE2000s. I also bought (for $5) a big VLB IDE/IO/SCSI card (Adaptec 1520 based), also no drivers. Hamish -- Hamish Moffatt, StudIEAust[EMAIL PROTECTED] Student, computer science computer systems engineering.3rd year, RMIT. http://hamish.home.ml.org/ (PGP key here) CPOM: [ ] 47% The opposite of a profound truth may well be another profound truth. --Bohr -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
On Fri, 13 Jun 1997, Jason Gunthorpe wrote: On Thu, 12 Jun 1997, Bruce Perens wrote: fit in the kernel. If you can tell me about the I/O ports of your network card we can give you magic words to put on the boot command line for that device that reserve its ports and prevent other drivers from touching them. Fraid the reserve boot command did not help this problem, it's EEProm IO ports may not have been in the region I had the card set to or one of the drivers may be ill behaved. I've struggled with some software configurable isa ne2k's. They appeared to function quite nicely with linux, but win95's autoprobing had severe difficulties with the cards. The dos configuration utility would let me change io and irq settings just fine, I could also write them to the register but not to the card's eeprom, giving me an error in the card's own setup utility. The problem appeared to be that the cards used a different combination of irq and io for configuration and actual operation. It listened only half the time to the operation addresses and the configuration addresses were conflicting with other hardware. This kept me stumped for quite a while and until I figured it out I too had long bought pci cards (which also gave some trouble sigh.) This was the solution in my case: -on the motherboard bios setup, disable com2:, freeing irq 3. -with the dos utility, set the io and irq to what the card uses to receive programming data. -then set it to what would suit the computer's available interrupts and io addresses. Don't forget to write the settings to the card's eeprom. In your case, the conflicts may ofcourse be a little bit harder to resolve before you can access the card again. Maybe it doesn't work altogether on your card. Maybe it's really burnt. You can always try. I've long since gotten rid of it, now have a RealTek PCI NE2k. Hmmm, I bought winbonds. They don't work without a patch. It would be great if this patch would make it to the next bootfloppy, or even better - 2.0.31. Until then, I have to make my own rescue-floppy kernels. I heard of two fried network cards, one was mine and one was a friends, both D-Link DE-250's and both fried by booting the rescue disk. My other De-250 just got disabled during linux's boot, had a bit of a time figuring out why Linux didn't want to use my card till I figured it out. Please check my solution if that may help you, if the reprogrammed io and irq aren't too outrageous there may still be hope. I think that it is however possible to fry hardware with linux: while trying 1.3 I inserted a wrong module for the cdrom interface and it fried the cdrom drive. Good luck, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
Joost writes: I think that it is however possible to fry hardware with linux: while trying 1.3 I inserted a wrong module for the cdrom interface and it fried the cdrom drive. IMHO anything that can be truly fried in this way (that is, physically damaged) is broken as designed. John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Rescue disk hurts my ethernet card
Hi, after updating my Debian box at work from 1.2 to 1.3 (with no problems) I accidently managed to lock as well my root as my user account. To repair I got the newest 1.3 Rescue Disk (resq1440.bin) from my Debian mirror, rawrite2´ed it to a floppy, booted the system using the floppy, mounted my partitions, got a shell and did some repair. All went well :-) When I rebooted to linux I noticed several network error messages, and ping showed Network is unreachable. Apparently the rescue disk had confused my WD8013 ethernet card. Then I booted do DOS -- and it complety hang after probing the ethernet card: WD80x3 adress PROM contents are invalid. I did a hard reset, and, look, my ethernet card automagically awoke from paralyzation -- what the hell had happened? I remember that I had similar problems with two cheapo NE2000 clones after installing Debian the first time. One (Debian 1.1, Dec 96) came back to life after consulting the DOS configuration tool (grrr...). The second case (1.2, Apr 97) was more severe: the card refused even to answer to that DOS config tool. This card has changed its PROM state to a new IRQ (3) und IO (0x300). I managed to get it work again -- but that should not happen. Am I the only one with such an expirience? I should add that I never managed to get the standard kernel to work with my ethernet cards, and always had to built a custom kernel (which I prefer anyway). The hardware is in no way fancy: elderly 486 boards (with and without PCI) but quite sufficient under linux. No, this no flame against Debian. Debian has been proved to be a rock solid linux distribution for me -- and its upgradebilty is outstanding. But the initial hardware test seems to be offensive against the hardware under test -- and that should not be. KWS -- Mfg K.-W. Schulte -- O##OO##O O##O O##O ==The famous SchwebebahnAA==suspension==AA===AA===railway===AA Dr. Karl-Wilhelm Schulte AA AA AA AA Bergische Univ.-GH/HRZ ,__AA__AA___AA_AA___. Gaussstr. 20 | || || || |X| |X| || || || | D-42097 Wuppertal | || || || |X| |X| || || || | Tel 0202/4392807,Fax -2910 |_|| ||___|| |X|_|X| ||___|| ||_| [EMAIL PROTECTED] | | | | |X X| | | | | `==+=+=+=+X===X+=+=+=+==' -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rescue disk hurts my ethernet card
I had a similar problem with tcpdump. After I saw it referenced in a message here I decided to see what kind of info it would print out. The info on my card (3C509) looked correct, but after running tcpdump, I couldn't connect to any other machines. The light on my hub indicated the card wasn't alive. Rebooting in win95 :^( and then back into debian fixed the problem. -- Lee Bradshaw [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
