Posts by chewitt

Quote from rigowetekplay2

figured by writing the wetek play 2 img.gz on the stick instead of the box version. what i suspect is that the box thought that the sdcard contains the exact same system, why would i boot from sdcard. but that doesn't sound very real.. anyway this way i could boot from sdcard, could wget the correct img file, and could run emmctool w libreelec11.img.gz and it's all good now.

That sounds like the wrong way around. Android (vendor) u-boot will not boot the WP2 image as it doesn't understand any of the extlinux boot files. If you boot from the box image which has boot.scr and s905_autoscript etc. it should boot. Unless somehow you broke/erased vendor u-boot; then the WP2 image on SD will boot as vendor u-boot on eMMC doesn't exist. Either way.. glad you got there in the end.

[    5.185287] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0

This means the FTDI_SIO driver in the RPi4 kernel loaded and the /dev/ttyUSB0 device is how you access it from a terminal app.

Probably not since we (still) don't understand where the bug is.

gonp Can you boot from SD card (so emmc is not in-use) and then (re)write this image to emmc:

https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-11.0.1-wetek-hub.img.gz

I've modifed U-Boot with the content from this patch, but I'm nowhere near a Hub board to test it:

Bootloader-Builder/0003-Autoboot-keyboard-beaglebone-fixes.patch at fix/autoboot · BrianAdams/Bootloader-Builder

create sanity in the insanity. Contribute to BrianAdams/Bootloader-Builder development by creating an account on GitHub.

github.com

The patch should cause u-boot to pause if input is detected on the <space> key, and then you have 15 seconds to type "stop" to enter the u-boot console else it resets and boots again. The possible flaw is that constant noise might result in persistent triggering of the pause and reset cycle, but the first step is to ensure the changes are present in the image linked above. If yes, then we can fine-tune the behaviour.

Perhaps use network-online.target instead of network.target.

We aren't going to complicate LE11 with aarch64 support, it will be LE12 only.

There should be more Lego based cases!

tune2fs -L newlabel /dev/sda1 <= where /dev/sda1 is the NTFS partition that you want to change the label for.

[Unit]
Description=Hidden SSID Connect Service
After=network.target connman.service iwd.service
Wants=network.target connman.service iwd.service
Before=kodi.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/iwctl --passphrase <PWD> station wlan0 connect-hidden <SSID>
ExecStop=/usr/bin/iwctl station wlan0 disconnect

[Install]
WantedBy=multi-user.target

^ Something like that probably works. Create and enable /storage/.config/system.d/hidden-ssid.service

Amlogic uses the same patches in LE11 now - there are several boards with embedded chips or optional RTL8822CS modules.

It looks like I still have this driver in my RPi4 tree (from providing build guideance before) so you can use this image:

https://chewitt.libreelec.tv/testing/LibreELEC-RPi4.arm-11.0.1.tar

I make no promises that it works (if it does, great. If not, so be it). I also make no promises of future images; I have no need for this driver so the first time it fails to compile I'll drop it from my tree.

First read the LE11 release notes so you understand the limitations of AMLGX on an S905X3 board. Then (as per the notes) read the Amlogic boot instructions in the wiki: https://wiki.libreelec.tv/hardware/amlogic - there is no specific device-tree for that box but pick another SM1

Android box and it will probably work (they are all fairly similar).

gonp that kind of confirms the issue is noise on the UART pins. Have you tried resoldering the UART pins?

LE10 uses wpa_supplicant. LE11 uses iwd. I'm not sure knowing that helps, but it probably explains the difference.

Make a backup .. then update to 11.0 via the settings add-on. This avoids the need for clean-install and restore. If (and only if) something goes wrong you have the backup to restore back to 10.0.

P200 is for internal PHY boards with 10/100 Ethernet. P201 is for external PHY boards with Gbit Ethernet (like your box). Cold boot the box with Ethernet connected, then SSH in and run "pastekodi" and share the URL generated so I can see the boot log. This will show if any WiFi drivers and firmware are being loaded (or not).

You should read the LE11 release notes. These clearly state the AMLGX image is not perfect; although it works well with most normal media and codecs but some users have odd content and it might not suit them. They also tell you there is no support for internal DVB cards. I'd need to see debug logs to make any further comment on playback issues. Run "pastekodi" after clean boot and enabling debug logging and demonstrating problems.

All files under /storage/.kodi should be owned by root and except for specific files under /storage/.kodi/addons nothing should be executable; so a simple find/exec command setting 644 permissions but excluding the addons path should work. As a general rule permissions are not something that should end up being changed though, so I wouldn't waste time creating script tools. And that's probably why I've never seen them being created.

None.

    0.000000] Linux version 4.19.62-sunxi ([email protected]) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.92 SMP Wed Jul 31 22:07:23 CEST 2019

I think you've pasted the wrong log .. becuase all I can see are Armbian boot logs (Armbian issues are theirs to solve).