How can I load the right module of my network card?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How can I load the right module of my network card?
After compiling kernel 2.6.1, my network card is not working. However, I keep the old kernel, so now I can use the old one and the network card is working in the old kernel.
My network card is:
Silicon Integrated Systems [SiS] SiS 900 10/100 Ethernet (rev 145)
How can I get my network card to work in the new kernel?
I have the same one and I have it compiled into 2.6.1 and working, there is an option for it in make menuconfig under device drivers > networking > ethernet (10 or 100 mbit).
Hi, what is the different between '*' indicator and 'M' indicator when I select things in "make menuconfig"
Which one should I use?
Also, I think there probably is another problem that I don't have internet access. Do I need to tell the system that I use DHCP to assign IP address to this computer? I just find that there is no DHCP checking during boot up. If I need to set DHCP after recompiling the kernel, how can I do it?
[QUOTE]Originally posted by ICO Hi, what is the different between '*' indicator and 'M' indicator when I select things in "make menuconfig"
Which one should I use?/[quote]
* means that you are compiling it into the kernel
M means that you are not compiling it, but are setting it up later as a Module
It's entirely up to you which one you choose.
Quote:
Also, I think there probably is another problem that I don't have internet access. Do I need to tell the system that I use DHCP to assign IP address to this computer? I just find that there is no DHCP checking during boot up. If I need to set DHCP after recompiling the kernel, how can I do it?
Thanks.
If you want to, you can run netconfig as root which will set up your internet access and ask you about your DHCP and everything. Hope this helps.
Originally posted by ICO Hi, what is the different between '*' indicator and 'M' indicator when I select things in "make menuconfig"
Which one should I use?.
* means that the option is compiled directly into the kernel and will load at boot time. M means it's compiled as a module, which can be inserted into the module later on if need be. I'd used *.
I try it but doesn't work.
In my old kernel system, when the system boots, I have these messages:
dhcpcd[161]: DHCP_ACK received from XXXX (can't read these characters) (10.0.0.2)
but for the new kernel, I don't have, I think that's why I don't have internet access. And I did choose my network card in menuconfig. And I try netconfig as well.
So what's wrong with that?
What is the output of lsmod? You need your modules installed for your NIC and your sound card. If they're both installed, then there's other problems at hand.
Originally posted by Texicle What is the output of lsmod? You need your modules installed for your NIC and your sound card. If they're both installed, then there's other problems at hand.
When I type lsmod, the output is:
Module Size Used by
and nothing else.
Does that mean it is empty?
Then what should I do?
Originally posted by ICO When I type lsmod, the output is:
Module Size Used by
and nothing else.
Does that mean it is empty?
Then what should I do?
Thanks for help.
Yeah it looks pretty empty. Okay, what you need to do is check around www.google.com/linux (aka G4L) for your correct module for your sound and NIC. Once you find it, login as root into a terminal or directly at CLI, and type:
modprobe <module name>
for each of them, but without the <>'s and obviously with the proper module name.
Okay, nevermind. I just a did a search and found the modules you should be using. Go into the command line or terminal and login as root:
su -
enter root password
modprobe sis900
modprobe emu10k1
This should get your NIC and your sound card working. If you like, you can take it a step further and run insmod <module name>, but the modprobe should get you started. If after a reboot or something, your sound and NIC aren't working again, try the insmod command and if that doesn't work, let me know. We'll get it to run for you at boot time.
hi, Texicle
Thank you very much!
modprobe sis900
will get my NIC working, and now I have internet access.
However, I think there must be some other way that make it automatically work at boot time so that I don't need to type this command every time. And I know it is possible you add this command to my bash_profile file. But it seems not the proper way to do so since in my old kernel, I don't need this. So do u know another way that I can make it work at boot time?
Also, after modprobe sis900, and I type lsmod command, the output is:
Module Size Used by
sis900 17476 -
crc32 3648 -
that crc32 thing seems not normal, is it all right?
The sound card works after I recompiling kernel again, so don't worry about the sound card.
Originally posted by mrpdaemon in /etc/rc.d/rc.modules, uncomment the line:
#/sbin/modprobe sis900
and it shall load at boot.
This works just like magic!
I love you guys!!!
Heaps of thanks!
And I want to take one step further, problems probably relate to the file /etc/rc.d/rc.modules as well.
When I boot my system, I have some error message indicated FATAL. Most of them are that os tries to detect some device that I don't have on my computer such as scsi device or so.
Can you guys tell me that how I can track back to that startup message since it is just so quick I don't have a chance to write the error message down.
And if I want to prevent it from detecting those devices, should I modify the file /etc/rc.d/rc.modules as well?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.