Kernel update with yum

[David McCormick]

I recently did a clean install of FC-4 64 bit on a new disk and updated 
using yum update with livna. Now when I reboot Grub starts the 2111 
kernel by default which is waht I want but fails with the following

root (hd2,0)

filesystem is ext2fs, partition type 0x87

kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet

error15: file not found

I have reinstalled and updated several times with the same results.

I have done this before and never had this problem, any ideas what is 
happening with the update?
I have also just tried to update the kernel with out a full update with 
the same result.  It is a 64 bit machine but I did not have this trouble 
with the old disk on the same machine.

Thanks

Dave

[Rainer Traut]

Hi,

David McCormick schrieb:
>  I recently did a clean install of FC-4 64 bit on a new disk and
> updated 
>  using yum update with livna. Now when I reboot Grub starts the 2111 
>  kernel by default which is waht I want but fails with the following
>  
>  root (hd2,0)
>  
>  filesystem is ext2fs, partition type 0x87
>  
>  kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet 
lable? should that be LABEL?
Have you edited grub.conf by hand?

HTH
Rsiner

[David McCormick]

Rainer Traut wrote:

>  Hi,
>
>  David McCormick schrieb:
>
> > I recently did a clean install of FC-4 64 bit on a new disk and 
> > updated using yum update with livna. Now when I reboot Grub starts 
> > the 2111 kernel by default which is waht I want but fails with the 
> > following
> >
> > root (hd2,0)
> >
> > filesystem is ext2fs, partition type 0x87
> >
> > kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet
>
>
>  lable? should that be LABEL?
>  Have you edited grub.conf by hand?
>
>  HTH
>  Rsiner
>  
It is label just my fingers getting out of sync.  I checked gurb.conf 
and it has the proper files for 2111, the same number and type as 3069 
has. 

Dave

[Thomas Taylor]

On Monday 29 May 2006 06:43, David McCormick wrote:
>  Rainer Traut wrote:
>  > Hi,
>  >
>  > David McCormick schrieb:
>  >> I recently did a clean install of FC-4 64 bit on a new disk and
>  >> updated using yum update with livna. Now when I reboot Grub starts
>  >> the 2111 kernel by default which is waht I want but fails with the
>  >> following
>  >>
>  >> root (hd2,0)
>  >>
>  >> filesystem is ext2fs, partition type 0x87
>  >>
>  >> kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet
>  >
>  > lable? should that be LABEL?
>  > Have you edited grub.conf by hand?
>  >
>  > HTH
>  > Rsiner
>
>  It is label just my fingers getting out of sync.  I checked gurb.conf
>  and it has the proper files for 2111, the same number and type as 3069
>  has.
>
>  Dave 
Hi Dave:
You missed the point of Rainers reply.  It is supposed to be CAPITOL letters 
for label (LABEL).  

You should spellcheck and proofread your posts.  What is a gurb.conf file? 
That should be grub.conf.  I'm not trying to put you down, but a spelling 
mistake in a file can cause unexpected results and it's best to check all 
your work.

3069?  What kernel is that from?  Was that a 2.4 kernel?

I would recommend not updating with anything but the stock Fedora repos until 
the system is working properly, then add things like livna or dags.  This way 
you will at least know what the problem is related to.

You might also want to check the archives relevant to the 64 bit 2111 kernel.  
I seem to recall seeing some problems about that.

-- 
Tom Taylor
Linux user #263467
Federal Way, WA

[Paul Howarth]

On Tue, 2006-05-30 at 00:01 -0700, Thomas Taylor wrote:
>  On Monday 29 May 2006 06:43, David McCormick wrote:
>  > Rainer Traut wrote:
>  > > Hi,
>  > >
>  > > David McCormick schrieb:
>  > >> I recently did a clean install of FC-4 64 bit on a new disk and
>  > >> updated using yum update with livna. Now when I reboot Grub starts
>  > >> the 2111 kernel by default which is waht I want but fails with the
>  > >> following
>  > >>
>  > >> root (hd2,0)
>  > >>
>  > >> filesystem is ext2fs, partition type 0x87
>  > >>
>  > >> kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet
>  > >
>  > > lable? should that be LABEL?
>  > > Have you edited grub.conf by hand?
>  > >
>  > > HTH
>  > > Rsiner
>  >
>  > It is label just my fingers getting out of sync.  I checked gurb.conf
>  > and it has the proper files for 2111, the same number and type as 3069
>  > has.
>  >
>  > Dave
>  
>  Hi Dave:
>  You missed the point of Rainers reply.  It is supposed to be CAPITOL letters 
>  for label (LABEL).  
>  
>  You should spellcheck and proofread your posts. 
Indeed. You might then use the word CAPITAL instead of CAPITOL.

>  What is a gurb.conf file? 
>  That should be grub.conf.  I'm not trying to put you down, but a spelling 
>  mistake in a file can cause unexpected results and it's best to check all 
>  your work.
>  
>  3069?  What kernel is that from?  Was that a 2.4 kernel? 
Probably another typo, should have been 2069.

>  I would recommend not updating with anything but the stock Fedora
> repos until 
>  the system is working properly, then add things like livna or dags.  This way 
>  you will at least know what the problem is related to. 
Sounds reasonable.

>  You might also want to check the archives relevant to the 64 bit 2111
> kernel.  
>  I seem to recall seeing some problems about that. 
I think the 2111 kernel fixed the networking issues that the 2107 kernel
was plagued by:
http://www.redhat.com/archives/fedora-list/2006-May/msg00890.html

Paul.

[David McCormick]

Thomas Taylor wrote:

> On Monday 29 May 2006 06:43, David McCormick wrote:
>   
>
> >Rainer Traut wrote:
> >    
> >
> >>Hi,
> >>
> >>David McCormick schrieb:
> >>      
> >>
> >>>I recently did a clean install of FC-4 64 bit on a new disk and
> >>>updated using yum update with livna. Now when I reboot Grub starts
> >>>the 2111 kernel by default which is waht I want but fails with the
> >>>following
> >>>
> >>>root (hd2,0)
> >>>
> >>>filesystem is ext2fs, partition type 0x87
> >>>
> >>>kernel /boot/vmlinux-2.6.16-1.2111_FC4 ro root=lable=/123 rhgb quiet
> >>>        
> >>>
> >>lable? should that be LABEL?
> >>Have you edited grub.conf by hand?
> >>
> >>HTH
> >>Rsiner
> >>      
> >>
> >It is label just my fingers getting out of sync.  I checked gurb.conf
> >and it has the proper files for 2111, the same number and type as 3069
> >has.
> >
> >Dave
> >    
> >
>
> Hi Dave:
> You missed the point of Rainers reply.  It is supposed to be CAPITOL letters 
> for label (LABEL).  
>
> You should spellcheck and proofread your posts.  What is a gurb.conf file? 
> That should be grub.conf.  I'm not trying to put you down, but a spelling 
> mistake in a file can cause unexpected results and it's best to check all 
> your work.
>
> 3069?  What kernel is that from?  Was that a 2.4 kernel?
>
> I would recommend not updating with anything but the stock Fedora repos until 
> the system is working properly, then add things like livna or dags.  This way 
> you will at least know what the problem is related to.
>
> You might also want to check the archives relevant to the 64 bit 2111 kernel.  
> I seem to recall seeing some problems about that.
>
>   
>  
No I didn't miss the point I was just in a hurry. My spell check needs 
to have grub.conf  added it doesn't seem to be there along with a lot of 
other words and acronyms. I did find the problem and correct it, I had 
added an IDE drive to a SCSI system and as soon as I removed it 
everything worked as it has in the past 13 years that I have been using 
Linux.

Thank you for your help.

Dave

[Mikkel]

David McCormick wrote:
>  I did find the problem and correct it, I had
>  added an IDE drive to a SCSI system and as soon as I removed it
>  everything worked as it has in the past 13 years that I have been using
>  Linux.
>  
>  Thank you for your help.
>  
>  Dave
>   
I am more used to seeing this problem with LILO then Grub. Depending
on your BIOS and SCSI controller, the drive mapping can change when
you add an IDE drive to a SCSI system. LILO used to always assume
that BIOS device 80 was the IDE drive. (It is supposed to determine
that at boot time now.) So if you booted from the SCSI drive, you
had to tell LILO that the SCSI drive was BIOS 80. I have not used
Grub on a SCSI/IDE mix, but I am sure there is a way to tell it to
double check the drive mapping when you add an IDE drive.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

[Paul Howarth]

On Tue, 2006-05-30 at 20:13 -0500, Mikkel L. Ellertson wrote:
>  David McCormick wrote:
>  > I did find the problem and correct it, I had
>  > added an IDE drive to a SCSI system and as soon as I removed it
>  > everything worked as it has in the past 13 years that I have been using
>  > Linux.
>  > 
>  > Thank you for your help.
>  > 
>  > Dave
>  > 
>  I am more used to seeing this problem with LILO then Grub. Depending
>  on your BIOS and SCSI controller, the drive mapping can change when
>  you add an IDE drive to a SCSI system. LILO used to always assume
>  that BIOS device 80 was the IDE drive. (It is supposed to determine
>  that at boot time now.) So if you booted from the SCSI drive, you
>  had to tell LILO that the SCSI drive was BIOS 80. I have not used
>  Grub on a SCSI/IDE mix, but I am sure there is a way to tell it to
>  double check the drive mapping when you add an IDE drive. 
I think grub makes the same assumption. Use the device.map file to get
grub to understand the BIOS ordering, e.g.:

# cat /boot/grub/device.map
(fd0)   /dev/fd0
(hd0)   /dev/sda
(hd1)   /dev/sdb
(hd2)   /dev/hdc

Paul.