Gentoo!

Originally posted by burns
H'okay, I have /boot/grub/grub.conf open in front of me and it says:
Code:
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.7-r11
root (hd0,0)
kernel /kernel-2.6.7-gentoo-r11 root=/dev/hda3 vga=788
After you compiled your kernel did you copy it over to /boot as "kernel-2.6.7-gentoo-r11" or did you leave it as "bzImage"?
 
Originally posted by Mpemba Effect
After you compiled your kernel did you copy it over to /boot as "kernel-2.6.7-gentoo-r11" or did you leave it as "bzImage"?

if he used genkernel which i think he did because he hasnt asked about kernel compiling then "kernel-2.6.7-gentoo-r11" would be right i think
 
Originally posted by riven
Code:
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.7-r11
root (hd0,0)
kernel [B](hd0,0)/boot[/B]/kernel-2.6.7-gentoo-r11 root=/dev/hda3 vga=788

you missed a bit, see bold ^^^^^^^^^

i assume the name of that kernel is correct
I checked the name of the kernel, thats okay, the bit you've got in bold there isn't in the handbook, but it does make sense...
 
Originally posted by riven
Code:
default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz
title=Gentoo Linux 2.6.7-r11
root (hd0,0)
kernel [color=deeppink](hd0,0)/boot[/color]/kernel-2.6.7-gentoo-r11 root=/dev/hda3 vga=788

you missed a bit, see bold ^^^^^^^^^

i assume the name of that kernel is correct
No, thats how it's done the old way and it will not work on recent installs. How burns has it is correct now. That confused the hell out of me when I reinstalled my server, I used my old working config which no longer worked.
 
Originally posted by burns
I checked the name of the kernel, thats okay, the bit you've got in bold there isn't in the handbook, but it does make sense...

i seem to have a different manual to you three because its in mine!
 
Originally posted by Mpemba Effect
No, thats how it's done the old way and it will not work on recent installs. How burns has it is correct now. That confused the hell out of me when I reinstalled my server, I used my old working config which no longer worked.

eh? mine are like this gentoo install is about 6 weeks old :confused:
 
Originally posted by riven
if he used genkernel which i think he did because he hasnt asked about kernel compiling then "kernel-2.6.7-gentoo-r11" would be right i think
No, I compliled my own kernel, so we can expect some problems with that later:p. I did copy it over though, there is a file in /boot called kernel-2.6.7-gentoo-r11
 
Originally posted by Mpemba Effect
What did you format the /boot partition as? and did you compile support for that filesystem in the kernel? Double check!
How do I do that sorry? I think I formatted it as ext3, and I think I compiled support for it, but how can I check?
 
Originally posted by Mpemba Effect
No, thats how it's done the old way and it will not work on recent installs. How burns has it is correct now. That confused the hell out of me when I reinstalled my server, I used my old working config which no longer worked.

im going to do an experiment and take the bit you dont think should be there out, and try booting from it.

back in a few mins
 
Originally posted by riven
eh? mine are like this gentoo install is about 6 weeks old :confused:
Really? Weird, I did a gentoo install in June and the config had changed. If I used the old way with "kernel (hd0,0)/boot/bzImage" it would boot grub but the image would be corrupted and in black and white, an error regarding a failure to find the kernel follows. This baffled me for ages (since the grub.conf was copied over from the old install) and I had to read the manual :p I made the change and it solved it.
 
Right, my /boot/config-2.6.7-gentoo-r11 which I backed up contains CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y

so I think thats a good thing...
 
Originally posted by riven
im going to do an experiment and take the bit you dont think should be there out, and try booting from it.

back in a few mins

your way works fine too. perhaps they decided to support both methods in a more recent version to stop confusion?
 
Originally posted by riven
im going to do an experiment and take the bit you dont think should be there out, and try booting from it.

back in a few mins
This was what was really weird, on my old install I'm pretty certain grub was up to date. I'm sure on the fresh install the grub version was identical however I'm unsure on why our original line doesn't work.
 
you did put grub on you mbr too didnt you?

grub> root (hd0,0) (your boot partiiton)
grub> setup (hd0) (the mbr)

i missed that once and it took me ages to figure it all out
 
Originally posted by Mpemba Effect
This was what was really weird, on my old install I'm pretty certain grub was up to date. I'm sure on the fresh install the grub version was identical however I'm unsure on why our original line doesn't work.

i have 0.94, the latest one in portage
 
Originally posted by riven
you did put grub on you mbr too didnt you?

grub> root (hd0,0) (your boot partiiton)
grub> setup (hd0) (the mbr)

i missed that once and it took me ages to figure it all out
Yeah grub is there, it'll start loading grub, then it gives error 2 during stage 1.5...
Of error 2 the grub manual says:
2 : Bad file or directory type
This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.
 
Originally posted by burns
How do I do that sorry? I think I formatted it as ext3, and I think I compiled support for it, but how can I check?
Ooo that uncertainty doesn't sound too good. You can check if you've compiled it in by
Code:
cd /usr/src/linux
make menuconfig
Go to "filesystems" make sure "Ext3 journalling file system support" is enabled.

You can check what filesystem something is by typing
Code:
cat /proc/self/mounts
when it is mounted. Also you should have made entered the filesystem type in /etc/fstab.
 
ok, hda1, my boot partition is ext3 according to cat /proc/self/mounts.
however my /usr/src folder is empty:confused:. I can't see this being a good thing.
 
Back
Top Bottom