/boot is ext3, rootfs is ext4. That was the first thing I checked. I am tempted to start over and clone the card the unit shipped with to the new card, then repopulate the rootfs. I can get the networking configs out of the running card. Then maybe I can build a EL kernel and headers for it, then build zfs support into the kernel.
I wish I had the screen dump in front of me, somewhere very early in the initialization process, the chipset identifies itself as Sheeva, so I thought it would work. I do remember you saying that now... Well, live and learn. On Thu, Jul 19, 2012 at 10:12 AM, Gordan Bobic <[email protected]> wrote: > > I doubt it - the RSEL kernel is for Kirkwood and unless you have a > Sheeva/Guru/DreamPlug it wouldn't work. Hence why I said to keep the > original kernel and /lib/[modules|firmware] that the device shipped with. > > If I had to hazard a guess, it might be worth checking what FS the working > SD card has. Uboot is known to not understand ext4, and it is plausible > that your kernel can't, either. Worth double checking. > > > The boot order, if the nvram image is not used, is USB0, USD1, microsd, >> esata, then tftp, which is where I get stuck trying to boot to the new >> card. >> >> Here is the output on both cards: >> >> New card: >> >> /dev/sdb1 : start= 16, size= 39088, Id=83 >> /dev/sdb2 : start= 39104, size= 15484736, Id=83 >> >> Existing card: >> >> /dev/mmcblk0p1 : start= 16, size= 39088, Id=83 >> /dev/mmcblk0p2 : start= 39104, size= 15646528, Id=83 >> > > So far so good. What about the file system used? Is there a chance the > original SD card uses ext[23] and your new one uses ext4? > > > Gordan > ______________________________**_________________ > users mailing list > [email protected] > http://lists.redsleeve.org/**mailman/listinfo/users<http://lists.redsleeve.org/mailman/listinfo/users> > -- Thanks, Ian M Perkins
_______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
