| 1 |
On 03/05/12 17:13, Raffaele BELARDI wrote: |
| 2 |
> On 05/03/2012 08:50 AM, Nikos Chantziaras wrote: |
| 3 |
>> On 03/05/12 09:39, Raffaele BELARDI wrote: |
| 4 |
>>> One month ago I switched to an Nvidia-based (ASUS GT520, PCI-e) video |
| 5 |
>>> card on an ~amd64 box. I immediately had problems with the latest Nvidia |
| 6 |
>>> driver causing a segfault when X started (text console is ok) so I |
| 7 |
>>> switched to 295.20-r1 and everything was fine. |
| 8 |
>>> |
| 9 |
>>> But I forgot to mask 295.40 and during yesterday's update it got pulled |
| 10 |
>>> in again, with the same segfault behaviour when starting X. |
| 11 |
>>> |
| 12 |
>>> I tried to manually downgrade nvidia-drivers but now glibc is upgraded |
| 13 |
>>> to 2.15-r1 and nvidia-drivers-295.20-r1 depends on an older glibc |
| 14 |
>>> (2.14.1-r3, I think). Emerge refuses to downgrade glibc so I am stuck. |
| 15 |
>>> |
| 16 |
>>> Since it is a mythtv box I want to stay away from nouveau. No problem |
| 17 |
>>> myself with it but most of the mythtv development is around proprietary |
| 18 |
>>> nvidia drivers. |
| 19 |
>>> |
| 20 |
>>> What other options do I have? |
| 21 |
>>> Is everybody running nvidia-drivers-295.40 without problems? |
| 22 |
>> |
| 23 |
>> No problems here, but you can try 302.07 (I run those since yesterday.) |
| 24 |
>> The usual way: copy the ebuild in your local overlay and rename it to |
| 25 |
>> nvidia-drivers-302.07.ebuild, then do a digest. Same for |
| 26 |
>> nvidia-settings, but edit it and remove the patches. |
| 27 |
> |
| 28 |
> thanks, but I'd rather keep that as a last option because I have no |
| 29 |
> guarantee of success with the 302.07 driver. |
| 30 |
|
| 31 |
There are no guarantees in life. Only wasted time, which in this case |
| 32 |
amounts to 5-8 minutes for copying/editing and emerging. If you even |
| 33 |
need a guarantee even for not losing 8 minutes of your time, then I |
| 34 |
don't know :-/ |
Archives