Solved

SETTING UP A NE1000 NETWORK CARD

Posted on 1998-07-21
7
329 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
0
Comment
Question by:OAKESM
7 Comments
 

Author Comment

by:OAKESM
Comment Utility
Edited text of question
0
 
LVL 4

Expert Comment

by:swwelsh
Comment Utility
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.
0
 
LVL 2

Expert Comment

by:richrussell
Comment Utility
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.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 32

Expert Comment

by:jhance
Comment Utility
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.
0
 

Accepted Solution

by:
nivo earned 200 total points
Comment Utility
I guess you've got a ne module in your kernel compiled, or loaded as a supplemental kernel. If the adress 0x320 doesnt work, you can force Linux to use other hardware adresses, by adding the following line to your /etc/lilo.conf (afterwards reload lilo by typing /sbin/lilo)

(in the boot entry of your linux add:)

append="ether=5,0x280,eth0"

Where 5 stands for the IRQ, 0x280 the IO adress and eth0 the logical device for linux.

Grtz,

WebSpider@IRCnet
0
 

Expert Comment

by:openGL
Comment Utility
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

0
 

Expert Comment

by:openGL
Comment Utility
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!
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

After running Ubuntu some time, you will be asked to download updates for fixing bugs and security updates. All the packages you download replace the previous ones, except for the kernel, also called "linux-image". This is due to the fact that w…
SSH (Secure Shell) - Tips and Tricks As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now