What to rebuild after a kernel upgrade?

Message

dE_logics · Post by **dE_logics** » Wed Mar 30, 2011 2:06 pm

Apparently there's no info on this and I started to realize it when X started to crash for some unknown reason (X, kernel logs reveal nothing at all....).

So what should be rebuild after a kernel upgrade?

XQYZ · Post by **XQYZ** » Wed Mar 30, 2011 2:14 pm

Stuff that links against kernel sources? Nvidia's binary blob driver and extensions/modules for virtual servers comes to mind. Also everything that brings a kernel module along I guess.

GES · Post by **GES** » Wed Mar 30, 2011 3:09 pm

Code: Select all

# eix module-rebuild
[I] sys-kernel/module-rebuild
     Available versions:  0.5 ~0.6
     Installed versions:  0.5(16.25.50 2011-01-27)
     Homepage:            http://www.gentoo.org/
     Description:         A utility to rebuild any kernel modules which you have installed

d2_racing · Post by **d2_racing** » Wed Mar 30, 2011 3:23 pm

Yep, I use module-rebuild since 2008, it's really something that I use when I change my kernel.

aCOSwt · Post by **aCOSwt** » Wed Mar 30, 2011 3:24 pm

GES wrote:
Code: Select all
# eix module-rebuild

Of course, module-rebuild is the final solution... provided... you know with what you should populate it...

Because, per se, module-rebuild will not discover this automagically.

As SQYZ correctly points out, the kind of thing you are likely to have to rebuild is drivers.
But... depending on what you have installed, it might not be enough.

mikegpitt and I have had a fruitful discussion on how to find exhaustively the packages : (Posts 4 and 6) http://forums.gentoo.org/viewtopic-t-85 ... ernel.html

depontius · Post by **depontius** » Wed Mar 30, 2011 7:53 pm

aCOSwt wrote:
GES wrote:
Code: Select all
# eix module-rebuild
Of course, module-rebuild is the final solution... provided... you know with what you should populate it...
Because, per se, module-rebuild will not discover this automagically.

Has "module-rebuild populate" failed for you?

aCOSwt · Post by **aCOSwt** » Wed Mar 30, 2011 9:57 pm

depontius wrote:Has "module-rebuild populate" failed for you?

It has.
Well... in the past I mean...

So... things might have changed since.
module-rebuild populate was recurrently unable to find drivers with more or less exotic naming schemes, those of the kind only a driver programmer can imagine...

mixing hyphens and digits.
It was also unable to correctly deal with vmware kernel modules.
My opinion being that this kind of tool is either exhaustive or useless, I no longer use it.

davidm · Post by **davidm** » Wed Mar 30, 2011 10:04 pm

d2_racing wrote:Yep, I use module-rebuild since 2008, it's really something that I use when I change my kernel.

Same here. They cover it decently in the kernel upgrade guide as well.
http://www.gentoo.org/doc/en/kernel-upgrade.xml

depontius · Post by **depontius** » Thu Mar 31, 2011 1:50 am

aCOSwt wrote: module-rebuild populate was recurrently unable to find drivers with more or less exotic naming schemes, those of the kind only a driver programmer can imagine... mixing hyphens and digits.

Since my usage generally extends to nvidia-drivers, openafs-kernel, and lirc, I've never seen a problem. But then, none of those are exotic.

dE_logics · Post by **dE_logics** » Thu Mar 31, 2011 3:51 am

I was wondering I need to rebuild things like X libs, *glib* etc...

slackline · Post by **slackline** » Thu Mar 31, 2011 8:25 am

If you're using the latest development arm of portage then you can use...

Code: Select all

emerge @module-rebuild && emerge @x11-module-rebuild

...without the need for sys-kernel/module-rebuild.

truekaiser · Post by **truekaiser** » Sun May 08, 2011 7:48 pm

depontius wrote:
aCOSwt wrote: module-rebuild populate was recurrently unable to find drivers with more or less exotic naming schemes, those of the kind only a driver programmer can imagine... mixing hyphens and digits.
Since my usage generally extends to nvidia-drivers, openafs-kernel, and lirc, I've never seen a problem. But then, none of those are exotic.

Lirc in the portage tree is out of date and no longer needed now that it is being included in the kernel all be it under staging drivers.

depontius · Post by **depontius** » Sun May 08, 2011 7:55 pm

truekaiser wrote:
depontius wrote:
aCOSwt wrote: module-rebuild populate was recurrently unable to find drivers with more or less exotic naming schemes, those of the kind only a driver programmer can imagine... mixing hyphens and digits.
Since my usage generally extends to nvidia-drivers, openafs-kernel, and lirc, I've never seen a problem. But then, none of those are exotic.
Lirc in the portage tree is out of date and no longer needed now that it is being included in the kernel all be it under staging drivers.

You still need the userspace side, and some (like me) haven't moved to devinput yet. I saw a while back on the list one of the developers saying that some 2.6.37 code might be stale, and the 2.6.38 drivers would likely work better. It's a little new, yet.

cwr · Post by **cwr** » Mon May 09, 2011 8:38 am

dE_logics wrote:I was wondering I need to rebuild things like X libs, *glib* etc...

No. That is, I've never had to, and I don't see how they could be affected. The problem
is in modules which the kernel doesn't automatically rebuild, and some kernel profiling and
debugging stuff. I've never used binary drivers, but I'd expect that they'd bite you too.

Will

Sysa · Post by **Sysa** » Mon May 09, 2011 9:42 am

Usually I do

Code: Select all

emerge -1 $(qlist -IC udev driver)

only but recently (after migration to 2.6.37 and KMS) I had to make

Code: Select all

emerge -1 $(qlist -IC xorg x11 drm)

also to solve a "black screen" problem.