[gentoo-user] [drm] loading RV710 Microcode fails

[gentoo-user] [drm] loading RV710 Microcode fails

[James]

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

Re: [gentoo-user] [drm] loading RV710 Microcode fails

[Gregory Shearman]

In linux.gentoo.user, you wrote:
> 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.

Are you using kernel modesetting? If you are then you have to get your
microcode built into the kernel.

You need CONFIG_EXTRA_FIRMWARE, and provide the filenames of the
firmware you require (in the form of a space delimited string) to run
your graphics card.

You also need CONFIG_EXTRA_FIRMWARE_DIR to tell the kernel where to find
the microcode. Mine is set to /lib/firmware.

> 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.....?

I don't think it has anything to do with HAL. Check to make sure if you
are now running Kernel Modesetting where the previous kernel wasn't.

-- 
Regards,
Gregory.

[gentoo-user] Re: [drm] loading RV710 Microcode fails

[James]

Gregory Shearman <zekeyg <at> gmail.com> writes:


> Are you using kernel modesetting? If you are then you have to get your
> microcode built into the kernel.

Not sure, can you be more specific on "modesetting" as 
grepping the /usr/src/linux/.config does not find anything,
so I'm not exactly sure what "modesetting" refers to....

Nothing under the "Generic Driver section of the kernels
I have been using has changed. The kernel worked before
I began following web pages and notes from this list
on removing hald and the hal flag from the system. I did
rebuild the kernel-2.6.36-gentoo-r5 after these
hal purge exercises began.....

CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""

> You need CONFIG_EXTRA_FIRMWARE, and provide the filenames of the
> firmware you require (in the form of a space delimited string) to run
> your graphics card.

Here are the setting from .config, as they always have
been: (I'd prefer not to use modsetting, unless provided
a GOOD reason to use it?)


CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""