When I boot my system and start X, everything is fine. But when I kill X and start it again xorg uses a resolution of just 800x600 instead of 1400x1050 as before. When i run xrandr, the only available resolutions listed are 640x800 and 800x600, after restarting X. When i reboot my system it is fine, again. I pasted my xorg.conf at the bottom of this bug report, but this problem also occurs when I use the configuration generated by Xorg -configure without changes. $ uname -a Linux korv 2.6.23.8 #1 Sun Nov 18 16:53:39 CET 2007 i686 Intel(R) Pentium(R) M processor 1.70GHz GenuineIntel GNU/Linux $ lspci | grep VGA 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 02) $ lsmod Module Size Used by ipv6 195940 8 snd_pcm_oss 33568 0 snd_mixer_oss 12352 2 snd_pcm_oss snd_seq_dummy 2500 0 snd_seq_oss 24704 0 snd_seq_midi_event 5184 1 snd_seq_oss snd_seq 37392 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 5772 3 snd_seq_dummy,snd_seq_oss,snd_seq radeon 109600 2 drm 62996 3 radeon intel_agp 19924 1 agpgart 23920 2 drm,intel_agp rtc 8472 0 dm_crypt 9608 1 dm_mod 39424 5 dm_crypt video 15504 0 output 2624 1 video parport_pc 22308 0 ohci1394 24944 0 irtty_sir 6208 0 parport 29064 1 parport_pc ieee1394 68724 1 ohci1394 sir_dev 11076 1 irtty_sir irda 154236 2 irtty_sir,sir_dev crc_ccitt 1792 1 irda e1000 105408 0 ipw2200 125620 0 yenta_socket 20876 0 rsrc_nonstatic 8000 1 yenta_socket pcmcia_core 28880 2 yenta_socket,rsrc_nonstatic snd_intel8x0 25692 1 snd_ac97_codec 86560 1 snd_intel8x0 ac97_bus 1792 1 snd_ac97_codec snd_pcm 57992 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec snd_timer 15300 2 snd_seq,snd_pcm ehci_hcd 25740 0 snd 37284 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer snd_page_alloc 7048 2 snd_intel8x0,snd_pcm uhci_hcd 18380 0 usbcore 102872 3 ehci_hcd,uhci_hcd joydev 7296 0 unix 18992 330 $ cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "AIGLX" "true" Option "DontZap" "true" EndSection Section "Files" RgbPath "/usr/share/X11/rgb" ModulePath "/usr/lib/xorg/modules" FontPath "unix/:7100" FontPath "/usr/share/fonts/util" FontPath "/usr/share/fonts/misc/" EndSection Section "Module" Load "i2c" Load "bitmap" Load "ddc" Load "glx" Load "extmod" Load "record" Load "dbe" Load "glx" Load "xtrap" Load "dri" Load "freetype" Load "type1" Load "int10" Load "vbe" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbLayout" "de" Option "XkbModel" "pc105" Option "XkbVariant" "nodeadkeys" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" Identifier "Card0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "Radeon R250 [Mobility FireGL 9000]" BusID "PCI:1:0:0" Option "DynamicClocks" "on" Option "BIOSHotkeys" "on" Option "RenderAccel" "on" Option "XAANoOffscreenPixmaps" "true" Option "EnablePageFlip" "on" Option "ColorTiling" "on" Option "FBTexPercent" "90" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1400x1050" ViewPort 0 0 EndSubSection EndSection Section "DRI" Mode 0666 EndSection Section "Extensions" Option "Composite" "Enable" EndSection
I also tried two older versions of the linux kernel (2.6.18.8 and 2.6.23.1) and the new xorg-7.3 with xorg-server-1.4. But the problem still exists. I am currently using the "vesa" driver instead of the "radeon" and it works. But this doesn't solved this bug.
Please attach (as opposed to cutting and pasting) your xorg logs (working and non-working).
Created attachment 12645 [details] Log file after first start with radeon driver, when it still works as expected.
Created attachment 12646 [details] [review] Log file after second start with radeon driver, when it fails as described in this bug.
Created attachment 12647 [details] Log file after starting with vesa driver.
The second time around the driver is finding a second monitor attached for some reason and attempting to use it. The following should fix it: Option "MergedFB" "FALSE"
Thanks. This worked for me. But even though I don't use MergedFB, shouldn't it work with the radeon driver?
(In reply to comment #7) > Thanks. This worked for me. But even though I don't use MergedFB, shouldn't it > work with the radeon driver? > For some reason it's detecting a phantom monitor on the second start up which is causing your problem. Turning off mergedfb causes the driver to ignore the second output.
The old version of the driver is no longer actively maintained. Please upgrade to the latest version.
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.