From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.
Date: Wed, 03 Jan 2018 12:57:36 +0000 [thread overview]
Message-ID: <bug-101483-502-pxl9MGOOf9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101483-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101483
--- Comment #39 from FFAB <lx@o2mail.de> ---
Upstream kernel test - kernel 4.15-rc6
Installation, on which upstream kernel was installed:
ubuntu 16.04.3, kernel 4.10.0-42, updated 2018-01-02
1. booting without any workaround parameters
2. booting with kernel parameter iommu=soft
boot-time 45sec
->> Login-screen!!!
Local login
Now:
led backlight brightness adjustable
hdmi connection works
systemsettings - display and monitor adjustable
"sudo lshw -short", missing line:
/0/100/3.1/0 display Topaz XT [Radeon R7 M260/M265]
attachments: 2018_01_02_dmesg_4.15-rc6.txt,
2018_01_02_dmesg_4.15-rc6_iommu_soft.txt
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1749 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-03 12:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 15:23 [Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter bugzilla-daemon
2017-06-17 15:27 ` bugzilla-daemon
2017-06-17 16:41 ` bugzilla-daemon
2017-07-03 22:24 ` bugzilla-daemon
2017-07-03 22:29 ` bugzilla-daemon
2017-08-21 18:29 ` bugzilla-daemon
2017-08-25 14:30 ` bugzilla-daemon
2017-08-25 14:38 ` bugzilla-daemon
2017-08-28 21:33 ` bugzilla-daemon
2017-08-28 21:35 ` bugzilla-daemon
2017-09-04 19:36 ` bugzilla-daemon
2017-09-04 19:38 ` bugzilla-daemon
2017-09-04 19:48 ` bugzilla-daemon
2017-09-17 16:58 ` bugzilla-daemon
2017-09-17 17:03 ` bugzilla-daemon
2017-09-17 17:04 ` bugzilla-daemon
2017-10-03 22:37 ` bugzilla-daemon
2017-10-07 14:01 ` bugzilla-daemon
2017-10-07 14:05 ` bugzilla-daemon
2017-10-10 13:32 ` bugzilla-daemon
2017-10-18 22:53 ` bugzilla-daemon
2017-10-31 13:01 ` bugzilla-daemon
2017-10-31 13:04 ` bugzilla-daemon
2017-10-31 13:06 ` bugzilla-daemon
2017-11-06 11:48 ` bugzilla-daemon
2017-11-06 11:50 ` bugzilla-daemon
2017-11-06 11:53 ` bugzilla-daemon
2017-11-14 13:46 ` bugzilla-daemon
2017-11-14 13:49 ` bugzilla-daemon
2017-11-14 13:50 ` bugzilla-daemon
2017-11-28 14:59 ` bugzilla-daemon
2017-11-28 15:02 ` bugzilla-daemon
2017-11-28 15:05 ` bugzilla-daemon
2017-11-30 16:25 ` bugzilla-daemon
2017-12-13 22:16 ` bugzilla-daemon
2017-12-13 22:19 ` bugzilla-daemon
2017-12-13 22:21 ` bugzilla-daemon
2017-12-14 11:43 ` bugzilla-daemon
2017-12-14 17:36 ` bugzilla-daemon
2017-12-14 22:37 ` bugzilla-daemon
2018-01-03 12:51 ` bugzilla-daemon
2018-01-03 12:52 ` bugzilla-daemon
2018-01-03 12:57 ` bugzilla-daemon [this message]
2018-02-12 16:15 ` bugzilla-daemon
2018-02-12 16:17 ` bugzilla-daemon
2018-02-12 16:20 ` 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-101483-502-pxl9MGOOf9@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 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).