Tvheadend

AFAICT the version of TVH you used isn't one that is prebuilt for Tumbleweed, so maybe a little more information about where you got it and how you built it would help diagnosis? In particular why does the log show that '/usr/share/dvb' does not contain expected data? What scan tables do you have?

The card seems it should be supported, maybe you've seen https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-Starburst2 and checked that what you see on your system matches what they state? The system seems to have recognized the correct card, but there is 'cx23885⁰: warning: unknown hauppauge model #150300' so perhaps there's a new version of the hardware that is causing some problem?

Also what do you mean by 'it stuck'? Is the process running? Can you access its web pages?

Hi,

thank you for your reply.

1.) Yes, I do not use the prebuild for Tumbleweed. I compiled my own, according to this guide:
https://tvheadend.org/boards/4/topics/48471?r=48498

2.) about scan tables:
I did not create any scan tables. I just used the wizard of Tvheadend to scan for the muxes and for the channels.
Muxes were empty, so I needed to create one manually and the rest was auto detect (according to this post here):
https://tvheadend.org/boards/5/topics/15414

3.) I configured the card exactly as in this wiki article. I do not think that it is the TV card, it worked without problems after I configured it in the first step (could already watch some channels).

4.) with "stuck" I mean that Tvheadend does nothing after this line - I can't access the webserver (even with "netstat -an | grep 9981" saying that the port is open) and I can stop the service, but the tvheadend process continue running. even "sudo kill -9 <pid>" do not bring the tvheadend process to stop.

Best regards,
bmwGTR

Is tuner functional?
Is w-scan can found channels?

Tuner drivers
https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder

"sudo kill -9 <pid>"

something's very strange there. That should work.

What machine is this running on. What satellite are you trying to receive. I noticed you are using PowerVU and BISS descrambler. Do you have official subscription for these.

saen acro wrote:

Is tuner functional?
Is w-scan can found channels?

Tuner drivers
https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder

Yes, tuner is functional. Work without problems in Windows 11 (have it in double boot with openSuse Tumbleweed)
w-scan stuck in the same way as tvheadend. Also w-scan do not react on CTRL+C.
dvbv5-scan works (https://www.linuxtv.org/wiki/index.php/Dvbv5-scan).

"sudo kill -9 <pid>"

something's very strange there. That should work.

Yes I know. I find this very strange.

What machine is this running on. What satellite are you trying to receive. I noticed you are using PowerVU and BISS descrambler. Do you have official subscription for these.

CPU: AMD Ryzen 5700X
GPU: Palit Geforce RTX 3070
Mainboard: MSI B550 Mortar Max

Satellite: Astra 19.2E - Single LNB

PowerVU and BISS descrambler: do not know why they are active. I use OSCAM for descrambling.

Best regards,
bmwGTR

David Jansel wrote:

saen acro wrote:

Is tuner functional?
Is w-scan can found channels?

Tuner drivers
https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder

Yes, tuner is functional. Work without problems in Windows 11 (have it in double boot with openSuse Tumbleweed)
w-scan stuck in the same way as tvheadend. Also w-scan do not react on CTRL+C.
dvbv5-scan works (https://www.linuxtv.org/wiki/index.php/Dvbv5-scan).

Is it functional in current OS?

"sudo kill -9 <pid>"

something's very strange there. That should work.

Yes I know. I find this very strange.

killall tvheadend

Unless you have a particular reason for running Open Suse, I’d look at an alternative Linux OS. Never having used it but reading up on it the general consensus is it can be very bloated which affects overall performance.

Jonas Lang wrote:

Unless you have a particular reason for running Open Suse, I’d look at an alternative Linux OS. Never having used it but reading up on it the general consensus is it can be very bloated which affects overall performance.

I use openSUSE as my daily driver (Leap rather than Tumbleweed though). It's fine and I haven't noticed any people complaining of poor performance, so if the OP is familiar with it I'd suggest sticking with it rather than introducing yat another variable for no reason. I don't think performance is an issue for the OP; some specific hardware- or driver-related issue seems more likely.

David Jansel wrote:

4.) with "stuck" I mean that Tvheadend does nothing after this line - I can't access the webserver (even with "netstat -an | grep 9981" saying that the port is open) and I can stop the service, but the tvheadend process continue running. even "sudo kill -9 <pid>" do not bring the tvheadend process to stop.

Hmm, what I see is:

$ ss -an | grep 9981
u_str ESTAB 0 0 * 39981 * 40968
u_str ESTAB 0 0 /run/dbus/system_bus_socket 40968 * 39981
tcp LISTEN 0 511 0.0.0.0:9981 0.0.0.0:*

$ ps -fe | grep [t]vh
hts 2433 1 0 May30 ? 02:19:59 /usr/bin/tvheadend -f -p /run/tvheadend.pid -c /var/lib/tvheadend/config -u hts -g video --http_port 9981 --htsp_port 9982 --noacl

What does bash say when you run the kill command?

Hi,

thank you all for your help, my issue is now solved.

I do not know why, but today I updated my kernel to 6.3.9 (alongside other updates) and now it works without a problem!

Maybe it was something faulty in the kernel before (6.3.6).

Best regards,
bmwGTR

I can confirm observing same issue on 6.3.8-200.fc38.x86_64 kernel using https://docs.linuxserver.io/images/docker-tvheadend @ 4.3-2066~g81c986d55 (update: tested with docker-tvheadend with tvheadnend built at 4.3-2140~g14298acb6)

I didn't put much effort in investigating and following discoveries above I saw the issue disappear when got kernel downgraded to 6.2.9-300.fc38.x86_64

Another side affect was that system would hang on reboot and fail to stop affected container which suggests some ugly kernel issue.

I am happy to help any investigation, dmesg was not revealing much

this is with failing kernel

[    8.851454] em28xx 1-4:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x16cdc980
[    8.851463] em28xx 1-4:1.0: EEPROM info:
[    8.851466] em28xx 1-4:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[    8.861701] em28xx 1-4:1.0:  AC97 audio (5 sample rates)
[    8.861706] em28xx 1-4:1.0:  500mA max power
[    8.861708] em28xx 1-4:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[    8.914317] em28xx 1-4:1.0: Identified as PCTV tripleStick (292e) (card=94)
[    8.914326] em28xx 1-4:1.0: dvb set to bulk mode.
[    8.914480] usbcore: registered new interface driver em28xx
[    8.950804] em28xx 1-4:1.0: Binding DVB extension
[    8.967611] i2c i2c-11: Added multiplexed i2c bus 12
[    8.967617] si2168 11-0064: Silicon Labs Si2168-D60 successfully identified
[    8.967619] si2168 11-0064: firmware version: D 6.0.1
[    8.982212] si2157 12-0060: Silicon Labs Si2157 successfully attached
[    8.982245] dvbdev: DVB: registering new adapter (1-4:1.0)
[    8.982250] em28xx 1-4:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[    8.982257] dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
[    8.982552] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    8.983201] em28xx 1-4:1.0: DVB extension successfully initialized
[    8.983205] em28xx: Registered (Em28xx dvb Extension) extension
[    8.989449] em28xx 1-4:1.0: Registering input extension
[  154.924324] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'
[  155.302749] si2168 11-0064: firmware version: D 6.0.2
[  155.318128] si2157 12-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50'
[  155.318296] si2157 12-0060: Using ROM firmware.
[  155.374625] si2157 12-0060: firmware version: 3.0.5
[  155.388173] em28xx 1-4:1.0: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)

this is with working kernel

[    9.297355] em28xx 1-4:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x16cdc980
[    9.297366] em28xx 1-4:1.0: EEPROM info:
[    9.297370] em28xx 1-4:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[    9.307603] em28xx 1-4:1.0:  AC97 audio (5 sample rates)
[    9.307608] em28xx 1-4:1.0:  500mA max power
[    9.307611] em28xx 1-4:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[    9.360282] em28xx 1-4:1.0: Identified as PCTV tripleStick (292e) (card=94)
[    9.360288] em28xx 1-4:1.0: dvb set to bulk mode.
[    9.360460] usbcore: registered new interface driver em28xx
[    9.410590] em28xx 1-4:1.0: Binding DVB extension
[    9.430644] i2c i2c-11: Added multiplexed i2c bus 12
[    9.430651] si2168 11-0064: Silicon Labs Si2168-D60 successfully identified
[    9.430654] si2168 11-0064: firmware version: D 6.0.1
[    9.441855] si2157 12-0060: Silicon Labs Si2157 successfully attached
[    9.441878] dvbdev: DVB: registering new adapter (1-4:1.0)
[    9.441882] em28xx 1-4:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
...
[  130.311266] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'
[  130.679292] si2168 11-0064: firmware version: D 6.0.2
[  130.694917] si2157 12-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50'
[  130.695044] si2157 12-0060: Using ROM firmware.
[  130.749564] si2157 12-0060: firmware version: 3.0.5
[  130.763067] em28xx 1-4:1.0: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)
[  130.777087] si2168 11-0064: downloading firmware from file 'dvb-demod-si2168-d60-01.fw'
[  131.163907] si2168 11-0064: firmware version: D 6.0.2