Numerous Errors after Installation on Plasma

gdm brings in gnome-session:
https://archlinux.org/packages/extra/x86_64/gdm/

 Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB]
    vendor: Micro-Star MSI driver: N/A

it does not load any driver for the nvidia GPU… what results in what you see (nothing :wink: ) the system is only using the intel igpu from the CPU… it could be that Linux disable the nvidia GPU because display is connected to igpu (motherboard) but this is only a bet on infos we have.
Best would be to see eig the boot log say something more informative about what happens on the GPU and driver loading… also x-logs could tell a story:
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/
journalctl -b -0 | eos-sendlog
cat /var/log/Xorg.0.log | eos-sendlog

Ahh! Thank you for the information and explanation. Sorry for being so confusing. Attached below is my logs.

https://clbin.com/DXbfO
https://clbin.com/eP27n

shows there is a BIOS/Firmware update for your Motherboard…
Not that i say this is the issue… but could be part of the issue …

Jul 20 08:03:48 arch-eos kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel

something is failing on boot:
Jul 20 10:34:44 arch-eos kernel: traps: Missing ENDBR: _nv011433rm+0x0/0x10 [nvidia]
Jul 20 10:34:44 arch-eos kernel: ------------[ cut here ]------------
Jul 20 10:34:44 arch-eos kernel: kernel BUG at arch/x86/kernel/traps.c:252!
Jul 20 10:34:44 arch-eos kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Jul 20 10:34:44 arch-eos kernel: CPU: 8 PID: 370 Comm: systemd-modules Tainted: P           OE     5.18.12-arch1-1 #1 96418c890ae0efcbf26c551e98cb3d72a56d7da8
Jul 20 10:34:44 arch-eos kernel: Hardware name: ASUS System Product Name/PRIME B660M-A WIFI D4, BIOS 0423 10/18/2021
Jul 20 10:34:44 arch-eos kernel: RIP: 0010:exc_control_protection+0xc2/0xd0
Jul 20 10:34:44 arch-eos kernel: Code: 8b 93 80 00 00 00 be f9 00 00 00 48 c7 c7 4b e1 c6 bd e8 e1 d3 4f ff e9 72 ff ff ff 48 c7 c7 32 e1 c6 bd e8 cb 21 fb ff 0f 0b <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 66 0f 1f 00 55 53 48 89
Jul 20 10:34:44 arch-eos kernel: RSP: 0018:ffffabbac130bc08 EFLAGS: 00010002
Jul 20 10:34:44 arch-eos kernel: RAX: 0000000000000033 RBX: ffffabbac130bc28 RCX: 0000000000000027
Jul 20 10:34:44 arch-eos kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff99621f6216a0
Jul 20 10:34:44 arch-eos kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffabbac130ba28
Jul 20 10:34:44 arch-eos kernel: R10: 0000000000000003 R11: ffffffffbe4caa08 R12: 0000000000000000
Jul 20 10:34:44 arch-eos kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jul 20 10:34:44 arch-eos kernel: FS:  00007fd5ee8e2200(0000) GS:ffff99621f600000(0000) knlGS:0000000000000000
Jul 20 10:34:44 arch-eos kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 20 10:34:44 arch-eos kernel: CR2: 000055599065a000 CR3: 00000001043b4001 CR4: 0000000000f70ee0
Jul 20 10:34:44 arch-eos kernel: PKRU: 55555554
Jul 20 10:34:44 arch-eos kernel: Call Trace:
Jul 20 10:34:44 arch-eos kernel:  <TASK>
Jul 20 10:34:44 arch-eos kernel:  asm_exc_control_protection+0x22/0x30
Jul 20 10:34:44 arch-eos kernel: RIP: 0010:_nv011433rm+0x0/0x10 [nvidia]
Jul 20 10:34:44 arch-eos kernel: Code: 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 57 10 1e 00 48 83 c4 08 48 89 c7 e9 bb ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 89 f7 e9 18 08 00 00 0f 1f 84 00 00 00 00 00 48 89 f7 e9 18 08
Jul 20 10:34:44 arch-eos kernel: RSP: 0018:ffffabbac130bcd8 EFLAGS: 00010202
Jul 20 10:34:44 arch-eos kernel: RAX: ffffffffc0dbd8f0 RBX: ffffffffc2fd2170 RCX: 0000000000000000
Jul 20 10:34:44 arch-eos kernel: RDX: 00000000000985f4 RSI: 0000000000000010 RDI: ffffffffc2fd2170
Jul 20 10:34:44 arch-eos kernel: RBP: ffff995adccc5fe0 R08: 0000000000000020 R09: ffffffffc2fd21b0
Jul 20 10:34:44 arch-eos kernel: R10: ffffffffc2f88eb0 R11: 0000000000000000 R12: 0000000000000010
Jul 20 10:34:44 arch-eos kernel: R13: ffff995adccc3000 R14: 00007fd5ef2c8343 R15: ffffabbac130be58
Jul 20 10:34:44 arch-eos kernel:  ? _nv034913rm+0x20/0x20 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv011431rm+0x24/0xe0 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv034914rm+0xe/0xa0 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv034917rm+0x1d/0x30 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv034919rm+0x2f/0x40 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv015567rm+0x15/0x70 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  _nv000642rm+0x9/0x20 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  ? cdev_add+0x4d/0x60
Jul 20 10:34:44 arch-eos kernel:  rm_init_rm+0x17/0x60 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  nvidia_init_module+0x242/0x613 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  ? nvidia_init_module+0x613/0x613 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  nvidia_frontend_init_module+0x50/0x91 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  ? nvidia_init_module+0x613/0x613 [nvidia 3d1366ee8bc9aa4f701e0e4cfb4072684b4c63e1]
Jul 20 10:34:44 arch-eos kernel:  do_one_initcall+0x5a/0x220
Jul 20 10:34:44 arch-eos kernel:  do_init_module+0x4a/0x240
Jul 20 10:34:44 arch-eos kernel:  __do_sys_init_module+0x138/0x1b0
Jul 20 10:34:44 arch-eos kernel:  do_syscall_64+0x5c/0x90
Jul 20 10:34:44 arch-eos kernel:  ? exc_page_fault+0x74/0x170
Jul 20 10:34:44 arch-eos kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jul 20 10:34:44 arch-eos kernel: RIP: 0033:0x7fd5eeb1299e
Jul 20 10:34:44 arch-eos kernel: Code: 48 8b 0d fd a3 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ca a3 0e 00 f7 d8 64 89 01 48
Jul 20 10:34:44 arch-eos kernel: RSP: 002b:00007ffe48903c28 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
Jul 20 10:34:44 arch-eos kernel: RAX: ffffffffffffffda RBX: 000055aeb04a7a70 RCX: 00007fd5eeb1299e
Jul 20 10:34:44 arch-eos kernel: RDX: 00007fd5ef2c8343 RSI: 0000000003cd4885 RDI: 00007fd5e710f010
Jul 20 10:34:44 arch-eos kernel: RBP: 00007fd5ef2c8343 R08: 0000000002061000 R09: 9e3779b185ebca87
Jul 20 10:34:44 arch-eos kernel: R10: 00000000000176e1 R11: 0000000000000246 R12: 0000000000020000
Jul 20 10:34:44 arch-eos kernel: R13: 000055aeb04a7b40 R14: 000055aeb04a7a70 R15: 000055aeb04a7ca0
Jul 20 10:34:44 arch-eos kernel:  </TASK>
Jul 20 10:34:44 arch-eos kernel: Modules linked in: pcc_cpufreq(-) acpi_cpufreq(-) vfat fat nvidia(POE+) mac_hid crypto_user fuse bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid nvme xhci_pci crc32c_intel nvme_core xhci_pci_renesas vmd
Jul 20 10:34:44 arch-eos kernel: ---[ end trace 0000000000000000 ]---

So something is causing this issue… nvidia module and gpu is not getting activated and can not load the driver…

I’ve just updated my BIOS but it seems like that module verification is still failing. Any thoughts?

https://clbin.com/ms5xl
https://clbin.com/0WccM

possible to get me this ?
pacman -Qs nvidia

Sorry for the delay in getting you this.

https://clbin.com/hUJ1F

@YourMCGeek
It should work with kernel parameter ibt=off in the default grub command line and then update grub.

1 Like

so using nvidia-dkms package… i would try the kernel option from the post I mentioned before sam as what rick giving… ibt=off

Ask if you do not know how to do that…

Other things to try is using the LTS kernel or try to replace nvidia-dkms with nvidia package… mostlikely it will be the same (should be) but could be an issue with dkms.

Thank you both for this. If I’m not mistaken I’ve already tried with ibt=off per @ricklinux’s comment 3 days ago. Is this not the same or am I mistaken?

I’m surprised then if it didn’t work. :thinking: Are you sure you did it correctly? It has to be added to the default grub command line and then you have to update grub with the proper command.

I followed your steps here,

Edit: You need to use a text editor and add it to /etc/default/grub in the command line. Then update grub with sudo grub-mkconfig -o /boot/grub/grub.cfg

Are these the correct steps? I can try again if needed

Did you put it in this top line? Not the one below it or it doesn’t read it. Then you update grub.

Example:

GRUB_CMDLINE_LINUX_DEFAULT="amd_pstate.shared_mem=1 loglevel=3 nowatchdog nvme_load=YES"
GRUB_CMDLINE_LINUX=""

Edit: I have an amd processor so my grub command line will be different.

Oops. I put it at the end of the file, apologies for being silly. I’ve now updated it and rebooted, all I get is the gray screen from GNOME though it seems. Nothing ever pops up besides that gray screen. I left it there for about 3-5 minutes. Apologies for the pictures.
image
image
image

It should be added to the grub command line like this as an example.

GRUB_CMDLINE_LINUX_DEFAULT="ibt=off loglevel=3 nowatchdog nvme_load=YES"

Edit: Then update grub.

I see the compositor as gnome-shell. This is not plasma. As i said before i wouldn’t install gnome and plasma together. :man_shrugging:

Again, Im not sure how I got gnome. It wasn’t intentional, but I guess gnome came in via GDM like @joekamprad stated? I could switch to SDDM to see if the issues are resolved, but I’m not confident. I can provide you my grub command line later tonight

1 Like

Here’s my command line. I’ve also changed to SDDM and it seems to be working just fine now! Im sorry for so many issues. One final question, I’m running Plasma on Wayland, is this okay or should I be trying it on X11 instead?


GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="EndeavourOS"
GRUB_CMDLINE_LINUX_DEFAULT="ibt=off loglevel=3 nowatchdog nvme_load=YES nvidia-drm.modeset=1"
GRUB_CMDLINE_LINUX=""

I use x11 but there is nothing wrong with using wayland if it works okay for you. Some software such as simplescreenrecorder doesn’t work on Wayland so you would have to fins something equivalent that would work for you on Wayland. Could you give the output now of

inxi -Ga

Good to know, thank you.

  Device-1: Intel AlderLake-S GT1 vendor: ASUSTeK driver: i915 v: kernel
    ports: active: HDMI-A-2 empty: DP-1,HDMI-A-1,HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:4680 class-ID: 0300
  Device-2: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Micro-Star MSI
    driver: nvidia v: 515.57 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-06) arch: Pascal process: TSMC 16nm
    built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: none off: DP-2 empty: DVI-D-1,HDMI-A-4
    bus-ID: 01:00.0 chip-ID: 10de:1c03 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_wayland driver: X: loaded: intel,nvidia
    unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: i915,nvidia
    d-rect: 3920x1440 display-ID: 0
  Monitor-1: DP-2 pos: primary,left res: 2560x1440 size: N/A modes: N/A
  Monitor-2: HDMI-A-2 pos: right res: 1360x768 size: N/A modes: N/A
  OpenGL: renderer: Mesa Intel Graphics (ADL-S GT1) v: 4.6 Mesa 22.1.3
    direct render: Yes

So currently it is running on the intel on the Hdmi which i assume is the motherboard port as that’s how they work only on integrated graphics. So you do also have another monitor on displayport? Is that working?

Current Nvidia drivers are installed.