[arch-dev-public] Problem with X?

Damir Perisa damir.perisa at solnet.ch
Mon Oct 1 05:58:00 EDT 2007


i experienced this lock described by Jason once. it happened while X 
was idle for some minutes (and the screen was send to standby), but i 
didn't track it further. disabling power management for screen i 
wasn't able to reproduce it any more. probably the new XINPUT 
architecture is not yet working fine with the dpms off/standby 
commands?

Monday 01 October 2007, Tobias Powalowski wrote:
 | only thing i discovered now is that the lights on my keyboard are
 | not working. it's still functionall though.

now that you mention it... Number-Lock led works fine for me, but 
Caps-Lock indeed the led is always off, no matter of the state of the 
Caps-Lock. ... quite strange.


from the intel driver i get some warnings:

(WW) intel(0): Bad V_BIOS checksum

(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 
0xd0000009
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on

(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and 
initialized /usr/lib/xorg/modules/dri/i965_dri.so

and starting DRM is somehow strange: 

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] loaded kernel module for "i915" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.

I'm suffering also from the not-yet-supported wacom driver in 
xorg-server 1.4 (linuxwacom 0.7.x is not building and 0.8.y is not 
yet out).

otherwise, X works fine.

- D

-- 
.·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´
            °        °           °
             °      °            °
     ><((((º>      °              °
                    °            °
                   °            <º)))><
                  <º)))><




More information about the arch-dev-public mailing list