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.
Are you really compiling 2.6.24.4? That's moving backwards from the default kernel included with Slackware 12.1 (2.6.24.5). What is the purpose of doing so?
Are you really compiling 2.6.24.4? That's moving backwards from the default kernel included with Slackware 12.1 (2.6.24.5). What is the purpose of doing so?
Thats true, I didnt even notice that.. I have confirmed that, I am running 2.6.24.5 on my 12.1
after kernel compiling , couldnt ping other ip, buy could ping locally. can anyone tel me please, after kernel compiling, where the modules stored? sometimes new kernel label not seems while booting? default one displayed
It is VERY difficult to understand what you are doing and what you have done the way you have presented your problem. You need to explain EVERYTHING you have done and everything that is not working. At this point, I literally have no idea what you're doing.
Quote:
Originally Posted by geethas
after kernel compiling , couldnt ping other ip, buy could ping locally.
Are you sure that's a kernel issue? It is possible, but it could also be a configuration problem (try running `netconfig` as root and then issuing `/etc/rc.d/rc.inet1 restart` to restart the network interfaces).
Quote:
Originally Posted by geethas
can anyone tel me please, after kernel compiling, where the modules stored?
Again, I have no idea how you built your kernel, so I don't know. They SHOULD be placed in /lib/modules/$(uname -r), which is /lib/modules/2.6.24.5-smp for the default kernel. I tried to ask which kernel you are compiling, but you gave two different answers, making it more confusing than it should be. Please make sure that there are no typos in your posts. If you're compiling 2.6.24.5, you're going to overwrite the default modules, which isn't really a good thing. If you ARE compiling 2.6.24.5, you should set the LOCALVERSION option to something (like "custom" or something) in the kernel configuration. If you are compiling 2.6.25.4 (or later), then you don't need to worry about the LOCALVERSION option because the /lib/modules/2.6.25.4 directory does not exist and therefore will be created instead of overwritten.
Quote:
Originally Posted by geethas
sometimes new kernel label not seems while booting? default one displayed
I'm not entirely sure what you mean here. If you're suggesting that the default MODULES are being loaded, then I can help you -- but if you're talking about a LILO thing, you'll need to explain yourself better. If it is the default (2.6.24.5-smp or 2.6.24.5) modules being loaded, then the wrong rc.modules* file in /etc/rc.d is being loaded. rc.S loads the first rc.modules* file it finds, searching in the following order:
In a default setup, rc.modules is symlinked to rc.modules-2.6.24.5-smp. You should copy rc.modules-2.6.24.5-smp to rc.modules-$(uname -r) or rc.modules.local and customize the resulting file to load only the modules you need to based on your new kernel configuration.
Ok, so if you ping google you get nothing, but what happens if you ping 72.14.207.99 (IP equivalent of google.com). If the ip works but the domain name doesn't, then its a dns problem. Take a look in your /etc/resolv.conf All else fails, try putting the line: 'nameserver 4.2.2.2' at the top. If it works then, well... it works. That is the DNS I use because the DNS servers where I am located are weird and more or less deny a linux box, but a windows machine it works perfect on. 4.2.2.2 works good for me though.
Another thing you might try is 'dhcpcd eth0' . It it says something like eth0 not found, do ifconfig which will show you all of your network devices. If eth0 is not listed, then your probably didnt enable your ethernet card in your kernel config.
Another thing you might try is 'dhcpcd eth0' . It it says something like eth0 not found, do ifconfig which will show you all of your network devices. If eth0 is not listed, then your probably didnt enable your ethernet card in your kernel config.
Good advice, but I would advise using `ifconfig -a` instead to show all devices, even if they are not currently active. If a simple ifconfig is used, eth0 might not show up and the OP may be incorrectly led to believe that the device drivers are not compiled into the kernel when they actually are. If they are not shown using `ifconfig -a`, however, then you have a problem with your kernel config (probably).
Good advice, but I would advise using `ifconfig -a` instead to show all devices, even if they are not currently active. If a simple ifconfig is used, eth0 might not show up and the OP may be incorrectly led to believe that the device drivers are not compiled into the kernel when they actually are. If they are not shown using `ifconfig -a`, however, then you have a problem with your kernel config (probably).
I dont notice a difference running ifconfig vs ifconfig -a with the exception of showing my bluetooth. It shows me all mine whether they are active or not. Oh well, run ifconfig -a to be absolutely sure.
If no arguments are given, ifconfig displays the status of the cur-
rently active interfaces.
-a display all interfaces which are currently available, even if
down
Experience also tells me that ifconfig without options does not always display all detected interfaces.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.