We’re rewarding the question askers & reputations are being recalculated! Read more.
20

In the Linux kernel context, firmware is software which runs on another processor in the system, e.g. a wireless controller, a GPU, a SCSI controller... This software used to be stored in ROM (of various types) attached to the relevant controller, but to reduce costs and make upgrades simpler, controllers now tend to rely on the host operating system to load ...


20

After hours of searching on different resources i ended up solving the problem which was caused by a missing of firmware-realtek the realtek driver . The missing of this firmware can throw different errors prefixed by rtl_nic/ to solve this simply add the official repository Debian firmware-realtek to your /etc/apt/sources.list and make sure you are ...


16

The sudden appearance of this message is rather odd; it suggests your updated firmware is no longer upgrading your CPU’s microcode, whereas the previous firmware you had, did. Weird... (Another possible scenario is that your CPU originally didn’t support TSC deadline at all, and your firmware is now upgrading its microcode to a version which declares support ...


11

Flashing with FreeDOS, one reboot and no removable devices Ensure you are using GRUB2 (check if you have the package grub-pc installed on Ubuntu) Get hold of SYSLINUX's MEMDISK. On Ubuntu, install the package syslinux-common and your memdisk will reside in /usr/lib/syslinux/memdisk Download fdboot.img, save it in your home directory, or some other directory ...


11

Samsung is really, really weird and it took me many hours to figure this one out because it's absolutely counterintuitive. It turned out that I was right with my skepticism of an image provided by Samsung probably actually being suitable to boot from it. Putting the image they offer you on a thumb drive doesn't work. It's not that it's super fast and you ...


9

I have the same issue, I needed to disable gpe16 and gpe17 for kworker to stop hogging the CPU. I followed the recipe found here: http://sudoremember.blogspot.com.au/2013/05/high-cpu-usage-due-to-kworker.html An abbreviated (and corrected, at least for my instance) version is here: $sudo -s #echo "disable" > /sys/firmware/acpi/interrupts/gpe17 #echo "...


8

The iwlwifi driver loads the microcode file for your wifi adapter at startup. If you want to know the version of the blobs you have on your machine, try Andrew Brampton's script. Run: ## Note the firmware may stored in `/usr/lib` ./ucode.py /lib/firmware/iwlwifi-*.ucode And compare the output to your journal (dmesg output). Note that the script works ...


7

You need to enable non-free first: edit /etc/apt/sources.list, and at the end of lines ending with main, add contrib non-free. You'll end up with something like deb http://ftp.fr.debian.org/debian jessie main contrib non-free etc. Then update your repositories and install firmware-realtek: apt-get update && apt-get install firmware-realtek That ...


7

It is not related to any bootloader at all. When a driver uses the kernel's common firmware loading infrastructure to load a firmware file, the kernel can either load the file directly from the standard /lib/firmware directory tree, or it can optionally start an user-space process to handle the firmware load. This user-space process used to be part of the ...


6

First things first: your hostname.urtwn0 file looks good and if you had a mistake in there you'd get completely different error messages. The message urtwn0: failed loadfirmware of file urtwn-rt18192cfwT (error 2) indicates that the firmware isn't installed in the proper location: As explained in loadfirmware(9), this function returns errno style error ...


6

for Seagate 3TB video (ST3000VX000-9YW1): sg_write_buffer -v -m 5 -I <FW file> <dev>


6

These are pre-calibration and calibration files; they are optional, and as you’ve noticed, the device can work fine without them. Calibration data can be obtained in a variety of ways (from EEPROM in the device, from files on disk, from device tree information). I get the impression the “firmware” files are intended for very specific configurations (where ...


6

If you solely get your microcode from intel-microcode, uninstalling it will get rid of the low-level Spectre patches. However, note that this won't prevent firmware (EFI or BIOS) from loading its own microcode updates before the OS boots. To check if Spectre patches are enabled, you can observe the contents of the files in /sys/devices/system/cpu/...


5

Firmware is software that runs on a processor in the device itself, not on the main CPU. Firmware is more likely to be closed source than drivers for a variety of reasons. Firmware has to be made only once, whereas different operating systems require different drivers. Therefore hardware manufacturers have an incentive to allow third parties to write their ...


5

According to this, https://wikidevi.com/wiki/R8712u your chipset does not supports monitor mode. Not all combinations of hardware/software support wifi monitor mode. Like any other functionality implemented in silicon/firmware, be it listening to the media, sending and listening to packets, monitor mode has to be usually implemented by the manufacturer for ...


5

It used to be the case that firmware was stored on the device, either in ROM or in flash. But that’s no longer always the case, and many devices need to have their firmware given to them before they’ll function. This reduces hardware costs and makes it easier to provide firmware updates. Generally speaking the firmware is provided to devices by their driver. ...


5

As Anthony Geoghegan mentions, What is "firmware" in Linux terminology? and Why do some drivers still require firmware? provide useful background. Firmware packages are packages which contain firmware files, i.e. files which contain code which is intended to run on devices in or connected to your system — common examples include wifi chipsets, as ...


4

Only the vendors themselves know the real answer but here are some guesses. I would assume that it's simply because it would make the device more expensive. By requiring the OS to inject firmware at run time they get to avoid the need for non-volatile memory like ROM or Flash on the device. Secondarily, I would assume the vendors might also feel that the ...


4

If anyone is still having problems with this: Look into this post: https://patchwork.kernel.org/patch/9791523/ Kernelwarrior Hans has collected firmware implementations for the bcm43430 from various sources. You can find them here: http://jwrdegoede.danny.cz/brcm-firmware/ or here (if the link is down): https://wolk.wopwop.cc/s/AmPFsOgJdnK4xMU I have ...


4

Gentoo wiki radeon article describes how to include firmware into your kernel binary. The article also includes a table listing firmware binaries required for each GPU model. For your FirePro W2100 (Oland chipset) the table lists following firmware binaries: radeon/oland_ce.bin radeon/oland_mc.bin radeon/oland_me.bin radeon/oland_pfp.bin radeon/oland_rlc....


4

Loadable firmware is typically not "one-shot" installs that are written to flash on the device. The firmware is loaded into volatile storage on the device and needs to be done each time the host computer is turned on. The device does not function before the firmware is loaded. The firmware can be written to RAM on the device, in which case it contains code ...


4

As described on the Wikipedia page: coreboot, formerly known as LinuxBIOS, is a software project aimed at replacing proprietary firmware (BIOS or UEFI) found in most computers with a lightweight firmware designed to perform only the minimum number of tasks necessary to load and run a modern 32-bit or 64-bit operating system. Essentially, it is an ...


3

The error message doesn't indicate that iwlwifi couldn't find a required firmware file; it indicates that it was unable to load a chunk of firmware into the adapter. So iwlwifi found the firmware it was looking for, it just couldn't load (all of) it into the adapter... Generally speaking, when looking for firmware, if you're using your distribution's kernel ...


3

Since file doesn't recognize it, the vendor probably used a custom SquashFS magic signature. I expect that unsquashfs is also giving you an error about not being able to find a valid superblock. Give sasquatch a try; it's a modified version of unsquashfs that attempts to support such vendor hacks.


3

I have successfully flashed a Seagate Barracuda 7200.12 ST31000528AS (1TB SATA) drive with the following method: (Use at your own risk!) Download ISO from Seagate: http://www.seagate.com/staticfiles/support/downloads/firmware/Barracuda12-ALL-CC49.iso mount/extract PH-CC49.ima from .iso file dd the .ima to a USB thumb-drive: dd if=./PH-CC49.ima of=/dev/sdX ...


3

Obviously, it will be difficult to download software if your network is not working. Debian also creates non-free installation images. One of these would probably have been better to use for your hardware. If your Ethernet is currently working with a different free driver, then you can get the rest of the firmware that you may need for your hardware as ...


3

I could swear I had to format the pen to ext2fs last time I installed firmware blobs with the method you describe. However, you do not need to download/install the firmware from a pen with that process, and in fact I do advise another course of action. Whilst the booting asks for it, when you have the needed drivers in the Debian repos, the best course of ...


3

Here's what a colleague shared recently. Thought it might be useful to a wider audience. Marking as a community wiki as I don't share credit for it. Procedure might work for other laptop makes I guess. Visit the driver matrix for your T460p on support.lenovo.com and download the image of the "BIOS Update CD for Windows 10". (I ended up getting the version ...


3

All you can do is ignore those messages as iwlwifi-7265D-26.ucode and iwlwifi-7265D-25.ucode were never released to the linux-firmware git site. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ The iwlmvm module handles the firmware upload and will look for the highest version supported by the kernel, if not found it will ...


3

I also had that problem in Fedora 26. Today they released an update that should solve the issue. Update the packages and repeat the procedure you have done before: sudo fwupdmgr refresh sudo fwupdmgr update


Only top voted, non community-wiki answers of a minimum length are eligible