Bug#575501: initramfs-tools: radeon.ko not included into initrd
On Fri, Mar 26, 2010 at 02:39:47PM +0100, Marc Haber wrote:
> On Fri, Mar 26, 2010 at 02:20:06PM +0100, Bastian Blank wrote:
> > On Fri, Mar 26, 2010 at 01:25:38PM +0100, Marc Haber wrote:
> > > I see. So there is no KMS for radeon at this time?
> > There is. The radeon module is loaded by udev later from the real
> > system.
> This doesn't seem to work here,
You either have to set DRM_RADEON_KMS to enable auto-loading---this is
done partially in the Debian kernels to provide an upgrade path---or
load it somewhere early, via /etc/modules for example.
> as the modeset-parameter never gets
> its way to the module, despite /etc/modprobe.d/radeon-kms.conf saying
> "options radeon modeset=1".
I'm not sure how this module is loaded in the traditional way. But maybe
the Xorg and kernel logs shows something.
> Also, in my understanding, if I want a splashscreen to be shown, the
> graphics driver moduled needs to be loaded early, right?
You ignore the first step ("make it work") and directly go to the second
("make it right"). You have not shown anything (logs for example,
installed packages with i-t hooks) that suggests that i-t does anything
wrong; the case that you use a different kernel config than the official
kernels does not make it easier.
> Are the directfb-based splash screens such as splahy compatible with
> KMS in the first place?
KMS provides a framebuffer device, so I would say yes.
> > | $ gunzip -c initrd.img-2.6.32-4-686-bigmem | cpio -tv | grep -a i915
> > | -rw-r--r-- 1 root root 23 Jan 7 23:51 etc/modprobe.d/i915-kms.conf
> What are you trying to say? You need to be a little bit more verbose
> to be actually helpful.
There is no i915 module in a initramfs generated on my rather generic
system. So it is included either by your config or by another package.
Bastian
--
The sight of death frightens them [Earthers].
-- Kras the Klingon, "Friday's Child", stardate 3497.2
Reply to: