Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for blank vr screens not working #2432

Open
2 tasks
bushibot opened this issue Sep 29, 2024 · 13 comments
Open
2 tasks

Fix for blank vr screens not working #2432

bushibot opened this issue Sep 29, 2024 · 13 comments
Labels
help request Not an issue, simply a help request

Comments

@bushibot
Copy link

Description

ALVR reports green, steam reports it seems the pico4 headset. Games start fine and show vr screen on monitor.
PICO screens remain blank (sometimes little bit of flashing).
I tried the recommended fix
~/.steam/debian-installation/steamapps/common/SteamVR/bin/vrmonitor.sh %command%
and
QT_QPA_PLATFORM=xcb ~/.steam/debian-installation/steamapps/common/SteamVR/bin/vrmonitor.sh %command%

No change.

General Troubleshooting

checked and rechecked, seems everything is in order.

Environment

Pop_os (Debian)

Hardware

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
https://linux-hardware.org/?probe=3db990dffa
CPU:
i9 13kf
GPU:
nvidia 4070TI
GPU Driver Version:
550
Audio:
realtek

Installation

ALVR Version:
20.1.1.1
ALVR Settings File:

SteamVR Version:
what ever is current
Install Type:

  • [ x] Packaged (exe, deb, rpm, etc)
  • Portable (zip)
  • Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
"Pop!_OS 22.04 LTS"
debug

[Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.623351522s, time: -495329086200094
20:34:25.384 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.634474491s, time: -495329075077125
20:34:25.396 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.645578136s, time: -495329063973480
20:34:25.407 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.656684074s, time: -495329052867542
20:34:25.418 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.667804647s, time: -495329041746969
20:34:25.429 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.678912459s, time: -495329030639157
20:34:25.440 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.690017355s, time: -495329019534261
20:34:25.451 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.701132824s, time: -495329008418792
20:34:25.462 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.712275741s, time: -495328997275875
20:34:25.473 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.723356053s, time: -495328986195563
20:34:25.485 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.734474074s, time: -495328975077542
20:34:25.496 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.745576001s, time: -495328963975615
20:34:25.507 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.756687251s, time: -495328952864365
20:34:25.519 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.767804803s, time: -495328941746813
20:34:25.531 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.778911522s, time: -495328930640094
20:34:25.540 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.790018084s, time: -495328919533532
20:34:25.551 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.801146261s, time: -495328908405355
20:34:25.563 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.812245741s, time: -495328897305875
20:34:25.573 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.823351157s, time: -495328886200459
20:34:25.586 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.834468501s, time: -495328875083115
20:34:25.596 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.845573866s, time: -495328863977750
20:34:25.607 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.856682668s, time: -495328852868948
20:34:25.618 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.867802147s, time: -495328841749469
20:34:25.629 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.878914491s, time: -495328830637125
20:34:25.640 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.890016366s, time: -495328819535250
20:34:25.651 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.901140636s, time: -495328808410980
20:34:25.662 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.912245793s, time: -495328797305823
20:34:25.673 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.923350897s, time: -495328786200719
20:34:25.684 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.934479543s, time: -495328775072073
20:34:25.696 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.94557673s, time: -495328763974886
20:34:25.707 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.956685584s, time: -495328752866032
20:34:25.718 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.967802876s, time: -495328741748740
20:34:25.733 [INFO] Client 7894.client: [Error] End frame failed! the provided XrTime was zero, negative, or out of range, timestamp: 18446248744.978907772s, time: -495328730643844
20:34:26.157 [INFO] Client disconnected. Cause: Connection refused (os error 111)
20:35:05.098 [INFO] Server disconnected
20:38:31.640 [INFO] GPU supports H264 profile.
20:38:31.640 [INFO] GPU supports HEVC profile.
20:38:34.041 [INFO] Server connected
20:38:37.029 [INFO] Initial socket buffer size: send: 87040B, recv: 131072B
20:38:37.052 [INFO] Initial socket buffer size: send: 212992B, recv: 212992B
20:38:37.052 [INFO] Set socket send buffer succeeded: 425984
20:38:37.052 [INFO] Set socket recv buffer succeeded: 425984
20:38:37.057 [INFO] Render Target: 4288 2336
20:38:37.057 [INFO] Refresh Rate: 90
20:38:37.059 [INFO] CEncoder::Run
20:38:37.060 [INFO] CEncoder Listening
20:38:37.067 [WARNING] Received invalid playspace size: [0, 0]
20:39:02.561 [INFO] Client disconnected. Cause: Broken pipe (os error 32)
20:39:45.038 [INFO] Initial socket buffer size: send: 87040B, recv: 131072B
20:39:45.057 [INFO] Initial socket buffer size: send: 212992B, recv: 212992B
20:39:45.057 [INFO] Set socket send buffer succeeded: 425984
20:39:45.057 [INFO] Set socket recv buffer succeeded: 425984
20:39:45.058 [INFO] Render Target: 4288 2336
20:39:45.058 [INFO] Refresh Rate: 90
20:39:45.067 [INFO] Received new playspace with size: [2, 2]
20:39:48.058 [INFO] Client disconnected. Cause: Broken pipe (os error 32)
20:39:57.042 [INFO] Initial socket buffer size: send: 87040B, recv: 131072B
20:39:57.059 [INFO] Initial socket buffer size: send: 212992B, recv: 212992B
20:39:57.059 [INFO] Set socket send buffer succeeded: 425984
20:39:57.059 [INFO] Set socket recv buffer succeeded: 425984
20:39:57.060 [INFO] Render Target: 4288 2336
20:39:57.060 [INFO] Refresh Rate: 90
20:39:57.072 [WARNING] Received invalid playspace size: [0, 0]
20:40:27.066 [INFO] Client disconnected. Cause: Broken pipe (os error 32)
20:40:49.107 [INFO] Server disconnected

@The-personified-devil
Copy link
Collaborator

You seem to also have the firewall issue from #2424

@The-personified-devil The-personified-devil added the help request Not an issue, simply a help request label Sep 29, 2024
@bushibot
Copy link
Author

bushibot commented Oct 1, 2024

I don't have a fire wall enabled, so I'm not seeing the connection even if the error is the same? I respectively suggest this is an issue and not just a help ask since disable your fire wall, which appears to be the solution in the other thread is suboptimal at best.
griffon@pop-os:~$ sudo ufw status Status: inactive

@The-personified-devil
Copy link
Collaborator

Even in that case it's tracked by that issue, this would just be a duplicate. Judging by some of the errors you could also try to properly restart your headset. After that it needs further investigating

@bushibot
Copy link
Author

bushibot commented Oct 2, 2024

I’m not sure what you mean by properly. I tried both headset reset, power cycle, and resetting steam. I run through a bunch of permutations. But the error seems to persist.

@gabriele2000
Copy link

I have the black screen issue inside the headset too, SteamVR now doesn't have problems unlike yesterday, but a complete reinstall of Steam using official debs and not ubuntu debs tends to fix most problems

In my case I'm using a Meta Quest 3

@bushibot
Copy link
Author

bushibot commented Oct 2, 2024

Even in that case it's tracked by that issue, this would just be a duplicate. Judging by some of the errors you could also try to properly restart your headset. After that it needs further investigating

That issues is closed and doesn’t seem to have a proper resolution.

@bushibot
Copy link
Author

bushibot commented Oct 2, 2024

I have the black screen issue inside the headset too, SteamVR now doesn't have problems unlike yesterday, but a complete reinstall of Steam using official debs and not ubuntu debs tends to fix most problems

In my case I'm using a Meta Quest 3

I’m on POp_os and using the proper Debian package.

@gabriele2000
Copy link

I’m on POp_os and using the proper Debian package.

I had to completely reinstall Steam using the official .deb from the website because SteamVR was complaining about "libcef.so missing" while it was right there... now it doesn't complain one bit, it doesn't crash one bit, but inside the headset I see black and a weird "light" flickering.

This is a new problem, love it.
I managed to overcome all odds and I'm stopped by... this

@Leetius
Copy link

Leetius commented Oct 8, 2024

I'm getting the same "End frame failed!" error and getting a black screen, even with the wiki fixes. I can't find anywhere else mentioning the error so i assume it's new. Using Tumbleweed with a Quest 1, SteamVR shows movement.

@bushibot
Copy link
Author

They already decided it was related to a clearly unrelated fire wall issue (as in I don't have one), so not sure this will get any real attention :p. The sorta fix in the other thread is no good here.

@gabriele2000
Copy link

They already decided it was related to a clearly unrelated fire wall issue (as in I don't have one), so not sure this will get any real attention :p. The sorta fix in the other thread is no good here.

I don't have a firewall either, but my system has iptables, and the "add firewall" button takes care of it too.
You have to press it two times, the first time it'll fail, the second time it'll succeed.

To verify it, do a sudo iptables -L, you should have everything working and even if the rules won't persist during reboots, it'll work anyway, somehow.

@The-personified-devil
Copy link
Collaborator

I'm getting the same "End frame failed!" error and getting a black screen, even with the wiki fixes. I can't find anywhere else mentioning the error so i assume it's new. Using Tumbleweed with a Quest 1, SteamVR shows movement.

Might be a vaapi codec thing, see https://dev.to/archerallstars/re-enable-va-api-hardware-video-acceleration-on-opensuse-tumbleweed-g8i

@Leetius
Copy link

Leetius commented Oct 13, 2024

That actually worked, even though I'm using an Nvidia card. Much obliged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help request Not an issue, simply a help request
Projects
None yet
Development

No branches or pull requests

4 participants