• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dual booting Gentoo and XP makes me want to cry

rbrandon

Banned
Just finished up installing Gentoo, XP and Gentoo are on separate disks, XP on the 1st, and Gentoo on the 2nd. I installed LILO on the 1st drive, and while XP boots fine, when i try to boot Gentoo I get the message


Kernel Panic:no init found. Try passing the init= options to the kernel.

Any help is appreciated, cuz Im stumped 🙁
 
Yeper.

In you lilo configuration do you have a line like:

init=initrd.blahblahblah.

For your gentoo entry? It should be very similar to your Kernel name. It's a actual file, the initrd is a loopback file system that temperarially becomes root to load up drivers, then you automaticly change over to the real root in the boot up proccess. Initrds are optional, but I think they are created by default during Gentoo's kernel compile tool usage.

Just boot up with your Gentoo install CD. Chroot over and fix it and rerun lilo and everything should be fine.
 
no good 🙁


heres my lilo.conf, just in case i made a dumb mistake (extremely possible)
😕



boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=30
lba32
default=Gentoo


#Gentoo
image=/boot/kernel-2.4.26-gentoo-r6
label=Gentoo
root=/dev/hdb1
initrd=/boot/initrd-2.4.26-gentoo-r6
append="root/dev/hdb1 init=/linuxrc"

#XP
other=/dev/hda1
label=WindowsXP

I'm sure theres a mistake there somewhere.....
 
Looks almost correct.

append="root/dev/hdb1 init=/linuxrc"

should be root=/dev/hdb1, forgot the = sign.

(If that isn't it, then just comment out the initrd line entirely and get rid of the init=/linuxrc part)
 
The gentoo forums are excellent for things like this, but I think drag has it.

I use grub myself and have never had a problem I couldn't fix with grub.
 
init=initrd.blahblahblah.

For your gentoo entry? It should be very similar to your Kernel name. It's a actual file, the initrd is a loopback file system that temperarially becomes root to load up drivers, then you automaticly change over to the real root in the boot up proccess. Initrds are optional, but I think they are created by default during Gentoo's kernel compile tool usage.

init= is used to set the binary for init, not the initrd.
 
Originally posted by: Nothinman
init=initrd.blahblahblah.

For your gentoo entry? It should be very similar to your Kernel name. It's a actual file, the initrd is a loopback file system that temperarially becomes root to load up drivers, then you automaticly change over to the real root in the boot up proccess. Initrds are optional, but I think they are created by default during Gentoo's kernel compile tool usage.

init= is used to set the binary for init, not the initrd.


I figured it's pointed to the init inside the initrd loopback filesystem. I don't remember seeing a linuxrc file anywere inside gentoo last time I used it, and you shouldn't need to specify the init anyways, unless you have a very special setup.

So that's why I told him to get rid of it...
 
Most initrds do use /linuxrc to bootstrap the system, but the kernel automatically looks for linuxrc after it mounts root so no, he shouldn't need it.
 
Back
Top