On Monday, August 14, 2017, Nicolas Pitre wrote: > > However, now with your mkcramfs tool, I can no longer mount my cramfs > > image as the rootfs on boot. I was able to do that before (ie, 30 > minutes > > ago) when using the community mkcramfs (ie, 30 minutes ago). > > > > I get this: > > > > [ 1.712425] cramfs: checking physical address 0x1b000000 for linear > cramfs image > > [ 1.720531] cramfs: linear cramfs image appears to be 15744 KB in > size > > [ 1.728656] VFS: Mounted root (cramfs_physmem filesystem) readonly on > device 0:12. > > [ 1.737062] devtmpfs: mounted > > [ 1.741139] Freeing unused kernel memory: 48K > > [ 1.745545] This architecture does not have kernel memory protection. > > [ 1.760381] Starting init: /sbin/init exists but couldn't execute it > (error -22) > > [ 1.769685] Starting init: /bin/sh exists but couldn't execute it > (error -14) > > Is /sbin/init a link to busybox? Yes. > I suppose it just boots if you do mkcramfs without -X? Correct. I just created another image and removed the "-X -X" when creating it. Now I can boot that image as my rootfs. (I'm using -X -X because I'm using a Cortex-A9 with MMU). > If so could you share your non-working cramfs image with me? I will send it (in a separate email) Chris -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
