Declan Moriarty wrote:
<0>Kernel panic - not syncing: Attempted to kill init!
Not enough there for us.
My apologies. I'm still ploughing through Google results, but while
I've found many posts along the order of mine ("Help! I just installed
XXX and now I get this kernel panic!") I haven't yet found a reference
to interpret what it means, exactly.
Aside from the source (I'll need to go there eventually, but I was
hoping to be further along in my understanding before then...), is there
a shortcut to a reference for understanding how one might deciper what
was printed, and what this particular panic means?
> Your hardware may not be coming up correctly. I'd be looking for
> your mobo chipset driver(s) and video driver(s) compiled in, and
> other drivers not compiled in.
The "hardware" is VMWare Player 5.5. It brought up svn-20060108 without
a hitch. AFAIK, the only thing that might vary in practice from install
to install is the CPU type, which in my case is an Athlon MP. However,
this is literally the exact same install which is (simultaneously)
running the LFS livecd and HLFS svn-20060108. So, I don't think it's a
hardware issue.
Mount the disk and go through the logs. Get into /var/log and find
the first error in the boot, which usually is the issue. ideally
use a distro kernel, made to be as adaptable as possible.
One nice thing about doing this one VM is that this kind of thing is
very easy. I built the HLFS system under the livelfs cd, and have been
booting back to that and remounting the HLFS partition to try new ideas.
I can mount it under Fedora Core 4 if there's some tool there that
would make debugging easier...
Some of what I got back from Google suggested a problem with /dev, and
perhaps with grub not seeing the devices right. The latter, at least,
doesn't seem to be the issue; I haven't ruled out the former yet
(trouble with udev). I'm guessing that the kernel is bailing out very
early in the inittab, but I don't know where.
In any event, there's no data in /var/log - literally. They're virgin
from the install.
Another useful thing is to set up another kernel and modules in grub.
You may have to copy over /lib/modules/something as well, and boot on a
known good kernel & modules, then hunt for errors.
My thought was to copy over and install the known good svn-20060108
kernel, system map etc and see what happens. My plan was that if that
works, I'd recompile the new kernel with the config I used for 20060108
and see what happens then.
On what basis would one suspect an issue in the kernel itself over the
rest of the install?
Just off of what I've read from Google, my suspicion is that something
is wrong with udev, and that it manifests when we try to remount
/dev/hda1 as / rw. But I don't know how to check that. When I boot
under LFS and chroot in, /sbin/udevstart works and populates /dev
correctly...
-jps
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
