View previous topic :: View next topic |
Author |
Message |
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Tue Jan 28, 2003 11:45 am Post subject: Multiple Kernel Issues ...... |
|
|
Ok I have currently 3 kernel versions available at boot , and all are running fine APART from the pain In the ass of having to re emerge the nvidia-kernel module after changing the /usr/src/linux symlink every time I boot into a different kernel, is there any way to have all the kernels use the nvidia module compiled against them at boot as per usual ???
Cheers
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
Matje l33t
Joined: 29 Oct 2002 Posts: 619 Location: Hasselt, Belgium
|
Posted: Tue Jan 28, 2003 1:43 pm Post subject: |
|
|
Compile it for one kernel, copy module, boot next kernel, re-emerge, copy module, boot next kernel, re-emerge. Copy the other two modules back to their folder in /lib/modules/kernel-version/... _________________ Life is like a box of chocolates... Before you know it, it's empty... |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Tue Jan 28, 2003 4:38 pm Post subject: |
|
|
Cheers ill give that a go .....
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Tue Jan 28, 2003 4:45 pm Post subject: |
|
|
I see when the new module is compiled the video dir gets removed from the previous kernels modules dir .......
Ill reboot when I get home and update ...putty has its downfalls lol ...
Cheers
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Tue Jan 28, 2003 7:07 pm Post subject: |
|
|
Thanks matje that sorted it
Cheers
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
AlterEgo Veteran
Joined: 25 Apr 2002 Posts: 1619
|
Posted: Tue Jan 28, 2003 8:31 pm Post subject: |
|
|
The same problem also occurs for lm-sensors, alsa, and possibly more kernel-related ebuilds. I started a similar topic a while back, basically asking the same thing.
A clever alternative to matje's solution is given here:
kybber wrote: | I am having the same problem with my RTAI kernel vs. gentoo kernel. My guess it can be solved by using the SLOT-variable in the ebuilds. For alsa, this is simply 0.9, whereas for nvidia it is the kernel version ($KV). I suppose you can just manually change the SLOT-variable in the ebuild and emerge the package for the other kernel in another slot. But if this has to be done manually for each package that causes problem, then you may as well copy the ebuilds to your PORTAGE_LOCAL dir, rename them and emerge them as totally separate packages. |
Personally, I think the "autoclean" USE flag is the key to a real solution: if you disable autoclean, portage still autocleans ebuilds that have the same version-number, causing the unwanted removal of eg. nvidia-kernel.
By default, that's of course correct, but when you're using multiple kernels.
A way to temporarily really disable the autoclean-feature, would be nice-to-have. Sugestions welcome |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Wed Jan 29, 2003 10:41 am Post subject: |
|
|
I see , I was trying to work out why even when disabled the modules got removed .....
I wonder if there is any way in the ebuild to "lock" the module against that kernel , so unless the emerge is against that specific kernel version it leaves it in place ...ie it looks to see what kernel the linux symlink is against and ignores all other versions modules
Maybe even the autoclean script could look to the ebuild that has finished and verify wether other kernels installed "depend" on the module it is about to remove ......if that makes sense ????
Cheers
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
asimon l33t
Joined: 27 Jun 2002 Posts: 979 Location: Germany, Old Europe
|
Posted: Wed Jan 29, 2003 10:59 am Post subject: |
|
|
Best post a bug report for portage. This is a annoying problem and should be solved for the general case, not for nvidia drivers alone. Portage should be intelligent enough to handle kernel dependend stuff in a sane way. Removing kernel modules which are still needed when one boots with an other kernel is not acceptable.
Cheers,
Andreas |
|
Back to top |
|
|
Swishy Guru
Joined: 06 Jun 2002 Posts: 491 Location: NZ
|
Posted: Wed Jan 29, 2003 12:43 pm Post subject: |
|
|
It appears quite a few bug reports have already been logged on this one ........no point adding to the list
Cheers
Dale. _________________ Theres no substitute for C.I. |
|
Back to top |
|
|
|