From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108221] amdgpu: mouse cursor flickers + black boxes
Date: Fri, 22 Jan 2016 08:36:16 +0000 [thread overview]
Message-ID: <bug-108221-2300-OELRVX0Lc7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-108221-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=108221
--- Comment #14 from Fred Santos <frederic.santos@u-bordeaux.fr> ---
(In reply to Michel Dänzer from comment #10)
> (In reply to Fred Santos from comment #9)
> > (Is there a way to 'force' the use of amdgpu?)
>
> Yes, you can force it in Section "Device" in /etc/X11/xorg.conf . If there
> is no such file yet, creating it with only something like this should work:
>
> Section "Device"
> Identifier "Device0"
> Driver "amdgpu"
> EndSection
I compiled and booted some old kernels, and here are my observations:
1. Even when booting with old kernels that should have worked fine (e.g., 4.2),
the problem persists...
2. We found (Comment #10) that amdgpu was not found/activated during boot: when
'forcing' its use by creating this /etc/X11/xorg.conf file, everything is OK,
with all kernels I have tested (4.4, 4.3, 4.2). To put it in a nutshell, no
matter the kernel we use, we have the same behavior: it works if and only if we
add this /etc/X11/xorg.conf file.
Maybe an Xorg autodetection problem that doesn't come from the kernel itself?
(Is it possible?)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-01-22 8:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 10:11 [Bug 108221] New: amdgpu: mouse cursor flickers + black boxes bugzilla-daemon
2015-11-23 14:52 ` [Bug 108221] " bugzilla-daemon
2015-11-24 9:20 ` bugzilla-daemon
2015-11-25 3:37 ` bugzilla-daemon
2016-01-17 9:51 ` bugzilla-daemon
2016-01-18 6:41 ` bugzilla-daemon
2016-01-18 7:36 ` bugzilla-daemon
2016-01-18 7:37 ` bugzilla-daemon
2016-01-18 7:57 ` bugzilla-daemon
2016-01-18 8:24 ` bugzilla-daemon
2016-01-18 9:56 ` bugzilla-daemon
2016-01-18 14:07 ` bugzilla-daemon
2016-01-18 14:08 ` bugzilla-daemon
2016-01-19 9:30 ` bugzilla-daemon
2016-01-22 8:36 ` bugzilla-daemon [this message]
2016-01-27 7:21 ` 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-108221-2300-OELRVX0Lc7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).