Nice work. I only have a small problem since I updated to krypton. I have a dvd/hdd combo like this one -> USB Portable DVD/CD Writer and HDD All-In-One Combo
But when there is a cd in the tray, the hdd doesn't mount anymore. Strange as it wasn't a problem on Jarvis. I got to investigate it further, maybe it's a hardware problem that occured on the same time I upgraded to Krypton.
Indeed on the 2 latest builds (also MXIII-plus) the libreelec splash screen is gone. I get a "no signal" message on the screen. But libreelec works. Wait a little bit and suddenly the kodi screen appears. I had the same issue yesterday and downgraded again to the 14/06 build.
Yeah, these M8S devices are funny things. On mine the LibreElec-S812.M8S version does work but no lan and no wifi. The lan.100 version gets stuck on boot. The lan.1000 version did work, with lan and wifi, but now I have the corrupted filesystem error. So I tried the MXIII_PLUS image and this one boots fine and everything works, theonly thing I had to do is add my remote.config to the LIBREELEC partition on the sd-card.
When you try to boot from usb, do you put your stick in the usb port closest to hdmi port? You are sure you used the toothpick method with balbes images and not the one from Demetris? Although it shouldn't be a problem, cause the image from Demetris searches for a kernel.img and the one from Balbes searches for a S805_autoscript. So Balbes images should work on a 'Demetris-system'.
I checked you picture. It isn't the same board, mine is labeled M9&M8_V1.0 2014/07/07, it's almost 3 years old, time fly.
Could you boot your ENY M8S box and install LE to an SDcard or USB stick ?
Can you give more details about the exact image you have used and the boot/install procedure ?
I booted from SD. It was the image LibreELEC-S812.MXIII_Plus.arm-17.3_20170614.img.gz
I burned the image to SD with etcher.
My m8s is multiboot enabled. So I just put in the sd-card and power on the device. Since the last lan1000 images I had the "filesystem corruption" error, but with the MXIII-plus image everything works fine. Didn't test it very well though, but remote, wifi and lan works OK.
Have you tried to use the image MXIII_Plus ?
Balbes tested yesterday your latest MXIII_Plus image on my ENY M8S and it works like a charm (never thought to try de MXIII-plus version). No corrupted filesystem message, LAN and WIFI works great and it's fast also. So for the moment, nothing to complain.
Hello,
is it possible to configure pulseaudio to support network streaming without avahi/zeroconf? I want to stream the sound from pulseaudio to my widora neo (openwrt). As the pulseaudio package from openwrt doesn't support avahi/zeroconf I want to do it by editing default.pa. I tried to copy the default.pa to /storage/.config pulse-daemon.conf.d. Maybe it soes work like that, but i'm not able to select this sound output in settings->system->audio.
Maybe somebody already managed to do it?
it will not boot from SD card says filesystem corruption has been detected
Same problem here with Balbes latest builds for LAN1000. Since the builds after 20170418 they don't boot anymore from SD-card. Even if you do a upgrade with a tar file you get the error mesage after the update. Very strange. I use a real samsung sd-card and it boot's the old images just fine.
Is there something changed in the compilation of your versions since your 20170414 builds. Those I can write happily to sd-card and boot from is. With the newer versions 20170418 and 20170513 I get the corrupted file system error. I thought to be smart and update the 20170414 build wit the update tar of 20170513, but guess what ... when rebooting i got the corrupted file ssytem error again. Didn't try form usb, but as it worked with the older versions I wonder why not with the newer versions.
Thanks a lot Balbes, I really appreciate your work. As your LibreElec runs fine on my Eny M8S, I don't really need the testing, but I definitely will try you armbian version.
My recovery firmware comes from the ENY site (search for EM8S): EM8-M8C and M8S Amlgoic S812 Support Firmware-Android TV Box , Android TV Sitck,Google TV Box, Google TV Stick, China Manufacturer Supplier
This is the content of my remote.conf (copy and paste it in a text file and rename it to remote.conf):
# ZAP-A10 NEC remote
factory_code = 0xfe010001
work_mode = 0
repeat_enable = 1
release_delay = 121
debug_enable = 1
reg_control = 0xfbe40
key_begin
0x4e 2 ;NUM_1
0x0d 3 ;NUM_2
0x0c 4 ;NUM_3
0x4a 5 ;NUM_4
0x09 6 ;NUM_5
0x08 7 ;NUM_6
0x46 8 ;NUM_7
0x05 9 ;NUM_8
0x04 10 ;NUM_9
0x01 11 ;NUM_0
0x42 111 ;DEL
0x51 105 ;LEFT
0x16 103 ;UP
0x50 106 ;RIGHT
0x1a 108 ;DOWN
0x13 28 ;OK
0x10 74 ;VOL-
0x41 66 ;MUTE
0x11 172 ;HOME
0x4c 46 ;MENU
0x18 78 ;VOL+
0x19 14 ;EXIT
0x40 116 ;POWER
0x5a 119
0x59 122
0x52 128
0x58 123
0x54 120
0x55 121
0x45 130
0x49 134
0x0a 133
0x48 138
0x4d 70
0x0e 136
0x0f 135
0x43 132
0x03 127
0x06 139
0x44 140
0x00 63
key_end
My M8S seems ENY's M8S 2GB/8GB. I try Libreelec 8.0 I could install and works. But remote couldn't work only I can use for power off.
And problem with reboot, I had to re plug always. I think it's dtb problem where can I found my device tree?6330 ap+2GB/8GB+10/100 Fastethernet version
Thank you so much your great job! balbes150
I'm running Balbes latest lan1000 version on my ENY M8S just fine. No problems with the remote or power on/off. I will post my remote.conf this evening.
I just unpacked the tar. inside are three folders (3rdparty, Licenses and target) Inside the target are the files that you referenced to. In addition are Change log, Readme.md and Release. So to be clear the only file that are needed are those in the target and should be to be copy into Userfolder>update of the Libreelec.
Indeed only the kernel and system files should be copied to the update folder of libreelec.
Probably he tried it with the aml_autoscript so now it is booting from SD as it sees a kernel.img. Try it with copying the unextracted zip to the sd-card and boot the device with the toothpick method with the SD-card in the SD slot.
BTW, Did you login as root through ssh
@ Balbes, I just tried this image on Tronsmart S82, using the tar file, in the process of updating the file stopped, error the hardware for 802 is not compatible with 812.Thanks
You have to unpack the tar file and copy the files from the target folder to the update folder of your libreelec device. Files are kernel.img, kernel.md5, system.img and system.md5. Should work for updating without the error.
Hello,
a few years ago, always-innovating had the option to dual boot on their touchbook. I wonder if it could also be done, for example 2 different versions of LibreElec or Lakka and LibreElec or Ubuntu and LibreElec. Maybe it's possible to do it on a SD-card and with a s805_autoscript?
Here is the link to sources from always-innovating:
git.alwaysinnovating.com Git - ai.tools/tree - ai-launcher/
Burn the image on a usb stick and boot from usb.
Thanks for that, I found the platform_ini on your github page. I will recompile with these settings.
-> Where do you learn these things?
