View previous topic :: View next topic |
Author |
Message |
CDM Guest
|
Posted: Thu Aug 29, 2002 6:06 am Post subject: Kernel recompile |
|
|
After recompiling my kernel to change some settings everything works fine but alsa. The stuff I changed in no way effects alsa and everything will work fine if I re emerge the alsa stuff but there must be a less time consuming way without all the hassle, right? |
|
Back to top |
|
|
Valen Apprentice
Joined: 18 Aug 2002 Posts: 197 Location: Toronto, Ontario, Canada
|
Posted: Thu Aug 29, 2002 6:10 am Post subject: |
|
|
Is it possible that your alsa modules got cleared out when you recompiled the kernel? IIRC they stay in the same place as all the other kernel stuff. |
|
Back to top |
|
|
masseya Bodhisattva
Joined: 17 Apr 2002 Posts: 2602 Location: Baltimore, MD
|
Posted: Thu Aug 29, 2002 7:37 am Post subject: |
|
|
Valen wrote: | Is it possible that your alsa modules got cleared out when you recompiled the kernel? IIRC they stay in the same place as all the other kernel stuff. |
This is correct you will have to re-emerge alsa every time you compile your kernel. This applies for nvidia drivers, pcmcia-cs drivers, etc.. _________________ if i never try anything, i never learn anything..
if i never take a risk, i stay where i am.. |
|
Back to top |
|
|
CDM Guest
|
Posted: Thu Aug 29, 2002 9:04 am Post subject: . |
|
|
Hrmm...
Thats odd, I haven't had to recompile my nvidia drivers yet and its been several recompiles.
Alsa is the only thing I ever have to do, thats why I was wondering if I was missing something obvious. |
|
Back to top |
|
|
masseya Bodhisattva
Joined: 17 Apr 2002 Posts: 2602 Location: Baltimore, MD
|
Posted: Thu Aug 29, 2002 2:44 pm Post subject: |
|
|
Actually, now that I think about it I think I've done the same thing. I could be wrong. I know you have to do this for pcmcia-cs and alsa though. I remember doing those distinctly. Nvidia may be different. _________________ if i never try anything, i never learn anything..
if i never take a risk, i stay where i am.. |
|
Back to top |
|
|
Valen Apprentice
Joined: 18 Aug 2002 Posts: 197 Location: Toronto, Ontario, Canada
|
Posted: Thu Aug 29, 2002 3:48 pm Post subject: |
|
|
Don't the graphics modules sit somewhere in the X11 directory structure? |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Thu Aug 29, 2002 6:08 pm Post subject: |
|
|
Valen wrote: | Don't the graphics modules sit somewhere in the X11 directory structure? |
You're thinking of nvidia-glx. nvidia-kernel does indeed sit in /lib/modules, and must be reemerged after you build a new kernel. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
CDM Guest
|
Posted: Thu Aug 29, 2002 8:51 pm Post subject: . |
|
|
Well I just tested it again and nvidia has no problems after recompile without re-emerging but alsa does.
Not sure how I the nvidia stuff works like that but I won't complain |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Thu Aug 29, 2002 9:18 pm Post subject: Re: . |
|
|
CDM wrote: | Well I just tested it again and nvidia has no problems after recompile without re-emerging but alsa does.
Not sure how I the nvidia stuff works like that but I won't complain |
Can anyone else confirm this finding? If this is really true, we need to update our FAQ entry on this point. I must admit, this makes no sense to me. Are you calling "make modules_install" when you compile your kernel? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
CDM Guest
|
Posted: Thu Aug 29, 2002 9:41 pm Post subject: . |
|
|
yes I make clean bzImage modules modules_install after make dep.
The nvidia works fine and the alsa still has to be re-emerged.....Its not a huge deal, I just wondered how the nvidia worked and alsa didn't and wanted to make alsa do the same. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Thu Aug 29, 2002 9:47 pm Post subject: Re: . |
|
|
CDM wrote: | yes I make clean bzImage modules modules_install after make dep.
The nvidia works fine and the alsa still has to be re-emerged.....Its not a huge deal, I just wondered how the nvidia worked and alsa didn't and wanted to make alsa do the same. |
It's a big deal to me, because I don't want our FAQ to be wrong. So to confirm, after you make modules_install, and without reemerging nvidia-kernel, you still find something with the command: Code: | $ find /lib/modules/[kernelversion]/ -name 'NV*' |
...and when rebooting with this new kernel, lsmod shows NVdriver loaded? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Thu Aug 29, 2002 9:52 pm Post subject: |
|
|
Excuse me while I butt in with my non nvidia system . I thought I'd read somewhere that there were 2 different types of nvidia drivers? Can anyone confirm this? _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Guest
|
Posted: Thu Aug 29, 2002 9:57 pm Post subject: |
|
|
kanuslupus wrote: | Excuse me while I butt in with my non nvidia system . I thought I'd read somewhere that there were 2 different types of nvidia drivers? Can anyone confirm this? | Yes, it is possible that the user is using the "nv" module, and only thinks he is using NVDriver.
I always rm the kernel modules directory before recompiling a particular kernel, that way I *know* everything that's going to be in there, and nothing is left over from before. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Thu Aug 29, 2002 9:59 pm Post subject: |
|
|
Anonymous wrote: | I always rm the kernel modules directory before recompiling a particular kernel, that way I *know* everything that's going to be in there, and nothing is left over from before. |
I checked this before I posted originally with "make -n modules_install". Here's the first four things "make modules_install" does: Code: | rm -rf /lib/modules/2.4.18-xfs/kernel
rm -f /lib/modules/2.4.18-xfs/build
mkdir -p /lib/modules/2.4.18-xfs/kernel
ln -s /usr/src/linux-2.4.18-xfs /lib/modules/2.4.18-xfs/build |
_________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
Guest
|
Posted: Thu Aug 29, 2002 10:09 pm Post subject: |
|
|
rac wrote: | Anonymous wrote: | I always rm the kernel modules directory before recompiling a particular kernel, that way I *know* everything that's going to be in there, and nothing is left over from before. |
I checked this before I posted originally with "make -n modules_install". Here's the first four things "make modules_install" does: Code: | rm -rf /lib/modules/2.4.18-xfs/kernel
rm -f /lib/modules/2.4.18-xfs/build
mkdir -p /lib/modules/2.4.18-xfs/kernel
ln -s /usr/src/linux-2.4.18-xfs /lib/modules/2.4.18-xfs/build |
|
That's curious. I exaggerated when I said "always" btw; yesterday I recompiled without vaping that directory first, and my wireless-adapter modules (not a part of the kernel dist) were still there afterwards. -and I did use "modules_install" |
|
Back to top |
|
|
CDM Guest
|
Posted: Thu Aug 29, 2002 10:30 pm Post subject: . |
|
|
Quote: | bash-2.05a# find /lib/modules/2.4.19-gentoo-r7/ -name 'NV*'
/lib/modules/2.4.19-gentoo-r7/video/NVdriver
|
And it loads the NVdriver fine everytime after kernel compile along with the nvidia splash screen when gnome starts and I'm pretty sure I wouldn't be getting the same fps in q3
This is the first time I have ever NOT had to recompile the drivers in linux after a kernel compile. Not sure what changed but I sure do like it. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Thu Aug 29, 2002 10:43 pm Post subject: Re: . |
|
|
CDM wrote: | Quote: | bash-2.05a# find /lib/modules/2.4.19-gentoo-r7/ -name 'NV*'
/lib/modules/2.4.19-gentoo-r7/video/NVdriver
|
|
Thank you for taking the time to follow up on this. I will work on fixing the FAQ.
Quote: | Not sure what changed but I sure do like it. |
Here's what changed, part of a diff between nvidia-kernel-1.0.2960.ebuild and nvidia-kernel-1.0.2960-r1.ebuild: Code: | - insinto "/lib/modules/${KV}/kernel/video"
+ insinto "/lib/modules/${KV}/video" |
Your module is in the video directory, which doesn't get wiped by modules_install. Mine (older) is in kernel/video, which does. ALSA could probably do the same thing by moving their modules out of kernel, too.
And, as I check the Changelog, sure enough: Quote: | 17 Aug 2002; Gustavo Felisberto <gustavo@felisberto.net>: Changed a small
line in the ebuild so that the kernel module gets installed in
/lib/modules/${KV}/video this way a "make modules_install" in /usr/src/linux
will not erase the nvidia module. (added by drobbins) This closes bug #5572. |
_________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
|