Posts by chewitt

If all you want/need to do is edit files in the OS, enable SSH access and connect using PuTTY (on Windows) and use nano to edit files. It's a lot less hassle than (re)booting from another OS to make minor changes.

libdsm is a lightweight SMB client that VLC uses for browsing SMB shares. Kodi has an SMB client that it uses for browsing SMB shares. Kodi does not support alternatives; because there's no need for that .. it already has an SMB client. If for some reason that doesn't work you can also use kernel SMB capabilities to mount a remote filesystem to a path on the local host .. but that kind of thing is not really required as Kodi has a perfectly good SMB client.

ngrok would probably have dependencies on networking so systemd would always be the better approach since you can sequence the start to happen after the network is up/online.

You can add a systemd service file in /storage/.config/system.d to execute commands

Unless you share the boot logs there is nothing to take a stab at.

Please read https://wiki.libreelec.tv/hardware/amlogic#install2internal .. in short, that script isn't usable now.

I'm working on an approach for user-driven tweaking of the speeds that the mmc controller runs the SD card at. There are silicon bugs in the Amlogic controller that cause stability issues at higher speeds so most boards are currently and deliberatly underclocked to use a safe "runs everywhere" 50MHz speed. Most (but not all) boards will support this being raised to 100MHz with UHS modes enabled, and some might even tolerate 150MHz, but i'm confident none will reliably run at the 200MHz rate used in the vendor kernel. Amlogic implemented some hacky and unsafe workarounds for the vendor kernel to run that fast; and those changes would never be accepted into the usptream kernel.

In the absence of a log file, no idea. Perhaps try other device-tree files?

video=HDMI-A-1:1920x1080M@60

Only use the HDMI port nearest the PSU connector, and add this ^ to cmdline.txt. Fixed?

Not a known thing (at least not in this forum). As it's technically nothign to do with LE, the Kodi forum would be a better place to look.

ilmich ^ the above issue is caused by sarbes front-to-back patch, I've seen the same with AMLGX. It's a promising change but it needs further testing before we adopt it

echo "options snd-usb-audio quirk_alias=05a71020:047f02f7" > /storage/.config/modprobe.d/bose.conf
reboot

^ run that over SSH

Disable the official Plex add-on and install the one from this repo which works fine: https://pannal.github.io/dontpanickodi/

Hopefully Plex will figure out the same changes needed for the official add-on, but until then..

Can you drop the connman.service/iwd.service from the file and then run "systemctl daemon-reload" before rebooting? .. still working?

If yes I will write it up for the wiki.

It means the KERNEL init script cannot find the first partition on the SD card to mount it and decompress the SYSTEM file; which is odd since U-Boot could see the same partition to load the KERNEL file in the first place. Perhaps experiment with other SD cards and a different device-tree file. You could also try setting "boot=/dev/mmcblk1p1 disk=/dev/mmcblk1p2" in uEnv.ini instead of the current boot=GUID/disk=GUID content.

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.