You are not logged in.

#1 2010-02-24 12:30:41

Ashren
Member
From: Denmark
Registered: 2007-06-13
Posts: 1,229
Website

Replacing firmware from kernel 2.6.32 with firmware from 2.6.31?

It get this error when installing kernel26-xen-dom0:

 pacman -U /tmp/packer-1000/kernel26-xen-dom0/kernel26-xen-dom0/kernel26-xen-dom0-2.6.31.9-5-x86_64.pkg.tar.gz 
loading package data...
checking dependencies...
(1/1) checking for file conflicts                   [###########################################################################################] 100%
error: failed to prepare transaction (conflicting files)
kernel26-xen-dom0: /lib/firmware/3com/typhoon.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/acenic/tg1.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/acenic/tg2.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/adaptec/starfire_rx.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/adaptec/starfire_tx.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/advansys/3550.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/advansys/38C0800.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/advansys/38C1600.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/advansys/mcode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/atmsar11.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/av7110/bootcode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/cis/3CCFEM556.cis exists in filesystem
kernel26-xen-dom0: /lib/firmware/cis/3CXEM556.cis exists in filesystem
kernel26-xen-dom0: /lib/firmware/cis/LA-PCM.cis exists in filesystem
kernel26-xen-dom0: /lib/firmware/cpia2/stv0672_vp4.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/cxgb3/t3b_psram-1.1.0.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/cxgb3/t3c_psram-1.1.0.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/cxgb3/t3fw-7.4.0.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/dabusb/bitstream.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/dabusb/firmware.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/e100/d101m_ucode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/e100/d101s_ucode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/e100/d102e_ucode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/edgeport/boot.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/edgeport/boot2.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/edgeport/down.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/edgeport/down2.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/edgeport/down3.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi26/bitstream.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi26/firmware.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi26/loader.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi62/bitstream.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi62/loader.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi62/midi.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/emi62/spdif.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/ess/maestro3_assp_kernel.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/ess/maestro3_assp_minisrc.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/kaweth/new_code.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/kaweth/new_code_fix.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/kaweth/trigger_code.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/kaweth/trigger_code_fix.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/keyspan_pda/keyspan_pda.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/keyspan_pda/xircom_pgs.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/korg/k1212.dsp exists in filesystem
kernel26-xen-dom0: /lib/firmware/mts_cdma.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/mts_edge.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/mts_gsm.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/ositech/Xilinx7OD.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/qlogic/1040.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/qlogic/12160.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/qlogic/1280.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/sun/cassini.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/tehuti/bdx.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/ti_3410.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/ti_5052.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/tigon/tg3.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/tigon/tg3_tso.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/tigon/tg3_tso5.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/ttusb-budget/dspbootcode.bin exists in filesystem
kernel26-xen-dom0: /lib/firmware/vicam/firmware.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/whiteheat.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/whiteheat_loader.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/yamaha/ds1_ctrl.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/yamaha/ds1_dsp.fw exists in filesystem
kernel26-xen-dom0: /lib/firmware/yamaha/ds1e_ctrl.fw exists in filesystem

errors occurred, no packages were upgraded.

I dont feel completely confident that is is a good idea to overwrite firmware files from kernel 2.6.31 . Is it safe?

Offline

#2 2010-02-24 12:41:48

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,556

Re: Replacing firmware from kernel 2.6.32 with firmware from 2.6.31?

are you using any hardware listed here ? in any case, it should be harmless.

Offline

#3 2010-02-24 13:45:48

Ashren
Member
From: Denmark
Registered: 2007-06-13
Posts: 1,229
Website

Re: Replacing firmware from kernel 2.6.32 with firmware from 2.6.31?

Ok, thanks.

Offline

Board footer

Powered by FluxBB