We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

SETTING UP A NE1000 NETWORK CARD

OAKESM
OAKESM asked
on
Medium Priority
401 Views
Last Modified: 2013-12-15
I HAVE LINUX REDHAT, BUT IT DOESN'T SEEM TO SUPPORT MY NETWORK CARD (NE1000), IT SUPPORTS THE NE2000 THOUGH. HOW DO I GO ABOUT GETTING IT TO WORK WITH MY NETWORK CARD?

I ALSO HAVE SLACKWARE AND ALTHOUGH IT SUPPORTS MY NETWORK CARD, IT SAYS THAT THE CARD CANNOT BE FOUND AT ADDRESS 320.
WHATS THAT ABOUT THEN?

I SPENT DAYS TRYING TO FIGURE THIS ONE OUT.

CHEERS
MICHAEL OAKES
Comment
Watch Question

Author

Commented:
Edited text of question

Commented:
The ne1000 seems to be treated the same as the ne2000 from the documents I have read. Support for network cards is part of the kernel, and given the same kernel version it should make no difference whether you use slackware or redhat It's 8 bit instead of 16 bit, but it should still work. You'll need to know what irq and address the card is set to. This is written into the eeprom on the card, or maybe set by jumpers on the card. To change it you will need a dos utility that reads and writes to the eeprom. If you know the manufacturer, you can try their web site to see if there is a utility for the card, or try one for a similar card. If you have the card working in win95 or other os, you can get the irq and address from there. Support for the card can be compiled into the kernel or added as a module. You obviously have some sort of support set up in slackware, since it tries to probe for the card. Do you get any other messages at boot up about the card? Are you sure it set up at address 320? If you have any more detail about the card, kernel version, etc. maybe it would help to set it up.
Don't fall into the trap I did: When RedHat (or slackware) asks you for the io and irq of the NE2000 (or NE1000), don't type '320' as the address, use '0x320' - then it works. Pity it isn't documented that you have to give the prefix for hex, rather than it being assumed as in all the other options.

Commented:
I don't think the support for the NE1000 is robust.  These cards are so old that there isn't much interest on the part of the developers to update them anymore.  You can get an NE2000 compatible NIC for about US$20 so there is little reason anymore to keep banging your head against an obsolete card.
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Commented:
If the setup is the same as for an NE2000, the best way to do it is to recompile your kernel...I don't trust those red hat and slackware pre-installs.  compile the NE*000 support as a module then load it like:
/sbin/modprobe ne irq=5 io=0x320
As stated above most cards will either provide jumpers to change the ip and irq settings or will provide a dos utility (use a dos boot disk to run it) to save the settings to the card's eeprom.  Make sure that if the card has either plug & play or manual modes you take it out of plug and play or Linux will not detect it.  Do the settings by hand and make sure the irq and io address do not conflict with any other devices

Commented:
Whoops, just remembered that when you compile NE support as a module another module (8390.o) gets created as well. Load that one too before the ne module as so:

/sbin/modprobe 8390
/sbin/modprobe ne irq=5 io=0x320

sorry!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

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