F10 > F11 issues
Kam Leo
kam.leo at gmail.com
Tue Aug 11 18:38:17 UTC 2009
On Tue, Aug 11, 2009 at 11:27 AM, Michael Schwendt<mschwendt at gmail.com> wrote:
> On Tue, 11 Aug 2009 18:49:35 +0100, Tom wrote:
>
>>
>> >
>> > What do you get for rpm -qa kernel\* ?
>> >
>>
>> # rpm -qa kernel\*
>> kernel-2.6.27.25-78.2.56.fc9.i686
>> kernel-devel-2.6.26.5-45.fc9.i686
>> kernel-headers-2.6.27.29-170.2.78.fc10.i386
>> kernel-PAE-2.6.27.29-170.2.78.fc10.i686
>> kernel-firmware-2.6.27.29-170.2.78.fc10.noarch
>> kerneloops-0.12-2.fc10.i386
>> kernel-2.6.26.5-45.fc9.i686
>> kernel-xen-2.6.25.3-2.fc9.i686
>
> (!)
>
>> kernel-2.6.27.29-170.2.78.fc10.i686
>> kernel-devel-2.6.27.25-78.2.56.fc9.i686
>> kernel-devel-2.6.27.29-170.2.78.fc10.i686
>>
>> > $ rpm -q --conflicts DeviceKit-disks-004-4.fc11.i586
>> > kernel < 2.6.26
>
> The kernel-xen above is lower than 2.6.26 and causes the conflict.
> You need to remove it prior to the upgrade: rpm --erase kernel-xen
>
While you are in the erasing mode, get rid of the F9 kernels and all
except for the single F10 kernel that you are using. After you
complete your upgrade to F11 erase the last F10 kernel pacakges. No
sense filling up /boot with obsolete packages.
More information about the users
mailing list