Posts by chewitt

avl-demod-support please check your email inbox. It's nice to see you here.

I still have some issues to solve before I send a PR to bump to Linux 5.5; and until this master is still using a 5.3 kernel which doesn't have the GT-King device-tree included. I believe Oleg's images will have it, as he mostly tracks my sources.

I forked the driver at the last "GPLv2" commit before Arther bumped it to GPLv3 to avoid using a kernel driver that is not license compatible with the GPLv2 (only) kernel, but in reality this is irrelevant because the code he started from was not license marked. To change the license (or state one) he needs permission from the original author and since this person isn't known .. he doesn't have permission.

Andreas Faerber posted the following series to the LKML and I hope this provides an upstream, GPLv2, less hacky alternative:

Linux ARM Kernel Architecture - Patchwork

Quote from crazyturk

balbes150 versions Beelink King Pro works well but the remote control is unstable.

The night versions did not work.Can you export dtb file for Beelink King Pro in overnight versions?

I am sory for my english.

kodi: add patch for Beelink wireless remote · chewitt/LibreELEC.tv@bc52c92 · GitHub <= check this file is modified like this in the image (not sure if Oleg has this patch applied .. just search for peripherals.xml). IIRC you also need to disable mouse mode on the remote (top-left button if I remember correctly) else navigation goes crazy. The behaviour is all in the input subsystem, it has nothing to do with device-tree.

echo "options cfg80211 ieee80211_regdom=GB” > /storage/.config/modprobe.d/cfg80211.conf

^ run this command from the (now available) SSH console and you'll be able to see all channels correctly. Change "GB" for your local ISO country code, e.g. DE, FR, ES, RU, CN, etc.

User provided firmware needs to go into /storage/firmware/<filename> which will overlay files (and any dirs created) to /usr/lib/firmware on reboot.

Quote from ramoncio

Am I doing something wrong? Maybe missing something?

Any ideas how can I get a LE kernel able to boot from the git repos sources?

I've honestly no idea. I'm able to boot the images created from my repo

Quote from steved

balbes150 I just installed image 20200108 on my VIM2 Pro, installation and everything works fine, but video playback only shows a green screen. I guess its the video acceleration.

Currently I test this with an RTSP stream over IPTV Simple Client. The log says the following Log

Even though the 'InputStream Client for RTMP Streams' is installed, is says ' unsupported protocol(RTSP)'.

The green screen problem and the log message might be unrelated, since local media files won't work neither.

Is this already a known problem?

You probably need to disable hardware acceleration to solve the green screen. Video is currently rather broken until ffmpeg and Kodi changes catch up with recent API compliance changes to the hardware decode driver.

[le92] tz: update to 2019c by HiassofT · Pull Request #4105 · LibreELEC/LibreELEC.tv · GitHub is merged and will be picked up in the next Leia bump (although there is no schedule on that).

It's mostly being discussed between Pi Foundation and LE developers in our private chat, with some overspill into the Pi Foundation GitHub repo when bits of plumbing are added there and other external people notice.

It's a simple-sounding idea until you attempt to programattically define what "idle" means in an environment where the OS and Kodi are constantly doing something. It's a non-trivial thing to do.

What's the model name of the MacBook? .. and what GPU does it actually contain?

balbes150 publishes some images that are mostly based on my upstream sources. I don't publish images myself.

From a networking perspective LE is functionally no different to any other Linux OS. You can use the settings add-on (or connmanctl from the console) to give the device a static IP address (switch from auto to manual config and set one). If you need to 'name' things /storage/.config/hosts.conf acts the same as /etc/hosts.

Fixed IP = Static IP .. instead of DHCP

Quote from ramoncio

Thank you! I'll try that later today.

Any hints about the compile process? Was my last build command with the "box" u-boot OK? Do I need to dd the u-boot to the disk and copy the u-boot.usb to the fat partition or that should be already included in the image?

"PROJECT=Amlogic DEVICE=AMLG12 ARCH=arm UBOOT_SYSTEM=box make image" should give you something that most boxes will boot via one of the usual reset methods. The X96max dtb is another S905X2 device, although some are 1000-BaseT and others 100-BaseT so it's not exact.

LE master branch is still on Linux 5.3 and I'm not sure what state the nightly images are in .. but doesn't sound good. I'm working on a bump to Linux 5.5 but that still has some unresolved issues on older hardware and some weeks to run before I push a PR to GitHub - the amlogic-master branch in my git repo has current changes if you want to self build something. Once that bump goes in nightlies should be in good again; although pending the ffmpeg and Kodi changes needed for hardware decode (work on that hopefully starts next week).