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.
I have been back and forth through the books, these forums, install guides, etc. etc/rc.d/rc.modules does not contain any reference to lan 10,100,1000. I am using a Abit IP35 Pro motherboard with built in lan. netconfig sets up fine but I can't connect to or ping my router or the internet.
So far I like my new slack install (12.0) but this is really frustrating me. Computer is of no value without internet connection.
I appreciate any help and will be glad to post any logs or system info that are needed.
I have been through the network configuration in slackbook. Somewhat lacking in info on 10/100/1000 lan, Where are these loadable kernel modules? I have no rc.netdevice file which tell me that /sbin/netconfig didn't recognize my interface. rcmodules contains no reference to anything resembling my interface. Do I need additional modules or is my onboard lan simply not supported?
I have Kubuntu 64 Gutsy on another partition. The Ethernet controller was recognized without problems. Google led me back to LQ http://www.linuxquestions.org/hcl/sh...t/3992/cat/all
After reading those posts I am wondering if it is a Kernel issue, Slackware 12 uses 2.6.12. There must be a way to make this work that I am not aware of (I constantly discover I am aware or very little about Linux ). I am open to suggestions and enjoy the learning process. Thanks for the quick replies to my posts.
I think that uses the r8169 module, which is included in the Slackware 12.0 kernel modules.
Are you sure that you've configured the network?
What does "ifconfig -a" show?
According to this page (http://hardware4linux.info/component/23851/) your ethernet card uses the r8169 module, which is compiled as a module in the default 2.6.21.5-smp kernel that ships with Slackware. Try typing `modprobe r8169` as root and then run `netconfig`, also as root. You should also be using the generic-smp kernel instead of the huge-smp kernel, which *may* make a difference if another module is interfering with it -- though this is probably unlikely. The page linked above also suggests booting with 'acpi=noirq noapic', which would require that you add a line in /etc/lilo.conf (something like append="acpi=noirq noapic" should do the trick), but I'm not sure if that'll work (try modprobeing the r8169 module before trying this).
This is the loopback interface. It's irrelevant for our purposes right now.
Quote:
If that module ships with the kernel it is cleverly hidden. It is not listed in /etc/rc.d/rc.modules
It's not hidden at all. Do "modinfo r8169" as root and you'll see all sorts of stuff about it, including its location in the filesystem.
More importantly, the module that your network card requires is *already* loaded (regardless of whether it's actually r8169 or not). The fact that you have two interfaces shown above proves it.
Re rc.modules, there's no reason for it to be listed there -- the module is loaded automatically by the kernel and udev.
The problem is not my network since I am sending this from my Mac connected to the same router. I did modinfo r8169 and received no response. Ping gives me 100% dropped packets. Something is obviously not right and I would very much like to find out what.
The problem is not my network since I am sending this from my Mac connected to the same router. I did modinfo r8169 and received no response. Ping gives me 100% dropped packets. Something is obviously not right and I would very much like to find out what.
How did you configure the network on the Slackware box?
It really doesn't help in troubleshooting, but did you run the modinfo command as root?
The fact that you have a network device up (despite it not working) means that the module was found. `locate r8169.ko` does find the module (in the expected directory) and an `lsmod | grep r8169` after running `modprobe r8169` should also return something, indicating that the module IS present and WAS loaded. Trust me -- it's there -- UNLESS you are not using a default Slackware kernel (2.6.21.5-smp, preferably the generic-smp kernel). As for dropped packets, are you sure your network is setup correctly (ie when you ran `netconfig`)? Are you using DHCP or did you setup static IPs? If you ping 64.233.187.99 (instead of google.com), do you then get a response? (If so it's probably your nameserver that's messed up -- check /etc/resolv.conf).
Since you are not receiving anything from `modinfo r8169`, it suggests that something is wrong with your kernel setup. Did you change anything? What kernel are you using? What is the output of `uname -a`? Post your /etc/lilo.conf. Did you make sure to actually run `lilo` after editing lilo.conf? Is /etc/lilo.conf pointing to a symlink instead of an actual kernel image? If so, where does that symlink point to? etc., etc., etc.
I will try and answer the questions I can, I don't have access to the Slack box again until Sunday Evening, working this weekend.
First, thanks again for the timely responses and help. This is why I love Linux and the Linux community.
How did you configure the network on the Slackware box?
It really doesn't help in troubleshooting, but did you run the modinfo command as root?
I first tried to configure the network with a static IP as that is how my router is set. I did that as part of the install. That didn't work so I used netconfig and changed the settings to DHCP. I then got the correct IP and netmask but no connection to the internet.
The fact that you have a network device up (despite it not working) means that the module was found. `locate r8169.ko` does find the module (in the expected directory) and an `lsmod | grep r8169` after running `modprobe r8169` should also return something, indicating that the module IS present and WAS loaded. Trust me -- it's there -- UNLESS you are not using a default Slackware kernel (2.6.21.5-smp, preferably the generic-smp kernel). As for dropped packets, are you sure your network is setup correctly (ie when you ran `netconfig`)? Are you using DHCP or did you setup static IPs? If you ping 64.233.187.99 (instead of google.com), do you then get a response? (If so it's probably your nameserver that's messed up -- check /etc/resolv.conf).
Since you are not receiving anything from `modinfo r8169`, it suggests that something is wrong with your kernel setup. Did you change anything? What kernel are you using? What is the output of `uname -a`? Post your /etc/lilo.conf. Did you make sure to actually run `lilo` after editing lilo.conf? Is /etc/lilo.conf pointing to a symlink instead of an actual kernel image? If so, where does that symlink point to? etc., etc., etc.
As I said in the above post I don't have access to the slackware box right now so I can only answer some of your questions.
I downloaded Slackware 12.0 off one of the mirrors linked from the slackware site. I used the DVD iso and selected hugesmp.s during install as that seemed appropriate for a multicore processor.
I initially set up static IP but ran netconfig and changed the settings to DHCP.
I have booted from lilo several times since install and it points to the kernel image.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
10/100/1000M Lan not found
). I am open to suggestions and enjoy the learning process. Thanks for the quick replies to my posts.
[/edit]
