Posts by chewitt

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

mglae can you link to any upstream discussion on this?

The main two variables are wifi drivers and firmware. You can see if LE10 nightly images (with newer bits) are better than LE 9.2 images, but if not there is not much we can do. See: Index of / for images.

Andre Bollo BT in the GUI is managed by the LE settings add-on which is in the process of being rewritten for Python3; and BT is still one of the bits that's being worked on. If you SSH into the OS you can use "bluetoothctl" to pair devices etc. - until the GUI work is completed.

[ 41.084656] usb 1-1.2: USB disconnect, device number 3
[ 41.085934] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 41.286978] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00

^ I see this which triggers the "removal" notice that you see, but 10 seconds later the drive remounts and "mount" shows it as mounted read-write which indicates the filesystem is okay (else it would mount read-only or fail).

The only odd thing that I can see is this from blkid:

PTTYPE="atari"

but I'm not sure that's the reason..

The length of a passphrase string determines its ability to resist brute forcing. Once you've gone much beyond 16 chars the amount of compute time needed to guess the passphrase is so insanely huge that there's not much point in having a longer one. It's also largely irrelevant because attackers rarely brute-force, they focus on finding flaws in the crypto implementation; which is how WEP, WPA and WPA2 are normally beaten.

Anyway.. if you cannot change it, access via SSH and (from memory):

connmanctl

agent on

scan wifi

services

connect <identifier of service>

copy/paste the string when prompted

Purchase is done. Martin is rather amazingly persistent with Meson8 support. I'd liken the reverse engineering effort to working a crime scene where you already know whodunit but there are few clues. The older BSP kernels are full of magic values so there's a lot of detective work involved.

Ahh, ok, it will need to be in /storage/.config/firmware then not the mediatek subfolder. We need to replicate the bad location in the upstream repo.