[rv200] initial mode is 1280x768 instead of preferred 1280x1024

Got similar problem with a x300 and my D610 laptop.

i used to have a 1400*1050*75Hz resolution and the last ati-driver package which is working is 1:6.6.193-1ubuntu1.

Regards

I just installed the first Release Candidate for Gutsy (still using 1:6.7.195-1ubuntu2). After using the Screens and Graphics Tool and the Screen Resolution Tool under System -> Preferences, I can login and get 1280x1204 @ 85. Now the only problem is that GDM still only displays 1280x768 @ 60. I will upload the new xorg.conf and Xorg.0.log. Thanks.

What do you get if you run without any xorg.conf?

Note1: I upgraded to the full release of Gutsy 7.10 (still using 1:6.7.195-1ubuntu2) and configured my resolution the same way as stated on the above post (2007-10-13).

Note2: I still get the same results as stated on the above post (2007-10-13).

If I run without xorg.conf, gdm still defaults to 1280x768 @ 60. Now when I login, the maximum resolution is 1280x800 @ 60. I am attaching my Xorg.0.log. Thank you again.

Can you please run "sudo ddcprobe > ddcprobe.txt" and attach the file ddcprobe.txt?

Attached is the ddcprobe.txt. I am still running without xorg.conf until you say otherwise. Thanks again for the help.

Seems like the server rules out the 1280x1024 modes with no xorg.conf:
II) RADEON(0): Not using default mode "1280x1024" (hsync out of range)
(II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) RADEON(0): Not using default mode "1280x1024" (vrefresh out of range)

You probably need to specify the modelines in your xorg.conf for some reason.

Ok, thanks. I did specify the modelines in my xorg.conf posted above, which didn't work either. Is there something wrong with my xorg.conf that I am not seeing? What do I do now? Thanks again.

In comment 5 you say "I can login and get 1280x1204 @ 85", with 7.10 RC I suppose. Now with 7.10 final it does not work any longer, even with that xorg.conf?

Please attach the new Xorg.0.log from using that xorg.conf.

With that xorg.conf from the above post, gdm defaults to 1280x768 @ 60. Once I login with my user name, the resolution changes to 1280x1024 @ 85 because I selected it in the "System" -> "Preferences" -> "Screen Resolution". So if I am logged in, everything seems fine. It's just that I can't get X to display to the proper resolution in gdm, only 1280x768 @ 60. I will attach both files just in case.

Thanks!

Please attach the output from "xrandr" and from "xrandr --verbose".

Attached are the outputs you requested ("xrandr" and from "xrandr --verbose"). I ran these commands in a terminal while I was logged in with 1280x1024 @ 85 resolution and I am not sure if that will affect their output. Thanks.

What if you only leave the wanted mode in the Modes line in your xorg.conf:
 Modes "1280x1024@85"

Please also try to regenerate a new xorg.conf using "sudo dpkg-reconfigure -phigh xserver-xorg" on a console, and attach it.

If I only list Modes "1280x1024@85" in my xorg.conf, I get the same results. gdm is at 1280x768 @ 60 and when I login it switches to 1280x1024@85. I am attaching the xorg.conf that I used and my Xorg.0.log. Thanks.

If I run "sudo dpkg-reconfigure -phigh xserver-xorg", the new xorg.conf gives me the same results from when I removed my xorg.conf completely. gdm is at 1280x768 @ 60 and my maximum resolution when I login is 1280x800 @ 60. Attached are the xorg.conf and Xorg.0.log. Thanks.

Sorry, this is the correct Xorg.0.log for the last post.

Can you try commenting out the Monitor entry in the Screen section:
 #Monitor "SONY CPD-E40"

I tried commenting out #Monitor "SONY CPD-E40" the my xorg.conf. It produces the same results as above. gdm is at 1280x768 @ 60 and my maximum resolution when I login is 1280x800 @ 60.

Try adding a Preferred mode, see "III.5. Forcing a preferred mode" at http://wiki.debian.org/XStrikeForce/HowToRandR12
It goes in the Monitor section, I suggest you associate it with the correct output as in "III.1. Per Output Config".

This can help us to see if the problem is that the monitor is not reporting a "preferred" mode.

Fixed!

I regenerated a new xorg.conf from the "Screen and Graphics" tool and then I added (Option "PreferredMode" "1280x1024@85") to the Monitor section in my xorg.conf. I restarted X and now my resolution is correct, both in gdm and when I login. Thank you again for your help. Will this issue be addressed in future patches or will I have to always use this fix?

Thanks!

The problem is that the monitor is not reporting any preferred mode, which makes it hard for the driver to just guess. If this is the monitor's fault, nothing can be done. If it's the driver that doesn't ask the correct way (ddc/edid problems) it might get fixed one day.

Since your ddcprobe output has only one "dtiming" entry at "1280x1024@99" we can consider it a driver bug not to choose it automatically:

"The VESA E-EDID Standard requires that the First Detailed Timing Descriptor be the “preferred” video format and subsequent detailed timing descriptors listed in order of decreasing preference."

However it doesn't extract those timings, and you don't have a 99Hz modeline.

BTW, I would not recommend the current "Screen and Graphics" tool to make an xorg.conf. According to the log it adds "MergedFB" which is obsolete in the new ati driver.

For more investigation, I can only suggest you to install the "read-edid" package and run somthing like get-edid | parse-edid

output of "sudo get-edid | parse-edid"

This does not sound good:
        Call failed

 The EDID data should not be trusted as the VBE call failed
 parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
 parse-edid: first bytes don't match EDID version 1 header
 parse-edid: do not trust output (if any).

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

Running the Live Intrepid Alpha 4 CD produces the following screen resolution: 1152x864 @ 60Hz.

Thanks for testing with Intrepid!

The issue here is that the monitor is returning EDID that the driver does not seem to recognize properly (parse-edid seems not to comprehend it either), as it doesn't pick up the correct preferred mode. Likely the monitor is simply emitting invalid edid information.

Since the DDC output seems more valid, perhaps the right workaround is to use Option "IgnoreEDID".

Please run `sudo get-edid > edid.dat` and attach that file to this bug report.

Also, if possible, could you test the monitor with a different computer (using -intel or -nv graphics if possible), and/or try a different model of monitor with your Radeon 7500, and report if you can reproduce the issue with any of those combinations.

I will try to obtain a different monitor/setup and test this further. Attached is the file edid.dat from `sudo get-edid > edid.dat'

NOTE: I installed the Live Intrepid Alpha 4 CD on my computer for testing.

For some reason the file did not save correctly. Try this instead.

Thanks for the quick response!

Actually the second file is not data but looks to be text output. The first one is data, but it looks very invalid:

$ xxd edid.dat
0000000: a000 4e13 1313 1313 1313 1313 1313 1313 ..N.............
0000010: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000020: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000030: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000040: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000050: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000060: 1313 1313 1313 1313 1313 1313 1313 1313 ................
0000070: 1313 1313 1313 1313 1313 1313 1313 1313 ................

Weird. Let me dig through some man pages and see if I can get better directions to give you.

Okay well near as I can tell my original directions were accurate: `sudo get-edid > edid.dat'

This is what I get on my system:

bryce@blackwold:/tmp$ sudo get-edid > edid.dat
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 200
 VBE string at 0x11110 "ATI R350"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call successful

bryce@blackwold:/tmp$ xxd edid.dat
0000000: 00ff ffff ffff ff00 09d1 da76 1d1e 0000 ...........v....
0000010: 2511 0103 6c34 2178 ea5a d5a7 564b 9b24 %...l4!x.Z..VK.$
0000020: 1350 54bd ef80 714f 8190 8180 818c a940 .PT...qO.......@
0000030: b300 0101 0101 283c 80a0 70b0 2340 3020 ......(<..p.#@0
0000040: 3600 0744 2100 001e d509 80a0 205e 6310 6..D!....... ^c.
0000050: 1060 5208 782d 1100 001a 0000 00fd 0038 .`R.x-.........8
0000060: 4c1e 5311 000a 2020 2020 2020 0000 00fc L.S... ....
0000070: 0042 656e 5120 3234 3157 0a20 2020 0065 .BenQ 241W. .e

Valid EDID always starts with those first few bytes 0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00, if that's any help. If your monitor is putting out something other than that, then maybe we're just screwed here...

There are some additional tips/tricks at http://john.fremlin.de/programs/linux/read-edid/. You might review that.

If you happen to have windows installed on the box, he includes directions for running the program under DOS. Guess there's a chance that might return the valid EDID.

Some additional questions... Do you have any adapters, kvms, customized cables or anything else unusual between your graphics card and your monitor? Do you have more than one graphics card installed?

You should also test booting with Option "IgnoreEDID" or Option "IgnoreDDC".

I ran "sudo get-edid > edid.dat" again and the file is attached. Below is a copy of the terminal output from my computer.
-----------------------------------------------------------------------------

qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 200
 VBE string at 0x11110 "ATI RV200"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat
0000000: ffa2 00ff ffff ff00 4dd9 9003 f24a 7b00 ........M....J{.
0000010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /....%......WG.'
0000020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL......O.Y.OqY
0000030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@.
0000040: 1300 6008 1100 001e 0000 00fd 0030 781e ..`..........0x.
0000050: 601e 000a 2020 2020 2020 0000 00fc 0053 `... .....S
0000060: 4f4e 5920 4350 442d 4534 3030 0000 00ff ONY CPD-E400....
0000070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. ..
qsomi@qsomi-desktop:~/Desktop$

---------------------------------------------------------------------------

I am not using any adapters, KVM, etc. I tried using each option (Option "IgnoreEDID" and Option "IgnoreDDC") with the default xorg.conf from the Live CD and no luck. The screen just kept flickering really bad. Unfortunately I am short on extra hardware and I don't use Windows but I will attempt to boot from the onboard video card and report those results soon. Also I removed the Option "PreferredMode" "1280x1024@85" from the my edited xorg.conf and the resolution is perfect. Please let me know if you need that xorg.conf and/or that Xorg.0.log. Thanks!

Ok, attached is the edid.dat which was generated while using the onboard video card (SiS630/730). It appears that the output is similar to the ATI Card, which I guess suggests its a monitor issue. Below is the output from the terminal window.

-------------------------------------------------------------------------
qsomi@qsomi-desktop:~/Desktop$ sudo get-edid > edid.dat
get-edid: get-edid version 1.4.1

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11110 "SiS"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination does not support DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call failed

The EDID data should not be trusted as the VBE call failed
qsomi@qsomi-desktop:~/Desktop$ xxd edid.dat
0000000: ffa2 00ff ffff ff00 4dd9 9003 f24a 7b00 ........M....J{.
0000010: 2f0a 0102 0e25 1b96 eb0c c9a0 5747 9b27 /....%......WG.'
0000020: 1248 4cff ff80 c280 a94f 8159 814f 7159 .HL......O.Y.OqY
0000030: 6159 4559 3159 863d 00c0 5100 3040 40a0 aYEY1Y.=..Q.0@@.
0000040: 1300 6008 1100 001e 0000 00fd 0030 781e ..`..........0x.
0000050: 601e 000a 2020 2020 2020 0000 00fc 0053 `... .....S
0000060: 4f4e 5920 4350 442d 4534 3030 0000 00ff ONY CPD-E400....
0000070: 0038 3038 3031 3134 0a20 2020 2020 00d8 .8080114. ..
qsomi@qsomi-desktop:~/Desktop$

Okay, given that the edid issues are appearing on both the ati and sis graphics, I'm guessing this is not an -ati issue but perhaps the server. Refiling. Probably this should be forwarded upstream at this point. Thanks for the work gathering data on this issue.

Hi $name,

I've forwarded this bug upstream to <URL>. Could you please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time!

Oops, holy script mis-fire there batman!

qsomi - I've filed this upstream at https://bugs.freedesktop.org/show_bug.cgi?id=18066. Please subscribe to that bug; upstream may have additional questions. xserver bugs sometimes don't get reviewed very rapidly so we may need to be patient in order to see a fix become available.

Oh, and to follow up on your comment #50, yes if you could please attach your working xorg.conf and corresponding Xorg.0.log. Thanks!

qsomi,

Upstream would like to see the output of 'xrandr -prop', to see how the EDID is getting misinterpreted. Would you mind running that and attaching the output to the upstream bug at http://bugs.freedesktop.org/show_bug.cgi?id=18066 ?

Thanks ahead of time.

please provide the output of 'xrandr -prop' like was requested many months ago..

qsomi@qsomi-desktop:~$ xrandr --prop
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1680 x 1200
VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
 load_detection: 1 (0x00000001) range: (0,1)
   1280x1024@85 85.0*+
   1600x1200 75.0 70.0 65.0 60.0
   1680x1050 84.9 74.9 69.9 60.0
   1600x1024 60.2
   1400x1050 85.0 74.8 70.0 60.0
   1280x1024 85.0 75.0 59.9 60.0
   1440x900 59.9
   1280x960 85.0 60.0
   1360x768 59.8
   1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0
   1024x768 85.0 75.0 70.1 60.0
   832x624 74.6
   800x600 85.1 72.2 75.0 60.3 56.2
   640x480 85.0 72.8 75.0 59.9
   720x400 85.0
   640x400 85.1
   640x350 85.1
DVI-0 disconnected (normal left inverted right x axis y axis)
 dvi_monitor_type: auto
 scaler: off
 load_detection: 0 (0x00000000) range: (0,1)
S-video disconnected (normal left inverted right x axis y axis)
 tv_standard: ntsc
 tv_vertical_position: 0 (0x00000000) range: (-5,5)
 tv_horizontal_position: 0 (0x00000000) range: (-5,5)
 tv_horizontal_size: 0 (0x00000000) range: (-5,5)
 load_detection: 0 (0x00000000) range: (0,1)

I am currently using Ubuntu 9.04 with my modified xorg.conf

[This is an automatic notification.]

Hi qsomi,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 150709

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 150709 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/150709