Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
04-17-2006, 06:33 AM
|
#1
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Rep:
|
Output of lsmod in new kernel
Hi Everyone,
Finally got a new kernel (2.6.16.5) to compile and install, but I have a couple of questions if someone could help me out.
1. lsmod returns no modules. This is not caused by everything being built into the kernel as I did configure several modules (alsa being one, as I have read it needs to be in a new kernel.)
2. I have no X working with the error that the nVidia module could not be loaded. Again, a similar thread recently reported that the problem was corrected when the latest nVidia driver was installed. I have this driver (8756, I believe), but it reports that it found an existing nVidia driver and would overwrite it. I was hesitant to let it do that as I have the 2.4.31 kernel working great with nVidia. Anyone know of any issues with the latest nVidia driver not working with the 2.4.31 kernel?
Aside from these two things, the new kernel seems to work (I can boot to a command line, anyway), and I have no sound but I am sure I can fix that one.
Any help appreciated,
Bob
|
|
|
04-17-2006, 07:18 AM
|
#2
|
Member
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 770
Rep:
|
Looks like you are not a beginner, but could it be a simple matter of forgetting make modules_install?
is there a directory in /lib/modules corresponding to your new kernel?
Alsa does not have to be compiled as modules, but many prefer it that way.
tobyl
|
|
|
04-17-2006, 07:25 AM
|
#3
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
Nvidia driver normally cannot be used for both old and new kernels. Nvidia driver should be built each time you recompile kernel and for specific kernel only (that's why it needs kernel sources).
|
|
|
04-17-2006, 07:33 AM
|
#4
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Original Poster
Rep:
|
Thanks for replying.
Quote:
Looks like you are not a beginner, but could it be a simple matter of forgetting make modules_install?
is there a directory in /lib/modules corresponding to your new kernel?
|
Thanks for the vote of confidence, but there are still a lot of things I struggle with. But, yes, I did do make_install, and no, there is no lib/modules.
To Alien Hominid: Thanks for responding, but what I really want to know is if I do install the latest version of the nVidia driver, will it still work with the 2.4.31 kernel? The nVidia driver will not install unless it overwrites the one I am curretnly using with 2.4.31, which is very stable and I want to keep it.
Thanks for your help.
Bob
|
|
|
04-17-2006, 07:35 AM
|
#5
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
No, it won't work. (It didn't work for me).
|
|
|
04-17-2006, 07:43 AM
|
#6
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Original Poster
Rep:
|
Thank you, that is what I needed to know. Looks like I will just be X-less in 2.6.16.5. I still do not understand why X will not work without the nVidia driver. Slack 10.2 worked with X fine before I installed the driver. Do you know of any other way to get X working in the new kernel?
Thanks,
Bob
|
|
|
04-17-2006, 08:00 AM
|
#7
|
Member
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 770
Rep:
|
From Nvidia's readme.txt (/usr/doc/NVIDIA_GLX-1.0 in my case)
You can specify the location of the kernel source tree (or headers) when
you install the NVIDIA driver using the --kernel-source-path command line
option (see `sh NVIDIA-Linux-x86-1.0-8178-pkg1.run --advanced-options` for
details).
but likely Alien Hominid knows better, I have not tried this
just to clarify,
you said
Quote:
yes, I did do make_install
|
but did you do make modules_install?
tobyl
|
|
|
04-17-2006, 08:11 AM
|
#8
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Original Poster
Rep:
|
Thank you, yes I did. That was a typing error. My routine was:
make menuconfig
make bzImage
make modules
make modules_install
cp arch/i386/bzImage /boot/mynewkernel
cp .config /boot/config
cp System.map /boot/System.map
Then rebooted. Boots into the kernel fine, but no lsmod output, which I am sure is related to why I cannot get into X somehow.
Thanks for responding,
Bob
|
|
|
04-17-2006, 08:45 AM
|
#9
|
Member
Registered: Jan 2005
Location: Boston
Distribution: slackware
Posts: 502
Rep:
|
You have no sound because you compiled alsa as a module. You have to load the alsa module then you will have sound and see it in lsmod.
as for nvidia, either use the generic nv driver or reinstall the nvidia driver package (you will have to do this for every new kernel compile). I find nothing wrong with nv (actually, I don't notice much difference between that and the official nvidia package) but I don't do much with my video card.
You do not have any output of lsmod because you compiled pretty much all the modules you need directly into the kernel.
Cheers
|
|
|
04-17-2006, 10:31 AM
|
#10
|
Member
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 770
Rep:
|
dcdbutler,
if there is no /lib/modules/2.6.16.5 or whatever, then the modules were not installed
even 1 module would cause this dir to be created
so Bob is not in a position to load his alsa modules yet. It strikes me that the lsmod output is empty because the modules he configured with make menuconfig were not compiled/installed for some reason which is yet to be determined
tobyl
|
|
|
04-17-2006, 11:57 AM
|
#11
|
Member
Registered: Jan 2005
Location: Boston
Distribution: slackware
Posts: 502
Rep:
|
No you're right. I didn't see the bit about this directory being empty. That's rather strange.
|
|
|
04-17-2006, 02:16 PM
|
#12
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Original Poster
Rep:
|
Hi and thanks for responding. I do not know what happened, but I recompiled (I believe I must have recompiled a dozen times) removing all the nVidia built-in drivers, selecting VESA only, reinstalled the modules, then installed the official nVidia driver, and WONDERS, it worked! The output of lsmod now shows six modules loaded, which is about what I expected.
I really don't know what I did wrong during the config of the kernel, but it is now corrected.
Many thanks for your help, it is very much appreciated.
|
|
|
04-18-2006, 02:06 AM
|
#13
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
I think we can't use Nvidia in both kernels because nvidia drivers are installed into /usr/lib and not into any kernel specific directory. So new drivers overwrite the old ones and they can't be used both. I believe, you can make some kind of hack:
1) Compile Nvidia for an old kernel
2) Copy Nvidia drivers from /usr/lib and /usr/lib/tls (maybe some other dirs too) into separate directory
3) Boot new kernel
4) Compile Nvidia
5) Copy drivers into another separate directory
6) Write a script, which would load (copy into /usr/lib and /usr/lib/tls from specified dir) Nvidia drivers depending on the kernel which you booted
|
|
|
04-18-2006, 01:24 PM
|
#14
|
Senior Member
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,526
Original Poster
Rep:
|
Alien Hominid...you are exactly correct, I found I could no longer use the nVidia driver with the 2.4.31 kernel (won't start X now, same problem I was originally having witht the 2.6 kernel) because when it compiled for the 2.6 kernel it warned me that the 2.4 version would be overwritten and that is exactly what it did. It's really OK, though, because I am finding that using the 2.6 kernel works much better than Slack did with the 2.4 (much faster boot time.) I have read in other places that there is a way to use a separate driver for a different kernel, but I doubt if I will bother with since 2.6 is working so well.
Thank you for that info, though, I might just try it at some point.
Bob
|
|
|
All times are GMT -5. The time now is 12:05 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|