You are not logged in.

#1 2021-09-14 00:50:38

black fire hydrant
Member
Registered: 2021-09-08
Posts: 3

[SOLVED] mkinitcpio can't find 'usbhid', 'i915', and nvidia modules

Can I fix this in any way?
I'm using the intel modesetting drivers, nvidia-dkms, and optimus-manager.


lspci -k output:

$ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
        Subsystem: Lenovo Device 3978
lspci: Unable to load libkmod resources: error -2
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
        Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
        Subsystem: Lenovo Device 3809
        Kernel driver in use: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
        Subsystem: Intel Corporation Device 2010
        Kernel driver in use: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
        Subsystem: Lenovo Device 3978
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
        Subsystem: Intel Corporation Device 2010
        Kernel driver in use: mei_me
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
        Subsystem: Lenovo Device 3978
        Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
        Subsystem: Intel Corporation Device 2010
        Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5)
        Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
        Subsystem: Lenovo Device 3978
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 05)
        Subsystem: Intel Corporation Device 2010
        Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
        Subsystem: Intel Corporation Device 2010
        Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
        Subsystem: Lenovo Device 3978
        Kernel driver in use: i801_smbus
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2)
        Subsystem: Lenovo Device 3809
        Kernel driver in use: nvidia
07:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
        Subsystem: Intel Corporation Wireless-N 7260
        Kernel driver in use: iwlwifi
08:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
        Subsystem: Qualcomm Atheros Device 1091
        Kernel driver in use: alx

mkinitcpio output:

$ mkinitcpio
==> Starting dry run: 5.10.63-1-lts
  -> 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]
==> ERROR: module not found: `usbhid'
  -> Running build hook: [fsck]
==> ERROR: module not found: `i915'
==> ERROR: module not found: `nvidia'
==> ERROR: module not found: `nvidia_modeset'
==> ERROR: module not found: `nvidia_uvm'
==> ERROR: module not found: `nvidia_drm'
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Dry run complete, use -g IMAGE to generate a real image

neofetch output:

$ neofetch
                   -`                     
                  .o+`                   --------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: 20250 Lenovo Z710 
               `+oooooo:                 Kernel: 5.10.63-1-lts 
               -+oooooo+:                Uptime: 1 hour, 26 mins 
             `/:-:++oooo+:               Packages: 825 (pacman) 
            `/++++/+++++++:              Shell: bash 5.1.8 
           `/++++++++++++++:             Resolution: 1920x1080 
          `/+++ooooooooooooo/`           DE: Plasma 5.22.5 
         ./ooosssso++osssssso+`          WM: KWin 
        .oossssso-````/ossssss+`         Theme: Breeze Dark [Plasma], Breeze [GTK2/3] 
       -osssssso.      :ssssssso.        Icons: [Plasma], breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: konsole 
     /ossssssss/        +ssssooo/-       CPU: Intel i7-4710MQ (8) @ 2.500GHz 
   `/ossssso+/:-        -:/+osssso+-     GPU: NVIDIA GeForce 840M 
  `+sso+:-`                 `.-/+oso:    GPU: Intel 4th Gen Core Processor 
 `++:.                           `-/+/   Memory: 1723MiB / 15929MiB 
 .`                                 `/

mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=(i915 nvidia nvidia_modeset nvidia_uvm nvidia_drm)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Last edited by black fire hydrant (2021-09-14 02:03:15)

Offline

#2 2021-09-14 01:01:45

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,306

Re: [SOLVED] mkinitcpio can't find 'usbhid', 'i915', and nvidia modules

Update your system, or rather reboot as I'm assuming this being a consequence of having updated and thus receiving the 5.10.64 set of kernels/modules. What's the output when doing a real run?

Offline

#3 2021-09-14 01:33:16

black fire hydrant
Member
Registered: 2021-09-08
Posts: 3

Re: [SOLVED] mkinitcpio can't find 'usbhid', 'i915', and nvidia modules

V1del wrote:

Update your system, or rather reboot as I'm assuming this being a consequence of having updated and thus receiving the 5.10.64 set of kernels/modules. What's the output when doing a real run?

rebooted, i915 error is gone

$ mkinitcpio -g IMAGE
==> Starting build: 5.10.64-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> ERROR: module not found: `nvidia'
==> ERROR: module not found: `nvidia_modeset'
==> ERROR: module not found: `nvidia'
==> ERROR: module not found: `nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /home/user/IMAGE
==> WARNING: errors were encountered during the build. The image may not be complete.

Offline

#4 2021-09-14 01:41:02

Ammako
Member
Registered: 2021-07-16
Posts: 267

Re: [SOLVED] mkinitcpio can't find 'usbhid', 'i915', and nvidia modules

I can't see why nvidia-dkms wouldn't be functioning, it should have been building the kernel modules automatically when you installed the kernel and/or when you installed the drivers. Maybe you might need to manually trigger the kernel module build?

That being said you don't actually need nvidia-dkms. Get rid of it and use nvidia-lts instead, less headache.

Last edited by Ammako (2021-09-14 01:41:56)

Offline

#5 2021-09-14 02:02:53

black fire hydrant
Member
Registered: 2021-09-08
Posts: 3

Re: [SOLVED] mkinitcpio can't find 'usbhid', 'i915', and nvidia modules

That was easier than I thought it would be. I reinstalled linux-lts-headers and it succeeded for some reason. amazing
i would delete this if i could

Offline

Board footer

Powered by FluxBB