[mythtv-users] Problem upgrading to the latest kernel
gaberubin at gmail.com
Thu Aug 9 05:52:16 UTC 2007
For the benefit of both lists, in case anyone else runs into this
trouble, Axel's solution (unsurprisingly) solved my problem when I ran
into troubles upgrading from fedora core 5 to fedora 7:
On 8/8/07, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> On Wed, Aug 08, 2007 at 02:08:02AM -0700, Gabe Rubin wrote:
> > Axel,
> > I hope it is not a problem to email you directly.
. . .
> > 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
not worth filing; I probably screwed something up and the solution
below solved the problem.
> > 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.
Probably correct. Clearing out my /ect/smart/channels directory,
removing all the smart related packages, then reinstalling yum.
atrpms-package-config and fedora-package-config all via yum, and then
doing what is recited below did the trick of enabling everything and
eliminating the problem I had, which was:
> > 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
> > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/autofs-5.0.1-9.i386.rpm
> 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
this, I believe, solved the rpmdb issue:
> b) ensure proper smart channels are in place
> - smart query kernel should return
> kernel-2.6.21-1.3194.fc7 at x86_64
> kernel-18.104.22.168-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.
no need to, uninstalling, and reinstalling everything, as described
above, via yum did the trick
> 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.
that order worked. All I had to do after is get all my *kmdl*
packages (alsa, nvidia and lirc) in aside from ivtv, which was
installed with the avalanche of other packages.
> And make sure you don't have any priorities/weighing etc. hindering the
> upgrade to F7.
No issues there.
Again, thanks for your help.
More information about the mythtv-users