-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Fish wrote: > On 6/11/06, gentuxx <[EMAIL PROTECTED]> wrote: >> While looking closely at /var/log/Xorg.0.log, I noticed that Xorg had >> been built under a different kernel. So, I re-emerged Xorg under the >> new kernel. Which spawns a tangential question: How can I tell what >> other programs on my system would benefit from being re-compiled under >> the new kernel - instead of re-emerging world? > > Why do you think you need to remerge *anything* that is not a kernel > module under a new kernel? You must re-merge any proprietary graphics > drivers that you are using, like nivida-kernel or ati-drivers, or > other out of tree kernel modules (alsa-drivers, ipwXXXX, and so on), > but there is no benefit at all to remerging xorg or any other program > due to a new kernel. > > -Richard Well, when it wasn't working, I was grasping at straws to find a solution. I noticed the difference between what kernel xorg was built under and the current one, so I thought I would give it a shot.
How do I know what is out of tree, and thus what needs to be rebuilt when I recompile my kernel? I'm using an older ATI Rage128 All-in-Wonder (with the TV tuner), and through this process, I've re-emerged the ati-drivers. But, is there an easy way to tell what else *should* be recompiled? - -- gentux echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239 D840 4CF0 39E2 18D3 4A9E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEjNnxTPA54hjTSp4RAu0bAKCKuiQufVLZQZ0U6nJ4PVtwnELLsACguYSQ jMaMjGt4pPeooiR124t82bs= =XdHj -----END PGP SIGNATURE----- -- gentoo-user@gentoo.org mailing list
