Created attachment 27174 [details] picture of the garbled screen When kdm gets started after booting up my pc, i get a garbeled screen(check the attached picture) and Xorg is using the wrong resolution (1024x768 instead of correct 1280x1024). I'm using the oss radeon driver(extra/xf86-video-ati-6.12.2-2) on x86 Archlinux. If i login via ssh and restart the kdm login manager using the rc.d script, everything seems to work fine again(screen is ok, resolution is fine, too). I've attached all kind of logs which i think could be useful. Need additional infos? Please tell me what kind of log/output etc. you need and you'll get it.
Created attachment 27175 [details] dmesg output
Created attachment 27176 [details] lspci output
Created attachment 27177 [details] [review] Xorg.0.log
Created attachment 27178 [details] xorg.conf
Is the log file from a broken or working X server? Is there any difference in it in the other case?
Created attachment 27335 [details] Xorg.0.log of garbled screen
Created attachment 27336 [details] Xorg.0.log of correct screen
It should have been the one that was written while having a garbled screen. However, i added some newer log files with better names which should be self-explanatory ;) A simple diff of those 2 files: --------------------------- [root@vater tmp]# diff -u Xorg.0.log.garbeled Xorg.0.log.correct --- Xorg.0.log.garbeled 2009-07-02 15:19:59.000000000 +0200 +++ Xorg.0.log.correct 2009-07-02 15:20:47.000000000 +0200 @@ -19,7 +19,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 2 15:17:15 2009 +(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 2 15:20:32 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) @@ -364,9 +364,7 @@ (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (II) RADEON(0): Legacy BIOS detected 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: open result is 10, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) @@ -654,13 +652,13 @@ (II) RADEON(0): [agp] Mode 0x1f000203 [AGP 0x1106/0x3189; Card 0x1002/0x5159 0x174b/0x7112] (II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001 (II) RADEON(0): [agp] ring handle = 0xf0000000 -(II) RADEON(0): [agp] Ring mapped at 0xb37a5000 +(II) RADEON(0): [agp] Ring mapped at 0xb36d8000 (II) RADEON(0): [agp] ring read ptr handle = 0xf0101000 -(II) RADEON(0): [agp] Ring read ptr mapped at 0xb8085000 +(II) RADEON(0): [agp] Ring read ptr mapped at 0xb7fb8000 (II) RADEON(0): [agp] vertex/indirect buffers handle = 0xf0102000 -(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb35a5000 +(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb34d8000 (II) RADEON(0): [agp] GART texture map handle = 0xf0302000 -(II) RADEON(0): [agp] GART Texture map mapped at 0xb30c5000 +(II) RADEON(0): [agp] GART Texture map mapped at 0xb2ff8000 (II) RADEON(0): [drm] register handle = 0x2ce00000 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): RADEONRestoreMemMapRegisters() : ---------------------------
Appendix: Switching from the garbled screen to console by pressing [ctrl]+[alt]+[f1] and instantly switching back ([ctrl]+[alt]+[f7]) to the graphical login fixes the screen, too (but takes a lot of time, switching resolution/framebuffer is very slow on this old card).
I temporary got around this issue by adding a xrandr line to /usr/share/config/kdm/Xsetup. [code] xrandr --output VGA-0 --mode 1280x1024 [/code] This is not really a fix, but at least it works.
Is this still an issue with KMS or a newer version of the driver?
Both monitor and graphic card died some time ago. Bug can be closed as i can't reproduce the problem anymore.
Closing per submitter.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.