You are not logged in.

#1 2012-02-12 14:09:34

Tectu
Member
Registered: 2011-11-10
Posts: 29

[SOLVED] linux-firmware file conflict

Hello folks,

May you help me out with this one? I have no idea what's wrong and how to fix that.
Google didn't help too, seems to be a personal problem, since the new page dosen't refer to anything similar. I did http://www.archlinux.org/news/filesyste … -required/ and http://www.archlinux.org/news/initscrip … -required/ a few days/weeks ago, the system worked fine after that for a few days. I also did the pacman 4 and kmod updates.

[tectu@Cosinus ~]$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
:: Replace lorcon-old-svn with community/lorcon? [Y/n] 
:: Replace pylorcon with community/python2-pylorcon? [Y/n] 
resolving dependencies...
looking for inter-conflicts...

Targets (60): aircrack-ng-1.1-8  aircrack-ng-scripts-1.1-8  apr-1.4.5-2  blender-3:2.61-5  device-mapper-2.02.90-1  docbook-xsl-1.76.1-2  firefox-10.0.1-1  fuse-2.8.7-1
              geos-3.3.2-1  ghostscript-9.05-1  git-1.7.9-2  glib2-2.30.2-2  grep-2.10-2  hicolor-icon-theme-0.12-2  imagemagick-6.7.5.3-1  iw-3.3-1  kdelibs-4.8.0-3  less-444-3
              libdmtx-0.7.4-3  libdrm-2.4.31-1  libiodbc-3.52.7-5  libjpeg-turbo-1.2.0-1  libksba-1.2.0-2  libltdl-2.4.2-3  libraw1394-2.0.7-2  libshout-1:2.3.0-1
              libssh2-1.4.0-1  libtool-2.4.2-3  libvorbis-1.3.3-1  linux-3.2.5-1  linux-firmware-20120205-1  linux-headers-3.2.5-1  lorcon-224-2  lorcon-old-svn-224-1 [removal]
              lvm2-2.02.90-1  nmap-5.51-3  ntfs-3g-2012.1.15-1  opencollada-867-1  openexr-1.7.0-2  pacman-mirrorlist-20120211-1  pcre-8.30-1  phonon-1:4.6.0-2  pixman-0.24.4-1
              pm-utils-1.4.1-4  pylorcon-3-4 [removal]  python2-pylorcon-2-2  qca-2.0.3-2  shared-desktop-ontologies-0.9.0-1  syslog-ng-3.3.4-2  tdb-1.2.9-2  unrar-4.1.4-2
              v4l-utils-0.8.6-1  vim-7.3.434-1  vim-runtime-7.3.434-1  xmlto-0.0.25-2  xorg-mkfontdir-1.0.7-1  xorg-mkfontscale-1.1.0-1  xorg-xclock-1.0.6-1  xorg-xinit-1.3.2-1
              zip-3.0-3

Total Installed Size:   575.90 MiB
Net Upgrade Size:       34.02 MiB

Proceed with installation? [Y/n] 
(58/58) checking package integrity                                                                          [################################################################] 100%
(58/58) loading package files                                                                               [################################################################] 100%
(58/58) checking for file conflicts                                                                         [################################################################] 100%
error: failed to commit transaction (conflicting files)
linux-firmware: /lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw exists in filesystem
linux-firmware: /lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw exists in filesystem
linux-firmware: /lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw exists in filesystem
linux-firmware: /lib/firmware/isci/isci_firmware.bin exists in filesystem
Errors occurred, no packages were upgraded.
[tectu@Cosinus ~]$ 

Thanks

~ Tectu

Last edited by Tectu (2012-02-12 18:16:05)

Offline

#2 2012-02-12 14:30:39

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,466
Website

Re: [SOLVED] linux-firmware file conflict

What's the output of

pacman -Qo /lib/firmware/bnx2x/*

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2012-02-12 14:43:34

Tectu
Member
Registered: 2011-11-10
Posts: 29

Re: [SOLVED] linux-firmware file conflict

Trilby wrote:

What's the output of

pacman -Qo /lib/firmware/bnx2x/*

Here you go:

tectu@Cosinus ~]$ pacman -Qo /lib/firmware/bnx2x/*
error: No package owns /lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
error: No package owns /lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
error: No package owns /lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
[tectu@Cosinus ~]$ 

P.S. I did a 'pacman -Rddn linux-firmware' before, since I hoped it will help. Maybe not a so good idea?

Last edited by Tectu (2012-02-12 14:46:15)

Offline

#4 2012-02-12 14:58:03

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,466
Website

Re: [SOLVED] linux-firmware file conflict

Before you did the 'Rddn' were you getting the same errors or different ones, were there more of them?  I believe there should be more files in the directory than that (mine shows over a dozen).

Take this with a *very* large grain of salt - and perhaps wait for others to chime in first - but if it were me, I'd do a pacman -Sf linux-firmware.

The only thing I can figure is there was some issue that lead you to do the Rddn removal, but for some reason that removal left behind a few files which it should have removed.  (Was the removal interrupted by chance?)  Now pacman will not overwrite those files without being explicitly instructed to with the --force or -f flag.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#5 2012-02-12 15:13:12

Tectu
Member
Registered: 2011-11-10
Posts: 29

Re: [SOLVED] linux-firmware file conflict

The errors and number of errors before the  'pacman -Rddn linux-firmware'  were exact the same.

I've really no clue what happened here. I am running 3 archlinux computers, and I have that problem only with this one.
But since this is not a very important system for me and I have my backups, I gave the  'pacman -Sf linux-firmware'  a shot. Aaaand it worked afterwards.


Thank you for your help, Trilby.

Shall I mark this thread as [SOLVED] or not, since we don't know where the problem is/was.

Offline

#6 2012-02-12 17:00:24

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,466
Website

Re: [SOLVED] linux-firmware file conflict

It sounds like your problem is solved.  The source of those stray files could be an interesting mystery, but without more data-points I doubt there'd be any way to solve it.

Perhaps being marked as SOLVED but also edited to highlight the source of the problem would draw in anyone else with similar issues (eg "[SOLVED] linux-firmware file conflict")


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#7 2012-02-12 21:57:43

jabooth
Member
Registered: 2011-10-26
Posts: 2

Re: [SOLVED] linux-firmware file conflict

Hey guys, have the exact same issue here. I've not taken any action yet - my output of

pacman -Qo /lib/firmware/bnx2x/* 

is

error: No package owns /lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
/lib/firmware/bnx2x/bnx2x-e1-7.0.20.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e1-7.0.23.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e1-7.0.29.0.fw is owned by linux-firmware 20111101-1
error: No package owns /lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
/lib/firmware/bnx2x/bnx2x-e1h-7.0.20.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e1h-7.0.23.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e1h-7.0.29.0.fw is owned by linux-firmware 20111101-1
error: No package owns /lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
/lib/firmware/bnx2x/bnx2x-e2-7.0.20.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e2-7.0.23.0.fw is owned by linux-firmware 20111101-1
/lib/firmware/bnx2x/bnx2x-e2-7.0.29.0.fw is owned by linux-firmware 20111101-1

any ideas before I try 'pacman -Rddn linux-firmware'? If anyone wants me to run any diagonsitics, let me know.

Cheers, jabooth

Offline

#8 2012-02-12 22:49:51

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,466
Website

Re: [SOLVED] linux-firmware file conflict

pacman -Rddn will not help the problem any.  The step that worked for Tectu was the pacman -Sf linux-firmware.  The removal will not remove any of the files that are causing the problem.

If this is a recurring problem though someone much smarter than me should figure out why it is happening, and if needed post something on the front page about a needed intervention.

It looks like those three files in particular are not claimed by the previous version of linux-firmware, but the new version does claim them.  This leads to the conflict.  Removal of the old package will not help as it isn't registered as owning those files.

EDIT: mailed linux-firmware maintainer for further insight.

Last edited by Trilby (2012-02-12 23:04:31)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#9 2012-02-13 01:40:29

jabooth
Member
Registered: 2011-10-26
Posts: 2

Re: [SOLVED] linux-firmware file conflict

Many thanks for emailing Trilby, and thanks for cleaning up my -Sf/ -Rddn pacman mistake.

Trying to think if there's any special case as to why I might have this problem. I did build the Linux 3.2rc3 kernel back in early December, though since the official release of 3.2 I've just moved back to using the standard kernel.

Is there any chance that the conflict could be to do with that? The pre release kernel is still installed, I'm just not booting from it. I was under the impression that moving between the standard kernel and a one compiled myself was completely independent of pacman etc, is that correct?

Offline

Board footer

Powered by FluxBB