Created attachment 22872 [details]
Xorg.0.log with problem

pls refer to http://intellinuxgraphics.org/how_to_report_bug.html to see how to report a bug...

especially, turns modedebug on and submit the log..

So this machine is not a laptop, so doesn't have a local flat panel connected, right?

Ok I have attached some more info.  This is a not a laptop, but I think it is using a mobile chipset.  There is an LVDS connector, but it's not connected to anything and I have disabled it in BIOS.

gentoo ~ # uname -a
Linux gentoo 2.6.29-rc5-zen1 #1 SMP PREEMPT Sat Feb 14 12:30:57 EST 2009 x86_64 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux

Created attachment 22948 [details]
xorg.conf with debug turned on

Created attachment 22949 [details]
xrandr output

Created attachment 22950 [details]
dmesg

Created attachment 22951 [details]
Xorg.0.log with debug turned on

Does your system has 'lid' directory under /proc/acpi/button/? if yes, what about its status? Looks we need a quirk for your system, please attach lspci -vn.

I do not have /proc/acpi/button/lid/, only /proc/acpi/button/power/PWRB and /proc/acpi/button/power/PWRF: 

gentoo / # cat /proc/acpi/button/power/PWRB/info
type:                    Power Button (CM)
gentoo / # cat /proc/acpi/button/power/PWRF/info
type:                    Power Button (FF)

Created attachment 23003 [details]
lspci -vn

oh, subdevice id is same as device id...Could you attach dmidecode output too?

Created attachment 23037 [details]
dmidecode

Created attachment 23053 [details] [review]
Jetway J9F2 LVDS quirk

It looks there's no specific product info within dmi? Do you know any method can be used to identify this board? Otherwise we might just use this quirk patch or try another way to parse VBT.

Could you attach your vbios dump? Do like

cd /sys/devices/pci0000:00/0000:00:02.0/
echo 1 > rom
cat rom > /tmp/vbios

Then attach vbios file.

Created attachment 23059 [details]
vbios

Created attachment 23065 [details] [review]
Use LVDS config from vbios

Here's the patch against git master, that trys to use driver feature block data from vbios for LVDS info. That should eliminate the need for your quirk.

Thanks, your patch fixes the problem.  Will this be included in the main git tree?

I hope I can get more test to show this patch should work at least in most case, and reviews from intel-gfx list is also what I'd like to see. Keep open until I push the patch.

Pushed the patch. Close.

commit f6d8ae69b0f97e696c142f06c8038f336ed024f9
Author: Zhenyu Wang <zhenyu.z.wang@intel.com>
Date:   Wed Feb 25 09:57:00 2009 +0800

    Use LVDS config in Driver feature BDB for integrated LVDS check
    
    The LVDS config bits in VBT driver feature block is used by vendor
    to identify the board implement of integrated LVDS/eDP or SDVO LVDS.
    And video bios uses these bits for LVDS enabling or not. So check
    these bits for integrated LVDS might eliminate more quirks.

Your pushed patch has been working, but after switching to KMS, I now have the same problem.  I can again work around it by adding a LVDS1 "ignore" line to my xorg.conf.  I suppose your same fix just needs to be applied somewhere else in the kernel code?  Do you need any additional information?

I've sent patch for KMS to intel-gfx list, and Eric Anholt has my patch integrated to drm-intel-next tree, which might haven't hit linus's tree yet. And I have a little updated patch for checking this block only for 9XX chips, which has also been sent to intel-gfx. You can try anholt's drm-intel-next tree from http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=summary, or wait for my patch to hit linus's.