9.2.2 DVB tbs driver / Hauppauge USB wintv dual HD / Tvheadend conflict

No hub device connected directly on front otg port of n2

Just moved the usb dvb to one of the two usb 3.0 ports of the Beelink. Used a fresh installed 9.2.2 (original, not the one you sent me) and… same results!

Can you try replace kernel.img on your SD/USB with this file and let me know if it helps, thanks. This is only for users on ‘Amlogic-ng/4.9’ builds.

@anon88919003
I just try with your kernel.img but doesn’t helps, it’s the same result for me. Tvh service is working with CE default drivers, but not working/crash/hangs with crazycats drivers or drivers from latest kernel enabled.

with crazycats drivers or drivers from latest kernel enabled :
kodi log : http://ix.io/2j2y
tvh log : http://ix.io/2j2C

with CE default drivers :
kodi log : http://ix.io/2j2D
tvh log : http://ix.io/2j2B

Let me know if I can help with other logs / tests …
Thanks a lot for your hard work

Problem is not a conflict with tvheadend or Kodi and you are providing the wrong logs, I need kernel logs (dmesg).

Here is: http://ix.io/2j4R
Fresh formatted SD with 9.2.2 release, kernel file replaced, TVHeadEnd 4.2 and Cats drivers enabled.

Can you boot with the adaptor unplugged, then attach the adaptor after everything has booted, makes it easier to see the issue in the logs then.

Yes, of course: http://ix.io/2j4S

I wonder if tvheadend 4.2 would produce different results than 4.3 which is what is apparently used.

I had to revert to 4.2 to get proper functionality.

The issue is nothing to do with TVH.

The problem is the crazycat driver, it crashes the kernel straight after the firmware for this adaptor has been loaded, which you can see in the previous log provided.

[   34.467935@2] si2168 6-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[   34.467946@2] Unable to handle kernel paging request at virtual address fffffffe0
...

I have a different card but is uses the same demodulator and it doesn’t crash.

[ 64.292171@3] si2168 5-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 65.927518@5] si2168 5-0064: firmware version: B 4.0.25

A bit of a long shot but you could try to download another (older) firmware from here and put it under /storage/.config/firmware (Reboot required). The one under /usr/lib/kernel-overlays/base/lib/firmware/ seems to be 4.0.25.

@Rascal is yours a 3.14 or 4.9 device?

My bad, it’s a 3.14. I guess the issue is with -ng and 4.9.

I am struggling with the same problem here using a Hauppauge dual DVB-T2 stick connected to Hardkernel N2.
Meanwhile it’s 9.2.3. If I enable “latest drivers from kernel” the driver (?) crashes. System works but tvheadend server (4.2) doesn’t. No web interface, no connection from clients possible. Without driver add-ons it works, but without the second receiver of the Hauppauge stick.

If I shall provide logs I am ready to do.

More information are available in this thread: CoreELEC 9.2.3: tvheadend not working
With the help of Ray I found out that it seems to be the same problem as discussed here.

Yes it’s the same issue. There is just no chance to debug it Jochen. I already looked at an easy fix. I don’t think anyone in the Team can tackle it either.
Only thing I can do is maybe make a build with a lot of printk and then send it to you. See what it prints before oops happen.

It seems to be the driver packet from the addon “latest drivers from kernel”, right? So, at least, the packet to blame is identified?
Sure, I would like to try a kernel with massive printk. Last time I did that was when I added a 2nd SCSI adapter to Linux kernel1.x kernel driver. :wink:

Sorry, I don’t have any experience in cross compiling.

Yes but this driver “addon” contains a lot of latest linux media driver code with is compiled with the current linux source code. So it is not easy to identify. My guess is that it’s a 4.9 Kernel issue as it works with 3.14 kernel which uses the same addon driver code.

But it works in 9.2.1:
> # uname -a
> Linux odroid 4.9.190 #1 SMP PREEMPT Wed Nov 27 07:28:48 GMT 2019 aarch64 GNU/Linux
May be a 4.9 kernel issue, but 4.9.190 works.

And now please do the same uname on 9.2.3 and the me the difference.

Sure. Here it is:
# uname -a
Linux odroid 4.9.113 #1 SMP PREEMPT Tue Jun 16 12:53:14 CEST 2020 aarch64 GNU/Linux

That’s from the development built you sent me. Why is ist an older kernel than in 9.2.1?
Now I would like to try 9.2.3 with kernel release 4.9.190.