Dixi quod… >Even if this may have some minor issues still, it’ll be better >than building kernel images that fail to boot at all, that’s why
Ah well. Of course it didn’t boot. /lib/modules/3.10-0+m68k.2-m68k/kernel/arch/m68k/emu/nfblock.ko is the “IDE” driver for ARAnyM machines (like virtio-blk). It’s not present in the initrd (others, like buddha, falconide, gayle, macide, q40ide in drivers/ide/ and atari_scsi.ko and friends in drivers/scsi/ are), which makes my boot fail, since I used root=/dev/nfhd8p1 like before (nfhd8 ~= vda in kvm terms). Which package is responsible for the inclusion of arch-specific kernel modules into the initrd (for MODULES=most right now; I have yet to try MODULES=dep)? Thanks, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
