I'm in the middle of stage 1 of a gentoo install...
 

...please pray for me. I'll add to this thread as things go wrong and I have to ask questions.

Installing gentoo is not exactly rocket science, just follow the install guide and its done. Just takes time.

I'm not used to things compiling properly first time, stage 1 went with no problems though (wonders will never cease) and stage 2 is under way.

If this actually works first time the folks at Gentoo deserve a medal :)

One question though, would you advise using the gentoo kernel or a kernel.org one? Am I right in thinking that Gentoo tend to update their kernel pretty much as a new stable version is released?

:confused: :down:

YOU = VERREH USEFUL

It was never gonna happen :(

Okay, I now get a warning that my partition table or superblock is corrupt on boot (fsck).

Filesystem size according to superblock is 104391, partition table (i.e. physical size) says 96358.

Lilo is reporting an error because of different drive geometries for BIOS functions 0x08 and 0x48. 0x08 is reporting the LBA geometry (as set in the BIOS) and 0x48 is reporting the geometry as it would be set for non-LBA use. Setting it to non-LBA in the BIOS causes the kernel to get pissed and tell me it should be set to the LBA settings.

This is all on /dev/hda1 (/boot) so I don't understand, it boots and works fine but the warnings are worrying me as they sound like they have the potential to kinda screw everything up real easily.

Any ideas anyone? If I try to run fsck (or e2fsck) I get errors when accessing past inode 98309 out of 104391 but I have no idea how to fix it (or why it doesn't give an error at 96359).

I managed a gentoo install without a problem, its now running my 'test' server for the PA Tools, and a few other things. I used the Gentoo-sources kernel - seems to be running well... only problem i had was with compiling the kernel - moaning about not being able to find some functions or other, i solved that by disabling one of the modules (to do with the chipset - SiS something or other)

Okay, I copied /boot to a temp directory, repartitioned, rebuilt the fs, copied the data back, and it worked \0/

Now all I have to do is work out why lilo is giving me an error about disk geometry...

ditto :rolleyes: :up:

maybe its lost stitch

Can't help you there, i used GRUB and it all worked first time \o/

KDE has been compiling since Sunday (still going when I left for work this morning) and I think I forgot to set USE="cups". If I did I'll have re re-emerge it and that sucks :(