[SOLVED] Can't get GPU to use nvidia driver

sourproton · 2023-06-02 12:52:47

To install plasma, I first installed the xorg group (pacman -S xorg). Can this be related to the problem?

V1del · 2023-06-02 15:35:33

No. Your driver crashes, installation order is completely irrelevant here. This is either something very broken on the HW level (in which case you should RMA it) or firmware or you have found some bug in the driver

Last messages still being retained can be normal and is not immediately cause for concern. The weird thing about this new journal however is

juin 02 14:18:23 sabbath kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:28a1)
                                 NVRM: installed in this system is not supported by the
                                 NVRM: NVIDIA 530.41.03 driver release.
                                 NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products'
                                 NVRM: in this release's README, available on the operating system
                                 NVRM: specific graphics driver download page at www.nvidia.com.
juin 02 14:18:23 sabbath kernel: nvidia: probe of 0000:01:00.0 failed with error -1
juin 02 14:18:23 sabbath kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
juin 02 14:18:23 sabbath kernel: NVRM: None of the NVIDIA devices were initialized.
juin 02 14:18:23 sabbath kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 234

which makes little sense to me... It might be worth trying the current beta driver that got released 2 days ago here which would mandate some custom PKGBUILDS. Install linux-headers, grab a copy of https://gitlab.archlinux.org/archlinux/ … idia-utils and adjust the pkgver to 535.43.02 and run a makepkg -s on it, install the resulting nvidia-utils and nvidia-dkms packages. For some more general info, see https://wiki.archlinux.org/title/Arch_build_system

Last edited by V1del (2023-06-02 16:33:34)

sourproton · 2023-06-02 17:12:58

I tried following your instructions but the makepkg -s command fails

> $ makepkg -s
==> Making package: nvidia-utils 535.43.02-1 (ven. 02 juin 2023 19:09:35)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
[sudo] password for sourproton:
resolving dependencies...
looking for conflicting packages...

Packages (1) patchelf-0.18.0-1

Total Download Size:   0.10 MiB
Total Installed Size:  0.24 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
 patchelf-0.18.0-1-...    98.2 KiB   491 KiB/s 00:00 [############################] 100%
(1/1) checking keys in keyring                       [############################] 100%
(1/1) checking package integrity                     [############################] 100%
(1/1) loading package files                          [############################] 100%
(1/1) checking for file conflicts                    [############################] 100%
(1/1) checking available disk space                  [############################] 100%
:: Processing package changes...
(1/1) installing patchelf                            [############################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
==> Retrieving sources...
  -> Found nvidia-drm-outputclass.conf
  -> Found nvidia-utils.sysusers
  -> Found nvidia.rules
  -> Downloading NVIDIA-Linux-x86_64-535.43.02.run...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  330M  100  330M    0     0  3653k      0  0:01:32  0:01:32 --:--:-- 3647k
==> Validating source files with sha512sums...
    nvidia-drm-outputclass.conf ... Passed
    nvidia-utils.sysusers ... Passed
    nvidia.rules ... Passed
    NVIDIA-Linux-x86_64-535.43.02.run ... FAILED
==> ERROR: One or more files did not pass the validity check!

I tried downloading the nvidia-beta package from the AUR too but I have conflicts with nvidia-utils that is a dependency of steam

V1del · 2023-06-02 17:20:50

Ah whoops, run updpkgsums from pacman-contrib in the pkgbuild directory and retry (or replace the last entry in sha256sum array with 'SKIP')

Last edited by V1del (2023-06-02 17:24:36)

sourproton · 2023-06-02 17:43:57

I'll try that and report here.

For the sake of completeness, when booting from the LTS kernel, without nvidia drivers installed, KDE is still veeeeeery sluggish. The screen only updates when I move the mouse and if I zig zag with the mouse, it updates at a ~2 fps rate.

Here is the jounrnal from the LTS kernel boot.

I don't know if these problems are related.

seth · 2023-06-02 17:47:07

nouveau isn't loaded (and likely won't support that chip either) so the only way you can use KDE is on the fbdev or vesa X11 drivers and yeah: that's gonna suck.

sourproton · 2023-06-02 17:48:39

I still can't build the package

sourproton@sabbath ~/Downloads/nvidia-utils-main                             [19:45:41]
> $ updpkgsums
==> Retrieving sources...
  -> Found nvidia-drm-outputclass.conf
  -> Found nvidia-utils.sysusers
  -> Found nvidia.rules
  -> Found NVIDIA-Linux-x86_64-535.43.02.run
==> Generating checksums for source files...

sourproton@sabbath ~/Downloads/nvidia-utils-main                             [19:45:56]
> $ makepkg -s
==> Making package: nvidia-utils 535.43.02-1 (ven. 02 juin 2023 19:46:08)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found nvidia-drm-outputclass.conf
  -> Found nvidia-utils.sysusers
  -> Found nvidia.rules
  -> Found NVIDIA-Linux-x86_64-535.43.02.run
==> Validating source files with sha512sums...
    nvidia-drm-outputclass.conf ... Passed
    nvidia-utils.sysusers ... Passed
    nvidia.rules ... Passed
    NVIDIA-Linux-x86_64-535.43.02.run ... Passed
==> Extracting sources...
==> Starting prepare()...
Creating directory NVIDIA-Linux-x86_64-535.43.02
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 535.43.02.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==> Entering fakeroot environment...
==> Starting package_nvidia-utils()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "nvidia-utils"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Starting package_opencl-nvidia()...
install: cannot stat 'libnvidia-compiler.so.535.43.02': No such file or directory
==> ERROR: A failure occurred in package_opencl-nvidia().
    Aborting...

Sorry I'm taking baby steps now, this is pretty new territory to me.

I'm really surprised by how hard this turned out to be, specially because as I said before, the laptop arrived tuesday, when I did the clean install and made minecraft work with nvidia-prime, and after an update everything melt down.

sourproton · 2023-06-02 17:54:12

nouveau isn't loaded

Is there a reason it loads on linux but not on linux-lts?

(and likely won't support that chip either)

Why do you think that? When you say chip, you say the intel or nvidia one ?

seth · 2023-06-02 17:56:24

https://gitlab.archlinux.org/archlinux/ … GBUILD#L69
Comment that line, you can also skip opencl entirely (it's not required for basic functionality)

Your GPU is very new, this is why we're trying the latest binary nvidia driver and why I'd not bet no nouveau at all.
It's also the reason why you're having a bit of a struggle here.

nouveau should™ be blacklisted by nvidia-utils, the only way it can load despite if it's in the initramfs (something you'll have to clean up anyway)

----
Edit: sorry, I missed that this is an optimus system and you're likely running KDE on i915/modesetting.
Please post the output of "glxinfo -B" and your xorg log in this case, https://wiki.archlinux.org/title/Xorg#General

Edit #2: … and you're running a wayland session, try the behavior of plasma on X11 first.

Edit #3: and pay attention to the CPU/Disk IO usage

juin 02 19:25:33 sabbath systemd[846]: Starting Baloo File Indexer Daemon...
juin 02 19:25:33 sabbath systemd[846]: Started Baloo File Indexer Daemon.

can be pretty resource hogging.

Last edited by seth (2023-06-02 18:04:19)

sourproton · 2023-06-02 18:22:12

Here is the log from the X11 session with lts kernel. It's sluggish like the plasma session.

I ran "top" to watch for resource hogging but baloo wasn't there. The system is new (installed today) and always ran with KDE, so baloo already did all the indexing.

> $ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Graphics (RPL-P) (0xa7a0)
    Version: 23.1.1
    Accelerated: yes
    Video memory: 15717MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

sourproton · 2023-06-02 18:23:57

Also, commenting the line worked to build the package. I installed the then-generated nvidia-utils and nvidia-dkms packages but the boot crashed all the same.

Here is the journal

V1del · 2023-06-02 18:42:15

The nvidia module loads properly but there's not much else, however seeing as this is the LTS kernel, did you install linux-lts-headers as well and do not have a potentially existing nvidia-lts that is still the old version? In case you'd need to remove nvidia-lts and install linux-lts-headers and pay attention to the pacman output because you'll see the kernel module for the new nvidia-dkms being built, maybe post

pacman -Qs nvidia
dkms status

sourproton · 2023-06-02 18:46:19

There were no nvidia drivers installed previously. If they were installed, the system wouldn't boot. linux-headers and linux-lts-headers are installed and I can see the initramfs being built for both when installing the dkms package (either from the repo or the just recently built from source).

I have since uninstalled them to boot again. I need to chroot to uninstall them.

sourproton@sabbath ~                                                 [20:43:22]
> $ pacman -Qs nvidia
local/egl-wayland 2:1.1.11-4
    EGLStream-based Wayland external platform
local/lib32-nvidia-utils 530.41.03-1
    NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-1
    Nvidia VDPAU library
local/nvidia-prime 1.0-4
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-utils 530.41.03-1
    NVIDIA drivers utilities

sourproton@sabbath ~                                                 [20:43:29]
> $ dkms status

V1del · 2023-06-02 18:50:49

There's not much point in installing the known broken nvidia driver, how do these look with the beta drivers installed? FWIW I doubt you need to chroot, adding module_blacklist=nvidia,nvidia-uvm,nvidia-drm to the kernel commandline if necessary should clean this up relevantly: https://wiki.archlinux.org/title/Kernel … and_line_2

FWIW I find it very well possible that there's also a bug with that intel gpu and the interactions that would have to take place, but then we'd go into rc/unstable kernel release territory to try and get fixes here.

Last edited by V1del (2023-06-02 18:53:11)

sourproton · 2023-06-02 18:51:50

#36 is the journal from the crashed boot with the beta built-from-source drivers

---

EDIT I'll reinstall them and boot to multi-user.target and post the output of the commands. Then I'll uninstall them so I can boot to the GUI.

Last edited by sourproton (2023-06-02 18:53:51)

V1del · 2023-06-02 18:55:06

I'm aware but in that log theres no indication of an issue and if the crash was just on the xorg level because e.g. a mismatch in nvidia-utils that would be interesting. reinstalling them and posting the output directly from multi-user target without having provoked a crash isn't really useful, if you can boot into multi-user.target, what happens if you then try to run a graphical session manually?

Last edited by V1del (2023-06-02 18:58:36)

sourproton · 2023-06-02 18:55:28

V1del wrote:

adding module_blacklist=nvidia,nvidia-uvm,nvidia-drm to the kernel commandline

I need "editor yes" on loader.conf for that, don't I?

seth · 2023-06-02 19:04:37

https://wiki.archlinux.org/title/Kernel … stemd-boot

wrt the sluggishness, does it happen if you remove the external display?

When the system "crashes" can you still switch the VT?
What if you boot the multi-user.target and run startx from there (make sure to at least install xterm)?

sourproton · 2023-06-02 19:08:46

wrt the sluggishness, does it happen if you remove the external display?

Yes, the external display plays no role in it.

When the system "crashes" can you still switch the VT?

No. That's why I've been installing nvidia, crashing, chrooting to uninstall nvidia and boot again.

What if you boot the multi-user.target and run startx from there (make sure to at least install xterm)?

Will do and report. I just re-installed the beta drivers and changed the target. Will boot to run pacman -Qs nvidia and dkms status. Here's the install process:

sourproton@sabbath ~/Downloads/nvidia-utils-main                     [21:00:12]
> $ ls
nvidia-dkms-535.43.02-1-x86_64.pkg.tar.zst
nvidia-drm-outputclass.conf
NVIDIA-Linux-x86_64-535.43.02.run
nvidia.rules
nvidia-utils-535.43.02-1-x86_64.pkg.tar.zst
nvidia-utils.install
nvidia-utils.sysusers
opencl-nvidia-535.43.02-1-x86_64.pkg.tar.zst
pkg
PKGBUILD
src
term.txt

sourproton@sabbath ~/Downloads/nvidia-utils-main                     [21:00:13]
> $ sudo pacman -U nvidia-dkms-535.43.02-1-x86_64.pkg.tar.zst nvidia-utils-535.43.02-1-x86_64.pkg.tar.zst
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (2) nvidia-dkms-535.43.02-1  nvidia-utils-535.43.02-1

Total Installed Size:  611.62 MiB
Net Upgrade Size:      -47.14 MiB

:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring                     [######################] 100%
(2/2) checking package integrity                   [######################] 100%
(2/2) loading package files                        [######################] 100%
(2/2) checking for file conflicts                  [######################] 100%
(2/2) checking available disk space                [######################] 100%
:: Processing package changes...
(1/2) upgrading nvidia-utils                       [######################] 100%
If you run into trouble with CUDA not being available, run nvidia-modprobe first.
If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
(2/2) installing nvidia-dkms                       [######################] 100%
:: Running post-transaction hooks...
(1/6) Creating system user accounts...
(2/6) Reloading system manager configuration...
(3/6) Reloading device manager configuration...
(4/6) Arming ConditionNeedsUpdate...
(5/6) Install DKMS modules
==> dkms install --no-depmod nvidia/535.43.02 -k 6.3.5-arch1-1
==> dkms install --no-depmod nvidia/535.43.02 -k 6.1.31-1-lts
==> depmod 6.3.5-arch1-1
==> depmod 6.1.31-1-lts
(6/6) Reloading system bus configuration...

sourproton@sabbath ~/Downloads/nvidia-utils-main                     [21:02:19]
> $ sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.31-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.1.31-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img --microcode /boot/intel-ucode.img
==> Starting build: '6.3.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.3.5-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful

seth · 2023-06-02 19:10:10

No. That's why I've been installing nvidia, crashing, chrooting to uninstall nvidia and boot again.

Can you ssh into the system?

sourproton · 2023-06-02 19:16:04

I don't know how to set up such SSH tunnel, nor what to do to try and connect when it crashes.

I'm writing from my phone now. The system booted to the multi-user target and lspci shows the GPU is using "nvidia" (even though I installed beta nvidia-dkms as shown above). I saved the output of the pacman and dkms commands, will upload soon after uninstalling nvidia and rebooting.

I installed xterm but the startx command is not available.

Last edited by sourproton (2023-06-02 19:20:08)

seth · 2023-06-02 19:23:49

https://archlinux.org/packages/extra/x86_64/xorg-xinit/

sourproton · 2023-06-02 19:23:58

So I said above I re-installed the beta nvidia-dkms and nvidia-utils packages and booted to multi-users with standard linux kernel.

Here is the journal.

lspci -k | grep -A 2 -E 3D:

01:00.0 3D controller: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] (rev a1)
	Subsystem: Lenovo GN21-X2
	Kernel driver in use: nvidia

dkms status:

nvidia/535.43.02, 6.1.31-1-lts, x86_64: installed
nvidia/535.43.02, 6.3.5-arch1-1, x86_64: installed

seth · 2023-06-02 19:28:55

juin 02 21:10:29 sabbath kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0

The driver picked up your GPU and there're no further errors with it, but

juin 02 21:10:30 sabbath kernel: ------------[ cut here ]------------
juin 02 21:10:30 sabbath kernel: i915 0000:00:02.0: Port A asks to use VBT vswing/preemph tables
juin 02 21:10:30 sabbath kernel: WARNING: CPU: 3 PID: 432 at drivers/gpu/drm/i915/display/intel_bios.c:2709 intel_bios_init+0x19c6/0x2090 [i915]
juin 02 21:10:30 sabbath kernel: Modules linked in: usbnet(+) hid_logitech_dj(+) mousedev(+) mac80211(+) snd_pcm_dmaengine(+) kvm_intel(+) snd_hda_intel i915(+) libarc4 snd_intel_dspcfg snd_intel_sdw_acpi kvm snd_hda_codec btusb irqbypass btrtl crct10dif_pclmul snd_hda_core crc32_pclmul btbcm polyval_clmulni btintel uvcvideo polyval_generic gf128mul btmtk ghash_clmulni_intel snd_hwdep drm_buddy videobuf2_vmalloc sha512_ssse3 bluetooth i2c_algo_bit iTCO_wdt uvc aesni_intel pmt_telemetry snd_pcm iwlwifi ttm intel_pmc_bxt processor_thermal_device_pci videobuf2_memops hid_multitouch crypto_simd videobuf2_v4l2 r8152 processor_thermal_device vfat cryptd mei_pxp mei_hdcp iTCO_vendor_support pmt_class intel_rapl_msr rapl intel_cstate usbhid mii ecdh_generic wmi_bmof fat processor_thermal_rfim videodev drm_display_helper snd_timer nvidia_drm(POE) ideapad_laptop intel_uncore ucsi_acpi pcspkr processor_thermal_mbox nvidia_modeset(POE) spi_nor snd cfg80211 typec_ucsi intel_ish_ipc(+) platform_profile i2c_i801 videobuf2_common cec
juin 02 21:10:30 sabbath kernel:  processor_thermal_rapl intel_lpss_pci mei_me mtd thunderbolt video typec intel_lpss i2c_hid_acpi mei soundcore i2c_smbus intel_ishtp rfkill idma64 intel_vsec intel_gtt intel_rapl_common roles mc int3403_thermal i2c_hid intel_hid int3400_thermal int340x_thermal_zone wmi sparse_keymap acpi_pad acpi_thermal_rel acpi_tad mac_hid nvidia_uvm(POE) nvidia(POE) crypto_user fuse dm_mod loop bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd nvme libps2 vivaldi_fmap nvme_core spi_intel_pci crc32c_intel xhci_pci nvme_common spi_intel i8042 xhci_pci_renesas serio
juin 02 21:10:30 sabbath kernel: CPU: 3 PID: 432 Comm: (udev-worker) Tainted: P           OE      6.3.5-arch1-1 #1 649d963afc0261175aabf0511660febbb7b06177
juin 02 21:10:30 sabbath kernel: Hardware name: LENOVO 82Y7/LNVNB161216, BIOS LWCN22WW 03/07/2023
juin 02 21:10:30 sabbath kernel: RIP: 0010:intel_bios_init+0x19c6/0x2090 [i915]
juin 02 21:10:30 sabbath kernel: Code: 48 8b 7d 08 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 ef 75 3d f5 44 89 e1 48 89 da 48 c7 c7 78 9c 05 c7 48 89 c6 e8 3a db b9 f4 <0f> 0b e9 7c f8 ff ff 80 fa 01 45 19 d2 41 81 e2 15 b7 ff ff 41 81
juin 02 21:10:30 sabbath kernel: RSP: 0018:ffffb18dc3b43a88 EFLAGS: 00010286
juin 02 21:10:30 sabbath kernel: RAX: 0000000000000000 RBX: ffff9b0c430b3770 RCX: 0000000000000027
juin 02 21:10:30 sabbath kernel: RDX: ffff9b0fdf6e1688 RSI: 0000000000000001 RDI: ffff9b0fdf6e1680
juin 02 21:10:30 sabbath kernel: RBP: ffff9b0c6ca20000 R08: 0000000000000000 R09: ffffb18dc3b43918
juin 02 21:10:30 sabbath kernel: R10: 0000000000000003 R11: ffff9b0fefbad8a8 R12: 0000000000000041
juin 02 21:10:30 sabbath kernel: R13: 0000000000000000 R14: ffff9b0c6ca20000 R15: 0000000000000000
juin 02 21:10:30 sabbath kernel: FS:  00007f8f82e50200(0000) GS:ffff9b0fdf6c0000(0000) knlGS:0000000000000000
juin 02 21:10:30 sabbath kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
juin 02 21:10:30 sabbath kernel: CR2: 00007ffee9404438 CR3: 0000000104b52000 CR4: 0000000000f50ee0
juin 02 21:10:30 sabbath kernel: PKRU: 55555554
juin 02 21:10:30 sabbath kernel: Call Trace:
juin 02 21:10:30 sabbath kernel:  <TASK>
juin 02 21:10:30 sabbath kernel:  ? intel_bios_init+0x19c6/0x2090 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  ? __warn+0x81/0x130
juin 02 21:10:30 sabbath kernel:  ? intel_bios_init+0x19c6/0x2090 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  ? report_bug+0x171/0x1a0
juin 02 21:10:30 sabbath kernel:  ? prb_read_valid+0x1b/0x30
juin 02 21:10:30 sabbath kernel:  ? handle_bug+0x3c/0x80
juin 02 21:10:30 sabbath kernel:  ? exc_invalid_op+0x17/0x70
juin 02 21:10:30 sabbath kernel:  ? asm_exc_invalid_op+0x1a/0x20
juin 02 21:10:30 sabbath kernel:  ? intel_bios_init+0x19c6/0x2090 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  ? intel_bios_init+0x19c6/0x2090 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  intel_modeset_init_noirq+0x39/0x260 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  i915_driver_probe+0x63a/0xc50 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  local_pci_probe+0x42/0xa0
juin 02 21:10:30 sabbath kernel:  pci_device_probe+0xc1/0x260
juin 02 21:10:30 sabbath kernel:  ? sysfs_do_create_link_sd+0x6e/0xe0
juin 02 21:10:30 sabbath kernel:  really_probe+0x19b/0x3e0
juin 02 21:10:30 sabbath kernel:  ? __pfx___driver_attach+0x10/0x10
juin 02 21:10:30 sabbath kernel:  __driver_probe_device+0x78/0x160
juin 02 21:10:30 sabbath kernel:  driver_probe_device+0x1f/0x90
juin 02 21:10:30 sabbath kernel:  __driver_attach+0xd2/0x1c0
juin 02 21:10:30 sabbath kernel:  bus_for_each_dev+0x85/0xd0
juin 02 21:10:30 sabbath kernel:  bus_add_driver+0x116/0x220
juin 02 21:10:30 sabbath kernel:  driver_register+0x59/0x100
juin 02 21:10:30 sabbath kernel:  i915_init+0x22/0xc0 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  ? __pfx_init_module+0x10/0x10 [i915 0064ab97cf984a3bd35172634e1d6f65877e9eef]
juin 02 21:10:30 sabbath kernel:  do_one_initcall+0x5a/0x240
juin 02 21:10:30 sabbath kernel:  do_init_module+0x4a/0x200
juin 02 21:10:30 sabbath kernel:  __do_sys_init_module+0x17f/0x1b0
juin 02 21:10:30 sabbath kernel:  do_syscall_64+0x5d/0x90
juin 02 21:10:30 sabbath kernel:  ? syscall_exit_to_user_mode+0x1b/0x40
juin 02 21:10:30 sabbath kernel:  ? do_syscall_64+0x6c/0x90
juin 02 21:10:30 sabbath kernel:  ? exc_page_fault+0x7c/0x180
juin 02 21:10:30 sabbath kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
juin 02 21:10:30 sabbath kernel: RIP: 0033:0x7f8f83121f9e
juin 02 21:10:30 sabbath kernel: Code: 48 8b 0d bd ed 0c 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 8a ed 0c 00 f7 d8 64 89 01 48
juin 02 21:10:30 sabbath kernel: RSP: 002b:00007ffee940d6c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
juin 02 21:10:30 sabbath kernel: RAX: ffffffffffffffda RBX: 0000556db3c94a90 RCX: 00007f8f83121f9e
juin 02 21:10:30 sabbath kernel: RDX: 00007f8f836c5343 RSI: 00000000008037be RDI: 00007f8f80a4e010
juin 02 21:10:30 sabbath kernel: RBP: 00007f8f836c5343 R08: 0000000000261000 R09: 0000000000000000
juin 02 21:10:30 sabbath kernel: R10: 0000000000012571 R11: 0000000000000246 R12: 0000000000020000
juin 02 21:10:30 sabbath kernel: R13: 0000556db3bb9c00 R14: 0000556db3c94a90 R15: 0000556db3c7ff50
juin 02 21:10:30 sabbath kernel:  </TASK>
juin 02 21:10:30 sabbath kernel: ---[ end trace 0000000000000000 ]---

Not suer whether that becomes a problem.

sourproton · 2023-06-02 19:37:03

Do you think it's still valuable to know what happens if I run startx with the drivers installed from the multi-user target?

To rule out a hardware problem, would you say it is worth it installing Ubuntu or Windows to see what happens? I'll reinforce that I got that machine on Tuesday, when I did its first OS install and got to run KDE with nvidia and launch minecraft using nvidia-prime. Minecraft's F3 screen confirmed the game was running with the nvidia GPU. It was Tuesday night or Wednesday morning that I ran yay to upgrade the kernel (and nvidia?) and I started having this freeze during boot.

Arch Linux

#26 2023-06-02 12:52:47

Re: [SOLVED] Can't get GPU to use nvidia driver

#27 2023-06-02 15:35:33

Re: [SOLVED] Can't get GPU to use nvidia driver

#28 2023-06-02 17:12:58

Re: [SOLVED] Can't get GPU to use nvidia driver

#29 2023-06-02 17:20:50

Re: [SOLVED] Can't get GPU to use nvidia driver

#30 2023-06-02 17:43:57

Re: [SOLVED] Can't get GPU to use nvidia driver

#31 2023-06-02 17:47:07

Re: [SOLVED] Can't get GPU to use nvidia driver

#32 2023-06-02 17:48:39

Re: [SOLVED] Can't get GPU to use nvidia driver

#33 2023-06-02 17:54:12

Re: [SOLVED] Can't get GPU to use nvidia driver

#34 2023-06-02 17:56:24

Re: [SOLVED] Can't get GPU to use nvidia driver

#35 2023-06-02 18:22:12

Re: [SOLVED] Can't get GPU to use nvidia driver

#36 2023-06-02 18:23:57

Re: [SOLVED] Can't get GPU to use nvidia driver

#37 2023-06-02 18:42:15

Re: [SOLVED] Can't get GPU to use nvidia driver

#38 2023-06-02 18:46:19

Re: [SOLVED] Can't get GPU to use nvidia driver

#39 2023-06-02 18:50:49

Re: [SOLVED] Can't get GPU to use nvidia driver

#40 2023-06-02 18:51:50

Re: [SOLVED] Can't get GPU to use nvidia driver

#41 2023-06-02 18:55:06

Re: [SOLVED] Can't get GPU to use nvidia driver

#42 2023-06-02 18:55:28

Re: [SOLVED] Can't get GPU to use nvidia driver

#43 2023-06-02 19:04:37

Re: [SOLVED] Can't get GPU to use nvidia driver

#44 2023-06-02 19:08:46

Re: [SOLVED] Can't get GPU to use nvidia driver

#45 2023-06-02 19:10:10

Re: [SOLVED] Can't get GPU to use nvidia driver

#46 2023-06-02 19:16:04

Re: [SOLVED] Can't get GPU to use nvidia driver

#47 2023-06-02 19:23:49

Re: [SOLVED] Can't get GPU to use nvidia driver

#48 2023-06-02 19:23:58

Re: [SOLVED] Can't get GPU to use nvidia driver

#49 2023-06-02 19:28:55

Re: [SOLVED] Can't get GPU to use nvidia driver

#50 2023-06-02 19:37:03

Re: [SOLVED] Can't get GPU to use nvidia driver

Board footer