On Tuesday 07 August 2007 20:40, cscscscscs cscscscscs wrote:

> First of all sorry if my English is not perfect.

No worries, neither is mine.  ;-)

> I become a little bit upset sucking installing Gentoo Linux throughout 3
> days. There was several errors during the install process (networkless,
> installer-dialog), so I was beginning to be afraid of memory-module errors,
> motherboard failure etc. I ran memory and other tests: everything is OK
> with my computer. However, the install succeeded only for the sixth time.

It took me 3 times to install Gentoo from a stage 1 and I was not getting any 
overheating problems with my PC.  If you try to install it on a laptop, or a 
PC which is has cooling fans covered in fluff and dust in the middle of the 
summer, you may well be experiencing overheating problems.

> 'Now' the main problem is that GRUB returns with error code 15. I've read
> the documentation: http://www.gentoo.org/doc/en/grub-error-guide.xml ;
> however it didn't help. The kernel image is where it must be.

Grub error 15 means that the drive and partition are correct, but the file in 
question (your kernel image) is not found.

In the first instance I can think of two possibilities:

1. You've made a typographic error when you entered the name of your kernel 
(kernel-genkernel-x86-2.6.19-gentoo-r5) in grub.conf.  This is easy to check.  
Mount boot with a live CD and ls the contents of it.  Then check the name of 
the kernel character-by-character.

2. When you installed your kernel (copied your kernel image in /boot) you had 
not mounted your /boot partition.  This means that all your /boot fs has been 
installed in your / partition.  It is also easy to check.  Unmount /boot and 
then ls the contents of it.  If you can see a kernel image then this is your 
problem.  Mount /dev/sdb5 on a different mount point (e.g. mkdir /mnt/test) 
and then cp -a /boot /mnt/test.  List everything under /mnt/test and compare 
with all files and directories under /boot.  As long as access rights are 
correct for each file and directory you can rm -Rf /boot/* 

> I have got two HDD-s with SATA interface. My system is installed on sdb.
> Here are my partitions, beginning from the 0. cylinder:
>
> First:           sdb5  ext2 /boot
> Second:       sdb6  ext3 /
> Third:           sdb7  ext3 /home
> Fourth:        sdb2  swap
>
> As other Linux distributions boots fine from logical partitions I think
> this shouldn't be the reason.

That's right.  This is not the reason.

> (After sdb2 there are 2 more primary data partition (with no influence to
> the system)).
>
> I think GRUB is in the MBR of sdb. (One thing is 100%: the MBR of sda
> remains untouched, however the installer hasn't asked where to install it.)

If Grub is in the MBR of sdb then it must be chainloaded from the MBR of sda, 
or assuming that you have Grub also installed in the MBR of sda then copy 
your grub.conf entry to the /boot filesystem that the MBR of sda boots from.

> grub.conf:
>
> default 0
> timeout 30
> splashimage=(hd1,4)/grub/splash.xpm.gz
> title=Gentoo Linux
> root (hd1,4)
> kernel /kernel-genkernel-x86-2.6.19-gentoo-r5 root=/dev/ram0 init=/linuxrc
> ramdisk=8192 real_root=/dev/sdb6  doscsi
> initrd /initramfs-genkernel-x86-2.6.19-gentoo-r5
>
>
> Everything looks to be good, but I have no idea what does
> root=/dev/ram0 init=/linuxrc ramdisk=8192
> mean and why appears 'ramdisk'.

Google for initrd
>
>
> Reading through many pages about Gentoo linux, and it's "power", "freedom",
> "choices",  package management ...etc. this distribution looks like very
> fine.

You'll realise how fine it is when you learn how to fix it without 
reinstalling.  Gentoo has (almost) self-healing properties . . .  :-)

> I'm now totally depressed.... The last thing for the rest is reading the
> 100 pages documentation of GRUB. It's very complicated for as an 'beginning
> difficult'.

You can try info grub - it is a bit more condensed (but I am not sure if it is 
up to date).

Hope this helps.
-- 
Regards,
Mick

Attachment: pgpeDyvG0h5y3.pgp
Description: PGP signature

Reply via email to