Bug 26927 - Blank LVDS Dell Studio 17
Summary: Blank LVDS Dell Studio 17
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-06 08:35 UTC by Damien Mir
Modified: 2010-03-11 19:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
requested vbios dump (62.00 KB, application/octet-stream)
2010-03-06 19:28 UTC, Damien Mir 		no flags Details
lspci output (16.85 KB, application/octet-stream)
2010-03-06 19:30 UTC, Damien Mir 		no flags Details
View All

Description Damien Mir 2010-03-06 08:35:25 UTC 
When using linux-next-20100305 with drm/radeon/kms, the LVDS panel of my laptop (Dell Studio 17) gets blank, and occasionally displays some brief artifacts when the KDM login screen supposed to pop up.

Maybe it needs some quirks (as Alex Daucher did for Dell Studio 15) ?
Comment 1 Alex Deucher 2010-03-06 09:26:48 UTC 
Does radeon.new_pll=0 fix it?
Comment 2 Damien Mir 2010-03-06 09:56:42 UTC 
(In reply to comment #1)
> Does radeon.new_pll=0 fix it?
> 

No it doesn't, same result.

Note that KMS with mainline 2.6.33 is OK. Seems to occur since recent merges in linux-next.
Comment 3 Alex Deucher 2010-03-06 15:08:11 UTC 
Can you attach the output of lspci -vnn and your video bios?  To dump your video bios do the following (as root):
cd /sys/bus/pci/devices/<pci bus id>
echo 1 > rom
cat rom > /tmp/vbios.rom
echo 0 > rom
Comment 4 Damien Mir 2010-03-06 19:28:48 UTC 
Created attachment 33822 [details]
requested vbios dump
Comment 5 Damien Mir 2010-03-06 19:30:02 UTC 
Created attachment 33823 [details]
lspci output
Comment 6 Damien Mir 2010-03-11 19:14:54 UTC 
Somehow I cannot reproduce with 2.6.34rc1, or even with next + glisse/drm-next.

I am closing the bug report.

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.