Nico_198X

joined 4 days ago
[–] Nico_198X@europe.pub 1 points 6 hours ago* (last edited 6 hours ago)

yeah, the menu will never change. that kind of stuff in-game would need to be done by the game devs.

you'd need other tools, like Optiscaler, to tell you that FSR4 is running.

alternatively, you can check the folder where the executable is. you should see this dll there: amdxcffx64.dll

otherwise, if it's an FSR3 game, if you don't want to check you can just assume it's working.

[–] Nico_198X@europe.pub 3 points 17 hours ago

omg i never even considered that! i would LOVE that!

[–] Nico_198X@europe.pub 1 points 17 hours ago* (last edited 17 hours ago) (2 children)

lol it's really not bad. its bark is worse than its bite. XD

ok, CyP2077. looks like it has FSR3 already, that's good. so add this launch parameter in steam:

PROTON_FSR4_UPGRADE=1 %COMMAND%

and set it to FSR3 in-game.

that should auto download the FSR4 dll to the game folder and you'll be good to go. note that the settings in game will still say FSR3, but it will be FSR4, since FSR4 only needs a dll drop-in to update from FSR3.

that will not work with FSR2 games, however.

[–] Nico_198X@europe.pub 2 points 22 hours ago (1 children)

that's fine for now. Mullvad is very affordable though.

[–] Nico_198X@europe.pub 7 points 23 hours ago

it's not easy. but unfortunately both states are captured. no one else is coming to save them.

so either the populace rises up as one, or they continue to be abused.

i don't think either population has their heart in it anymore.

[–] Nico_198X@europe.pub 1 points 1 day ago

best? i dunno about that. it was an option, tho.

i prefer Photon, or just the default.

[–] Nico_198X@europe.pub 2 points 1 day ago

this. and incredibly sane defaults. for me, basically the perfect "traditional" distro and it ended my distrohopping.

[–] Nico_198X@europe.pub 8 points 1 day ago (2 children)

we need WAAAAY more Una.

[–] Nico_198X@europe.pub 3 points 1 day ago (4 children)

nice! i just updated to the 9000 series myself! specifically for this reason.

it just has made such great leaps in the realms of FSR and encoding.

i can attest, FSR4 looks incredible. i'm using it on Lies of P, which you just need the parameter for. any game with FSR3 support you only need the parameter.

i'm also using it on Returnal. Returnal only has FSR2, so for games like that, you need some assistance from OptiScaler.

you can scope out my video here as an example if you want to see!

https://vods.198x.eu/w/u72HQH8fVybQ4xsa9t9yyq

[–] Nico_198X@europe.pub 2 points 1 day ago

great thoughts, thank you for sharing! i'm still quite new to containerization.

[–] Nico_198X@europe.pub 7 points 1 day ago (6 children)

optional launch parameters for your game in question.

 

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

i think i'm giving up on this for now.

thanks all!


hey all!

for the life of me, i cannot get VAAPI hardware accelerated encoding to work. i always get this error:

Error: ffmpeg exited with code 234: Device creation failed: -22.

Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Invalid argument

Error parsing global options: Invalid argument`

at ChildProcess.<anonymous> (/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22)
at ChildProcess.emit (node:events:524:28)
at ChildProcess._handle.onexit (node:internal/child_process:293:12)
  • AMD Radeon RX 9060 XT
  • the peertube vaapi transcoding plugin is installed
  • i have mesa-va-drivers and mesa-libgallium installed from bookworm backports.
  • the container is rootful.
  • /dev/dri is mapped
  • the render group id matches between host and container.
  • SELinux is set to allow containers access to devices.

no joy.

vainfo

error: XDG_RUNTIME_DIR is invalid or not set in the environment.

error: can't connect to X server!

libva info: VA-API version 1.17.0

libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so

libva info: Found init function __vaDriverInit_1_17

amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.

If they do, bad things may happen!

libva info: va_openDriver() returns 0

vainfo: VA-API version: 1.17 (libva 2.12.0)

vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for AMD Radeon Graphics (radeonsi, gfx1200, ACO, DRM 3.63, 6.15.4-1-default)

vainfo: Supported profile and entrypoints VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD VAProfileAV1Profile0 : VAEntrypointVLD VAProfileAV1Profile0 : VAEntrypointEncSlice VAProfileNone : VAEntrypointVideoProc

i've also tried updating the packages from trixie and sid, and installing the firmware-linux-nonfree.

i've tried disabling SELinux. i've tried making the container permissive.

no change.

any help is appreciated! thank you!

i’m starting to think it’s the debian base of this container image. it may just be too out of date for my GPU.

 

i just ended up going with a new image with the components installed, which i've been informed is best practice.

 

i just ended up going with a new image with the components installed, which i've been informed is best practice.


Hey there!

i have an Owncast container that needs two extra files added to it every time it starts up because the base image doesn't include them. they can be downloaded from within the container. i just need a way to tell the container to always do that when it starts up.

i've tried adding this to my quadlet:

[Container]

Exec=apk update && apk add --no-cache mesa-va-gallium mesa-dri-gallium

but it doesn't work.

does anyone know how to correctly automate this?

thanks!

 

SOLVED: turns out mesa is not enough for this. i also had to install:

mesa-va-gallium mesa-dri-gallium

now we're good!


hi all!

i've hit a wall here and could use your input if you have any thoughts!

i'm running Owncast latest via rootful Podman on a distro with SELinux.

i'm trying to implement hardware acceleration via the server's AMD GPU, but it is not working.

AMD Radeon RX 7600

Kernel: 6.15.4-1-default

i've turned VAAPI on in the web admin settings.

the container comes with ffmpeg 6 and libva.

For SELinux, i've run:

setsebool -P container_use_devices true

In my quadlet i've added:

[Container]

AddDevice=/dev/dri

Exec=apk add mesa

the devices appear rw in the container:

/app # ls -l /dev/dri

total 0

crw-rw---- 1 root 486 226, 0 Jul 9 15:58 card0

crw-rw---- 1 root 489 226, 128 Jul 9 15:58 renderD128

here is the error i'm getting:

time="2025-07-09T15:58:46Z" level=error msg="[AVHWDeviceContext @ 0x7f96891c7cc0] Failed to initialise VAAPI connection: -1 (unknown libva error)."

time="2025-07-09T15:58:46Z" level=error msg="Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': I/O error"

time="2025-07-09T15:58:46Z" level=error msg="transcoding error. look at data/logs/transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/codecs/"

time="2025-07-09T16:04:25Z" level=info msg="Inbound stream connected from 192.168.0.235:42698"

time="2025-07-09T16:04:25Z" level=info msg="Processing video using codec VA-API with 3 output qualities configured."

time="2025-07-09T16:04:25Z" level=error msg="[AVHWDeviceContext @ 0x7f8a2a047cc0] Failed to initialise VAAPI connection: -1 (unknown libva error)."

time="2025-07-09T16:04:25Z" level=error msg="Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': I/O error"

time="2025-07-09T16:04:25Z" level=info msg="Inbound stream disconnected."

time="2025-07-09T16:04:25Z" level=error msg="unable to write rtmp packet io: read/write on closed pipe"

time="2025-07-09T16:04:25Z" level=error msg="transcoding error. look at data/logs/transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/codecs/"

any help to troubleshoot this would be most appreciated! thank you!

view more: next ›