new kernel kernel-2.6.24-0.107.rc5.git3.fc9 does not boot

[Antonio Olivares]

[olivares@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.24-0.83.rc5.fc9 #1 SMP
Tue Dec 11 12:04:08 EST 2007 i686 i686 i386 GNU/Linux
[olivares@localhost ~]$ rpm -qa kernel
kernel-2.6.24-0.80.rc4.git6.fc9
kernel-2.6.24-0.107.rc5.git3.fc9
kernel-2.6.24-0.83.rc5.fc9
kernel-2.6.24-0.81.rc4.git7.fc9
[olivares@localhost ~]$ su -
Password: 
[root@localhost ~]# cat /boot/grub/grub.conf
# 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,2)
#          kernel /vmlinuz-version ro
root=/dev/VolGroup01/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.24-0.83.rc5.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.83.rc5.fc9 ro root=LABEL=/
rhgb quiet
	initrd /initrd-2.6.24-0.83.rc5.fc9.img
title Fedora (2.6.24-0.81.rc4.git7.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.81.rc4.git7.fc9 ro
root=LABEL=/ rhgb quiet
	initrd /initrd-2.6.24-0.81.rc4.git7.fc9.img
title Fedora (2.6.24-0.80.rc4.git6.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.80.rc4.git6.fc9 ro
root=LABEL=/ rhgb quiet
	initrd /initrd-2.6.24-0.80.rc4.git6.fc9.img
title Microsoft Windows Vista Home Edition
	rootnoverify (hd0,1)
	chainloader +1
[root@localhost ~]# 


     
____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

[Antonio Olivares]

--- Antonio Olivares <olivares14031(a)yahoo.com&gt; wrote:

>  
>  [olivares@localhost ~]$ uname -a
>  Linux localhost.localdomain 2.6.24-0.83.rc5.fc9 #1
>  SMP
>  Tue Dec 11 12:04:08 EST 2007 i686 i686 i386
>  GNU/Linux
>  [olivares@localhost ~]$ rpm -qa kernel
>  kernel-2.6.24-0.80.rc4.git6.fc9
>  kernel-2.6.24-0.107.rc5.git3.fc9
>  kernel-2.6.24-0.83.rc5.fc9
>  kernel-2.6.24-0.81.rc4.git7.fc9
>  [olivares@localhost ~]$ su -
>  Password: 
>  [root@localhost ~]# cat /boot/grub/grub.conf
>  # 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,2)
>  #          kernel /vmlinuz-version ro
>  root=/dev/VolGroup01/LogVol00
>  #          initrd /initrd-version.img
>  #boot=/dev/sda
>  default=0
>  timeout=5
>  splashimage=(hd0,2)/grub/splash.xpm.gz
>  hiddenmenu
>  title Fedora (2.6.24-0.83.rc5.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.83.rc5.fc9 ro root=LABEL=/
>  rhgb quiet
>  	initrd /initrd-2.6.24-0.83.rc5.fc9.img
>  title Fedora (2.6.24-0.81.rc4.git7.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.81.rc4.git7.fc9 ro
>  root=LABEL=/ rhgb quiet
>  	initrd /initrd-2.6.24-0.81.rc4.git7.fc9.img
>  title Fedora (2.6.24-0.80.rc4.git6.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.80.rc4.git6.fc9 ro
>  root=LABEL=/ rhgb quiet
>  	initrd /initrd-2.6.24-0.80.rc4.git6.fc9.img
>  title Microsoft Windows Vista Home Edition
>  	rootnoverify (hd0,1)
>  	chainloader +1
>  [root@localhost ~]# 
>  
>  
>       
____________________________________________________________________________________
>  Never miss a thing.  Make Yahoo your home page. 
>  http://www.yahoo.com/r/hs
>  
>  --  
This happens on both machines.  

[root@localhost ~]# cat /boot/grub/grub.conf
# 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,2)
#          kernel /vmlinuz-version ro
root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
#   kernel /vmlinuz-2.6.20-1.3040.fc7 ro
root=/dev/VolGroup00/LogVol00 removed -> rhgb quiet
#
default=0
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.24-0.83.rc5.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.83.rc5.fc9 ro
root=/dev/VolGroup00/LogVol00 
	initrd /initrd-2.6.24-0.83.rc5.fc9.img
title Fedora (2.6.24-0.81.rc4.git7.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.81.rc4.git7.fc9 ro
root=/dev/VolGroup00/LogVol00 
	initrd /initrd-2.6.24-0.81.rc4.git7.fc9.img
title Fedora (2.6.24-0.80.rc4.git6.fc9)
	root (hd0,2)
	kernel /vmlinuz-2.6.24-0.80.rc4.git6.fc9 ro
root=/dev/VolGroup00/LogVol00 
	initrd /initrd-2.6.24-0.80.rc4.git6.fc9.img
title Microsoft Windows XP Professional
	rootnoverify (hd0,0)
	chainloader +1
title floppy
	rootnoverify (fd0)
	chainloader +1
[root@localhost ~]# rpm -qa kernel
kernel-2.6.24-0.80.rc4.git6.fc9
kernel-2.6.24-0.81.rc4.git7.fc9
kernel-2.6.24-0.107.rc5.git3.fc9
kernel-2.6.24-0.83.rc5.fc9


I can add the kernel manually to grub.conf, but
shouldn't yum automatically add it for us.  This has
to be a bug.  Anybody else see this?

Regards,

Antonio 


     
____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search. 
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[Antonio Olivares]

--- Antonio Olivares <olivares14031(a)yahoo.com&gt; wrote:

>  
>  --- Antonio Olivares <olivares14031(a)yahoo.com&gt;
>  wrote:
>  
>  > 
>  > [olivares@localhost ~]$ uname -a
>  > Linux localhost.localdomain 2.6.24-0.83.rc5.fc9 #1
>  > SMP
>  > Tue Dec 11 12:04:08 EST 2007 i686 i686 i386
>  > GNU/Linux
>  > [olivares@localhost ~]$ rpm -qa kernel
>  > kernel-2.6.24-0.80.rc4.git6.fc9
>  > kernel-2.6.24-0.107.rc5.git3.fc9
>  > kernel-2.6.24-0.83.rc5.fc9
>  > kernel-2.6.24-0.81.rc4.git7.fc9
>  > [olivares@localhost ~]$ su -
>  > Password: 
>  > [root@localhost ~]# cat /boot/grub/grub.conf
>  > # 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,2)
>  > #          kernel /vmlinuz-version ro
>  > root=/dev/VolGroup01/LogVol00
>  > #          initrd /initrd-version.img
>  > #boot=/dev/sda
>  > default=0
>  > timeout=5
>  > splashimage=(hd0,2)/grub/splash.xpm.gz
>  > hiddenmenu
>  > title Fedora (2.6.24-0.83.rc5.fc9)
>  > 	root (hd0,2)
>  > 	kernel /vmlinuz-2.6.24-0.83.rc5.fc9 ro
>  root=LABEL=/
>  > rhgb quiet
>  > 	initrd /initrd-2.6.24-0.83.rc5.fc9.img
>  > title Fedora (2.6.24-0.81.rc4.git7.fc9)
>  > 	root (hd0,2)
>  > 	kernel /vmlinuz-2.6.24-0.81.rc4.git7.fc9 ro
>  > root=LABEL=/ rhgb quiet
>  > 	initrd /initrd-2.6.24-0.81.rc4.git7.fc9.img
>  > title Fedora (2.6.24-0.80.rc4.git6.fc9)
>  > 	root (hd0,2)
>  > 	kernel /vmlinuz-2.6.24-0.80.rc4.git6.fc9 ro
>  > root=LABEL=/ rhgb quiet
>  > 	initrd /initrd-2.6.24-0.80.rc4.git6.fc9.img
>  > title Microsoft Windows Vista Home Edition
>  > 	rootnoverify (hd0,1)
>  > 	chainloader +1
>  > [root@localhost ~]# 
>  > 
>  > 
>  >      
>  >
____________________________________________________________________________________
>  > Never miss a thing.  Make Yahoo your home page. 
>  > http://www.yahoo.com/r/hs
>  > 
>  > -- 
>  
>  This happens on both machines.  
>  
>  [root@localhost ~]# cat /boot/grub/grub.conf
>  # 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,2)
>  #          kernel /vmlinuz-version ro
>  root=/dev/VolGroup00/LogVol00
>  #          initrd /initrd-version.img
>  #boot=/dev/sda
>  #   kernel /vmlinuz-2.6.20-1.3040.fc7 ro
>  root=/dev/VolGroup00/LogVol00 removed -> rhgb quiet
>  #
>  default=0
>  timeout=5
>  splashimage=(hd0,2)/grub/splash.xpm.gz
>  hiddenmenu
>  title Fedora (2.6.24-0.83.rc5.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.83.rc5.fc9 ro
>  root=/dev/VolGroup00/LogVol00 
>  	initrd /initrd-2.6.24-0.83.rc5.fc9.img
>  title Fedora (2.6.24-0.81.rc4.git7.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.81.rc4.git7.fc9 ro
>  root=/dev/VolGroup00/LogVol00 
>  	initrd /initrd-2.6.24-0.81.rc4.git7.fc9.img
>  title Fedora (2.6.24-0.80.rc4.git6.fc9)
>  	root (hd0,2)
>  	kernel /vmlinuz-2.6.24-0.80.rc4.git6.fc9 ro
>  root=/dev/VolGroup00/LogVol00 
>  	initrd /initrd-2.6.24-0.80.rc4.git6.fc9.img
>  title Microsoft Windows XP Professional
>  	rootnoverify (hd0,0)
>  	chainloader +1
>  title floppy
>  	rootnoverify (fd0)
>  	chainloader +1
>  [root@localhost ~]# rpm -qa kernel
>  kernel-2.6.24-0.80.rc4.git6.fc9
>  kernel-2.6.24-0.81.rc4.git7.fc9
>  kernel-2.6.24-0.107.rc5.git3.fc9
>  kernel-2.6.24-0.83.rc5.fc9
>  
>  
>  I can add the kernel manually to grub.conf, but
>  shouldn't yum automatically add it for us.  This has
>  to be a bug.  Anybody else see this?
>  
>  Regards,
>  
>  Antonio  
I have manually added the kernel entry for 107 kernel,
but it does not boot :(.  The initrd for it does not
exist in /boot directory.  How do I create it so that
I can boot 107 kernel ?

[root@localhost ~]# ls /boot/ -l
total 25178
-rw-r--r-- 1 root root   82318 2007-12-14 12:02
config-2.6.24-0.107.rc5.git3.fc9
-rw-r--r-- 1 root root   82365 2007-12-08 22:00
config-2.6.24-0.80.rc4.git6.fc9
-rw-r--r-- 1 root root   82365 2007-12-10 14:38
config-2.6.24-0.81.rc4.git7.fc9
-rw-r--r-- 1 root root   82360 2007-12-11 11:14
config-2.6.24-0.83.rc5.fc9
drwxr-xr-x 2 root root    1024 2007-12-17 19:37 grub
-rw------- 1 root root 3664552 2007-08-30 13:34
initrd-2.6.23-0.149.rc4.fc8.img.orig
-rw------- 1 root root 3195157 2007-12-11 08:00
initrd-2.6.24-0.80.rc4.git6.fc9.img
-rw------- 1 root root 3195254 2007-12-12 07:41
initrd-2.6.24-0.81.rc4.git7.fc9.img
-rw------- 1 root root 3195682 2007-12-13 07:45
initrd-2.6.24-0.83.rc5.fc9.img
drwx------ 2 root root   12288 2007-04-03 12:04
lost+found
-rw-r--r-- 1 root root  900975 2007-12-14 12:02
System.map-2.6.24-0.107.rc5.git3.fc9
-rw-r--r-- 1 root root  900932 2007-12-08 22:00
System.map-2.6.24-0.80.rc4.git6.fc9
-rw-r--r-- 1 root root  900932 2007-12-10 14:38
System.map-2.6.24-0.81.rc4.git7.fc9
-rw-r--r-- 1 root root  900898 2007-12-11 11:14
System.map-2.6.24-0.83.rc5.fc9
-rw-r--r-- 1 root root 2105248 2007-12-14 12:02
vmlinuz-2.6.24-0.107.rc5.git3.fc9
-rw-r--r-- 1 root root 2110656 2007-12-08 22:00
vmlinuz-2.6.24-0.80.rc4.git6.fc9
-rw-r--r-- 1 root root 2110656 2007-12-10 14:38
vmlinuz-2.6.24-0.81.rc4.git7.fc9
-rw-r--r-- 1 root root 2110368 2007-12-11 11:14
vmlinuz-2.6.24-0.83.rc5.fc9


Also did this happen to anybody else?


Regards,

Antonio 


     
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now. 
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Andrew Farris]

Antonio Olivares wrote:
>  Also did this happen to anybody else? 
Lots of good info about your setup in there but I don't see your mkinitrd
version (the one you had when the kernel installed itself).  There was a warning
that a mkinitrd version was coming out which might fail to build initrd on
kernel installs.

http://www.redhat.com/archives/fedora-test-list/2007-December/msg00316.html

Is it possible this impacted you?

-- 
Andrew Farris <lordmorgul(a)gmail.com&gt; <ajfarris(a)gmail.com&gt;
 gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
----                                                                       ----

[Antonio Olivares]

--- Andrew Farris <lordmorgul(a)gmail.com&gt; wrote:

>  Antonio Olivares wrote:
>  > Also did this happen to anybody else?
>  
>  Lots of good info about your setup in there but I
>  don't see your mkinitrd
>  version (the one you had when the kernel installed
>  itself).  There was a warning
>  that a mkinitrd version was coming out which might
>  fail to build initrd on
>  kernel installs.
>  
>  
http://www.redhat.com/archives/fedora-test-list/2007-December/msg00316.html
>  
>  Is it possible this impacted you?
>  
>  -- 
>  Andrew Farris <lordmorgul(a)gmail.com&gt;
>  <ajfarris(a)gmail.com&gt;
>   gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E
>  A2E0 F0F6 E622 C99B 1DF3
>  No one now has, and no one will ever again get, the
>  big picture. - Daniel Geer
>  ----                                                
>                        ----
>  
>  --  
I am not sure, because the one that is present is this
one

[olivares@localhost ~]$ rpm -qa mkinitrd
mkinitrd-6.0.24-1.fc9

Thanks,

Antonio 



     
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now. 
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Andrew Farris]

Antonio Olivares wrote:
>  I have manually added the kernel entry for 107 kernel,
>  but it does not boot :(.  The initrd for it does not
>  exist in /boot directory.  How do I create it so that
>  I can boot 107 kernel ? 
Meant to answer this in the last email, but if you've already updated passed
mkinitrd-6.0.22-1 (the broken one) you should be able to just uninstall the
kernel and put it back in (to see that the kernel install script correctly works
that time on your hardware).  It would probably be best to try this before
manually calling mkinitrd.

The initrd for that kernel did get generated on my macbook in vmware-fusion,
using mkinitrd-6.0.24-1.

-- 
Andrew Farris <lordmorgul(a)gmail.com&gt; <ajfarris(a)gmail.com&gt;
 gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
----                                                                       ----

[Antonio Olivares]

--- Andrew Farris <lordmorgul(a)gmail.com&gt; wrote:

>  Antonio Olivares wrote:
>  > I have manually added the kernel entry for 107
>  kernel,
>  > but it does not boot :(.  The initrd for it does
>  not
>  > exist in /boot directory.  How do I create it so
>  that
>  > I can boot 107 kernel ?
>  
>  Meant to answer this in the last email, but if
>  you've already updated passed
>  mkinitrd-6.0.22-1 (the broken one) you should be
>  able to just uninstall the
>  kernel and put it back in (to see that the kernel
>  install script correctly works
>  that time on your hardware).  It would probably be
>  best to try this before
>  manually calling mkinitrd.
>  
>  The initrd for that kernel did get generated on my
>  macbook in vmware-fusion,
>  using mkinitrd-6.0.24-1.
>  
>  -- 
>  Andrew Farris <lordmorgul(a)gmail.com&gt;
>  <ajfarris(a)gmail.com&gt;
>   gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E
>  A2E0 F0F6 E622 C99B 1DF3
>  No one now has, and no one will ever again get, the
>  big picture. - Daniel Geer
>  ----                                                
>                        ----
>  
>  --  
Thank you for your suggestions.  Removing and
reinstalling did the job :)

[olivares@localhost ~]$ uname -a
Linux localhost 2.6.24-0.107.rc5.git3.fc9 #1 SMP Fri
Dec 14 12:45:18 EST 2007 i686 athlon i386 GNU/Linux
[olivares@localhost ~]$ 

Regards,

Antonio 


     
____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search. 
http://tools.search.yahoo.com/newsearch/category.php?category=shopping