Posts by TobiasWe

Hallo Everybody,
Spotify addon has changed its regsitration stuff purely to avahi zeroconf. In github it was found out that my zeroconf is not working well

zeroconf version 1.3.10 - addon isn't found in the LAN - libreelec · Issue #7 · glk1001/plugin.audio.spotify

Hallo everybody, updated spotify addon to version 1.3.10 on libreelec and before I deleted the addon cache. The addon isn't found in the local WLAN hotspot…

github.com

I enabled avhai deamon

systemctl enable avahi-daemon.service

But the registration is still not working (after reboot and in local hotspot). How can I configure zeroconf avahi to get Spotify addon to work:

cat /etc/avahi/avahi-daemon.conf
[...]

[server]
#host-name=foo
#domain-name=local
# browse-domains=
use-ipv4=yes
use-ipv6=yes
#allow-interfaces=eth0
#deny-interfaces=eth1
#check-response-ttl=no
#use-iff-running=no
#enable-dbus=yes
#disallow-other-stacks=no
#allow-point-to-point=no
#cache-entries-max=4096
#clients-max=4096
#objects-per-client-max=1024
#entries-per-entry-group-max=32
ratelimit-interval-usec=1000000
ratelimit-burst=1000

[wide-area]
enable-wide-area=no

[publish]
#disable-publishing=no
#disable-user-service-publishing=no
#add-service-cookie=no
#publish-addresses=yes
publish-hinfo=no
publish-workstation=no
#publish-domain=yes
#publish-dns-servers=192.168.50.1, 192.168.50.2
#publish-resolv-conf-dns-servers=yes
#publish-aaaa-on-ipv4=yes
#publish-a-on-ipv6=no

[reflector]
#enable-reflector=no
#reflect-ipv=no
#reflect-filters=_airplay._tcp.local,_raop._tcp.local

[rlimits]
#rlimit-as=
#rlimit-core=0
#rlimit-data=8388608
#rlimit-fsize=0
#rlimit-nofile=768
#rlimit-stack=8388608
#rlimit-nproc=3

Kind regards,

Tobias

No, I don't have any windows computer. But I feel the stick got more and more damaged. So after 482MHz, also the 498MHz didn't work. On the very begining I could watch everything on the laptop. Now it doesn't work on the laptop.

So it got damaged in slow motion.

I will try to buy the same Stick again. Then I will see that all drivers and the new stick will work, I think!

Tobias

I think now the DVB-T2 stick is defect. After all it doesn't funk on my laptop, which did at the very beginning!

I tried

Quote from CvH

modprobe em28xx card=94
echo "2040 8268" > /sys/bus/usb/drivers/em28xx/new_id

With updated and without updated firmware. It didn't help.

I put the USB hub away and connected the DVB-T2 stick to the raspberry directly. Now none of the channels work correctly. Before only the ZDF Mux didn't work.

Here is the dmesg output for the direct connection.

There is a lot output with dmsg. But the last ca 50 lines repeat this:

em28xx 1-1.4.1:1.0: write to i2c device at 0xc8 failed with unknown error (status=128)

I know from

[SOLVED/WORKAROUND] Hauppauge SoloHD not working/new product ID - Tvheadend

that em28xx is the corresponding kernel module for the firmware and the dvb-t2 stick.

Is there a conflict between two firmware files?

[7.125042] em28xx: Registered (Em28xx Input Extension) extension

[ 7.391689] si2168 8-0064: firmware version: B 4.0.11

[ 7.397775] si2157 9-0060: found a 'Silicon Labs Si2157-A30'

[ 7.447904] si2157 9-0060: firmware version: 3.0.5

Is it important that I use a USB hub with its own power supply?

I did so, but that didn't help to solve the dvb-t problem )-:

OK, but I also have to delete the old version in the order

/usr/lib/kernel-overlays/base/lib/firmware/

How can I do that?

Hello Everybody,

from this forum I know that I have to update my WinTV Solo HD firmware to watch DVB-T2 correctly (the channels of one tvheadend mux are disturbed):
DVB-T2 ZDF Mux in Leipzig/Germany at 482MHz not working - Tvheadend

When I try to exchange the file dvb-demod-si2168-b40-01.fw on my Raspberry 4, I cannot because it's a read-only filesystem. I tried to remount root and I tried to mount the sd card on my Laptop. Neither helped.

So how can I update the firmware file on my Raspberry Pi 4?

kind regards,

Tobias