From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41265] Radeon KMS does not work on thunderbolt media dock
Date: Fri, 28 Dec 2012 03:34:05 +0000 [thread overview]
Message-ID: <bug-41265-502-FGe5sau1sP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-41265-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=41265
--- Comment #53 from Gerald Nunn <gerald.b.nunn@gmail.com> ---
Does AMD need to make a change to the proprietary fglrx drivers in order for
the kernel patch to work with their drivers and if so has a bug been opened
with them? I'm using Ubuntu 12.10 with kernel 3.6.9 and no problem getting this
to work with the gallium (radeon) drivers, however when I try the fglrx drivers
I get the following messages in kern.log:
Dec 27 13:07:11 gnunn-laptop2 kernel: [ 11.925204] <3>[fglrx:hal_read_VBIOS]
*ERROR* Invalid AMD VBIOS!
Dec 27 13:07:11 gnunn-laptop2 kernel: [ 11.925207] <3>[fglrx:hal_init_gpu]
*ERROR* Failed to read VBIOS!
Dec 27 13:07:11 gnunn-laptop2 kernel: [ 11.925208] <6>[fglrx] device open
failed with code -1
Which sounds like a similar issue to what was described here. While I generally
find the gallium drivers to be more stable and reliable then fglrx,
unfortunately fglrx significantly outperforms the open source drivers when it
comes to gaming.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1941 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-12-28 3:34 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 15:48 [Bug 41265] New: KMS does not work on Radeon HD6700M bugzilla-daemon
2011-09-27 15:49 ` [Bug 41265] " bugzilla-daemon
2011-09-29 18:53 ` bugzilla-daemon
2011-09-29 18:54 ` bugzilla-daemon
2011-09-29 19:26 ` bugzilla-daemon
2011-10-13 17:36 ` bugzilla-daemon
2011-11-03 3:40 ` bugzilla-daemon
2011-11-04 15:37 ` bugzilla-daemon
2011-11-14 21:26 ` bugzilla-daemon
2012-01-05 9:58 ` bugzilla-daemon
2012-01-05 10:14 ` bugzilla-daemon
2012-01-10 13:59 ` bugzilla-daemon
2012-01-10 14:55 ` bugzilla-daemon
2012-03-09 13:04 ` bugzilla-daemon
2012-05-10 17:11 ` bugzilla-daemon
2012-05-10 17:14 ` bugzilla-daemon
2012-07-27 3:39 ` bugzilla-daemon
2012-07-27 5:08 ` bugzilla-daemon
2012-07-27 5:16 ` bugzilla-daemon
2012-07-30 8:45 ` bugzilla-daemon
2012-07-30 13:37 ` bugzilla-daemon
2012-08-04 16:14 ` bugzilla-daemon
2012-08-04 16:32 ` bugzilla-daemon
2012-08-04 16:35 ` bugzilla-daemon
2012-08-04 17:02 ` bugzilla-daemon
2012-08-09 21:12 ` bugzilla-daemon
2012-08-09 21:14 ` [Bug 41265] Radeon KMS does not work on thunderbolt media dock bugzilla-daemon
2012-08-10 12:11 ` bugzilla-daemon
2012-08-10 13:50 ` bugzilla-daemon
2012-08-10 17:44 ` bugzilla-daemon
2012-08-10 17:46 ` bugzilla-daemon
2012-08-12 15:40 ` bugzilla-daemon
2012-08-14 15:30 ` bugzilla-daemon
2012-08-14 17:05 ` bugzilla-daemon
2012-08-14 18:38 ` bugzilla-daemon
2012-08-15 3:20 ` bugzilla-daemon
2012-08-16 5:34 ` bugzilla-daemon
2012-08-16 8:39 ` bugzilla-daemon
2012-08-16 9:26 ` bugzilla-daemon
2012-08-16 10:08 ` bugzilla-daemon
2012-08-16 14:31 ` bugzilla-daemon
2012-08-16 15:16 ` bugzilla-daemon
2012-08-16 17:05 ` bugzilla-daemon
2012-08-16 17:21 ` bugzilla-daemon
2012-08-16 17:22 ` bugzilla-daemon
2012-08-16 17:29 ` bugzilla-daemon
2012-08-16 17:37 ` bugzilla-daemon
2012-08-16 17:39 ` bugzilla-daemon
2012-08-16 17:41 ` bugzilla-daemon
2012-08-16 18:23 ` bugzilla-daemon
2012-08-16 18:59 ` bugzilla-daemon
2012-08-17 10:09 ` bugzilla-daemon
2012-08-17 13:09 ` bugzilla-daemon
2012-08-17 13:09 ` bugzilla-daemon
2012-08-20 7:32 ` bugzilla-daemon
2012-09-05 20:41 ` bugzilla-daemon
2012-12-28 3:34 ` bugzilla-daemon [this message]
2013-01-07 17:16 ` 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-41265-502-FGe5sau1sP@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