You are not logged in.

#1 2021-06-22 13:25:43

Biaogo
Member
Registered: 2020-08-07
Posts: 8

kernel install error: The image may not be complete.

$ sudo pacman -S linux-zen crda linux-zen-headers linux-firmware

resolving dependencies...
looking for conflicting packages...

Packages (4) crda-4.14-4  linux-firmware-20210511.7685cf4-1  linux-zen-5.12.12.zen1-1  linux-zen-headers-5.12.12.zen1-1

Total Installed Size:  915.01 MiB

:: Proceed with installation? [Y/n] 
(4/4) checking keys in keyring                                                   [##############################################] 100%
(4/4) checking package integrity                                                 [##############################################] 100%
(4/4) loading package files                                                      [##############################################] 100%
(4/4) checking for file conflicts                                                [##############################################] 100%
(4/4) checking available disk space                                              [##############################################] 100%
:: Processing package changes...
(1/4) installing linux-zen                                                       [##############################################] 100%
Optional dependencies for linux-zen
    crda: to set the correct wireless channels of your country [pending]
    linux-firmware: firmware images needed for some devices [pending]
(2/4) installing crda                                                            [##############################################] 100%
Uncomment the right regulatory domain in /etc/conf.d/wireless-regdom.
It will automatically be set on boot.
(3/4) installing linux-zen-headers                                               [##############################################] 100%
(4/4) installing linux-firmware                                                  [##############################################] 100%
:: Running post-transaction hooks...
(1/5) Creating temporary files...
(2/5) Reloading device manager configuration...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating module dependencies...
(5/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 5.12.12-zen1-1-zen
  -> 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_uvm'
==> ERROR: module not found: `nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 5.12.12-zen1-1-zen
  -> 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
==> 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_uvm'
==> ERROR: module not found: `nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
# /etc/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=(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=()
#/etc/X11/xorg.conf

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 465.31
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Module"
    load "modesetting"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "4:0:0"
    Option         "AllowEmptyInitialConfiguration"
    Option         "RenderAccel" "1"
    Option         "TripleBuffer" "1"
    Option         "DamageEvents" "1"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
# /etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BusID          "PCI:4:0:0"
    Option         "AllowEmptyInitialConfiguration"
    Option         "RenderAccel" "1"
    Option         "TripleBuffer" "1"
    Option         "DamageEvents" "1"
EndSection
$ lspci |egrep 'VGA|3D'

04:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
$ pacman -Qs nvidia

local/egl-wayland 1.1.7-1
    EGLStream-based Wayland external platform
local/lib32-libvdpau 1.4-1
    Nvidia VDPAU library
local/lib32-nvidia-utils 465.31-1
    NVIDIA drivers utilities (32-bit)
local/lib32-opencl-nvidia 465.31-1
    OpenCL implemention for NVIDIA (32-bit)
local/libvdpau 1.4-1
    Nvidia VDPAU library
local/libxnvctrl 465.31-1
    NVIDIA NV-CONTROL X extension
local/nvidia 465.31-10
    NVIDIA drivers for linux
local/nvidia-prime 1.0-4
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-settings 465.31-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 465.31-1
    NVIDIA drivers utilities
local/opencl-nvidia 465.31-1
    OpenCL implemention for NVIDIA

Offline

#2 2021-06-22 13:44:46

Scimmia
Fellow
Registered: 2012-09-01
Posts: 8,696

Re: kernel install error: The image may not be complete.

You don't have the nvidia modules for that kernel. See the nvidia wiki page, the nvidia package only includes modules for the 'linux' kernel.

Offline

#3 2021-06-22 15:03:41

Biaogo
Member
Registered: 2020-08-07
Posts: 8

Re: kernel install error: The image may not be complete.

Scimmia wrote:

You don't have the nvidia modules for that kernel. See the nvidia wiki page, the nvidia package only includes modules for the 'linux' kernel.

how to add then?

Offline

#4 2021-06-22 15:25:30

Scimmia
Fellow
Registered: 2012-09-01
Posts: 8,696

Re: kernel install error: The image may not be complete.

Biaogo wrote:

how to add then?

Scimmia wrote:

...See the nvidia wiki page...

Offline

Board footer

Powered by FluxBB