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] .
