Bug 15596 (tpp)

Summary: intel driver does not appear to be creating modeline from EDID properly
Product: xorg Reporter: Tom Parnell <tom.parnell>
Component: Driver/intelAssignee: Hong Liu <hong.liu>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium Keywords: NEEDINFO
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log
none
my xorg.conf
none
xorg log + modedebug none

Description Tom Parnell 2008-04-18 15:11:05 UTC
Created attachment 16028 [details]
Xorg log

I just bought a new 24" monitor and a new PC with Ubuntu Gutsy pre-installed.
The processor is a Q6600 with the G33/31 graphics integrated. The lspci output is as follows:

00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)

When I plug in the monitor I was cannot use the maximum resolution 1920x200.
I see from the Xorg.0.log that 

(II) intel(0): Not using default mode "1920x1200" (vrefresh out of range)

It then probes for modes it can use and discovers:

(II) intel(0): Printing probed modes for output VGA-1
(II) intel(0): Modeline "1280x800"x60.0   83.46  1280 1344 1480 1680  800 801 804 828 (49.7 kHz)
(II) intel(0): Modeline "1280x768"x60.0   80.14  1280 1344 1480 1680  768 769 772 795 (47.7 kHz)
(II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)

None of which are 1920x1200! So my first thought is that the EDID information is broken but get-edid returns the following:

Section "Monitor"
        # Block type: 2:0 3:fc
        Identifier "MB24W"
        VendorName "NTS"
        ModelName "MB24W"
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:fd
        HorizSync 30-74
        VertRefresh 50-61
        # Max dot clock (video bandwidth) 160 MHz
        # Block type: 2:0 3:ff
        # DPMS capabilities: Active off:yes  Suspend:no  Standby:no

        Mode    "1920x1200"     # vfreq 59.950Hz, hfreq 74.038kHz
                DotClock        154.000000
                HTimings        1920 1968 2000 2080
                VTimings        1200 1203 1209 1235
                Flags   "-HSync" "+VSync"
        EndMode
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:ff
EndSection

Which looks perfectly correct! If I force this modeline with xrandr, then the display works beautifully. Unfortunately I cannot figure out:

a) how to force the intel driver to use a modeline - it always ends up probing for them
b) why the intel driver does not come up with the correct mode from the edid

I am using whichever version of the intel driver is included with Ubuntu Gutsy, so I am sorry if this bug has been addressed in later releases. I did try upgrading to the latest Hardy repositories and it still did not work.

Apologies if this has been addressed.

tpp
Comment 1 Julien Cristau 2008-04-19 06:01:42 UTC
On Fri, Apr 18, 2008 at 15:11:06 -0700, bugzilla-daemon@freedesktop.org wrote:

> When I plug in the monitor I was cannot use the maximum resolution 1920x200.
> I see from the Xorg.0.log that 
> 
> (II) intel(0): Not using default mode "1920x1200" (vrefresh out of range)
> 
Can you move your xorg.conf away and try again?

Cheers,
Julien
Comment 2 Tom Parnell 2008-04-19 06:40:05 UTC
I moved it away and restart X but X fails to start.

Cheers,

Tom

On Sat, Apr 19, 2008 at 2:01 PM, <bugzilla-daemon@freedesktop.org> wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=15596
>
>
>
>
>
> --- Comment #1 from Julien Cristau <jcristau@debian.org>  2008-04-19
> 06:01:42 PST ---
> On Fri, Apr 18, 2008 at 15:11:06 -0700, bugzilla-daemon@freedesktop.orgwrote:
>
> > When I plug in the monitor I was cannot use the maximum resolution
> 1920x200.
> > I see from the Xorg.0.log that
> >
> > (II) intel(0): Not using default mode "1920x1200" (vrefresh out of
> range)
> >
> Can you move your xorg.conf away and try again?
>
> Cheers,
> Julien
>
>
> --
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Julien Cristau 2008-04-19 09:37:35 UTC
> --- Comment #2 from Tom Parnell <tom.parnell@gmail.com>  2008-04-19 06:40:05 PST ---
> I moved it away and restart X but X fails to start.
> 
Sadness.  Can you attach your xorg.conf then?

Cheers,
Julien
Comment 4 Tom Parnell 2008-04-19 10:43:16 UTC
Created attachment 16046 [details]
my xorg.conf
Comment 5 Tom Parnell 2008-04-19 10:44:19 UTC
(In reply to comment #4)
> Created an attachment (id=16046) [details]
> my xorg.conf
> 

I've attached the xong.conf, note that when I enter modelines in the correct location, the intel driver ignores them and probes for modelines anyway.
Comment 6 Hong Liu 2008-04-20 19:33:30 UTC
What is your PC model? It seems that there are two VGA ports on your PC, one is from the internal VGA output and the other is from SDVO-VGA (VGA-1 in xorg log), would you please try to connect your monitor on the other VGA port and have a try?

For a temporary workaround, you need to add
1. Option "Monitor-VGA-1" "MB24W" to your device setcion
2.  then add the following lines to your monitor (MB24W) section
    HorizSync 30-74
    VertRefresh 50-61
    Option "maxclock" "160MHz"
    modeline 1920x1200_OK 154 1920 1968 2000 2080 1200 1203 1209 1235 -hsync +vsync
     Option "PreferredMode" "1920x1200_OK"


It seems that our driver fails to get the EDID data from your monitor on the SDVO-VGA output (i.e VGA-1 from xrandr), and then uses the default hsync & vert sync rate which filters out your 1920x1200 mode. 
So the real problem is why we failed to get the EDID data from your VGA-1 output, Would you please attach xorg log with option modedebug turned on?

Thanks,
Hong



Comment 7 Tom Parnell 2008-04-21 06:49:06 UTC
(In reply to comment #6)
> What is your PC model? It seems that there are two VGA ports on your PC, one is
> from the internal VGA output and the other is from SDVO-VGA (VGA-1 in xorg
> log), would you please try to connect your monitor on the other VGA port and
> have a try?
> 
> For a temporary workaround, you need to add
> 1. Option "Monitor-VGA-1" "MB24W" to your device setcion
> 2.  then add the following lines to your monitor (MB24W) section
>     HorizSync 30-74
>     VertRefresh 50-61
>     Option "maxclock" "160MHz"
>     modeline 1920x1200_OK 154 1920 1968 2000 2080 1200 1203 1209 1235 -hsync
> +vsync
>      Option "PreferredMode" "1920x1200_OK"
> 
> 
> It seems that our driver fails to get the EDID data from your monitor on the
> SDVO-VGA output (i.e VGA-1 from xrandr), and then uses the default hsync & vert
> sync rate which filters out your 1920x1200 mode. 
> So the real problem is why we failed to get the EDID data from your VGA-1
> output, Would you please attach xorg log with option modedebug turned on?
> 
> Thanks,
> Hong
> 

Hi Hong,

There is only one VGA port on my computer, it's hooked up to the motherboard. As as I understand it this SDVO port is a pass-through from the PCI, but I have no PCI cards installed so I cannot use it. The monitor is connected to the sole VGA port, which seems to be linked to VGA-1. 

I tried putting the above in my xorg.conf, but when I restarted X it just fell back to the VESA driver. I added the modedebug option and have attached it.

Cheers,

Tom

Comment 8 Tom Parnell 2008-04-21 06:49:35 UTC
Created attachment 16073 [details]
xorg log + modedebug
Comment 9 Hong Liu 2008-04-22 18:33:14 UTC
(In reply to comment #7)
> Hi Hong,
> 
> There is only one VGA port on my computer, it's hooked up to the motherboard.
> As as I understand it this SDVO port is a pass-through from the PCI, but I have
> no PCI cards installed so I cannot use it. The monitor is connected to the sole
> VGA port, which seems to be linked to VGA-1. 

There may be some motherboard has on-board sdvo controller, what is your PC model and what is the motherboard model?

BTW, would you please try a newer driver (2.1.1 may be too old)?

Thanks,
Hong
Comment 10 Michael Fu 2008-04-30 16:42:36 UTC
looking for bug reporter's response to comment# 9
Comment 11 Michael Fu 2008-06-05 01:57:13 UTC
reject this bug due to no response from bug reporter. please feel free to reopen if you have response to comment#9. thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.