Posts by jaykass

Quote from escalade

jaykass

Could you tell me a bit about how it performs in different cores? Is it powerful enough to use any shaders? I'd be interested to know if it can use the crt-frutbunn shader for example.

I tested Gameboy, Gameboy color, Gameboy advance, NES, SNES, Genesis, n64, and an assortment of arcades. Everything seemed to run at full speed (and I have my display at 1080p), steady 60fps when applicable. I ran more emulation intensive games (such as Mario World 2 for the SNES) if I am aware of them.

If you have specific games you are curious about, I can look at them specifically.

As for the shaders, retroarch doesn't seem to recognize any of the installed shaders. I verified via sftp that they exist (and in the right location) but retroarch just shows empty dirs. Is there an option to have retroarch recognize the slang shaders? I don't generally use shaders so this testing is for others' benefit, not my own.

Quote from Liquidmercury

I think I was pulling the wrong log files, was pulling the last set not second from last. Sorry brain fart on my part hopefully this is what you need.

Per a response Escalade had earlier to a question of mine, those logs seem to be created when you connect to the share. So, you'll want to boot your system, trigger the error, and then pull the latest logs before rebooting again.

Quote from escalade

jaykass

Yeah, I did the same with the RPi3b, it performs a lot better at 720p. I agree with you that it would make sense to set 1080p as a default for the RPi4. Hardware accelerated video playback at 4k is a totally different thing from being able to rendering graphics at 4k. Could you tell me a bit about how it performs in different cores? Is it powerful enough to use any shaders? I'd be interested to know if it can use the crt-frutbunn shader for example.

I'll continue to test cores and I'll look at that shader specifically. So far everything I've tested has been at 1080p 60fps.

Are you interested in pull requests? I would like to have just a few more cores (tg16/pcengine, Sega CD, sameboy or gambatte depending on performance). If you push your latest to GitHub, I'll send some PR if/when I make any worthwhile changes.

Quote from jaykass

Screen tearing still seems to be a minor problem in Kodi, this is also the case in the latest stable vanilla LE build (9.2).

I just took another look and I think the tearing may be resolved by escalade.

escalade I recommend if someone is connecting a Pi4 to a 4K TV that they force the display into 1080p60Hz otherwise it feels a bit laggy in the various interfaces. Once I switched to 1080p, it all seems to be running buttery smooth!

I added the following to my /flash/config.txt:

hdmi_group=1
hdmi_mode=16

I'm not sure if it is something that makes sense to have as a default or not for Pi4 builds but I can't imagine anyone would want to run this at 4K based on performance.

Quote from escalade

Can anyone confirm if the screentearing in menus’s is fixed in the rpi4 build?

Screen tearing still seems to be a minor problem in Kodi, this is also the case in the latest stable vanilla LE build (9.2).

Quote from escalade

jaykass

Regarding multiple key presses, did you try disabling lirc (seem to remember that was a solution in a thread with similar issue)? Can't say I have much experience with remotes. My lirc and eventlircd package is now in sync with LE 9.2, not sure I can be of further help regarding that.

I figured this out.

Your build is missing some standard LE udev rules for some reason. I note the specific issue below but you may wish to review why others are also missing.

In my case "/usr/lib/udev/rules.d/70-input-repeat.rules" fixes this issue.

ACTION=="add", SUBSYSTEM=="input", KERNEL=="event[0-9]*", GOTO="start"
GOTO="end"
LABEL="start"

# don't change eventlircd device settings
ATTRS{name}=="eventlircd", GOTO="end"

# don't change settings of rc remotes
SUBSYSTEMS=="rc", GOTO="end"

# set default repeat delay to 500ms like rc remotes
RUN+="/usr/bin/ir-keytable --delay=500 --device=$devnode"

# make lircd-uinput use same repeat period like keyboards in kodi
ATTRS{name}=="lircd-uinput", \
  RUN+="/usr/bin/ir-keytable --period=80 --device=$devnode"

LABEL="end"

To verify the fix, I copied the file from Vanilla LE to your build in "/storage/.config/udev.rules.d/70-input-repeat.rules"

This will work as a temp resolution for me until it gets included properly in "/usr/lib/udev/rules.d/"

Here are all the rules found in Vanilla LE but not in your build:

70-infrared.rules

70-input-repeat.rules

90-libinput-model-quirks.rules

96-e2scrub.rules

98-eventlircd.rules

Quote from jaykass

No worries about being the guinea pig. I want this on my Pi4, so the way I look at it, you are doing me a huge favor.

RetroELEC-RPi4.arm-9.2-devel-20200123173325-28eddc2.img

• Errors/warnings at boot are gone.
• Launching Retroarch results in restarting Kodi.
• Launching Browser displays SWAY for a long while and then restarts Kodi. Previously it just restarted Kodi.
• I tried to launch an NES rom from ES and it just exited back to ES.
• Multiple button presses/missing button presses remains when using flirc.

Do you need someone to review the RPi2 image as well? I still have an assortment of RPi2/3/3+. If so I can review after we get through testing the RPi4 image.

Latest log file attached.

RetroELEC-RPi4.arm-9.2-devel-20200125142536-28eddc2.img

• Retroarch is now working
• Browser still fails (honestly, I don't care about this but I'll keep testing if you want)
• Multiple button presses/missing button presses remain when using flirc.
  • Not 100% certain but I think it might be better (but not completely fixed) by setting my TV to 1080p 60hz rather than the default 4K 30hz. I'll be running at 1080p most likely anyway. I have no need to drive 4K at this time.
  • I updated fw on the flirc which took me down a nightmare path last night, but same results in the end.
  • Is lirc easy to disable? I didn't see it in settings. I'll google around if you aren't sure off the top of your head.

Latest log attached.

This is now at a point where I will use as primary OS so I may have more specific feedback as I go.

Quote from escalade

That's odd, I can't see any Emulationstation or retroarch logs in there, perhaps you had rebooted inbetween. Looks like something went wrong while extracting the container. These issues are fixable though, the logs are of great help. Please do test RPi2/RPi3 if possible too, although I expect them to work the same. They should perform better with the new Mesa driver as well.

No reboot was done. I can grab Retroarch and ES logs separately though.

*EDIT*

D'oh! I think I did reboot from within ES.

Updated log attached. I saw RA and ES logs in there.

Quote from escalade

jaykass

Thanks for being my guinea pig here, can you try out the latest image? The mentioned issues should now be fixed I've created a new browser container for ARM as well, escalade1/archarm, which has Firefox 72. It's a bit on the fat side (~1GB compressed), and completely untested as I don't have any RPi available to test.

No worries about being the guinea pig. I want this on my Pi4, so the way I look at it, you are doing me a huge favor.

RetroELEC-RPi4.arm-9.2-devel-20200123173325-28eddc2.img

• Errors/warnings at boot are gone.
• Launching Retroarch results in restarting Kodi.
• Launching Browser displays SWAY for a long while and then restarts Kodi. Previously it just restarted Kodi.
• I tried to launch an NES rom from ES and it just exited back to ES.
• Multiple button presses/missing button presses remains when using flirc.

Do you need someone to review the RPi2 image as well? I still have an assortment of RPi2/3/3+. If so I can review after we get through testing the RPi4 image.

Latest log file attached.

Quote from escalade

jaykass

Please try the latest build, it should be linked correctly against bcmhost to fix the undefined symbol and kernel is in sync with master.

Using RetroELEC-RPi4.arm-9.2-devel-20200122130326-28eddc2.img.

Noticed an error/warning during boot. I think it said "NFSD", hopefully it'll show up in the logs.

Boots into Kodi.

Launches ES properly.

Trying to launch Retroarch just causes Kodi to restart. Same thing for Browser.

In general, Kodi seems to be working properly. I have a flirc that I use with a remote control, with this build there are many more double key-presses and unresponsive button presses than with base LibreELEC (which is essentially none). When I use a standard keyboard however, nothing feels out of the ordinary.

I'll review more in the coming days (e.g. I haven't tried to run any emulator cores yet).

Latest logs attached.

Quote from escalade

They are automatically generated by the createlog script when connecting to the Logs share. Placement in the filesystem is /storage/Logs.

Please try RetroELEC-RPi4.arm-9.2-devel-20200122001042-28eddc2.img.gz that I have just uploaded.

Seemingly same results with RetroELEC-RPi4.arm-9.2-devel-20200122001042-28eddc2.img.

Logs attached.

Quote from escalade

jaykass

Awesome, I think I have an idea what to fix now. Please provide the logfiles as outlined on the first page of the thread.

Attached.

Do you know where these logs are located when accessing via ssh/scp? I couldn't find them until I connected using samba.

Quote from escalade

jaykass

I think so. It seems I had messed up the bootloader. Could you try the one I've just uploaded?

Using RetroELEC-RPi4.arm-9.2-devel-20200120093047-28eddc2.

First boot, I see the RetroELEC splash (looks real nice, btw), resizing file system, then reboots as expected.

Then it hung for a minimum 15 minutes during boot-up.

I forced a reboot and now following the RetroELEC splash screen I get a blank screen. Note: A signal appears to be sent as my TV would otherwise display a no signal message.

I have SSH access so I did the following:

RetroELEC:~ # paste /storage/.kodi/temp/kodi.log
cat: can't open '/storage/.kodi/temp/kodi.log': No such file or directory

RetroELEC:~ # dmesg|paste
http://ix.io/27WP

RetroELEC:~ # cat /var/log/emulationstation.log
lvl2:   EmulationStation - v2.10.0rp-dev, built Jan 20 2020 - 09:31:10
lvl2:   Parsing XML file "/storage/../usr/share/emulationstation/resources/mamenames.xml"...
lvl2:   Parsing XML file "/storage/../usr/share/emulationstation/resources/mamebioses.xml"...
lvl2:   Parsing XML file "/storage/../usr/share/emulationstation/resources/mamedevices.xml"...
lvl2:   Creating window...
lvl0:   Error initializing SDL!
        Couldn't create gbm device.
lvl0:   Renderer failed to initialize!
lvl0:   Window failed to initialize!

Am I the first to try RPi4?

It doesn't seem to boot. I get no video output and no signs that it got far enough to connect to my network (wired).

Quote from MagicSeb

This one : leia-18.4-rpi4

You can compile master branch but, you will NOT get optimised HEVC decoding

I'm sorry, I meant from LibreELEC. Reviewing your commits, it looks like its master but last merged in October.

Have you considered building from the LE9.2 branch?

Quote from MagicSeb

Release 2019-12-10-RPi4 · magicseb/LibreELEC.tv · GitHub

latest release

Updated to 18.5 kodi

Are you still building from master branch? Or 9.2 branch?

I was able to successfully build for a RPi4 from your dev-RR branch. 😀

The system booted to Kodi successfully. The default of 4Kp30 display setting seemed a bit glitchy and sluggish. I tried changing to 1080p60 but it was only displaying as the upper left quarter of the screen. I tried to start emulationstation and retroarch from the home screen and both relaunched Kodi (I'm guessing both crashed and your script/systemd relaunched Kodi).

To see if these were LE issues or just your build I reflashed the SD card with the current 9.2 beta (9.1.501). The default of 4Kp30 did not feel sluggish and changing to 1080p60 did not result in only the upper left corner display.

I didn't pull logs yet but want to give you a heads up on a couple early issues. Hopefully I can review more this weekend and get some logs as well. I understand this is from the dev branch and you are likely actively working on changes.

Back to my S905X for now.

Quote from SpaceAgeHero

Hi,

this project looks awesome.

(When) will Raspberry Pi 4 be supported?

5schatten has merged several pull requests I created to fix building for a RPi4 but a few build errors remain. Furthermore, nothing has been tested regarding performance. I haven't actively worked on the RPi4 build errors for a while as I recently moved which has taken up most of my free time.

Assistance is welcome.