Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am looking for information on one of the NE2000 NIC's in my server. It has problem, not listed in the Ethernet how-to, or at least I don't think so.
I don't have any information on the NIC accept for the info on the board itself:
Novell NetWare Remote Programm Loader
NetWare Ethernet NE2000 VL00EC 880819
Is this NIC a plug-and-play device? That might cause the problem. Maybe, original DOS setup software can detect that problem. I was wondering if anybody has got that kind of software.
The NIC is detected during boot-up. The LED's in the NIC glow, whenever they have to, but the NIC can't pick up any signal from the ethernet. Other NIC's function perfectly in the exact same configuration.
I can also try to use the diagnostic programs at http://www.scyld.com/diag. However, I don't have a clue about what I have to look for in the resulting diagnostics, an ygelp on that would be great.
I sort of recall a command 'isapnp' which lists all PnP devices on the machine, which might tell you something.
Some pre-PnP ISA cards came with DOS configuration programs. You had to set IRQ, IO range (and some other thing I forget) using this. I believe the linux ISA NIC driver needs this info. I think I used Debian's 'netcardconfig' utility to do that, and it ended up in the modules.conf file.
Maybe the diagnostic program could find out what these parameters are set for in your card. Trial and error is probably also a possibility, although I think I would probably junk the card before it got to that.
No PCI? An old 486 maybe? I've never seen a PnP NIC, all the ones I've used have the DOS utility for setup. Looks like linux has installed your card OK. Does ifconfig show eth0 as up? I suppose you could toggle 'ifconfig eth0 up/down' a few times to see if it might be an intermittent hardware fault. Pretty old piece of hardware tho'...
Yes, you are correct. I am setting up a zero budget server/network with some fossil remains. I am dealing with a i486dx and two NIC's without manual or software.
I identified one as a rtl 8019, which can be set to PnP. I have been able to set it manualy using the DOS utility, still available at realtek.com.tw. Novell doesn't provide similar software for their Netware Ethernet NE2000 V1.OOEC on their site. Since it is the original NE2000, and thus very common, I was hoping to find more info here and/or the dos utility.
Both cards have been configured identical using ifconfig, ifup, ifdown, the etc/interfaces-file and dhcp3. The realtek board is working fine. The Novell Netware board doesn't receive any packets, according to tcpdump. The board is detected correctly and the LEDs at the board indicate activity when packets are send, so I still believe it can run, despite its age.
Thanks for the adress of that site. However I tried to use the DOS drivers provided there, but none of them did the trick. One of the drivers reports a hardware conflict, but provides no means of a solution.
I tried to compile the diagnostic program of Donald Becker, www.scyld.com. It gave compiling errors about non-existing *.h files (unistd.h, stdio.h, stdlib.h, getopt.h, sys/io.h) but no information on the correct IRQ and IO port. If I provide, IRQ and IO port, wrong, will the card be detected then?
BTW: pnpdump doesn't detect any unconfigured pnp devices.
Do I have any options at the moment, or is it time to dump the interface?
Thanks for the tip on the libc6-dev packages. It's suggested package, so apt-get skipped it. The ne2k-diag proggie now results in:
Checking the ethercard at 0x300.
Receive alignement error counter (0x30d) is ff
Failed initial NE2000 probe, value ff.
Station Address PROM 0:ff ff ff ... (<-16 ff's)
Station Address PROM 0x10:ff ff ff ... (<-16 ff's)
Invalid signature found, wordlength 2.
I tried scanport (in hwtools package) to find the ports for the ethercard. There's only one unknown device which is twenty ports wide: 320 - 33f. So now I only need to find out it's IRQ, which I will try to do manualy if I can't find a package to do so.
The contradiction between scanport and ne2k-diag both is confusing.
When I use the hardware address to find out the cards manufacturer. Four companies are asociated with 00:40:05: TRENDWare, LinkSys, Simple Net and ANI Communications Inc. After inspection of the card it self I believe it's type indication is
I tried one of the drivers supplied by trendware. The NIC has a bnc and a rj45 connector. The NIC was set to bnc. With the dos utility supplied by trendware I was able to set it to rj45. Now it works, I get a ping and can move on configuring the network.