[FireGL T2] xrandr reports only the highest resolution on Thinkpad T41p

[Martin Emrich]

Binary package hint: xserver-xorg-video-ati

On hardy, xrandr offered many resolutions from 320x200 up to the display's native resolution (1400x1050). Since the upgrade to intrepid, only the highest resolution is reported:

$ xrandr
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 1680 x 1050
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1400x1050 50.0*+
S-video disconnected (normal left inverted right x axis y axis)

I was able to add e.g. 1024x768 using --newmode and a modeline, but they are no longer autodetected.
VGA is a FireGL T2 (Thinkpad T41p).

[Bryce Harrington (bryce)]

Please attach your /var/log/Xorg.0.log and the output from `sudo ddcprobe > ddc.txt`. Also, please install the 'read-edid' package and attach the file generated by `sudo get-edid > edid.dat`.

[Martin Emrich (emme)]

Attached is my Xorg.0.log.

This is the output of get-edid. The resulting edid.dat is empty.

martin@gwaihir:~$ sudo get-edid 2>&1 > 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 MOBILITY RADEON 9600 "

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
Error: output block unchanged
----------------------------

This is the output of ddcprobe:
vbe: VESA 2.0 detected.
oem: ATI MOBILITY RADEON 9600
memory: 131008kb
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

[Bryce Harrington (bryce)]

Ah, if you're not able to get EDID out of the monitor, automatic configuration ain't gonna work.

Try setting Option "IgnoreEDID" "true" in your /etc/X11/xorg.conf.

It would be interesting if you could boot the hardy LiveCD and, assuming X comes up, snag the Xorg.0.log and xorg.conf from there. Oh, and the ddcprobe and get-edid file.

Btw, don't run `sudo get-edid 2>&1 > edid.dat` because that will put stdout into the dat file. We only want stdout, because it's binary data from the monitor.

[Martin Emrich (emme)]

IgnoreEDID did not work, still only 1400x1050 is reported.

Actually, 2>&1 did strangely not put stderr into the file, thus I cut&pasted the error message; get-edid will probably only send valid data to stdout, which was not possible here.

I just booted the hardy-i386-desktop Live-CD and collected all the information. get-edid didn't work here, too, but xrandr reported all the useful lower resolutions I miss on intrepid.

[Martin Emrich (emme)]

I'm at the university right now and connected an external 20" widescreen TFT (Dell 2005FPW) to the VGA port. On hardy, it reported all necessary resolutions, on intrepid this is all I get:

VGA-0 connected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768 59.8
   1152x864 60.0*
   1024x768 60.0
   800x600 60.3
   640x480 59.9

Attached is the output of get-edid for this display.

[Martin Emrich (emme)]

Hmm, the upper LP field does not upload the attachments, here's the EDID data.

[Bryce Harrington (bryce)]

$ parse-edid edid-external.dat
parse-edid: parse-edid version 1.4.1
parse-edid: EDID checksum passed.

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "DELL 2005FPW"
 VendorName "DEL"
 ModelName "DELL 2005FPW"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 HorizSync 30-83
 VertRefresh 56-75
 # Max dot clock (video bandwidth) 150 MHz
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:yes Suspend:yes Standby:yes

 Mode "1680x1050" # vfreq 59.954Hz, hfreq 65.290kHz
  DotClock 146.250000
  HTimings 1680 1784 1960 2240
  VTimings 1050 1053 1059 1089
  Flags "+HSync" "-VSync"
 EndMode
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
EndSection

[Bryce Harrington (bryce)]

Right, so it looks like there are two separate issues.

First, your home monitor does not report its EDID. I don't think there's anything that can be done that. Maybe try IgnoreDDC. There's already a bug open for the EDID fail issue - https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/194760

Second, the original issue you reported was with it reporting different sets of resolutions between hardy and intrepid. I've not seen that issue myself. Looking at the log I notice this:

(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 0
(II) RADEON(0): Detected non-DDC Monitor Type: 0
(II) RADEON(0): Detected non-DDC Monitor Type: 2
in RADEONProbeOutputModes
(II) RADEON(0): Added native panel mode: 1400x1050
(II) RADEON(0): Total number of valid Screen mode(s) added: 0

[Bryce Harrington (bryce)]

Oh also, could you give the name and model number of the monitor you're seeing the EDID fail on?

[Martin Emrich (emme)]

The EDID failing monitor is the built-in display of the laptop (14.1" LCD, 1400x1050@50).

I would assume that the internal display does not support EDID/DDC at all, but the native resolution is read from the BIOS. On hardy, the driver just adds some VESA modes, which is no longer done on intrepid.