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