On 07/09/2012 05:30 AM, Joseph wrote:
> On 07/08/12 16:08, Joseph wrote:
>> On 07/08/12 17:48, Michael Mol wrote:
>>
>>> Re-emerge the drivers. I don't know a quick-and-easy way to scoop them
>>> all up, though.
>>>
>>> -- 
>>> :wq
>>
>> I did:
>>  emerge $(qlist -IC x11-drivers)
>>
>> you can list the drivers by runing:
>> qlist -IC x11-drivers
>>
>> It doesn't help.
> 
> Since in make.conf I have:
> VIDEO_CARDS="radeon vesa"
> 
> one of them should be able to start X after I recompile the drivers:
> qlist -IC x11-drivers
> x11-drivers/xf86-input-evdev
> x11-drivers/xf86-video-ati
> x11-drivers/xf86-video-vesa
> 
> but it deosn't.  What else to check.
> 
> In the log I get:
> [   805.883] 15: /usr/bin/X (0x400000+0x24609) [0x424609]
> [   805.883] Segmentation fault at address 0x9c
> [   805.883] Fatal server error:
> [   805.883] Caught signal 11 (Segmentation fault). Server aborting
> [   805.883] [   805.883] Please consult the The X.Org Foundation
> support      at http://wiki.x.org
>  for help. [   805.883] Please also check the log file at
> "/var/log/Xorg.0.log" for additional information.
> [   805.883] [   805.886] Output CRT1 disable success
> [   805.891] Blank CRTC 0 success
> [   805.891] Disable CRTC memreq 0 success
> [   805.891] Disable CRTC 0 success
> [   805.891] Blank CRTC 1 success
> [   805.891] Disable CRTC memreq 1 success
> [   805.891] Disable CRTC 1 success
> [   805.891] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [  
> 805.891] (II) RADEON(0):   MC_FB_LOCATION   : 0x00e700c0 0x00e700c0
> [   805.891] (II) RADEON(0):   MC_AGP_LOCATION  : 0x00000000
> [   805.902] (II) RADEON(0): avivo_restore !
> [   806.002] Enable CRTC 0 success
> [   806.002] Enable CRTC memreq 0 success
> [   806.002] Unblank CRTC 0 success
> [   806.005] Server terminated with error (1). Closing log file.
> 

Did you by chance compile libc with gcc 4.7 and xorg with 4.6? I had did
something like this with gnome and dependent libraries causing segfaults
just like this.

--
Nilesh Govindrajan
http://nileshgr.com



Reply via email to