Hybrid Nvidia laptop won't boot when I switch to Nvidia GPU

stepanzak · May 15, 2023, 6:16pm

Hi, my friend just got a new laptop HP Victus 16 and we installed EndeavourOS KDE Plasma edition here. It has NVIDIA GeForce RTX 3050.

The problem:

The laptop was using only integrated intel GPU. The nvidia-settings was showing the Nvidia GPU, but it was 0% in use.

What we did:

We tried different things that didn’t work, but then we installed Envy Control.
We run sudo envycontrol -s nvidia and rebooted the system.

What happened:

This error showed up and even after a long time, the system didn’t boot. However, this error happens on every boot on this laptop, so it’s just that it is the last thing printed before the boot process stops. We tried powering it off and on multiple times, but it was the same. However, when we run envycontrol --reset from the systemd-boot rescue shell, everything worked just fine.

What we did:

We thought it happened because of multiple things we tried before to get Nvidia to work, OR it was because when installing the system, we didn’t select the Nvidia (latest cards only) version in GRUB.

So we completely reinstalled EndeavourOS, this time with the Nvidia option. Again, KDE Plasma version.
Then we followed this article. We installed optimus-manager and optimus-manager-qt-kde and enabled optimus-manager with systemctl with --now flag as described in the article.

What happened

We rebooted the laptop and the same thing happened. The boot was stuck and the last printed thing was the bluetooth error (which I believe has nothing to do with this). When we removed the optimus-manager from the rescue console, the laptop booted up normally.

Please help

Can somebody please suggest any solution to this?
Having Nvidia GPU and not using it is obviously bad and my friend is not as big Linux maniac as I am.
If we cannot resolve this, he would switch to Windows, or dual-boot it, but he doesn’t want that.
I’m quite an experienced Linux user, so I don’t need completely newbie help with every command explained. I just never had to do anything with Nvidia and I’m not so experienced to resolve this issue.

Thank you in advance and sorry for my awful english.

ringo · May 15, 2023, 11:17pm

you running Xorg ?

ringo · May 15, 2023, 11:21pm

is rough gues got a feeling nvidia drivers not proper installed ?

pacman -Qs nvidia

and pacman -Qs linux-headers ?

stepanzak · May 16, 2023, 5:08am

Yes, I am.

stepanzak · May 16, 2023, 5:08am

Thank you, will try it asap and let you know if that worked.

stepanzak · May 16, 2023, 5:40am

But before the first case with envycontrol we installed it using nvidia-inat --32 (–32 to be able to run 32bit apps)

stepanzak · May 16, 2023, 9:40am

This is the output of those commands:
[frankieee@frantaspc ~]$ pacman -Qs nvidia
local/bumblebee 3.2.1-21
NVIDIA Optimus support for Linux through VirtualGL
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/libxnvctrl 530.41.03-1
NVIDIA NV-CONTROL X extension
local/nvidia-dkms 530.41.03-1
NVIDIA drivers - module sources
local/nvidia-inst 23-5
Script to setup nvidia drivers (dkms version) in EndeavourOS
local/nvidia-installer-common 23-6
Common scripts for nvidia-installer-dkms and nvidia-inst
local/nvidia-settings 530.41.03-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 530.41.03-1
NVIDIA drivers utilities
[frankieee@frantaspc ~]$ pacman -Qs linux-headers
local/linux-headers 6.3.2.arch1-1
Headers and scripts for building modules for the Linux kernel
[frankieee@frantaspc ~]$

manuel · May 16, 2023, 11:20am

You can remove bumblebee, it is for older systems.

stepanzak · May 16, 2023, 11:50am

It was installed by nvidia-inst -b. I was following this guide, but the same thing happened after installing optimus-manager. I didn’t even have to enable it with systemctl.

manuel · May 16, 2023, 3:42pm

As said, bumblebee is something you don’t need, so no need to use option -b with nvidia-inst.

Please read this (https://wiki.archlinux.org/title/NVIDIA) and also these (https://discovery.endeavouros.com/?s=nvidia+optimus) if you haven’t already.

mrvictory · May 16, 2023, 4:50pm

How is this a problem? Intel driving display and %0 usage on Nvidia if you aren’t playing games (or CUDA etc.) is how these laptops work. Is Nvidia GPU used when it is necessary?

stepanzak · May 16, 2023, 4:53pm

It’s 0% when playing CS:GO if the nvidia-settings GUI is working correctly, so we assumed that only integrated intel is in use.

ricklinux · May 16, 2023, 5:00pm

First of all can we see

inxi -Ga

mrvictory · May 16, 2023, 5:00pm

Add -vulkan to launch parameters of CSGO. This will boost FPS and should make CSGO use Nvidia. Also install prime-run

sudo pacman -S prime-run

and any Steam games that use Intel iGPU, change launch parameters to

prime-run %command%

stepanzak · May 16, 2023, 5:21pm

Sure:

Graphics:
Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: eDP-1 empty: DP-1 bus-ID: 0000:00:02.0 chip-ID: 8086:9a68
class-ID: 0300
Device-2: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: Hewlett-Packard
driver: N/A alternate: nouveau non-free: 530.xx+
status: current (as of 2023-05) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 bus-ID: 0000:01:00.0
chip-ID: 10de:25a2 class-ID: 0300
Device-3: Quanta HP Wide Vision HD Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:4 chip-ID: 0408:5425
class-ID: fe01 serial: 0001
Display: x11 server: X.Org v: 21.1.8 compositor: kwin_x11 driver: X:
loaded: intel unloaded: modesetting alternate: fbdev,vesa dri: i965
gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP1 model: BOE Display 0x0aad built: 2021
res: 1920x1080 hz: 144 dpi: 135 gamma: 1.2 size: 360x200mm (14.17x7.87")
diag: 407mm (16") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel UHD Graphics (TGL GT1)
direct-render: Yes

stepanzak · May 16, 2023, 5:31pm

Thank you, this is a good acceptable solution, especially when needing to save battery.
However, when you don’t need to save battery, isn’t using Nvidia for the whole system and Xorg better?
I don’t have experience with hybrid laptops, but this is what it seems like to me.

mrvictory · May 16, 2023, 6:09pm

Depends on your needs.
Pros:

No need to modify applications to use Nvidia
Gsync on internal display (if supported. This may be possible on iGPU as well, I am not sure)

Cons:

No hardware acceleration on browsers and Electron apps. link
If Nvidia driver breaks, which is rare but possible, you may lose display output entirely making the PC unusable.
Bad battery life but you mentioned you don’t care.

mrvictory · May 16, 2023, 6:12pm

Ok, we have a bigger problem. Send full output of sudo journalctl -b

stepanzak · May 16, 2023, 6:24pm

I’m really sorry, my friend had to go and I’m trying to ping him but no response yet.
I will send the output as soon as I can, but if he won’t respond I have to post it tomorrow from school.
Thank you for helping us.

stepanzak · May 16, 2023, 6:51pm

This is what he sent me:
kvě means may in Czech, sorry for that.

kvě 16 17:31:59 frantaspc kernel: microcode: updated early: 0x40 -> 0x44, date = 2022-12-28
kvě 16 17:31:59 frantaspc kernel: Linux version 6.3.2-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Thu, 11 May 2023 16:40:42 +0000
kvě 16 17:31:59 frantaspc kernel: Command line: initrd=\88b10d000f85419689183c6b91ba7264\6.3.2-arch1-1\initrd nvme_load=YES nowatchdog rw root=UUID=82dbd04e-7d11-4b8b-9e52-ddcdf00f5bb6 resume=UUID=6f93c45e-8f8c-42df-aaa5-1e4b5a79fcde n>
kvě 16 17:31:59 frantaspc kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format.
kvě 16 17:31:59 frantaspc kernel: signal: max sigframe size: 3632
kvě 16 17:31:59 frantaspc kernel: BIOS-provided physical RAM map:
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000039a5afff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000039a5b000-0x000000003cb5afff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cb5b000-0x000000003cc26fff] ACPI data
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cc27000-0x000000003cd45fff] ACPI NVS
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cd46000-0x0000000041efefff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000041eff000-0x0000000041efffff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000041f00000-0x0000000049ffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000004a200000-0x000000004a3fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000004b000000-0x00000000503fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000100000000-0x00000004afbfffff] usable
kvě 16 17:31:59 frantaspc kernel: NX (Execute Disable) protection: active
kvě 16 17:31:59 frantaspc kernel: e820: update [mem 0x35a88018-0x35a97e57] usable ==> usable
kvě 16 17:31:59 frantaspc kernel: e820: update [mem 0x35a88018-0x35a97e57] usable ==> usable
kvě 16 17:31:59 frantaspc kernel: extended physical RAM map:
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000000009f000-0x00000000000fffff] reserved
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000035a88017] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000035a88018-0x0000000035a97e57] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000035a97e58-0x0000000039a5afff] usable
kvě 16 17:31:59 frantaspc kevě 16 17:31:59 frantaspc kernel: microcode: updated early: 0x40 -> 0x44, date = 2022-12-28
kvě 16 17:31:59 frantaspc kernel: Linux version 6.3.2-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Thu, 11 May 2023 16:40:42 +0000
kvě 16 17:31:59 frantaspc kernel: Command line: initrd=\88b10d000f85419689183c6b91ba7264\6.3.2-arch1-1\initrd nvme_load=YES nowatchdog rw root=UUID=82dbd04e-7d11-4b8b-9e52-ddcdf00f5bb6 resume=UUID=6f93c45e-8f8c-42df-aaa5-1e4b5a79fcde n>
kvě 16 17:31:59 frantaspc kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
kvě 16 17:31:59 frantaspc kernel: x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
kvě 16 17:31:59 frantaspc kernel: x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format.
kvě 16 17:31:59 frantaspc kernel: signal: max sigframe size: 3632
kvě 16 17:31:59 frantaspc kernel: BIOS-provided physical RAM map:
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000039a5afff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000039a5b000-0x000000003cb5afff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cb5b000-0x000000003cc26fff] ACPI data
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cc27000-0x000000003cd45fff] ACPI NVS
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000003cd46000-0x0000000041efefff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000041eff000-0x0000000041efffff] usable
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000041f00000-0x0000000049ffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000004a200000-0x000000004a3fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x000000004b000000-0x00000000503fffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
kvě 16 17:31:59 frantaspc kernel: BIOS-e820: [mem 0x0000000100000000-0x00000004afbfffff] usable
kvě 16 17:31:59 frantaspc kernel: NX (Execute Disable) protection: active
kvě 16 17:31:59 frantaspc kernel: e820: update [mem 0x35a88018-0x35a97e57] usable ==> usable
kvě 16 17:31:59 frantaspc kernel: e820: update [mem 0x35a88018-0x35a97e57] usable ==> usable
kvě 16 17:31:59 frantaspc kernel: extended physical RAM map:
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000000009f000-0x00000000000fffff] reserved
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000035a88017] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000035a88018-0x0000000035a97e57] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000035a97e58-0x0000000039a5afff] usable
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x0000000039a5b000-0x000000003cb5afff] reserved
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cb5b000-0x000000003cc26fff] ACPI data
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cc27000-0x000000003cd45fff] ACPI NVS
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cd46000-0x0000000041efefff] reserved
rnel: reserve setup_data: [mem 0x0000000039a5b000-0x000000003cb5afff] reserved
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cb5b000-0x000000003cc26fff] ACPI data
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cc27000-0x000000003cd45fff] ACPI NVS
kvě 16 17:31:59 frantaspc kernel: reserve setup_data: [mem 0x000000003cd46000-0x0000000041efefff] reserved