Hi, Timo Juhani Lindfors a écrit , Le 03/11/2011 21:36: > Timo Jyrinki <timo.jyri...@gmail.com> writes: >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(179,1) > > I just tested with a SDHC card that is known not to work with linux. The > error message I get mentions unknown-block(0,0) and gives me a list of > partitions that only have mtdblock* entries.
Same error here. My guess is is that's due to linux-base which warns during (re-)configuration: > Configuring linux-base > ---------------------- > > The new Linux kernel version provides different drivers for some PATA > (IDE) controllers. The names of some hard disk, CD-ROM, and tape > devices may change. > > It is now recommended to identify disk devices in configuration files > by label or UUID (unique identifier) rather than by device name, which > will work with both old and new kernel versions. > > If you choose to not update the system configuration automatically, > you must update device IDs yourself before the next system reboot or > the system may become unbootable. Then: > Boot loader configuration check needed > > The boot loader configuration for this system was not recognized. > These settings in the configuration may need to be updated: > > * The root device ID passed as a kernel parameter; > * The boot device ID used to install and update the boot loader. > > You should generally identify these devices by UUID or label. > However, on MIPS systems the root device must be identified by name. I'm using qi-menu to handle multi-boot. There must be a way to change its configuration so that it uses UUIDs. Ant idea? Thanks, _g.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint
