From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82431] Garbled screen on boot
Date: Fri, 15 Aug 2014 05:18:41 +0000 [thread overview]
Message-ID: <bug-82431-2300-as4x34sqRy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82431-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82431
--- Comment #3 from Fede <fedevx@yahoo.com> ---
Hi Alex,
In deed, adding radeon.dpm=1 works. I tested it after submitting the bug report
since I went thru what the actual patch changed. Currently running kernel
3.16.0-5 and it works as long as radeon.dpm=1 is passed to the kernel.
GRUB_GFXPAYLOAD_LINUX=keep (nor text) did make any difference.
Can this be permanently fixed for everyone affected?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-15 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 4:34 [Bug 82431] New: Garbled screen on boot bugzilla-daemon
2014-08-15 4:38 ` [Bug 82431] " bugzilla-daemon
2014-08-15 4:46 ` bugzilla-daemon
2014-08-15 5:18 ` bugzilla-daemon [this message]
2014-08-15 5:24 ` bugzilla-daemon
2014-08-15 6:43 ` bugzilla-daemon
2014-08-15 7:05 ` bugzilla-daemon
2017-09-19 0:59 ` 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-82431-2300-as4x34sqRy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.