From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111182] Fade-to-white after KMS is set on RV635
Date: Mon, 22 Jul 2019 09:38:01 +0000 [thread overview]
Message-ID: <bug-111182-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2061 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111182
Bug ID: 111182
Summary: Fade-to-white after KMS is set on RV635
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: thumperward@hotmail.com
Created attachment 144837
--> https://bugs.freedesktop.org/attachment.cgi?id=144837&action=edit
dmesg output after blacklisting radeon, then enabling it after boot
I have a laptop with a Radeon Mobility 3670. With KMS disabled I can boot
normally; however, otherwise it typically locks hard as soon as modesetting
happens, with an odd effect where the screen gradually fades to being nearly
completely white. (I can provide video if for some reason this would help).
However, on occasion (rarely) it will flicker for a second, successfully switch
modes, spit out "Timeout setting UVD clocks", and then carry on correctly.
Given that this happens very early in the boot, and hard locks the system, I've
taken to blacklisting radeon in my boot parameters, then doing a "sudo modprobe
radeon" after logging in and crossing my fingers. Attached is dmesg output from
such a case - note the delay between lines 918 and 919 as boot finished, I
logged in, and then ran modprobe. Lines 950-955 show the errors that get echoed
as the system then successfully switches modes.
(blacklisting until after boot isn't the only way to get it working - it just
happens to give me more of a sense of control than repeatedly power-cycling and
hoping the system boots normally.)
The closest example I could find on search was 16389 - however none of the
workarounds there help, and when the screen fades the machine is subsequently
completely unreponsive.
Debian 10 buster, 1:19.0.1-1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3594 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-07-22 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 9:38 bugzilla-daemon [this message]
2019-07-22 10:33 ` [Bug 111182] Fade-to-white after KMS is set on RV635 bugzilla-daemon
2019-11-19 9:35 ` 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-111182-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.