Bug 29567

Summary: [Huron River] System boots up and X is running but nothing is displayed on LVDS
Product: DRI Reporter: Manjeet Singh <manjeet>
Component: DRM/IntelAssignee: Wang Zhenyu <zhenyu.z.wang>
Status: CLOSED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: blocker    
Priority: medium CC: yingying.zhao
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
output of drm.debug=0xe attached
none
Xorg.0.log output on HuronRiver
none
dmesg output on Huron River with disabling LVDS and drm.debug=6 none

Description Manjeet Singh 2010-08-13 12:14:59 UTC 
CRB Board Details:
PBA E73564-002
BIOS date 07/08/2010 (core version 4.6.3.2)
1GFX VBIOS version 2044

With libdrm 2.4.21 and xorg-x11-drv-intel-1.12.0 system boots up Huron River CRB and X is running but nothing is displayed on the screen 

HP’s problem is that on Huron River they don’t see anything on the screen.  The data HP has is the following:
•Updated to 2.6.35-rc6 and needed to add 3 patches in order to get suspend/resume to function problem on HP Cartier platform (calpella based)
•http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=4a655f043160eeae447efd3be297b6b4c397a640
•http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=9934c132989d5c488d2e15188220ce240960ce96
•http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=5620ae29f1eabe655f44335231b580a78c8364ea
•Using vesa driver on Huron River CRB – need to do chvt 1 followed by chvt 2 after suspend/resume to get video back
•With libdrm 2.4.21 and xorg-x11-drv-intel-1.12.0 system boots up Huron River CRB and X is running but nothing is displayed on the screen (monitor doesn’t see a signal)
•Detailed EDID data is showing up under VGA1 but not LVDS1 – is this expected?
Comment 1 Chris Wilson 2010-08-13 13:05:04 UTC 
No, we expect to get an EDID for the integrated panel as well, so something is clearly amiss and that alone is sufficient for X not to apply any modes to the LVDS.

Can you please add drm.debug=0xe to your boot commandline and upload the dmesg obtained? Thanks.
Comment 2 Manjeet Singh 2010-08-13 14:49:27 UTC 
Created attachment 37853 [details]
output of drm.debug=0xe attached

We have another Huron River CRB and that odd device ID. See blow
Massachusetts CRB board info:
                PBA E73564-202
                BIOS date 05/05/2010 (core version 4.6.3.2)
                IGFX VBIOS version 2024

We get past this bug by issuing the following commands
                Xrandr -output LVDS1 -off
                Xrandr -output VGA1 -preferred
Comment 3 Wang Zhenyu 2010-08-15 21:38:46 UTC 
LVDS port exists on your CRB, but no panel is there, which will cause problem we've seen on many CRB before. 

So either attach a panel to LVDS port or disable LVDS for testing, like video=LVDS-1:d
Comment 4 Yingying 2010-08-15 22:54:51 UTC 
It seems like disabling LVDS doesn't resolve my black screen issue on HuronRiver. I will attach the dmesg and Xorg.0.log output with adding "drm.debug=6" and "video=LVDS-1:d".
Comment 5 Yingying 2010-08-15 23:02:54 UTC 
Created attachment 37893 [details]
Xorg.0.log output on HuronRiver
Comment 6 Yingying 2010-08-15 23:03:49 UTC 
Created attachment 37894 [details]
dmesg output on Huron River with disabling LVDS and drm.debug=6
Comment 7 Manjeet Singh 2010-08-17 13:03:55 UTC 
See the comment#4 from yingying.zhao@intel.com. 
disabling LVDS doesn't resolve the blank screen issue.

Reopening the bug again.
Comment 8 Yingying 2010-09-01 01:37:59 UTC 
My issue is resolved after upgrading xserver-xorg-video-intel driver to latest. 

The workable configuration is:
- Maverick (kernel 2.6.35-19-generic);
- Latest Intel 2D driver (git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel);
- Huron River Beta SDP;

Thanks,
Yingying
Comment 9 Manjeet Singh 2010-09-01 17:17:47 UTC 
disabling LVDS worked for us.

Thanks,
Manjeet

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.