From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [drm] loading RV710 Microcode fails
Date: Tue, 8 Feb 2011 19:19:49 +0000 (UTC) [thread overview]
Message-ID: <loom.20110208T200930-860@post.gmane.org> (raw)
Hello,
I cleanup up a system, per the postings to not use HAL.
k3b does not work, but, I'll look for a fix for it later.
I keep 2 kernels on this system.
kernel-2.6.34-gentoo-r12 and kernel-2.6.36-gentoo-r5
the *36 does not work. I have copied it over from
an identical system, build new kernels an still it
fails with the verbiage listed in the title.
I can go back and boot the old *34 kernel and all is
fine. The system was updated on 3Feb2011. I've tried
all sorts of things, but to no avail.
Google indicates that it may be the x setup. Before the
upgrade and elimination of hal the kernel-2.6.36-gentoo-r5
kernel worked just fine. Now if I build a new kernel, it
does not work.
somewhere in the removal of the use flag hal and the hald
it has decidded not build a kernel-2.6.36-gentoo-r5 that
will work, but boots and runs fine with older *34
gentoo stable kernel.
I have no idea what to do. When the boot tails, it
hard locks up so I have to reset power, boot the older
kernel so there is no dmesg trail to look at.
Reboot and Running:
xorg-server-1.9.2 ati-drivers-10.11
xorg-x11-7.4-r1 kernel-2.6.34-gentoo-r12
with no hald all is fine?
The old kernel was built with hal and hald
running, if that makes a difference.....?
Stumped
James
next reply other threads:[~2011-02-08 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 19:19 James [this message]
[not found] <gk1qb-m1-37@gated-at.bofh.it>
2011-02-08 21:21 ` [gentoo-user] [drm] loading RV710 Microcode fails Gregory Shearman
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=loom.20110208T200930-860@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox