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