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

Raspberry Pi 4 is no longer correctly starting #12388

Closed
kaiomatico opened this issue Oct 5, 2019 · 8 comments
Closed

Raspberry Pi 4 is no longer correctly starting #12388

kaiomatico opened this issue Oct 5, 2019 · 8 comments

Comments

@kaiomatico
Copy link
Contributor

kaiomatico commented Oct 5, 2019

What happens?

PPSSPPSDL crashes and does not display the menu. It seems like the old issue of SDL not using the default display all over again on the Pi 4 maybe?

`pi@raspberrypi:~/ppsspp $ ./PPSSPPSDL
I: VulkanLoader.cpp:264: VulkanMayBeAvailable: Device allowed ('SDL:Linux')
I: VulkanLoader.cpp:271: VulkanMayBeAvailable: Library loaded ('libvulkan.so')
I: VulkanLoader.cpp:322: VulkanMayBeAvailable: Enumerating instance extensions
I: VulkanLoader.cpp:333: VulkanMayBeAvailable: Instance extension count: 2
I: VulkanLoader.cpp:341: VulkanMaybeAvailable: Instance extension found: VK_EXT_debug_report (00000009)
I: VulkanLoader.cpp:341: VulkanMaybeAvailable: Instance extension found: VK_EXT_debug_utils (00000001)
E: VulkanLoader.cpp:359: Surface extension not found
DEBUG: Vulkan is not available, not using Vulkan.
I: Config.cpp:517: Longest display side: -1 pixels. Choosing scale 1
20:25:244 Core/Config.cpp:1558 E[LOADER]: Failed to read /home/pi/.config/ppsspp/PSP/SYSTEM/controls.ini. Setting controller config to default.
20:25:249 Core/Config.cpp:1227 E[LOADER]: Error saving config - can't read ini '/home/pi/.config/ppsspp/PSP/SYSTEM/ppsspp.ini'
20:25:257 Core/Config.cpp:1272 I[LOADER]: Config saved (got storage permission): '/home/pi/.config/ppsspp/PSP/SYSTEM/ppsspp.ini'
20:25:257 Core/Config.cpp:1278 E[LOADER]: Error saving config - can't read ini '/home/pi/.config/ppsspp/PSP/SYSTEM/controls.ini'
20:25:258 Core/Config.cpp:1285 I[LOADER]: Controller config saved: /home/pi/.config/ppsspp/PSP/SYSTEM/controls.ini
Pixels: 960 x 544
Virtual pixels: 960 x 544

  • failed to add service - already in use?
    `

What should happen?

PPSSPPSDL should start normally showin the menu window with the game selection using the SDL / OpenGL backend as how it was up until very recently ( ~1 month since I last tried)

What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.

Raspberry Pi 4, latest raspbian (debian buster armhf based) with latest updates and firmware, latest git PPSSPP version pulled and compiled from git today

@kaiomatico kaiomatico changed the title Raspberry Pi 4 is suddenly Vulkan forced -> broken Raspberry Pi 4 is no longer correctly starting Oct 5, 2019
@unknownbrackets
Copy link
Collaborator

See here:
#12137 (comment)

Are you USING_FBDEV or not? Are you starting within X or not?

The only recent change to SDL was 18edfef. You could try reverting it.

-[Unknown]

@kaiomatico
Copy link
Contributor Author

I am using the ppsspp provided cmake file which auto detects the pi 4 model and then is not using_fbdev. I am running it within X. I also tried running not within X, then a red text appears
Failed graphics backends: OPENGL,ALL,ALL
Grapgics backend failed for 0, trying another
All graphics backends failed

Thank you, I will try reverting to the recent SDL change

@kaiomatico
Copy link
Contributor Author

kaiomatico commented Oct 6, 2019

Mh I checked out 5a4a968 so the codebase is before the recent SDL change, but I get this slighty different error message now (4 times an "ALL" backend)

pi@raspberrypi:~/ppsspp $ ./PPSSPPSDL
I: VulkanLoader.cpp:264: VulkanMayBeAvailable: Device allowed ('SDL:Linux')
I: VulkanLoader.cpp:271: VulkanMayBeAvailable: Library loaded ('libvulkan.so')
I: VulkanLoader.cpp:322: VulkanMayBeAvailable: Enumerating instance extensions
I: VulkanLoader.cpp:333: VulkanMayBeAvailable: Instance extension count: 2
I: VulkanLoader.cpp:341: VulkanMaybeAvailable: Instance extension found: VK_EXT_debug_report (00000009)
I: VulkanLoader.cpp:341: VulkanMaybeAvailable: Instance extension found: VK_EXT_debug_utils (00000001)
E: VulkanLoader.cpp:359: Surface extension not found
DEBUG: Vulkan is not available, not using Vulkan.
I: Config.cpp:517: Longest display side: -1 pixels. Choosing scale 1
59:58:650 Core/Config.cpp:1187 I[LOADER]: Loading controller config: /home/pi/.config/ppsspp/PSP/SYSTEM/controls.ini
59:58:654 UI/NativeApp.cpp:387 E[LOADER]: Failed graphics backends: OPENGL,ALL,ALL,ALL,ALL,ALL
59:58:654 Core/Config.cpp:599 E[LOADER]: Graphics backend failed for 0, trying another
59:58:654 Core/Config.cpp:624 E[LOADER]: All graphics backends failed
59:58:663 Core/Config.cpp:1272 I[LOADER]: Config saved (got storage permission): '/home/pi/.config/ppsspp/PSP/SYSTEM/ppsspp.ini'
59:58:664 Core/Config.cpp:1285 I[LOADER]: Controller config saved: /home/pi/.config/ppsspp/PSP/SYSTEM/controls.ini
Pixels: 960 x 544
Virtual pixels: 960 x 544

  • failed to add service - already in use?

Edit: just checked: after switching back to master and compiling and this time also make install'ing (not just make'ing) I get the same error message with these many backends. Running PPSSPPSDL as root however only says that the OPENGL backend has failed.

@hrydgard
Copy link
Owner

hrydgard commented Oct 6, 2019

It says right here that it's not using Vulkan:
DEBUG: Vulkan is not available, not using Vulkan.

Is there no log after Virtual Pixels? "Failed to add service", is that part of the log?

@kaiomatico
Copy link
Contributor Author

Yes I'm sorry I misread the Vulkan message (so I edited the thread title). After "Virtual pixels" there comes "Failed to add service" which is part of the log. After that no further logging appears and I get back to the shell prompt (so the program exited). I can see a window border with no content popping up for the fraction of a second before I get returned to the shell.

@unknownbrackets
Copy link
Collaborator

Failed to add service is something that is logged by Raspberry Pi drivers or something.

Maybe try fresh settings just in case:

mv /home/pi/.config/ppsspp /home/pi/.config/ppsspp~

And also make sure USING_FBDEV is not enabled. Maybe even use make clean and do a full rebuild after checking that it's off.

Do you remember the last sha that did work? If you go back to it, does it work again?

-[Unknown]

@kaiomatico
Copy link
Contributor Author

I reverted back to #edcd5e1 which was known working but it does not work now. I guess the latest raspberry pi drivers are broken, so no issue of PPSSPP itself. Feel free to close this now, it will probably fix itself :)

@hrydgard
Copy link
Owner

hrydgard commented Oct 6, 2019

Well, you should probably create a bug report upstream then! Thanks for testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants