DDC works wrong with Acer AL1916 monitors

[Mike A. Kuznetsov]

Sorry for my bad english
After some of XOrg starts/restarts (much more possibility if XOrg killed or crashed) DDC become working in wrong way and give only some of resolutions and works with 1152x864 (tested with two Intel Onboard cards and one ATI Radeon on three different machines)

stop X (e.g. /etc/init.d/gdm stop), power off monitor (by disabling power cable only!) and starting X agains solves the problem temporary

Tested four monitors Acer AL1916

Xorg.log of bad session attached

[Mike A. Kuznetsov (mike4gg)]

good session log for comparison

[Mike A. Kuznetsov (mike4gg)]

tested on ubuntu 8.10 and ubuntu 9.04

[Martin Olsson (mnemo)]

Can you please run:
apport-collect 375609
(this will attach more data about your hw / sw etc)

[Martin Olsson (mnemo)]

Can you also please run "sudo get-edid | parse-edid" and "xrander --verbose" both when it works and when it does not work?

[Martin Olsson (mnemo)]

I mean "xrandr" of course and also note that get-did ships in the read-edid package.

[Mike A. Kuznetsov (mike4gg)]

GOOD session:

$ sudo get-edid | parse-edid
parse-edid: parse-edid version 1.4.1
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 "Intel(r) 82945G Chipset Family Graphics Chip Accelerated VGA BIOS"

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

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 "Acer AL1916"
 VendorName "ACR"
 ModelName "Acer AL1916"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 HorizSync 30-83
 VertRefresh 55-75
 # Max dot clock (video bandwidth) 140 MHz
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:yes Suspend:no Standby:no

 Mode "1280x1024" # vfreq 60.020Hz, hfreq 63.981kHz
  DotClock 108.000000
  HTimings 1280 1328 1440 1688
  VTimings 1024 1025 1028 1066
  Flags "+HSync" "+VSync"
 EndMode
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
EndSection

$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1280 x 1280
VGA connected 1280x1024+0+0 (0x3c) normal (normal left inverted right x axis y axis) 376mm x 301mm
 Identifier: 0x3b
 Timestamp: 46714962
 Subpixel: unknown
 Clones:
 CRTC: 0
 CRTCs: 0 1
 Panning: 0x0+0+0
 Tracking: 0x0+0+0
 Border: 0/0/0/0
 Transform: 1.000000 0.000000 0.000000
             0.000000 1.000000 0.000000
             0.000000 0.000000 1.000000
            filter:
 EDID_DATA:
  00ffffffffffff00047249ad0f054080
  0412010368261e6b2a6760a25a499e23
  135054bfef00818f8180714f7140614f
  6140454f4540302a009851002a403070
  1300782d1100001e000000ff004c3439
  3038363831343244490a000000fd0037
  4b1e530e000a202020202020000000fc
  004163657220414c313931360a200076
  1280x1024 (0x3c) 108.0MHz +HSync +VSync *current +preferred
        h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
        v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
  1280x1024 (0x3d) 135.0MHz +HSync +VSync
        h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 80.0KHz
        v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz
  1280x1024 (0x3c) 108.0MHz +HSync +VSync *current
        h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
        v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
  1152x864 (0x3e) 108.0MHz +HSync +VSync
        h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
        v: height 864 start 865 end 868 total 900 ...

[Mike A. Kuznetsov (mike4gg)]

I run app
$ apport-collect 375609
logged in launchpad, choose "read anything", then app told me choose "change anything", i revoked authorization to begin again, and saw this:

$ apport-collect 375609
Logging into Launchpad...
Traceback (most recent call last):
  File "/usr/bin/apport-collect", line 131, in <module>
    lp = login()
  File "/usr/bin/apport-collect", line 48, in login
    launchpad = Launchpad(credentials, launchpad_instance, cache_dir)
  File "/usr/lib/python2.6/dist-packages/launchpadlib/launchpad.py", line 60, in __init__
    self._wadl = self._browser.get_wadl_application(self._root_uri)
  File "/usr/lib/python2.6/dist-packages/launchpadlib/_browser.py", line 230, in get_wadl_application
    url, media_type='application/vd.sun.wadl+xml')
  File "/usr/lib/python2.6/dist-packages/launchpadlib/_browser.py", line 212, in _request
    raise HTTPError(response, content)
launchpadlib.errors.HTTPError: HTTP Error 401: Unauthorized

[Mike A. Kuznetsov (mike4gg)]

I think bug is monitor related, i can't reproduce it by killing X now
I will report you `sudo get-edid | parse-edid` and `xrandr --verbose` from other machine (bad session on it), then report good session from there, if you want

[Mike A. Kuznetsov (mike4gg)]

`xrandr --verbose` from OTHER machine (BAD session):

$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360
VGA connected 1152x864+0+0 (0x3c) normal (normal left inverted right x axis y axis) 0mm x 0mm
 Identifier: 0x3a
 Timestamp: 30356
 Subpixel: unknown
 Clones:
 CRTC: 0
 CRTCs: 0
 Panning: 0x0+0+0
 Tracking: 0x0+0+0
 Border: 0/0/0/0
 Transform: 1.000000 0.000000 0.000000
             0.000000 1.000000 0.000000
             0.000000 0.000000 1.000000
            filter:
  1360x768 (0x3b) 84.8MHz -HSync +VSync
        h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.7KHz
        v: height 768 start 771 end 781 total 798 clock 59.8Hz
  1152x864 (0x3c) 81.6MHz -HSync +VSync *current
        h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz
        v: height 864 start 865 end 868 total 895 clock 60.0Hz
  1024x768 (0x3d) 65.0MHz -HSync -VSync
        h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
        v: height 768 start 771 end 777 total 806 clock 60.0Hz
  800x600 (0x3e) 40.0MHz +HSync +VSync
        h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
        v: height 600 start 601 end 605 total 628 clock 60.3Hz
  640x480 (0x3f) 25.2MHz -HSync -VSync
        h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
        v: height 480 start 490 end 492 total 525 clock 59.9Hz

I can't run `sudo get-edid | parse-edid` here because read-edid package is not avaible for amd64

[Mike A. Kuznetsov (mike4gg)]

What next?

[Geir Ove Myhr (gomyhr)]

Mike, you can get a amd64 version of read-edid from this PPA: https://launchpad.net/~intuitivenipple/+archive/ppa/ . This was supposed to go into Jaunty, but for some unknown reason it didn't (see bug 242043).

[Mike A. Kuznetsov (mike4gg)]

Thanx, but i don't know how to reproduce the bug

[Thomas Karmann (samoht)]

I have the exact same problem with an Intel 945GME (rev03) and an Acer monitor connected via vga-out.
The highest resolution xrandr shows me is 1152x864, tough the monitor is capable of 1280x1024.

Turning the monitor off and on and restarting X helps, but only until the next reboot (state after resume from suspend is fine).

I also downgraded the intel xorg driver to 2.4 but the issue remained, so I assume it's on the kernel side...

[d4rr3ll (darrell-taylor)]

Architecture: i386
DistroRelease: Ubuntu 9.04
LsHal:

Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Xrandr:

glxinfo:

setxkbmap:

xdpyinfo:

xkbcomp:

[d4rr3ll (darrell-taylor)]

I am having the same problem, as you can see I have successfully run apport-collect 375609 but this was run from a shell as that's the only way I can get into the box due to not being able to startx.

Does anyone have a suggested workaround for this, i.e. some way of bypassing the automatic detection and forcing the system to have the settings I tell it?

[d4rr3ll (darrell-taylor)]

after apt-get upgrade Xorg log is slightly different, in that I see the following line in the log :

(II) intel(0): EDID vendor "ACR", prod id 1916

Xlog.0.log attached

[d4rr3ll (darrell-taylor)]

ok, I seem to have a work around, simply add a modeline to the "Monitor" Section at least gets me up and running with X

this is the current snippet from my config

Section "Monitor"
        Identifier "Monitor0"
        ModelName "AL1916"
        VendorName "Acer"
        HorizSync 31.0 - 81.0
        VertRefresh 56.0 - 75.0
        Option "DPMS"
        modeline "1280x1024@60" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
EndSection

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[Bryce Harrington (bryce)]

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.

It seems likely to me this bug is gone; the -intel driver has improved immensely in Karmic and a lot of bugs are being reported as no longer present. So hopefully that's the case here too.

[Martin (martin-wetterstedt)]

I have the same problem, what info woul you like? This is probably the same bug as this: https://bugs.launchpad.net/ubuntu/+bug/221566