All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82588] X fails to start with linus-tip or drm-next
Date: Mon, 15 Sep 2014 22:00:46 +0000	[thread overview]
Message-ID: <bug-82588-502-YzieYLiEBC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82588-502@http.bugs.freedesktop.org/>


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

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

--- Comment #19 from jospezial <jospezial@gmx.de> ---
(In reply to comment #18)
> That's the issue - it seems there was an issue with the firmwares I
> downloaded
> 
> Isn't there new checking in the code to make sure the firmwares are correct?
> 
> Now running 3.16-rc5 with no issues

You wanted to say 3.17-rc5?

So is it bad to use 3.16.2 and 3.17-rc5 because every kernel installs his
firmware files to the same directory and overwrites the other one's?

The kernel installs the firmware with most of the filenames of r(v)+numbers in
/lib/firmware/radeon/ .

And the gentoo package "x11-drivers/radeon-ucode-20140823" installs the files
with the chip codenames and some numbered files which are not installed by the
kernel in the same dir.

So much from me now for more confusion.

You marked that bug as resolved/invalid.

Would you please tell me in detail, how you fixed this? I'd like to reopen this
bug.
Reverting "drm/radeon/cik: Add support for new ucode format (v5)" did not help
me.

I know I have to bisect ... But this is new stuff for me.

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

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

  parent reply	other threads:[~2014-09-15 22:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 22:41 [Bug 82588] New: X fails to start with linus-tip or drm-next bugzilla-daemon
2014-08-13 22:42 ` [Bug 82588] " bugzilla-daemon
2014-08-13 22:42 ` bugzilla-daemon
2014-08-14  1:35 ` bugzilla-daemon
2014-08-14  7:28 ` bugzilla-daemon
2014-08-18  6:03 ` bugzilla-daemon
2014-08-26 22:05 ` bugzilla-daemon
2014-08-26 22:13 ` bugzilla-daemon
2014-08-26 22:16 ` bugzilla-daemon
2014-09-07 22:58 ` bugzilla-daemon
2014-09-08 21:36 ` bugzilla-daemon
2014-09-13  0:22 ` bugzilla-daemon
2014-09-13 16:11 ` bugzilla-daemon
2014-09-13 16:12 ` bugzilla-daemon
2014-09-13 16:44 ` bugzilla-daemon
2014-09-13 16:51 ` bugzilla-daemon
2014-09-13 18:52 ` bugzilla-daemon
2014-09-13 18:54 ` bugzilla-daemon
2014-09-15 18:43 ` bugzilla-daemon
2014-09-15 22:00 ` bugzilla-daemon [this message]
2014-09-15 22:05 ` bugzilla-daemon
2014-09-15 22:06 ` bugzilla-daemon
2014-09-16  4:25 ` bugzilla-daemon
2014-09-16  5:25 ` bugzilla-daemon
2014-09-16 13:51 ` [Bug 82588] [drm:r100_ring_test] *ERROR* radeon: ring test failed - since linux-3.17_rc1 on RS690/RS740 [Radeon 2100] bugzilla-daemon
2014-09-16 14:03 ` bugzilla-daemon
2014-09-17  3:51 ` [Bug 82588] X fails to start with linus-tip or drm-next bugzilla-daemon
2014-09-17 13:44 ` 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-82588-502-YzieYLiEBC@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.