Laptop failing to boot - flashing backlight

Hello everyone
I have been enjoying EOS for almost a year and so far it has been great.
Recently my installation has failed to get past the startup stage and I have no idea why. I believe it started after running an update and then after the update concluded, shutting down and using my Windows partition.

A few key details:

  • I am on a HP Omen 15 2020 laptop with an Nvidia RTX 2060 and an AMD Ryzen 7 4800H CPU
  • It is a dual boot system with two separate M.2 SSDs, one for Windows 10 and the other for EOS
  • The system is up to date
  • EOS is encrypted with Luks and I use the XFCE Desktop Environment

Currently during startup my system seems to run normally but eventually hits a black screen with a cursor while the backlight flashes until I shut down the laptop. Ctrl + Alt + F2 does not bring up a terminal. The backlight is on a roughly 2 second duty cycle.

I was able to get a terminal by appending “systemd.unit=multi-user.target” to the GRUB startup command. From there I ran an update using YAY and reinstalled LightDM but this did not fix the underlying issue.

Attached below are the logs I was able to export.

Any suggestions would be greatly appreciated
Thanks.

Latest Logs from journalctl -p3:

-- Boot 172c95444a3f48c98437f93339fc1302 --
May 22 00:26:34 anon-laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20221020/dswload2-162)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20221020/psobject-220)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P000 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P001 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P002 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P003 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P004 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P005 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P006 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P007 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P008 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P009 (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00A (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00B (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00C (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00D (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00E (20221020/dspkginit-438)
May 22 00:26:34 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00F (20221020/dspkginit-438)

Logs from inxi -FAZ --no-host

System:
  Kernel: 6.3.2-arch1-1 arch: x86_64 bits: 64 Console: tty 1 Distro: EndeavourOS
Machine:
  Type: Laptop System: HP product: OMEN Laptop 15-en0xxx v: N/A serial: <superuser required>
  Mobo: HP model: 8787 v: 22.58 serial: <superuser required> UEFI: AMI v: F.13 date: 03/04/2021
Battery:
  ID-1: BAT0 charge: 56.2 Wh (100.0%) condition: 56.2/56.2 Wh (100.0%)
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP cache:
    L2: 4 MiB
  Speed (MHz): avg: 1587 min/max: 1400/2900 cores: 1: 1400 2: 1400 3: 2900 4: 1400 5: 1400
    6: 1400 7: 2900 8: 1400 9: 1400 10: 1400 11: 1400 12: 1400 13: 1400 14: 1400 15: 1400 16: 1400
Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] driver: N/A
  Device-2: AMD Renoir driver: amdgpu v: kernel
  Device-3: Luxvisions Innotech HP Wide Vision HD Camera driver: uvcvideo type: USB
  Display: server: X.org v: 1.21.1.8 driver: X: loaded: modesetting,nvidia dri: radeonsi
    gpu: amdgpu tty: 240x67 resolution: 1920x1080
  API: OpenGL Message: GL data unavailable in console. Try -G --display
Audio:
  Device-1: NVIDIA TU106 High Definition Audio driver: snd_hda_intel
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_rn_pci_acp3x
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  API: ALSA v: k6.3.2-arch1-1 status: kernel-api
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  IF: eno1 state: down mac: f8:0d:ac:1a:9c:fd
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
  IF: wlan0 state: up mac: 18:26:49:b3:83:a0
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled rfk-block: hardware: no
    software: no address: see --recommends
Drives:
  Local Storage: total: 1.4 TiB used: 851.98 GiB (59.3%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: MZVLB512HBJQ-000H1 size: 476.94 GiB
  ID-3: /dev/sda vendor: SanDisk model: Cruzer Spark size: 28.65 GiB type: USB
Partition:
  ID-1: / size: 898.62 GiB used: 851.62 GiB (94.8%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot/efi size: 998 MiB used: 476 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 16.49 GiB used: 0 KiB (0.0%) dev: /dev/dm-1
Sensors:
  System Temperatures: cpu: 78.4 C mobo: N/A gpu: amdgpu temp: 59.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 296 Uptime: 4h 54m Memory: available: 14.99 GiB used: 784.2 MiB (5.1%) Init: systemd
  Shell: Bash inxi: 3.3.27

Other person said acpi=off but I believe only for time of debugging.

Looks like Kernel regression, would try LTS OR downgrading intel microcode package

My laptop’s BIOS did not seem to have an option to change anything related to SATA or the drives.

I reverted to the LTS kernel by installing the LTS kernel and headers using YAY, regenerating the GRUB config and then selecting the LTS option in the GRUB boot menu. I still got stuck on the same flashing backlight, but this time there was a message that said the following:
[ OK ] Started Accounts Service

The journalctl log from that startup attempt is attached below.
Thanks.

-- Boot 339b4c2640f3468f9b95a7852c79cc12 --
May 22 03:09:00 anon-laptop kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP4.WLAN], AE_NOT_FOUND (20220331/dswload2-162)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P000 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P001 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P002 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P003 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P004 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P005 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P006 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P007 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P008 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P009 (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00A (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00B (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00C (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00D (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00E (20220331/dspkginit-438)
May 22 03:09:00 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00F (20220331/dspkginit-438)
May 22 03:09:09 anon-laptop kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
May 22 03:09:09 anon-laptop kernel: ucsi_ccg 1-0008: i2c_transfer failed -110
May 22 03:09:09 anon-laptop kernel: ucsi_ccg 1-0008: ucsi_ccg_init failed - -110
May 22 03:09:10 anon-laptop kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
May 22 03:09:10 anon-laptop kernel: amdgpu 0000:07:00.0: amdgpu: Secure display: Generic Failure.
May 22 03:09:10 anon-laptop kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
May 22 03:09:12 anon-laptop kernel: 
May 22 03:09:16 anon-laptop kernel: iwlwifi 0000:03:00.0: Unhandled alg: 0x707
May 22 03:09:17 anon-laptop dnsmasq[1452]: error at line 121 of /etc/dnsmasq.conf
May 22 03:09:17 anon-laptop dnsmasq[1452]: FAILED to start up
May 22 03:09:18 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:09:18 anon-laptop dnsmasq[1459]: error at line 121 of /etc/dnsmasq.conf
May 22 03:09:18 anon-laptop dnsmasq[1459]: FAILED to start up
May 22 03:09:18 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:09:18 anon-laptop dnsmasq[1460]: error at line 121 of /etc/dnsmasq.conf
May 22 03:09:18 anon-laptop dnsmasq[1460]: FAILED to start up
May 22 03:09:18 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:09:18 anon-laptop dnsmasq[1461]: error at line 121 of /etc/dnsmasq.conf
May 22 03:09:18 anon-laptop dnsmasq[1461]: FAILED to start up
May 22 03:09:18 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:09:19 anon-laptop dnsmasq[1463]: error at line 121 of /etc/dnsmasq.conf
May 22 03:09:19 anon-laptop dnsmasq[1463]: FAILED to start up
May 22 03:09:19 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:09:19 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 03:10:17 anon-laptop systemd-cryptsetup[1984]: Device luks-3a93dea5-10f1-426a-8fe3-c07fcde2a9ba is still in use.
May 22 03:10:17 anon-laptop systemd-cryptsetup[1984]: Failed to deactivate: Device or resource busy
May 22 03:10:18 anon-laptop systemd[1]: Failed unmounting /tmp.
May 22 03:10:19 anon-laptop kernel: watchdog: watchdog0: watchdog did not stop!
sudo systemctl status dnsmasq.service 

Try staring the service

sudo systemctl start dnsmasq.service

Edit: I also see that your UEFI Bios is way out of date. I’m sure there is a newer update for it probably dated for 2023. I would check and update it also.

The flashing screen reminds me of one old system that I have which does not like Nouveau’s KMS. Could it be a video driver issue?

2 Likes

I updated the bios to the latest version but it had no effect on the failure to boot.

The status of dnsmasq is as follows. It seems that it was enabled but crashes on startup

Ă— dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Mon 2023-05-22 04:39:05 BST; 1min 30s ago
       Docs: man:dnsmasq(8)
    Process: 1420 ExecStartPre=/usr/bin/dnsmasq --test (code=exited, status=1/FAILURE)
        CPU: 16ms

May 22 04:39:05 anon-laptop systemd[1]: dnsmasq.service: Scheduled restart job, restart counter is at 5.
May 22 04:39:05 anon-laptop systemd[1]: Stopped dnsmasq - A lightweight DHCP and caching DNS server.
May 22 04:39:05 anon-laptop systemd[1]: dnsmasq.service: Start request repeated too quickly.
May 22 04:39:05 anon-laptop systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
May 22 04:39:05 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

I tried starting the service but it kept throwing errors saying that line 121 of the config file was invalid. Everything above line 121 is commented out using hashes so I just pasted line 121 below.
listen-address=127.0.0.1:5300

I disabled the dnsmasq service and then rebooted but it had no effect.

Thanks for the suggestion. I do use optimus-manager with the dedicated Nvidia GPU set as the default one. I will try switch over to the integrated one and see if it has an effect.

Not sure how you are using optimus manager as there are no drivers loaded for the nvidia gpu. Did you install the nvidia drivers?

Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] driver: N/A

Please post

inxi -Ga
1 Like

Did you try

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
sudo systemctl mask systemd-resolved

Edit: reboot

inxi -Ga

Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard driver: N/A
    alternate: nouveau, nvidia_drm, nvidia non-free: 530.xx+ status: current (as of 2023-05)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f15
    class-ID: 0300
  Device-2: AMD Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: eDP-1 empty: none bus-ID: 07:00.0 chip-ID: 1002:1636
    class-ID: 0300 temp: 53.0 C
  Device-3: Luxvisions Innotech HP Wide Vision HD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3 chip-ID: 30c9:000e class-ID: 0e02
  Display: server: X.org v: 1.21.1.8 driver: X: loaded: modesetting,nvidia dri: radeonsi
    gpu: amdgpu tty: 240x67
  Monitor-1: eDP-1 model: LG Display 0x05fe built: 2018 res: 1920x1080 dpi: 142 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL Message: GL data unavailable in console. Try -G --display

Optimus manager was disabled and not running, so I enabled it and rebooted but there was no change to the flashing screen.
Systemd-resolved was already disabled and inactive, but I followed the instructions, masked it and it had no noticeable effect.

Pulled the most recent journalctl and attached it below.
Any insight would be greatly appreciated

-- Boot e6fcd8e49dde4cab8c0123b1ab786617 --
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P000 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P001 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P002 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P003 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P004 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P005 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P006 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P007 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P008 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P009 (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00A (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00B (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00C (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00D (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00E (20220331/dspkginit-438)
May 22 16:26:08 anon-laptop kernel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_PR_.P00F (20220331/dspkginit-438)
May 22 16:26:20 anon-laptop kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
May 22 16:26:20 anon-laptop kernel: ucsi_ccg 4-0008: i2c_transfer failed -110
May 22 16:26:20 anon-laptop kernel: ucsi_ccg 4-0008: ucsi_ccg_init failed - -110
May 22 16:26:21 anon-laptop kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
May 22 16:26:22 anon-laptop kernel: amdgpu 0000:07:00.0: amdgpu: Secure display: Generic Failure.
May 22 16:26:22 anon-laptop kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
May 22 16:26:26 anon-laptop kernel: 
May 22 16:26:30 anon-laptop kernel: iwlwifi 0000:03:00.0: Unhandled alg: 0x707
May 22 16:26:36 anon-laptop dnsmasq[1469]: error at line 121 of /etc/dnsmasq.conf
May 22 16:26:36 anon-laptop dnsmasq[1469]: FAILED to start up
May 22 16:26:36 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:26:37 anon-laptop dnsmasq[1485]: error at line 121 of /etc/dnsmasq.conf
May 22 16:26:37 anon-laptop dnsmasq[1485]: FAILED to start up
May 22 16:26:37 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:26:37 anon-laptop dnsmasq[1486]: error at line 121 of /etc/dnsmasq.conf
May 22 16:26:37 anon-laptop dnsmasq[1486]: FAILED to start up
May 22 16:26:37 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:26:37 anon-laptop dnsmasq[1493]: error at line 121 of /etc/dnsmasq.conf
May 22 16:26:37 anon-laptop dnsmasq[1493]: FAILED to start up
May 22 16:26:37 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:26:37 anon-laptop dnsmasq[1494]: error at line 121 of /etc/dnsmasq.conf
May 22 16:26:37 anon-laptop dnsmasq[1494]: FAILED to start up
May 22 16:26:37 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:26:38 anon-laptop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
May 22 16:27:07 anon-laptop systemd-cryptsetup[1758]: Device luks-3a93dea5-10f1-426a-8fe3-c07fcde2a9ba is still in use.
May 22 16:27:07 anon-laptop systemd-cryptsetup[1758]: Failed to deactivate: Device or resource busy
May 22 16:27:07 anon-laptop systemd[1]: Failed unmounting /tmp.
May 22 16:27:08 anon-laptop kernel: watchdog: watchdog0: watchdog did not stop!

I find it odd that it still throws dnsmasq errors despite disabling the dnsmasq.service and the systemd-resolved

First of all i don’t see any Nvidia drivers loaded? Did you install them?

Here is what i would do first. Uninstall optimus-manager Revert to nouveau open source drivers with

nvidia-inst -n

reboot

Then post

inxi -Ga

I would like to see then if it shows it’s running on nouveau.

1 Like

I removed the optimus-manager package, installed the nouveau drivers and it booted with no issues.
Thanks for the help!

inxi -Ga output for those curious

Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1f15 class-ID: 0300
  Device-2: AMD Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: eDP-1 empty: none bus-ID: 07:00.0 chip-ID: 1002:1636
    class-ID: 0300 temp: 50.0 C
  Device-3: Luxvisions Innotech HP Wide Vision HD Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:3
    chip-ID: 30c9:000e class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
    loaded: amdgpu,nvidia unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0.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: eDP model: LG Display 0x05fe built: 2018
    res: 1920x1080 hz: 144 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.49 6.1.29-1-lts) direct-render: Yes

Okay so now we have Nvidia drivers loaded.

Graphics:
  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Hewlett-Packard
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-05) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8
    link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0

I was expecting this or Nouveau to be loaded but this is good. Now you should be able to install optimus-manager and it should work for switching to Nvidia. I’m not sure what desktop you are running but make sure you install the proper package of optimus-manager for the desktop used.

https://discovery.endeavouros.com/nvidia/optimus-manager-for-nvidia/2021/03/

Edit: If the laptop is booting fine and you don’t care about switching to Nvidia then you wouldn’t need to worry about optimus-manager. The AMD graphics are not bad so you have the choice what you want to do or not.

Edit: It’s currently rendering on AMD.

API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon Graphics (renoir LLVM
    15.0.7 DRM 3.49 6.1.29-1-lts) direct-render: Yes
1 Like

I think I will hold off on installing Optimus Manager for now, as everything seems to be running smoothly and I probably get better battery life. I am currently using a prime-run script to allocate the NVIDIA as required for graphically intensive programs such as games.

For those who are curious I used the guides below to make and test it.
(I am not sure if it is recommended or not but I just put the script directly in the /bin/ folder, as I could not get it recognized in console from the ~/bin/ folder)

Making the script:

Testing the script:

1 Like

I agree running on nvidia will use more battery life. optimus-manger is is good but you’ll need to test to see if it is working for you now that the nvidia drivers are getting loaded. But that’s entirely up to you.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.