Missing firmware? It could be here - sfs moved to mediafire
Posted: Mon 12 Jan 2015, 15:00
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 ... rmware.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 ... rmware.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: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.
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 ... rmware.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 ... rmware.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: Select all
# dmesg | grep 'firmware'
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.