if you try to install debian-7.5.0-amd64-netinst.iso that you can download here on a lower power (50watts with 2x disks and „normal“ power supply) ASRock E350M1
if not found check here: http://ftp.acc.umu.se/debian-cd/
you will get a message like: „firmware for your network card not found – please insert usb stick with the firmware file or you will have no network“
1. format usb stick FAT32
2. you need to download only one file in the root directory of your usb stick which is: rtl8168e-2.fw.tar.gz
3. untar it: tar fxvz rtl8168e-2.fw.tar.gz
then attach the usb stick to your computer running the debian setup and scan for firmware should automatically detect the firmware in the root of your fat32-usb stick.
after you are done with the installation, you can add non-free repository to the sources.list like this:
echo "deb http://ftp.de.debian.org/debian/ wheezy main contrib non-free" >> /etc/apt/sources.list
Update your repository cache and install the missing firmware.
apt-get update # get list of packages apt-get install firmware-linux-nonfree firmware-realtek # install non-free firmware from repo
Then you’re all set to do a reboot in normal mode. You now have a functioning Debian.
* Realtek RTL8192E boot code (RTL8192E/boot.img) * Realtek RTL8192E init data (RTL8192E/data.img) * Realtek RTL8192E main code (RTL8192E/main.img) * Realtek RTL8192SU firmware, version 902B (RTL8192SU/rtl8192sfw.bin) * Realtek RTL8105E-1 firmware (rtl_nic/rtl8105e-1.fw) * Realtek RTL8111D-1/RTL8168D-1 firmware (rtl_nic/rtl8168d-1.fw) * Realtek RTL8111D-2/RTL8168D-2 firmware (rtl_nic/rtl8168d-2.fw) * Realtek RTL8168E-1 firmware (rtl_nic/rtl8168e-1.fw) * Realtek RTL8168E-2 firmware (rtl_nic/rtl8168e-2.fw) * Realtek RTL8168E-3 firmware, version 0.0.4 (rtl_nic/rtl8168e-3.fw) * Realtek RTL8168F-1 firmware, version 0.0.4 (rtl_nic/rtl8168f-1.fw) * Realtek RTL8168F-2 firmware, version 0.0.4 (rtl_nic/rtl8168f-2.fw) * Realtek RTL8192CE/RTL8188CE firmware, version 4.816.2011 (rtlwifi/rtl8192cfw.bin) * Realtek RTL8192CE/RTL8188CE B-cut firmware, version 4.816.2011 (rtlwifi/rtl8192cfwU_B.bin) * Realtek RTL8188CE A-cut firmware, version 4.816.2011 (rtlwifi/rtl8192cfwU.bin) * Realtek RTL8192CU/RTL8188CU firmware (rtlwifi/rtl8192cufw.bin) * Realtek RTL8192DE firmware (rtlwifi/rtl8192defw.bin) * Realtek RTL8192SE/RTL8191SE firmware (rtlwifi/rtl8192sefw.bin) * Realtek RTL8192SU/RTL8712U firmware (rtlwifi/rtl8712u.bin)
extract this to the root of your fat32-usb-stick.
6.4. Loading Missing Firmware
As described in Section 2.2, “Devices Requiring Firmware”, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features.
If a device driver requests firmware that is not available,
will display a dialog offering to load the missing firmware. If this option is selected,
will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (
) and the driver module will be reloaded.
Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. On i386 and amd64 firmware can also be loaded from an MMC or SD card.
Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation.
only prompts for firmware needed by kernel modules loaded during the installation. Not all drivers are included in
, in particular radeon is not, so this implies that the capabilities of some devices may be no different at the end of the installation from what they were at the beginning. Consequently, some of your hardware may not be being used to its full potential. If you suspect this is the case, or are just curious, it is not a bad idea to check the output of the dmesg command on the newly booted system and search for “firmware”.
Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named
of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation.
Tarballs and zip files containing current packages for the most common firmware are available from:
Just download the tarball or zip file for the correct release and unpack it to the file system on the medium.
If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:
It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor.
Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew.
If the firmware was loaded from a firmware package,
will also install this package for the installed system and will automatically add the non-free section of the package archive in APT’s
. This has the advantage that the firmware should be updated automatically if a new version becomes available.
If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually.
If the firmware was loaded from loose firmware files, the firmware copied to the installed system will not be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed.
use unofficial non-free iso – that allready has the drivers on it. (Richard Stallman IS VERY MUCH AGAINST ANYTHING THAT IS NON-FREE) For good reasons of privacy… because after all a backdoor in your network card firmware could really compromise your system in terms of security and privacy.
Unofficial non-free images including firmware packages:
recommendation: ALWAYS GO FOR THE MINIMAL and load packages during setup straight from the internet…
Parent Directory - MD5SUMS 2017-01-17 11:09 66 MD5SUMS.sign 2017-01-17 11:10 819 SHA1SUMS 2017-01-17 11:09 74 SHA1SUMS.sign 2017-01-17 11:10 819 SHA256SUMS 2017-01-17 11:09 98 SHA256SUMS.sign 2017-01-17 11:10 819 SHA512SUMS 2017-01-17 11:09 162 SHA512SUMS.sign 2017-01-17 11:10 819 firmware-8.7.1-i386-netinst.iso 2017-01-16 11:09 335M
Here are some extra images, equivalent to the normal images we produce regularly except in that they also include non-free firmware to make things easier on some systems requiring proprietary but redistributable firmware. See http://wiki.debian.org/Firmware for more details.
There are two types of image here:
- „netinst“ install CDs that also include firmware to make installation easier
- live images including firmware packages pre-installed
Parent Directory - 8.7.1+nonfree/ 2017-01-17 11:11 - 8.7.1-live+nonfree/ 2017-01-17 11:11 - archive/ 2017-02-01 23:50 - current-live/ 2017-01-17 11:11 - current/ 2017-01-17 11:11 - daily-builds-debian-edu/ 2012-07-22 21:57 - daily-builds/ 2015-04-27 18:30 - stretch_di_rc1/ 2017-01-14 00:53 - stretch_di_rc2/ 2017-02-01 23:49 - stretch_di_rc3/ 2017-04-09 23:04 - weekly-builds/ 2017-04-24 10:37 - weekly-live-builds/ 2017-04-25 10:25 -