All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101377] Gigabyte R9 380 card fails to load, kernel reports bug
Date: Sat, 29 Jul 2017 15:36:57 +0000	[thread overview]
Message-ID: <bug-101377-502-QnB6r0mLRX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101377-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 600 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101377

--- Comment #6 from john@dev1ce.com ---
the problem with this regression to older firmware is that while the kernel
boots, none of the 3D functionality inherent in the new drivers is functional.
I can regress to an older kernel with the newer firmware 20170622
https://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git

and the system boots, however with zero 3d support.

confirming this bug still exists in 4.12.0 through 4.12.14 as of today.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1450 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

  parent reply	other threads:[~2017-07-29 15:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11  3:44 [Bug 101377] Gigabyte R9 380 card fails to load, kernel reports bug bugzilla-daemon
2017-07-21 12:10 ` bugzilla-daemon
2017-07-22 20:36 ` bugzilla-daemon
2017-07-22 20:37 ` bugzilla-daemon
2017-07-22 20:40 ` bugzilla-daemon
2017-07-23  8:12 ` bugzilla-daemon
2017-07-29 15:36 ` bugzilla-daemon [this message]
2017-07-30 21:12 ` bugzilla-daemon
2017-07-30 21:42 ` bugzilla-daemon
2017-07-31 23:34 ` bugzilla-daemon
2017-08-01 12:17 ` bugzilla-daemon
2017-08-04 19:55 ` bugzilla-daemon
2017-08-08 16:38 ` bugzilla-daemon
2019-11-19  8:19 ` 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-101377-502-QnB6r0mLRX@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.