Messages in this thread | | | Date | Sat, 5 Aug 2000 13:51:21 +0100 (BST) | From | Tigran Aivazian <> | Subject | Re: bug in ne.c/isapnp |
| |
correction - the story below is from 2.4.0-test6-pre2. Now, in 2.4.0-test6-pre5 it seems to work fine when both ne and isapnp are statically linked. The card is now (by itself, probably assisted by some reboots into Windows, FreeBSD, Solaris and UnixWare (or maybe BIOS did it?) in the meantime) permanently migrated to io=0x220 and irq=5.
So, it all works now and whosoever remembers the past shall lose his eyes (or so the russian saying goes).
Regards, Tigran
On Sat, 5 Aug 2000, Tigran Aivazian wrote:
> Hi guys, > > Interesting situation. I have a ne2000 ISA card at 0x280 on irq=9 and > here is what I get if I compile both ISAPNP and ne.c statically: > > eth1: NE2000 found at 0x280, using IRQ 9. > eth1: interrupt from stopped card > NE*000 ethercard probe at 0x220: 00 48 45 80 6d 38 > eth2: NE2000 found at 0x220, using IRQ 5. > ne.c: ISAPnP reports Generic PNP at i/o 0x220, irq 5. > > and neither eth1 nor eth2 work. If I compile only ISAPNP statically but > ne.c as a module then it finds ne at 0x280 on irq=9 and works. But > sometimes it finds it on 0x220 on irq=5 and still works. Strange. > > Probably I need to run the DOS pnp ne2000 config utility and set the card > in Jumperless mode... > > Regards, > Tigran > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |