[r300 KMS] KMS uses wrong display resulution, xrandr causes X to crash
Submitted by Daniel Klaffenbach
Assigned to Default DRI bug account
Description
Created attachment 31034
dmesg from 2.6.32-rc6 after X crash
I just tested KMS with 2.6.32-rc6 for my Radeon Xpress 200M in a HP nx6125.
When the system boots KMS selects the wrong resolution for the framebuffer (800x600 instead of 1024x768). In dmesg it says:
[drm] LVDS-11: set mode 1024x768 16
[drm] crtc 1 is connected to a TV
[drm] TV-9: set mode 800x600 17
However, I do not have any other monitors/TVs connected (just the laptop panel). But the worst thing of all is that X behaves abnormally:
- X also uses 800x600
- X (or let's say my XSession) does not load correctly
- to make my XSession start up completely I need to switch to VT1 and back to VT7
- when issuing "xrandr --output LVDS --auto" Xorg crashes immediately
I had KMS enabled in 2.6.31 and it worked - this is why this bug seems to be a regression.
The packages I am using:
- XServer 1.7.1
- mesa 7.6
- libdrm 2.4.15
- xf86-video-ati git master
I did compile all the X packages with debug support, but still gdb does not produce any useful output:
```
(gdb) bt full
#0 0xb71a57f1 in ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so
No symbol table info available.
#1 0x0000009c in ?? ()
No symbol table info available.
#2 0x00000000 in ?? ()
No symbol table info available.
```
I am going to attach my xorg.conf, dmesg and Xorg.log. This crappy Xpress 200M chipset makes nothing but troubles in newer kernel versions. With an old system (Ubuntu 7.10) it runs stable. With KMS and/or newer video-ati version not even suspend2ram is working any more - but this is a different story.
**Patch 31034**, "dmesg from 2.6.32-rc6 after X crash":
dmesg