RetroELEC Kodi+Wayland+Emulationstation+RetroArch (x86/XU4/RPi)

**escalade** · February 26, 2020 at 12:04 AM

Also check if there is a /var/log/sway.log.

Liquidmercury · February 26, 2020 at 1:44 AM

there is a /var/log/docker some other files and a private folder attaching docker.log

**escalade** · February 26, 2020 at 2:24 AM

I've uploaded

RetroELEC-Generic.x86_64-9.2-devel-20200226025821 where I've reverted the extra F2FS features (encryption and compression), that I think might have caused issues. Please give it a shot.

mtk1 · February 26, 2020 at 6:15 AM

Quote from escalade

mtk1

Seems like you are on an old release as well Generic.x86_64-devel-20200220125702-28eddc2. Latest is

RetroELEC-Generic.x86_64-9.2-devel-20200225010434-28eddc2.img.gz md5sum

66b9f295f70544861b7f75c859753621.

I'm sure I installed that release. Here:

mathias@stretch[i686]:~/src/WiBACK/node> ssh root@cinemax

#############################################

# RetroELEC #

# GitHub - escalade/RetroELEC: Just enough OS for emulators (and some other stuff) #

#############################################

RetroELEC (community): devel-20200225010434-28eddc2 (Generic.x86_64)

Anyway, I will give your latest release a try.

mtk1 · February 26, 2020 at 8:05 AM

Quote from mtk1

I'm sure I installed that release. Here:

mathias@stretch[i686]:~/src/WiBACK/node> ssh root@cinemax

#############################################

# RetroELEC #

# GitHub - escalade/RetroELEC: Just enough OS for emulators (and some other stuff) #

#############################################

RetroELEC (community): devel-20200225010434-28eddc2 (Generic.x86_64)

Anyway, I will give your latest release a try.

Display More

OK. So, a fresh install helped. I'm now on the latest release from the 26th.

"Desktop" starts and I can use FF.

What is the suggested 'mouse' device to use ? Is there any chance to use a PS3 controller (joystick) ?

**escalade** · February 26, 2020 at 9:02 AM

You might be able to set up antimicro (gamepad icon) to do it, not sure. In any case, if you are gaming just get a DS4 they are superb as mouse and even have two-finger scrolling and right click. Or an iPazzport from dealextreme.

Yohoki · February 26, 2020 at 9:32 AM

Quote from jaykass

Try flashing a clean image. I suspect upgrading from LibreELEC will not work properly.

Sorry, I wasn't clear enough. That's my fault. By upgrade, I meant that I've removed the USB running LibreELEC and put in a new USB with RetroELEC. There is no HDD, so it's all run off the USB for now. So it is a clean install.

Edit:

The issue seems to have something to do with the version I was using. I've tried again today with the newest generic build and it works. Whatever you've changed seems to have fixed it. Thanks!

RetroELEC-Generic.x86_64-9.2-devel-20200226025821-28eddc2 = works

RetroELEC-Generic.x86_64-9.2-devel-20200214162808-28eddc2 = Boot loop

**escalade** · February 26, 2020 at 12:39 PM

Great to hear! In other news, the XU4 images have a functional desktop as well now. RPi is next

Oh, and worth to mention the generic builds has the 330% vulkan mesa improvement for gen7/haswell. Happy gaming.

Liquidmercury · February 26, 2020 at 6:09 PM

Im at a complete loss as to why this is not working at all for me, both desktop and emulationstation hang at a black screen. Right now Im trying to roll back to the images that I still have im beginning to wonder if its a hardware issue with the new generics for me and I'll just live with what I can hopefuly get working until I can get some new hardware. The strange thing is when Im looking at my log files it seems that new ones are not being created. I know that Ive rebooted several times today for example but my most recent log file is showing from 2/24/2020

does anyone have the 821 image?

**escalade** · February 26, 2020 at 6:18 PM

Liquidmercury

You can see the version tag when you log in through SSH, perhaps there is an issue writing to your filesystem for some reason? Is the upgrade succcessful at all? You can try hitting "escape" when the upgrade boot animation is running to see what's going on in the background. I'm interested to see the log files from the actual issue as well, you can upload them to pastebin with the command pastebinit < logfile.

Liquidmercury · February 26, 2020 at 6:32 PM

the latest version you have on google drive kodi works fine but when I try to enter emulation station or the desktop it just hangs the only thing that I can enter into with out issue is retroarch.

**escalade** · February 26, 2020 at 6:36 PM

Well yeah, I'd like to see the logs and verify that you are actually running the latest version. If Emulationtation doesn't start, it should say something in sway.log, emulationstation.log or system.log.

Liquidmercury · log-2020-02-26-19.57.26.zip

Ill upgrade to the latest 944 image from your google drive I do have a copy of image 253 that boots emulationstation for me, there was also an image in the test folder 937 im assuming do an install of 944 and press escape key while it says reading from file during upgrade?

From what I could tell everything looked ok when I hit escape during upgrade did not see any errors could not find the emulationstation.log nor system.log

Watching my tv screen, there’s an input info box that shows up periodically during the black screen the same that pops up when you Change inputs or power on makes me think bootloop

**escalade** · February 26, 2020 at 9:15 PM

Code

2020-02-26 20:00:38 - [backend/drm/drm.c:1305] Found connector 'DP-1'
2020-02-26 20:00:38 - [backend/drm/drm.c:1453] Requesting modeset for 'HDMI-A-1'
2020-02-26 20:00:38 - [backend/drm/drm.c:697] Modesetting 'HDMI-A-1' with '1366x768@59790 mHz'
2020-02-26 20:00:38 - [backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument
2020-02-26 20:00:38 - [backend/drm/drm.c:611] Page-flip failed with primary FB modifiers enabled, retrying without modifiers
2020-02-26 20:00:38 - [backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument
2020-02-26 20:00:38 - [backend/drm/drm.c:620] Failed to initialize renderer on connector 'HDMI-A-1': initial page-flip failed
2020-02-26 20:00:38 - [backend/drm/drm.c:703] Failed to initialize renderer for plane
2020-02-26 20:00:38 - [sway/config/output.c:398] Failed to modeset output HDMI-A-1

Something weird going on, it seems to find your connector at DP-1 but tries to set up HDMI-A-1 instead. What do you mean bootloop, does it reboot? Does the network interface go down?

Try replacing /storage/.config/sway/config with a copy of /etc/sway/config, then add this to the end:

output DP-1 resolution 1920x1080

BTW, is your main GPU the integrated Intel HD Graphics 2500? I suppose maybe it's too old and lacking something in way of GLES compatibility, but then again I see no sign of that. Perhaps the connector issue can be fixed by config.

Liquidmercury · February 27, 2020 at 12:09 AM

added that line to the end of the replaced config file and I still cannot launch into desktop or emulationstation.

mtk1 · February 27, 2020 at 7:43 AM

Quote from escalade

You might be able to set up antimicro (gamepad icon) to do it, not sure. In any case, if you are gaming just get a DS4 they are superb as mouse and even have two-finger scrolling and right click. Or an iPazzport from dealextreme.

Connection via Bluetooth (pairing in Retro/LibreElec) would work ?

Gaming is not the main activity. But something that could act as mouse and gamepad would be nice.

As a gyro mouse / keyboard, I also tried this one here: Orbsmart AM-1 – Orbsmart

The gyro does not work so well, though/

Liquidmercury · February 27, 2020 at 3:03 PM

went through and googled each error this is what i got dont know if it will help nail down the problem.

[backend/drm/drm.c:1305] Found connector 'DP-1' ---- Sway cannot initailize rendered for external monitor - DP-1: Atomic commit failed (modeset): Invalid argument · Issue #1877 · swaywm/wlroots · GitHub

[backend/drm/drm.c:1453] Requesting modeset for 'HDMI-A-1' --- [backend/drm/drm.c:1453] Requesting modeset for 'HDMI-A-1' - Yahoo Search Results

[backend/drm/drm.c:697] Modesetting 'HDMI-A-1' with '1366x768@59790 mHz' --- [backend/drm/drm.c:697] Modesetting 'HDMI-A-1' with '1366x768@59790 mHz' - Yahoo Search Results

[backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument --- [backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument - Yahoo Search Results

[backend/drm/drm.c:611] Page-flip failed with primary FB modifiers enabled, retrying without modifiers -- [backend/drm/drm.c:611] Page-flip failed with primary FB modifiers enabled, retrying without modifiers - Yahoo Search Results

[backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument -- [backend/drm/util.c:210] Unable to add DRM framebuffer: Invalid argument - Yahoo Search Results

[backend/drm/drm.c:620] Failed to initialize renderer on connector 'HDMI-A-1': initial page-flip failed -- [backend/drm/drm.c:620] Failed to initialize renderer on connector 'HDMI-A-1': initial page-flip failed - Yahoo Search Results

[backend/drm/drm.c:703] Failed to initialize renderer for plane --[backend/drm/drm.c:703] Failed to initialize renderer for plane - Yahoo Search Results

[sway/config/output.c:398] Failed to modeset output HDMI-A-1 -- [sway/config/output.c:398] Failed to modeset output HDMI-A-1 - Yahoo Search Results

Not sure if what ive done here will help at all but it does seem at least others are having issues like mine. I really do appreciate you looking into this as much as you have.

Liquidmercury · February 27, 2020 at 3:41 PM

Did some more searching at the sway website and I came across in the wiki section of known issues --sway crashing right away #5033 the issue was opened six days ago, the time frame seems to fit in my head of when issues started (dont quote me on that it may just be wishful thinking) just a thought. Might be worth looking into i guess. if there is anything else you need from me regarding this please do not hesitate to ask.

RetroELEC Kodi+Wayland+Emulationstation+RetroArch (x86/XU4/RPi)

Similar Threads

HDMI Output to Top Left of TV Screen