1 |
On 05/03/2012 08:50 AM, Nikos Chantziaras wrote: |
2 |
> On 03/05/12 09:39, Raffaele BELARDI wrote: |
3 |
>> One month ago I switched to an Nvidia-based (ASUS GT520, PCI-e) video |
4 |
>> card on an ~amd64 box. I immediately had problems with the latest Nvidia |
5 |
>> driver causing a segfault when X started (text console is ok) so I |
6 |
>> switched to 295.20-r1 and everything was fine. |
7 |
>> |
8 |
>> But I forgot to mask 295.40 and during yesterday's update it got pulled |
9 |
>> in again, with the same segfault behaviour when starting X. |
10 |
>> |
11 |
>> I tried to manually downgrade nvidia-drivers but now glibc is upgraded |
12 |
>> to 2.15-r1 and nvidia-drivers-295.20-r1 depends on an older glibc |
13 |
>> (2.14.1-r3, I think). Emerge refuses to downgrade glibc so I am stuck. |
14 |
>> |
15 |
>> Since it is a mythtv box I want to stay away from nouveau. No problem |
16 |
>> myself with it but most of the mythtv development is around proprietary |
17 |
>> nvidia drivers. |
18 |
>> |
19 |
>> What other options do I have? |
20 |
>> Is everybody running nvidia-drivers-295.40 without problems? |
21 |
> |
22 |
> No problems here, but you can try 302.07 (I run those since yesterday.) |
23 |
> The usual way: copy the ebuild in your local overlay and rename it to |
24 |
> nvidia-drivers-302.07.ebuild, then do a digest. Same for |
25 |
> nvidia-settings, but edit it and remove the patches. |
26 |
|
27 |
thanks, but I'd rather keep that as a last option because I have no |
28 |
guarantee of success with the 302.07 driver. |
29 |
|
30 |
Another possibility came to my mind: I have a backup partition which I |
31 |
did not upgrade since I switched from the on-board ATI GPU to the Nvidia |
32 |
video card. |
33 |
I'll try to upgrade that partition masking >nvidia-drivers-295.20-r1. |
34 |
|
35 |
It'd be interesting to understand why I'm getting the segfault with the |
36 |
295.40, but being a closed driver I suppose there is little I can diagnose. |
37 |
|
38 |
raffaele |