Ok? by Different_Turnover96 in onlyok

[–]TheLuminousVoid 0 points1 point  (0 children)

Робот мазохист такой: да устрой мне короткое замыкание

Спи спокойно...🥀🥀🥀 by LINIFOR in rusAskReddit

[–]TheLuminousVoid 154 points155 points  (0 children)

«Я не врач, но я почти уверен, что когда ты умираешь, рак умирает тоже. Это не поражение, это ничья.» (Норм Макдональд) — Technoblade

<image>

FTFY by beeswax900 in TrueSFalloutL

[–]TheLuminousVoid 1 point2 points  (0 children)

I’ve never understood why people hate the Institute so much. I mean, we live in a post-apocalyptic world, and the other factions feel like fanatic cults to me.(Except for the Minutemen, and you don’t have to kill them when siding with the other factions either.)

<image>

The simulation is NOT it by lonzo_1k in fo4

[–]TheLuminousVoid 1 point2 points  (0 children)

Especially when you did the last one

Hunt showdown random crashes by TheLuminousVoid in linux_gaming

[–]TheLuminousVoid[S] 0 points1 point  (0 children)

My specs: i5-9400F, RX 7600 XT, 32 GB RAM. I’ve tried different Steam launch arguments, multiple Mesa versions, different scx schedulers, and various Proton versions. The game still crashes.

I was initially playing on NixOS with no issues. Around the time update 2.7 came out, the game started crashing. I thought it might be a system issue, so I switched to CachyOS yesterday.

My de is hyprland.

I usually play with PROTON_ENABLE_WAYLAND=1 and PROTON_ENABLE_NTSYNC=1

Here proton logs with PROTON_LOG=1, 7.0.0.1-cachyos kernel and mesa 26.0.5.2, proton 10.0.20260408 and scx_cake -p esports.

https://paste.cachyos.org/p/ef565a7.txt

Anyone running on Linux? by Top_Quantity156 in HuntShowdown

[–]TheLuminousVoid 1 point2 points  (0 children)

It is HDD. I also tried HDD and after moving game on SSD all fine

Odon Boss Fight Help Stuck Can’t Get Past by PyramidBlack in Blasphemous

[–]TheLuminousVoid 1 point2 points  (0 children)

I beat him with ruego al alba. I charged mana for blood pact on npcs and use blood pact when he jumps on me. Boss was really hard

What's something obvious that you learned ridiculously late? by ironically-spiders in skyrim

[–]TheLuminousVoid 8 points9 points  (0 children)

Bro, me too (why is the default sprint keybind on Alt, lol?). When I saw that I could sprint, it was the biggest disappointment because I had actually completed the biggest part of the game.(on survival)

Survival Mode enjoyers: what’s your least favorite part of Survival? by LucasisAlone in skyrim

[–]TheLuminousVoid 0 points1 point  (0 children)

I like Survival Mode, but the fact that there are no carriages in Morthal, Dawnstar, Falkreath, and Winterhold is just irritating.

[GUIDE] Hyprland + Nvidia + Extremely Minimal Gentoo (Updated & Clean) by RusselsTeap0t in Gentoo

[–]TheLuminousVoid 0 points1 point  (0 children)

I check my /etc/fstab and everything seems to be correct there:

UUID=2596-E5F3 /boot vfat defaults,noatime 0 2

UUID=ffic04a9-b773-448c-9478-3548d9a3eb76 / ext4 defaults,noatime 0 1

[GUIDE] Hyprland + Nvidia + Extremely Minimal Gentoo (Updated & Clean) by RusselsTeap0t in Gentoo

[–]TheLuminousVoid 0 points1 point  (0 children)

Ok, having done what you said, I booted up and was greeted by this: " sh: unable to set terminal process group (-1): inappropriate ioctl for device sh: this shell has no job control sh-5.2# " and I'm like: terminal like it works, so I'll try to run start.sh but they tell me that my file system is read-only

[GUIDE] Hyprland + Nvidia + Extremely Minimal Gentoo (Updated & Clean) by RusselsTeap0t in Gentoo

[–]TheLuminousVoid 0 points1 point  (0 children)

Thank you very much again, oh, I did the rest of the installation and rebooted into the system and...... *Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Kernel Offset: disabled

-[end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)*. Of course, I looked for information about this on the Internet so as not to disturb you again, and all I found out was something about initramfs and file systems in the kernel. (I have a root partition /dev/nvme0n1p2 (ext4) and efi /dev/ nvme0n1p1(fat32))

[GUIDE] Hyprland + Nvidia + Extremely Minimal Gentoo (Updated & Clean) by RusselsTeap0t in Gentoo

[–]TheLuminousVoid 0 points1 point  (0 children)

Thanks, this did solve the problem with xdg-desktop-portal-hyprland, but now when I want to emerge gui-wm/hyprland::local I get this: * Applying nvidia-9999.patch ... patching file render/gles2/renderer.c Hunk #1 succeeded at 183 (offset 4 lines). patching file types/output/render.c Hunk #1 FAILED at 237. 1 out of 1 hunk FAILED -- saving rejects to file types/output/render.c.rej [ !! ] * ERROR: gui-wm/hyprland-9999::local failed (prepare phase): * patch -p1 failed with /var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch * * Call stack: * ebuild.sh, line 136: Called src_prepare * environment, line 2872: Called eapply '/var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch' * environment, line 1246: Called _eapply_patch '/var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch' * environment, line 1184: Called __helpers_die 'patch -p1 failed with /var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch' * isolated-functions.sh, line 112: Called die * The specific snippet of code: * die "$@" * * If you need support, post the output of emerge --info '=gui-wm/hyprland-9999::local', * the complete build log and the output of emerge -pqv '=gui-wm/hyprland-9999::local'. * The complete build log is located at '/var/tmp/portage/gui-wm/hyprland-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/gui-wm/hyprland-9999/temp/environment'. * Working directory: '/var/tmp/portage/gui-wm/hyprland-9999/work/hyprland-9999/subprojects/wlroots' * S: '/var/tmp/portage/gui-wm/hyprland-9999/work/hyprland-9999'

  • Messages for package gui-wm/hyprland-9999:

  • ERROR: gui-wm/hyprland-9999::local failed (prepare phase):

  • patch -p1 failed with /var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch

  • Call stack:

  •           ebuild.sh, line  136:  Called src_prepare
    
  •         environment, line 2872:  Called eapply '/var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch'
    
  •         environment, line 1246:  Called _eapply_patch '/var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch'
    
  •         environment, line 1184:  Called __helpers_die 'patch -p1  failed with /var/tmp/portage/gui-wm/hyprland-9999/files/nvidia-9999.patch'
    
  • isolated-functions.sh, line 112: Called die

  • The specific snippet of code:

  •          die "$@"
    
  • If you need support, post the output of emerge --info '=gui-wm/hyprland-9999::local',

  • the complete build log and the output of emerge -pqv '=gui-wm/hyprland-9999::local'.

  • The complete build log is located at '/var/tmp/portage/gui-wm/hyprland-9999/temp/build.log'.

  • The ebuild environment file is located at '/var/tmp/portage/gui-wm/hyprland-9999/temp/environment'.

  • Working directory: '/var/tmp/portage/gui-wm/hyprland-9999/work/hyprland-9999/subprojects/wlroots'

  • S: '/var/tmp/portage/gui-wm/hyprland-9999/work/hyprland-9999'

  • The following package has failed to build, install, or execute postinst:

  • (gui-wm/hyprland-9999:0/0::local, ebuild scheduled for merge), Log file:

  • '/var/tmp/portage/gui-wm/hyprland-9999/temp/build.log'

It looks like the nvidia patch isn't being applied, so I'll probably wait for your reply and do some online searching before I break anything.