On Dienstag, 7. August 2007, cscscscscs cscscscscs wrote: > Hi folk, > > First of all sorry if my English is not perfect. > > 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. > > > '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. > > 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. > > (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.) > > > 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 >
so you copied the grub.conf from the cd? or does genkernel this atrocity? If you don't use an initrd (and if you don't use a raid-setup there is imho no good reason to do so), make it look like this: kernel (hd1,4)/boot/vmlinuz root=/dev/sdb6 replace vmlinuz with whatever your kernel is called. Don't use genkernel - make all modules_install install is IMHO way better. > > P.S.: Please don't ask me for repartition my hard drive. I hope that a > simplier solution exist. if you boot from the second harddisk, grub may get confused, so instead of root (hd0,0) kernel (hd0,0)/boot/vmlinuz root=/dev/sda3 nmi_watchdog=0 (as an example) root (hd1,0) kernel (hd1,0)/boot/vmlinuz root=/dev/sda3 nmi_watchdog=0 may help. (or in your case, instead of a 1 a 0), play around with it, at somepoint it might work ;) ) -- [EMAIL PROTECTED] mailing list
