RTX 3050 ti mobile not being detected

Hi, I am new to linux, but wanted a rolling release, terminal centric distro. Everything was working fine, until yesterday when i ran sudo pacman -Syu and installed the updates. My gpu is no longer be detected, and I have tried multiple things, from similar issues already posted. They have not worked for my system, and have no clue what to do to fix it. Thank you in advance, for spending your time helping me.

Welcome to the forum :enos_flag: :enos:

To be able to help you better please look at this wiki

Thank you, and sorry if the information is not formatted correctly.

Here is the hardware information: from inxi -Fxx0z | eos-sendlog

Hardware Info
System:
  Kernel: 6.17.3-2-cachyos arch: x86_64 bits: 64 compiler: clang v: 20.1.8
  Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX506HE_FX506HE
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX506HE v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FX506HE.311 date: 08/12/2022
Battery:
  ID-1: BAT1 charge: 45.6 Wh (50.3%) condition: 90.7/90 Wh (100.8%)
    volts: 14.67 min: 15.4 model: ASUS A32-K55 serial: N/A charging:
    status: discharging cycles: N/A
CPU:
  Info: 6-core model: 11th Gen Intel Core i5-11400H bits: 64 type: MCP
    arch: Tiger Lake rev: 1 cache: L1: 480 KiB L2: 7.5 MiB L3: 12 MiB
  Speed (MHz): avg: 1800 min/max: 800/4500 cores: 1: 1800 2: 1800 3: 1800
    4: 1800 5: 1800 6: 1800 bogomips: 32256
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Xe ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
    bus-ID: 0000:00:02.0 chip-ID: 8086:9a68
  Device-2: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-7:4 chip-ID: 322e:202c
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x1521 res: 1920x1080 hz: 144
    dpi: 142 diag: 394mm (15.5")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.4-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (TGL GT1)
    device-ID: 8086:9a68 display-ID: :1.0
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 0000:00:1f.3 chip-ID: 8086:43c8
  API: ALSA v: k6.17.3-2-cachyos status: kernel-api
  Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel bus-ID: 0000:2d:00.0
    chip-ID: 14c3:7961
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:2e:00.0
    chip-ID: 10ec:8168
  IF: enp46s0 state: down mac: <filter>
  Device-3: ASIX AX88179 Gigabit Ethernet driver: cdc_ncm type: USB rev: 3.2
    speed: 5 Gb/s lanes: 1 bus-ID: 2-1:2 chip-ID: 0b95:1790
  IF: enp0s13f0u1c2 state: up speed: 1000 Mbps duplex: unknown mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 3-14:5 chip-ID: 13d3:3563
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b
Drives:
  Local Storage: total: 942.7 GiB used: 98.08 GiB (10.4%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SFYRS500G size: 465.76 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
  ID-2: /dev/nvme1n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 52.9 C
Partition:
  ID-1: / size: 463.76 GiB used: 97.49 GiB (21.0%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /home size: 463.76 GiB used: 97.49 GiB (21.0%) fs: btrfs
    dev: /dev/nvme0n1p2
  ID-3: /var/log size: 463.76 GiB used: 97.49 GiB (21.0%) fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 2300
Info:
  Memory: total: 64 GiB note: est. available: 62.54 GiB used: 6.17 GiB (9.9%)
  Processes: 266 Power: uptime: 30m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: pm: pacman pkgs: 1370 Compilers: clang: 20.1.8 gcc: 15.2.1
    alt: 14 Shell: Zsh v: 5.9 running-in: wezterm-gui inxi: 3.3.39

Here is the boot log: from journalctl -k -b -0 | eos-sendlog

https://0x0.st/K1Qy.txt

The boot log is too long to include as text.

Judging by the inxi output (and the nvidia GPU not found message in the log) there seems to be no such chip on your machine, that could mean either inxi isn’t perfect or there is a serious (hardware) problem with the chip. But that is just the way I see it.

Is my GPU dead then, because my laptop does have the RTX 3050ti, and it was being detected fine. It only happen this mourning when I tried booting a game, and realized that my GPU was no longer running.

I booted into windows, and it detected my GPU. That means it should not be a hardware problem right?

I reinstalled endeavor os and it detects my GPU. Thank you for your help.

It might have been a compatibility issue between the kernel and the nvidia driver.

I’d suggest using package nvidia-open-dkms as the driver if you aren’t already using it. That requires the kernel headers installed too.

Such a shame you did a reinstall.

I did have nvidia-open-dkms as my driver, I have no clue what was causing the issue with the driver, as I did some steps to see if there was an issue with the kernel and the drivers.

Yeah, but while I was reinstalling, I change the bootloader from systemd to grub, which I was planning on doing for booting with snapshots. So in the end, reinstalling help me switch much easier.