Gentoo!

Originally posted by burns
hmm, well, lilo's installed, it runs when I reboot and says starting "gento....................." then just stops just showing the lilo Boot Menu:(. The fact it says starting gentoo would make me think it's a problem with gentoo rather than lilo though...
Click to expand...

at least we have a boot loader working now!

the prob here is probably lilo's config. but ive never used it.

post your config up and i'll check it against documentation

also you have to run lilo after editing the lilo config i think.

# /sbin/lilo
 
Originally posted by Mpemba Effect
eurhrrr! ACPI! Yuk! What do you want that for? :D
Click to expand...

haha. well in windows i set up suspend to ram and it worked nicely and was very useful for me. i have a very small room and window, and a pc that kicks out a lot of heat. so i could suspend rather than using a screensaver, yet have my desktop up in the same time it would take for my monitor to turn on, but without a tonne of heat being produced.

also i like being able to hit the power button to shutdown.

but at the moment acpi looks rather dodgy, but i havnt delved in much yet.
 
Originally posted by riven
also you have to run lilo after editing the lilo config i think.

# /sbin/lilo
Click to expand...
I got that after the first reboot;)

This is what mine looks like but without the comments

boot=/dev/hda # Install LILO in the MBR
prompt # Give the user the chance to select another section
timeout=50 # Wait 5 (five) seconds before booting the default section
default=gentoo # When the timeout has passed, boot the "gentoo" section

# For non-genkernel users
image=/boot/kernel-2.6.7-gentoo-r11
label=gentoo # Name we give to this section
read-only # Start with a read-only root. Do not alter!
root=/dev/hda3 # Location of the root filesystem
 
Originally posted by burns
I got that after the first reboot;)

This is what mine looks like but without the comments

boot=/dev/hda # Install LILO in the MBR
prompt # Give the user the chance to select another section
timeout=50 # Wait 5 (five) seconds before booting the default section
default=gentoo # When the timeout has passed, boot the "gentoo" section

# For non-genkernel users
image=/boot/kernel-2.6.7-gentoo-r11
label=gentoo # Name we give to this section
read-only # Start with a read-only root. Do not alter!
root=/dev/hda3 # Location of the root filesystem
Click to expand...
It should look like
Code: 
boot=/dev/hda
prompt
timeout=50
default=gentoo

image=/boot/kernel-2.6.7-gentoo-r11
  label=gentoo
  read-only
  root=/dev/hda3
you do not want to put int he genkernel part since you're not using genkernel.
 
I've done the corrections riven suggested, but it's still hanging at the lilo screen after displaying starting gentoo..............
 
I've just emerged gentoo-dev-sources to take a look at your .config again. But still I can't see anything wrong with it. Apart from may be
Code: 
[*] Use 4Kb for kernel stacks instead of 8Kb
under kernel hacking.

I've tried 4k stacks before and it was a no go
Code: 
 ll
total 7314
-rw-r--r--  1 root root 1577285 Jul 30 21:39 bzImage
-rw-r--r--  1 root root 1405847 May 19 15:29 bzImage-2.6.6-love4
[color=deeppink]-rw-r--r--  1 root root 1406775 May 21 08:53 bzImage-2.6.6-love4.st4[/color]
-rw-r--r--  1 root root 1539380 Jul 24 08:17 bzImage.dfi
-rw-r--r--  1 root root 1508919 Jun 28 16:29 bzImage.smp
drwxr-xr-x  2 root root    1024 Jun 28 11:25 grub
drwx------  2 root root   12288 May 19 15:25 lost+found
Still I'm not sure if it's a kernel problem, normally when a kernel dies, it goes dramatically with a kernel panic.
 
You must log in or register to reply here.
Back
Top Bottom