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

[gyro]

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

[gyro]

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

[peebee]

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

[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?

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

[perdido]

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.

[gyro]

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.

That's the sort of thing that got me thinking more seriously about an sfs.
"Download this largish .sfs file and rename it as an adrv or ydrv and reboot", is not a terribly difficult process to explain in the forum.

If I do this, I will be producing only sfs files.
In a full install all that needs to be done is unsquashfs it, and then replace the "/lib/firmware" directory in the system with the "lib/firmware" directory created by unsquashfs.

gyro

[gyro]

Now available as an ".sfs" file from http://www.fishprogs.software/puppy/firmware-sfs/ (64.5MiB).
Simply download and use as an adrv, ydrv or fdrv.
gyro

[gyro]

Updated files:

cxgb4/t4fw-1.15.37.0.bin
cxgb4/t4fw.bin
cxgb4/t5fw-1.15.37.0.bin
cxgb4/t5fw.bin
qed/qed_init_values_zipped-8.10.5.0.bin

Also, new ".sfs" file uploaded.

gyro

[gyro]

Updated files:

intel/dsp_fw_bxtn.bin
intel/dsp_fw_bxtn_v430.bin

Also, new ".sfs" file uploaded.

gyro

[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

Also, new ".sfs" file uploaded.

gyro

[gyro]

Updated file:

intel/fw_sst_22a8.bin

Also, new ".sfs" file uploaded.

gyro

[gyro]

Updated files:

intel/ibt-11-5.sfi
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
intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
radeon/bonaire_k_smc.bin
radeon/hainan_k_smc.bin
radeon/hawaii_k_smc.bin
radeon/oland_k_smc.bin
radeon/pitcairn_k_smc.bin
radeon/tahiti_k_smc.bin
radeon/verde_k_smc.bin

Also, new ".sfs" file uploaded.

gyro

[gyro]

Updated files:

amdgpu/polaris10_uvd.bin
amdgpu/polaris11_uvd.bin
intel/dsp_fw_release.bin
intel/dsp_fw_release_v948.bin
intel/ibt-11-16.ddc
intel/ibt-11-16.sfi
ti-connectivity/wl18xx-fw-4.bin

Also, new ".sfs" file uploaded.

gyro

[gyro]

Updated files:

intel/dsp_fw_bxtn.bin
intel/dsp_fw_bxtn_v702.bin

Also, new sfs uploaded.

gyro

[gyro]

Modified files:

i915/bxt_dmc_ver1.bin
i915/bxt_dmc_ver1_04.bin
i915/bxt_dmc_ver1_05.bin
i915/bxt_dmc_ver1_06.bin
i915/bxt_dmc_ver1_07.bin
i915/kbl_dmc_ver1.bin
i915/kbl_dmc_ver1_01.bin
i915/skl_dmc_ver1_23.bin
i915/skl_guc_ver1.bin
i915/skl_guc_ver1.bin
i915/skl_guc_ver1_1059.bin
i915/skl_guc_ver4.bin
i915/skl_guc_ver4.bin
i915/skl_guc_ver4_3.bin
intel/dsp_fw_release.bin
intel/dsp_fw_release_v951.bin
intel/ibt-11-16.ddc
intel/ibt-11-16.sfi
intel/ibt-12-16.ddc
intel/ibt-12-16.sfi
vpu_d.bin
vpu_p.bin

Uploaded:
linux_firmware_20160712.sfs

gyro

[jlst]

I wrote a somewhat long message but when I hit the submit button i was already logged out, so this one is shorter.

gyro, your server does not accept wget, i think it's to prevent abuse..

I have a firmware package that may contain some more duplicates since the last update and synchronization with your package, but it also has extra firmware i gathered from various sources... 78mb xz compressed. I'll probably upload it tomorrow, in case you want to check it out.

i'm writing a script to download and install the sfs as the fdrv then prompt to restart, it should have a .md5.txt or .version file to detect changes and redownload.... that's the idea.

[gyro]

gyro, your server does not accept wget, i think it's to prevent abuse..

I have no control over that, it's a commercial web hosting company. I use curl to upload the firmware.

I have a firmware package that may contain some more duplicates since the last update and synchronization with your package, but it also has extra firmware i gathered from various sources... 78mb xz compressed.

My firmware stuff simply makes the linux-firmware site more easily accessible to puppy users. It does not attempt to be a complete repository of all firmware.

gyro

[gyro]

Updated files:

amdgpu/carrizo_vce.bin
amdgpu/fiji_vce.bin
amdgpu/tonga_vce.bin
intel/dsp_fw_kbl.bin
intel/dsp_fw_kbl_v701.bin
iwlwifi-3160-17.ucode
iwlwifi-3168-22.ucode
iwlwifi-7260-17.ucode
iwlwifi-7265-17.ucode
iwlwifi-7265D-17.ucode
iwlwifi-7265D-22.ucode
iwlwifi-8000C-22.ucode
iwlwifi-8265-22.ucode
nvidia/gp100/acr/bl.bin
nvidia/gp100/acr/ucode_load.bin
nvidia/gp100/acr/ucode_unload.bin
nvidia/gp100/gr/fecs_bl.bin
nvidia/gp100/gr/fecs_data.bin
nvidia/gp100/gr/fecs_inst.bin
nvidia/gp100/gr/fecs_sig.bin
nvidia/gp100/gr/gpccs_bl.bin
nvidia/gp100/gr/gpccs_data.bin
nvidia/gp100/gr/gpccs_inst.bin
nvidia/gp100/gr/gpccs_sig.bin
nvidia/gp100/gr/sw_bundle_init.bin
nvidia/gp100/gr/sw_ctx.bin
nvidia/gp100/gr/sw_method_init.bin
nvidia/gp100/gr/sw_nonctx.bin
rockchip/dptx.bin

sfs:
linux_firmware_20160715.sfs

gyro

[gyro]

Updated files:

rockchip/dptx.bin
usbduxsigma_firmware.bin

linux_firmware_20160729.sfs

gyro

[ahoppin]

> Now available as an ".sfs" file from http://www.fishprogs.software/
> puppy/firmware-sfs/ (64.5MiB).
> Simply download and use as an adrv, ydrv or fdrv.

Sorry to display my ignorance, but what are adrv, ydrv, and fdrv? And how would I use them?

Thanks!