Posts by sailorpito

Quote from blackride

I changed file extlinux.conf:

Code

LABEL LibreELEC
  LINUX /KERNEL
  FDT /meson-gxbb-odroidc2.dtb
  APPEND boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0

And get the same error where "/dev/mmcblk0p1" is written instead of "LABEL=LIBREELEC".

I can say with certainty that older the official nightly builds of LE10 worked on my C2 (the only thing that worked slowly was the KODI interface). And then in the last nightly official builds of LE10 I got this error. This error is apparently due to the fact that support has been added for booting from a USB flash drive. I have not tried to write to a USB flash drive your builds, but I tried to write a USB flash drive on the latest official night builds of LE10 - if a microsd card is inserted, which also contains the LE10 build and a flash drive, then Odroid C2 is loaded from the USB flash drive. I can try it on your build and I'm sure it will work. But I want to use only a microsd card.

I have another idea. But I think that it will not give anything. Install the official LE9 on the microsd card, run it to create a full size STORAGE. And then replace on it all the contents (files) of the LIBREELEC section from your LE10 build. Don't work, when you turn on the odroid C2, the blue LED is constantly on and nothing else.

Is it possible from your side to write step-by-step commands to start loading LE10 using the connected keyboard to the Odroid C2, when such an error appears?

I tried to write the microsd card via Creator LibreELEC USB-SD, balenaEtcher in windows 10. And even started opensuse in live mode and writing the microsd card via dd (I previously unpacked img from img.gz). And I still get the same error.

Could you do 2 things for me ?:

1. View the revision of the release on the board odroid c2.

2. Via Gparted, reduce section STORAGE on your microsd card (if you have a large microsd card) and make a full dump microsd card via dd and upload img dump to some file hosting (yandex, google disk or another).

Display More

I've only successfully booted my Minix U1 using Samsung EVO sdcard, check attached image. The other sdcards just simply won't boot.

Quote from chewitt

sailorpito update with LibreELEC-AMLGX.arm-10.0.0.tar and audio should appear? share dmesg again pls.

Great, HDMI audio is now working with MINIX-NEO Analog node!

I'll do some more testing and report back.

Here it is dmesg log:

Donation on the way, thank you

Here you go:

kodi.log:

dmesg.log:

Enjoy the rest of your vacation, thanks again!

Quote from chewitt

sailorpito It looks like there are no sound/audio nodes in the current device-tree which explains why there is no audio devices showing up. I can look into adding them in a couple of days once I return from vacation. If you can pastebin the contents of dmesg and Kodi debug logs it would be useful.. ISTR the current device-tree was a blind guess so it will be useful to validate what other bits are showing or not.

First of all many thanks for your work.

I've successfully booted LibreELEC-AMLGX.arm-10.0.0-box.img.gz on my minix neo u1 (S905), everything seems ok but HDMI audio doesn't work (already tried to change fixed sample rate limit to 44.1KHz in kodi settings). I don't know if this is expected or if you need any logs

Quote from chewitt

erbas the main influence is the ffmpeg changes the Raspberry Pi foundation devs have been doing on stateful V4L2 support. I'm tracking the work but beyond a point in mid-December the changes to ffmpeg need corresponding changes in the vdec drvier and this is beyond my non-coding abilities to do .. and since nobody else works on this we're stalled and unable to keep up. H264 is now working well on Pi hardware.

I'm also using updated firmware, but updated is not always better since Amlogic does not backwards test on older hardware they no longer support so change that fix e.g. GXL may also regress GXBB, and testing that is a hugely time intesive task (and work is busy).

In other news, I now have mainline u-boot booting a WP2 (GXBB) box from SD card (after erasing vendor u-boot from emmc) and have been using it as the family daily-driver for the last week. I'm currently trying to understand why audio must be forced to 44.1KHz to get audio output while the same kernel image on a GXL/GXM device is fine. However I'm at the limits of my non-coding-developer knowledge so progress comes only from guesswork and trial/error testing which is time consuming.

For the wider audience: I added a Minix Neo U9-H (S912) device tree to the "box" image based on educated guesswork and the vendor kernel device tree. It would be nice if someone with that box could test it and give feedback.