On Sat, May 26, 2007 at 06:08:30PM +0100, Ted Harding wrote:
I'm puzzled! Can someone give me a hint?
I've had an (ancient) NE2000 clone which plugs into an ISA (not PCI) slot running happily on a very old machine (ca 1995) for years.
On SuSe 5.2 I had it set up to use module ne.o, with options "io=0x300".
Now that machine's PSU has failed, so I moved the hard drives etc. to another box (of more recent vintage ... ).
Now it fails to find the card and/or any IRQ line when given 0x300.
I've removed all other ISA cards from that box to make sure there are no conflicts.
I've tried this not only with the "native "SuSE-5.2 off the hard drive, but also booting with tomsrtbt ("Linux on a Floppy" and with Ubuntu live CDs, in all cases without success.
I'm puzzled that it works one the one box but (with the same system and settings) fails on another. Is there a possibility that ISA IO addresses and IRQs can change between different motherboards?
A lot of the NE2000 clones were actually ISA Plug'n'Play (aka Plug'n'Pray). These could well change IRQ/IO if moved between motherboards. However I thought that the drivers these days would perform the appropriate PNP query/setup to automatically configure the device. What kernel version are you using and is it self compiled or distribution provided?
Another option is that if the IRQ is hardwired on the card you may need to reserve it in the BIOS settings so that no PCI device is assigned the same one.
As a final suggestion, some cards had a vendor supplied tool which would allow you to change/view the card settings. nictools-nopci under Debian has Linux tools for some cards, but I suspect for a cheap clone you're going to end up with a DOS tool.
Is there a reason not to move to a cheap PCI card? (The only reason I can think not to is that 10base2 PCI cards are harder to get hold of, but they do exist.)
J.