On Sun, Oct 30, 2005 at 10:21:39PM +0100, Jonas Smedegaard wrote: > On Sun, 30 Oct 2005 15:25:33 +0000 "Richard Burton" <[EMAIL PROTECTED]> wrote: > > > >This could be changes to video drivers in the kernel. Please describe > > >your graphics card used. > > > > Oops, I did intened to mention that. It's an Nvidia GeForce 6600GT > > 128MB (generic unbranded reference board). > > Nvidia. Ok (or "ok" is perhaps an exageration: problems with this > specific hardware vendor is not really a surprise to me...) > > > > >Please try the following: > > >1) add "ramdisk = /usr/sbin/mkinitrd.yaird" to /etc/kernel-img.conf > > >2) make a backup of the initrd for your older working kernel > > >3) Run "dpkg-reconfigure <old kernel package>" > > >4) Reboot with older kernel > > > > Now older kernel hits same problem. So I guess this is yaird problem > > then? > > > > >You can also try installing initramfs-tools, uninstalling yaird, run > > >"dpkg-reconfigure <new kernel package>" and reboot with new kernel. > > > > Also has no video on boot. > > You did remember to uninstall yaird before regenerating the ramdisk? > > Then it sounds like the nvidia driver being buggy then - not a yaird > bug if also appearing with initramfs-tools. > > I am not experienced here, so others please comment, if this is a > known situation! > > Richard: Are you ready for some more geeky tests? Perhaps initrd-tools > loads other modules or in another order than both yaird and > initramfs-tools. 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, and (blindly) dump > to a separate file. Then post both dumps here...
Just a quick note that there's nothing in yaird 0.0.11 tarball to support vga=... This will probably require an extra module in the config file, vesafb or so, plus an equivalence to a kernel define (I seem to remember modular framebuffers are broken on some architectures, so it may be compiled in on some machines). Perhaps also an 'optional' variant of the MODULE keyword, that will not complain if the module is not compiled in and not a module. --erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
