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