I got the value 0x340 through trial and error. All the others fail the initial ne2000 probe.
dsl-093-a:~# ne2k-diag -p 0x340 Checking the ethercard at 0x340. Receive alignment error counter (0x34d) is 00 Passed initial NE2000 probe, value 00. Station Address PROM 0: 00 00 40 40 33 33 37 37 e1 e1 6e 6e 05 05 01 01 Station Address PROM 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 57 57 57 57 NE2000 found at 0x340, using start page 0x40 and end page 0x80. The current MAC stations address is 00:40:33:37:E1:6E. dsl-093-a:~# The only IRQ related option I saw was -Q, to set the IRQ line. The card doesn't have any jumpers on it. The exact model number is: Winbond W89C905F. I wasn't able to locate that chip on the Winbond site. However, most of the Googling I've tried has included Linux as a keyword. When I try 'modprobe ne io=0x340' it reports: ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) Last modified Nov 1, 2000 by Paul Gortmaker NE*000 ethercard probe at 0x340: failed to detect IRQ line. ne.c: No NE*000 card found at i/o = 0x340 then the standard modprobe error lines. dmesg has two sections that report about ne.c: NE*000 ethercard probe at 0x340: 00 40 33 37 e1 6e eth0: NE2000 found at 0x340, using IRQ 5. about 10 lines from the end of the output -- and -- NE*000 ethercard probe at 0x340: failed to detect IRQ line. ne.c: No NE*000 card found at i/o = 0x340 at the end of the dmesg output. So, I'm curious why that first part seems to find the card but the second part doesn't. -- Nick Traxler Computer Science, Purdue University http://www.cs.purdue.edu/people/traxlend "The two most common things in the Universe are Hydrogen and Stupidity." On Wed, 5 Jun 2002, Rainer Ellinger wrote: > Nick Traxler wrote: > > Any ideas? I'm not sure if the interrupt can be arbitrary or if I > > have to find a way to read it off the card. > > Could you please give the full output of ne2k-diag? > > Usually the IRQ is reported, too. If this is not a PnP card, you need > to reserve the interrupt in your BIOS setup, section "PNP and PCI" > manually for ISA usage. But you need to know the right interrupt > before, not just a guess. > > If ne2k-diag doesn't report the interrupt of your card, you've to > examine the card for jumper settings. Additionally, you might have a > MS-DOS based setup program from the vendor. > > Please also grep the output from system startup with dmesg or from > /var/log/dmesg. Only assign io=0x340 when loading the ne module, don't > assign a interrupt. What does the kernel report concerning the > interrupt in dmesg? > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
