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