Posts by Asxetos

Quote from niabi

Cool, when you get it working please share it (or do a pull request on github) maybe it can help others

Well, i officially need help .

New device MiniMX is in, and i think the following is in no way related to the device changes.
Compile stops at vlc (when compiling the games related group near the end), complains about build.../toochain/bin/luac missing (it's there).
Tried to overcome it by reverting to Alexelec's vlc and lua packages (small modifications made by you), installed lua 5.3 on host, no go.

Just out of curiosity i tried Alexelec's latest release for T95N (with dtb change) and it works fine on my box. Kodi, games and all... Its just a pain to get rid of all the Russian stuff ...

Quote from niabi

if you have those settings for the minimx I can try and compile a version for you.

That's ok, i like to do it and it will take some work.
I also need to change the remote to mine, and add the patch i use for my usb dtb card (remember, old TV).

Thanks for this though...

The card is really fast, it's a Samsung uhs1.

The box boots really fast, just a few seconds to get ssh.

No gui starts, unless i manually start kodi and then the games gui comes to life and they start fighting.

If i manually try to start (like kodi) emulationstation or retroarch by:
"touch /var/lock/start.games" or "touch /var/lock/start.retro" followed by "systemctl start retroarch or emustation"
but before i start kodi, nothing happens. Both games gui's come alive only if kodi is started.

Weird...

PS
I like your approach better because it (can be) more complete.
My guess is (since it works on your end) it is a strange box compatibility problem.
Perhaps it can be fixed if i compile it from scratch using minimx 1gb dtb and settings (add it as a new S905 device).

Quote from niabi

I will check why is doing that, seems very weird, I am using v1.2 right now, but I will download the image and try that one, maybe by mistake I did something wrong.

Now it's getting weird.

I see you have set emulationstation to load in autostart.sh but it doesn't.
After i added a couple of roms and bios, when i manually start kodi gui, at the same time out of the blue the emulationstation gui pops out, and the two gui's are fighting each other.
Plus the emulationstation gui is stretched and i can only see the top left part (about 1/4 i guess) on a 1920x1080 TV.

PS
no change with your dtb (i use gxbb_p200_1G_1Gbit.dtb)

Quote from niabi

you should have gotten your device splash screen surely, right?

If you can try with the dtbs I linked just to make sure it is not that.

Don't worry about the splash screen, i don't get one with LE either (old tv compatibility probably).

But, It takes an unreasonable amount of time ~ >7-8 mins, and finally emulationstation appears on ps output.
after that "touch /var/lock/start.kodi" - "systemctl start kodi" works and gui comes on.

On reboot, again no gui, and "systemctl start kodi" alone does not work, needs "touch /var/lock/start.kodi" every time.
I think this needs fixing. Gui should start automatically.

Will try the games part and report...

Quote from niabi

Did you get a splash screen at all?

No splash screen at all, something with hdmi detection perhaps?

Quote from niabi

systemctl start kodi

Tried it already, no go.

niabi

Just to report,
Tried 1.1 and 1.2 on a MiniMX s905 1gb ram,
Apparently the box boots because i have ssh access, but no picture on TV at all.
I used the dtb.img i use with kzaq's LE8 for my box.

Tried to manually start kodi and retroarch through ssh, nothing.

Any tips?

Guys, how can i add dual boot support (sd boot) on a mxiii-1gb (s802)?

Thanks...

The LibreElec repo for binary addons says "unable to connect".

Is there a fix for it?

Quote from Demetris

Just wait am going to release a new beta4 image soon with updated kernel to latest 3.10.104 LTS from The Linux Kernel Archives and upstream libreelec changes

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk

Demetris, two of the patches in /packages/sysutils/lirc are broken (on beta3 and beta4) in your repo.
I've corrected them locally to be able to compile the source, but i am not 100% sure if its correct.

Check it out, if you think they are ok, i'll upload the beta4 image for the mxiii-1g (it seems to work fine as it is now anyway) ...

patches.zip

Quote from Demetris

M8 build up in OP, enjoy.
Asxetos
File mou ekana update to source code link, sorry eixa to palio
An kaneis compile gia tin syskeyei sou mporeis se parakalo na kaneis upload to image gia na mporoun na to katevasoun kai alloi?
Euxaristo poly.
Translation:I have now updated LE8 source link, didn't noticed i had the old one only, sorry.
Please Asxetos if you compile for your machine could you please upload image so others can try it too?
Thank you very much in advance

Display More

Efharisto file mou, tha to anevaso molis teleiosei.

Thanks my friend, I' ll upload it when done.

Quote from Demetris

roel my source is ready to also build for (MXIII-1G),(M8),(T8) i just need the time and the motivation so if you guys have any request i can do it but bare in mind that updates cant be done so frequently for obvious reasons.

Kalimera Demetris

I also have an MXIII-1G and would like to try Libreelec 8.0,

I more than able to compile it my self if you don't have the time, but the code in your repo looks quite old.

Quote from kszaq

Source code is ready to compile 32-bit userspace only. To compile for aarch64 you need to delete this patch: Python-32bit-usespace-workaround.patch and rename (or copy) linux.arm.conf to linux.aarch64.conf. Remember that the main reason for 32-bit userspace is memory leak that has not been fixed.

You also need to disable SARADC.

It's ready.

Thanks for the help kszaq,
So this is OK? "PROJECT=S905 ARCH=arm make amlpkg"
And do you mean disable this "CONFIG_AM_SARADC" ?

Some questions about compiling from source. What confuses me (among others) is the 32bit userspace vs 64bit cpu.

Would this be ok to compile with 32bit userspace? "PROJECT=S905 ARCH=arm make amlpkg" (and again with ARCH=aarch64 for 64bit userspace?)

Would changing "CONFIG_AML_TEMP_SENSOR" in linux.arm.conf be enough to compile with temp-sensor enabled vs disabled?

Are there any changes necessary to prepare for dual boot support or is the source code ready for SD boot as well as internal nand install?

Just want to familiarize my self with this.
Thanks...

Quote from afl1

Kodi Addons repository for Krypton is still incompleted.

For testing - Addons - pvr compiled by me.

Request;
Please compile the "vdr-addon" service for Krypton.

Thanks...