Warning mkinitcpio

HeikeOnFire · 2016-12-25 11:52:04

Hello.

I got two warnings everytime I want to build the "Kernel"? with mkinitcpio:

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

I already read something about the "problem" (for example here), but I just don't understand, what I should do now to get the modules working.

Here is are some Informations about the modules:

description:    Western Digital WD7193/7197/7296 SCSI driver

description:    Adaptec aic94xx SAS/SATA driver

Should I install Arch now new?

ugjka · 2016-12-25 11:58:31

those warnings are harmless, i get them too

HeikeOnFire · 2016-12-25 12:06:12

Shouldn't I install now wd719x-firmware and aic94xx-firmware from the AUR?

I thought my SSD can't work that good with the aic94xx-firmware missing.

Last edited by HeikeOnFire (2016-12-25 12:08:03)

ugjka · 2016-12-25 12:11:59

Yeah, I just did that

olegabrielz · 2016-12-25 12:28:20

This has been a subject for a long time. Read this

Lone_Wolf · 2016-12-25 13:06:52

mkinitcpio wiki wrote:

If you do not use hardware which uses these firmwares you can safely ignore this message.

The aic94xx was used in enterprise class hardware raid controller cards mostly used with super fast 15k+ rpm serial attached scsi drives.
In case you're unfamiliar with those terms : the drives were 5-10 times as expensive as standard 7200 rpm drives of the same size.
If you have such hardware in a home system,you (and your bank account) will know it.

Last edited by Lone_Wolf (2016-12-25 13:07:15)

Trilby · 2016-12-25 13:14:42

Not an installation issue. Not really an issue at all ... but I'll move this to NC for now.

HeikeOnFire, you link to a thread that has all the information you're asking about. You say you still don't understand - that's ok, we can help, but you didn't bother to provide your responses to all the questions asked of the OP in that other thread, like whether this is the main image or fallback image. That other thread also seems to lay out the issues pretty clearly. If you have follow up questions, please specify what they are, but it's silly for this thread to just duplicate everything that was already said there (which we've now done).

HeikeOnFire · 2016-12-25 14:32:49

I don't understand how can my SSD work, if the SATA Driver is "possible" missing? Is there a "fallback" driver which can rather handle it? Something like the Windows Video driver?
And if I install now the two packages from the AUR. Must I "tell the Kernel" somehow to use them?

Register them here maybe?: /etc/modules-load.d/meinemodule.conf

I dont know anymore which image was warning by creating. Should i repeat the command?

Last edited by HeikeOnFire (2016-12-25 14:43:36)

loqs · 2016-12-25 14:50:35

HeikeOnFire wrote:

I don't understand how can my SSD work, if the SATA Driver is "possible" missing?

Is the ssd working now? Is either the wd719x or aic94xx modules loaded?

HeikeOnFire · 2016-12-25 14:59:23

Yes I can use my SSD. I already installed arch on It.
I will start my laptop later home and look which modules are loaded.

Trilby · 2016-12-25 15:25:46

There's no harm in rerunning `mkinicpio -p linux` to see which image gave the warnings. I'm pretty sure it'd just be the fallback though. In which case you are drastically overinterpreting everything. It's just being verbose. It's expected. If it aint broke ... don't break it!

HeikeOnFire · 2016-12-27 19:54:52

Hm ok......
I have installed wd719x-firmware and aic94xx-firmware from the AUR now.

yaourt -S wd719x-firmware
yaourt -S aic94xx-firmware

Can I now assume that the drivers are working?
Or do I have to do something else too?

Trilby · 2016-12-27 19:57:43

You can assume whatever you want as you seem to be unwilling to listen to any input from others.

loqs · 2016-12-27 19:58:46

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.

Daerandin · 2016-12-27 20:02:49

As have been pointed out multiple times already, you seem to misunderstand a lot here. It is highly unlikely that you need those modules. I have personally never owned any hardware that require those modules. The warnings will show up for all Arch users on generation of the fallback image (except those that have specifically installed those modules). As long as those warning only appeared for the fallback image, as stated by Trilby, then nothing is wrong with your system.

Of course, having those modules installed should not affect you negatively, but you will not benefit from them either.

Edit: Too slow...

Last edited by Daerandin (2016-12-27 20:03:08)

HeikeOnFire · 2016-12-27 20:37:36

Haha guys please calm down.
I am happy about answers in this thread and I don't ignore messages from you.

I understand what Trilby said. The fallback image shouldn't load all modules. It's expected like that.
Just had my problems looking in dmesg when the warnings had come.
Thought they came while installing base and base-devel, too. (If that can be, just know the warnings came two times)

So I thought It would be no problem if I play safe and install those firmwares....

Last edited by HeikeOnFire (2016-12-27 20:41:10)

loqs · 2016-12-27 21:15:36

HeikeOnFire wrote:

I am happy about answers in this thread and I don't ignore messages from you.

If did not ignore the advice from ugjka, olegabrielz, Lone_Wolf and Trilby then why did you not accept the issue was harmless?

HeikeOnFire wrote:

I understand what Trilby said. The fallback image shouldn't load all modules. It's expected like that.

No the fallback image will include all modules of a particular class irrespective of the hardware present on an acutal system.

HeikeOnFire wrote:

Just had my problems looking in dmesg when the warnings had come.
Thought they came while installing base and base-devel, too. (If that can be, just know the warnings came two times)

You mean these kernel errors?

[0.000000]efi: requested map no found
[0.000000]esrt: ESRT header is not in the memory map.

From the efi and esrt modules not the wd719x or aic94xx modules.
Also it has taken until your 6th post in the thread to indicate this is the cause of your concern.
This does not match your previous explanation of

HeikeOnFire wrote:

I thought my SSD can't work that good with the aic94xx-firmware missing.

Also note you do not answer questions asked of you such as: during the generation of which image were these errors produced, do you have hardware that requires either of those modules, are those modules loaded on the system?

HeikeOnFire · 2016-12-27 21:42:08

loqs wrote:

No the fallback image will include all modules of a particular class irrespective of the hardware present on an acutal system.

Hmm OK, so you mean the warning is harmless while creating the fallback image, because if one is missing, It doesn't be said that I need It.

loqs wrote:

You mean these kernel errors?

No, I meant this warnings while installation:

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

loqs wrote:

Also note you do not answer questions asked of you such as: during the generation of which image were these errors produced

Like I said. I don't know anymore when the warnings appeared during the installation. Just know that they came two times.
Having problems finding them again with dmesg.

This says lsmod now. Hope this helps:

Module                  Size  Used by
fuse                   98304  3
ctr                    16384  2
ccm                    20480  1
uvcvideo               86016  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         20480  1 uvcvideo
videobuf2_core         36864  2 uvcvideo,videobuf2_v4l2
videodev              151552  3 uvcvideo,videobuf2_core,videobuf2_v4l2
media                  32768  2 uvcvideo,videodev
btusb                  40960  0
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
btintel                16384  1 btusb
bluetooth             487424  5 btrtl,btintel,btbcm,btusb
snd_hda_codec_hdmi     45056  1
snd_hda_codec_realtek    69632  1
snd_hda_codec_generic    69632  1 snd_hda_codec_realtek
joydev                 20480  0
mousedev               20480  0
iTCO_wdt               16384  0
iTCO_vendor_support    16384  1 iTCO_wdt
arc4                   16384  2
intel_rapl             20480  0
nls_iso8859_1          16384  1
intel_powerclamp       16384  0
coretemp               16384  0
nls_cp437              20480  1
vfat                   20480  1
fat                    65536  1 vfat
kvm_intel             188416  0
kvm                   516096  1 kvm_intel
i915                 1241088  15
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
crc32c_intel           24576  0
iwlmvm                278528  0
ghash_clmulni_intel    16384  0
mac80211              667648  1 iwlmvm
evdev                  24576  21
iwlwifi               188416  1 iwlmvm
input_leds             16384  0
mac_hid                16384  0
drm_kms_helper        126976  1 i915
psmouse               126976  0
pcspkr                 16384  0
aesni_intel           167936  2
aes_x86_64             20480  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
glue_helper            16384  1 aesni_intel
ablk_helper            16384  1 aesni_intel
cryptd                 20480  3 ablk_helper,ghash_clmulni_intel,aesni_intel
intel_cstate           16384  0
cfg80211              495616  3 iwlmvm,iwlwifi,mac80211
drm                   294912  10 i915,drm_kms_helper
snd_intel_sst_acpi     16384  0
snd_intel_sst_core     69632  1 snd_intel_sst_acpi
snd_soc_sst_mfld_platform    77824  1 snd_intel_sst_core
snd_soc_sst_match      16384  1 snd_intel_sst_acpi
intel_gtt              20480  1 i915
lpc_ich                24576  0
i2c_i801               24576  0
syscopyarea            16384  1 drm_kms_helper
snd_hda_intel          32768  6
i2c_smbus              16384  1 i2c_i801
snd_soc_core          188416  1 snd_soc_sst_mfld_platform
sysfillrect            16384  1 drm_kms_helper
snd_hda_codec         106496  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
sysimgblt              16384  1 drm_kms_helper
mei_txe                20480  0
fb_sys_fops            16384  1 drm_kms_helper
i2c_algo_bit           16384  1 i915
snd_hda_core           65536  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
processor_thermal_device    16384  0
mei                    86016  1 mei_txe
sdhci_pci              28672  0
snd_compress           20480  1 snd_soc_core
snd_hwdep              16384  1 snd_hda_codec
intel_soc_dts_iosf     16384  1 processor_thermal_device
shpchp                 32768  0
snd_pcm_dmaengine      16384  1 snd_soc_core
ac97_bus               16384  1 snd_soc_core
thermal                20480  0
snd_pcm                90112  7 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_core,snd_hda_codec_hdmi,snd_soc_sst_mfld_platform,snd_soc_core
i2c_hid                20480  0
fan                    16384  0
snd_timer              28672  1 snd_pcm
hid                   114688  1 i2c_hid
ideapad_laptop         24576  0
sparse_keymap          16384  1 ideapad_laptop
rfkill                 20480  7 bluetooth,ideapad_laptop,cfg80211
wmi                    16384  1 ideapad_laptop
battery                20480  0
snd                    69632  23 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_soc_sst_mfld_platform,snd_hda_codec_realtek,snd_soc_core,snd_pcm
i2c_designware_platform    16384  0
fjes                   28672  0
video                  36864  2 i915,ideapad_laptop
soundcore              16384  1 snd
int3403_thermal        16384  0
i2c_designware_core    20480  1 i2c_designware_platform
int340x_thermal_zone    16384  2 int3403_thermal,processor_thermal_device
int3400_thermal        16384  0
acpi_thermal_rel       16384  1 int3400_thermal
8250_dw                16384  0
spi_pxa2xx_platform    24576  0
soc_button_array       16384  0
tpm_tis                16384  0
tpm_tis_core           20480  1 tpm_tis
tpm                    36864  2 tpm_tis,tpm_tis_core
button                 16384  1 i915
ac                     16384  0
sch_fq_codel           20480  5
ip_tables              28672  0
x_tables               28672  1 ip_tables
ext4                  524288  1
crc16                  16384  2 bluetooth,ext4
jbd2                   90112  1 ext4
fscrypto               24576  1 ext4
mbcache                16384  2 ext4
sd_mod                 36864  4
serio_raw              16384  0
atkbd                  24576  0
libps2                 16384  2 atkbd,psmouse
ahci                   36864  3
libahci                28672  1 ahci
xhci_pci               16384  0
xhci_hcd              172032  1 xhci_pci
libata                208896  2 ahci,libahci
usbcore               208896  4 uvcvideo,xhci_pci,btusb,xhci_hcd
scsi_mod              159744  2 sd_mod,libata
usb_common             16384  1 usbcore
i8042                  28672  1 ideapad_laptop
serio                  20480  6 serio_raw,atkbd,psmouse,i8042
sdhci_acpi             16384  0
sdhci                  40960  2 sdhci_pci,sdhci_acpi
led_class              16384  3 iwlmvm,sdhci,input_leds
mmc_core              122880  3 sdhci,sdhci_pci,sdhci_acpi

Last edited by HeikeOnFire (2016-12-27 21:45:17)

loqs · 2016-12-27 22:01:21

HeikeOnFire wrote:

Hmm OK, so you mean the warning is harmless while creating the fallback image, because if one is missing, It doesn't be said that I need It.

Trilby wrote:

There's no harm in rerunning `mkinicpio -p linux` to see which image gave the warnings. I'm pretty sure it'd just be the fallback though. In which case you are drastically overinterpreting everything. It's just being verbose. It's expected. If it aint broke ... don't break it!

HeikeOnFire wrote:

No, I meant this warnings while installation:

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

So it is the warnings the first 4 responders in this thread told you were harmless.

loqs wrote:

Also note you do not answer questions asked of you such as: during the generation of which image were these errors produced

HeikeOnFire wrote:

Like I said. I don't know anymore when the warnings appeared during the installation. Just know that they came two times.
Having problems finding them again with dmesg.
This says lsmod now. Hope this helps:

So the lsmod output does not contain wd719x or aic94xx. You can not find any reference to those modules in dmesg.
You could follow Trilby's advice ( with the firmwares removed ) to see during which image generation the warnings are produced.
So far do you agree there is no evidence your system needs these modules, loads these modules or attempts to load these module?

HeikeOnFire · 2016-12-27 22:22:49

So far do you agree there is no evidence your system needs these modules, loads these modules or attempts to load these module?

Yes, just want to make sure everything is working without problems. Installed the modules -> system still don't use them -> It's clear I don't need them?

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.8.13-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.8.13-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Trilby is right with his guess.

infinarchy · 2016-12-28 05:23:19

empty

Last edited by infinarchy (2017-11-04 21:41:07)

Arch Linux

#1 2016-12-25 11:52:04

Warning mkinitcpio

#2 2016-12-25 11:58:31

Re: Warning mkinitcpio

#3 2016-12-25 12:06:12

Re: Warning mkinitcpio

#4 2016-12-25 12:11:59

Re: Warning mkinitcpio

#5 2016-12-25 12:28:20

Re: Warning mkinitcpio

#6 2016-12-25 13:06:52

Re: Warning mkinitcpio

#7 2016-12-25 13:14:42

Re: Warning mkinitcpio

#8 2016-12-25 14:32:49

Re: Warning mkinitcpio

#9 2016-12-25 14:50:35

Re: Warning mkinitcpio

#10 2016-12-25 14:59:23

Re: Warning mkinitcpio

#11 2016-12-25 15:25:46

Re: Warning mkinitcpio

#12 2016-12-27 19:54:52

Re: Warning mkinitcpio

#13 2016-12-27 19:57:43

Re: Warning mkinitcpio

#14 2016-12-27 19:58:46

Re: Warning mkinitcpio

#15 2016-12-27 20:02:49

Re: Warning mkinitcpio

#16 2016-12-27 20:37:36

Re: Warning mkinitcpio

#17 2016-12-27 21:15:36

Re: Warning mkinitcpio

#18 2016-12-27 21:42:08

Re: Warning mkinitcpio

#19 2016-12-27 22:01:21

Re: Warning mkinitcpio

#20 2016-12-27 22:22:49

Re: Warning mkinitcpio

#21 2016-12-28 05:23:19

Re: Warning mkinitcpio

Board footer