Xorg start with incorrect frequency for LKM monitor

Bug #29291 reported by Alejandro Zaro
6
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Dapper by jtl999
Nominated for Feisty by jtl999
Nominated for Gutsy by jtl999

Bug Description

I have a "Likom/Aqua/Multiscan" L4011ND monitor.
 This 14" monitor is working with 1024x768 only at 60Hz.

In log file of DDC/EDID this is detected correctly.

But after detection it put name "Generic Monitor" and select as default 1024x768@75 mode.
************
Here some parts of /var/log/Xorg.0.log
************
X Window System Version 6.99.99.904 (7.0.0 RC 4)
Release Date: 14 December 2005
X Protocol Version 11, Revision 0, Release 6.99.99.904
Build Operating System:Linux 2.6.10 i686
Current Operating System: Linux ubuntu 2.6.15-12-386 #1 PREEMPT Fri Jan 13 05:22:30 UTC 2006 i686
Build Date: 15 December 2005
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/lib/xorg/modules/libddc.so
(II) VIA(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
(II) VIA(0): I2C device "I2C bus 1:ddc2" removed.
(II) VIA(0): Manufacturer: LKM Model: 162 Serial#: 40940
(II) VIA(0): Year: 1998 Week: 29
(II) VIA(0): EDID Version: 1.1
(II) VIA(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) VIA(0): Sync: Separate Composite
(II) VIA(0): Max H-Image Size [cm]: horiz.: 27 vert.: 20
(II) VIA(0): Gamma: 2.50
(II) VIA(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) VIA(0): redX: 0.610 redY: 0.350 greenX: 0.307 greenY: 0.595
(II) VIA(0): blueX: 0.150 blueY: 0.065 whiteX: 0.281 whiteY: 0.311
(II) VIA(0): Supported VESA Video Modes:
(II) VIA(0): 640x480@60Hz
(II) VIA(0): 640x480@75Hz
(II) VIA(0): 800x600@56Hz
(II) VIA(0): 800x600@60Hz
(II) VIA(0): 800x600@72Hz
(II) VIA(0): 1024x768@87Hz (interlaced)
(II) VIA(0): 1024x768@60Hz
(II) VIA(0): Manufacturer's mask: 0
(II) VIA(0): Supported additional Video Mode:
(II) VIA(0): clock: 25.2 MHz Image Size: 260 x 195 mm
(II) VIA(0): h_active: 640 h_sync: 656 h_sync_end 751 h_blank_end 800 h_border: 0
(II) VIA(0): v_active: 350 v_sync: 388 v_sync_end 390 v_blanking: 448 v_border: 0
(II) VIA(0): Supported additional Video Mode:
(II) VIA(0): clock: 25.2 MHz Image Size: 260 x 195 mm
(II) VIA(0): h_active: 640 h_sync: 656 h_sync_end 751 h_blank_end 800 h_border: 0
(II) VIA(0): v_active: 400 v_sync: 413 v_sync_end 415 v_blanking: 448 v_border: 0
(II) VIA(0): Ranges: V min: 47 V max: 104 Hz, H min: 30 H max: 65 kHz, PixClock max 110 MHz
(II) VIA(0): AZALEA V1.00
(WW) VIA(0): This device is supposed to have a TV encoder but we are unable to detect it (support missing?).
(II) VIA(0): Generic Monitor: Using default hsync range of 30.00-65.00 kHz
(II) VIA(0): Generic Monitor: Using default vrefresh range of 47.00-104.00 Hz
(II) VIA(0): Clock range: 20.00 to 230.00 MHz
(II) VIA(0): Not using default mode "1024x768" (interlace mode not supported)
(II) VIA(0): Not using default mode "1024x768" (hsync out of range)
(II) VIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(--) VIA(0): Virtual size is 1024x768 (pitch 1024)
(**) VIA(0): *Default mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
(II) VIA(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
(**) VIA(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
(II) VIA(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
(**) VIA(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
(II) VIA(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
(--) VIA(0): DPI set to (96, 97)
(--) Depth 24 pixmap format is 32 bpp
************

Revision history for this message
Alejandro Zaro (grapequade) wrote : Xorg log file

Full Xorg log file

Revision history for this message
Alejandro Zaro (grapequade) wrote : xorg.conf file

default xorg.conf file from Ubuntu Dapper Flyer 3 LiveCD.

This problem has also Ubuntu 5.04 and 5.10

Revision history for this message
Alejandro Zaro (grapequade) wrote :

This monitor has a common motherboard with other LKM 15" monitor that may work at other more high frequency. I think these 15" LKM monitors must have other ID's.

Revision history for this message
Jerome S. Gotangco (jsgotangco) wrote :

hmmm this looks like a very peculiar hardware we have here. Does anyone who have this particular make/model confirm if it still exists in recent Flight 6 release (crosses fingers).

Changed in xorg:
status: Unconfirmed → Needs Info
Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

no info from the submitter. It looks like the monitor returns to usable ddc information to the driver.

Changed in xorg:
status: Needs Info → Rejected
Revision history for this message
Alejandro Zaro (grapequade) wrote :

I have tested with recent Flight 7 release.
It still use other frequency (78 Hz or 75 Hz).

 In Control Center I can select 75, 70 and 60 Hz. With 60 Hz is work good.
Also I try to detect the monitor in Control Center (displayconfig) I get "Plug'n'Play Monitor".

 May be Xorg also trying select interlace mode frequency at 75 Hz that is first in list of modes, but this card/chip has not supported interlace mode (from messages in log file Xorg.0.log).

Revision history for this message
Alejandro Zaro (grapequade) wrote : Flight-7 Full log

Flight-7 Full log

Revision history for this message
Alejandro Zaro (grapequade) wrote : Flight-7 Xorg.conf

Flight-7 Xorg.conf

Revision history for this message
Alejandro Zaro (grapequade) wrote :

This bug I have posted in Xorg bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=6904

Revision history for this message
Alejandro Zaro (grapequade) wrote :

In Ubuntu 6.10 don't work correctly.

Revision history for this message
Alejandro Zaro (grapequade) wrote :

Workarounds:
 In Ubuntu 6.10 you can go to console [Ctrl+Alt+F2], and add this line in to xorg.conf:
sudo nano -w /etc/X11/xorg.conf

In section Monitor you need to add line:
   VertRefresh 43-60

 The second testing CD of 7.04 Feisty Fawn starts with vesa driver. Vesa driver detects correctly monitor frequency (60Hz).

If you want to start you go to the console and edit the configuration file: sudo nano -w /etc/X11/xorg.conf

In section Monitor you need to add Line:
   VertRefresh 43-60

And in section Device change from vesa to via:
  Driver "via"

Now restart xorg [Ctrl+Alt+BackSpace].

+++

 Then via xorg driver will select only correct frequency (only non-interlaced if video chip doesn't support interlaced mode) this bugs will be fixed.

Revision history for this message
Alejandro Zaro (grapequade) wrote :

VIA driver in Ubuntu 8.04 Hardy Heron automatically selects 1024x768@60Hz monitor mode and all things are working fine during installation and after installation.
Thanks to all.

This bug is can be closed.

Revision history for this message
Alejandro Zaro (grapequade) wrote :

This bug resolved in Ubuntu 8.04 Hardy Heron

Changed in xorg:
status: Invalid → Fix Released
Revision history for this message
Icarosaurus (giuschet) wrote :

Fglrx driver doesn't automatically selects the correct refresh for this monitor.
I can use it only deleting xorg.conf and let it use the vesa driver.
It seems that the bug cannot be closed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.