Bug 22478

Summary: [945GME] X server fails to initialize display on MSI Wind laptop
Product: xorg Reporter: Matthew McLean <matthew>
Component: Driver/intelAssignee: MaLing <ling.ma>
Status: RESOLVED WORKSFORME QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: high CC: jbarnes, matthew
Version: gitKeywords: NEEDINFO
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log file
none
xorg configuration file
none
xorg log file (when booting with i915.modeset=0)
none
xorg log file (when booting with i915.modeset=0)
none
pleaset try the patch on your machine, thanks.
none
xorg log file UMS (PATCHED) none

Description Matthew McLean 2009-06-25 10:45:33 UTC
Nothing is displayed on the screen when starting the X server.

System environment:
-- machine description: MSI Wind 10" mini laptop
-- chipset: Mobile 945GME Express Integrated Graphics Controller rev 3
-- architecture: i686
-- xf86-video-intel: source from GIT (built on 06/24/09)
-- xorg-server: X.Org X Server 1.6.1.901 (1.6.2 RC 1)
-- mesa: source from GIT (built on 06/24/09)
-- libdrm: source from GIT (built on 06/24/09)
-- kernel version: source from GIT (drm-intel, built on 06/24/09) "2.6.30"
-- display connector: LVDS1, mode 1024x600@60Hz is attempted
-- 100% reproducible
-- relevant kernel options: CONFIG_DRM=m CONFIG_DRM=I915=m CONFIG_I915_KMS=y 
-- kernel log output: "integrated sync not supported"
Comment 1 Matthew McLean 2009-06-25 10:46:01 UTC
Created attachment 27137 [details]
xorg log file
Comment 2 Matthew McLean 2009-06-25 10:46:19 UTC
Created attachment 27138 [details]
xorg configuration file
Comment 3 MaLing 2009-06-25 19:59:14 UTC
(In reply to comment #2)
> Created an attachment (id=27138) [details]
> xorg configuration file

Could you please try it in UMS mode via i915.modeset=0, then upload logfile with modedebug option on.

thanks
Ma Ling
Comment 4 Matthew McLean 2009-06-26 14:16:35 UTC
Created attachment 27182 [details]
xorg log file (when booting with i915.modeset=0)
Comment 5 Matthew McLean 2009-06-26 14:29:18 UTC
Created attachment 27183 [details]
xorg log file (when booting with i915.modeset=0)
Comment 6 MaLing 2009-06-28 06:06:35 UTC
Hi Matthew  
from log file, I found the lvds timing after X starts is almost the same with that of vbios setting -1024x600. My question is in UMS before X start every thing works fine, and after X start get back? If yes could you please try below timing by xrandr ? 

Modeline "1024x600_vbios" 41.42  1024 1072 1184 1200 600 601 604 625

Thanks for your help.
Ma Ling
Comment 7 Matthew McLean 2009-06-28 14:52:48 UTC
Ma Ling,

I tried what you asked for, but the screen remains blank.  Yes, you are correct the console works fine with both KMS and UMS, only when I start X the problem occurs.

I did the following:

$ xrandr --newmode "1024x600_vbios" 41.42 1024 1072 1184 1200 600 601 604 625
$ xrandr --addmode LVDS "1024x600_vbios"
$ xrandr --output LVDS --mode "1024x600_vbios"
$ xrandr 
Screen 0: minimum 320 x 200, current 1024 x 600, maximum 2048 x 2048
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x600+0+0 (normal left inverted right x axis y axis) 220mm x 129mm
   1024x600       60.0 +   65.0  
   800x600        60.3  
   640x480        59.9  
   1024x600_vbios   55.2*

The screen remains blank.

Any ideas?

Matthew.
Comment 8 MaLing 2009-06-28 18:37:01 UTC
Created attachment 27207 [details]
pleaset try the patch on your machine, thanks.

Matthew, please try the debug patch, then upload log file with modedebug option on.
BTW could you ever found X worked fine with last version of driver ? If yes, could you pleaes also upload that log file too?

Thanks for your help.
Ma Ling
Comment 9 MaLing 2009-06-29 18:10:16 UTC
ping~
Comment 10 Matthew McLean 2009-06-30 12:25:00 UTC
Created attachment 27270 [details]
xorg log file UMS (PATCHED)

Ma Ling,
I patched the driver and attached the log.
Comment 11 Michael Fu 2009-06-30 17:34:24 UTC
just FYI, ling. the message of 

 DEBUG_1 fixed mode line
(II) intel(0): Modeline "2136x17"x0.0   10.24  2136 2392 2395 2396  17 17 17 23 (4.3 kHz)

is a bug# 22529 which was just fixed by Jesse.
Comment 12 MaLing 2009-06-30 20:24:16 UTC
hi Matthew
What's  your laptop Model No, our machine is MSI Wind U100.
Because our MSI WIND netbook U100 works fine in version 2.7, could you kindly please download 2.7 version from http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.7.1.tar.bz2, then upload log file and output from command $lspci.

Thanks for your help.
Ma Ling


Comment 13 Matthew McLean 2009-07-01 11:30:24 UTC
Ma Ling,

It is a U100 also.  I know that some combination of drm/xorg/driver has worked before (for example: stock OpenSuSE install).  My current system is Gentoo/unstable and 2.7.1 release is failing too.  I even tried 2.6.x and still failed.  Could something else be the culprit?
Comment 14 MaLing 2009-07-01 19:14:50 UTC
Matthew, we have tested msi wind 100 and 100 plus successfully under following enviroment, could you please verify it again?

Thanks a lot
Ma Ling

Libdrm:    (master)de1ed01214874dcdd6116ff2587c8710d6ed4d2d

Mesa:      (master)5e6b593d35156a0068dc0eb3e55dec086f1cadd3

Xserver:   (master)3525d140567e0ad5f0184e4b37893c47239e1628

Xf86_video_intel: (master)1e4784bf26e3c154f5673f7b5add3ef7af3b1474

Kernel:    (drm-intel-next)b5aa8a0fc132dd512c33e7c2621d075e3b77a65e

 
Comment 15 MaLing 2009-07-05 18:05:18 UTC
(In reply to comment #14)
> Matthew, we have tested msi wind 100 and 100 plus successfully under following
> enviroment, could you please verify it again?
> Thanks a lot
> Ma Ling
> Libdrm:    (master)de1ed01214874dcdd6116ff2587c8710d6ed4d2d
> Mesa:      (master)5e6b593d35156a0068dc0eb3e55dec086f1cadd3
> Xserver:   (master)3525d140567e0ad5f0184e4b37893c47239e1628
> Xf86_video_intel: (master)1e4784bf26e3c154f5673f7b5add3ef7af3b1474
> Kernel:    (drm-intel-next)b5aa8a0fc132dd512c33e7c2621d075e3b77a65e

Matthew,
I will close the issue, please open it if you need.
Thanks
Ma Ling

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.