[needs quirk] Hansol H750 giving wrong EDID refresh rate

[Damiano Dallatana]

This particular bug I am reporting is killing me from a few years ago, with every Linux distribution (so, from the removal of xorg.conf). Now that I have two computers, I can say I did find out the problem.

My monitor is a 17" Hansol H750 LCD, and I cannot use any Linux distribution without having my monitor say "out of range".

I did find out the monitor is reporting a wrong maximum frequency: vfreq 333.176Hz, hfreq 355.166kHz - whilst its maximum is a 70-75 Hz.
I am going to attach the output of get-edid (parsed), ddcprobe, and the xorg.conf that solved everything.

I am at your complete disposal to solve this particular bug.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: None
Date: Sun Aug 28 11:47:18 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
GraphicsCard:
 ATI Technologies Inc Radeon RV250 If [Radeon 9000] [1002:4966] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:4010]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Unknown 00000000000000000000000
ProcEnviron:
 LANGUAGE=it_IT:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=90fabb29-9c6f-466d-b936-35909eac80f2 ro quiet splash nomodeset vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2002
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0H
dmi.board.name: SiS651
dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0H:bd10/26/2002:svnUnknown:pn00000000000000000000000:pvrLG00000106:rvnNECCOMPUTERSINTERNATIONAL:rnSiS651:rvr1.0:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr!l977:
dmi.product.name: 00000000000000000000000
dmi.product.version: LG00000106
dmi.sys.vendor: Unknown
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[Tormod Volden (tormodvolden)]

Thanks for your (new) report. The old one seems to have been forgotten and died. The issue here is clear: The monitor is reporting bad data in the EDID. From the xrandr output you posted in the other report:
 1280x1024 (0x3d) 599.5MHz +HSync +VSync *current
which is also seen in your ddcprobe output:
 dtiming: 1280x1024@392

I believe there is no bug in the drivers, but a quirk (hardware-specific workaround) should be added for your type of monitor.

[Damiano Dallatana (damidalla)]

Yes, exactly, it's not a bug on the driver; I think fglrx does it well just ignoring the wrong EDID data and forcing the refresh rate he thinks can work.
I marked the old report as a duplicate of this: I did have only this computer and no secondary pc nor monitor to test this bug, so I had to wait for months before filing a complete report... sorry for that, at least now we have a complete view of the problem :) thanks Tormod :)

[Bryce Harrington (bryce)]

Hey damidalla,

You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.

If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)

If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Tormod Volden (tormodvolden)]

I think the poor chaps at Hansol have encoded the detailed mode clock frequency as big-endian instead of little-endian. Swapping bytes 36 and 37 would give a frequency of 125.22 MHz (1280x1024@70) instead of 599.22 Mhz. I have studied a couple of other Hansol EDID dumps but I could not find any other model having this error.

I therefore made a proposal for a quirk for your model. Can you please test this kernel?
 http://alioth.debian.org/~tormod-guest/linux-image-3.2.0-3-generic_3.2.0-3.7tv_i386.deb

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original bug reporter. However, if the issue still exists in the latest development version of Ubuntu and you are the original reporter please feel free to reopen with the requested information. If you are not the original reporter, please don't reopen this one but instead file a new bug and reference this one.