Wow, how come? It couldn’t be because of hardware limitation, right?
Check out [email protected]. :3
Wow, how come? It couldn’t be because of hardware limitation, right?
Time.
This post reminded me why I had this community blocked for several months until recently.
Not really beginner friendly because it doesn’t teach you much but the site has a nice list of resources that goes even boyond piracy: https://fmhy.net/beginners-guide
They’re active on discord so if you want you can contact them there.
They abandoned lemmy and it was partly because of how their .ml domain went down. lol
That’s a meme community.
ELI5? What does that mean and how did you do it?
Yeah, I will have to look up a visual guide for that. I can’t make this shit work. Thank you for sharing.
Welp, in that case a crash in a session without any updates shouldn’t happen. I will be looking into logs later. But first I need to get some good sleep and find out where the relevant logs are.
This is what I got from: “inxi -Fza”
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 Rev. A] vendor: Gigabyte
driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-04; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 0b:00.0
chip-ID: *REDACTED REDACTED REDACTED*
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: N/A unloaded: modesetting
failed: nvidia alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 2560x2160 s-dpi: 80 s-size: 813x686mm (32.01x27.01")
s-diag: 1064mm (41.88")
Monitor-1: DP-3 pos: top res: 2560x1080 hz: 60 dpi: 81
size: 798x334mm (31.42x13.15") diag: 865mm (34.06") modes: N/A
Monitor-2: HDMI-0 pos: primary,bottom res: 2560x1080 hz: 60 dpi: 81
size: 798x334mm (31.42x13.15") diag: 865mm (34.06") 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 x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
memory: 5.86 GiB
API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2060 driver: nvidia v: 550.78 device-ID: *REDACTED REDACTED REDACTED*
surfaces: xcb,xlib
RTX 2060, will check drivers after getting home.
The funny thing is I’m already on X11 because when it launched on wayland I couldn’t do anything because of messed up resolution. It was very low and most of the interface was outside the screen and while trying to troubleshoot what’s going on I found this switch on login page and was using X11 ever since. I have 4 monitors connected to my pc and my main one is a FullHDUW monitor and second one like that on top of it. For some reason the second monitor is always visible to the system even though it’s turned off but I didn’t knew at the time so I haven’t tried disconnecting it to see if it was the fault.
Will check them once I’m home. Glad to hear that it’s uncommon.
[email protected] or [email protected] material.
I have seen people explain it but I still can’t visualise this. Can you explain in more detail? For science. (But unironically)
I got told that energized is in easyprivacy list.
I should have been corrected tbh.
Thank you for info. Since making the post I got distracted with other stuff and didn’t get into troubleshooting too much. Last crash was today so any help is still appreciated. <3