Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am building a custom 2.6.18 kernel and creating initrd image using command mkinitrd.
I am creating a bootdisk out of these 2 through the command mkbootdisk and using that to boot on a different pc.But it throws out an error "Kernel Panic".
Sorry I can't do that yet for some reasons and I hope somebody else will do that for you instead.
But anyway I just recognized that you already have a working system (sorry 'bout that) and you're just trying to boot a newly built kernel right?; so your /etc/fstab is probably ok. You can know the proper root device that your should pass as an argument to 'root=' by doing 'cat /etc/mtab' or 'cat /proc/partitions' or just running 'mount' to have a list.
No friend,the kernel i build boots up on a working system.
What i am trying is to boot a bare PC(without OS) with a bootdisk created out of my kernel and initrd images.
I am getting error of this kind.
***********************************************************
Red Hat nash version 3.5.14 starting
Mounting /proc filesystem
Creating block devices
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 224k freed
Kernel panic: No init found. Try passing init= option to kernel.
Maybe the problem is caused by your "working system" and "bare PC" having different hardware and your kernel and/or initrd having hardware-secific stuff in them. How similar/different are the computers?
I think that means your kernel and/or initrd are looking for a root file system on the "bare PC" in the same place (/dev/sda or some such) as on your "working system" -- and not finding it.
N
Red Hat nash version 3.5.14 starting
Mounting /proc filesystem
Creating block devices
Creating root device
Mounting root filesystem mount: error 6 mounting ext3
pivotroot: pivot_root(/sysroot, /sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 224k freed
Kernel panic: No init found. Try passing init= option to kernel.
If only we can tell what's causing that error. Is the kernel built with support for ext3? Also there's probably a bad parameter for the initrd. For example, in gentoo, real_root needs to have the final root that will be mounted after booting on a temporary ramdisk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.