Bug 30758 - [arrandale] [eDP] Blank screen with KMS on Sony Vaio VPCY2
Summary: [arrandale] [eDP] Blank screen with KMS on Sony Vaio VPCY2
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-10 13:20 UTC by William Roe
Modified: 2010-12-30 13:04 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Output from intel_reg_dumper tool (10.82 KB, text/plain)
2010-10-10 13:20 UTC, William Roe
no flags Details
Output from dumping the vbios (64.00 KB, application/octet-stream)
2010-10-10 13:22 UTC, William Roe
no flags Details
Output of intel_reg_dumper when booting with nomodeset i915.modeset=0 (10.78 KB, text/plain)
2010-10-10 13:26 UTC, William Roe
no flags Details

Description William Roe 2010-10-10 13:20:43 UTC
Created attachment 39329 [details]
Output from intel_reg_dumper tool

This kernel is built from drm-intel-next

The chipset is Intel HM55

Uname: Linux silver 2.6.36-rc5-ARCH-01304-g2d7b836 #1 SMP PREEMPT Fri Oct 8 23:33:35 BST 2010 x86_64 Intel(R) Pentium(R) CPU U5400 @ 1.20GHz GenuineIntel GNU/Linux

Arch Linux

I haven't attached any xf86-video-intel stuff because KMS isn't working.

The machine is a Sony Vaio VPCY21S1E
The native screen resolution is 1366x768 - but without modeset, with vesa, it'll only do 1024x768.
It has VGA and HDMI connections available. 

To reproduce you just boot with a recent Linux kernel (KMS capable).
Comment 1 William Roe 2010-10-10 13:22:13 UTC
Created attachment 39330 [details]
Output from dumping the vbios
Comment 2 William Roe 2010-10-10 13:26:37 UTC
Created attachment 39331 [details]
Output of intel_reg_dumper when booting with nomodeset i915.modeset=0
Comment 3 William Roe 2010-10-16 20:48:21 UTC
Can anyone help with this? Any more information I can provide?
Comment 4 Dongxu Li 2010-10-18 14:06:35 UTC
is this the similar to #29221 ?
Comment 5 Dongxu Li 2010-10-20 19:00:59 UTC
William,

maybe, you should try my workaround, which is essentially one line to reset backlight,

https://bugs.freedesktop.org/attachment.cgi?id=37406
Comment 6 William Roe 2010-11-07 15:04:24 UTC
Hi,

That file doesn't exist in the kernel tree I'm using (drm-intel-next). That code is in intel_opregion.c and is slightly different. So I'm not sure what to do there.

Is there any more debug info I can provide to sort this? I'm stuck in Windows at the moment and it looks like everyone with the same model is having the same problems according to the Ubuntu forums and so on.

Thanks,
Will

(In reply to comment #5)
> William,
> 
> maybe, you should try my workaround, which is essentially one line to reset
> backlight,
> 
> https://bugs.freedesktop.org/attachment.cgi?id=37406
Comment 7 William Roe 2010-11-07 15:27:38 UTC
I tried applying the opregion patch (adapting it to the source I have - and it didn't work - blank screen still.
Comment 8 H 2010-11-07 16:09:46 UTC
(In reply to comment #4)
> is this the similar to #29221 ?

This bug is not similar to #29221. The xrandr workaround does not work on this model. An external monitor however does work.
Comment 9 Dongxu Li 2010-11-10 09:57:30 UTC
xrandr is a workaround for #29221.

 if xrandr doesn't recover your monitor, then it's not the same.

Sorry for pointing to the wrong place.
Comment 10 Jorge Maroto 2010-11-12 03:56:37 UTC
Same problem here. Same machine.

Sony VAIO Y21S1E/SI

William, I guess if you tried with drm-intel-next it is because #29141. Did you try with the latest commits of that report?
Comment 11 William Roe 2010-11-12 15:03:33 UTC
I just tried pulling the latest from drm-intel-next and the same happens - blank screen, backlight on.


(In reply to comment #10)
> Same problem here. Same machine.
> 
> Sony VAIO Y21S1E/SI
> 
> William, I guess if you tried with drm-intel-next it is because #29141. Did you
> try with the latest commits of that report?
Comment 12 Marcel Heß 2010-11-19 05:18:24 UTC
Hello,

I have the same model and the same problems.

I read and tried a couple of things, which are referred in the bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=29141
https://bugs.freedesktop.org/show_bug.cgi?id=29221
https://bugs.freedesktop.org/show_bug.cgi?id=29278

With an external LCD on HDMI it works fine, but the internal Screen stays black.

Have anybody a new hint for me what to do, or missed I something?

Best regards
Comment 13 William Roe 2010-12-11 17:22:02 UTC
I have just tried the latest drm-intel-next kernel (which identifies itself as 2.6.37-rc5-ARCH-13051-g8d5203c   : ARCH obviously because this is an ArchLinux system) and it's working!
I booted and KMS worked - switched the mode properly as it should, no blank screen.

I now need to get X working. It starts in 1024x768 rather than the native resolution at the moment. I'm upgrading libdrm and xf86-video-intel to see if that fixes the problem. I suspect it's a configuration issue.
Comment 14 Jorge Maroto 2010-12-12 02:24:58 UTC
(In reply to comment #13)
> I have just tried the latest drm-intel-next kernel (which identifies itself as
> 2.6.37-rc5-ARCH-13051-g8d5203c   : ARCH obviously because this is an ArchLinux
> system) and it's working!
> I booted and KMS worked - switched the mode properly as it should, no blank
> screen.
> 
> I now need to get X working. It starts in 1024x768 rather than the native
> resolution at the moment. I'm upgrading libdrm and xf86-video-intel to see if
> that fixes the problem. I suspect it's a configuration issue.

I checked out the kernel repository but it is not clear to me what specific version as you tried. 

Could you tell me what tree and branch have you used? I would like to test it too.
Comment 15 William Roe 2010-12-12 02:53:44 UTC
Certainly, I am using the tree: git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel
Branch: drm-intel-next
Revision: 8d5203ca62539c6ab36a5bc2402c2de1de460e30
9th December was the last commit

Cheers,
Will

(In reply to comment #14)
> (In reply to comment #13)
> > I have just tried the latest drm-intel-next kernel (which identifies itself as
> > 2.6.37-rc5-ARCH-13051-g8d5203c   : ARCH obviously because this is an ArchLinux
> > system) and it's working!
> > I booted and KMS worked - switched the mode properly as it should, no blank
> > screen.
> > 
> > I now need to get X working. It starts in 1024x768 rather than the native
> > resolution at the moment. I'm upgrading libdrm and xf86-video-intel to see if
> > that fixes the problem. I suspect it's a configuration issue.
> 
> I checked out the kernel repository but it is not clear to me what specific
> version as you tried. 
> 
> Could you tell me what tree and branch have you used? I would like to test it
> too.
Comment 16 H 2010-12-19 17:14:53 UTC
(In reply to comment #13)
> I have just tried the latest drm-intel-next kernel (which identifies itself as
> 2.6.37-rc5-ARCH-13051-g8d5203c   : ARCH obviously because this is an ArchLinux
> system) and it's working!
> I booted and KMS worked - switched the mode properly as it should, no blank
> screen.
> 
> I now need to get X working. It starts in 1024x768 rather than the native
> resolution at the moment. I'm upgrading libdrm and xf86-video-intel to see if
> that fixes the problem. I suspect it's a configuration issue.

Did upgrading libdrm and xf86-video-intel fix the problem?
Comment 17 William Roe 2010-12-21 05:14:12 UTC
What fixed the problem was removing the Driver "vesa" line from my xorg.conf.d ... Then X used the intel driver and it's working fine now.

Only issue now is suspend. The display does not wake when the machine wakes from suspend.

(In reply to comment #16)
> (In reply to comment #13)
> > I have just tried the latest drm-intel-next kernel (which identifies itself as
> > 2.6.37-rc5-ARCH-13051-g8d5203c   : ARCH obviously because this is an ArchLinux
> > system) and it's working!
> > I booted and KMS worked - switched the mode properly as it should, no blank
> > screen.
> > 
> > I now need to get X working. It starts in 1024x768 rather than the native
> > resolution at the moment. I'm upgrading libdrm and xf86-video-intel to see if
> > that fixes the problem. I suspect it's a configuration issue.
> 
> Did upgrading libdrm and xf86-video-intel fix the problem?
Comment 18 Jorge Maroto 2010-12-22 10:56:10 UTC
The same kernel works like a charm for me too. 

After compile it and remove the vesa driver I got the native resolution.

Does anyone know if the changes are comming in the mainstream?

(In reply to comment #15)
> Certainly, I am using the tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel
> Branch: drm-intel-next
> Revision: 8d5203ca62539c6ab36a5bc2402c2de1de460e30
> 9th December was the last commit
> 
> Cheers,
> Will
>
Comment 19 tino.truppel 2010-12-30 11:32:07 UTC
git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel works for me great, as well.

After months of waiting I can use my internal monitor of my Sony Vaio VPCY21C5E with Intel HD Graphics. Thumbs up!

BTW: resume from stand by works as well.
Comment 20 Chris Wilson 2010-12-30 13:04:34 UTC
Ok, looks like the VPCY2 joins the small (but growing) list of working eDP chipsets.

Anyone following this bug but does not have a Sony Vaio VPCY2 please search for an open bug specific to your machine or open a new report (be sure to include the manufacturer/model in the summary). 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.