Odroid XU4 SDL Problem Emulationstation

mitu

@aaronouthier said in Odroid XU4 SDL Problem Emulationstation:

I'll be back shortly.

There's no rush. When you get to the system, just look up and check what repositories are enabled/used by your system.

aaronouthier

root@odroid:~# cat /etc/apt/sources.list
deb http://ports.ubuntu.com/ubuntu-ports/ noble main universe restricted
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble main universe restricted

deb http://ports.ubuntu.com/ubuntu-ports/ noble-updates main universe restricted
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble-updates main universe restricted

deb http://ports.ubuntu.com/ubuntu-ports/ noble-backports main restricted
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble-backports main restricted

deb http://ports.ubuntu.com/ubuntu-ports/ noble-security main restricted
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble-security main restricted
deb http://ports.ubuntu.com/ubuntu-ports/ noble-security universe
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble-security universe
deb http://ports.ubuntu.com/ubuntu-ports/ noble-security multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ noble-security multiverse

mitu

@aaronouthier I see - this is 32bit system ? I think the default Ubuntu repos - and the ports system - don't have these packages, although they're available for 64bit (arm64). Isn't the XU4 a 64bit CPU - shouldn't you be using a 64bit system ?

aaronouthier

@mitu No, the xu3 and xu4 are 32 bit CPUs, to the best of my knowledge.

aaronouthier

@mitu Even if, for some reason, the CPU is 64-bit capable, there is no 64-bit OS available for it.

mitu

@aaronouthier That explains the lack of Ubuntu packages in recent versions. Maybe use the armhf packages from the previous LTS (22.04) - https://packages.ubuntu.com/jammy/python3-uinput ?

aaronouthier

@mitu Would it be worth the trouble, you suppose, to rework the install from scratch with 22.04 LTS as the OS? If the packages are present, it may be worth a shot. I will try your suggestion 1st however, just for fun and learning.

FWIW, I just checked to verify: XU4 uses an Samsung Exynos 5422 CPU, which is definitely 32-bit hardware.

aaronouthier

Just installed python3-urwid. The SDL2 packages were installed from source. Do I still need python3-sdl2, or is that taken care of by the main sdl2 source package? I don't want to mess-up/overwrite anything that was installed manually.

aaronouthier

FWIW, speaking of sources, I was able to download the sources with 'apt source python3-uinput' from current repos. Not too sure how I can incorporate that into the existing build.

I've compiled stuff before, but never via apt-source.

mitu

@aaronouthier said in Odroid XU4 SDL Problem Emulationstation:

Do I still need python3-sdl2, ...

Yes, only the SDL library is compiled into a package, the rest are expected to be provided by the distribution's repostories.

aaronouthier

@mitu I was pretty sure this was the case, but wanted to be certain.

aaronouthier

Dang it!

running build
running build_py
running build_ext
building '_libsuinput' extension
arm-linux-gnueabihf-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -fPIC -I/usr/include/python3.12 -c libsuinput/src/suinput.c -o build/temp.linux-armv7l-cpython-312/libsuinput/src/suinput.o
libsuinput/src/suinput.c: In function ‘suinput_emit’:
libsuinput/src/suinput.c:48:28: error: ‘struct input_event’ has no member named ‘time’
   48 |         gettimeofday(&event.time, 0);
      |                            ^
error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1

Trying to build the source package.

Was logged-in as root. I don't think that would make a difference though.

aaronouthier

@mitu Not able to install the 22.04 version either. Depends on Python3.10 or below, but Python3.12 is installed.

At this point, I think I'm going to wipe the SD card and try again with 22.04 .

aaronouthier

Currently compiling the system for xu4 under Ubuntu 22.04 Operating System. No problems yet. (Need to go knock some wood now...)

aaronouthier

Well, about 1.5 hours later, compilation finished. No errors reported during compile process that I could see, however, emulationstation crashes when run.

I tried with --debug flag, however the screen is cleared by the crash dialog that comes up, so I can't read. I'll try tee'ing it to a text file.

aaronouthier

@aaronouthier I watched a bit closer. Nothing out of the ordinary displayed when running with --debug flag. Just shows loading some xml files.

On a related note, however, Xserver does NOT seem to be running. I am attaching a tar.gz file with all of the build logs, a log of installed packages, and a log of running processes.

Hmm. Can't seem to upload it directly.
Link to files on my Google drive: https://drive.google.com/file/d/1ro_ZYzHFcI6TfbSUjzsLksvwf6rc9vMy/view?usp=sharing

mitu

@aaronouthier said in Odroid XU4 SDL Problem Emulationstation:

I tried with --debug flag, however the screen is cleared by the crash dialog that comes up, so I can't read. I'll try tee'ing it to a text file.

That would have been useful to look, the other logs not so much. You can find the same log file in $HOME/.emulationstation/es_log.txt, there's no need to tee it.
Does detection works better on 22.04 - is the SBC detected as odroid-xu ?

aaronouthier

@mitu

I checked those logs. 3 lines about mame-related .xml files.

No, still detects as "Armv7l". I used your workaround when I ran RetroPie-Setup.

I mentioned twice now that XWindows doesn't seem to be running. Very few X-related packages installed as well. This might be normal, but I don't have a frame of reference here. This was the case in 24.04 also.

mitu

@aaronouthier said in Odroid XU4 SDL Problem Emulationstation:

I checked those logs. 3 lines about mame-related .xml files.

Even when running with --debug ? There should be more information printed when debug is enabled.

No, still detects as "Armv7l". I used your workaround when I ran RetroPie-Setup.

I added some detection here, but it may not be enough (?) or you're using an earlier commit.

I mentioned twice now that XWindows doesn't seem to be running.

I think that's ok.

aaronouthier

@mitu

Even when running with --debug ? There should be more information printed when debug is enabled.

There might have been another line or two. I'm not in front of the system right now. Yes, with --debug. My point was that no errors were displayed.

I added some detection here, but it may not be enough (?) or you're using an earlier commit.

Probably hadn't pulled the latest commit then. This was 2 days ago.

I created an image file from the SD card, then tried to install Lakka just to test that out. That one doesn't boot at all, but hey, I tried. I haven't taken the time to restore the RetroPie Disk image just yet.