On Mon, Oct 31, 2005 at 12:45:54AM +0100, Sven Luther wrote: > On Mon, Oct 31, 2005 at 12:13:30AM +0100, Jonas Smedegaard wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Sun, 30 Oct 2005 22:22:44 +0000 > > "Richard Burton" <[EMAIL PROTECTED]> wrote: > > > > > >Richard: Are you ready for some more geeky tests? > > > > > > Always ;-) > > > > :-) > > > > > > > >So if you could boot an old kernel with initrd ramdisk > > > >and kernel options "init=/bin/sh rw", and run the following command: > > > >/sbin/lsmod >/mkinitrd-modules.dump > > > >Then do the same with same kernel but yaird ramdisk > > > > > > It also needed a "mount /proc" for lsmod to work. It looks as though > > > yaird loads a whole lot less modules. If I had to guess I'd say it > > > might be all those frame buffer modules that mkinitrd version loads > > > but yaird doesn't. > > > > Try editing /etc/yaird/Default.cfg and add the following: > > > > MODULE vesafb > > > > Then regenerate ramdisk and reboot (but sounds like I don't need to > > spell things out to you...), and tell us how that went. > > Vesafb is no more modular now, and should either have been dropped fully or > builtin, please check the config file.
As the driver is no longer modular it is now built into the kernel on all i386 and amd64 architectures. It is not included in any other achitecture, but I believe this was the case when it was modular. # grep -r VESA debian/arch/ | grep -v .svn debian/arch/i386/config:CONFIG_FB_VESA=y debian/arch/amd64/config:CONFIG_FB_VESA=y The reason that it has been changed from modular to builtin, is that making it modular was a somewhat problematic patch. I hope we can find a solution that doesn't lead us back to that code. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
