Boot freeze updating from kernel 5.15 to 6.1

Support Kernel
1

Hi folks, I wanted to upgrade my kernel to the 6.X series but my laptop won’t boot anymore (it boots if I choose to boot on the 5.15 kernel)

I have this in the logs :

journalctl -b-1 -p4 --no-pager
août 10 18:58:02 kwikemart kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
août 10 18:58:02 kwikemart kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
août 10 18:58:02 kwikemart kernel:   #7  #8  #9 #10 #11
août 10 18:58:02 kwikemart kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
août 10 18:58:02 kwikemart kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
août 10 18:58:02 kwikemart kernel: hpet_acpi_add: no address or irqs in _CRS
août 10 18:58:02 kwikemart kernel: i8042: Warning: Keylock active
août 10 18:58:02 kwikemart kernel: usb: port power management may be unreliable
août 10 18:58:02 kwikemart kernel: vboxdrv: loading out-of-tree module taints kernel.
août 10 18:58:02 kwikemart kernel: VBoxNetAdp: Successfully started.
août 10 18:58:02 kwikemart kernel: VBoxNetFlt: Successfully started.
août 10 18:58:02 kwikemart systemd-journald[311]: File /var/log/journal/97165eae32224043ba8b42198f73ab57/system.journal corrupted or uncleanly shut down, renaming and replacing.
août 10 18:58:03 kwikemart kernel: wmi_bus wmi_bus-PNP0C14:05: WQBC data block query control method not found
août 10 18:58:03 kwikemart kernel: i801_smbus 0000:00:1f.4: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
août 10 18:58:03 kwikemart kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
août 10 18:58:03 kwikemart kernel: spi-nor: probe of spi0.0 failed with error -524
août 10 18:58:03 kwikemart (udev-worker)[389]: cfg80211: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.
août 10 19:52:50 kwikemart kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart kernel: ACPI Warning: Time parameter 250 us > 100 us violating ACPI spec, please fix the firmware. (20220331/exsystem-141)
août 10 19:52:50 kwikemart tlp[603]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
août 10 19:52:50 kwikemart tlp[603]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
août 10 19:52:50 kwikemart tlp[603]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
août 10 19:52:50 kwikemart tlp[603]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.

inxi :

inxi --full --admin --filter --width
System:
Kernel: 5.15.122-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=3a73c777-2409-40d3-91ca-9d74d96413c2 rw quiet
resume=UUID=9b5e4530-6b1c-46c6-a66c-984c6986ebe0
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 info: polybar wm: kwin_x11
vt: 2 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: Dell product: XPS 15 9570 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 0D0T05 v: A00 serial: <superuser required> UEFI: Dell
v: 1.14.0 date: 11/08/2019
Battery:
ID-1: BAT0 charge: 51.1 Wh (99.0%) condition: 51.6/97.0 Wh (53.2%)
volts: 12.7 min: 11.4 model: LGC-LGC8.33 DELL 5XJ288A type: Li-ion
serial: <filter> status: charging
CPU:
Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF2
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 1487 high: 3352 min/max: 800/4100 scaling:
driver: intel_pstate governor: powersave cores: 1: 1659 2: 3352 3: 900 4: 900
5: 3209 6: 900 7: 900 8: 900 9: 900 10: 900 11: 2435 12: 900
bogomips: 52815
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: retbleed mitigation: IBRS
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional,
RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell driver: i915
v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
active: eDP-1 empty: DP-1,DP-2,DP-3 bus-ID: 00:02.0 chip-ID: 8086:3e9b
class-ID: 0300
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: Dell
driver: N/A alternate: nouveau, nvidia_drm, nvidia non-free: 535.xx+
status: current (as of 2023-07) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-21 pcie: speed: Unknown lanes: 63 link-max: gen: 6
speed: 64 GT/s bus-ID: 01:00.0 chip-ID: 10de:1c8c class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:5 chip-ID: 0c45:671d
class-ID: 0e02
Display: x11 server: X.Org v: 21.1.8 compositor: kwin_x11 driver: X:
loaded: modesetting alternate: fbdev,vesa dri: iris 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 model: Sharp 0x149a built: 2018 res: 1920x1080 hz: 60
dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 23.0.4 renderer: Mesa Intel UHD Graphics 630 (CFL
GT2) direct-render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
API: ALSA v: k5.15.122-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 0.3.75 status: off with: pipewire-media-session
status: active tools: pw-cli
Server-3: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 3b:00.0
chip-ID: 168c:003e class-ID: 0280 temp: 53.0 C
IF: wlp59s0 state: up mac: <filter>
IF-ID-1: br-0ed07940f845 state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3
chip-ID: 0cf3:e300 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 476.94 GiB used: 196.56 GiB (41.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: PC401 NVMe 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 80006E00 temp: 33.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 100.14 GiB size: 98.01 GiB (97.87%) used: 41.31 GiB (42.2%)
fs: ext4 dev: /dev/nvme0n1p8 maj-min: 259:8
ID-2: /boot/efi raw-size: 650 MiB size: 646 MiB (99.38%)
used: 83.5 MiB (12.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 121.19 GiB size: 118.72 GiB (97.97%)
used: 104.78 GiB (88.3%) fs: ext4 dev: /dev/nvme0n1p10 maj-min: 259:10
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 18.04 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p9 maj-min: 259:9
Sensors:
System Temperatures: cpu: 47.0 C pch: 52.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2469 fan-2: 2480
Info:
Processes: 323 Uptime: 9m wakeups: 1293 Memory: total: 16 GiB note: est.
available: 15.27 GiB used: 3.63 GiB (23.8%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
Packages: 2041 pm: pacman pkgs: 2016 libs: 485 tools: octopi,pamac,trizen,yay
pm: flatpak pkgs: 25 Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.28

edit: I updated my BIOS just to be sure, and I still have the exact same logs.

2

Do your BIOS updates…

Oh. Nevermind. :sweat_smile:

3

I also tried to add ibt=off to my boot parameters, but still the same.

4

Also tried kernel 6.4, with and without ibt=off
Still cannot boot.

I’m continuing my investigations.

5

I updated to latest stable update (2023-09-18) just in case, but still cannot boot with kernel 6.1.

I don’t have any more clues.

6

Hi folks, just upgraded to the latest available stable release and still cannot boot with kernel 6.1.
Anyone got a clue ?

7

Tried 6.6 ?

8

Thanks for coming back ! :slight_smile:
I just tried 6.6 with no luck unfortunately (tried with and without ibt=off param).

I compared a successful boot log and a failed one.
The failed one stops during NetworkManager initialization and just before the video initialisation sequence. This sequence is what happens just after the freeze on a successful boot :

déc. 27 16:02:00 kwikemart kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
déc. 27 16:02:00 kwikemart kernel: ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
déc. 27 16:02:00 kwikemart kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input23
déc. 27 16:02:00 kwikemart kernel: ACPI: video: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
déc. 27 16:02:00 kwikemart kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0b/LNXVIDEO:01/input/input24
déc. 27 16:02:00 kwikemart kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
déc. 27 16:02:00 kwikemart kernel: fbcon: i915drmfb (fb0) is primary device

Could this be a graphic issue ? I can see bumblebeed starting without errors in the logs.
I’m using this config :

mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
video-linux            2018.05.04                true            PCI
video-modesetting            2020.01.13                true            PCI
video-hybrid-intel-nvidia-prime            2023.03.23               false            PCI


Warning: No installed USB configs!
9

You should not be using bumblebee along with prime.

(prime is the newer, preferred, method for gfx switching and replaces bumblebee)

Do you have bumblebee configs?

cat /etc/X11/{mhwd,xorg.conf}.d/*

Or packages?

pacman -Qs bumble

We may want to check all nvidia related packages

pacman -Qs nvidia
10

Ok thanks. Graphics are a mystery to me.

Here we go :

cat /etc/X11/{mhwd,xorg.conf}.d/*
##
## Generated by mhwd - Manjaro Hardware Detection
##


Section "Device"
Identifier  "Device0"
Driver      "intel"
BusID       "PCI:0:2:0"
Option      "AccelMethod" "sna"
Option      "DRI"    "true"
EndSection


Section "DRI"
Group  "video"
Mode   0666
EndSection


Section "Extensions"
Option "Composite" "Enable"
Option "RENDER"    "Enable"
EndSection


Section "InputClass"
Identifier          "Keyboard Defaults"
MatchIsKeyboard        "yes"
Option              "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

##
## Generated by mhwd - Manjaro Hardware Detection
##


# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "fr"
Option "XkbModel" "pc105"
EndSection
##
## Generated by mhwd - Manjaro Hardware Detection
##

pacman -Qs bumble : 
local/bumblebee 3.2.1-23
NVIDIA Optimus support for Linux through Primus/VirtualGL
local/lib32-primus 20151110-5
Faster OpenGL offloading for Bumblebee (32-bit)
local/primus 20151110-9
Faster OpenGL offloading for Bumblebee

pacman -Qs nvidia : 
local/bumblebee 3.2.1-23
NVIDIA Optimus support for Linux through Primus/VirtualGL
local/egl-wayland 2:1.1.13-1
EGLStream-based Wayland external platform
local/lib32-libvdpau 1.5-2
Nvidia VDPAU library
local/lib32-nvidia-utils 545.29.06-1
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-2
Nvidia VDPAU library
local/libxnvctrl 545.29.06-1
NVIDIA NV-CONTROL X extension
local/linux510-nvidia 545.29.06-5 (linux510-extramodules)
NVIDIA drivers for linux
local/linux515-nvidia 545.29.06-6 (linux515-extramodules)
NVIDIA drivers for linux
local/linux54-nvidia 545.29.06-5 (linux54-extramodules)
NVIDIA drivers for linux
local/linux61-nvidia 545.29.06-9 (linux61-extramodules)
NVIDIA drivers for linux
local/linux66-nvidia 545.29.06-27 (linux66-extramodules)
NVIDIA drivers for linux
local/mhwd-nvidia 545.29.06-1
MHWD module-ids for nvidia 545.29.06
local/mhwd-nvidia-340xx 340.108-1
MHWD module-ids for nvidia 340.108
local/mhwd-nvidia-390xx 390.157-9
MHWD module-ids for nvidia 390.157
local/mhwd-nvidia-470xx 470.223.02-1
MHWD module-ids for nvidia 470.223.02
local/nvidia-prime 1.0-4
NVIDIA Prime Render Offload configuration and utilities
local/nvidia-utils 545.29.06-1
NVIDIA drivers utilities
local/xf86-video-nouveau 1.0.17-2 (xorg-drivers)
Open Source 3D acceleration driver for nVidia cards
11

Alright.
Lets remove the bumblebee stuff and reinstall the prime profile.

sudo pacman -Rns bumblebee lib32-primus primus
sudo mhwd -f -i pci video-hybrid-intel-nvidia-prime

PS
Do you have all kernels 5.4,5.10,5.15,6.1,6.6 ?
It may be a good time to remove some of the oldest ones.

sudo mhwd-kernel -r linux54
sudo mhwd-kernel -r linux510
12

Ok I applied the first 2 commands and rebooted fine with kernel 66 thank you !
After that i removed the 2 older kernels and rebooted but it froze.
I rebooted again and it works now, so I guess it is solved.
Thank you !

13

I am glad its worked out.

Maybe one last check, to make sure prime is working as intended;

glxinfo | grep 'renderer string'
prime-run glxinfo | grep 'renderer string'
14

seems fine :

glxinfo | grep 'renderer string'
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)

prime-run glxinfo | grep 'renderer string'
OpenGL renderer string: NVIDIA GeForce GTX 1050 Ti with Max-Q Design/PCIe/SSE2

So if I understand the wiki correctly, I should add prime-run in front of the command that should be run with the nvidia card ?
And which apps are best used with the nvidia card usually ? Games like steam ? Internet browser ? Graphical design apps ?

15

Usually just 3D stuff - if you do creation with tools like Blender … or gaming.
In the case of steam dont run it with prime-run, instead edit a games launch options like so;
(assuming no other options)

prime-run %command%

Theres probably not many other examples.
But, in the case there is some program you wish to always launch using prime, I would suggest creating a script or desktop file for that purpose. A desktop file can be copied from /usr/share/applications to ~/.local/share/applications and edited to contain the prime-run prefix on any Exec lines.

16

Ok perfect, thank you for your time :+1:

17

Cheers. Glad you arent stuck with a blackscreen.
And prime is much more performant than bumblebee so its winning all around.
Happy linuxing. :penguin:

1 Like
18

Btw. is there a reason why you have 2 GPU’s active?

I normally would deactivate the iGPU in your Bios and only working with the nvidia GPU, so everything should work better (out of the box) and you may dont need a hybrid driver then?

Im not a expert in such things, possible im total wrong here… i have never installed prime, bumblebee or a hybrid driver.

19

Most people choose to use the hybrid setup using the more widely compatible and less energy-hungry iGPU (intel), only calling the heavier dGPU (nvidia) when needed.

Also, only a minority of BIOS allow disabling one card or another … and is only desirable by some.

(and if you didnt intend to use it in such a way … you would normally not opt to buy such a system)

20

I’m really not an expert, but the iGPU hits less the battery as cscs said.

I prefer only use the nvidia card for intense computations.

But again, it may be my ignorance speaking.