Missing firmware? It could be here - sfs moved to mediafire

Under development: PCMCIA, wireless, etc.
Message
Author
gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated file

#46 Post by gyro »

Updated file:

brcm/brcmfmac4366b-pcie.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#47 Post by gyro »

Updated files:

intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
rtlwifi/rtl8192eu_ap_wowlan.bin
rtlwifi/rtl8192eu_nic.bin
rtlwifi/rtl8192eu_wowlan.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#48 Post by gyro »

Updated files:

ar3k/AthrBT_0x31010100.dfu
ar3k/ramps_0x31010100_40.dfu
i915/skl_dmc_ver1.bin
i915/skl_dmc_ver1_26.bin
intel/dsp_fw_release.bin
intel/dsp_fw_release_v827.bin
intel/dsp_fw_release_v869.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated file

#49 Post by gyro »

Updated file:

hfi1_dc8051.fw

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#50 Post by gyro »

Updated files:

nvidia/gm200/acr/bl.bin
nvidia/gm200/acr/ucode_load.bin
nvidia/gm200/acr/ucode_unload.bin
nvidia/gm200/gr/fecs_bl.bin
nvidia/gm200/gr/fecs_data.bin
nvidia/gm200/gr/fecs_inst.bin
nvidia/gm200/gr/fecs_sig.bin
nvidia/gm200/gr/gpccs_bl.bin
nvidia/gm200/gr/gpccs_data.bin
nvidia/gm200/gr/gpccs_inst.bin
nvidia/gm200/gr/gpccs_sig.bin
nvidia/gm200/gr/sw_bundle_init.bin
nvidia/gm200/gr/sw_ctx.bin
nvidia/gm200/gr/sw_method_init.bin
nvidia/gm200/gr/sw_nonctx.bin
nvidia/gm204/acr/bl.bin
nvidia/gm204/acr/ucode_load.bin
nvidia/gm204/acr/ucode_unload.bin
nvidia/gm204/gr/fecs_bl.bin
nvidia/gm204/gr/fecs_data.bin
nvidia/gm204/gr/fecs_inst.bin
nvidia/gm204/gr/fecs_sig.bin
nvidia/gm204/gr/gpccs_bl.bin
nvidia/gm204/gr/gpccs_data.bin
nvidia/gm204/gr/gpccs_inst.bin
nvidia/gm204/gr/gpccs_sig.bin
nvidia/gm204/gr/sw_bundle_init.bin
nvidia/gm204/gr/sw_ctx.bin
nvidia/gm204/gr/sw_method_init.bin
nvidia/gm204/gr/sw_nonctx.bin
nvidia/gm206/acr/bl.bin
nvidia/gm206/acr/ucode_load.bin
nvidia/gm206/acr/ucode_unload.bin
nvidia/gm206/gr/fecs_bl.bin
nvidia/gm206/gr/fecs_data.bin
nvidia/gm206/gr/fecs_inst.bin
nvidia/gm206/gr/fecs_sig.bin
nvidia/gm206/gr/gpccs_bl.bin
nvidia/gm206/gr/gpccs_data.bin
nvidia/gm206/gr/gpccs_inst.bin
nvidia/gm206/gr/gpccs_sig.bin
nvidia/gm206/gr/sw_bundle_init.bin
nvidia/gm206/gr/sw_ctx.bin
nvidia/gm206/gr/sw_method_init.bin
nvidia/gm206/gr/sw_nonctx.bin
nvidia/gm20b/acr/bl.bin
nvidia/gm20b/acr/ucode_load.bin
nvidia/gm20b/gr/fecs_bl.bin
nvidia/gm20b/gr/fecs_data.bin
nvidia/gm20b/gr/fecs_inst.bin
nvidia/gm20b/gr/fecs_sig.bin
nvidia/gm20b/gr/gpccs_data.bin
nvidia/gm20b/gr/gpccs_inst.bin
nvidia/gm20b/gr/sw_bundle_init.bin
nvidia/gm20b/gr/sw_ctx.bin
nvidia/gm20b/gr/sw_method_init.bin
nvidia/gm20b/gr/sw_nonctx.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#51 Post by gyro »

Updated files:

iwlwifi-3168-21.ucode
iwlwifi-7265D-21.ucode
iwlwifi-8000C-21.ucode
iwlwifi-8265-21.ucode
ti-connectivity/wl18xx-fw-4.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#52 Post by gyro »

Updated files:

amd-ucode/microcode_amd_fam15h.bin
amd-ucode/microcode_amd_fam15h.bin.asc
i915/skl_guc_ver6.bin
i915/skl_guc_ver6_1.bin
intel/dsp_fw_release.bin
intel/dsp_fw_release_v896.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#53 Post by gyro »

Updated files:

amdgpu/carrizo_ce.bin
amdgpu/carrizo_me.bin
amdgpu/carrizo_mec.bin
amdgpu/carrizo_mec2.bin
amdgpu/carrizo_pfp.bin
amdgpu/carrizo_rlc.bin
amdgpu/fiji_ce.bin
amdgpu/fiji_me.bin
amdgpu/fiji_mec.bin
amdgpu/fiji_mec2.bin
amdgpu/fiji_pfp.bin
amdgpu/fiji_sdma.bin
amdgpu/fiji_sdma1.bin
amdgpu/fiji_smc.bin
amdgpu/fiji_uvd.bin
amdgpu/fiji_vce.bin
amdgpu/polaris10_ce.bin
amdgpu/polaris10_mc.bin
amdgpu/polaris10_me.bin
amdgpu/polaris10_mec.bin
amdgpu/polaris10_mec2.bin
amdgpu/polaris10_pfp.bin
amdgpu/polaris10_rlc.bin
amdgpu/polaris10_sdma.bin
amdgpu/polaris10_sdma1.bin
amdgpu/polaris10_smc.bin
amdgpu/polaris10_smc_sk.bin
amdgpu/polaris10_uvd.bin
amdgpu/polaris10_vce.bin
amdgpu/polaris11_ce.bin
amdgpu/polaris11_mc.bin
amdgpu/polaris11_me.bin
amdgpu/polaris11_mec.bin
amdgpu/polaris11_mec2.bin
amdgpu/polaris11_pfp.bin
amdgpu/polaris11_rlc.bin
amdgpu/polaris11_sdma.bin
amdgpu/polaris11_sdma1.bin
amdgpu/polaris11_smc.bin
amdgpu/polaris11_smc_sk.bin
amdgpu/polaris11_uvd.bin
amdgpu/polaris11_vce.bin
amdgpu/stoney_ce.bin
amdgpu/stoney_me.bin
amdgpu/stoney_mec.bin
amdgpu/stoney_pfp.bin
amdgpu/stoney_rlc.bin
amdgpu/tonga_ce.bin
amdgpu/tonga_me.bin
amdgpu/tonga_mec.bin
amdgpu/tonga_mec2.bin
amdgpu/tonga_pfp.bin
amdgpu/tonga_sdma.bin
amdgpu/tonga_sdma1.bin
amdgpu/tonga_smc.bin
amdgpu/topaz_ce.bin
amdgpu/topaz_me.bin
amdgpu/topaz_mec.bin
amdgpu/topaz_pfp.bin
amdgpu/topaz_sdma.bin
amdgpu/topaz_sdma1.bin
amdgpu/topaz_smc.bin
radeon/bonaire_ce.bin
radeon/bonaire_me.bin
radeon/bonaire_mec.bin
radeon/bonaire_pfp.bin
radeon/bonaire_smc.bin
radeon/bonaire_uvd.bin
radeon/hawaii_ce.bin
radeon/hawaii_me.bin
radeon/hawaii_mec.bin
radeon/hawaii_pfp.bin
radeon/hawaii_smc.bin
radeon/hawaii_uvd.bin
radeon/kabini_ce.bin
radeon/kabini_me.bin
radeon/kabini_mec.bin
radeon/kabini_pfp.bin
radeon/kaveri_mec.bin
radeon/kaveri_mec2.bin
radeon/kaveri_pfp.bin
radeon/mullins_ce.bin
radeon/mullins_me.bin
radeon/mullins_mec.bin
radeon/mullins_pfp.bin
radeon/mullins_sdma.bin
radeon/mullins_sdma1.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#54 Post by gyro »

Updated files:

intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
r8a779x_usb3_v3.dlmem

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#55 Post by gyro »

Updated files:

amdgpu/carrizo_uvd.bin
intel/ibt-11-5.ddc
intel/ibt-11-5.sfi

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#56 Post by gyro »

Updated files:

ath10k/QCA6174/hw2.1/board-2.bin
ath10k/QCA6174/hw2.1/firmware-5.bin
ath10k/QCA6174/hw3.0/board-2.bin
ath10k/QCA9377/hw1.0/board-2.bin
ath10k/QCA9377/hw1.0/board.bin
ath10k/QCA9377/hw1.0/firmware-5.bin
radeon/BONAIRE_uvd.bin
radeon/bonaire_uvd.bin
radeon/hawaii_uvd.bin
radeon/kabini_uvd.bin
radeon/kaveri_uvd.bin
radeon/mullins_uvd.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#57 Post by gyro »

This web site will be unavailable until further notice.
gyro

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#58 Post by ally »


User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#59 Post by perdido »

Thank you gyro for posting this. I took your idea and made the sfs, it is available here


T̶h̶i̶s̶ ̶S̶F̶S̶ ̶i̶s̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶t̶h̶r̶o̶u̶g̶h̶ ̶0̶5̶-̶0̶4̶-̶1̶6̶

Please see gyro's latest post for the latest sfs file.

.
Last edited by perdido on Wed 01 Jun 2016, 22:06, edited 2 times in total.

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Updated files

#60 Post by gyro »

Updated files:

amdgpu/carrizo_ce.bin
amdgpu/carrizo_me.bin
amdgpu/carrizo_mec.bin
amdgpu/carrizo_mec2.bin
amdgpu/carrizo_pfp.bin
amdgpu/fiji_ce.bin
amdgpu/fiji_me.bin
amdgpu/fiji_mec.bin
amdgpu/fiji_mec2.bin
amdgpu/fiji_pfp.bin
amdgpu/polaris10_ce.bin
amdgpu/polaris10_mc.bin
amdgpu/polaris10_me.bin
amdgpu/polaris10_mec.bin
amdgpu/polaris10_mec2.bin
amdgpu/polaris10_pfp.bin
amdgpu/polaris10_rlc.bin
amdgpu/polaris10_sdma.bin
amdgpu/polaris10_smc.bin
amdgpu/polaris10_smc_sk.bin
amdgpu/polaris10_uvd.bin
amdgpu/polaris11_ce.bin
amdgpu/polaris11_mc.bin
amdgpu/polaris11_me.bin
amdgpu/polaris11_mec.bin
amdgpu/polaris11_mec2.bin
amdgpu/polaris11_pfp.bin
amdgpu/polaris11_rlc.bin
amdgpu/polaris11_smc.bin
amdgpu/polaris11_smc_sk.bin
amdgpu/polaris11_uvd.bin
amdgpu/stoney_ce.bin
amdgpu/stoney_me.bin
amdgpu/stoney_mec.bin
amdgpu/stoney_pfp.bin
amdgpu/tonga_ce.bin
amdgpu/tonga_me.bin
amdgpu/tonga_mec.bin
amdgpu/tonga_mec2.bin
amdgpu/tonga_pfp.bin
amdgpu/topaz_ce.bin
amdgpu/topaz_me.bin
amdgpu/topaz_mec.bin
amdgpu/topaz_pfp.bin
intel/dsp_fw_release.bin
intel/dsp_fw_release_v927.bin
rt2860.bin
rt2870.bin

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

back again

#61 Post by gyro »

It's back again. Please note the new url, http://www.fishprogs.software/puppy/firmware/.
gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#62 Post by gyro »

perdido wrote:Thank you gyro for posting this. I took your idea and made the sfs, it is available here

http://www.ibm-pc.org/puppy/pup_firmwar ... .05.04.sfs
MD5sum 75af4d5882af76ed368109238cd6ad45
Size is 65.2MB

This SFS is updated through 05-04-16
I'm begining to think that providing an sfs might be the way to go, instead of the directory tree.
I have a problem with ftp'ing symlinks to my online repository, so any updated files that were a symlink, end up being a copy of the target file.
If I create an sfs file directly from my local copy of the git repository, all symlinks remain intact.
I just did this as a test, and the resultant sfs file "firmware_20160524.sfs" is 67,686,400 bytes, probably not a very significant difference.
Also an sfs file can easily be integrated into puppy as an extra-sfs or as a ydrv.

Any thoughts?

gyro

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#63 Post by peebee »

gyro wrote:Any thoughts?
gyro
Hi gyro

I think sfs is a good way to go - but maybe not just 1 big one if that's possible - maybe 1 with the "common" firmware like "big" in http://distro.ibiblio.org/puppylinux/firmware/ but brought up date and then a 2nd with the more exotic?

Do you get any download statistics from your current repository to know what people have been downloading?

Excellent resource for the community though....

Cheers
PeeBee
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#64 Post by gyro »

peebee wrote:I think sfs is a good way to go - but maybe not just 1 big one if that's possible - maybe 1 with the "common" firmware like "big" in http://distro.ibiblio.org/puppylinux/firmware/ but brought up date and then a 2nd with the more exotic?
Thanks for contributing.
But, if I replace the current directory with one or more sfs files, they will all be "just 1 big one", the only difference will be date created, (part of the filename).
The currrent setup already tries to do the "common" v "exotic" thing, and I have no confidence in the selection.
I often wonder how many forum problems, where something just doesn't work on someones computer, are down to the optimal firmware being unavailable because someone else decided it's "exotic".
I'm only interested in providing an "all" alternative.

gyro

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#65 Post by perdido »

gyro wrote:
perdido wrote:Thank you gyro for posting this. I took your idea and made the sfs, it is available here

http://www.ibm-pc.org/puppy/pup_firmwar ... .05.04.sfs
MD5sum 75af4d5882af76ed368109238cd6ad45
Size is 65.2MB

This SFS is updated through 05-04-16
I'm begining to think that providing an sfs might be the way to go, instead of the directory tree.
I have a problem with ftp'ing symlinks to my online repository, so any updated files that were a symlink, end up being a copy of the target file.
If I create an sfs file directly from my local copy of the git repository, all symlinks remain intact.
I just did this as a test, and the resultant sfs file "firmware_20160524.sfs" is 67,686,400 bytes, probably not a very significant difference.
Also an sfs file can easily be integrated into puppy as an extra-sfs or as a ydrv.

Any thoughts?

gyro
Hi gyro,

This thread is important and I hope you keep it going!

Some might not like the size of the sfs but it is a good tool for troubleshooting missing firmware, I think the average user (like me) has an easier time troubleshooting with the sfs instead of trying to identify missing individual firmware. Those running a full install might like a .pet, maybe if you start making the sfs I will do the .pet?

I do not have git installed so initially I did wget of your repository and stripped out the index.html files, have been just updating the individual files from your web site using info provided in this thread, thats why my sfs date coincides with the dates of some of your thread updates.

My current pup_firmware_all_16.05.21.sfs is 68,300,800 bytes(65.1MB). There are 132 duplicate files in my sfs that probably represent the replacement of sym links with target files in your repository and would explain the size difference between our sfs files.

Post Reply