All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34462] 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?)
Date: Fri, 18 Feb 2011 21:23:15 -0800 (PST)	[thread overview]
Message-ID: <20110219052316.1C45A130009@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-34462-502@http.bugs.freedesktop.org/>

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

--- Comment #2 from Owen Riddy <owen.riddy@gmail.com> 2011-02-18 21:23:16 PST ---
Comparing the initrd of 2.6.37 and 2.6.32 show they are both the same, and
neither of them have any firmware in them. They didn't actually have the radeon
module at all.

I compared /lib/firmware to the git repository
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git , everything
matched (I checked with md5sum) except the newer
BARTS/CAICOS/BTC/PALM/SUMO/TURKS firmware which I assume is all later than my
card.

I tried to force update-initramfs to include the radeon kernel modules by
listing it in /etc/initramfs-tools/modules, but this caused the
update-initramfs to hang when loading radeon.ko in.

Rather than try to insert everything manually in my initrd, I blacklisted
radeon in /etc/modeprobe.d and modprobe'd it in after a complete boot to a
virtual terminal.

On my old kernel, this worked swimmingly (no radeon in lsmod, module loaded
nicely). On the debian stock kernel modprobe hangs, I stopped timing after ten
minutes, the screen doesn't resize as usual for KMS, lsmod lists
radeon/drm/drm_kms_helper. dmesg again shows only RS780 Microcode being loaded.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-02-19  5:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 22:01 [Bug 34462] New: 180 second hang on boot, DRM doesn't seem to initialize (firmware issue?) bugzilla-daemon
2011-02-18 22:26 ` [Bug 34462] " bugzilla-daemon
2011-02-18 22:29 ` bugzilla-daemon
2011-02-19  5:23 ` bugzilla-daemon [this message]
2011-02-20  9:47 ` bugzilla-daemon
2011-02-23 14:05 ` bugzilla-daemon
2011-02-24 10:11 ` bugzilla-daemon
2011-12-03  8:16 ` bugzilla-daemon
2014-09-14  7:04 ` 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=20110219052316.1C45A130009@annarchy.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.