Posts by rkershenbaum

Can't thank you enough, chewitt, for the qukck and expert response! The Ugreen ASIX-based adapters work perfectly (almost -- see below) with the test version. You can feel confident in pushing out the change.

(I'm assuming that you only made this update to the Rpi4 version. The problem was still there when I tried the 11.80 Rpi5 version.)

I'm going to return the RT8153-based adapters that require the usb_modeswitch fiddling, and keep the (more expensive) Ugreen 20256 adapters that don't.

There is a semi-unrelated problem, though. After switching between interfaces (both with static IPs, if it makes any difference), and accessing a local or remote network resource, the UI hangs for periods of 30 seconds to several minutes. Also, many of the icons disappear. The o/s is not hung, since I can still ssh into it and enter commands. I think this is unrelated to the USB adapters, since I saw the same problem when switching between wired and wireless interfaces.

Here's a debug log that (hopefully) will show the problem:

https://paste.libreelec.tv/next-turkey.log

New install of LE 11 with the AX88179 adapter plugged into a USB3 port on a Rpi4, but not showing up as eth1. Here's the debug log:

https://paste.libreelec.tv/square-gobbler.log

Quote from chewitt

NB: usb_modeswitch is in the LE "system-tools" add-on.

Thanks very much for that! By adapting the instructions in the link above, I was able to get the RT8153-based adapter to come up across boots.

For anyone else needing to do this, after installing the LE "system-tools" addon, navigate to ~/.config/system.d and create a file a file named "rpi-usbfix.service" with this content:

[Unit]
Description=Fixes some usb issues

[Service]
ExecStart=/storage/.kodi/addons/virtual.system-tools/bin/usb_modeswitch -v 0bda -p 8151 -R
Type=oneshot
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

The do

systemctl enable rpi-usbfix.service

...so that the command runs following each boot.

Not ideal -- but it does work.

Now...I'll work on getting you the info you requested re: the AX88179 driver not loading....

Quote from chewitt

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

New install of LE 11 with the AX88179 adapter plugged into a USB3 port on a Rpi4. Here's the debug log:

https://paste.libreelec.tv/square-gobbler.log

I need to add a second wired Ethernet interface to my Rpi4s and Rpi5s -- and I'm not having any luck. The same problems occur with the latest LibreELEC 11.0.6 release, and also with the latest LibreELEC 12 nightlies.

First, I tried a cheap generic USB3 to Gigabit adapter based on the RTL8153 chipset. It works when plugged into the Pi, but the network instance disappears after a boot. I can unplug it from the USB3 port on the Pi, plug it back in, and it works -- until the next boot. I'm encountering the exact problem described here:

RaspPi 4 & RTL8153 Ethernet USB gadget need to be unplugged - Raspberry Pi Forums

After a boot, the output from lsusb shows

Bus 002 Device 002: ID 0bda:8151 Realtek Semiconductor Corp. RTL8151 Adapteon Business Mobile Networks BV

...and the eth1 device does not appear in the output from ifconfig. After unplugging the device and plugging it back in, it shows

Bus 002 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter

...and the eth1 device works. But I'd rather not have to remember to replug the device after each boot.

I read elsewhere that the Ugreen adapters worked well with LibreELEC and Rpi, so I ordered the Ugreen 20256 model, which uses the AX88`179 chipset. This one does not work at all. Lsusb shows

Bus 002 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet

But the driver does not seem to be loading. The eth1 interface does not appear in ifconfig, or in the "connections" section of the LibreELEC settings. Rebooting does not make a difference.

Are there any workarounds to make either of these work? Or are there fixes in the works? Or, is there another model I should order that will work out of the box?

Any help with this would be much appreciated!

Hi, guys, and thanks for all of your work on this.

One suggestion -- you should add one note to the Wiki: Although the "preshared key" is optional, if a preshared key isn't used, the entire line must be deleted. If the line is present, but no key is supplied, the Wireguard instance will fail.

I wasted several hours before I figured this out, and I know others have as well.

Quote from Da Flex

It's a bug in the settings add-on. The cache file is used, but it has to be activated by touch /storage/.cache/hostname.

Thank you!! That worked.

Quote from chewitt

IIRC *the* place to change hostname is the LE settings add-on; this is the master location that defines what is set/propagated at runtime. If you edit /etc/hostname directly the change will not persist over a reboot. LE is not a general purpose distro - it does not always follow other distro conventions for doing things.

Thanks for the reply! The problem is that, in the LE12 nightlies, when you do use the LE settings addon to change the hostname, it immediately reverts to "LibreELEC" on the next boot.

Changing it in /etc/hostname was a failed attempt at a workaround. Sorry if that wasn't clear.

Same problem here with the LE 12 nightlies.

I tried editing /etc/hostname, but it reverts back to LibreELEC after a boot.

I have three LibreELEC installations, and this makes it a little more difficult to administer them, although I can address them separately by IP address.

Ideally LE would give priority to an external usb BT dongle, over the built-in Rpi adapter. If a user has installed an external BT dongle, that's probably the one he or she wants to utilize. But that may not be technically feasible.

Quote from lrusak

Why don't you try disabling the internal BT with a dtoverlay?

Thanks for the suggestion!! That seems to have fixed the problem. I added

dtoverlay=disable-bt

...to config.txt. I had to re-pair my BT speaker, but now the BT audio works properly -- and the light on the BT dongle flickers as it should. So it is definitely using the external dongle.

However, I never needed to do this with LE 9.x and earlier.

Quote from SupervisedThinking

So looks like the device was detected - when you enter LE settings & the bt menu the light does not start to steadily flicker/light up? Does some devices show up at all?

No, the light does not come on at all. I even tried a new identical dongle, with the same results.

BT devices do show up in the LE settings, but I believe they're being accessed through the Rpi4's built-in Bluetooth adapter, instead of the outboard CSR dongle. I'm getting considerable breaking up of the audio on a BT speaker in a nearby room. That didn't happen when the CSR dongle was working properly (with LE 9.x and earlier).

Quote from SupervisedThinking

When I run lsusb I get this output:

Bus 007 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and dmesg | grep CSR states:

[ 1.463995] usb 7-1: Product: CSR8510 A10

So does your Pi detect the BT dongle? Please upload the logs as chewitt mentioned

Apparently it does detect the device, so I'm not sure why it's not working.

I posted the urls for the logs as chewitt requested. Do I need to upload them also?

Bedroom:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bedroom:~ # dmesg | grep CSR
[   46.875265] usb 1-1.1: Product: CSR8510 A10

Quote from SupervisedThinking

CSR should be "Cambridge silicon radio", I use the same bt dongle at my RockPro64. So it should work, if it doesn't some driver is probably missing.

The led only lights up when you're looking for devices & if you've enabled Bluetooth in LE settings. You did this?

Yes, Bluetooth is enabled. It's working with the Rpi4's built-in Bluetooth adapter, but I want to extend the range with the external dongle (attached to a USB cable). With LE9.x, the LED flashed when Bluetooth was in use.

Here you go:

http://ix.io/2TPh

http://ix.io/2TPg

I've been using a cheap "CSR V4.0" Bluetooth dongle with my Rpi4 to increase the signal range. It worked great with LibreELEC 9.x, but does not with LE10. The LED on the dongle does not light up, so it appears that the driver is not being loaded, or that the device isn't being recognized for some reason.

Is there something I can do to fix this?

Or, can the devs re-add the appropriate driver?

Thanks for any help with this!

I'm using this on a RPi4 with LibreELEC 9.2 final. It works sometimes -- but usually doesn't work.

What's really strange is that when the Bluetooth device is turned on, the audio device is actually changed to the Pulse Bluetooth setting. In Kodi Settings / System / Audio it shows as Bluetooth audio. But the actual sound stays on the HDMI-connected device (stereo receiver, in my case) and doesn't switch to the Bluetooth speaker.

Any ideas??

I just upgraded to LibreELEC 9.0.2, and this fix for this seems to have disappeared. EPG downloading broke for me.

After some investigation, I found the underlying problem. The tv_grab_file script doesn't "unescape" the URL from settings.xml before using it in the wget command to fetch the XMLTV listings. I.e. it doesn't change "&" to simply "&", so the URL doesn't properly pass the login credentials to the server.

I changed the line:

wget -qO - "$XMLTV_LOCATION_WEB"

to:

wget -qO - $(xml unesc $XMLTV_LOCATION_WEB)

I'm not a Linux guru, so I don't know if this is the best way to fix the problem, or if it might break something for other users. But my listings are now downloading properly.