Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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 the 2.6.10 version of the kernel with a ramdisk (for
mips). When I build it with a gcc 3.4.3-glibc-2.3.6 toolchain, it
works find. When I build it with a gcc-4.2.2-glibc-2.7 toolchain I get
the following error:
Kernel panic - not syncing: No init found
Any suggestions? Note: the ramdisk images was built with Busybox (so
that can be the culprit). However, why would it work with the older
version of glibc? I am sure I am being stupid here; all help is appreciated!
This is a kernel image built for an embedded system. I have a very simple bootloader. The thing that is strange is that it works fine with the older toolchain but does not work with the newer one. Does anyone know any known issues there? I am using the same ramdisk for both.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.