I did have to redo my kernel config almost completely with the 4.4.0 release.
I did:
       make mrproper      #cleans eveything up
       make defconfig      #basic x86_64 config
       make xconfig         #custom configs (needs qt)

The new kernel (informed by the old 4.3.3 config) booted and ran the first time,
but I got a lockup after the first screen timeout (nothing would wake
up the video)
and I netted in and did a "shutdown -r now" followed by a rebuild of
all the kernel
dependent packages (there are about 24 in my mix).

Since that, I have not had a problem.  I suspect that perhaps there are enough
changes in the 4.4.0 kernel that glib and sone of the others need a rebuild.

I have a little script that scans the installed package db to find
everything that
references the kernel and linux-headers eclasses and rebuilds them.  There are
one or two packages in that list that don't strictly need a rebuild
(e.g. google-chrome-beta)
but with time to spare I just let emerge go-to-town with everything.
(I scan the INHERETED files for linux-info and linux-mod to make a
temp set for emerge.)

With new kernel versions being tracked ell the time, this little trick
has cured lots of ills since
I wrote it in 2013.  I've posted it once (I think) but I'll do so
again in a few minutes on a new thread.


-- 
G.Wolfe Woodbury
[email protected]

Reply via email to