Posts by roel

balbes150

A new problem showed up. I wanted to update with the tar file, but I got this error: Missing (target) files kernel and /system

I burned the MXIII-plus image on my SD-card and otted the M8S from the sd-card. No problems with resizing the storage partition.

After the first-run items I did following:

- Added my remote.conf to the rc_keymaps folder and adjusted rc_maps.conf to use my remote.

- Did the following command: ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

- No error messages, but remote didn't seem to work.

- ir-keytable -t didn't respond to the keypresses on the remote.

- ir-keytable without flag gave me this result:

LibreELEC-M8S:~ # ir-keytable

Found /sys/class/rc/rc0/ (/dev/input/event0) with:

Driver: rc-loopback, table: rc-empty

lirc device: /dev/lirc0

Supported protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6

Enabled protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6

Name: rc-core loopback device

bus: 6, vendor/product: 0000:0000, version: 0x0001

Repeat delay = 500 ms, repeat period = 125 ms

So it seems meson-ir is not used by the system.

output from lsmod:

LibreELEC-M8S:~ # lsmod

Module Size Used by

hci_uart 41143 1

bluetooth 191493 2 hci_uart

8021q 15927 0

dhd 657022 0

cfg80211 204691 1 dhd

wifi_dummy 737 0

mali 160908 5

Quote from balbes150

Added support for the remote control, but I can not figure out what is the reason that "ir-keytable" does not accept codes from the remote control.

I will look into this, maybe I can figure it out. But I have little time, so it could take some time.

balbes150,

Quote from roel

Didn't test the remote yet, but I don't expect problems with it.

Seems there are some problems. I kill kodi and eventlircd and when I want to activate my own remote.conf, I get this message:

LibreELEC-M8S:~/.config # ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

/sys/class/rc/: No such file or directory

No devices found

Maybe it is indeed missing module meson-ir as stated in the error message of systemd.

This is the output from cat /proc/bus/input/devices:

I: Bus=0010 Vendor=0001 Product=0001 Version=0100

N: Name="aml_keypad"

P: Phys=keypad/input0

S: Sysfs=/devices/platform/meson-remote/input/input3

U: Uniq=

H: Handlers=kbd mouse1 event3

B: PROP=0

B: EV=f

B: KEY=7fffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff fffffffe

B: REL=103

B: ABS=0

I: Bus=0010 Vendor=0001 Product=0001 Version=0100

N: Name="gpio_keypad"

P: Phys=gpio_keypad/input0

S: Sysfs=/devices/platform/gpio_keypad.6/input/input4

U: Uniq=

H: Handlers=kbd event4

B: PROP=0

B: EV=100003

B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0001 Product=0001 Version=0100

N: Name="rn5t618_pmu"

P: Phys=m1kbd/input2

S: Sysfs=/devices/i2c-0/0-0032/rn5t618_pmu.0/input/input5

U: Uniq=

H: Handlers=kbd event5

B: PROP=0

B: EV=7

B: KEY=100000 0 0 0

B: REL=0

It seems also the inputstream-adaptive addon is not installed. I wanted to install it from the libreelec add-ons repository but I get following message: Could not connetct to repository.

balbes150,

I tested all you images for 100Mb network. For your knowledge, I have a Eny M8S with a AP6330 wifi chip. Recently I had some problems with it, but I flashed the android firmware again and now everything is fine again. Seems doiing the toothpick method to much for different AML_AUTOSCRIPTS corrupts uboot after a while...

So I tested all images to boot from sdcard and from usbstick.

The 100M image boots, I had to do a manual resizing of the storage partition because it stuck in the boot on the resizing. It can be it had something to do with my old uboot because after reflashing the android firmware the other firmwares didn't have that problem anymore. Same for the freezing as mentioned in post 737.

Conclusion: this image works OK, including network, wifi and bluetooth.

The image in folder 1: boots but no wifi and bluetooth

The image in folder 2: didn't boot at all, the M8S stuck at the S812 boot logo

The image for the mxIII-plus: Works without glitches on the M8S. Network OK, Wifi OK, Bluetooth OK

The only thing I noticed is that the option in the shutdown menu to install the image to nand doesn't work, and also some systemd message during boot about systemd-modules-load.service:

● systemd-modules-load.service - Load Kernel Modules

Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static;

vendor preset: disabled)

Active: failed (Result: exit-code) since Tue 2018-05-29 18:44:02 UTC; 23min a

go

Docs: man:systemd-modules-load.service(8)

man:modules-load.d(5)

Process: 2291 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, st

atus=1/FAILURE)

Main PID: 2291 (code=exited, status=1/FAILURE)

May 29 18:44:02 LibreELEC systemd[1]: Starting Load Kernel Modules...

May 29 18:44:02 LibreELEC systemd-modules-load[2291]: Failed to find module 'aml

videodri'

May 29 18:44:02 LibreELEC systemd-modules-load[2291]: Failed to find module 'mes

on-ir'

May 29 18:44:02 LibreELEC systemd[1]: systemd-modules-load.service: Main process

exited, code=exited, status=1/FAILURE

May 29 18:44:02 LibreELEC systemd[1]: systemd-modules-load.service: Failed with

result 'exit-code'.

May 29 18:44:02 LibreELEC systemd[1]: Failed to start Load Kernel Modules.

I will continue with the MXIII-plus image. Didn't test the remote yet, but I don't expect problems with it.

doggyofone

It's as I already told balbes in post 737: the .please_resize_me file could not be deleted. It's easy to fix if you have a linux pc. Just put the usb stick or sdcard in your linux pc. Go to the storage partition of your usb stick or sdcard and remove the file .please_resize_me as root (or with sudo in the terminal). After you done this, You can use gparted to expand the storage partition.

I don't think it is possible on a windows pc as windows doesnt support the ext4 filesystem. But actualy, I don't know as I'm not a windows user.

If you don't understand the above howto, wait for a next image of Balbes150 where he fixed the permissions of the storage partition. -> just noticed it could be a uboot problem also, as a reflashed my android firmware and started again with the toothpick method to activate multiboot. After I did this the resize problem was gone.

balbes150

I tried your Leia version for the 100Mb network. Following things I noticed:

1) It keeps on rebooting because it can't delete the file .please_resize_me, after manualy deleting this file as root and expanding the filesystem myself I was able to boot.

2) When in Kodi after a few seconds it freezes, sometimes kodi restarts itself another time I had to pull the plug.

3) The script "install to internal" doesn't seem to work, or there is something wrong with uboot of my M8S.

I see on the download page there is a folder for the 100Mb network with two folders, both with an image. What is the difference between all the 100Mb images. I used the one from the front page.

Quote from Gregoir3

I'd like to add that from Coreelec 8.90.1 onwards "longpress" is supported but you have to switch from remote.xml to keyboard.xml for it to work.

Do you mean you have to create a different file for keyboard buttons? I thought it was specified in the format of the file for example <keymap><global><keyboard> and for remote it is for example <keymap><global><remote>. As I understood, with the ir-keytable method all button presses where interpreted as keyboard inputs. Or am I wrong?

Quote from balbes150

The good news is Martin is gradually adding support for the s812 to the kernel mainline. Now you can use s812 as a server (there is no HDMI output yet).

Nice to hear the mainline kernel for the S812 is also getting shape. Your armbian build made me dust of my M8S. Now I have to find the proper DTB. Hopefully HDMI will be functional soon.

balbes150,

do you use the same approach as the libre-computer-project: Mali Opengl on the libretech cc s905x using GBM with LibreELEC Kodi · libre-computer-project/libretech-linux Wiki · GitHub

Would be nice to test on the Khadas VIM.

Quote from Raybuntu

KONAMI code

I did the KONAMI code and I have the game menu. Probably my mistake is that I did a upgrade from libreelec 8. I better do a complete new install.

Doesn't work, it seems kodi doesn't see it's a game. It want's to play the file (like a movie) not launch it. I will enable the log and see what is goiing wrong.

I will try the snes9x versions this evening. Is there a way to choose which emulator to choose or do you have to enable/disable the addons first?

I tried it on coreelec, but when I want to launch a game, the systems freezes and after a while it goes back to the kodi home screen. Did only try with snes games and beetle-snes.( -> from de corelec games addons not the ones from raybuntu)

What I think is strange is that You can't choose which emulator to use, for example f you installed 2 snes emulators.

Quote from Demetris

Guys just wait for my new 8.2.3 image i think i fixed the sdcard issue once and for all

Demetris,

can You implemnt it on you Lakka builds also. For some reason I can't boot the latest 2.1 version on my M8S. It hangs on the bootscreen (flower).

Balbes,

your 21/12 build works OK, does even boot from sd. No corrupted file system error.

Regarding the systemd errors on startup, according me these are modules that systemd wants to load, but probably, you integrated them in the kernel and didn't compile them as modules.

You can see which error it is when ssh'ing into the box an run following command: systemctl status systemd-modules-load.service

On my box this is the result:

-> systemd-module-load.service:

Sep 29 10:17:51 LibreELEC systemd[1]: Starting Load Kernel Modules...

Sep 29 10:17:51 LibreELEC systemd-modules-load[2196]: Failed to find module 'aml

videodri'

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Main process

exited, code=exited, status=1/FAILURE

Sep 29 10:17:51 LibreELEC systemd[1]: Failed to start Load Kernel Modules.

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Unit entered

failed state.

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Failed with

result 'exit-code'.

and

->kodi-aml-hdmimonitor.service:

Sep 30 11:34:59 LibreELEC systemd[1]: Started Kodi Amlogic HDMI connection monit

or.

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Main process

exited, code=exited, status=1/FAILURE

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Unit entered

failed state.

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Failed with

result 'exit-code'.

balbes150

2 systemd error messages:

-> systemd-module-load.service:

Sep 29 10:17:51 LibreELEC systemd[1]: Starting Load Kernel Modules...

Sep 29 10:17:51 LibreELEC systemd-modules-load[2196]: Failed to find module 'aml

videodri'

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Main process

exited, code=exited, status=1/FAILURE

Sep 29 10:17:51 LibreELEC systemd[1]: Failed to start Load Kernel Modules.

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Unit entered

failed state.

Sep 29 10:17:51 LibreELEC systemd[1]: systemd-modules-load.service: Failed with

result 'exit-code'.

and

->kodi-aml-hdmimonitor.service:

Sep 30 11:34:59 LibreELEC systemd[1]: Started Kodi Amlogic HDMI connection monit

or.

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Main process

exited, code=exited, status=1/FAILURE

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Unit entered

failed state.

Sep 30 11:34:59 LibreELEC systemd[1]: kodi-aml-hdmimonitor.service: Failed with

result 'exit-code'.

Quote from kodiuser1

My issue is that I can power the box off from the remote but not back on. The only way I can power back on is by pulling the power cord from the back of the the box and reinserting to reset the box. I can then press the power button on the box to power it back on.

Same problem here, I have to pull out the power and back in before it starts. Didn't had this problem before.