Failed to start Load Kernel Modules + other errors

KronikPillow

Hi, I'm not sure where to post this, so If I'm in the wrong thread I apologize ... when i boot my Solus 4.0 Budgie, first thing i notice is a error message saying Failed to start Load Kernel Modules ... so i go in to my journalctl and i get the following 2

journalctl -p 3 -xb : https://hastebin.com/ihoxameler.sql
journalctl -b : https://hastebin.com/epoqojivey.coffeescript

can anyone help me debug this?

One thing i specially do not understand, the vbox errors... I'm not running a vbox, I'm running directly on my PC with Solus Budgie 4.0 installed ...

I also noticed that the Intel microcode wasn't installed by default, so i went and installed it via
sudo eopkg install intel-microcode

but I'm sure that I'm missing something ...

my system specs are

kronikpillow@susanoo ~ $ inxi -Fx
System:
  Host: susanoo Kernel: 4.20.16-112.current x86_64 bits: 64 compiler: gcc 
  v: 8.2.0 Desktop: Budgie 10.5 Distro: Solus 4.0 
Machine:
  Type: Desktop Mobo: MSI model: B75MA-E33 (MS-7808) v: 1.0 
  serial: <root required> UEFI: American Megatrends v: 1.7 date: 09/30/2013 
CPU:
  Topology: Quad Core model: Intel Core i5-3350P bits: 64 type: MCP 
  arch: Ivy Bridge rev: 9 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24742 
  Speed: 1596 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1596 4: 1596 
Graphics:
  Device-1: NVIDIA GK106 [GeForce GTX 650 Ti] vendor: Micro-Star MSI 
  driver: nvidia v: 418.43 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.3 driver: nvidia 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 650 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.43 
  direct render: Yes 
Audio:
  Device-1: NVIDIA GK106 HDMI Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Device-2: VIA ICE1712 [Envy24] PCI Multi-Channel I/O driver: snd_ice1712 
  v: kernel bus ID: 04:00.0 
  Device-3: Logitech Webcam C170 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 1-1.5:5 
  Sound Server: ALSA v: k4.20.16-112.current 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: d4:3d:7e:36:c7:04 
Drives:
  Local Storage: total: 945.95 GiB used: 11.34 GiB (1.2%) 
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
  ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 
  size: 14.44 GiB 
Partition:
  ID-1: / size: 43.57 GiB used: 8.63 GiB (19.8%) fs: ext4 dev: /dev/sda6 
  ID-2: /home size: 264.76 GiB used: 2.71 GiB (1.0%) fs: ext4 dev: /dev/sda7 
  ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda8 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 40 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:
  Processes: 216 Uptime: 37m Memory: 7.79 GiB used: 1.86 GiB (23.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 4.4.19 
  inxi: 3.0.32

Staudey

Do you have the virtualbox-guest-common, virtualbox-guest, or virtualbox-guest-current packages installed? Because that would at least explain the vbox errors.

KronikPillow

virtualbox-guest-common & virtualbox-guest-current are installed ... but why are these packages installed on a fresh install of Solud 4.0 Budgie? ? I did not install them

KronikPillow

Ok, i removed virtualbox-guest-common & virtualbox-guest-current and now there is no Kernel Modules errors ...thanks for the note @Staudey , but to be honest that is the weirdest thing I ever saw so far, Solus installing virtual box modules as a regular OS on regular hardware ...

continuation of debugging: https://hastebin.com/ihenicibob.rb

any help much appreciated

kyrios

The virtualbox guest stuffs have been added on the ISO to help the people who boot the live media on a virtual machine but they are not automatically installed !!??

JoshStrobl

kyrios They are automatically installed, I told you during release that I was putting them in the images, as per your request.

They likely are failing because Solus is running as a host, not as a guest inside VirtualBox. Or they didn't work in the first place.

KronikPillow

@kyrios they have installed on my system, I have ran the ISO from a USB, followed the installer, and i just removed the vbox modules from my system, as you can see from the journallogs they were installed .. i for sure did not install them on my hardware my self mate, i didn't even know what they are

kyrios

JoshStrobl Sorry I missed that. I thought it was just on the ISO image. I didn't understood it would be installed as well.

KronikPillow

would be good that the ISO would recognize if it is on a host machine or a vm machine so that it wouldn't install such modules to a host 🙂

Abhisht02

This problem is also present when booting the plasma iso on my laptop (nvidia gpu+ not on vm)

KronikPillow

@JoshStrobl @kyrios another thing i found that is installed on my system, are xorg-driver-video-vmware , xorg-driver-video-radeon, xorg-driver-video-nouveau, xorg-driver-video-intel, xorg-driver-video-fbdev, xorg-driver-video-amdgpu, xorg-driver-video-vesa, xorg-driver-video-qxl ... why are so many video drivers installed on my system? i would understand xorg-driver-video-noveau since i have a NVIDIA graphics card ... are these safe to remove?

Justin

You can remove them but they take up very little room. They are included so that no matter what hardware a person has, it will boot. I'd leave them on there so if you do ever decide to change to an AMD card there's no issues.