On Fri, Jun 3, 2011 at 10:59 AM, Kevin J. Cummings <cummings@kjchome.homeip.net> wrote:
On 06/02/2011 10:31 PM, GeeKer Wang wrote:
> On Thu, Jun 2, 2011 at 9:29 PM, Kevin J. Cummings
>     OK, so while looking at the live system chrooted to your system, what is
>     the response to:
>
>     rpm -q kernel
>
>     Let's find out if the proper kernel got installed.  If so, then we'll
>     have a look at your /etc/grub.conf (which is just a symlink to:
>     /boot/grub/grub.conf).  And then we'll try and figure out how to install
>     it by running grubby by hand....
>
> There is no fc15 kernel, only
>      kernel-2.6.35.12-88.fc14.i686
>      kernel-2.6.35.12-90.fc14.i686
>      kernel-2.6.35.13-91.fc14.i686

OK, so the f15 kernel never got installed.  That would bring into
question a whole raft of other potential problems that you will probably
need to clean uop from as well....

>     Are you 100% sure that preupgrade didn't stop prematurely with some sort
>     of error message?
>
> It halted halfway because of installing openjpeg-devel. I renamed
> related files and preupgrade continued without other problem.

Except that it seemed to miss installing the kernel....

>     If it did not get installed, it should be easy enough to install one by
>     hand (with RPM) and see if it installs without any errors (and correctly
>     modifies your /etc/grub.conf file).  If it requires dependencies to
>     install, then you will have other problems.
>
>   When I tried "rpm -ivh kernel-2.6.38.6-fc15.i686.rpm", it failed with
> "grubby fatal error: unable to find a suitable template". But it created
> some files(eg. vmlinuz-xxx-fc15, initramfs-xxx.img) in /boot and
> /lib/modules. However, grub-install didn't recognize these files.

We can always add the proper lines to /etc/grub.conf by hand if we have
to....

What is the contents of your current /etc/grub.conf file?
What and where are the f15 kernel files?
       (you are looking for at least a vmlinuz- file and possibly
         an initramfs- file and possibly a System.map- file as well)

I have the following on my botched f15 upgrade:

/boot
 config-2.6.35.12-90.fc14.i686  efi
initramfs-2.6.35.12-90.fc14.i686.img  initrd-plymouth.img
 System.map-2.6.35.13-91.fc14.i686  vmlinuz-2.6.35.12-90.fc14.i686
 config-2.6.35.13-91.fc14.i686  elf-memtest86+-4.10
initramfs-2.6.35.13-91.fc14.i686.img  memtest86+-4.10
 System.map-2.6.38.6-27.fc15.i686   vmlinuz-2.6.35.13-91.fc14.i686
 config-2.6.38.6-27.fc15.i686   grub
initramfs-2.6.38.6-27.fc15.i686.img   System.map-2.6.35.12-90.fc14.i686
 upgrade                            vmlinuz-2.6.38.6-27.fc15.i686

and my grub.conf contains this entry for f15 (which boots for me):

title Fedora (2.6.38.6-27.fc15.i686)
       root (hd0,0)
       kernel /boot/vmlinuz-2.6.38.6-27.fc15.i686 ro
root=UUID=f3299b81-9fc4-46eb-9189-a79591e894a1 rd_NO_LUKS rd_NO_LVM
rd_NO_MD rd_NO_DM vga=0x123 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16
KEYBOARDTYPE=pc KEYTABLE=us noiswmd
       initrd /boot/initramfs-2.6.38.6-27.fc15.i686.img

You will need to change the UUID to match your disk, and whether or not
you need all of the boot options that I have, you can compare to your
f14 kernel entries in your grub.conf file.  All of the options on my f15
kernel line appear verbatim on my f14 kernel lines.  And my test system
is currently booted in f15 (or some subset of it.  B^)

I have these files in /boot, and I tried to revise entry in grub.conf. Unfortunately, It complains cannot find /proc/cmdline when booting...
--



--
Bob