After upgrading to sys-kernel/genkernel-3.4.10_pre7 and compiling both sys-kernel/gentoo-sources-2.6.23-r9 and sys-kernel/gentoo-sources-2.6.24-r3, and then rebooting the kernel. The kernel displays "{NORMAL} ERROR /dev is broken!!!" before boot runlevels start. I down graded to sys-kernel/genkernel-3.4.9 and compiled both sys-kernel/gentoo-sources-2.6.23-r9 and sys-kernel/gentoo-sources-2.6.24-r3, and the message didn't display. Reproducible: Always Steps to Reproduce: 1.emerge =sys-kernel/genkernel-3.4.10_pre7 2.genkernel --kernel-config=/etc/kernels/config --menuconfig --bootloader=grub all 3.reboot
First, that's not 3.4.10_pre7. The "{NORMAL}" thing was fixed in SVN at least a week before _pre7 was released. Second, what makes you think this is a bug? The message triggers when the /dev in your / is "broken", which means it's missing certain expected initial dev nodes.
(In reply to comment #1) > First, that's not 3.4.10_pre7. The "{NORMAL}" thing was fixed in SVN at least a > week before _pre7 was released. When I type the following: # emerge -pv genkernel These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-kernel/genkernel-3.4.10_pre7 USE="bash-completion (-ibm) (-selinux)" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB > Second, what makes you think this is a bug? The message triggers when the /dev > in your / is "broken", which means it's missing certain expected initial dev > nodes. I use sys-kernel/genkernel-3.4.10_pre7 to install the kernel I get that message. When I down grade to sys-kernel/genkernel-3.4.9 I don't get that message. Nothing else has changed on the system, but genkernel. Th
(In reply to comment #1) I was about to say thanks for the fast reply..
I get the same error message after a new installation with the command line installer from the 2008.0_beta1 dvd release.
C D, was your install done with the Gentoo Installer? If so, this happens because the installer only creates /dev/null and /dev/console, but genkernel now checks for /dev/tty1 as well. I modified the installer to create tty1 now, and I also modified genkernel to check for tty1 only if splash is enabled, since that's all it's needed for.
(In reply to comment #5) > C D, was your install done with the Gentoo Installer? If so, this happens > because the installer only creates /dev/null and /dev/console, but genkernel > now checks for /dev/tty1 as well. > > I modified the installer to create tty1 now, and I also modified genkernel to > check for tty1 only if splash is enabled, since that's all it's needed for. Yes, I did use the Gentoo Installer. I do have a /dev/tty1 file, but I do see a message talking about it around the same time as the "{NORMAL} ERROR /dev is broken!!!" was happening. How can I fix this problem?
What problem? Is it preventing you from booting? If not, just be patient and wait for a new genkernel release. You can live with the harmless warning for now.
I have the same problem, but I didn't encounter any other problem when I was using gentoo. So I didn't take to much care about it.
I upgraded to sys-kernel/genkernel-3.4.10_pre8 then sys-kernel/genkernel-3.4.10_pre9 and it fixed the problem... Thanks... Keep up the great work your are doing... Love this O/S!!!!!
Don't close this bug, please. We'll do that from our end.
OK. This is resolved in genkernel 3.4.10, which is now in the tree and stable.
