We help IT Professionals succeed at work.

Ethernet Setup

anopanen
anopanen asked
on
Medium Priority
305 Views
Last Modified: 2012-05-04
Here's a pretty easy one, I hope:
I've got a MaxTech 16-bit ISA NE2000 compatible network
adapter (essentially "Generic Ethernet Card")
running on my Pentium with Slackware 2.0.29.
And I can't get Linux to work with it.  I compiled the kernel with NE2000/1000 support (not a module) and configured everything how it seems it should be.  When booting it croaks when trying to load the "eth0" interface with ifconfig from /etc/rd.c/rc.inet1--says "Device not found" a/o "Interface not found", then gives the lecture about "mebbe you don't have a card or the kernel don't support it"
The card works perfectly under Win95, and I previously had it working with a different kernel version under a UMSDOS filesystem that I killed off.

So, my questions (in addition to "How do ya fix it?") are:
Where is the card in /dev?
How do you specify an IRQ & I/O range for the card?
Where can I read more about interfaces and Linux networking in general?
Is the NE2000 support the appropriate and only driver necessary?
Comment
Watch Question

Commented:
1) check with dmesg if your card was recognized (like eth0)
2) for setting the irq/port it depend if you use lilo or loadlin
   a) (lilo) when you install lilo (in the liloconfig-color
       command) you can specify for more parameters like
       eth0:300,9 or something so (check the howto of lilo)
   b)  in the file the launch loadlin you can add other        parameters like before
3) yes NE2000 support is the only required for this card.
 

Commented:
1) check with dmesg if your card was recognized (like eth0)
2) for setting the irq/port it depend if you use lilo or loadlin
   a) (lilo) when you install lilo (in the liloconfig-color
       command) you can specify for more parameters like
       eth0:300,9 or something so (check the howto of lilo)
   b)  in the file the launch loadlin you can add other        parameters like before
3) yes NE2000 support is the only required for this card.
 

Author

Commented:
Okey-

dmesg had this in it:

lance.c: PCI bios is present, checking for devices...
eth0: D-Link DE-600 pocket adapter: not at I/O 0x378. <=!!!
D-Link DE-620 pocket adapter not identified in the printer port
arcnet.c: v2.53 96/06/06 Avery Pennarun <apenwarr@foxnet.net>
  arc0: Stage 3: No ARCnet cards found.
Partition check:
-------------

I dunno exactly why it's searching for the DE-600 card--I didn't compile support in for it.
...and it's searching in the wrong place for it; my card's at IRQ 11 and I/O address 240-25F
I tried putting that in as an option with LILO, but it didn't seem to have an effect.

Any ideas?
Commented:
Try configuring the card to someone other than IRQ 11, like 10 or 5 since these are typically free and most commonly used for NICs. In your /etc/lilo.conf, add to the top something like:
append="ether=10,0x300,eth0" where 10 and 0x300 are your IRQ and base addrs respectively for your card.  Make sure the card is not in any sort of PnP mode.  NICs don't show up as devices in /dev, you will only need to have NE* support compiled in the kernel and the probe should do the rest upon bootup.  What other devices do you have in your system which could be confusing things?  Have you just compiled a bare minimum kernel with only the required drivers and no fancy stuff?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.