Tvheadend

Except frequency leave all to AUTO

Dear Sean,

I had all entries on AUTO but the bandwidth. Now I tried to set the bandwidth
on AUTO too and started the scan. But the new scan ended with failure.

Tobias

Hallo Everybody,

I buyed a Raspberry Pi 4. With Libreelec, Hardware Decoding works with this device. So there is no overheat. But still, the ZDF Transponder at 482 MHz including the channels ZDF, ZDIinfo, ZDFneo and 3Sat does not work. This takes now half a year, so it can't be a temporary distortion of the antenna.

In two weeks, there are soccer european champinships. Could you please Help?

Tobias

What are you using as Tuner? A USB one?

It's hard to help without having the hardware and actually trying around with it, since the switch to DVB-T2 I never got a DVB-T2 Tuner again as I think it's not worth the money. You can try if w_scan works, then you at least know if it's a Tvheadend issue or not.

It's a Haupage WinTV soloHD.

what w_scan command exactly. I can try w_scan on my Linux Laptop.

I will try Kaffeine first.

OK, on my Laptop Kaffeine doesn't find any channel. I think there is a driver Problem on my Laptop.

But how can I use w_scan on my Raspberry?

On my Laptop I solved the driver problem wth this:

https://www.hauppauge.de/site/support/support_faq.php?n=FAQ.Linux

Now, the channel search with kaffeine works. Also the regarded channels ZDF, ZDFinfo, ZDFneo and 3Sat are without distortions.

It was a good idea, to test it with other software!!! I thought the antenna of the Broadcaster has errors.

And now?

I don't really understand what you've done now. Simply updated the firmware? Then do the same thing on the raspberry.

On my Raspberry it's not a problem of the firmware. The other muxes work: ARD, MDR, Phoenix and so on.

There is a difference in the search:

Raspberry de-all
Laptop: de-Saxony

You might still be running an outdated Firmware. Update it so that is ruled out. If it still doesn't work then you should try with w_scan (stop Tvheadend, run w_scan and see if it finds the channels).

On Raspberry ZDF is found, but it is distorted.

OK, I will update the firmware on Raspberry and start a new channel search. This will take a bit time ...

Thats interesting! The firmware file is dvb-demod-si2168-b40-01.fw .

In the order /lib/firmware/ there are links to the firmware files in /usr/lib/kernel-overlays/base/lib/firmware/ .

The only thing is, that there is no link to the existing file /usr/lib/kernel-overlays/base/lib/firmware/dvb-demod-si2168-b40-01.fw

So I did the following:
LibreELEC:/var/lib/firmware # ln -s /usr/lib/kernel-overlays/base/lib/firmware/dvb-demod-si2168-b40-01.fw /lib/firmware/dvb-demod-si2168-b40-01.fw

Now I will see if it works now ...

After making this link and starting a new channels search, all channels are distorted.

I can't replace the the file in /usr/lib/kernel-overlays/base/lib/firmware/ , because it is a read-only filesystem.

I have to see, how I can change this ...

For updating the firmware file, I have to remount "something", but I don't know what "something" is, in this case:

mount -o remount,rw /something

LibreELEC:~ # ls -al /
total 17
drwxrwxr-x 13 root root 202 May 27 2021 .
drwxrwxr-x 13 root root 202 May 27 2021 ..
lrwxrwxrwx 1 root root 8 May 27 2021 bin -> /usr/bin
drwxr-xr-x 17 root root 4120 Apr 11 18:28 dev
drwxrwxr-x 22 root root 1024 May 27 2021 etc
drwxr-xr-x 3 root root 16384 Jan 1 1970 flash
lrwxrwxrwx 1 root root 8 May 27 2021 lib -> /usr/lib
lrwxrwxrwx 1 root root 10 May 27 2021 media -> /var/media
drwxrwxr-x 3 root root 25 May 27 2021 opt
dr-xr-xr-x 128 root root 0 Jan 1 1970 proc
drwxr-xr-x 17 root root 540 Apr 11 18:28 run
lrwxrwxrwx 1 root root 9 May 27 2021 sbin -> /usr/sbin
drwxr-xr-x 16 root root 1024 Apr 11 18:34 storage
dr-xr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 9 root root 180 Apr 11 18:29 tmp
drwxrwxr-x 9 root root 136 May 27 2021 usr
drwxr-xr-x 9 root root 220 Apr 11 18:28 var

LibreELEC:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 1740988 4 1740984 0% /dev
/dev/mmcblk0p1 524008 147928 376080 28% /flash
/dev/loop0 135168 135168 0 100% /
/dev/mmcblk0p2 14550493 546533 13999864 4% /storage
tmpfs 1875132 0 1875132 0% /dev/shm
tmpfs 1875132 6904 1868228 0% /run
tmpfs 1875132 0 1875132 0% /sys/fs/cgroup
tmpfs 1875132 16 1875116 0% /var
tmpfs 1875132 0 1875132 0% /tmp
/dev/sda1 479668992 93182156 385493684 19% /var/media/TOSHIBA EXT

Should I delete the symbolic link?

Tobias

I will try with remount root / - I remember I also did some time ago ..

remounting / , /flash and /storage didn't change that I can't replace the firmware file, because of "read-only" filesystem

If / is on an read-only filesystem like cdromfs or squashfs you can't remount it as read/write.

Can this OpenElec post help? It suggests a 02 firmware file: dvb-demod-si2168-b40-02.fw

https://tvheadend.org/boards/4/topics/29460

_RE: [SOLVED/WORKAROUND] Hauppauge SoloHD not working/new product ID - Von Giacinto Lo Meo vor mehr als 3 Jahren hinzugefügt
I solved my problem and now i have the Hauppauge WinTV Solo HD id 2040:8268 fully functional with Ubuntu 16.04.3. The steps that i have done are the following. I don't know if all of them are necessary, however i hope this can help someone with this problem.

I've installed V4L-DVB as explained here: https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
    I've downloaded dvb-demod-si2168-02.fw (https://github.com/OpenELEC/dvb-firmware/blob/master/firmware/dvb-demod-si2168-02.fw) and copied to /lib/firmware
    I've installed the package linux-firmware-nonfree -> downloaded from https://launchpad.net/ubuntu/xenial/+package/linux-firmware-nonfree selected my architecture and then sudo dpkg -i linux-firmware-nonfree_xx.deb_
    Then the magic commands suggested by Sir Cypher:
    I have created a file dvbstick.sh

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

maked it executable with sudo chmod +x dvbstick.sh
    and then, because the udev rule not work for me, i have added the script to /etc/rc.local_

You need to figure out how to write to the filesystem. I don't know what kind of filesystem it is and how it's used, so it's probably a good idea to ask the maintainers of LibreELEC.

Maybe I could mount the sd card on my laptop. What changes do you suggest?

I suggest updating the Firmware if it's outdated.

should I take the 01.fw file which worked on my laptop or should I take the 02.fw file suggested for OpenElec?

Use the one that worked, the other one is probably already in there.