Posts by roel

Quote from Demetris

Found that hdmi port was my issue, i will resolder the pins and continue
Edit:Fixed!
roel
only thing left to push is a kodi upgrade

Sorry, I was talking about the Lakka sources. Are these up to date an github?

Edit: Nevermind, found them here: GitHub - libretro/Lakka-LibreELEC: Lakka is a lightweight Linux distribution that transforms a small computer into a full blown game console.
I see You named the labels to LAKKA and LAKKA_DISK, assuming you are Ntemis. Big thanks for that, I'm already downloading.

Demetris,

can I build from your sources on github or do You still need to push updated sources to github?

Quote from Demetris

I have some bad news. My S802 has some issues with outputing video out from hdmi. So now am left with a bootable device with no video out and looks like is a hardware issue.

Did it overheat? According me, these boxes need extra cooling if you use it to play games. My OPI-one with self made passive cooler stay's around 40° when playing games with Lakka.

Can you still ssh into the device?

Demetris,

is it possible to change your FAT_VOL_ID in the mkimage script for Lakka to LAKKA and ad EXT_VOL_ID and label it to disk and add it to the tune2fs command when creating partition 2?

FAT_VOLUME_LABEL="LAKKA"
EXT_VOLUME_LABEL="DISK"

&

# create filesystem on part2
echo "image: creating filesystem on part2..."
mke2fs -F -q -t ext4 -m 0 "$OE_TMP/part2.ext4"
tune2fs -L "$EXT_VOL_LABEL" -U $UUID_STORAGE "$OE_TMP/part2.ext4" >"$SAVE_ERROR" 2>&1 show_error
e2fsck -n "$OE_TMP/part2.ext4" >"$SAVE_ERROR" 2>&1 show_error
sync

If it is not possible, then I will buid it myself with these changes, so I can run it from SD-card. But I think it's interesting for others also to run from SD.

BTW, or You still on openelec or is it already along time ago You updated your sources on github?

Thanks

OP = Original post, so first post that you see on page 1 of this thread: thread-2877.html

Quote from balbes150

1. DVD previously worked ?
2. What version of LE you are trying to play a DVD ?
3. What media runs LE (SD or USB or eMMC) ?

1) I tried different DVD's. They worked previously. Strang thing is: I don't get the 'play dvd' on the menu, but it mounts in videos -> files. You know with the video_ts dir.
2) 7.0.3 lan 1000 with your modified kernel.
3) Did run it from SD, maybe the SD is to slow to handle that? I used a 8gig sandisk extreme pro UHS-1

Balbes,

I tested your build with new kernel configuration and everything on my Eny M8S seems to work. I also can see bleutooth devices altough I didn't try to pair them.
What I noticed is that it doesn't play dvd from my external dvd-rom. It mounts the DVD but if I try to play them it says "working" and the system hangs until you remove the dvd from the tray.

Quote from 4timepi

So download *.img > raw write to SD, insert into BOX and it should boot and extroot from SD/USB?

I will try the new image from Demetris this evening, if they are ready and if it works I will explain you how to do it. Which device do You have? Is it already multiboot enabled?

Quote from Demetris

Wait until i get my hands on an s812 device, images now are specific for s802

Demetris,

the fault was in the s805_autoscript as it searches for a disk with label BOOT, your label=LAKKA. I changed BOOT in the s805_autoscript to LAKKA, but then it complaint about the 2nd partition that should be labeled DISK. Your second partition isn't labeled. I don't know how it can be done otherwise in the s805_autoscript.
Is it possible to adjust your image so the 2nd partition label is labeled DISK? When I change it with e2label, it corrupts the partition.
Or if somebody knows what to change in the s805_autoscript to identify the 2nd partition on the sd card?

Quote from tomas_em

Hi,

which tool you use to burn the image to the MX III box? I tried latest Libreelec 7.03 and 8.0RC1 buils as well as LakkaTV for S82 and when I try to open those images in the Amlogc USB burning tool I get the error message "Parse burning iamge fail". The official IMG from Beelink and Tronsmart loads and burns OK.

Tomas

"I removed my answer, did misunderstood the question as I never use Amlogic Burning Tool. Maybe a moderator can remove this post."

Demetris,

your build doesn' boot om my M8S (S812). I see the Lakka screen and then it says something like: never touch boot on

It's possible because I tried to boot from sd with the S805-autoscript from balbes.

Thanks anyway!

Hello Balbes,

your latest build works like a charm from sd on my ENY M8S. It's the first build that works from sd for my ENY. Wifi and wired ethernet works. Didn't test bluetooth though.
Your image is really nicely build. Didn't test any videos yet. Maybe this evening I will try your image with the new kernel.

dankec,

if you still follow this thread, you should test this build from sd. The previous builds from Balbes didn't work for me. I had the blinking amlogic logo. This works. Just do the toothpick method. As before the amlogic logo will start blinking again. Pull out the power, leave your sd-card in the M8S and put the power back in. My device now started booting from the sd card. BTW - I used the lan 1000 image and everything works, also on a regular M8S.

Try with the sd-card version from Balbes. It won't hurt.

Quote from Demetris

S802 is way more powerful than S805 but to unlock the full potentials you must try our Lakka.tv image you will be amazed how fluid you can play e.g N64 at 1080p

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

Demetris,

Do you have a link to the lakka builds. Is there a build for the MK808B+ also? I already tried to merge the lakka source with the openelec sources for the mk808b+ without succes.
I think the problem is I'm building on Arch Linux. I got now errors while building gcc. I don't know what it else can be. The recipe downloads gcc and starts building and gives an error that it expected a space somewhere in the defaults.h file.
I will try this evening on Ubuntu 16.04.

Demetris

Thanks for the suggestion, but I will try until it works. It should be good I can compile the base system and starting from there to ad my own wishes to the system and not to rely on somebody else to do it.
I'm so glad with the foundation of the LibreELEC community and the fact they are possitive to community builds I prefer to show them the respect to try it myself so if I ask a question I can do it in a more 'to the point' way. So they have more time making LibreELEC better, and in our case helping mainline the amlogic kernel.

Quote from DoritosVodka

I've been doing S802 M8 builds for a couple of months now. First started using drieschel's and surkovalex's source as a starting point. But, moved my last 2 builds to a fork of kszaq's source...

I was trying also to combine surkovalex's and kszaq's sources to build LibreElec for my eny M8S, because kszaq's build for the MK808B+ is a lot better then the build for the M8S from amlinux.ru. But I don't manage to build an image, everytime I fixed an error I get a new error. It takes a lot of time to go through all the scripts and files to find the cause of the error. I have a lot of appreciation for the guys that manage to build it for new platforms and even more for those that fix stuff and try to improve the kernel for those specific platforms so others can enjoy it.

Regarding the power on/off issue. My remote works to turn it on and off again

In my remote.conf, found in /etc/amremote, the power is binded to 0x40 116. Altough I'm not sure this is the remote conf it uses, but I don't find another one.

For the rest, I don't use the the powercable but power it throug USB with such a splitted USB cable to power a external harddrive through 2 usb ports.
Lik this one:

Amazon.com: StarTech.com USB2HABMY3 3 Feet USB Y Cable for External Hard Drive - USB A to mini B: Computers & Accessories

Quote from dankec

Just FYI, drakulaboy, I tried with your remote.conf, remote is not working at all, of course.
But I found another remote.conf for M8S. This one's working, also shows a small menu when choosing power key, but still cannot power on after power off.

It means it's not remote.conf related, the problem is somewhere else...

I had the same problem if I remember. I fixed it by powering the box through one of the usb-ports. Altough I didn't try to fix it that way, but since I do it this way I don't have the problem anymore. I just started doiing that because I use a powered usb-hdd.

BTW, I had to switch the hardware acceleration to 'always' instead of ' 720p and up', cause I had a lot of stuttering while playing mkv's made with makemkv.