Comment 26 for bug 86072

Created an attachment (id=11892)
Xorg.0.log for ATI Radeon 7200 connected to HP A4576A 21" CRT and git radeon driver

(In reply to comment #13)
> Can you attach your xorg log? I suspect your monitor doesn't have a mode in
> the edid for 1400x1050. The edid's preferred mode is probably 1280x1024@85,
> that's why it's getting set to that by default. you can manually add the
> 1400x1050 mode:
> xrandr --newmode <1400x1050 modeline>
> xrandr --addmode VGA-0 <1400x1050 mode name>

Ok, I will try that. I'm simply surprised that a section like

Section "Screen"
        Identifier "Screen0"
        Device "Videocard0"
        DefaultDepth 24
        SubSection "Display"
                Viewport 0 0
                Depth 24
                Modes "1400x1050"
        EndSubSection
EndSection

doesn't work anymore. All this EDID/xrandr magic is certainly great but when the user decides to overrule this autodetection stuff [following standard xorg.conf conventions], one would expect his choices to be honoured.

Concerning the crash backtrace when switching to a virtual console, I'm on a single node network, and the Xdbg script trick devised at the FDO pages doesn't seem to work here because the X server will not even start up, so it's impossible to switch to a virtual console in order to trigger the segmentation fault. The monitor simply powers off upon start of the X server. Any hint howto proceed any further? The Xdgb script is:

-----------------------------------------------------------------
#!/bin/sh

#GDB
#XSERVER

ARGS=$*
PID=$$

test -z "$GDB" && GDB=gdb
test -z "$XSERVER" && XSERVER=/usr/bin/Xorg

cat > /tmp/.dbgfile.$PID << HERE
file $XSERVER
set args $ARGS
handle SIGUSR1 nostop
handle SIGUSR2 nostop
handle SIGPIPE nostop
run
module
bt
cont
quit
HERE

$GDB -silent < /tmp/.dbgfile.$PID &> /tmp/gdb_log.$PID

rm -f /tmp/.dbgfile.$PID
echo "Log written to: /tmp/gdb_log.$PID"
-----------------------------------------------------------------