Fedora Linux Support Community & Resources Center
  #1  
Old 23rd April 2006, 03:50 PM
jhetrick62 Offline
Registered User
 
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
Kernel 2.6.16-1.2096 installs and breaks kernel 2.6.16-1.2080

I haven't had time to attempt a re-install of kernel 2.6.16-1.2080 yet, but I will have to as after updating the kernel to .2096, my vnc over xinetd won't work so I need to see if that is the culprit. My problem is that when I attempt to go back to .2080 through GRUB, it fails with a kernel panic. Strange as I've never had that happen when adding a new kernel through YUM.

I was also wondering if anyone know why the new kernel installed with a "12" after the LABEL=/ instead of the normal 5 or 3?
kernel /vmlinux-2.6.16-1.2096_FC5 ro root=LABEL=/12 rhgb quiet

What does 12 indicate?
Anybody else have .2080 kernel get borked over after update?

Jeff
__________________
Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote
  #2  
Old 23rd April 2006, 04:13 PM
marko Offline
Registered User
 
Join Date: Jun 2004
Location: Laurel, MD USA
Posts: 6,062
The "LABEL=" should look the same as it did for your previous kernel,
try manually changing it to "LABEL=/" from "LABEL=/12" and try to
boot. My 2096 didn't do that (didn't append "12")

mark
Reply With Quote
  #3  
Old 23rd April 2006, 04:29 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 23
Posts: 9,224
AFAIK kernels can't break eachother -- All their files go into different places so there's no conflicts. Maybe there was a bug in the automatic editing of your grub.conf, though? Can you post you /etc/grub.conf and the output of:
Code:
ls /boot
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #4  
Old 24th April 2006, 01:56 AM
jhetrick62 Offline
Registered User
 
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
Firewing, that is what I thought also! But I never run yum with -y (nervouse I guess) so I okayed the install of the .2096 kernel and the removal of .2054 ( the original kernel from install). I was running .2080 before the update so that was still active. I checked the grub after yum was done and noticed the "12", but figured, what the heck. It booted just fine. I then installed vsftp as per Stanton Finley. It was right after this that I noticed that vnc over xinetd was broke. So yesterday I uninstalled vsftp and vnc was still down. So I re-booted to the .2080 kernel, and it listed a kernel panic. I tried twice with the same result. It talked about not being able to find files??

Oh well, here is the grub.conf and boot which both look good to me.
[root@jeffserver jeff]# ls /boot
config-2.6.16-1.2080_FC5 grub initrd-2.6.16-1.2096_FC5.img System.map-2.6.16-1.2080_FC5 vmlinuz-2.6.16-1.2080_FC5
config-2.6.16-1.2096_FC5 initrd-2.6.16-1.2080_FC5.img lost+found System.map-2.6.16-1.2096_FC5 vmlinuz-2.6.16-1.2096_FC5
[root@jeffserver jeff]#

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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdb2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=7
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.16-1.2096_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.16-1.2096_FC5 ro root=LABEL=/12 rhgb quiet
initrd /initrd-2.6.16-1.2096_FC5.img
title Fedora Core (2.6.16-1.2080_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=LABEL=/5 rhgb quiet
initrd /initrd-2.6.16-1.2080_FC5.img
title Fedora Core - 4 (2.6.14-1.1656_FC4)
root (hd0,0)
kernel /boot/vmlinuz-2.6.14-1.1656_FC4 ro root=LABEL=/ 5 rhgb quiet
initrd /boot/initrd-2.6.14-1.1656_FC4.img
title Fedora Core - 4 (2.6.14-1.1656_FC4)
root (hd0,0)
kernel /boot/vmlinuz-2.6.14-1.1656_FC4 ro root=LABEL=/ 3
initrd /boot/initrd-2.6.14-1.1656_FC4.img
__________________
Registered Linux User #411071

If at first you don't suceed, read the man page again!

Last edited by jhetrick62; 24th April 2006 at 02:00 AM.
Reply With Quote
  #5  
Old 24th April 2006, 04:03 AM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 23
Posts: 9,224
Did you do an update from FC4 > 5 via yum or the CDs?
Firewing1
Quote:
Originally Posted by jhetrick62
Firewing, that is what I thought also! But I never run yum with -y (nervouse I guess) so I okayed the install of the .2096 kernel and the removal of .2054 ( the original kernel from install). I was running .2080 before the update so that was still active. I checked the grub after yum was done and noticed the "12", but figured, what the heck. It booted just fine. I then installed vsftp as per Stanton Finley. It was right after this that I noticed that vnc over xinetd was broke. So yesterday I uninstalled vsftp and vnc was still down. So I re-booted to the .2080 kernel, and it listed a kernel panic. I tried twice with the same result. It talked about not being able to find files??

Oh well, here is the grub.conf and boot which both look good to me.
[root@jeffserver jeff]# ls /boot
config-2.6.16-1.2080_FC5 grub initrd-2.6.16-1.2096_FC5.img System.map-2.6.16-1.2080_FC5 vmlinuz-2.6.16-1.2080_FC5
config-2.6.16-1.2096_FC5 initrd-2.6.16-1.2080_FC5.img lost+found System.map-2.6.16-1.2096_FC5 vmlinuz-2.6.16-1.2096_FC5
[root@jeffserver jeff]#

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 (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdb2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=7
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.16-1.2096_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.16-1.2096_FC5 ro root=LABEL=/12 rhgb quiet
initrd /initrd-2.6.16-1.2096_FC5.img
title Fedora Core (2.6.16-1.2080_FC5)
root (hd1,0)
kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=LABEL=/5 rhgb quiet
initrd /initrd-2.6.16-1.2080_FC5.img
title Fedora Core - 4 (2.6.14-1.1656_FC4)
root (hd0,0)
kernel /boot/vmlinuz-2.6.14-1.1656_FC4 ro root=LABEL=/ 5 rhgb quiet
initrd /boot/initrd-2.6.14-1.1656_FC4.img
title Fedora Core - 4 (2.6.14-1.1656_FC4)
root (hd0,0)
kernel /boot/vmlinuz-2.6.14-1.1656_FC4 ro root=LABEL=/ 3
initrd /boot/initrd-2.6.14-1.1656_FC4.img
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #6  
Old 24th April 2006, 11:52 AM
jhetrick62 Offline
Registered User
 
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
NO, original install of FC5 on fresh partition. As I said, when it broke, I only "yum update" and then installed vsftp as per Stanton Finley. I would have never attempted to access the .2080 kernel again if vnc over xinetd didn't stop working and that originally was installed following your guidelines, Firewing.

I should get time today to search for the rpm and re-install the .2080 kernel to see if it still will work.

Jeff
__________________
Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote
  #7  
Old 24th April 2006, 01:20 PM
Firewing1 Offline
Registered User
 
Join Date: Dec 2004
Location: Canada
Age: 23
Posts: 9,224
That's odd - There's FC4 kernel listings in your grub.conf... I would remove them then.
Can you try re-doing the XineTD instructions and executing:
Code:
su -
yum update -y
chkconfig xinetd on
service xinetd restart
I also am using my own instructions for my VNC setup and nothing went wrong between kernel upgrades, so I just think a few files got corrupted.
Firewing1
__________________
[+] My open source software and blog
[+] Some of my howtos: (for full list, click here)
Reply With Quote
  #8  
Old 24th April 2006, 01:49 PM
jhetrick62 Offline
Registered User
 
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
Sure, I keep the FC4 settings as it still exists on this box. As I said, I put FC5 into a fresh partition so I haven't overwritten fC4 yet. That partition will be used for my experiment w/ FC5_64 as I have a 64 bit Sempron setup running 32 bit right now.

I will redo the xinetd setup.

Jeff
__________________
Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote
  #9  
Old 24th April 2006, 02:26 PM
jhetrick62 Offline
Registered User
 
Join Date: Feb 2005
Location: Buffalo, Ny
Posts: 875
Fixed! That is the vnc over xinetd. That's what happens when you assume! I made one other change the other day, I set the 5900 port to 8 bit as I was doing quite a bit of remote access. My current video driver obviously doesn't like 8-bit depth. No wonder port 5901 never worked! I assumed it was a port problem and never pursued it. I should know better.

Well, now they both work. I set port 5901 to 800x600 and 16-bit depth and it liked that. I also created a remote user profile and run the desktop with plain background and that speeds it up quite a bit.

That doesn't answer how I borked the kernel and I like to have a backup in case of an update problem, so I will manually load that! Oh well, thanks for your support Firewing, as it caused me to figure out the problem.

My next project is to get vsftp to run inside of xinetd so that I can take advantage of the denyhosts monitoring.

Jeff
__________________
Registered Linux User #411071

If at first you don't suceed, read the man page again!
Reply With Quote
Reply

Tags
breaks, installs, kernel

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panics and no installs Jose R Using Fedora 0 28th March 2007 06:13 AM
Kernel 2080 Breaks Captive-NTFS Computer Guru Using Fedora 2 3rd May 2006 02:17 AM
Lame segfaults with kernel 2.6.16-1.2080 daihard Using Fedora 7 2nd April 2006 09:21 PM


Current GMT-time: 16:46 (Tuesday, 21-10-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat
Oltu Photos - Eggenstein-Leopoldshafen - Mudanjiang Photos on Instagram