dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16389] New: New PM-Code produces white screen on laptop display on startup on an radeon x700
Date: Wed, 14 Jul 2010 17:57:09 GMT	[thread overview]
Message-ID: <bug-16389-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=16389

           Summary: New PM-Code produces white screen on laptop display on
                    startup on an radeon x700
           Product: Drivers
           Version: 2.5
    Kernel Version: 2.6.35-rc4
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: kontrollator@gmx.de
        Regression: Yes


After the merge of the new-pm code for radeon it get an all white screen on my
laptop display as soon as kms gets activated. Before the merge it worked as
long as i used radeon.dynpm=1 as boot parameter (without this parameter i also
get an all white screen with earlier kernels).

I can work around it with an vbetool dpms off / on cycle (which uses bios
routines i think), i tried all options / combinations of radeon.hw_i2c and
radeon.new_pll without success. I also get an all white laptop-screen as soon
as i change resolutions on my display, this also can be workaround with an
vbetool dpms off / on cycle. 

This also happens in the non-kms-case with the xorg-driver whenever i change
resolutions, in the old days i could workaround it with the MonitorLayout
"LVDS, none" option, however this option is long gone.

Chipset is an mobility radeon x700 pcie, pci-id is: 1002:5653

Please tell me what more information is needed.

Thank you

Jan Kreuzer

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--

             reply	other threads:[~2010-07-14 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 17:57 bugzilla-daemon [this message]
2010-07-14 18:14 ` [Bug 16389] New PM-Code produces white screen on laptop display on startup on an radeon x700 bugzilla-daemon
2010-07-15  5:04 ` bugzilla-daemon
2010-07-15  5:05 ` bugzilla-daemon
2010-07-20  8:33 ` bugzilla-daemon
2010-07-20 16:08 ` bugzilla-daemon
2010-07-21 21:36 ` bugzilla-daemon
2010-07-21 22:22 ` bugzilla-daemon
2010-07-23  7:42 ` bugzilla-daemon
2010-07-23 11:28 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-16389-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox