How to update CrazyCat driver package

  • Dear all,

    is there a comprehensive guide how to update the CrazyCat TBS drivers? I am using

    • @kszaq's image for amlogic (on Le Potato)
    • a WinTV Hauppauge dualHD DVB-T2 USB stick,
    • The CrazyCat TBS drivers
    • TVheadend 4.3

    and both tuners are properly recognized, but Tuner #1 works nearly fine (once in a while a continuity error) while Tuner #2 only gives jerky video and loads of continuity errors. I seem to understand that the drivers have improved, but for all Googling I seem to be to stupid to get a up-to-date package. Can you help me?


    Side remark: Yes, I am aware of CoreELEC and of the experimental support of Le Potato in the official LibreELEC build, but CoreELEC has very old CrazyCat drivers (by design/on purpose) and only TVheadend 4.2, and the official does not even recognize my TV card and also only has TVheadend 4.2. For DVB-T2 I need TVheadend 4.3, which luckily is in kszaq's image.


    Thanks for help!


    Hauke

  • Hauke

    Changed the title of the thread from “How to update CracyCat driver pakage” to “How to update CrazyCat driver package”.
  • Having similar issues: Still lots of continuity errors. Signal strength and SNR both good.


    I went from CrazyCat's 8 builds to the Alpha because of this.


    LibreELEC (official): 8.90.006 (Generic.x

    HomePVR:~ # uname -r

    4.18.11


    Hauppauge Win DualHD USB (I'm in USA, so ATSC..)

    HTS Tvheadend 4.2.6-62 ~ LibreELEC Tvh-addon v9.0.116


    hastebin Kodi Log File.


    For some reason dmesg isn't found..


    Hardware - Lanner Electronics NCA-1010 E3825 CPU


    HomePVR:/var/log # lsusb -v -d 2040:826d


    Bus 001 Device 002: ID 2040:826d Hauppauge

    Device Descriptor:

    bLength 18

    bDescriptorType 1

    bcdUSB 2.00

    bDeviceClass 0

    bDeviceSubClass 0

    bDeviceProtocol 0

    bMaxPacketSize0 64

    idVendor 0x2040 Hauppauge

    idProduct 0x826d

    bcdDevice 1.00

    iManufacturer 3 HCW

    iProduct 1 955D

    iSerial 2 0014043801

    bNumConfigurations 1

    Configuration Descriptor:

    bLength 9

    bDescriptorType 2

    wTotalLength 55

    bNumInterfaces 1

    bConfigurationValue 1

    iConfiguration 0

    bmAttributes 0x80

    (Bus Powered)

    MaxPower 500mA

    Interface Descriptor:

    bLength 9

    bDescriptorType 4

    bInterfaceNumber 0

    bAlternateSetting 0

    bNumEndpoints 2

    bInterfaceClass 255 Vendor Specific Class

    bInterfaceSubClass 0

    bInterfaceProtocol 0

    iInterface 0

    Endpoint Descriptor:

    bLength 7

    bDescriptorType 5

    bEndpointAddress 0x84 EP 4 IN

    bmAttributes 2

    Transfer Type Bulk

    Synch Type None

    Usage Type Data

    wMaxPacketSize 0x0200 1x 512 bytes

    bInterval 0

    Endpoint Descriptor:

    bLength 7

    bDescriptorType 5

    bEndpointAddress 0x85 EP 5 IN

    bmAttributes 2

    Transfer Type Bulk

    Synch Type None

    Usage Type Data

    wMaxPacketSize 0x0200 1x 512 bytes

    bInterval 0

    Interface Descriptor:

    bLength 9

    bDescriptorType 4

    bInterfaceNumber 0

    bAlternateSetting 1

    bNumEndpoints 2

    bInterfaceClass 255 Vendor Specific Class

    bInterfaceSubClass 0

    bInterfaceProtocol 0

    iInterface 0

    Endpoint Descriptor:

    bLength 7

    bDescriptorType 5

    bEndpointAddress 0x84 EP 4 IN

    bmAttributes 2

    Transfer Type Bulk

    Synch Type None

    Usage Type Data

    wMaxPacketSize 0x0200 1x 512 bytes

    bInterval 0

    Endpoint Descriptor:

    bLength 7

    bDescriptorType 5

    bEndpointAddress 0x85 EP 5 IN

    bmAttributes 2

    Transfer Type Bulk

    Synch Type None

    Usage Type Data

    wMaxPacketSize 0x0200 1x 512 bytes

    bInterval 0

    Device Qualifier (for other device speed):

    bLength 10

    bDescriptorType 6

    bcdUSB 2.00

    bDeviceClass 0

    bDeviceSubClass 0

    bDeviceProtocol 0

    bMaxPacketSize0 64

    bNumConfigurations 1

    can't get debug descriptor: Resource temporarily unavailable

    Device Status: 0x0000

    (Bus Powered)

    HomePVR:/var/log #

  • Additional - thought about this after I clicked reply:


    HomePVR:~ # lsmod

    Module Size Used by

    rc_hauppauge 16384 0

    em28xx_rc 20480 0

    rc_core 36864 3 em28xx_rc,rc_hauppauge

    si2157 20480 2

    lgdt3306a 28672 2

    i2c_mux 16384 1 lgdt3306a

    em28xx_dvb 36864 32

    dvb_core 131072 1 em28xx_dvb

    videobuf2_vmalloc 16384 1 dvb_core

    videobuf2_memops 16384 1 videobuf2_vmalloc

    videobuf2_common 45056 1 dvb_core

    8021q 24576 0

    intel_powerclamp 16384 0

    intel_soc_dts_thermal 16384 0

    intel_soc_dts_iosf 16384 1 intel_soc_dts_thermal

    em28xx 86016 2 em28xx_rc,em28xx_dvb

    tveeprom 24576 1 em28xx

    v4l2_common 16384 1 em28xx

    videodev 167936 2 v4l2_common,videobuf2_common

    media 32768 4 videodev,si2157,dvb_core,em28xx

    snd_hda_codec_hdmi 49152 1

    snd_hda_intel 36864 3

    snd_hda_codec 106496 2 snd_hda_codec_hdmi,snd_hda_intel

    snd_hwdep 16384 1 snd_hda_codec

    snd_hda_core 65536 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec

    pcc_cpufreq 16384 0

  • Could you update the build with the 8.2.3/4.8 kernel?

    Your DVB card is not affected by that problem.

    Signal strength and SNR both good.

    this are mostly bogus values, don't trust them !! (maybe they are correct for that card, I don't know).


    for that card you might test the DVB latest drivers from LE9 btw the default ones if they make anything different

  • Hi CvH ,


    I've just seen that the new release is there, and that CrazyCat drivers are in there in the newest version. Thanks a lot for that! Just tested on Le Potato: It is certainly the best experience I yet had with Kodi on LePotato regarding the Hauppauge DualHD card, but it is still not good. When watching a second channel, I still get too many errors to call the experience enjoyable.

    In the meanwhile I tested with Raspberry Pi and the 4.18 kernel, since Hauppauge claims native support for the dualHD stick starting with kernel 4.17, and I can confirm that the DVB-T2 reception is flawless with 4.18, even watching two channels simultaneaously. Raspberry, even 3B+, ist not powerful enough to watch even a single channel in HEVC (German DVB-T2 uses it), but using TVheadend on Raspberry and a Windows machine to watch the channels works totally fine.

    So, I suppose I need to stay patient until LibreELEC on Le Potato is on mainline kernel... According to a tweet by the Le Potato team, they already did a showcase with LibreELEC and mainline recently, so it seems to be close to reality anyhow...


    I really appreciate your efforts! Thanks again!


    Hauke

  • One of the current gaps on mainline code is software-only deinterlacing. It's watchable for most programming but sports with lots of fast panning shots have bad combing. I keep a spare box on 8.2.5 for watching F1 and MotoGP coverage :)

  • Is there still much interlaced content? Interlacing in my mind is something outdated from SD TV times, when technology was just not fit for full pictures... But I stand to be corrected.


    Whatever - what I am currently thinking about is just letting run my Raspberry in parallel to Le Potato and point the PVR frontend to the TVheadend on Raspberry with kernel 4.18. Not my long term solution, since it eats up another 5W of standby power, but until Le Potato is fit, it might be a solution.

  • It rather depends on where you are in the world. In a number of EU countries there are popular satellite and terrestrial broadcast channels (even HD ones) that use interlacing so it's important for people using Kodi's DVB capabilities.


    Using an RPi as the back-end should be fine.

  • Hi guys,


    just updated to LibreELEC (Leia) v8.95.2 BETA on my Potato - and lo and behold! - despite still having kernel 3.14, both tuners of the WinTV dualHD work flawlessly! Not sure what you changed, but it did the trick. Thanks a lot!


    Cheers


    Hauke

  • Sorry to say, but I was a bit too fast with my assessment. It is *nearly* flawless. The continuity errors on receiver 2 are gone, but funny as it is, now receiver 1 has occasional continuity errors, but very few. Changed the receiver priority in tvheadend so that receiver 2 is default - fine for the moment. Seems I have to wait for mainline kernel after all :-)

  • I think this little bug will be cleared in the next official release and I hope, because I ordered the same Hauppauge tuner :)

  • Well, even if the bug is not fixed, do not despair: The mainline kernel is around the corner also for Le Potato, and then all problems should be gone. I think only very few devices still use the 3.x kernel, and if you do not own such a device, you're safe now.

  • Sorry to say, but I was a bit too fast with my assessment. It is *nearly* flawless. The continuity errors on receiver 2 are gone, but funny as it is, now receiver 1 has occasional continuity errors, but very few. Changed the receiver priority in tvheadend so that receiver 2 is default - fine for the moment. Seems I have to wait for mainline kernel after all :-)

    Did you try the newest LibreELEC (Leia) v8.95.2 BETA?