Bug 21127

Before this is resolved, you could use workaround it by explicitly Ignore LVDS like http://bugs.freedesktop.org/show_bug.cgi?id=16757#c2.

Thank you very much for the suggestion.

I have added my board to the lvds quirk list in intel-lvds.c and then I recompiled the Fedora rawhide kernel, hoping this could solve the problem.

-----
diff -uNrp kernel-2.6.29.orig/drivers/gpu/drm/i915/intel_lvds.c kernel-2.6.29.new/drivers/gpu/drm/i915/intel_lvds.c
--- kernel-2.6.29.orig/drivers/gpu/drm/i915/intel_lvds.c	2009-04-12 20:25:54.327203301 +0200
+++ kernel-2.6.29.new/drivers/gpu/drm/i915/intel_lvds.c	2009-04-13 00:25:06.549684527 +0200
@@ -424,6 +424,14 @@ static const struct dmi_system_id __init
 			DMI_MATCH(DMI_PRODUCT_NAME, "Studio Hybrid 140g"),
 		},
 	},
+	{
+		.callback = intel_no_lvds_dmi_callback,
+		.ident = "Abit iL-90MV",
+		.matches = {
+			DMI_MATCH(DMI_BOARD_VENDOR, "http://www.abit.com.tw/"),
+			DMI_MATCH(DMI_BOARD_NAME, "iL-90MV(Intel i945GT-ICH7m-DH)"),
+		},
+	},
 
 	/* FIXME: add a check for the Aopen Mini PC */
-----

After this change LVDS does not show up, but the DVI resolution is still 1024x768 :/

1280x1024 works under X if I add a custom modeline with xrandr:

$ xrandr --newmode 1280x1024 108 1280 1328 1440 1688 1024 1025 1028 1066 +HSync +VSync
$ xrandr --addmode DVI1 1280x1024
$ xrandr --output DVI1 --mode 1280x1024

but the Linux console still runs at 1024x768 and on startup the modes get changed which is not as pretty as it could be.

I have attached the dmesg output after boot with drm.debug=1.

1280x1024 does not get listed under the probed modes for DVI-D-1:

[drm:drm_mode_debug_printmodeline] Modeline 23:"0x0" 0 0 0 0 0 0 0 0 0 0 0x0 0x0
[drm:drm_mode_prune_invalid] Not using 0x0 mode 16
[drm:drm_helper_probe_single_connector_modes] Probed modes for DVI-D-1
[drm:drm_mode_debug_printmodeline] Modeline 22:"1024x768" 60003 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
[...]

Is the "invalid" modeline a pointer to the origin of the bug?

Created attachment 24768 [details]
dmesg with drm.debug=1 after ignore LVDS patch

Similar issue on a Thinkpad X200s, but at least the panel resolution is correct:


1!bernie@giskard:~/src/kernel$ xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
   1440x900       50.0* 
DVI1 connected (normal left inverted right x axis y axis)
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
DVI2 connected (normal left inverted right x axis y axis)
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  

I don't even have those DVI1 and DVI2 connectors :-)

This happens on a Fedora 11 system:

bernie@giskard:~/src/kernel$ rpm -q xorg-x11-drv-intel kernel
xorg-x11-drv-intel-2.7.0-6.fc11.x86_64
kernel-2.6.29.4-162.fc11.x86_64

Hi, Markus
    Will you please boot the system with kms disabled("nomodeset") and attach the output of Xorg.0.log?
   note: Please add the modedebug in the xorg.conf
   >Option "ModeDebug" "on"

    Will you please also attach the output of dmidecode, vbios dump?
    Thanks.

Created attachment 26678 [details]
Xorg.0.log-nomodeset

Created attachment 26679 [details]
xrandr-nomodeset

Created attachment 26680 [details]
Xorg.0.log-modeset

Created attachment 26681 [details]
xrandr-modeset

Created attachment 26682 [details]
dmidecode

Created attachment 26684 [details]
dmidecode-u

I'm running Fedora 11 Release now, but the problem is still there.
 * kernel: 2.6.29.4-167.fc11.i586
 * intel driver: 2.7.0-7.fc11

I've attached some files, but I'm not sure know how to dump the VBIOS.

Without KMS the DVI Resolution gets detected correctly, but resolution stays at 1024x768. Probably because the LVDS connector is wrongly detected as connected.

Will you please attach the output of acpidump?
     The latest acpidump tool(pmtools-20071116) can be found in
     http://www.lesswatts.org/projects/acpi/utilities.php
    Thanks.

Created attachment 26832 [details] [review]
check the LID device to decide whether LVDS device should be initialized

Will you please try the attached patch and see whether it can work well for you?
    Thanks.

(In reply to comment #12)
> I'm running Fedora 11 Release now, but the problem is still there.
>  * kernel: 2.6.29.4-167.fc11.i586
>  * intel driver: 2.7.0-7.fc11
> 
> I've attached some files, but I'm not sure know how to dump the VBIOS.
you can get the vbios dump by using the following commands:
   1. echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
   2. cat /sys/devices/pci0000:00/0000:00:02.0/rom > vbios.bin
   3. echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom
Thanks.
> 
> Without KMS the DVI Resolution gets detected correctly, but resolution stays at
> 1024x768. Probably because the LVDS connector is wrongly detected as connected.
> 

Created attachment 26866 [details]
acpidump

Created attachment 26867 [details]
vbios.bin

I've tested the patch with kernel 2.6.29.4-167.fc11. The LVDS connector does not show up anymore. Very good, but...

$ xrandr 
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA1 disconnected (normal left inverted right x axis y axis)
DVI1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 338mm x 271mm
   1024x768       60.0* 
   800x600        60.3  
   640x480        60.0  
   720x400        70.1  
TV1 unknown connection (normal left inverted right x axis y axis)
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9

...this mainboard has no TV connector either. :/

In dmesg appears (over and over):
[drm] TV-10: set mode NTSC 480i 0
[drm] TV-10: set mode NTSC 480i 0
[drm] TV-10: set mode NTSC 480i 0
[drm] TV-10: set mode NTSC 480i 0
[drm] TV-10: set mode NTSC 480i 0
[drm] TV-10: set mode NTSC 480i 0

And the resolution is still limited to a maximum of 1024x768 during boot and under X, too. The TFT's EDID gets detected correctly as shown in Xorg.log, but 1280x1024 does not show up. During boot and while starting X the display flickers as if something gets detected (I suppose)

Created attachment 26868 [details]
dmesg-after-patch

Created attachment 26869 [details]
Xorg.0.log after patch

(In reply to comment #18)
> I've tested the patch with kernel 2.6.29.4-167.fc11. The LVDS connector does
> not show up anymore. Very good, but...
> 
> $ xrandr 
> Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
> VGA1 disconnected (normal left inverted right x axis y axis)
> DVI1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 338mm x
> 271mm
>    1024x768       60.0* 
>    800x600        60.3  
>    640x480        60.0  
>    720x400        70.1  
> TV1 unknown connection (normal left inverted right x axis y axis)
>    1024x768       60.0  
>    800x600        60.3  
>    640x480        59.9
> 
> ...this mainboard has no TV connector either. :/
Thanks for the test. Now the issue of LVDS detection is fixed.
But another issue about TV detection is remained. 

will you please check whether the TV is detected correctly in UMS mode?

Please also try the latest Eric's drm-intel-next git tree and see whether this issue still exists?

Thanks.

> 
> In dmesg appears (over and over):
> [drm] TV-10: set mode NTSC 480i 0
> [drm] TV-10: set mode NTSC 480i 0
> [drm] TV-10: set mode NTSC 480i 0
> [drm] TV-10: set mode NTSC 480i 0
> [drm] TV-10: set mode NTSC 480i 0
> [drm] TV-10: set mode NTSC 480i 0
> 
> And the resolution is still limited to a maximum of 1024x768 during boot and
> under X, too. The TFT's EDID gets detected correctly as shown in Xorg.log, but
> 1280x1024 does not show up. During boot and while starting X the display
> flickers as if something gets detected (I suppose)
> 

Comment on attachment 26832 [details] [review]
check the LID device to decide whether LVDS device should be initialized

queued:

commit e99da35f060f9a3407f7def474a1df31f3b8643a
Author: Zhao Yakui <yakui.zhao@intel.com>
Date:   Fri Jun 26 09:46:18 2009 +0800

    drm/i915: Check the LID device to decide whether the LVDS should be initialized

looks this bug should marked as fixed then.