1 |
On Thu, May 3, 2012 at 10:13 AM, Raffaele BELARDI |
2 |
<raffaele.belardi@××.com> wrote: |
3 |
> On 05/03/2012 08:50 AM, Nikos Chantziaras wrote: |
4 |
>> On 03/05/12 09:39, Raffaele BELARDI wrote: |
5 |
>>> One month ago I switched to an Nvidia-based (ASUS GT520, PCI-e) video |
6 |
>>> card on an ~amd64 box. I immediately had problems with the latest Nvidia |
7 |
>>> driver causing a segfault when X started (text console is ok) so I |
8 |
>>> switched to 295.20-r1 and everything was fine. |
9 |
>>> |
10 |
>>> But I forgot to mask 295.40 and during yesterday's update it got pulled |
11 |
>>> in again, with the same segfault behaviour when starting X. |
12 |
>>> |
13 |
>>> I tried to manually downgrade nvidia-drivers but now glibc is upgraded |
14 |
>>> to 2.15-r1 and nvidia-drivers-295.20-r1 depends on an older glibc |
15 |
>>> (2.14.1-r3, I think). Emerge refuses to downgrade glibc so I am stuck. |
16 |
>>> |
17 |
>>> Since it is a mythtv box I want to stay away from nouveau. No problem |
18 |
>>> myself with it but most of the mythtv development is around proprietary |
19 |
>>> nvidia drivers. |
20 |
>>> |
21 |
>>> What other options do I have? |
22 |
>>> Is everybody running nvidia-drivers-295.40 without problems? |
23 |
>> |
24 |
>> No problems here, but you can try 302.07 (I run those since yesterday.) |
25 |
>> The usual way: copy the ebuild in your local overlay and rename it to |
26 |
>> nvidia-drivers-302.07.ebuild, then do a digest. Same for |
27 |
>> nvidia-settings, but edit it and remove the patches. |
28 |
> |
29 |
> thanks, but I'd rather keep that as a last option because I have no |
30 |
> guarantee of success with the 302.07 driver. |
31 |
> |
32 |
> Another possibility came to my mind: I have a backup partition which I |
33 |
> did not upgrade since I switched from the on-board ATI GPU to the Nvidia |
34 |
> video card. |
35 |
> I'll try to upgrade that partition masking >nvidia-drivers-295.20-r1. |
36 |
> |
37 |
> It'd be interesting to understand why I'm getting the segfault with the |
38 |
> 295.40, but being a closed driver I suppose there is little I can diagnose. |
39 |
|
40 |
Emerge with --ggdb3, enable core dumps (I forget the particular |
41 |
sysctl, sorry), and open up the core dump in gdb. At the very least, |
42 |
you might get something interesting if the segfault happens in a stack |
43 |
frame belonging to an open-source function a closed blob links to, or |
44 |
if the segfault happens in a pure portion of the stack. |
45 |
|
46 |
(For example, on my broken boxes, the stack hadn't gotten into |
47 |
application-specific portions; it was still trying to get into the |
48 |
general CRT prologue code.) |
49 |
|
50 |
-- |
51 |
:wq |