Can’t built emulationstation

mitu

@E3L1 It seems lsb-release is not working without lsb-core, try installing that package also.

E3L1

root@tinkerboard:~# sudo apt install lsb-coreReading package lists... Done
Building dependency tree       
Reading state information... Done
Package lsb-core is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'lsb-core' has no installation candidate
root@tinkerboard:~#

E3L1

@mitu so got emulation station installed by using the instructions from emulation stations website, it still says it fails to install when running the basic install but then in the package manager it says it is, but when I run “emulationstation” all I get is

lv10:     Error initializing SDL!
               No available video device
lv10:     Renderer failed to initialize!
lv10:     Window failed to initialize!

Clyde

@E3L1 Is this still the Armbian you used in your former thread? It seems that lsb-release doesn't work on Armbian. This question on Stackexchange got an answer suggesting cat /etc/armbian-release instead.

But if ES' building script needs the output of lsb-release, the question is if it can be (easily) modified to use the Armbian way to display the release information.

edit: You may be able to determine the Debian release it's based on by looking at the file /etc/apt/sources.list and see which Debian repository it uses.

E3L1

@Clyde I know exactly what Debian it’s based on
Debian Buster minimal kernel 4.19.y
Also from doing some VERY in depth research it would seem at this point to be ES, actually got it running without retropie but there seems to be major issues like having to use the minimal desktop environment as the GUI maker that retropi (and even the non minimal desktop) have conflicting package version.... and even then there where major issues with things like frame times, response time, any graphics being broken, controller configuration be bugged (had to set it via config file) and so on.... does make me wonder how that one project that one guys was making even functioned back then (doesn’t now by the way... that’s why im doing all this, the newer packages DO NOT WORK to the point of braking the network manager and video...)

Also never could figure out that strange audio bug it had... literally ever other audio source did not work.... nor could anyone else.... including a Linux engineer friend I have...

E3L1

@Clyde also;

https://www.armbian.com/tinkerboard/

Wish I could try Jesse but the board is to new, it never had Jesse... and because asus was a mean pickle.... you can’t just install any old OS on the tinkerboard either...

Clyde

Seems like the tinkerboard is a very hard nut to crack. It makes one wonder if it's worth the time to try anyway … although I can understand the motivation to solve a puzzle like this absolutely.

E3L1

@Clyde it’s more.... why can’t raspberrypi release a SBC with a GPU faster that 300mhz..... the entire reason for me getting the tinkerboard is that it’s GPU is 700mhz, is the same form factor as the pi, and can (or should I say could) fully play the N64...

E3L1

@Clyde I have discovered something interesting, when trying to install as if it was an odroid xu4, found this in the system.sh file;

    ;;
“Rockchip (Device Tree)”)
    —platform=“tinker”
    ;;

And

function platform_tinker() {
    __default_cflags="-O2 -marm -march=armv7-a -mtune=cortex-a17 -mfpu=neon-vfpv4 $
    # required for mali headers to define GL functions
    __default_cflags+=" -DGL_GLEXT_PROTOTYPES"
    __default_asflags=""
    __default_makeflags="-j2"
    __platform_flags="arm armv7 neon kms gles"
}

So I’m thinking at this point there was at one time support, but via the tinker OS (witch is crud) and it’s just miss recognizing the tinkerboard as something else and installing the wrong versions of things

Clyde

Thanks for the update.

@E3L1 said in Can’t built emulationstation:

@Clyde it’s more.... why can’t raspberrypi release a SBC with a GPU faster that 300mhz.....

Because the Raspberry Pi was never meant to be powerful. It was (and is) developed first and foremost to be an educational device "to promote teaching of basic computer science in schools and in developing countries" (Wikipedia).