Kernel panic - not syncing. No init found.
andreas at tddm.se
Sat Oct 29 07:57:54 PDT 2005
Ken Moffat skrev:
> On Sat, 29 Oct 2005, Andreas Åberg wrote:
>>>> 1. Yes they exist.
>>>> 2. Yes i can run /bin/bash, and everything else to.
>>> Odd. In that case, the primary suspect has to be a linking problem.
>>> I'm no expert on how programs linked with uClibc ought to look, but
>>> what does 'ldd /bin/bash' show when you are inside chroot ?
>>> FWIW, if this was a /dev problem, I think you would get a different
>>> message, something like "unable to open initial console". You do have
>>> console and null in /mnt/lfs/dev (before running udevstart in chroot),
>>> don't you ?
>> No I have checked that and there is nit linking problem.
> Sure ? If you don't tell the list what ldd shows, nobody can offer
> alternative views, or be reminded of previous things they've seen.
> I was going to say that I'm out of ideas, but I do have one more -
> one of the libraries shown by ldd doesn't exist.
As far as I can telle there is no problem with the linking... but you
are right perheps someone else can spot something?
libintl.so.3 => /lib/libintl.so.3 (0xb7fec000)
libc.so.0 => /lib/libc.so.0 (0xb7f55000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb7ffb000)
ls -l /lib/libintl.so.3
lrwxrwxrwx 1 root root 16 2005-10-25 21:26 /lib/libintl.so.3 -> libintl.so.3.4.3
ls -l /lib/libintl.so.3.4.3
-rw-r--r-- 1 root root 44854 2005-10-26 01:38 /lib/libintl.so.3.4.3
ls -l /lib/libc.so.0
lrwxrwxrwx 1 root root 19 2005-10-26 01:23 /lib/libc.so.0 -> libuClibc-0.9.28.so
ls -l /lib/libuClibc-0.9.28.so
-rw-r--r-- 1 root root 596076 2005-10-26 01:38 /lib/libuClibc-0.9.28.so
ls -l /lib/ld-uClibc.so.0
lrwxrwxrwx 1 root root 19 2005-10-26 01:23 /lib/ld-uClibc.so.0 -> ld-uClibc-0.9.28.so
ls -l /lib/ld-uClibc-0.9.28.so
-rwxr-xr-x 1 root root 21096 2005-10-26 01:38 /lib/ld-uClibc-0.9.28.so
>> I have a console and a null, however I did notice now that i miss a
>> /dev/initctl where does that come into the picture?
> Created by init, apparently, as a fifo for telinit to use. But, how
> do you know it's missing ? In a normal boot the kernel sees the /dev
> containing only console and null, then later mounts a filesystem over
> it and uses udev to populate that. You haven't had a successful boot,
> so you can't see what did or didn't get created.
> If you mount /mnt/lfs and do not attempt to chroot to it, its /dev
> directory should contain only console and null, as character special
> devices 5,1 and 1,3.
When I chroot into /mnt/lfs and run the startupscript including
udevstart, the /dev gets populated but not with a initctl... but it is
perheps only created at boot time....
More information about the lfs-support