xorg can't load qxl driver
dbn.lists at gmail.com
Mon Jun 7 16:43:29 PDT 2010
On Mon, Jun 7, 2010 at 3:37 PM, brian <brianm at io.com> wrote:
>>> I followed the instructions here:
>> Where is the qxl driver being installed? Is it the same place that the
>> server expects to find drivers? The normal place would be something
>> like /usr/lib/xorg/modules/drivers if you're on x86. I see the
>> instructions there are instructing you to pass --libdir=/usr/lib64
>> when building qxl. Don't do that if you're not on x86_64.
>> On the other hand, I don't know why you don't have the void input
>> driver. Maybe it's not installed. I don't know the debian/ubuntu
>> package name, but it might be xserver-xorg-input-void.
>> Anyway, your log would help.
> Thanks Dan, that is a start. Since the instructions didn't mention
> putting the drivers anywhere special I just put them in my home folder.
> Please excuse any dumb mistakes, I'm kind of new to this. I went ahead
> and remade the drivers in the /usr/lib/xorg/modules/drivers minus the
> --libdir=/usr/lib64 since I'm using 32 bit ubuntu.
You can actually put them where you want if you tell the server where
to find them. See the ModulePath option in xorg.conf(5). Both ways
work fine, though.
> I also installed the void driver, which you had the correct name for.
> Now when I stop and start gdm it still puts me in low graphics mode but
> says it cannot detect my screen, video adapter, and input device settings.
> Here is the last section of my xorg log, which I hope has all the
> relevant info:
Can you attach the whole log? Sometimes there's interesting things
that happen earlier in the initialization.
> hadit at Citadel:~$ sudo tail -30 /var/log/Xorg.0.log
> (II) qxl(0): Device version 0.0
> (II) qxl(0): Compression level 0, log level 0
> (II) qxl(0): Currently using mode #-1, list at 0x34
> (II) qxl(0): 14357 io pages at 0x0
> (II) qxl(0): 8294400 byte draw area at 0x3815b68
> (II) qxl(0): RAM header offset: 0x3ffeb68
> (II) qxl(0): Correct RAM signature 41525851
> (II) qxl(0): Monitor0: Using hsync range of 31.50-80.00 kHz
> (II) qxl(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz
> (II) qxl(0): Clock range: 10.00 to 165.00 MHz
> (II) qxl(0): Not using default mode "640x350" (no mode of this name)
> (II) qxl(0): Not using default mode "320x175" (bad mode
> (II) qxl(0): Not using default mode "640x400" (no mode of this name)
> (II) qxl(0): Not using default mode "320x200" (bad mode
> (II) qxl(0): Not using default mode "720x400" (no mode of this name)
> (II) qxl(0): Not using default mode "360x200" (bad mode
> 0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
> 1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
> 2: [0xae9400]
> 3: /usr/bin/X(xf86InitialCheckModeForDriver+0x1ee) [0x80da28e]
> 4: /usr/bin/X(xf86ValidateModes+0xe91) [0x80dc011]
> 5: /usr/lib/xorg/modules/drivers//qxl_drv.so [0x28ade4]
> 6: /usr/bin/X(InitOutput+0x4e9) [0x80b05b9]
> 7: /usr/bin/X(main+0x1cb) [0x807234b]
> 8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0x126b56]
> 9: /usr/bin/X [0x80719c1]
> Saw signal 11. Server aborting.
> ddxSigGiveUp: Closing log
Looks like you got a segfault (signal 11 with a partial backtrace).
I'm not sure the reason why, but this is probably going to take
someone familiar with qxl.
More information about the xorg