kernel won't upgrade properly, something went wrong

masinick · 2008-03-02 08:03:04

I did a pacman -Syu a short while ago, and there were a lot of packages to upgrade, but the upgrade will not complete as is because I have some conflict. Not sharp enough yet in Arch to figure out what the messages are telling me. Could you help and tell me the steps I need to take to resolve this issue? Thanks!

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: flex: forcing upgrade to version 2.5.33-4
warning: iwlwifi-4965-ucode: forcing upgrade to version 4.44.1.20-1
warning: ruby: forcing upgrade to version 1.8.6_p111-4
resolving dependencies...
looking for inter-conflicts...

Targets: cairo-1.4.14-1 libcups-1.3.6-1 gtk2-2.12.7-1 gcc-libs-4.2.3-3
mpfr-2.3.1-1 gcc-4.2.3-1 libgl-7.0.3rc1-1 mesa-7.0.3rc1-1
acroread-8.1.2-1 filesystem-2007.11-6 avahi-0.6.20-3
bluez-libs-3.27-1 coreutils-6.10-2 curl-7.18.0-1 faac-1.26-1
fakeroot-1.9.3-1 x264-20071202-1 ffmpeg-20071204-1
findutils-4.2.32-1 flex-2.5.33-4 fribidi-0.10.9-1 gpgme-1.1.6-1
groff-1.19.2-4 grub-0.97-11 librsvg-2.20.0-1 imagemagick-6.3.8.0-1
iptables-1.4.0-2 iputils-20070202-4 mkinitcpio-0.5.17-2
kernel26-2.6.24.3-1 ipw3945-1.2.2-7 iwlwifi-4965-ucode-4.44.1.20-1
jack-audio-connection-kit-0.109.2-1 libao-0.8.8-2
libarchive-2.4.12-1 libidl2-0.8.10-1 libmysqlclient-5.0.51-2
libtasn1-1.3-1 libtool-1.5.26-1 libxml2-2.6.31-1 libxmu-1.0.4-1
licenses-2.3-1 lm_sensors-3.0.1-1 logrotate-3.7.5-1 lvm2-2.02.33-1
madwifi-utils-0.9.3.3.3246-1 madwifi-0.9.3.3.3246-2 man-1.6f-2
man-pages-2.78-1 ttf-dejavu-2.23-1 mplayer-1.0rc2-3
ndiswrapper-utils-1.52-1 ndiswrapper-1.52-1 ntfs-3g-1.2216-1
openntpd-3.9p1-7 python-2.5.2-2 openoffice-base-2.3.1-2
orbit2-2.14.12-1 pcre-7.6-3 pidgin-2.4.0-1 qt-4.3.3-4
poppler-qt-0.6.3-1 poppler-qt3-0.6.3-1 rt2500-1.1.0_B4-20
ruby-1.8.6_p111-4 sqlite3-3.5.6-1 libx86-0.99-1 vbetool-1.0-2
vi-7.1.228-1 which-2.19-2 wlan-ng26-0.2.8-14 wavpack-4.41.0-3
xine-lib-1.1.10-1 xorg-apps-1.0.3-3

Total Download Size: 0.00 MB
Total Installed Size: 296.41 MB

Proceed with installation? [Y/n]
checking package integrity...
(74/74) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
kernel26: /lib/modules/2.6.24-ARCH/modules.alias exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.ccwmap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.dep exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.ieee1394map exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.inputmap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.isapnpmap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.ofmap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.pcimap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.seriomap exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.symbols exists in filesystem
kernel26: /lib/modules/2.6.24-ARCH/modules.usbmap exists in filesystem
Errors occurred, no packages were upgraded.

wuischke · 2008-03-02 08:16:28

Try a "pacman -Sf kernel26" to force the upgrade of the kernel.

See what output "pacman -Qo /lib/modules/2.6.24-ARCH/modules.ofmap" gives you. I think it will show you an "error: No package owns ..." message. You most probably installed an earlier kernel26 (.24) package, which didn't include these files, but generated them somehow. The new package includes them, so pacman sees a conflict and stops the update to prevent any harm.

masinick · 2008-03-02 17:14:12

You are right: pacman -Qo /lib/modules/2.6.24-ARCH/modules.ofmap
error: No package owns /lib/modules/2.6.24-ARCH/modules.ofmap

What would be the best next step then? Rather that forge forward I will await a best recommendation. Thanks for your help!

wuischke · 2008-03-02 17:16:04

I think you can savely do a forced upgrade with "pacman -Sf kernel26". It will overwrite the files indicated above, but this shouldn't (will not) cause any problems.

masinick · 2008-03-02 19:01:07

I got an awful lot of error messages that scrolled and scrolled, but I finally put that on a different workspace and did some browsing. It never seemed to "complete" normally, so I had to Ctrl C, but it must have finished, because when I ran the command again it was installed. I was then able to do a pacman -Syu and yank in the 73 packages that were waiting to be upgraded. It worked normally this time. I will read up on the pacman options to understand my alternatives better. I am familiar with the Debian packaging system, so I ought to be able to draw some quick analogies, then I will much better understand it. The main thing was that I was unfamiliar with the messages I was receiving. As I become more familiar with "The Arch Way" I am sure this will sink in and become almost second nature.

Thanks for easing me in as I learn more about using Arch effectively. Appreciate both your time and your help - and it was indeed good help!

Arch Linux

#1 2008-03-02 08:03:04

kernel won't upgrade properly, something went wrong

#2 2008-03-02 08:16:28

Re: kernel won't upgrade properly, something went wrong

#3 2008-03-02 17:14:12

Re: kernel won't upgrade properly, something went wrong

#4 2008-03-02 17:16:04

Re: kernel won't upgrade properly, something went wrong

#5 2008-03-02 19:01:07

Re: kernel won't upgrade properly, something went wrong

Board footer