Conversation
|
Does it build? |
|
It compiles as a libretro core using: I just tried Dead or Alive Demo (I don't have any Saturn games) on my G4 OLED and it just goes to a black screen. I tried both GLES and GLES 2 compiled modes. It's correctly identified architecture as ARM according to my debugging in CMakeLists (I assume the JIT is automatically enabled by taking a quick look at the source?) I haven't used flycast before, but I tried a pre-compiled core on Ubuntu and that worked fine. I'm maintaining the webOS cores at the moment and doing lots of PRs to fix compilation issues. Here is a log if its any use: |
|
I happen to own a webOS TV. Unfortunately it's running an antique version (1.4) so I doubt I can run anything on it. |
|
Thanks for merging. If you want to give it a go: https://www.webosbrew.org/devmode/ The oldest confirmed version to work is webOS 3.4 (nobody has reported webOS 1 or 2 to me so I don't know) |
|
Surprisingly, not only retroarch installs fine but it actually runs! |
|
I'm curious did it produce a log? if it doesn't you can run it from ssh: cd /media/developer/apps/usr/palm/applications/com.retroarch.webos |
|
|
I think if you launched it with a setting to somewhere you had write access, it might work (but then again, launching it from the menu should have write access!) e.g. for me when debugging, but I created the retroarch folder. ./retroarch --verbose --config /media/developer/temp/retroarch/.config/retroarch.cfg |
|
After manually creating the config folder and editing retroarch.cfg, I managed to install the flycast core. This is the openmp shared lib used for texture upscaling. (I'm deprecating this feature btw) It can be disabled at build time with |
|
Looks like libgomp was introduced in webOS 3.9.2. I've removed it from retroarch-cores repo (might take a few mins to appear). On a clean install of retroarch, did it give you any indication of why it wasn't able to create the directories ? It should have had write permission to /media/developer/apps/usr/palm/applications/com.retroarch.webos/ where it was installed to. |
|
I installed retroarch from https://github.com/webosbrew/RetroArch/releases/tag/v1.22.2 and it installed without issue (I don't recall any notification in webos dev manager.) I don't know if retroarch itself showed any error since my TV is at the other end of the house 😄 and I first launched it from webos dev manager. |
|
Some progress. Now it looks like an issue with GLES. We might have reached the limit of what this version of webOS can do. |
|
Setting core logging level to debug doesn't provide more info |
|
Do you think you could uninstall it from the menu (this wipes the folder - or do it from webOS dev manager which also wipes the data), and try installing: https://github.com/webosbrew/RetroArch/actions/runs/20698787571/artifacts/5018990460 This makes sure HOME is set to the current working directory. Might fix the config issue launching from the menu. Regarding flycast, I haven't had the chance to investigate properly why it doesn't work on mine yet, and I'm on webOS 10. |
|
This is what I get (lots of Unknown trap vector then returns back to menu): My compiler always defines _OPENMP: |
|
I installed the RA update but it still can't write to its home folder: |
|
Was that launched from the menu? You would have to uninstall the app using webOS dev manager (which deletes the folder) and then re-install. Then launch from the menu. If you don't it would have been created with the wrong permissions (e.g. if your rooted for example, the folder may have root ownership if the first time you ran it was as root). |
|
I uninstalled and re-installed RA. Then did the first launch from the TV apps menu instead of dev manager but I was greeted with the usual |
|
I've asked in discord in case anyone can help. If your interested in building it yourself to find out the problem you can get the toolchain from: ./arm-webos-linux-gnueabi_sdk-buildroot/relocate-sdk.sh RetroArch is compiled with: It will automatically make the IPK in the webos/ folder. Or you can just upload the binary if you have write permissions. |
|
Not had any response on discord but would you be OK trying this build? If you uninstall, re-install: https://github.com/webosbrew/RetroArch/actions/runs/20753390573/artifacts/5038473647 I've added logging to /tmp/retroarch.log. It will set XDG_CONFIG_HOME, then create the .config folder if it doesn't exist. Could you provide the /tmp/retroarch.log? If you do run it from ssh accidentally, delete the file first otherwise it will have different permissions. |
|
Here is /tmp/retroarch.log, first run from the menu: No write permission to the app main directory. |
|
So thanks to a nice chap off Discord, both webOS 1 and 2 do not let you write to the app folders, which was then changed in webOS 3. Do you think you could find out if a file/directory persists in /tmp when the TV is powered off (switch off at the plug) and turn it back on? |
|
Unfortunately I can't easily unplug my TV because it's on a rigid wall mount. But I did a test anyway and the folder I created in |
|
That's great. Come up with a workaround if you can try it and let me know? (from the menu). /tmp/retroarch.log is still being written to. https://github.com/webosbrew/RetroArch/actions/runs/20895378655/artifacts/5089742768 If apps folder is not writeable, it will write config files to /media/developer/temp/webosbrew/com.retroarch.webos |
|
Yay! This build worked. With flycast I got the same |
|
That's great. Is /media/developer/temp a symlink to tmp? The code definitely says: It's separate directories on mine. The Unknown trap vector 8c008300 error needs to be investigated. |
|
Sorry, I meant |
|
Would you mind trying the build below for me? It has something I've been working on, adding wayland support. https://github.com/webosbrew/RetroArch/actions/runs/21092233778 You should try the bottom download, it will write to /tmp/retroarch.log as well as the normal retroarch log. If you could provide those logs? It needs some workarounds for the older wayland version which i've implemented. There is also a second IPK, this has GLES 3. I am not sure if it will run or not, because retroarch is supposed to use pointers to pick GLES 2 anyway. Would be good to see if that runs or not. (it wont if the above dont run!) |
|
The first build works and here is the (zipped) log: |
|
And the gles3 build also works: |
|
That's awesome thanks for trying that out. Could you post the normal retroarch.log as well? (not the one in /tmp?). Does the GLES 3 one actually load a core? (preferably one with GLES 2) and it works? |
|
The GLES3 build does run the 2048 core without issue and unloads then quits cleanly. |
|
Great, does something with 3D like Nintendo - Nintendo 64 (ParaLLel N64) - run Mario 64 for you? That is a specific GLES 2 core so if it works retroarch should deny GLES 3 and resort to GLES 2. If that doesnt work does the GLES 2 retroarch one work? |
|
Mario 64 with the ParaLLel core runs fine. I used the gles3 build. I didn't notice any graphical glitch but I don't have any controller on that thing so I couldn't get very far. |
Allows building for webOS