[ATrpms-users] Problem upgrading to the latest kernel
Axel.Thimm at ATrpms.net
Wed Aug 8 12:20:28 CEST 2007
On Wed, Aug 08, 2007 at 02:08:02AM -0700, Gabe Rubin wrote:
> I hope it is not a problem to email you directly.
Actually I do :)
> I am not on the atrpms list, and I thought this was too off-topic
> for the myth list. I just upgraded from fc5 -> f7 via a DVD upgrade
> because of the EOL issues.
Any question you have will be also a question of other users, that are
either on list or in the future googlinmg around, so this is
definitely a list question.
> However, the kernel stayed at 2.6.20-1.2320.fc5. It appeared to have
> a fc7 kernel installed, but no mention of it in grub.conf.
Sounds like a bug in F7's anaconda worth filing to
> I wound up removing it using smart, and tried to reinstall it doing
> a smart install kernel, but get this error:
> [root at localhost ~]# smart upgrade
> Loading cache...
> Updating cache... ######################################## [100%]
> Computing transaction...
> Upgrading packages (1):
> kernel-2.6.21-1.3194.fc7 at i686
You don't have the updates enabled.
> 16.2MB of package files are needed. 46.3MB will be used.
> Confirm changes? (Y/n):
> Committing transaction...
> error: hal-0.5.9-8.fc7 conflicts with kernel < 2.6.17
> error: autofs-5.0.1-9 conflicts with kernel < 2.6.17
Hm, smart usually cathec these. Perhaps a broken rpmdb?
> This is weird, because I am running a kernel higher than 2.6.17.
No, that's OK, you may be running a kernel higher than that, but you
also have another kernel package at least that is older than 2.6.17.
> Do you have any suggestions? I was going to remove both hal and
> autofs, but hal was going to take away a lot of stuff, and after I
> removed autofs I had to do this to reinstall it (which I hope didn't
> mess things up further):
> rpm -Uhv --nodeps
Oh, no, don't start shooting at the system :)
Try the following emergency steps:
a) fix potentially broken rpmdb:
- make sure nothing used the rpmdb (including yum-updatesd etc)
- rm -f /var/lib/rpm/__*
- rpm --rebuilddb (wait, use du -s /var/lib/rpm* to kill the time ...)
- check with rpm -qa | less that the rpmdb makes sense
b) ensure proper smart channels are in place
- smart query kernel should return
kernel-2.6.21-1.3194.fc7 at x86_64
kernel-220.127.116.11-41.fc7 at x86_64
- if the latter doesn't show up use smart channel --enable ...,
smart update, check atrpms-package-config etc. to make sure you
have the channels in place.
c) fix & upgrade the system
- smart update
- smart fix
- smart upgrade
- perhaps the latter two should be swapped, this depdends on what
suggested actions you will see.
And make sure you don't have any priorities/weighing etc. hindering the
upgrade to F7.
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20070808/bbc91943/attachment.bin
More information about the atrpms-users