Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 905298 - Fedora 18 starts with wrong kernel
Summary: Fedora 18 starts with wrong kernel
Keywords:
Status: CLOSED DUPLICATE of bug 842427
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-29 05:37 UTC by Andrei Gaponenko
Modified: 2013-04-05 14:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 888234
Environment:
Last Closed: 2013-04-05 14:03:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Andrei Gaponenko 2013-01-29 05:37:39 UTC 
+++ This bug was initially created as a clone of Bug #888234 +++

Cloning the bug as I can not change its status from "CLOSED ERRATA". From the resolution it sounds like the problem should have been fixed in the non-beta Fedora 18.  However I hit exactly the same issue: Fedora 18 installer picked an existing

/boot/vmlinuz-3.6.11-1.fc16.x86_64

kernel for the principal F18 grub boot menu entry, instead of properly using the one shipped with Fedora 18:

/boot/vmlinuz-3.6.10-4.fc18.x86_64

That produced a hard-to-debug system, that booted seemingly fine, but then had no working WiFi (kernel modules did not load because of the version mismatch).

Andrei
Comment 1 Josh Boyer 2013-01-29 13:03:29 UTC 
There's nothing we can do about this in the kernel.  Newer kernels will always show up after a release GA.

How did you manage to get from F16->F18 with the F16 kernel still installed though?  Anaconda itself doesn't do upgrades, having pushed that to the fedup tool.  Fedup is only available in F17, not F16.  So, can you elaborate on exactly what you did to get to F18?
Comment 2 Matthieu Pupat 2013-01-29 13:31:51 UTC 
IMHO this should be addressed in grub2. gurb2 should make sure the kernel it grabs match the library installed on the root partition.

In my case I had:

boot partition with both vmlinuz-3.6.6-3.fc18.x86_64 and vmlinuz-3.6.9-2.fc17.x86_64

f17 root partition with 3.6.9-2 libs

f18 root partition with 3.6.6-3 libs

but the boot loader decided to use f18 root partition (containing 3.6.6-3 libs) with vmlinuz-3.6.9-2.fc17.x86_64
Comment 3 Andrei Gaponenko 2013-01-29 13:40:55 UTC 
Hi,

@Josh
> There's nothing we can do about this in the kernel.

Yes, this is why I submitted this as an anaconda item.  It's the original #888334 that was against kernel.

@Mattieu
> IMHO this should be addressed in grub2.

If that can be done this sounds like the best solution.  My reasoning to report this for anaconda was that the installer knows exactly what kernel it was shipped with and should act accordingly.

@Josh
> How did you manage to get from F16->F18 with the F16 kernel still installed though? 

I had a Fedora 16 install with /boot on sda5 and root on an LVM volume.  It was fully updated, thus /boot/vmlinuz-3.6.11-1.fc16.x86_64
Then I installed Fedora 18 in a new LVM volume, while sharing /boot with Fedora 16.  Fedora 18 comes with the (older) vmlinuz-3.6.10-4.fc18.x86_64

Andrei
Comment 4 Steve Tyler 2013-01-29 15:10:52 UTC 
(In reply to comment #3)
...
> > How did you manage to get from F16->F18 with the F16 kernel still installed though? 
> 
> I had a Fedora 16 install with /boot on sda5 and root on an LVM volume.  It
> was fully updated, thus /boot/vmlinuz-3.6.11-1.fc16.x86_64
> Then I installed Fedora 18 in a new LVM volume, while sharing /boot with
> Fedora 16.  Fedora 18 comes with the (older) vmlinuz-3.6.10-4.fc18.x86_64
...

The installer lets you reuse /boot without reformatting it ...
Comment 5 Chris Lumens 2013-04-05 14:03:03 UTC 

*** This bug has been marked as a duplicate of bug 842427 ***
Note You need to log in before you can comment on or make changes to this bug.