This is an old revision of the document!
====== Booting Fedora with BKO ====== ===== Where I am getting stuck ===== Following are the messages which are showen before getting stuck <code> Mounting proc filesystem Mounting sysfs filesystem Creating initial /dev Running plymouthd udev: starting version 141 </code> and It hangs after this point. I have bad feeling that it is not even reaching the step where it will execute /init script <code> squashfs: version 4.0 (2009/01/31) Phillip Lougher </code> Found the problem, ''plymouth'' is not working properly. I don't know the reason right now, but for time being, I have commented out the line which starts plymouth and it is progressing after that point. ===== Mounting iso over httpfs ===== Quite a few things are missing from fedora initrd, so I am adding them as and when I am encountering the errors related to them. - Added ''ifconfig'' and ''route'' by using ''busybox'' soft link. (Note : I am using knoppix busybox here, Not using fedora busybox because it is not statically linked ) - Adding fuse module, somehow it is missing, it should have been present by default in kernel. But may be my assumption is wrong about fuse that fuse will present in kernel by default. Finally, iso is mounted over httpfs. ===== Next set of problems ===== <code> /dev/root: error opening volume /dev/root: error opening volume JBD: barrier-based sync failed on dm-0:8 - disabling barriers transfering control to /sbin/init Bug in initramfs /init detected. Dropping to a shell. Good luck! </code> It seems, fedora wants something to be set for ''/dev/root'' and another thing that I need to find out is what is this ''JBD'' error about ''barrier-based sync failed'' ==== /dev/root ==== ''/dev/root: error opening volume'' is handled, I just looked for various places where ''/dev/root'' is used and wrapped it with ''if [-z ${HTTPFS}]'' \\ now I need to find out what is that JBD problem ==== JBD problem ==== I initially doubted function ''do_live_overlay'' but it is clean, now, concentrating parent function ''do_live_from_base_loop'' function. may be, problem is in ''run-init'' script
