Lord Sauron schreef:
> Okay, here's where I've isolated the problem to.
<snip>
.>
> I know that it correctly compiles the kernel. I put a new name for
> the new kernel (test1) to try and ID it
<snip>
> # make install
>
> Sticks it into /boot. /boot now reads
>
> System.map config.old
> System.map-2.6.15-gentoo-r1 grub
> System.map-2.6.15-gentoo-r1.old initramfs-genkernel-x86-2.6.15-gentoo-r5
> System.map-2.6.15-gentoo-r1test1 kernel-genkernel-x86-2.6.15-gentoo-r5
> System.map-2.6.15-gentoo-r1test1.old lost+found
> System.map.old vmlinuz
> boot vmlinuz-2.6.15-gentoo-r1
> config vmlinuz-2.6.15-gentoo-r1.old
> config-2.6.15-gentoo-r1 v mlinuz-2.6.15-gentoo-r1test1
> config-2.6.15-gentoo-r1.old vmlinuz-2.6.15-gentoo-r1test1.old
> config-2.6.15-gentoo-r1test1 vmlinuz.old
> config-2.6.15-gentoo-r1test1.old
>
> Not terribly exciting. However, I went to /boot/grub/menu.lst and it
> reads as such:
>
> localhost boot # cat ./grub/menu.lst
> default 0
> timeout 7
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title=Gentoo Linux
> root (hd0,0)
> kernel /kernel-genkernel-x86-2.6.15-gentoo-r5 root=/dev/ram0
> init=/linuxrc ramdisk=8192 real_root=/dev/hda3
> initrd /initramfs-genkernel-x86-2.6.15-gentoo-r5
>
> The most concerning part is the last three lines. For any kernel, it
> appears to demand the kernel itself. If you'll refer back to # ls
> /boot then you'll notice that kernel-2.6.15-gentoo-r1test1 isn't
> there.
???? Yes it is:
vmlinuz-2.6.15-gentoo-r1test1
>Nor is the initrd. I don't know where they might be, or if
> they're not there then how to generate them.
No, the initrd isn't there; you apparently made your previous kernel
with genkernel, which creates an initrd, and you further do not have
splashutils installed (which would/can also make an initrd to contain
the bootsplash images).
Manual kernel installation using 'make install' copies the bzImage (the
kernel itself) to /boot/, and names it
vmlinuz-kernel.version-extra_version_if_used.
Make install also copies the "helpful but not strictly necessary"
.config and system.map files to /boot/ adding the version to the end to
distinguish it from other supplemental files for other kernels, and
creates two symlinks to the current and newly-installed kernel:
vmlinuz -- links to the newly installed kernel
vmlinuz.old -- links to the current kernel that the newly-installed
kernel is replacing.
Similar symlinks are also created for the .config and system.map files
for the respective kernels.
What this means is that you can just tell grub that the first item on
the list should load 'vmlinuz' (which is going to be a link to the most
recently installed kernel), and the second entry should load vmlinuz.old
(which is a link to the previous kernel to the most newly installed, in
case of problems). If you have even more old kernels, they can always be
listed by the full kernel version.
In any case, it seems to me that you basically need to create a new
entry for the test kernel; just copy the current entry, paste it above
the other one, then delete the following relevant portions:
1. Change 'kernel /kernel-genkernel-x86-2.6.15-gentoo-r5 root=/dev/ram0'
to read kernel /vmlinuz root=/dev/ram0 (not sure about the 'root= part;
/dev/ram0 seems a bit weird to me but perhaps this is in some way
functional for your particular setup. I have no experience with
genkernel, which this setting looks like to me, but maybe somebody can
confirm that. If it is from genkernel, root= should be the partition of
the root filesystem, on my system, this setting is root=/dev/hda5)
2. delete.... everything else, apparently. I can see that most of the
entry is generated by/related to genkernel.
Here, for reference is my grub entry for my manually compiled kernels
(never used genkernel, as I said):
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,1)
# kernel /vmlinuz-version ro root=/dev/hda5
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,1)/grub/grub-livecd2.xpm.gz
title Gentoo_current (2.6.15-gentoo-r7mga)
root (hd0,1)
kernel /vmlinuz ro quiet root=/dev/hda5
video=matroxfb:vesa:0x11B,depth:32 splash=silent,theme:livecd-2005.1
CONSOLE=/dev/tty1
title Gentoo_prev (2.6.15-gentoo-r7)
root (hd0,1)
kernel /vmlinuz.old ro root=/dev/hda5
video=matroxfb:vesa:0x11B:ywrap,pmipal,mtrr:3,[EMAIL PROTECTED]
splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1
title Failsafe_current
root (hd0,1)
kernel /vmlinuz ro root=/dev/hda5
video=vesafb:ywrap,pmipal,mtrr:3,[EMAIL PROTECTED] emergency
If you ignore all the video= settings, as you should, since they are to
provide the bootsplash, which is irrelevant here, the relevant entry
that allows me to boot is only
title Gentoo_current (2.6.15-gentoo-r7mga)
root (hd0,1)
kernel /vmlinuz ro quiet root=/dev/hda5
title Gentoo_prev (2.6.15-gentoo-r7)
root (hd0,1)
kernel /vmlinuz.old ro root=/dev/hda5
>>
>>>> Sorry, what does YMMV mean?
>>> Those are the resources that I use for that kind of questions:
>>>
>>> http://en.wikipedia.org/wiki/YMMV
>>> http://www.urbandictionary.com/define.php?term=ymmv
>> You can also emerge wtf.
>
> I assume wtf will tell me what wtf stands for... is the last letter
> representative of a forbidden word, by any chance?
Yes, it will, and yes it is.
On the web, you can also try acronymfinder.com, which has most everything.
HTH (look it up; wtf hth :-) )
Holly
--
gentoo-user@gentoo.org mailing list
