escalade : if I were to test a Ryzen CPU with an Nvidia GPU, which image should I choose?
Posts by slacker666
-
-
Liquidmercury : you should probably provide the zipped log file, not just the var logs
-
ive got a few dreamcast and sega saturn disks that ive dumped but I cant get them to play unless for atleast dreamcast I leave them in a file folder and saturn no joy at all am i misssing something as far as compiling iso's?
Have you added bios files for dreamcast (and ps2)? My issue with pcsx2 was that my hardware isn't supported (AMD APU)
-
Regarding PCSX2, it seems the repo I use for the container has advanced SIMD instructions enabled, so you're out of luck with your Sempron.
The ES warning is simply a warning, scraping should still work. I've added the missing tags and fixed genesis in my tree though, doing rebuilds now.
Ah, pity but thanks for the update!
Scraping works, but it's very inaccurate, it finds covers for nearly all platforms the game has been released on. -
Give the new generic image a spin, I fixed the shutdown option. Also do a docker pull escalade1/arch-pcsx2 to get the latest PCSX2 container. I might add Citra yes, but leaving for holiday a couple of weeks so not in the near future.
Didn't work either I'm afraid, still get the traps in pcsx2.sh:
"[ 95.509709] traps: PCSX2[1508] trap invalid opcode ip:5664282c sp:ffc897d0 error:0 in PCSX2[565aa000+5e0000]"But the shutdown from within ES works!
@Liquidmercury
After an update I don't seem to have the Genesis section either any more, plus ES scraper is warning that "some of your selected systems do not have a platform set." -
I did notice this in your journal which would explain no log, it seems to crash:
Jan 15 22:13:33 LibreELEC kernel: traps: PCSX2[1058] trap invalid opcode ip:56652833 sp:fff4bf20 error:0 in PCSX2[565ec000+559000]
Also lots of this in the Sway log:
mesa: st_get_external_sampler_key: unhandled pipe format 2
I'll push out a clean new generic image probably over the night, then you can test that. I'll also update the Arch container to get the latest Mesa, PCSX2 and dependencies, that might help. My image is bleeding edge everything, and the container OS is somewhat old.
Thnx a bunch, I'll do that!
Also, are you planning to add Citra/support for Nintendo 3DS in your generic version?One last thing, when entering menu in ES, it is not possible to shutdown system, it just restarts ES again.
-
That's the thing, I can't seem to produce a proper log for the issue as pcsx2.sh doesnt seem to run properly and does not generate any error. Is it possible to uninstall and re-install pcsx2? or open some gui for it to just see that it actually starts?
But I'll upload what I've got and hope there's something there. -
The varlog.txt? Logs for PCSX2 is in /var/log/pcsx2.log, there should definitely be a log showing the specific error.
Just post the logs from the log share as described in post 1.
/var/log/pcsx2.log is empty
This is from the zipfile in logfiles, that's the varlog i meant which i thought you meant as well (at least the zip containing all logs) -
I don't mean to be rude, but is your google not working? Nobody said anything about a ps2 subfolder, don't create unnecessary obstacles.
Anyway, here's what I got:
Code# md5sum SCPH-70004_BIOS_V12_PAL_200.* dc752f160044f2ed5fc1f4964db2a095 SCPH-70004_BIOS_V12_PAL_200.BIN 9feb1fdeadd6232a13b95e60b34ccef9 SCPH-70004_BIOS_V12_PAL_200.EROM 5195b9111609959d3a20e2fb9527edbd SCPH-70004_BIOS_V12_PAL_200.NVM 82dc50fa18e636850f557c4ea66c7bfd SCPH-70004_BIOS_V12_PAL_200.ROM1 82dc50fa18e636850f557c4ea66c7bfd SCPH-70004_BIOS_V12_PAL_200.ROM2 3faf7c064a4984f53e2ef5e80ed543bc SCPH-70004_BIOS_V12_PAL_200.mec 03792b108de92f9fa1d65956dc5f0d54 SCPH-70004_BIOS_V12_PAL_200.nvm
No rudeness taken
And I did a md5sum check on my files too which are the same as yours and put them in "/storage/roms/bios" - but the game won't start nonetheless.
Trying to run "/usr/bin/pcsx2.sh" from terminal just gives me this:
LibreELEC:/usr/bin # pcsx2.sh /storage/roms/ps2/game.iso
LIBREELEC_ARCH="Generic.x86_64"
LIBREELEC_PROJECT="Generic"
LibreELEC:/usr/bin #
the varlog.txt doesn't give me any info either, so I'm running out of ideas.
is it possible for you to post an es_systems.cfg with the appropiate entries for the genesis emulator for the generic build?
Here's mine:
-
You have an out of date es_systems.cfg, possibly from updating between incompatible builds. Copy over the one from /etc/emulationstation.
Excellent, thank you for pointing out this! I did install your old build from 20180820 and updated to Retroelec version above, but forgot to delete es_systems.cfg before updating, appreciate it!
Now I just need to fix the PS2 bios thing, how should they be named and they're stored in /storage/roms/bios I guess (tried creating subdir ps2 to no avail). Currently named SCPH-70004.BIN -
Hard to say without you posting the relevant logs as described on the first page. The emulationstation log doesn't show anything about what went wrong with the emulator. You should be using retroarch.sh, as it handles zip files, does necessary preparations for launching the emulator and outputs logs to disk. I suppose for PCSX2 you might not have the correct BIOS files. I don't use standalone Dolphin anymore, as the libretro core runs great these days. All the mentioned emulators launch fine here so I'm curious what's going on with your setup. Also please mention which build you are using.
I'm running RetroELEC-Generic.x86_64-9.1-devel-20200111203939-ea8d1e1.img , it seems like es_systems.cfg is pointing to "retroarch.start", which does not work, changing it to "retroarch.sh" does not work either, only "retroarch" works for nes/snes/gba/genesis and psp.
As for Dolphin, in the es_systems.cfg this is the command used for gamecube (and the same for Wii):<system>
<name>gc</name>
<fullname>Nintendo Gamecube</fullname>
<path>/storage/roms/gamecube</path>
<extension>.gcm .iso .wbfs .ciso .gcz .elf .dol .dff</extension>
<command>/usr/bin/dolphin.start -e %ROM%</command>
<platform>gc</platform>
It would seem as if the generic x86_x64 version would need an update regarding this? Not using libretro core but the standalone rather?
I have copied PS2 bios files but maybe they're named wrong, cause it still doesn't work. I will investigate further in this matter.This is the output from retroarch, not sure if you want any other logs (taken from varlog from the zipped file in Logfiles):
Code
Display More################################################################################ # ... output of cat /var/log/retroarch.log # LibreELEC release: Generic.x86_64-devel-20200111203939-ea8d1e1 # # https://github.com/escalade/RetroELEC # ################################################################################ [WARN] --libretro argument "-L" is neither a file nor directory. Ignoring. [INFO] RetroArch 1.8.3 (Git 99d5dba) [INFO] Redirecting save file to "/storage/.config/retroarch/savefiles/quicknes_libretro.srm". [INFO] Redirecting savestate to "/storage/.config/retroarch/savestates/quicknes_libretro.state". [INFO] === Build ======================================= [INFO] CPU Model Name: AMD Sempron(tm) 3850 APU with Radeon(tm) R3 [INFO] Capabilities: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES AVX [INFO] Built: Jan 11 2020 [INFO] Version: 1.8.3 [INFO] Git: 99d5dba [INFO] ================================================= [ERROR] Frontend is built for dynamic libretro cores, but path is not set. Cannot continue. [ERROR] Fatal error received in: "init_libretro_symbols()"
-
There is, but seems I forgot to add a platform for it in es_systems.cfg. I've uploaded a new build with that added, but after updating you'll need to add it to your local /storage/.config/es_systems.cfg, you can see the new addition in /etc/emulationstation/es_systems.cfg.
I get this error when trying to launch a game I believe:
So I assume there's another pathway for retroarch.start?Code
Display Morelvl2: Attempting to launch game... lvl0: VolumeControl::init() - Failed to attach to default card! lvl2: /usr/bin/retroarch.start -L /tmp/cores/quicknes_libretro.so /storage/roms/nes/game_rom.nes lvl1: ...launch terminated with nonzero exit code 32512! lvl2: Creating window... lvl2: Created window successfully. lvl2: GL vendor: X.Org lvl2: GL renderer: AMD KABINI (DRM 2.50.0, 5.5.0-rc5, LLVM 10.0.0) lvl2: GL version: 4.5 (Compatibility Profile) Mesa 20.0.0-devel lvl2: Checking available OpenGL extensions... lvl2: ARB_texture_non_power_of_two: ok lvl0: VolumeControl::init() - Failed to attach to default card!
edit again:
changed to the executable I could find:Code
Display Morelvl2: (missing) lvl2: Attempting to launch game... lvl0: VolumeControl::init() - Failed to attach to default card! lvl2: /usr/bin/retroarch.sh -L /tmp/cores/quicknes_libretro.so /storage/roms/nes/game_rom.nes lvl2: Creating window... lvl2: Created window successfully. lvl2: GL vendor: X.Org lvl2: GL renderer: AMD KABINI (DRM 2.50.0, 5.5.0-rc5, LLVM 10.0.0) lvl2: GL version: 4.5 (Compatibility Profile) Mesa 20.0.0-devel lvl2: Checking available OpenGL extensions... lvl2: ARB_texture_non_power_of_two: ok lvl0: VolumeControl::init() - Failed to attach to default card!
still no success though as you can see I guess.
Edit again:
Ok I figure it out, I had to change es_settings.cfg to use "retroarch" instead of "retroarch.start", then the game would launch. This only applies to nes, snes, genesis and gba though. mame, n64 , ps2 and psp still behaves the same as before; the "sway" background shows for a sec and then quits back to ES without game launching.
These are the errors I get when trying to launch mame or ps2 (for which i ran the pcsx2.sh file in terminal and it downloaded the docker):Code
Display Morelvl2: Attempting to launch game... lvl2: /usr/bin/retroarch -L /tmp/cores/mame2014_libretro.so /storage/roms/mame/game.zip lvl1: ...launch terminated with nonzero exit code 256! lvl2: Creating window... lvl2: Created window successfully. lvl2: GL vendor: X.Org lvl2: GL renderer: AMD KABINI (DRM 2.50.0, 5.5.0-rc5, LLVM 10.0.0) lvl2: GL version: 4.5 (Compatibility Profile) Mesa 20.0.0-devel lvl2: Checking available OpenGL extensions... lvl2: ARB_texture_non_power_of_two: ok lvl0: VolumeControl::init() - Failed to attach to default card! lvl2: req sound [detailed.launch] lvl2: (missing) lvl2: Attempting to launch game... lvl2: /usr/bin/pcsx2.start /storage/roms/ps2/game.iso lvl1: ...launch terminated with nonzero exit code 32512! lvl2: Creating window... lvl2: Created window successfully. lvl2: GL vendor: X.Org lvl2: GL renderer: AMD KABINI (DRM 2.50.0, 5.5.0-rc5, LLVM 10.0.0) lvl2: GL version: 4.5 (Compatibility Profile) Mesa 20.0.0-devel lvl2: Checking available OpenGL extensions... lvl2: ARB_texture_non_power_of_two: ok lvl0: VolumeControl::init() - Failed to attach to default card!
(the same also occurs on gamecube & Wii, don't think there's a /usr/bin/dolphin.start exec)
if I instead run the pcsx.sh with %ROM% from terminal, it looks like this:
LibreELEC:/usr/bin # pcsx2.sh /storage/roms/ps2/game.iso
LIBREELEC_ARCH="Generic.x86_64"
LIBREELEC_PROJECT="Generic"
LibreELEC:/usr/bin #
-
Try this build: x86-64 – Google Drive
It's compiled with -march=x86-64 like regular LibreELEC. Your mileage may vary with recent generations of nvidia cards though.
Just tried this version and seems like you fixed the scraping issue in ES and also quit to kodi works now so that's great! However, it seems as when I start a game from ES it won't start just exits back to ES in a second (I see "Sway" showing up for a sec), but if I start the very same title from Retroarch it works and I can play. Any ideas what I'm missing?
Thank you in advance! -
thanks so much for the more vanilla build, i can get it to boot but the next question ive got is probably pretty rudimentary. How do I enable my game pad to work in emulationstation? Thanks in advance.
You need a keyboard and then you can navigate to settings (Ctrl key) in ES and from there choose "configure input" to configure your game pad.
-
Haven't had the time to look at it yet. Add "frontend=es" to the kernel command line in /flash/syslinux.cfg. Sorry, I don't see the use for a web interface. There's SSH and ttyd
Okay, patience is a virtue tho
All right, so the storage/.config/frontend.conf is not in use? No worries, worth a shot and not that important.
-
were you able to reproduce the errors I am having in ES? Eagerly waiting for an updated version Keep up the good work!
Also, not sure if it's my end or not, but in "frontend.conf", I tried using both "emulationstation" and "es" but it would still start into Kodi. Seeing how I cant go back from ES to Kodi it was probably for the better and it could be my setup too I guess, but if you could look into that too maybe?
Feature request: is it possible to get something that Recalbox uses, a web interface for settings (anything from hostname to wifi settings are done there) and upload of roms/bioses etc, see below for an example:
Also, they boot into a modified version of ES where you press "X" on your gamepad to launch Kodi, very nifty. Just two ideas which you can send to /dev/null if it's too much work/not applicable.
Thank you in advance! -
This build uses Pulseaudio. In case you've got several outputs and the connected one isn't auto-detected, you need to set the default with something like this:
# pactl set-default-source alsa_output.pci-0000_00_1f.3.hdmi-stereo.monitor
Obviously you shouldn't update to a different OS, I'll remove the hardcoded menu entry in RetroArch that makes it possible. As for the ES issues, I'll have a look at it.
Yeah I figured that was a bad move, but at first I thought it would only update Retroarch itself and not the entire OS.
Great, thanks a lot!
-
escalade finally got around to install your build two days ago, installing was no issue, but if i started a game from Emulationstation it wouldn't get any sound. If i started from retroarch it worked fine though (with hw:0,3 audio setting). Also, couldn't scrape games in ES, got the following error "some of your systems do not have a platform set".
Couldn't import games in Retroarch either and it seems to be based on Lakka, so when I updated Retroarch/Lakka it updated the whole OS :p
Lastly, I couldn't go back to Kodi once I launched ES, if I chose Shutdown Emulationstation it would just start again.