I attempted to use linux-image-2.6.14-2-k7, and I have the same problem
others reported.
Here's the symptoms:
After a normal install of the kernel, the system built an appropriate
initrd.img -- using yaird, which installed along with the new kernel. I
rebooted the system. I got the same message as Bruno did, to the best of
my recollection:
/usr/lib/yaird/exec/run_init: opening console: No such file or directory
Kernel panic _ not syncing: Attempted to kill init
Ok, I figured it was a problem with RAID, SATA, or something similar, so
I rebuilt /boot/initrd.img.2.6.14-2-k7 using mkinitrd. When I tried that
image, boot also failed, this time with a complaint about dev/console.
I am using devfs. (Until I have an opportunity to figure out how that
udev replacement technology works; I haven't seen a conversion how-to yet.)
I read the notes in the bug report response that state:
Underneath the tmpfs mounted on /dev is the /dev/ that is part of your
root device.
but I don't understand this at all. How does remounting / under /mnt
help me find /dev/.static? What tmpfs fs -- the devfs fs? In any case, I
get "null" under /mnt/dev when I attempt to mount, and no .static directory.
I am currently running 2.6.12-1-k7, which is that I used to build
initrd.img (both mkinitrd and yaird versions).
Jonas, if you would like me to rebuild initrd.img using yaird and place
it online somewhere, please let me know and I shall. And I'd appreciate
any help.
--
Moshe Yudkowsky * [EMAIL PROTECTED] * www.pobox.com/~moshe
"He will win who knows when to fight
and when not to fight." -- Sun Tzu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
