Summary: | machine reboots trying to boot using kernel generated by genkernel (3.0.1_beta9) | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Moshe Kamensky <kamensky.fb> |
Component: | genkernel | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | nico |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Moshe Kamensky
2004-02-02 12:00:29 UTC
what coreutils version do you have installed? This has been reported before, but most people do not see this. -Brad coreutils-5.0.91-r4 (+acl +nls) I have the same problems with my Asus M6800N laptop. It is weird that I cannot boot the 2.6.1-gentoo kernel using root, real_root and init as parameters, but when I only put root=/dev/hda1 and then type /dev/ram0 when the bootscript asks for a boot partition, I can continue booting. i tried the following kernels: kernel-2.6.1 kernel-2.6.1-gentoo kernel-2.6.2-rc1-gentoo kernel-2.6.2-rc2-love4 kernel-2.6.2-rc2-mm1 and i was only able to boot 2.6.1-gentoo successfully. A search in Google Groups shows reports of first boot problems like this starting on January 19th, 2004. Search for the string "root block device unspecified on boot" e.g., http://groups.google.com/groups?q=%22root+block+device+unspecified%22 I experienced this on a machine that I built this week according to the GRP (I did stage 3) except that I did an emerge sync and did not ask emerge to use local packages. Two separate install attempts failed this way. I warned one of my coworkers about this, he skipped the emerge sync and is booting fine. It seems like an ebuild released in mid-January was flawed. I could fix it the way Moshe Kaminsky suggested: edit linuxrc on the initrd, change test to [ and add ] at the end of these lines remove umount /dev and change the last line to the chroot way - the author of the script seems to be unsure about how this should be done, look at the comments well, I removed 'test' because too many people have reported this now. I was told by Weeve that using [ ] on old coreutils versions did not work, as we've pivot_root'd at that point, and it uses the executables found on the root filesystem at that point. on _beta10 this is changed back to using [ ], so hopefully we won't see this issue anymore Well, this removed the previous errors, but now I get: /linuxrc: 295: cannot open /dev/console: No such file and right after that (the rather dramatic) kernel panic: Attempted to kill init! I still can boot with my version of linuxrc, where the line umount /dev (in step 6) is removed, and no ${CMDLINE} in the arguments to init sounds like when you installed your OS, you had a bad stage. There was a bug in some previous stages that did not have a /dev filesystem filled in with default device nodes. You must chroot into your filesystem with the livecd, and mkdir -p /dev ; MAKEDEV generic and try again. -Brad I'm having the exact same error as <a href="http://bugs.gentoo.org/show_bug.cgi?id=40210#c7">#7</a> Using kernel 2.6.7-r6 Anyone else still experimenting this problem? I wouldn't mark it as fixed. I tried: livecd / # mkdir -p /dev ; MAKEDEV generic and got: Running MAKEDEV in your root filesystem is a VERY BAD IDEA. Are you sure this is a good thing to do? My /dev looks fine, with all the nodes there. any hints? |