Gentoo!

Mpemba Effect · 5 Aug 2004 at 12:56

I've taken a look through (although I did load it up with a 2.6.6 menuconfig) but it looks like you have everything that you need in there (and some). I'm sure riven can double check if i've missed anything

I'd give lilo a go. So

Code:

mount /dev/hda3 /mnt/gentoo
mount /dev/hda1 /mnt/gentoo/boot
swapon /dev/hda2
mount -t proc proc /mnt/gentoo/proc
chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile
cp /boot/grub/grub.conf /tmp
[color=red]cd /boot
rm -R *[/color]
emerge lilo
emerge -C grub
cp /usr/src/linux/arch/i386/boot/bzImage /boot/kernel-2.6.7-gentoo-r11

edit your /etc/lilo.conf as described in section "10.c. Alternative: Using LILO" of the handbook.

WARNING: Beware of the red parts above, make sure you are in /boot and not in any other directory else you will delete the wrong stuff.

burns · 5 Aug 2004 at 12:59

Cheers for tidying that up, I wasn't sure if I had to uninstal grub first.

Mpemba Effect · 5 Aug 2004 at 13:01

You don't have to lilo and grub will add stuff into /boot and you'll end up having a whole mess of stuff in there.

riven · 5 Aug 2004 at 13:02

# CONFIG_DEVPTS_FS_XATTR is not set

[ ] /dev/pts file system for Unix98 PTYs
(Uncheck this, it is not needed unless you use a 2.6 kernel)

not entirely sure what it does but thats from the gentoo manual, and this is a 2.6. but it shouldnt affect grub or lilos startup, so we shall get that far 1st and see if anything needs doing about this.

Mpemba Effect · 5 Aug 2004 at 13:10

Originally posted by riven
# CONFIG_DEVPTS_FS_XATTR is not set

not entirely sure what it does but thats from the gentoo manual, and this is a 2.6. but it shouldnt affect grub or lilos startup, so we shall get that far 1st and see if anything needs doing about this.

CONFIG_DEVPTS_FS_XATTR is not /dev/pts file system for Unix98 PTYs. It's I assume extended attributes. The newer version of 2.6 doesn't even have that option to disable anymore since it's essential to have it else terminal emulation like xterms won't work properly.

burns · 5 Aug 2004 at 13:20

Code:
Originally posted by Mpemba Effect
I've taken a look through (although I did load it up with a 2.6.6 menuconfig) but it looks like you have everything that you need in there (and some). I'm sure riven can double check if i've missed anything

I'd give lilo a go. So

Code:

mount /dev/hda3 /mnt/gentoo mount /dev/hda1 /mnt/gentoo/boot swapon /dev/hda2 mount -t proc proc /mnt/gentoo/proc chroot /mnt/gentoo /bin/bash env-update source /etc/profile cp /boot/grub/grub.conf /tmp [color=red]cd /boot rm -R *[/color] emerge lilo emerge -C grub cp /usr/src/linux/arch/i386/boot/bzImage /boot/kernel-2.6.7-gentoo-r11

edit your /etc/lilo.conf as described in section "10.c. Alternative: Using LILO" of the handbook.

WARNING: Beware of the red parts above, make sure you are in /boot and not in any other directory else you will delete the wrong stuff.

When I do the "cp /boot/grub/grub.conf /tmp", it says it can't find the folder, I'm guessing it should be /mnt/gentoo/boot/grub/grub.conf having mounted /dev/hda1 to mount /dev/hda1 /mnt/gentoo/boot?

riven · 5 Aug 2004 at 13:24

Originally posted by Mpemba Effect
CONFIG_DEVPTS_FS_XATTR is not /dev/pts file system for Unix98 PTYs. It's I assume extended attributes. The newer version of 2.6 doesn't even have that option to disable anymore since it's essential to have it else terminal emulation like xterms won't work properly.

ah, that would make sense

Mpemba Effect · 5 Aug 2004 at 13:25

Originally posted by burns
When I do the "cp /boot/grub/grub.conf /tmp", it says it can't find the folder, I'm guessing it should be /mnt/gentoo/boot/grub/grub.conf having mounted /dev/hda1 to mount /dev/hda1 /mnt/gentoo/boot?

No since you've chrooted in. Unless you've missed out the whole

Code:

chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile

section

Deadly Ferret · 5 Aug 2004 at 13:35

I'm back, with what I hope is a final problem.

I finally got around to creating grub.conf late last night, and all I had to do was copy from the workbook:

Code:

default 0
timeout 30
splashimage=(hd0,0)/grub/splash.xpm.gz

title=Gentoo Linux 2.4.26-r6
root (hd0,0)
kernel /kernel-2.4.26-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3
initrd /initrd-2.4.26-gentoo-r6

However, there was the problem that "kernel-2.4.26-gentoo-r6" obviously needs to be adjusted to whatever I have instead. Unfortunately, I can remember that it's 2.6.7, but no more. I half-heartedly tried putting in "kernel-2.6.7-gentoo-r6", but as I suspected that was not correct and when using Grub at startup, it comes up with an error on the penultimate line, which is the first line that filename is mentioned (where it matters).

Does anyone know a way I can obtain the necessary information to edit the .conf accordingly please?

burns · 5 Aug 2004 at 13:39

ok, just setting up the lilo.conf...

paradigm · 5 Aug 2004 at 13:40

Code:

ls -l /usr/src/linux

Should show you what kernel you emerged.

riven · 5 Aug 2004 at 13:44

Code:
Originally posted by Deadly Ferret
I'm back, with what I hope is a final problem.

I finally got around to creating grub.conf late last night, and all I had to do was copy from the workbook:

Code:

default 0 timeout 30 splashimage=(hd0,0)/grub/splash.xpm.gz title=Gentoo Linux 2.4.26-r6 root (hd0,0) kernel /kernel-2.4.26-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 initrd /initrd-2.4.26-gentoo-r6

However, there was the problem that "kernel-2.4.26-gentoo-r6" obviously needs to be adjusted to whatever I have instead. Unfortunately, I can remember that it's 2.6.7, but no more. I half-heartedly tried putting in "kernel-2.6.7-gentoo-r6", but as I suspected that was not correct and when using Grub at startup, it comes up with an error on the penultimate line, which is the first line that filename is mentioned (where it matters).

Does anyone know a way I can obtain the necessary information to edit the .conf accordingly please?

the current kernel in portage is "kernel-2.6.7-gentoo-r11" (to fit in with your grub)

but to check do this:

chroot back in
mount /boot
then:
cd /boot
ls

that should print out everything in your boot directory

then update grub.conf in /boot/grub/grub.conf

Mpemba Effect · 5 Aug 2004 at 13:44

Code:
Originally posted by Deadly Ferret
I'm back, with what I hope is a final problem.

I finally got around to creating grub.conf late last night, and all I had to do was copy from the workbook:

Code:

default 0 timeout 30 splashimage=(hd0,0)/grub/splash.xpm.gz title=Gentoo Linux 2.4.26-r6 root (hd0,0) kernel /kernel-2.4.26-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 initrd /initrd-2.4.26-gentoo-r6

However, there was the problem that "kernel-2.4.26-gentoo-r6" obviously needs to be adjusted to whatever I have instead. Unfortunately, I can remember that it's 2.6.7, but no more. I half-heartedly tried putting in "kernel-2.6.7-gentoo-r6", but as I suspected that was not correct and when using Grub at startup, it comes up with an error on the penultimate line, which is the first line that filename is mentioned (where it matters).

Does anyone know a way I can obtain the necessary information to edit the .conf accordingly please?

Code:

ls -l /boot

will tell you whats in /boot. From there you can figure out which ones your kernel. Proberbly called "kernel-2.6.7-gentoo-r11 or something. Remember you'll need change both the

Code:

kernel /[color=deeppink]kernel-2.4.26-gentoo-r6[/color] root=/dev/ram0 init=/linuxrc ramdisk=8192 
initrd /[color=deeppink]initrd-2.4.26-gentoo-r6[/color]

parts of grub.conf

riven · 5 Aug 2004 at 13:46

Code:
Originally posted by paradigm

Code:

ls -l /usr/src/linux

Should show you what kernel you emerged.

thats not nessicarily the kernel images name though. if you compile one yourself you will get an image called bzImage by default. thats why you should check your /boot for the image, not the /usr/src/linux.

Mpemba Effect · 5 Aug 2004 at 13:47

Originally posted by riven
thats not nessicarily the kernel images name though. if you compile one yourself you will get an image called bzImage by default. thats why you should check your /boot for the image, not the /usr/src/linux.

Personally I just leave mine as bzImage. If I build a new kernel I just rename the old one see?

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
-rw-r--r--  1 root root 1406775 May 21 08:53 bzImage-2.6.6-love4.st4
-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

riven · 5 Aug 2004 at 13:51

i do a similar thing too

Code:

lrwxrwxrwx  1 root root       1 Jul  8 17:57 boot -> .
-rw-r--r--  1 root root 2097860 Aug  3 22:21 bzImage
-rw-r--r--  1 root root 1991745 Aug  3 22:16 bzImage.bak
-rw-r--r--  1 root root 1913287 Jul 11 16:13 bzImage.mm
-rw-r--r--  1 root root 2150270 Jul 15 18:18 bzImage.splash
-rw-r--r--  1 root root 1926267 Jul 26 14:56 bzImage.test
drwxr-xr-x  2 root root    1024 Jul  9 23:31 grub
-rw-r--r--  1 root root  101494 Jul 15 18:18 initrd-1280x1024
drwx------  2 root root   12288 Jul  8 17:40 lost+found

Mpemba Effect · 5 Aug 2004 at 13:56

Code:

-rw-r--r--  1 root root 2097860 Aug  3 22:21 bzImage

Big Kernels R' Us

burns · 5 Aug 2004 at 13:56

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...

riven · 5 Aug 2004 at 14:00

Code:
Originally posted by Mpemba Effect

Code:

-rw-r--r-- 1 root root 2097860 Aug 3 22:21 bzImage

Big Kernels R' Us

ive been messing around with acpi and few other bits, which beefs it up a bit

Mpemba Effect · 5 Aug 2004 at 14:02

Originally posted by riven
ive been messing around with acpi and few other bits, which beefs it up a bit

eurhrrr! ACPI! Yuk! What do you want that for?