If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

He can put radeon.modeset=1 on the kernel commandline and then load the radeon module a bit later in the boot process (when all needed filesystems are mounted so the firmware will be found). KMS will then work, I have used it this way.

Comment

/lib/firmware *should* be available after the root filesystem is mounted as long as /lib is not on another device.
If you use an initrd then shouldn't the necessary f/w should then be included within it so that its loaded as soon as you boot rather than waiting for filesystems to be mounted?

Comment

For some reason it does not work.
I have just now migrated from the setup I described in my earlier comment. I now compiled the radeon module into the kernel and it really couldn't find the firmware. I had to compile it into the kernel image as already described by other posters (I just came to the same solution as they did). I don't know why. /lib/firmware is on the root device.

Comment

For some reason it does not work.
I have just now migrated from the setup I described in my earlier comment. I now compiled the radeon module into the kernel and it really couldn't find the firmware. I had to compile it into the kernel image as already described by other posters (I just came to the same solution as they did). I don't know why. /lib/firmware is on the root device.

The firmware has to be in the initrd if you are using one since that is used before the filesystems are mounted and in most cases radeon is loaded early so you can have a console on boot. If you compile the driver into the kernel, you have to compile the firmware into the kernel as well.