Author |
Message |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Mon 12 Jan 2015, 11:00 Post subject:
Missing firmware? It could be here - sfs moved to mediafire Subject description: Use alternate Linux firmware direct download repository. |
|
Edit:
My firmware file repository is about to disappear.
Please use this alternate site, http://anduin.linuxfromscratch.org/BLFS/linux-firmware,
to acces the files from http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git.
The firmware sfs files have now moved to
http://www.mediafire.com/folder/k2j223jzddy9x/firmware (150MB).
Simply download and use as an adrv, ydrv or fdrv.
I no longer download this firmware repository, http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git,
and I no longer install it here, http://www.fishprogs.software/puppy/firmware/.
Some folk using modern kernels are having problems with some hardware, because the required firmware is not in puppy.
There are 2 reasons for this:
1) The commonly used firmware '.tar.bz2' files are now almost 6 months old.
2) The commonly used 'cut' version does not contain a significant number of firmware files.
Note1: This directory of firmware corresponds to the "/lib/firmware/" directory in puppy.
Note2: It's not pretty, because it's just the web-server generating an index of the directory.
Question: Why is the firmware distributed as part of the kernel?
It's not produced by compiling the kernel. It's just copied from one of the '.tar.bz2' files.
gyro
Edit: Should have included information about how I expect folk might use this repository in an ad-hoc manner. So here is an example of using it on an ether-net device.
1) I found I had a problem when I got some output from the console command: Code: | # dmesg | grep 'firmware' | 2) If you are lucky, the output from "dmesg" will also tell you the name of the firmware that failed to load.
In my case it didn't so I had to make a guess based on it being identified as an "RTL8168g".
3) Open the repository in a browser and find the required firmware file and download it. In my case I found 3 likely files in 'rtl_nic/'; 'rtl8168g-1.fw', 'rtl8168g-2.fw' and 'rtl8168g-3.fw', so I downloaded all 3.
4) Copy the downloaded firmware file to '/lib/firmware', making sure that you put it in any corresponding sub-directory. Since the file I was trying 'rtl8168g-3.fw' was contained in the 'rtl_nic' subdirectory of the repository, I copied it to '/lib/firmware/rtl_nic/rtl8168g-3.fw'.
5) Reboot and see if "dmesg" is now clean. In my case it wasn't so I tried again with 'rtl8168g-2.fw'. And that worked.
Last edited by gyro on Thu 25 Apr 2019, 10:32; edited 20 times in total
|
Back to top
|
|
 |
ally

Joined: 19 May 2012 Posts: 1983 Location: lincoln, uk
|
Posted: Mon 12 Jan 2015, 23:08 Post subject:
|
|
mirror mirrored here:
http://archive.org/details/Puppy_linux_firmware_repository
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Tue 13 Jan 2015, 04:00 Post subject:
|
|
@ally
Thanks.
gyro
|
Back to top
|
|
 |
rufwoof

Joined: 24 Feb 2014 Posts: 3725
|
Posted: Tue 13 Jan 2015, 15:31 Post subject:
|
|
Noob question : My /lib/firmware folder is around 2.5MB, that complete set as presented by gyro is around 80MB. If I merge/replace my existing /lib/firmware with that more complete set and then remaster is that all that is required for the newly remastered version to be able to better placed to boot/work across a wider range of hardware/devices? Or is firmware only part of it and something else has to accompany the firmware?
TIA
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Wed 14 Jan 2015, 08:16 Post subject:
|
|
First post has been edited to include an example of how I envisioned the repository might be used.
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Wed 14 Jan 2015, 08:17 Post subject:
|
|
rufwoof wrote: | Noob question : My /lib/firmware folder is around 2.5MB, that complete set as presented by gyro is around 80MB. If I merge/replace my existing /lib/firmware with that more complete set and then remaster is that all that is required for the newly remastered version to be able to better placed to boot/work across a wider range of hardware/devices? | Yes, you could do that, and I have considered making an sfs file for such a purpose. But I envisioned a more ad-hock usage when I uploaded the firmware. See the edit of the first post.
rufwoof wrote: | Or is firmware only part of it and something else has to accompany the firmware? | Firmware runs in the device, and is therefore not actually part of the kernel. But newer drivers, which are part of the kernel, may expect newer firmware to be available. So devices that worked perfectly in an older kernel, can sometimes have firmware problems with a newer kernel.
gyro
|
Back to top
|
|
 |
rufwoof

Joined: 24 Feb 2014 Posts: 3725
|
Posted: Wed 14 Jan 2015, 09:39 Post subject:
|
|
Thanks.
I've dropped (merged) it all into lib/firmware and remastered using lzop level 1 compression rather than leaving puppy sfs uncompressed and rebooted that puppy and it now uses less memory but has all 80MB of firmware available to it rather than the 2.5MB of firmware previously to hand.
Yes I know - wasteful of memory, but with GB's common nowadays 80MB odd isn't missed IMO.
Thanks again.
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Sat 17 Jan 2015, 13:23 Post subject:
Update rtlwifi/rtl8192eefw.bin |
|
The github repository has been updated with a new version of "rtlwifi/rtl8192eefw.bin".
I have uploaded the new version of "rtlwifi/rtl8192eefw.bin" to my site.
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Mon 02 Feb 2015, 09:40 Post subject:
Updated Marvell firmware - mrvl/* |
|
Uploaded updated Marvell firmware, replaced all files in "mrvl/".
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Tue 10 Feb 2015, 12:03 Post subject:
Update intel and iwlwifi |
|
Update "/intel/*" and "iwlwifi-*-12.ucode" firmware.
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Fri 27 Feb 2015, 10:50 Post subject:
Updated to current |
|
Updated files:
cbfw-3.2.5.1.bin
ct2fw-3.2.5.1.bin
ctfw-3.2.5.1.bin
iwlwifi-3160-10.ucode
iwlwifi-7260-10.ucode
iwlwifi-7265-10.ucode
iwlwifi-7265D-10.ucode
qat_895xcc.bin
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Sat 28 Feb 2015, 07:04 Post subject:
updated rtl_nic |
|
In directory "rtl_nic" updated files:
rtl8107e-1.fw
rtl8107e-2.fw
rtl8168h-1.fw
rtl8168h-2.fw
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Sun 08 Mar 2015, 09:38 Post subject:
Updated files: |
|
nvidia/tegra124/xusb.bin
htc_7010.fw
htc_9271.fw
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Thu 12 Mar 2015, 09:24 Post subject:
Updated files: |
|
iwlwifi-3160-10.ucode
iwlwifi-7260-10.ucode
iwlwifi-7265-10.ucode
iwlwifi-7265D-10.ucode
gyro
|
Back to top
|
|
 |
gyro
Joined: 28 Oct 2008 Posts: 1799 Location: Brisbane, Australia
|
Posted: Thu 19 Mar 2015, 19:08 Post subject:
Updated files: |
|
In directory 'radeon', updated files:
kaveri_mec2.bin
kaveri_mec.bin
gyro
|
Back to top
|
|
 |
|