Posts by chewitt

I never really used the NOOBS based recovery stuff so I can't really guide you on how to work it, but the best option for LE use is to connect the box to a PC and (as per the comment you've quoted) write the image directly to emmc overwriting NOOBS.

giancai best to ask for help in a forum like freaktab that specialises in Android devices and ROMs .. we're not one.

Images we (almost) support use the mainline kernel: linux/arch/arm64/boot/dts/amlogic at master · torvalds/linux · GitHub

Images with 3.14 or 4.9 kernels are no longer supported.

mglae .. read post #1 the user has Intel/nVidia cards and the nVidia drivers definitely aren't built-in

Images from ~ 5 mins ago have much improved audio on G12A, G12B and SM1 devices. You should be able to play all media without encountering static (all the multi-channel audio files I have work) and multi-channel audio channel mappings are fixed. I have disabled IEC958 devices in the alsa conf as I get static pops that don't sound tweeter friendly when trying to use the "HDMI" device or pass-through; the drivers are not ready for this yet. Select the "Analogue" card listed immediately above pulseaudio.

The same changes are in the GX device images, but I haven't done any testing to see if the revised alsa conf has a positive effect on the "machine gun noise" (buffer underrun) problem in the AIU driver.

tavoc The "box" image is for booting devices with vendor u-boot, the "khadas-vim" image has mainlne u-boot and is for writing LE to internal emmc (overwriting the vendor u-boot).

echo "sleep 30s" >> /storage/.config/autostart.sh

^ this is wrong, it should be "30" not "30s"

No plan to switch to pulse. It doesn't support HD audio formats properly (despite release notes that hint it does).

echo "nvidia" > /storage/.config/modprobe.d/blacklist.conf
reboot

^ It's about 5-years since I used an nvidia card so I forget the driver/module name, but assuming it is "nvidia" this will blacklist the driver and prevent it from being loaded at boot time, which should allow the Intel card to be detected by Xorg. In the current state where the nvidia card is sometimes seen first you might need to reboot a few times to have the GUI active (on the Intel card) to enable SSH and get access.

Please check if the LIRC service is enabled in the LE settings add-on. If yes, try disabling it.

I noticed this earlier LibreELEC.tv/soundconfig at master · LibreELEC/LibreELEC.tv · GitHub while looking at the file for some other reason. This might explain why some settings aren't preserved. The soundconfig file itself cannot be overriden, but it is called from udev through 90-alsa-restore.rules which can be, e.g. place a file of the same name in /storage/.config/udev.rules.d and it will be used at boot time instead of the embedded (read-only) one. This allows you to call a different soundconfig script with alternative mixer settings.

I still think you need to create a different alsa conf that deffines the on-board S/PDIF device as an IEC958 source. Unless you do this the device will not show up as pass-through capable in Kodi. Sadly, alsa configuration is one of Linux's "dark arts" that's particularly dense and difficult to Google search for solutions on as anything including "alsa" automatically gets a billion unrelated hits.

The lack of normally browsable repo avoids us having to support users who deliberately install the wrong add-on version in the wrong LE version, or in another OS. It's deliberate and it won't be changed. Users of LE can install the correct version of an add-on via the Kodi GUI, there is no real need to download them manually.

[provider_wireguard]

Type = WireGuard
Name = Cryptostorm
Host = 209.58.147.37
WireGuard.Address = 10.10.70.153/24
WireGuard.ListenPort = 51820
WireGuard.PrivateKey = my private
WireGuard.PublicKey = alFzGcAv99Mzjr7kRmoD8Mk8qgZ8HMtCNJPJRAOrL58=
WireGuard.PresharedKey = qrZ3+Jp0y2+eYlOE0heVBfFzcHhuWJ31Y5UF/mHQLRA=
WireGuard.DNS = 10.31.33.7
WireGuard.AllowedIPs = 0.0.0.0/0
WireGuard.EndpointPort = 443
WireGuard.PersistentKeepalive = 25

WireGuard.DNS also looks suspicious since 10.x.x.x is a private address; this is normally an external address like 8.8.8.8, 8.8.4.4 (Google)

USB stuff should work (and PCI cards etc. in Intel boxes) but none of the embedded cards like in the WP2 will work; there is no demux driver for mainline Amlogic (and the tuner/demod situation isn't brilliant) and nobody working on it.

No DVB drivers means .. no DVB drivers. I live in a counrty with no terrestrial TV so it works with local media and a friends TVHeadend that I have access to in Finland (3,500 miles away but lots of Ice Hockey .. works for me).

The -wetek-play2 image will not boot from SD card unless you zero the emmc first (else the box always boots factory u-boot which doesn't understand the boot files) and I wouldn't do that if the box is a daily driver. The mainline kernel OS is great but still has a few glitches and missing things. There is also no DVB support as a demux driver needs to be written from scratch and there's not many volunteers.

The -box image should boot though, and that's harmless enough to experiment witth.

LibreELEC-AMLGX.arm-9.80.8-box.img.gz

^ not entirely sure if this will boot from SD card, or not. There's also a dedicated WP2 image in the same folder but this needs you to erase the factory u-boot from emmc first before it will boot mainline u-boot on the SD card. It also has an audio glitch that you won't like if you encounter it.

Quote from eTrax

btw: Is there already a topic to discuss IMX.6 specific experiences, bugs etc. ?

Not really. We should probably create a forum section and let people start threads though.

Driver EEPROM-Failure · Issue #37 · kuba-moo/mt7601u · GitHub <= same issue, and looks unresolved