Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Arch Linux mkinitcpio: Possibly missing firmware for module

Problem

In Arch Linux mkinitcpio -p linux

shows

Possibly missing firmware for module: aic94xx
 Possibly missing firmware for module: wd719x

Solve

git clone https://aur.archlinux.org/aic94xx-firmware.git
cd aic94xx-firmware
makepkg -sri
git clone https://aur.archlinux.org/wd719x-firmware.git
cd wd719x-firmware
makepkg -sri

and then mkinitcpio -p linux again.

Reference

https://wiki.archlinux.org/index.php/Mkinitcpio

@technotherion

This comment has been minimized.

Copy link

@technotherion technotherion commented Feb 21, 2018

As a note to myself (and others) because I'm sure I'll be here again and will have forgotten a command or two.

Fresh arch install - "you can not install as root"

  1. make sure sudo, base-devel, and vim are installed
  2. useradd -m (user) then passwd (user)
  3. visudo
  4. Add the following line into the file: (user) ALL=(ALL) ALL
  5. Escape vim: Hit escape, then type :wq and enter.
  6. su (user) -
  7. try the gist instructions again, this time cloning the directory into your home folder.
@Tknott95

This comment has been minimized.

Copy link

@Tknott95 Tknott95 commented Aug 12, 2018

Will have fix on my ghub gists as well
yoaurt -S aic94xx-firmware wd719x-firmware

@rigred

This comment has been minimized.

Copy link

@rigred rigred commented Nov 8, 2018

Of importance is that this module is entirely unnecessary for most users.
It's simply a warning as these are commonly used modules for SAS/SCSI Disk Controllers in server hardware.

It's not recommended that you install these if you don't have such hardware in your system.
If you don't know what they are, don't install them.
Because if you did know what they are you'd know if you needed them to get your disks working.

@noraj

This comment has been minimized.

Copy link

@noraj noraj commented Jan 4, 2019

@rigred is totally right.

  • aic94xx-firmware: Adaptec SAS 44300, 48300, 58300 Sequencer Firmware for AIC94xx driver
  • wd719x-firmware: Driver for Western Digital WD7193, WD7197 and WD7296 SCSI cards

Most people won't have SAS/SCSI Disk Controllers, so just ignore those warnings and don't install those drivers.

Also RTFM Arch Wiki: Possibly missing firmware for module XXXX:

When initramfs are being rebuild after a kernel update, you might get these or similar warnings:

==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x 

These appear to any Arch Linux users, especially those who have not installed these firmware modules. If you do not use hardware which uses these firmwares you can safely ignore this message.

@Vrak

This comment has been minimized.

Copy link

@Vrak Vrak commented Mar 16, 2019

Can someone explain why we're seeing warnings about firmware for hardware that's not even installed?

@syaorandroid

This comment has been minimized.

Copy link

@syaorandroid syaorandroid commented Apr 22, 2019

I just execute the command: yaourt -S aic94xx-firmware wd719x-firmware, and it's all right!

@teethgrinder

This comment has been minimized.

Copy link

@teethgrinder teethgrinder commented Apr 22, 2019

@syaoandroid stop using yaourt , but it is not being developed anymore. https://itsfoss.com/best-aur-helpers/

@EgidioCaprino

This comment has been minimized.

Copy link

@EgidioCaprino EgidioCaprino commented Mar 14, 2020

Of importance is that this module is entirely unnecessary for most users.
It's simply a warning as these are commonly used modules for SAS/SCSI Disk Controllers in server hardware.

It's not recommended that you install these if you don't have such hardware in your system.
If you don't know what they are, don't install them.
Because if you did know what they are you'd know if you needed them to get your disks working.

Thank you 🙏

@codydg

This comment has been minimized.

Copy link

@codydg codydg commented Apr 21, 2020

Can someone explain why we're seeing warnings about firmware for hardware that's not even installed?

I would also like to know this. I've found myself at this page for two different arch installations on very different hardware, so it'd be nice to know why it thinks I need these drivers. I'm sure there are thousands more drivers that I don't need, so why does it warn about these 2? May expose a bug somewhere...

@NiklasBeierl

This comment has been minimized.

Copy link

@NiklasBeierl NiklasBeierl commented Apr 25, 2020

Can someone explain why we're seeing warnings about firmware for hardware that's not even installed?

I would also like to know this. I've found myself at this page for two different arch installations on very different hardware, so it'd be nice to know why it thinks I need these drivers. I'm sure there are thousands more drivers that I don't need, so why does it warn about these 2? May expose a bug somewhere...

Exactly my concern. Installing on Dell XPS 13 2 in 1 7390.

@gridley

This comment has been minimized.

Copy link

@gridley gridley commented May 26, 2020

Same here, would be nice if someone fixed the warnings.

@sci4me

This comment has been minimized.

Copy link

@sci4me sci4me commented Jun 19, 2020

Yeah I too would like to know why we would be getting these warnings on machines that don't have the hardware that firmware is for. And it's always those same two: wd719x and aic94xx. Am I crazy to label this as a bug? I mean, it's a false warning...

@Thomashighbaugh

This comment has been minimized.

Copy link

@Thomashighbaugh Thomashighbaugh commented Jun 22, 2020

I mean, it's a false warning...

Exactly what I am thinking here, especially because the number of users in need of the drivers in reality is smaller than the number of users alerted to the needs that makes it a false positive aka error/bug

@Isti115

This comment has been minimized.

Copy link

@Isti115 Isti115 commented Jun 24, 2020

Since reactions are not an options for gist comments, here is a textual +1 from me for removing these warnings, I think that they are confusing.

@asdiasx

This comment has been minimized.

Copy link

@asdiasx asdiasx commented Jun 27, 2020

Since reactions are not an options for gist comments, here is a textual +1 from me for removing these warnings, I think that they are confusing.

Same here! +1...

@kmanwar89

This comment has been minimized.

Copy link

@kmanwar89 kmanwar89 commented Sep 30, 2020

+1

@Starslayerx

This comment has been minimized.

Copy link

@Starslayerx Starslayerx commented Nov 1, 2020

+1

@jmelahman

This comment has been minimized.

Copy link

@jmelahman jmelahman commented Nov 28, 2020

When people say "ignore these" do they mean "ignore in your head" or is there a way to explicitly suppress warnings for individual modules?

I've since simply installed the necessary firmware (to my chagrin) so that I don't waste time re-discovering these can just be ignored next time.

@codydg

This comment has been minimized.

Copy link

@codydg codydg commented Nov 28, 2020

When people say "ignore these" do they mean "ignore in your head" or is there a way to explicitly suppress warnings for individual modules?

I've since simply installed the necessary firmware (to my chagrin) so that I don't waste time re-discovering these can just be ignored next time.

My understanding is they mean "ignore in your head" but if there is a way to suppress them without installing the drivers I'm unaware of it.

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Jan 11, 2021

It is already mentioned above that these "missing firmwares" are of any use to servers that use SAS/SCSI Disk Controllers.
How many years ago you last used SAS/SCSI Disk Controllers?
For those above that +1 the others that installed the "missing firmwares" for never used hardware:
Congratulations, you played yourselves.

@Thomashighbaugh

This comment has been minimized.

Copy link

@Thomashighbaugh Thomashighbaugh commented Jan 11, 2021

It is already mentioned above that these "missing firmwares" are of any use to servers that use SAS/SCSI Disk Controllers.
How many years ago you last used SAS/SCSI Disk Controllers?
For those above that +1 the others that installed the "missing firmwares" for never used hardware:
Congratulations, you played yourselves.

I don't know that's its quite as serious as all that no one is going to see any significant reductions in functionality from the missing firmware being present on their system but you're dead on that it's essentially useless to the vast majority and that will only on become more true as time marches om

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Jan 11, 2021

It is already mentioned above that these "missing firmwares" are of any use to servers that use SAS/SCSI Disk Controllers.
How many years ago you last used SAS/SCSI Disk Controllers?
For those above that +1 the others that installed the "missing firmwares" for never used hardware:
Congratulations, you played yourselves.

I don't know that's its quite as serious as all that no one is going to see any significant reductions in functionality from the missing firmware being present on their system but you're dead on that it's essentially useless to the vast majority and that will only on become more true as time marches om

This is a 2016 thread explaining that installing missing firmwares may make the warnings go away, but that doesn't make those firmwares work unless the related hardware is present.

Quote:
"You appear to have ignored all the advise offered in this thread up to this point.
The modules will not be loaded if the relevant hardware if not present on the system, presence or absence or the firmware will not change this."
https://bbs.archlinux.org/viewtopic.php?id=221076

@nmstoker

This comment has been minimized.

Copy link

@nmstoker nmstoker commented Feb 5, 2021

I suspect a lot of needless concern here stems from people conflating warnings and errors when they are distinct things. With a warning, consider if it applies and if not (as it won't for most people here in this case) or if you're not sure but have no specific observed problems, the simply carry on.

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Feb 6, 2021

My point is simple:
A warning is just a warning -harmless.
If you install firmware(s) for hardware you don't even have, you open the door for them to interact with your system or installed software to create difficult to solve issues.

@codydg

This comment has been minimized.

Copy link

@codydg codydg commented Feb 7, 2021

Warnings aren't simply harmless, though, and they shouldn't be ignored (otherwise there's no point in printing them in the first place!). They are used when there may be a problem. For example, if you did have one of the Disk Controllers in question, it can be problematic if you don't have the proper drivers.

There may be thousands of drivers you don't need, and it would be pointless to warn about every one of them - so why does it warn about these two in particular? If we can fix it and prevent the unnecessary warning, users will no longer have to go searching online to understand the warning and determine if it's a problem.

If there's a solid reason why it cannot be fixed for these two drivers in particular, then we can either leave it as is, add to the warning to identify the hardware that the drivers are for, or maybe make a web page that lists drivers and their corresponding hardware.

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Feb 8, 2021

@codydg Obviously you read nothing about those specific warnings above.
You "might" need those old SAS/SCSI Disk Controllers firmwares if you plan to use an old server.
The inevitable "Warnings" are there for the rest of us.
You like risking something not working in your system?
Sure, go ahead, install the firmwares, just to justify your OCD.

@codydg

This comment has been minimized.

Copy link

@codydg codydg commented Feb 8, 2021

@codydg Obviously you read nothing about those specific warnings above.
You "might" need those old SAS/SCSI Disk Controllers firmwares if you plan to use an old server.
The inevitable "Warnings" are there for the rest of us.
You like risking something not working in your system?
Sure, go ahead, install the firmwares, just to justify your OCD.

No need to be aggressive, I think you misunderstood my point. The warnings are not "inevitable". As I said, there are many drivers that it doesn't warn about. So I'm simply asking why it is that these two trigger a warning when none of the others do.

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Feb 8, 2021

@codydg Obviously you read nothing about those specific warnings above.
You "might" need those old SAS/SCSI Disk Controllers firmwares if you plan to use an old server.
The inevitable "Warnings" are there for the rest of us.
You like risking something not working in your system?
Sure, go ahead, install the firmwares, just to justify your OCD.

No need to be aggressive, I think you misunderstood my point. The warnings are not "inevitable". As I said, there are many drivers that it doesn't warn about. So I'm simply asking why it is that these two trigger a warning when none of the others do.

No worries, I'm not aggressive, just in point.
These specific warnings are well known, and documented a lot in various places.
Of course, if you get a new warning, you should ask/discuss about it.
The reason -as mentioned above in the comments- is some servers need such SCSI firmwares to operate, while most of us don't use such SCSI hardware.
See this comment:
https://gist.github.com/imrvelj/c65cd5ca7f5505a65e59204f5a3f7a6d#gistcomment-2801492

@gridley

This comment has been minimized.

Copy link

@gridley gridley commented Feb 8, 2021

There may be thousands of drivers you don't need, and it would be pointless to warn about every one of them - so why does it warn about these two in particular? If we can fix it and prevent the unnecessary warning, users will no longer have to go searching online to understand the warning and determine if it's a problem.

@cgcgcgcgcg you're not really addressing this excellent point. Don't you think it's annoying to hit every arch user on earth with this warning when only a tiny fraction actually need the firmware? Why not warn that every other irrelevant piece of firmware on earth has also not been installed, if this irrelevant warning appears? What makes it different? Maybe it is impossible to detect if this hardware is actually present until this firmware is installed?

Imagine if gcc spat out some totally irrelevant warning every time you compiled a program. Wouldn't you want that to be fixed? It's just annoying...

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Feb 8, 2021

There may be thousands of drivers you don't need, and it would be pointless to warn about every one of them - so why does it warn about these two in particular? If we can fix it and prevent the unnecessary warning, users will no longer have to go searching online to understand the warning and determine if it's a problem.

@cgcgcgcgcg you're not really addressing this excellent point. Don't you think it's annoying to hit every arch user on earth with this warning when only a tiny fraction actually need the firmware? Why not warn that every other irrelevant piece of firmware on earth has also not been installed, if this irrelevant warning appears? What makes it different? Maybe it is impossible to detect if this hardware is actually present until this firmware is installed?

Imagine if gcc spat out some totally irrelevant warning every time you compiled a program. Wouldn't you want that to be fixed? It's just annoying...

You answered yourself (some of us did too above).
Feel free to ask Kernel developers for more information.
Here are some useful links:
https://www.kernel.org/category/contact-us.html
https://kernelnewbies.org/

@jeffmikels

This comment has been minimized.

Copy link

@jeffmikels jeffmikels commented Feb 27, 2021

There should at least be an option in mkinitcpio to ignore specific firmware warnings... That way, the first time a user sees the warning, they can search the Arch Wiki and then once they know they don't need that firmware, they can change mkinitcpio.conf to suppress those specific warnings.

@Thomashighbaugh

This comment has been minimized.

Copy link

@Thomashighbaugh Thomashighbaugh commented Feb 28, 2021

@codydg Obviously you read nothing about those specific warnings above.
You "might" need those old SAS/SCSI Disk Controllers firmwares if you plan to use an old server.
The inevitable "Warnings" are there for the rest of us.
You like risking something not working in your system?
Sure, go ahead, install the firmwares, just to justify your OCD.

I fear that this may be trivializing serious mental challenges that people in this community and externally to it legitimately struggle with that we as a community with standards must be sensitive to if we truly seek to be inclusive, which is a goal of all technical communities, fora, other associated resources and the communities that are the means by which they operate.

Arch Linux itself states in the code of conduct we should attempt to treat others as we wish to be treated and I definitely don't want my own personal struggles that are unrelated to matters such as warnings from running pacman to be slung around as stigmatizing terms of abuse or means of supplying negative emphasis as is seemingly being done here to those who have to deal with the actual condition and the hardship it imposes on them. I suspect that is true of all of us.

Some individuals who struggle with OCD, a very real challenge that affects people of all sorts, are among those communities and I for one would like to be sure not alienate them though recognize your comment was intended to do so, in fact your sentiment I have actually come around to myself.

I am certainly guilty of using such terms so lightly in the past, but through reflection on these matters and seeing the ways that people struggle with challenges such as this as well as a litany of others, I have come to a crossroad where I think its best if we all, as a community, try to overcome this flourishes in our technical discussions that should remain as impartial as possible.

Nonetheless, I ask on behalf of all who struggle with mental health challenges, both within this community and external to it, that we all do our best to refrain for using a medical condition as describing behavior you seen as extraneous.

Additionally, here are some links about the condition in children, in general and in diagnosis that were informative and certainly deepened my empathy on the subject, helping me to further my empathy for those who struggle with it.

Edit: splitting it up a bit, making it easier to appreciate the sentiment at a glance. Added some links

@Thomashighbaugh

This comment has been minimized.

Copy link

@Thomashighbaugh Thomashighbaugh commented Feb 28, 2021

There should at least be an option in mkinitcpio to ignore specific firmware warnings... That way, the first time a user sees the warning, they can search the Arch Wiki and then once they know they don't need that firmware, they can change mkinitcpio.conf to suppress those specific warnings.

This seems the practical and applicable approach I have seen thus far suggested.

If this problem lingers much longer, which it seems it just might, I will be going down the C rabbit holes of interest to it in the near enough future, I might just have to deal with myself (or with whom ever else simply wants this very real issue corrected)

As I see it, warnings that can then be disabled, individually or perhaps collectively (though that's less optimal) would be a reasonable means of achieving the goals of those who have joined the chorus of irritated users while not excluding the ever shrinking group that would find these warnings helpful from receiving them and taking appropriate action.

Being that silencing output is a regular option affixed to many programs, I can't imagine finding some means of doing so outside of the scope of the programming that has generated them and would enhance the overall professional appearance of Arch Linux, which it seems is a common goal to all camps and a motivating factor on both sides of this spirited discussion.

@charlie39

This comment has been minimized.

Copy link

@charlie39 charlie39 commented Mar 2, 2021

i have been ignoring these messages like texts from my ex since 2018, but now there's another warning i am seeing about some xhci_usb firmware missing, turns out it was because of a commit that introduced support for some udpXXXXX ranesas devices.
So does it mean every time support for some peculiar device is added, the rest of are going to have to deal with the warnings?Nay!
I announce 20 busty brown country side fed cows for the one who suppresses the error messages.

@Thomashighbaugh

This comment has been minimized.

Copy link

@Thomashighbaugh Thomashighbaugh commented Mar 4, 2021

i have been ignoring these messages like texts from my ex since 2018, but now there's another warning i am seeing about some xhci_usb firmware missing, turns out it was because of a commit that introduced support for some udpXXXXX ranesas devices.
So does it mean every time support for some peculiar device is added, the rest of are going to have to deal with the warnings?Nay!
I announce 20 busty brown country side fed cows for the one who suppresses the error messages.

Quite a reward, for the bounty that is livestock surely we can find someone willing!

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Mar 11, 2021

mkinitcpio-firmware
Optional firmware for the default linux kernel to get rid of the annoying 'WARNING: Possibly missing firmware for module:' messages
https://aur.archlinux.org/packages/mkinitcpio-firmware/

@cgcgcgcgcg

This comment has been minimized.

Copy link

@cgcgcgcgcg cgcgcgcgcg commented Mar 12, 2021

Installing random binary blobs from the internet for hardware that you don't use has to be among the worst solutions for supressing a useless warning.

I have explained my point of view in above comments, but since I had a message about my vulgar (sic) ways, peeps with OCD issues can now relax.
mkinitcpio-firmware mentioned above installs the unnecessary firmware needed only by mkinitcpio to suppress the warnings.
Sorry, but I won't be commenting any more about it.

@codydg

This comment has been minimized.

Copy link

@codydg codydg commented Mar 12, 2021

We've already discussed why this thread exists. Thousands of pieces of firmware exist. You could warn about them all, but that would make the warning useless, and it might as well be removed. So the question is: why does it warn about these 3? What if pacman warned you about random programs you don't have installed every time you used it?

Warnings are supposed to alert of possible errors, and ignoring them regularly leads to issues. If people want to keep the warning, I'd suggest stating in the warning what hardware the firmware is for so you don't have to scrape the internet to figure out if each one applies to you. But the warning seems irrelevant to me.

@MeganerdNL

This comment has been minimized.

Copy link

@MeganerdNL MeganerdNL commented Mar 25, 2021

We've already discussed why this thread exists. Thousands of pieces of firmware exist. You could warn about them all, but that would make the warning useless, and it might as well be removed. So the question is: why does it warn about these 3? What if pacman warned you about random programs you don't have installed every time you used it?

Warnings are supposed to alert of possible errors, and ignoring them regularly leads to issues. If people want to keep the warning, I'd suggest stating in the warning what hardware the firmware is for so you don't have to scrape the internet to figure out if each one applies to you. But the warning seems irrelevant to me.

Couldn't agree more.
It seems utterly random and irrelevant.

Remove the warning OR at least add a link or an explaining text message.

@Sethox

This comment has been minimized.

Copy link

@Sethox Sethox commented May 6, 2021

So to my understanding, warnings are that- just warnings. Okey got it. And if we don't like it, take it to the kernel developers (or at least do some research because github isn't the best forum to complain or give suggestions, and to not waste anyone's busy time).

@biorpg

This comment has been minimized.

Copy link

@biorpg biorpg commented May 26, 2021

mkinitcpio-firmware
Optional firmware for the default linux kernel to get rid of the annoying 'WARNING: Possibly missing firmware for module:' messages
https://aur.archlinux.org/packages/mkinitcpio-firmware/

You went out of your way to create a package that installs the very firmware that the people in this thread are expressing concern about for the sole purpose of offering it up as a passive-aggressive 'remedy' to those concerns?

How about doing something constructive, such as making a package that easily removes firmware for non-present hardware entirely, warning messages and all?

@tylercrompton

This comment has been minimized.

Copy link

@tylercrompton tylercrompton commented Jul 25, 2021

I don't think that installing firmware for hardware that one doesn't have is an appropriate solution to this. I looked into this to find a better solution.

The logic is written in Bash. If you plan to never use SCSI, then copy “/usr/lib/initcpio/install/block” as “/etc/initcpio/install/block” and in the copy, change lines 6–9 from the following:

    map add_module sd_mod? sr_mod? usb_storage? mmc_block? firewire-sbp2? virtio_blk?

    # pata, sata, scsi, nvme
    for filter in 'scsi/.*ata' '/(block|scsi|fusion|nvme)/' 'ata/[ps]ata_' \

to the following:

    map add_module usb_storage? mmc_block? firewire-sbp2? virtio_blk?

    # pata, sata, nvme
    for filter in '/(block|fusion|nvme)/' 'ata/[ps]ata_' \

Feel free to reflect these changes in the help function in that file.

A custom hook (i.e. a hook in “/etc/initcpio/”) with the same name as a system hook (i.e. a hook in “/usr/lib/initcpio/”) overrides that system hook. If you want to use a different name for the custom hook, then you'll need to change the copy's file name and reflect that change in “/etc/mkinitcpio.conf”.

After running $ mkinitcpio --allpresets and rebooting my system, all seems to be in working order.

@kmanwar89

This comment has been minimized.

Copy link

@kmanwar89 kmanwar89 commented Aug 26, 2021

I don't think that installing firmware for hardware that one doesn't have is an appropriate solution to this. I looked into this to find a better solution.

The logic is written in Bash. If you plan to never use SCSI, then copy “/usr/lib/initcpio/install/block” as “/etc/initcpio/install/block” and in the copy, change lines 6–9 from the following:

    map add_module sd_mod? sr_mod? usb_storage? mmc_block? firewire-sbp2? virtio_blk?

    # pata, sata, scsi, nvme
    for filter in 'scsi/.*ata' '/(block|scsi|fusion|nvme)/' 'ata/[ps]ata_' \

to the following:

    map add_module usb_storage? mmc_block? firewire-sbp2? virtio_blk?

    # pata, sata, nvme
    for filter in '/(block|fusion|nvme)/' 'ata/[ps]ata_' \

Feel free to reflect these changes in the help function in that file.

A custom hook (i.e. a hook in “/etc/initcpio/”) with the same name as a system hook (i.e. a hook in “/usr/lib/initcpio/”) overrides that system hook. If you want to use a different name for the custom hook, then you'll need to change the copy's file name and reflect that change in “/etc/mkinitcpio.conf”.

After running $ mkinitcpio --allpresets and rebooting my system, all seems to be in working order.

Finally - an answer instead of infighting. Will be trying this soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment