Arch Linux

pecan

Member

Registered: 2007-04-06

Posts: 93

Upgrade package conflicts

I'm getting an error when I go pacman -Syu

error: could not prepare transaction                                                                      
error: failed to commit transaction (conflicting files)                                                   
filesystem: /etc/modprobe.d/usb-load-ehci-first.conf exists in filesystem                                 
kdemod-kdebase-workspace: /usr/share/kde4/services/kwin/cubeslide_config.desktop exists in filesystem     
kernel26-firmware: /lib/firmware/3com/3C359.bin exists in filesystem                                      
kernel26-firmware: /lib/firmware/3com/typhoon.bin exists in filesystem                                    
kernel26-firmware: /lib/firmware/advansys/3550.bin exists in filesystem                                   
kernel26-firmware: /lib/firmware/advansys/38C0800.bin exists in filesystem                                
kernel26-firmware: /lib/firmware/advansys/38C1600.bin exists in filesystem                                
kernel26-firmware: /lib/firmware/advansys/mcode.bin exists in filesystem                                  
kernel26-firmware: /lib/firmware/av7110/bootcode.bin exists in filesystem                                 
kernel26-firmware: /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw exists in filesystem                         
kernel26-firmware: /lib/firmware/bnx2/bnx2-mips-09-4.6.17.fw exists in filesystem                         
kernel26-firmware: /lib/firmware/bnx2/bnx2-rv2p-06-4.6.16.fw exists in filesystem                         
kernel26-firmware: /lib/firmware/bnx2/bnx2-rv2p-09-4.6.15.fw exists in filesystem                         
kernel26-firmware: /lib/firmware/cis/LA-PCM.cis exists in filesystem                                      
kernel26-firmware: /lib/firmware/cxgb3/t3fw-7.1.0.bin exists in filesystem                                
kernel26-firmware: /lib/firmware/myricom/lanai.bin exists in filesystem                                   
kernel26-firmware: /lib/firmware/ositech/Xilinx7OD.bin exists in filesystem                               
kernel26-firmware: /lib/firmware/qlogic/1040.bin exists in filesystem                                     
kernel26-firmware: /lib/firmware/qlogic/12160.bin exists in filesystem                                    
kernel26-firmware: /lib/firmware/qlogic/1280.bin exists in filesystem                                     
kernel26-firmware: /lib/firmware/qlogic/isp1000.bin exists in filesystem                                  
kernel26-firmware: /lib/firmware/tehuti/bdx.bin exists in filesystem                                      
kernel26-firmware: /lib/firmware/yam/1200.bin exists in filesystem                                        
kernel26-firmware: /lib/firmware/yam/9600.bin exists in filesystem                                        
kernel26-firmware: /lib/firmware/yamaha/yss225_registers.bin exists in filesystem
udev: /etc/modprobe.d/framebuffer_blacklist.conf exists in filesystem
module-init-tools: /etc/modprobe.d/modprobe.conf exists in filesystem
module-init-tools: /usr/share/man/man5/depmod.conf.5.gz exists in filesystem
module-init-tools: /usr/share/man/man5/modprobe.conf.5.gz exists in filesystem
module-init-tools: /usr/share/man/man5/modules.dep.5.gz exists in filesystem
module-init-tools: /usr/share/man/man8/depmod.8.gz exists in filesystem
module-init-tools: /usr/share/man/man8/insmod.8.gz exists in filesystem
module-init-tools: /usr/share/man/man8/lsmod.8.gz exists in filesystem
module-init-tools: /usr/share/man/man8/modinfo.8.gz exists in filesystem
module-init-tools: /usr/share/man/man8/modprobe.8.gz exists in filesystem
module-init-tools: /usr/share/man/man8/rmmod.8.gz exists in filesystem
libidn: /usr/lib/libidn.so.11.5.44 exists in filesystem
licenses: /usr/share/licenses/common/FDL exists in filesystem
licenses: /usr/share/licenses/common/GPL exists in filesystem
licenses: /usr/share/licenses/common/GPL2/license.txt exists in filesystem
licenses: /usr/share/licenses/common/LGPL exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_hal.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_pci.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_amrr.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_minstrel.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_onoe.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/ath_rate_sample.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_acl.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_ccmp.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_scan_ap.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_scan_sta.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_tkip.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_wep.ko exists in filesystem
madwifi: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/madwifi/wlan_xauth.ko exists in filesystem
ndiswrapper: /lib/modules/2.6.30-ARCH/kernel/drivers/net/wireless/ndiswrapper/ndiswrapper.ko exists in filesystem
Errors occurred, no packages were upgraded.

I recently downloaded the nvidia driver and it compiled a kernel module. Not to great at solving these kinds of problems? Can anyone see the issue?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Upgrade package conflicts

Read this: http://bbs.archlinux.org/viewtopic.php?id=56373

sand_man

Member

From: Australia

Registered: 2008-06-10

Posts: 2,164

Re: Upgrade package conflicts

If it's kernel26-firmware then you are probably ok to force the install...but please get a second opinion. (I would force it but that's just me )

---