From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60741] When using the 3.10 kernel, System boot is blocked on the udev stage because of loading the radeon DRM module
Date: Wed, 14 Aug 2013 02:34:21 +0000 [thread overview]
Message-ID: <bug-60741-2300-Lppjx8RBE3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60741-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60741
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher <alexdeucher@gmail.com> ---
I'm guessing you are getting a stall due to waiting for the firmware fetch to
time out. Make sure your initrd contains the firmware if you are using one or
if you are building the driver into the kernel, make sure the firmware is built
in as well. If you wait for a few minutes the the firmware fetch will
eventually timeout and the kernel will continue. You can also try backlisting
radeon and then booting to a non-X runlevel and then try loading radeon
manually. At that point the filesystem will be available and the driver will
be able to access the firmware.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-08-14 2:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 1:46 [Bug 60741] New: When using the 3.10 kernel, System boot is blocked on the udev stage because of loading the radeon DRM module bugzilla-daemon
2013-08-14 1:49 ` [Bug 60741] " bugzilla-daemon
2013-08-14 2:34 ` bugzilla-daemon [this message]
2013-08-14 2:49 ` bugzilla-daemon
2013-08-14 2:52 ` bugzilla-daemon
2013-08-14 3:14 ` bugzilla-daemon
2013-08-14 3:18 ` bugzilla-daemon
2013-08-14 3:23 ` bugzilla-daemon
2013-08-14 3:25 ` bugzilla-daemon
2013-08-21 8:17 ` bugzilla-daemon
2013-08-21 12:45 ` bugzilla-daemon
2013-08-23 2:01 ` 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-60741-2300-Lppjx8RBE3@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.