1 |
On 25/08/2013 02:45, »Q« wrote: |
2 |
> On Sat, 24 Aug 2013 09:49:43 +0200 |
3 |
> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
4 |
> |
5 |
>> On 24/08/2013 06:26, Chris Stankevitz wrote: |
6 |
>>> On Fri, Aug 23, 2013 at 9:12 PM, »Q« <boxcars@×××.net> wrote: |
7 |
>>>> It looks like maybe the best way to tell which ebuilds support |
8 |
>>>> which kernels is to read the conditional for the ewarn message in |
9 |
>>>> each ebuild. |
10 |
>>> |
11 |
>>> If this sort of problem spreads it might be good to build into |
12 |
>>> portage some kind of blocker/keyword mechanism so that users need |
13 |
>>> not deal with this.... not that I have any appreciation for the |
14 |
>>> work involved. |
15 |
>> |
16 |
>> Those tools already exist. |
17 |
>> |
18 |
>> Blockers, which do not really apply here; |
19 |
> |
20 |
> In a comment on the bug (which is full of bugspam), someone suggested |
21 |
> blocking kernels which are incompatible with the currently-installed |
22 |
> nvidia-drivers. I'm glad that idea was dismissed. |
23 |
> |
24 |
>> elog messages |
25 |
> |
26 |
> Those elog messages are presented after compiling a new kernel and then |
27 |
> trying and failing to compile nvidia-drivers. So now I grep the |
28 |
> nvidia-drivers ebuilds for the messages before I compile a new kernel. |
29 |
> |
30 |
> A wiki page with info about which nvidia-drivers will build against |
31 |
> which kernels would be a nice thing to have. |
32 |
|
33 |
Your reply demonstrates nicely the true nature of the problem: |
34 |
|
35 |
With nvidia-drivers, sometimes things break and there's nothing sane |
36 |
that portage and the devs can do to help you. You can't check the |
37 |
configured kernels as they may not be running. You can't check the |
38 |
installed sources as they may not be in use. You can't even try identify |
39 |
the sources symlinked by /usr/src/linux as they may have been patched, |
40 |
tweaked or modified and nvidia-drivers may well build whereas against |
41 |
stock sources they don't. |
42 |
|
43 |
The entire problem is completely due to how nVidia chose to do things, |
44 |
it's their business decision. Now, if they were to get their shim code |
45 |
into mainline, most of this nonsense would not happen anymore. |
46 |
|
47 |
The only thing left for Portage and the devs to do is to provide the |
48 |
ebuild and ask you to run it. If it doesn't compile, then don't run that |
49 |
kernel. |
50 |
|
51 |
I doubt your wiki page idea will work, it will be just accurate enough |
52 |
to look like it might work and just inaccurate enough to be useless. |
53 |
Which brings you back to the previous paragraph - try emerge |
54 |
nvidia-drivers and if it fails then don't use that kernel. |
55 |
|
56 |
|
57 |
|
58 |
-- |
59 |
Alan McKinnon |
60 |
alan.mckinnon@×××××.com |