On 2006-04-06 (Thu) 15:39:37 Jonas Smedegaard wrote: > > What is the best way to do mainboard-upgrades with generic kerneles > > and initrd. > > > Well, "best" depends on your goal. > > The design of yaird is to create "working ramdisks only", based on your > current hardware - it refuses to build ramdisks suspectedly not working > (eg. when upgrading kernel and the new kernel lack a required driver). So I started my system with 2 sata controllers. But disk was connected only to my silicon_image controller on pci. And I was expecting that regenerating initrd with two controllers will add both modules to initrd.
> As Max indirectly suggest, you could also switch from yaird to > initramfs-tools, the alternative ramdisk generator he is maintaining. > The design of initramfs-tools is to create "general mostly working > ramdisks", inspired by your current hardware - it relies on udev to > figure out the hardware needed. > > > > What are advantages for using generic-kernles if they always fail > > after hrdware upgrade? > > None of the ramdisk generators in Debian do *always* fail after > hardware upgrade. > > If you want plug'n'pray where you usually don't need to plan ahead, > then use inintramfs-tools. > > If you like the yaird design goal, then you need to prepare when > switching your setup: Each ramdisk image is optimized for a specific > setup, so you need to somehow generate an image _after_ changing setup > but _before_ booting into it. > > If all you need is to load that different driver, then > edit /etc/yaird/Default.conf and add "MODULE sta_via" and regenerate. Oki. I made it in that way, and everything works fine. > Leaving this bug open, as it is uncertain if yaird completely fails to > detect this VIA-based hardware correctly... actually it was intel-based controller so It needed ata_piix.ko module. I have via raid controller, so first I was thinking it will be via sata controller. Yaird was not adding modules, probably because there were no disks connected to this controller. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
