Resolution stuck at 1024x768 +Super lags [Garuda super noob]

Issues & Assistance
1

I just installed garuda dragonized gaming edition I don’t really understand at linux or anything just done with windows I need help with resolution that’s stuck and also ITS SOOO laggy I tried to look at wikis of many but dont find anything useful plus its so laggy and looks like crap that I cant even look around

Tried to update nvidia drive but it just opens it in console type of thing and i cant run it (I know garuda or linux is not for me in terms of skill but I want to use a different OS other then windows since windows 7 is not suppoerted) Please and thank you for the help

2

The resolution is also locked i catn click on anything

3

Please open a terminal, enter garuda-inxi and post the output here, formatted like this:
```
Text
```
That will look like this

Text
2 Likes
4 
garuda-inxi
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=358dd096-df39-4fa2-8767-6d6baa305c37 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: B360M-DS3H v: N/A
serial: <superuser required>
Mobo: Gigabyte model: B360M DS3H v: x.x serial: <superuser required>
UEFI: American Megatrends v: F4 date: 04/03/2018
Battery:
ID-1: hidpp_battery_0 charge: 70% condition: N/A volts: 3.9 min: N/A
model: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A
serial: <filter> status: discharging
CPU:
Info: model: Intel Core i5-8400 bits: 64 type: 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: 0xF4
Topology: cpus: 1x cores: 6 smt: <unsupported> 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: 800 min/max: 800/4000 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
bogomips: 33599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: ASUSTeK
driver: nvidia v: 545.29.02 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 link-max: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1e07 class-ID: 0300
Device-2: Microdia Webcam Vitade AF driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4
chip-ID: 0c45:6366 class-ID: 0102 serial: <filter>
Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
Monitor-1: Unknown-1 res: 1024x768 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia wayland:
drv: swrast x11: drv: swrast inactive: device-1
API: OpenGL v: 4.6.0 compat-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: 15.19 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.3.269 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2080 Ti driver: nvidia v: 545.29.02 device-ID: 10de:1e07
surfaces: xcb,xlib
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte 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
Device-2: NVIDIA TU102 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 1
link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
Device-3: Kingston HyperX Cloud Revolver S
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-3:3 chip-ID: 0951:16ad class-ID: 0300
serial: <filter>
Device-4: Microdia Webcam Vitade AF driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4
chip-ID: 0c45:6366 class-ID: 0102 serial: <filter>
Device-5: Kingston HyperX QuadCast
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-6:5 chip-ID: 0951:16df class-ID: 0300
serial: <filter>
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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 577.55 GiB used: 16.18 GiB (2.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 3B4QFXO7 temp: 31.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 71E0 scheme: GPT
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 16.18 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 16.18 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 16.18 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 16.18 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.55 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 6 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 41.0 C pch: 47.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 214 Uptime: 38m wakeups: 0 Memory: total: 16 GiB
available: 15.56 GiB used: 2.11 GiB (13.6%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1776 libs: 518 tools: octopi,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.18-1):
System install date:     2023-11-10
Last full system update: 2023-11-10
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Here are the results Sir.

1 Like
5

You booted onto a Wayland session. Try x11 (you can select it in the login screen), or with Wayland use the kernel boot parameter suggested here (maybe use the Garuda Boot Assistant, or micro as our default terminal editor instead of nano):

You don’t have that driver problem. This is just to explain what parameter to setup, how and why.

3 Likes
6

x11 worked thank you and also how do I update my driver in x11? it just shows me a code when i click on the downloaded file. and are all files gonna be like this apps and stuff?

7

You don’t upgrade the drivers manually.
They are packages that get updated along with the rest of the system with

garuda-update
3 Likes
8

So as long as I update every week or so my drivers are up to date?

9

Exactly

10

One last question before I mark solution I have 2 drives one is my main NVME which works and the other one doesnt appear about 100 GB’s regular SSD how do i make it appear?

11

Sorry, that’s a completely different issue which should be discussed in a different topic (for forum usability).
Check here if it helps.

PS: welcome to the forum!

2 Likes
12

Every day, if you want. Garuda is a rolling release and as such, is constantly updating packages, including kernels & drivers.

4 Likes
13

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