Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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've loaded Redhat 7.1 and it has been working fine.
But then i put in a network card and tried to configure it.
That's when the trouble began.
I don't know what i'm doing wrong... I followed the instruction in a book that I have. Which told me to use ifconfig. Which i did, but that didn't work, it still won't let me on the network.
and i've tried using the network config from KDE and that didn't seem to help at all either...
I have a NetGear FA311 network card and the latest drivers (for they actually provide linux drivers).
Now I'm not sure if installed the drivers correctly or not, but i'm pretty sure the driver was already installed.
But yeah, ever since i've tried to get this NIC to work, it's been giving me troubles. Now there are things that crash on boot up.
And sometimes it says
Initializing interface: eth0
and it sits there and hangs for a long time, then says that the IP couldn't be determined.
and then when do an ifconfig, sometimes it completely locks up and i have to do a hard reboot.
So I don't know.
If anyone can help... That'd be great.
I'm sure I'm going to have to rebuild the kernel, but I'm not quite sure how to go about doing that.
There is support for that card in the kernel. You need to load that modules natsemi.o before the system brins up the NIC at boot.
You should be able to load the driver as a module without recompiling the kernel. I am not sure how to do this with Read Hat, bu in Slackware there is a file /etc/rc.d/rc.modules that you uncomment the line that contains /sbin/modprobe/natsemi. You can run that command from the command line and see if the module is there. If if work you then need to do and ifconfig eht0 192.168.0.10 up to bring up the card.
Is it an ISA or PCI card? Reason I ask is that I had a lot of problems with old ISA PnP (Plug'n Pray) cards, but any PCI cards I have tried work like a charm.
That said, there are a couple of things you should look into. First of all, do you know if the driver for your card is a *.o module or is it compiled into the kernel? I'm guessing that since you said the driver came with the card, that it's a *.o module file.
You'll want to check that it's installed in the correct directory, it should be something like:
(Replace <yourkernelversion> and <drivername>.o with the appropriate values.)
<drivername>.o should be your driver module file. Make sure it's in the directory specified above, if the directory doesn't exist, get back to me.
If all is fine and the driver is in the correct place, try this:
That should automatically probe your hardware for a card that the driver supports, and if it finds it, load the driver. If that's successful, you should be able to use "ifconfig" to configure the card.
You should probably also to a "man modprobe" and "man ifconfig" just to get a basic view of what they do. When you use "ifconfig" make sure you specify an IP address like so:
ifconfig eth0 192.168.1.1
Of course use your correct IP address (if you are using DHCP get back to me).
If this works, you will need to add a line to your "/etc/modules.conf" file in order to load the module at boot time. You should be able to find exact details on how to do this easily enough.
Also, you might want to look up the commands "insmod" and "lsmod". "lsmod" will tell you what modules are loaded, you can use it after doing a "modprobe" to verify that the module (driver) is loaded. "insmod" is what modprobe uses to actually load the driver, and it can sometimes be used to force the driver to load.
One more thing, make sure that you have "PnP OS" disabled in your BIOS.
If you have problems with any of the above, or need more detail, get back to me.
Now, if you an old ISA PnP card, you will most likely need to download and install the "isapnp" program. Once it's installed, run the "pnpdump" utility from the /etc directory. This should produce a file called "isapnp.conf". Look in this file for an entry for your NIC. If it's there, we should be in business, you will need to make some small edits to you "isapnp.conf" file and then run "isapnp", which should make the hardware available to modprobe and ifconfig....Whew, if you have any problems, get back to me...
Great... Thanx very much for the support....
I checked, the driver is in the right place.
So I ran modprobe natsemi
And the result was:
Not: /etc/modules.conf is more recent than /lib/modules/2.4.202/modules.dep
/lib/modules/2.4.2-2/kernel/drivers/net/natsemi.o: init_module: No Such Device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.2-2/kernel/drivers/net/natsemi.o: insmod /lib/modules/2.4.2-2/kernel/drivers/net/natsemi.o failed
insmod: /lib/modules/2.4.2-2/kernel/net/natsemi/natsemi.o: No such file or directory
insmod: insmod /lib/modules/2.4.2-2/kernel/net/natsemi/natsemi.o failed
insmod: insmod natsemi failed
What should I try now?
Oh yes... I'm also using DHCP on my internal network.... so yeah
Last edited by LoRd Of XAoS; 08-05-2003 at 04:45 PM.
Hrm... it looks like it's having problems finding the hardware, at least that's what I get from the "No such device" message.
1) have you turned off "Plug and Play OS" in your BIOS?
2) Is it an ISA or PCI card? (Do you know how to tell the difference?)
If it is an ISA card, I have a feeling you will need to get the "isapnp" program.
Either way, we need to find out the correct IO and IRQ settings for this to work. Do you have a windows computer lying around? Sometimes they can be used to find out the IO/IRQ settings as their hardware support is generally better...
Also, take a look at what's in your /etc/modules.conf file, you can do this with
I think sticking it into a windows box just to see if it works would be a good idea, if it doesn't work, your card is bunk, if it does work, you have use the device manager to find the correct io/irq settings, then you will need to add lines to modules.conf:
alias eth0 natsemi
options natsemi io=<IOport> irq=<IRQ#>
Of course before doing so you should try inputting those values into your modprobe query to see if all's well.