From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74911] [R9 270X] - Frozen display output and no response from keyboard right after loading kernel image and initramfs
Date: Mon, 28 Apr 2014 09:37:38 +0000 [thread overview]
Message-ID: <bug-74911-2300-IMTu6jhMnt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-74911-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=74911
--- Comment #2 from Ivan Bulatovic <combuster@archlinux.us> ---
> How long have you waited for? Trying to load a non-existent firmware file
> may only time out after a minute or so.
I've left it once for a while, but I'll test for how long and report back,
seems to me it was about 4min.
>
> > This makes sense, there is no radeon/PITCAIRN_mc2.bin blob anywhere. At
> > least not in linux-firmware branch.
>
> You can get it e.g. from:
>
> http://people.freedesktop.org/~agd5f/radeon_ucode/
>
Thanx, got it!
> > I have compiled radeon drivers into the kernel image itself, [...]
>
> It's recommended to build the radeon driver as a module instead and let the
> firmware files be loaded from the initrd or normal filesystem.
Well, if it was recommended I haven't saw that recommendation anywhere. Used to
build an intel driver into kernel image itself, KMS kicks in as early as
possible. I did the same with radeon, and it works for me great this whole
time.
Don't mean to be rude or anything, but I don't know if it is recommended (or
desirable) to commit a piece of code to mainline that will _require_ a blob
that can't be found in linux-firmware ?
I'll see about the timeout and report back in.
Thanks Michel
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-28 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 15:27 [Bug 74911] New: [R9 270X] - Frozen display output and no response from keyboard right after loading kernel image and initramfs bugzilla-daemon
2014-04-28 8:27 ` [Bug 74911] " bugzilla-daemon
2014-04-28 9:37 ` bugzilla-daemon [this message]
2014-04-28 9:57 ` bugzilla-daemon
2014-04-28 10:20 ` bugzilla-daemon
2014-05-02 3:34 ` bugzilla-daemon
2014-05-02 3:36 ` bugzilla-daemon
2014-06-12 20:14 ` 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-74911-2300-IMTu6jhMnt@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 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.