On Mon, 2010-04-12 at 08:59 -0700, David L wrote:
> Fatal server error:
> Caught signal 11 (Segmentation fault). Server aborting
>
> But if I startx with one monitor connected and then plug in the
> second monitor after X is up, it runs fine with a single active
> monitor. Then, if I run system-c
On Sun, Apr 11, 2010 at 11:52 PM, Gilboa Davara wrote:
> Most likely by default, X will try and use nouveau which, at least in my
> case, did detect both displays.
>
> Could you post the complete xorg.conf file?
>
Here's the xorg.conf file that is created by system-config-display:
# Xorg config
On Sat, 2010-04-10 at 07:54 -0700, David L wrote:
> I think I'm using the xorg-x11-drv-nv driver, not the nouveau
> driver after running system-config-display. The xorg.conf that
> system-config-display creates has a section that looks like this:
>
> Section "Device"
> Identifier "Videocar
On 04/10/2010 07:54 AM, David L wrote:
> On Fri, Apr 9, 2010 at 12:29 PM, Gilboa Davara wrote:
>
>> On Thu, 2010-04-08 at 15:15 -0700, David L wrote:
>>
>>> On Thu, Apr 8, 2010 at 2:55 PM, David L wrote:
>>>
I'm running f12 and after an update today, X is broken on this syste
On Fri, Apr 9, 2010 at 12:29 PM, Gilboa Davara wrote:
> On Thu, 2010-04-08 at 15:15 -0700, David L wrote:
>> On Thu, Apr 8, 2010 at 2:55 PM, David L wrote:
>> > I'm running f12 and after an update today, X is broken on this system:
>> > http://www.smolts.org/client/show/pub_8aaac744-2cff-40c2-aeed-
On Thu, 2010-04-08 at 15:15 -0700, David L wrote:
> On Thu, Apr 8, 2010 at 2:55 PM, David L wrote:
> > I'm running f12 and after an update today, X is broken on this system:
> > http://www.smolts.org/client/show/pub_8aaac744-2cff-40c2-aeed-743e9495e525
> >
> > I had it working this morning but now
On Thu, Apr 8, 2010 at 2:55 PM, David L wrote:
> I'm running f12 and after an update today, X is broken on this system:
> http://www.smolts.org/client/show/pub_8aaac744-2cff-40c2-aeed-743e9495e525
>
> I had it working this morning but now the system becomes
> unresponsive unless I boot with nomodes
I'm running f12 and after an update today, X is broken on this system:
http://www.smolts.org/client/show/pub_8aaac744-2cff-40c2-aeed-743e9495e525
I had it working this morning but now the system becomes
unresponsive unless I boot with nomodeset. I tried booting to the
kernel that I think I was us
