Xorg crashes...

[Justin P. Mattock]

On 01/06/10 08:56, Ryan Daly wrote:
> On 01/06/2010 10:53 AM, Jeremy Huddleston wrote:
>> On Jan 6, 2010, at 10:50, Ryan Daly wrote:
>>
>>>> not sure whats going on, but by
>>>> looking at the log I see some userspace tools
>>>> erroring out(which should not keep the screen from
>>>> going forward), but I also see something about
>>>> fglrx not found.. could either mean that you
>>>> haven't the xorg module, as well as the kernel module,
>>>> or the fglrx module is crapping out with the
>>>> xserver version(had this a while ago with fglrx,
>>>> ended up switching to radeon);
>>>>
>>>> hope this helps.
>>>>
>>>> Justin P. Mattock
>>>>
>>> Justin - thanks for your reply.
>>>
>>> Is fglrx ATI specific?  I have a nVidia card.  I'm not sure how they all
>>> play together, though.
>>
>> fglrx is the closed-source ATI driver
>>
>
> OK.  That rules that out then...
>
> The backtrace is pretty consistent with the following few lines:
>
> Program received signal SIGTERM, Terminated.
> 0x00007f146bab8110 in __close_nocancel () from /lib/libpthread.so.0
> (gdb) backtrace r full
> #0  0x00007f146bab8110 in __close_nocancel () from /lib/libpthread.so.0
> No symbol table info available.
> #1  0x00007f1466f61516 in ?? () from
> /usr/lib/xorg/modules/input//evdev_drv.so
> No symbol table info available.
> #2  0x0000000000447723 in DisableDevice (dev=0x18a33a0) at
> ../../dix/devices.c:407
>
> Are those lines pointing to a device or to the card possibly?
>
> I'm running the same version of Ubuntu on three different machines, and
> I'm only experiencing the Xorg restarts on one system.  I'm at a loss...
>

yeah.. fglrx is specific to
ati chipsets(but could be wrong).

In your case If you have nvidia
you probably should be using
nv, nouveau, or the proprietary module.

if you can does changing your xorg.conf
to use vesa/vga have the xserver start properly?


Justin P. Mattock