Yes I did try 2 other kernels but both of 'em don’t boot into graphical, they hang at login to SDDM. I can TTY and I get the same error as above in my other post, which is no screen found. Funny isn’t it… from a working snapshot, I install a kernel through Garuda’s KDE System Settings list, twice, and both of 'em don’t graphically log in.
This is my inxi, however I am now in my main subvolume, so the nvidia info may not be the one of 460.39, the kernel is the same, the SSD is an nvme here but my other drives are Crucial (you can see that in inxi) and versions like Fish, etc. may differ if they had an update since Sunday. If need be I can reboot into my other drive and reissue inxi.
System: Kernel: 5.10.12-116-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
root=UUID=27cfff44-6eda-4ada-8ae8-e7b01a8e8acd rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3
vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 it87.force_id=0x8686 loglevel=3
Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Garuda Linux
Machine: Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF serial:
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x serial: UEFI [Legacy]: American Megatrends v: F11
date: 12/06/2019
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Illuminated Keyboard K800 serial:
charge: 55% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse MX Master serial: charge: 10% (should be ignored)
rechargeable: yes status: Discharging
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) model-id: 71 (113)
stepping: N/A microcode: 8701013 L2 cache: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 115090
Speed: 2192 MHz min/max: 2200/3600 MHz boost: disabled Core speeds (MHz): 1: 2192 2: 2195 3: 2187 4: 2186 5: 2195
6: 2190 7: 2189 8: 2192 9: 2193 10: 2186 11: 2195 12: 2194 13: 2194 14: 2194 15: 2191 16: 2196
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
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: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia v: 460.32.03
alternate: nouveau,nvidia_drm bus ID: 08:00.0 chip ID: 10de:1f82
Display: x11 server: [X.Org](http://X.Org) 1.20.10 compositor: kwin_x11 driver: loaded: nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x392mm (27.6x15.4") s-diag: 804mm (31.7")
Monitor-1: DP-0 res: 3840x2160 hz: 60 dpi: 140 size: 697x392mm (27.4x15.4") diag: 800mm (31.5")
OpenGL: renderer: GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 460.32.03 direct render: Yes
Audio: Device-1: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 10de:10fa
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 0a:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.10.12-116-tkg-bmq
Network: Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: f000 bus ID: 04:00.0
chip ID: 8086:1539
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac:
IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Drives: Local Storage: total: 2.73 TiB used: 770.74 GiB (27.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 serial: rev: 1B2QGXA7 temp: 32.9 C
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s serial: rev: 023
ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s serial: rev: 023
Partition: ID-1: / raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs dev: /dev/nvme0n1p1
maj-min: 259:1
ID-2: /home raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /var/log raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap: Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
ID-9: swap-9 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8
ID-10: swap-10 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9
ID-11: swap-11 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10
ID-12: swap-12 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11
ID-13: swap-13 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram12
ID-14: swap-14 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram13
ID-15: swap-15 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram14
ID-16: swap-16 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram15
Sensors: System Temperatures: cpu: 28.0 C mobo: 23.0 C gpu: nvidia temp: 32 C
Fan Speeds (RPM): cpu: 744 fan-1: 903 fan-3: 813 fan-4: 0 fan-5: 776 gpu: nvidia fan: 28%
Power: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.22
Info: Processes: 352 Uptime: 10m wakeups: 7 Memory: 15.64 GiB used: 4.83 GiB (30.9%) Init: systemd v: 247 Compilers:
gcc: 10.2.0 Packages: pacman: 1240 lib: 290 Shell: fish v: 3.1.2 running in: yakuake inxi: 3.2.02
Sorry guys I have yet to learn to post to PrivateBin, I’d prefer that for sure, I think I need to install something to get access to it. GitHub - PrivateBin/PrivateBin: A minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.
@tnt , ok I can try that initrd update. Let’s say I succeed. In what ways would that be better than my pacman upgrade that worked no issue (nothing on the terminal showing errors) and to which I can reboot with success? I mean, if I can manually update that initrd and login graphically to my snapshot after manually installing nvidia drivers, what would be my gain compared to my other drive which did all that automatically and is booting fine?
Just trying to understand where I am going before I try something. If I do boot into that snapshot, then I’ll face the same massive slow down and the /tmp/tmp.* that grubup is mounting every time. So my point is I wonder if should invest more time into manually installing/updating nvidia/initrd…