Can’t change the resolution, the monitor is unknown
here’s my garuda-inxi output
System:
Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=0b494584-62b9-4aa7-b6a8-fd72f5b25d0f rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: Z590 AORUS ELITE AX
serial: <superuser required> UEFI: American Megatrends LLC. v: F7
date: 11/03/2021
CPU:
Info: model: 11th Gen Intel Core i5-11400F bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x59
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 4200 min/max: 800/4400 scaling: driver: intel_pstate
governor: performance cores: 1: 4200 2: 4200 3: 4200 4: 4200 5: 4200 6: 4200
7: 4200 8: 4200 9: 4200 10: 4200 11: 4200 12: 4200 bogomips: 62208
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070] vendor: ASUSTeK driver: N/A
alternate: nouveau non-free: 545.xx+ status: current (as of 2023-10)
arch: Lovelace code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2786
class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
s-diag: 338mm (13.3")
Monitor-1: Unknown-1 mapped: None-1 res: 1024x768 hz: 60 size: N/A
modes: 1024x768
API: EGL v: 1.5 platforms: device: 0 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: swrast x11: drv: swrast inactive: wayland
API: OpenGL v: 4.5 vendor: mesa v: 23.2.1-arch1.2 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 16.0.6 256 bits)
device-ID: ffffffff:ffffffff memory: 61.2 GiB unified: yes
API: Vulkan v: 1.3.269 layers: 6 device: 0 type: cpu name: llvmpipe (LLVM
16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM 16.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bc
class-ID: 0403
API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:8 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 3.84 TiB used: 24.05 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: N/A
size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: RKT343.4 temp: 28.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: MZFLV128HCGR-000MV
size: 119.24 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: MBR
Partition:
ID-1: / raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 23.99 GiB (8.0%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 60.5 MiB (23.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 23.99 GiB (8.0%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-4: /var/log raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 23.99 GiB (8.0%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-5: /var/tmp raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 23.99 GiB (8.0%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.67 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: 31.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 318 Uptime: 54m wakeups: 0 Memory: total: 64 GiB note: est.
available: 62.67 GiB used: 3.09 GiB (4.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1960 libs: 533 tools: gnome-software,octopi,paru
Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date: 2023-11-14
Last full system update: 2023-11-14 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Failed units: [email protected]
SGS
15 November 2023 04:06
2
Try lts kernel
sudo pacman -S linux-lts linux-lts-headers
Use advanced from grub and try this kernel.
sudo nvidia-settings
2 Likes
filo
15 November 2023 05:38
3
Additionally, this final symbol means a reboot is pending after the last update.
You never can say …
4 Likes
I tried sudo nvidia-settings but it returned nvidia-settings: command not found
I had to go to sleep, restarted the machine and nothing much has changed
question, when you say advanced from grub is that from garuda assistant?
Kayo
15 November 2023 08:44
7
In the advanced menu at boot time (grub), you can select what kernel to use.
hit alt+space
and search for Nvidia
, and click on Nvidia X Server Settings
from the list.
1 Like
I executed the kernel command as well, do I need to restart after also going to garuda boot options and changing it to garuda linux with linux lts?
Kayo
15 November 2023 08:52
9
If you installed the kernel, and selected it from the advanced boot options in grub, you should be now in the kernel selected. This is only active for until next boot as it does not set a new default.
You can check what kernel you are running currently by checking your garuda-inxi
2 Likes
SGS
15 November 2023 08:56
10
In terminal
mhwd-kernel -li
Currently running: 6.6.1-zen1-1-zen (linux-zen)
The following kernels are installed in your system:
local/linux-amd-znver3 6.6.v.1-1
local/linux-zen 6.6.1.zen1-1
2 Likes
nothing came up when I only typed nvidia, I had to type nvidia for x settings and found nothing
Kayo
15 November 2023 09:05
13
Just noticed this is a fresh installed system. Could we get a new garuda-inxi
after you restart? (↻ means you haven’t restarted after an update). I’m a bit curious to see if that falied unit will go away.
Just forgetting to restart after the first update could of been your problem.
2 Likes
SGS:
mhwd-kernel -li
that was after I went to the settings and changed it to Garuda linux with linux linux-lts
[🔴] × mhwd-kernel -li
Currently running: 6.6.1-zen1-1-zen (linux-zen)
The following kernels are installed in your system:
local/linux-lts 6.1.62-1
local/linux-hardened 6.5.10.hardened1-1
local/linux-xanmod 6.5.11-1
local/linux-tt 6.5.9-2
local/linux-mainline 6.6rc6-1
local/linux-cachyos-bore 6.6.1-1
local/linux-zen 6.6.1.zen1-1
System:
Kernel: 6.6.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=0b494584-62b9-4aa7-b6a8-fd72f5b25d0f rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: Z590 AORUS ELITE AX
serial: UEFI: American Megatrends LLC. v: F7
date: 11/03/2021
CPU:
Info: model: 11th Gen Intel Core i5-11400F bits: 64 type: MT MCP
arch: Rocket Lake gen: core 11 level: v4 note: check built: 2021+
process: Intel 14nm family: 6 model-id: 0xA7 (167) stepping: 1
microcode: 0x5D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 480 KiB desc: d-6x48 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 4200 min/max: 800/4400 scaling: driver: intel_pstate
governor: powersave cores: 1: 4200 2: 4200 3: 4200 4: 4200 5: 4200 6: 4200
7: 4200 8: 4200 9: 4200 10: 4200 11: 4200 12: 4200 bogomips: 62208
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Graphics:
Device-1: NVIDIA AD104 [GeForce RTX 4070] vendor: ASUSTeK driver: N/A
alternate: nouveau non-free: 545.xx+ status: current (as of 2023-10)
arch: Lovelace code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:2786
class-ID: 0300
Display: x11 server: [X.Org](http://X.Org) v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: N/A display-ID: :0 screens: 1
Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
s-diag: 338mm (13.3")
Monitor-1: Unknown-1 mapped: None-1 res: 1024x768 hz: 60 size: N/A
modes: 1024x768
API: EGL v: 1.5 platforms: device: 0 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: swrast x11: drv: swrast inactive: wayland
API: OpenGL v: 4.5 vendor: mesa v: 23.2.1-arch1.2 glx-v: 1.4
direct-render: yes renderer: llvmpipe (LLVM 16.0.6 256 bits)
device-ID: ffffffff:ffffffff memory: 61.2 GiB unified: yes
API: Vulkan v: 1.3.269 layers: 6 device: 0 type: cpu name: llvmpipe (LLVM
16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM 16.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Tiger Lake-H HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:43c8 class-ID: 0403
Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bc
class-ID: 0403
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Tiger Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:43f0 class-ID: 0280
IF: wlo1 state: down mac:
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac:
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:8 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 3.84 TiB used: 22.98 GiB (0.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: N/A
size: 3.73 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: fw-rev: RKT343.4 temp: 28.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: MZFLV128HCGR-000MV
size: 119.24 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial:
fw-rev: 1.00 scheme: MBR
Partition:
ID-1: / raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 22.92 GiB (7.7%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 60.5 MiB (23.6%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 22.92 GiB (7.7%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-4: /var/log raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 22.92 GiB (7.7%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
ID-5: /var/tmp raw-size: 298.15 GiB size: 298.15 GiB (100.00%)
used: 22.92 GiB (7.7%) fs: btrfs dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.67 GiB used: 1.8 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 41.0 C mobo: 30.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 317 Uptime: 44m wakeups: 0 Memory: total: 64 GiB note: est.
available: 62.67 GiB used: 3.5 GiB (5.6%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1960 libs: 533 tools: gnome-software,octopi,paru
Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date: 2023-11-14
Last full system update: 2023-11-15 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Failed units:
Kayo
15 November 2023 09:12
16
That’s weird… it should be linux-lts if you selected it at boot. You sure haven’t rebooted again and forgot to select it again? (as I said before, it is only for that boot. It doesn’t set a default)
at least there are no failed units now
2 Likes
I’ll do that in a sec, also nice!
It’s stuck on loading initial ramdisk for a while, should I wait further?
Kayo
15 November 2023 09:26
19
Usually that means there is an error booting (or booting using a specific kernel)
If I had to take a guess it might be because DKMS packages, but you can never be sure. Check this FAQ Computer doesn’t boot, boots to a black screen, or stops at a message
If that doesn’t help, try a kernel you know that works (for instance the Zen one; which it should still default to). If that still doesn’t work, you can select a snapshot from a time the system was working Restoring snapshots to get the system back to working state | Garuda Linux wiki (after you follow that guide completely and do your reboot for it, made sure to update your system again with garuda-update
)
Is the monitor still reporting as unknown after the reboots?
Do you know the specific make of the monitor and how your are connecting to it (like what cable type)?
2 Likes
I’ll take a look at the FAQ, the monitor is a curved Sceptre 75hz, connected through an HDMI cable
1 Like