[Solved] Modprobe: module efivars not found in modules.dep  [Solved]

Message
Author
User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

[Solved] Modprobe: module efivars not found in modules.dep

#1 Post by gsm »

Today, during each new startup of MX-21 x64 Wildflower, a message is displayed at the top of the screen:
Modprobe: module efivars not found in modules.dep
This message did not show up before and the older laptop does not have UEFI.
The cause could be that i tried to boot from an ISO that i had made from this same system, using the MX snapshot utility.

My question is: How can i repair the system to remove this message?

System:

Code: Select all

System:    Kernel: 5.10.0-11-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-11-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21_ahs_x64 Wildflower November 22  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP Pavilion dv9500 Notebook PC v: Rev 1 
           serial: <filter> Chassis: Quanta type: 10 serial: <filter> 
           Mobo: Quanta model: 30CB v: 79.2E serial: <filter> BIOS: Hewlett-Packard v: F.5A 
           date: 03/22/2010 
Battery:   ID-1: BAT0 charge: 50.7 Wh (100.0%) condition: 50.7/65.1 Wh (77.8%) volts: 16.5 
           min: 14.8 model: Hewlett-Packard Primary type: Li-ion serial: N/A status: Full 
CPU:       Info: Dual Core model: Intel Core2 Duo T5250 bits: 64 type: MCP arch: Core Merom 
           family: 6 model-id: F (15) stepping: D (13) microcode: A4 cache: L2: 2 MiB 
           flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 5984 
           Speed: 997 MHz min/max: 1000/1500 MHz Core speeds (MHz): 1: 997 2: 997 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA G86M [GeForce 8400M GS] vendor: Hewlett-Packard Pavilion dv6700 
           driver: nvidia v: 340.108 bus-ID: 01:00.0 chip-ID: 10de:0427 class-ID: 0300 
           Device-2: Chicony Gateway USB 2.0 Webcam type: USB driver: uvcvideo bus-ID: 3-4:3 
           chip-ID: 04f2:b023 class-ID: 0e02 serial: <filter> 
           Display: x11 server: X.Org 1.20.13 compositor: compton v: 1 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.0x9.4") 
           s-diag: 449mm (17.7") 
           Monitor-1: LVDS-0 res: 1440x900 hz: 60 dpi: 100 size: 367x230mm (14.4x9.1") 
           diag: 433mm (17.1") 
           OpenGL: renderer: GeForce 8400M GS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
           direct render: Yes 
Audio:     Device-1: Intel 82801H HD Audio vendor: Hewlett-Packard Pavilion dv6700 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:284b class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-11-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network driver: iwl4965 
           v: in-tree: modules: wl port: 2000 bus-ID: 02:00.0 chip-ID: 8086:4229 class-ID: 0280 
           IF: wlan0 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: c000 bus-ID: 08:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 817.88 GiB used: 8.58 GiB (1.0%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series 
           size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD 
           serial: <filter> rev: 5B0Q scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MQ01ABD075 size: 698.64 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 
           serial: <filter> rev: 4M scheme: MBR 
Partition: ID-1: / raw-size: 56.61 GiB size: 55.42 GiB (97.90%) used: 8.42 GiB (15.2%) fs: ext4 
           dev: /dev/sda4 maj-min: 8:4 
           ID-2: /home raw-size: 297.71 GiB size: 292.04 GiB (98.09%) used: 172.8 MiB (0.1%) 
           fs: ext4 dev: /dev/sdb2 maj-min: 8:18 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 5.47 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sdb3 maj-min: 8:19 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2250 lib: 1141 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://nl.mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://nl.mxrepo.com/mx/repo/ bullseye ahs
Info:      Processes: 198 Uptime: 13m wakeups: 2 Memory: 3.84 GiB used: 1.18 GiB (30.7%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Shell: quick-system-in default: Bash v: 5.1.4 running-in: quick-system-in 
           inxi: 3.3.06 
Last edited by gsm on Thu Mar 10, 2022 9:57 am, edited 1 time in total.

User avatar
dolphin_oracle
Developer
Posts: 22665
Joined: Sun Dec 16, 2007 12:17 pm

Re: Modprobe: module efivars not found in modules.dep

#2 Post by dolphin_oracle »

try

Code: Select all

sudo depmod
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#3 Post by gsm »

Sudo depmod did not make any difference.

User avatar
fehlix
Developer
Posts: 12882
Joined: Wed Apr 11, 2018 5:09 pm

Re: Modprobe: module efivars not found in modules.dep

#4 Post by fehlix »

gsm wrote: Sat Feb 26, 2022 4:33 pm Today, during each new startup of MX-21 x64 Wildflower, a message is displayed at the top of the screen:
Modprobe: module efivars not found in modules.dep
This message did not show up before and the older laptop does not have UEFI.
The cause could be that i tried to boot from an ISO that i had made from this same system, using the MX snapshot utility.
Not sure I understand .. the sequence of events.
So, you booted from LiveISO ... and what was done? I mean just booting from a LiveISO, would not change something in the installed system.

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#5 Post by gsm »

In fact i have of course no evidence that the boot of the live system really could have caused a change in the installed system.
I agree that this is in fact unlikely.
The live system (snapshot) did not boot completely, but ended up in a blank screen with blinking cursor.
Then i pressed Ctrl+Alt+Delete to restart the computer and boot it normally again.
It only was for the first time that i then saw the modprobe message for the first time, but it is very well possible that this message was given already before the live boot happened.
I do not always monitor the boot process.

I have tried and removed quite some applications (e.g. anbox, which could not be started) and there have been some new updates too.
I added the Nvidia driver and also installed wine (running Picasa, Pinball and Pandora's Box).
A few times apt autoremove had to be executed and i have selected a different grub theme via MX Tweak.
For the rest everything is working very well.

I have no problem (just testing) to do the whole fresh installation over again, leaving the Home directory intact, to look carefully then when exactly or how this little problem did occur.
It would be nice however if there would be a simple and quicker solution to fix this.

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#6 Post by gsm »

I did a fresh install, reusing the Home directory content.
Some dmesg output with nouveau error logs:

Code: Select all

[   18.538385] r8169 0000:08:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   18.538408] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.470685] fuse: init (API version 7.32)
[   26.202888] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[   26.202898] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[   26.202904] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[   26.202908] nouveau 0000:01:00.0: vp: init failed, -2
[   26.202946] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[   26.202950] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[   26.202954] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[   26.202957] nouveau 0000:01:00.0: bsp: init failed, -2
[   56.111109] logitech-hidpp-device 0003:046D:4054.0003: HID++ 4.5 device connected.
Edit: Also at this point error about firmware: failed to load regulatory.db (-2)

Next applied all updates.
Added to grub:
quiet loglevel=3 splash
Install nvidia driver using the MX Tool.

Code: Select all

 libegl1-nvidia-legacy-340xx:amd64 (340.108-11~mx21) ...
 libegl1-nvidia-legacy-340xx:i386 (340.108-11~mx21) ...
 libgl1-nvidia-legacy-340xx-glx:amd64 (340.108-11~mx21) ...
 libgl1-nvidia-legacy-340xx-glx:i386 (340.108-11~mx21) ...
 libnvidia-legacy-340xx-cfg1:amd64 (340.108-11~mx21) ...
 libnvidia-legacy-340xx-cfg1:i386 (340.108-11~mx21) ...
 xserver-xorg-video-nvidia-legacy-340xx (340.108-11~mx21) ...
 nvidia-legacy-340xx-vdpau-driver:amd64 (340.108-11~mx21) ...
 libgles2-nvidia-legacy-340xx:amd64 (340.108-11~mx21) ...
 libgles2-nvidia-legacy-340xx:i386 (340.108-11~mx21) ...
 libgles1-nvidia-legacy-340xx:amd64 (340.108-11~mx21) ...
 libgles1-nvidia-legacy-340xx:i386 (340.108-11~mx21) ...
 nvidia-legacy-340xx-kernel-support (340.108-11~mx21) ...
 nvidia-legacy-340xx-driver-libs:amd64 (340.108-11~mx21) ...
 nvidia-legacy-340xx-driver-libs:i386 (340.108-11~mx21) ...
 libnvidia-legacy-340xx-ml1:amd64 (340.108-11~mx21) ...
 nvidia-legacy-340xx-driver-bin (340.108-11~mx21) ...
 nvidia-legacy-340xx-driver-libs-i386:i386 (340.108-11~mx21) ...
Some dmesg outputl:

Code: Select all

[    8.681975] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[    8.681978] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    8.681981] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    8.681987] cfg80211: failed to load regulatory.db
[    9.054468] nvidia: loading out-of-tree module taints kernel.
[    9.054486] nvidia: module license 'NVIDIA' taints kernel.
[    9.054488] Disabling lock debugging due to kernel taint
[    9.199292] nvidia: module verification failed: signature and/or required key missing - tainting 
Install crda to overcome regulatory failures.
Install wine from the stable repo, to overcome raw surface error when only wine staging was installed (no proper registration for exe files and no menu entries).
Install wine staging from the favorites of MX package installer, because wine staging is properly installed, which is not quite the case with wine stable.
Most of wine stable is automatically removed again by the previous step.
Install ICE-SSB (deb package obtained from Peppermint).
Install games and many other programs.
Install themes.

The problem with the efivars module not found did not reappear (to be expected just before the Nvidia 3 white dots and then the logo appear) and the boot process is significantly quicker now, because displaying the error message was also accompanied by a short startup delay.

Next i could autoremove the orphan packages listed below:

Code: Select all

fonts-wine gstreamer1.0-plugins-good:i386 libsoup2.4-1:i386 glib-networking:i386 gstreamer1.0-x:i386 libaa1:i386 libavc1394-0:i386 libcaca0:i386 libdv4:i386 wine64 libwine libfaudio0 wine32:i386 libwine:i386 libfaudio0:i386 libgudev-1.0-0:i386 libiec61883-0:i386 libmpg123-0:i386 libncursesw6:i386 libproxy1v5:i386 libraw1394-11:i386 libshout3:i386 libslang2:i386 libstb0 libstb0:i386 libtag1v5:i386 libtag1v5-vanilla:i386 libvkd3d1:i386 libvkd3d1 libxv1:i386
Potentially dangerous to remove?
Last edited by gsm on Mon Feb 28, 2022 9:32 am, edited 2 times in total.

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#7 Post by gsm »

Still there is some kind of error listed in the dmesg output:
Tainted kernel:

Code: Select all

[    8.854597] nvidia: loading out-of-tree module taints kernel.
[    8.854616] nvidia: module license 'NVIDIA' taints kernel.
[    8.854618] Disabling lock debugging due to kernel taint
[    9.017558] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    9.170704] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[    9.177477] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0
[    9.177533] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 PST 2019

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#8 Post by gsm »

So i tested again to boot from the same snapshot as before.
Again the snapshot did not boot completely but ended with a blinking cursor.
It appeared that, after Ctrl + Alt and F2, i could login to a command prompt using my username and password.

Edit: First i needed to remove /etc/X11/xorg.conf.

Startx then did the trick and the desktop appeared as expected.
After rebooting the installed system, there was no message about efivars.
So it is not clear what has caused that error message. I cannot reproduce it till now..

NOTE: I use a Ventoy multi ISO USB boot device to load the various Linux live systems.
Last edited by gsm on Wed Mar 09, 2022 5:53 pm, edited 1 time in total.

User avatar
dolphin_oracle
Developer
Posts: 22665
Joined: Sun Dec 16, 2007 12:17 pm

Re: Modprobe: module efivars not found in modules.dep

#9 Post by dolphin_oracle »

there are many unexplained things that happen when ventoy is used.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Live system help document: https://mxlinux.org/wiki/help-antix-live-usb-system/

User avatar
gsm
Posts: 120
Joined: Wed Dec 19, 2018 9:16 am

Re: Modprobe: module efivars not found in modules.dep

#10 Post by gsm »

Thank you.
With Ventoy you need at least to use the latest version to support as many distributions as possible.
I like using Ventoy because i can simply add, remove and boot quite a number of distributions and versions at only one USB boot device.
The Ventoy boot device (HDD) has a partition which MX 21, during the manual selection of partitions for root and Home, automatically allocates as ESP.
Delete or Backspace can simply be used to erase the word ESP avoiding a change to the Ventoy device
MX21 is not the only Linux distribution doing auto allocations of certain partitions.
I will try a snapshot, booting with Ventoy on a USB HDD and with a single USB stick, created by Rufus.

Post Reply

Return to “Software / Configuration”