> [4.824106] RAMDISK: gzip image found at block 0
> [5.568304] List of all partitions:
> [5.569281] No filesystem could mount root, tried:
> [5.571015] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(1,0)
> [5.572147] Pid: 1, comm: swapper Not taint
Hi Eric,
On Sat, 2011-10-22 at 11:26 -0700, Eric House wrote:
> Or: lsmod on my LEAF 3.x system shows ext2 as having no dependencies.
> Has this changed for 2.6? Are there other modules I need to add to
> initrd.lrp for ext2 to work?
Just tested this myself. Looks like the 2.6 ext2.ko depends on
Andrew wrote:
> On LEAF 4.x we switched from old, legacy ATA/ATAPI/MFM/RLL drivers to
> SCSI-like PATA/SATA drivers, which results in changing drive names from
> hdX to sdX.
Thanks. That's not the source of my problem then: I'll go with sda3
everywhere.
> What is said in dmesg after mount fai
Hi Eric
at 21.10.2011 08:59, Eric House wrote:
...
>
> BTW, I'm booting with grub, so both grub's conf file and leaf.cfg must
> agree on the device path. I've tried changing both from /dev/hda3 to
> /dev/sda3 without success. I've also tried manually mounting /dev/sda
> devices from the recover
21.10.2011 09:59, Eric House пишет:
> After three or four years of pretty much ignoring LEAF because 3x was
> *just working* on a couple of Soekris and WRAP boards I'm trying to
> upgrade the latter to 4.1. And failing. The failure comes because
> the packages described in leaf.cfg can't be loade
After three or four years of pretty much ignoring LEAF because 3x was
*just working* on a couple of Soekris and WRAP boards I'm trying to
upgrade the latter to 4.1. And failing. The failure comes because
the packages described in leaf.cfg can't be loaded:
[ 13.574839] sda: sda1 sda2 sda3 sda4
