Posts by chewitt

Nothing known or done on our side. Must be general internet wobbles in the ether.

Amlogic technical direction with their latest chips (S4, T7, etc.) is not friendly towards open source and basically forces distros to use vendor u-boot and vendor kernel sources. That's the opposite of LE technical direction so even when it's technically possible to boot things I'm not sure we'll invest time/effort in supporting them. TL/DR; don't hold breath and ask me again this time next year to see if anything changed.

Correct, it has initial support under Windows. K20 will add some improvements under Windows and hopefully initial support under Linux.

Install. Finish the setup wizard. Go to LE settings and update the RPi firmware(s). Avoid restoring backups from LE 9.x as these will restore Python2 add-ons that often cause issues (hence all the "clean install" advice for LE10). If you really need/want to restore things do a manual unpack of the .tar backup file and then manually restore only the bits you really need.

LE has no support for S905W2 chips at the current time, and since this is an all-new SoC type any future LE support will depend on Amlogic upstreaming lots of new drivers. I have low expectations we will support these chips anytime soon. NB: These boxes are built to run Android. Kodi runs on Android too; so I suggest you use it that way.

Kodi 19 does not support HDR, hence LE10 does not either. You need to use a Kodi 20 (LE11) development build.

Have a look at LE-9.2.8 builds for some Amlogic S905x, S802/S812 and S805 devices

dtech ^

Connect a UART cable to the board and share the early boot output.

Those commands only work on the LE11 image.

La langue de notre forum est Anglais, desolé.

1. First option sets global default NTP servers, and second sets connection specific servers that override the defaults when the connection is the active one. 2. Forces a startup delay in the LE boot process for X seconds; the second (in Kodi settings, not LE) has something to do with power and likely doesn't have any effect on LE since most HTPC devices (RPi4 is a good example) lack power management hardware.

WP2:~ # echo 0 > /sys/devices/platform/leds/leds/blue:power/brightness 
WP2:~ # echo 1 > /sys/devices/platform/leds/leds/blue:power/brightness 

^ the first command (0) turns the BLUE power LED off, but the underlying firmware (which we have no control over) switches the LED to RED. It can be reversed with (1). It's a good example for why it's hard to have a consistent feature in the settings GUI. Put some black electrical tape over the LED and it can be silenced.

For boot, I never understood why users are so obsessed with running from eMMC. I run an WP2 from a decent SD card (with mainline u-boot, as I wiped the emmc clean) and this works nicely. An RPi4 will be better overall, but for it's age the WP2 is still surprisingly useable.

Note that LE11 is functionally behind old vendor kernel images (no DVB tuners, no deinterlace etc.) .. there are few developers working on media drivers so progress is a bit slow.

systemctl stop kodi
mv /storage/.kodi /storage/.kodi-old
touch /storage/.update/.nocompat
reboot

^ after downloading the update file to /storage/.update .. this just moves the old Kodi install out of the way so that add-on issues don't cause issues as part of the update. Kodi will start in the new version with a clean environment, and then you can stop-kodi/move/restart-kodi to put back the essential bits you really need.

hkall that's nice work .. I see some bits already hit the mailing list

A1: Probably not, because there is zero consistency on LED naming over a wide range of devices and to script that feature you need something that can be consistently targetted.

A2: No, because in the past there were WeTek full-time paid staff hanging around to deal with their low-skill customers and the regular supply of support issues that came from that feature. These days it's mostly just me, and I have very limited enthusiasm for that kind of self-inflicted punishment. One of these days we'll figure out how to make mainline u-boot coexist with FAT partitions; then I'm fine to support an internal install on WP2 again.

Thanks to a side conversation while axe-throwing and drinking beer at Kodi DevCon a couple of weeks ago the latest images in my share now have a proper kernel-level workaround for the alsa speaker placement issue when using multi-channel PCM audio. The alsa channel map can now be detected/read by Kodi on the correct PCM device so magic works and audio comes out of correct speakers. It's a workaround not a proper fix (which requires some non-trivial alsa changes and more knowledge) but an improvement is an improvement. Happy Easter

Just keep an older RPi 2/3 board around for occasional 3D use. It's probably not impossible to make an LE 9.2 image with support for newer hardware but all time spent on making/testing something that ultimately few people will use is just a distraction from LE11 and encourages people to remain on LE 9.2 (when we'd generally like them to be on newer things) so I don't see staff making the effort. It's all open-source though so nothing to stop "the community" making the effort.

You can borrow someone else's computer for 5 minutes, or depending on what you want to install to, perhaps use a USB stick?