Let’s get back to topic. I want this fixed.
1 Like
Next test with CoreELEC (community): devel-1592741145 (Amlogic-ng.arm)
Linux odroid 4.9.113 #1 SMP PREEMPT Sun Jun 21 14:04:58 CEST 2020 aarch64 GNU/Linux
Without driver addon: DVB-T2 working but only one receiver on dual Hauppauge stick.
dmesg: http://ix.io/2pM0
With “DVB drivers from latest kernel” it “ooops” again: http://ix.io/2pM4
If the Hauppauge stick is out of your possibilities what DVB-T2 hardware do you recommend? I need a sum of 3 receivers.
Ok I give up. This is hopeless. If I have another Idea I will ping. Until then we better disable hauppauge driver in dvb latest and crazycat. The limitation for one driver is not a bug it’s just the status of the driver in 4.9 kernel.
Ok, Thank you for trying.
4.9 in CoreELEC 9.2.1 woks. But you mentioned a kernel decision of the CoreELEC team on the way to 9.2.2 wich unfortunately broke support of my DVB-T receiver.
I stick with 9.2.1 until I change over to real x86 hardware and working support in a recent kernel.
Tried the Haupauge with my notebook – works from first moment with both receivers. Kernel 5.3.
And I send you even newer 4.9.238 kernel and it didn’t work either.
It might be a good idea to relegate your tuners to a TVHeadend backend server where you can leave the version of CE at 9.2.1 indefinitely . You can then use just about any hardware to act as your frontend client for the media playback duties. The client can be a cheap Android box for €30.00 and can be kept on the latest builds and features.
This is a much better and more stable arrangement.
Shoog
Do it already. But I still use the “server” also as client.
Yes. Bad luck. Thank you for the effort.
Been there done that, the issues of support are much the same but the energy wastage is significantly higher, the hardware features are worse and the cost is orders of magnitude more. Thats enough for this chump to stick to AMLogic.
Shoog
Old Notebook with full Linux is the way I am going to try.
But that’s off-topic since the OS / distro will not be CoreELEC.
I would really like to fix this but I am out of ideas. The issue exists since November last year afaik and too many things changed since then.
If you want @jochen02 you can try one nightly after another between 9.2.1 and 9.2.2 and tell me when it broke. But it will probably be when the kernel was switched. Not only that we switched kernel we also use a more recent AML bsp kernel which already introduced some weird issues. But it also solved a lot of playback issues so there is no way going back.
Yes, it sounds plausible. Perhaps I’ll do that. May take some time, I’m a bit busy with other jobs.
CoreELEC consists of a kernel and the rest of the Kodi universe. How complicate is it just changing the kernel? That opens the chance for me to add the older kernel from 9.2.1 to the new releases of CoreELEC. May be a weird idea…
What about my question which DVB-T2 stick would be recommended by the CoreELEC team?
It is not complicated. Please try yourself. I am here if you have questions. I always encourage people to learn it. Maybe you can debug and trace the oops. Looking forward to this.
First I have to learn how to set up a cross compiling environment. I don’t have any experience in that field.
The issue about the Hauppauge soloHD/dualHD should be solved by next nightly.
1 Like
I want to thank publicly Portisch for his efforts to correct this issue.
1 Like
I wanted to thanks and congratulate @Portisch for his efforts. After compiling from source, and make fresh install, I confirm that it works. Thank you very much.
Thank you, CE users where just insist friendly and long enough until this issue was solved. Most hard part on issues like this is that it is not possible for Team CoreELEC to own every piece of hardware available out there on market for debugging.
1 Like
Just received a WinTV-dualHD today and encountered the same problem with a bit older build of coreelec, running on GT-King Pro. I can confirm that after rebuild from head of coreelec-9.2 branch (9f6f71fbe4) the problem reported in this thread is fixed.
However I get another problem: Hauppauge WinTV-dualHD tuner is not working in any USB 3.0 port of GT-King Pro. It works only in the one USB 2.0 port (marked as OTG) provided by GT-King Pro.
When in usb 3.0 port, following messages are logged:
[ 2476.674353@0] si2157 5-0060: downloading firmware from file 'dvb-tuner-si2157-a30-01.fw'
[ 2477.130041@1] em28xx 1-1.1:1.0: writing to i2c device at 0xc8 failed (error=-5)
[ 2477.386088@1] em28xx 1-1.1:1.0: writing to i2c device at 0xc8 failed (error=-5)
[ 2477.642023@2] em28xx 1-1.1:1.0: writing to i2c device at 0xc8 failed (error=-5)
[ 2477.642033@2] si2157 5-0060: firmware download failed -5
[ 2477.642077@2] em28xx 1-1.1:1.0: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)
[ 2477.898086@0] em28xx 1-1.1:1.0: writing to i2c device at 0xce failed (error=-5)
[ 2478.154087@0] em28xx 1-1.1:1.0: writing to i2c device at 0xce failed (error=-5)
[ 2478.410099@0] em28xx 1-1.1:1.0: writing to i2c device at 0xce failed (error=-5)
[ 2478.410232@0] em28xx 1-1.1:1.0: DVB: adapter 1 frontend 0 frequency 0 out of range (48000000..870000000)
[ 2480.938330@2] em28xx 1-1.1:1.0: writing to i2c device at 0xc8 failed (error=-5)
[ 2481.194134@0] em28xx 1-1.1:1.0: writing to i2c device at 0xc8 failed (error=-5)and it is not possible to show any tv station.
While when running in the usb 2.0 port, it is fine, no error message present and both tuners work simultaneously with tvheadend.
I guess this is probably GT-King Pro specific.
I planned to get a second WinTV-dualHD to be used with GT-King Pro, but that would need to use usb 3.0 ports as only one usb 2.0 port is available.
Any idea how to solve this?