Prev: Slack_12.2 dnsmasq quirk?
Next: hp smh and agents
From: mintflavor on 9 Jun 2010 21:18
I use Slackware64 13.1 and have ATI Mobility X1250 graphic card.
I recently downloaded and compiled kernel 2.6.34.
If I include DRM and radeon in the kernel, everything works fine.
If I compile DRM and radeon as modules and include them in initrd,
udev
fails to load RS600_cp.bin firmware, displays a black screen for a
minute,
and resumes booting. I confirmed it with dmesg.
Even after I put RS600_cp.bin in /boot/initrd-tree/lib/firmware/
radeon,
rebuild initrd, and execute lilo, udev fails to load the firmware.
Since I
want to compile only radeon source codes and not both radeon and
kernel, I
want to include radeon in initrd and enjoy the early apperance of KMS.
Is it
a mkinitrd bug? How can I solve this problem?
From: Clemens Ladisch on 10 Jun 2010 06:20
mintflavor wrote:
> If I compile DRM and radeon as modules and include them in initrd, udev
> fails to load RS600_cp.bin firmware, displays a black screen for a minute,
> and resumes booting. I confirmed it with dmesg.
> Even after I put RS600_cp.bin in /boot/initrd-tree/lib/firmware/radeon,
> rebuild initrd, and execute lilo, udev fails to load the firmware.

If I remember correctly the problem is that the graphics driver is
initialized before the kernel is able to run userspace programs.

You could try compiling the firmware file(s) into the kernel by adding
the file name(s) to CONFIG_EXTRA_FIRMWARE. (But then there's no reason
to have radeon as a module.)


Regards,
Clemens
 | 
Pages: 1
Prev: Slack_12.2 dnsmasq quirk?
Next: hp smh and agents