Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DVB-C Terratec Cinergy HTC 00b2 - drxk & em28xx errors #4243

Open
ChrizZz90 opened this issue Mar 28, 2021 · 4 comments
Open

DVB-C Terratec Cinergy HTC 00b2 - drxk & em28xx errors #4243

ChrizZz90 opened this issue Mar 28, 2021 · 4 comments

Comments

@ChrizZz90
Copy link

ChrizZz90 commented Mar 28, 2021

Describe the bug
Using a DVB-C/T Terratec Cinergy HTC USB device (0ccd:00b2) with TVHeadend is causing endless error messages and spams the logs. I have 2 sticks and I tested them on 2 Raspi4 (with different kernel versions), but the result is the same. It doesn't matter to install the firmware, using an external powered USB-Hub or change the power adapter. I tried the official one and another one with more power.
My goal is to use both on 1 Raspi4, but doing this now is causing new error messages in seconds and after some time the Raspi4 umounts all USB devices. Especially the umount behavior is critical for me because my goal is to have OMV running on the Raspi4, too.
Maybe it is similar to #3631
Based on this overview I guess this device should be supported.

To reproduce
Install TVHeadend, plug in the USB DVB-C device (downloading the firmware doesn't change anything) and start the channel search or play a channel in TVHeadend. As soon as the DVB-C device is in use, errors appear.

Actual behaviour
How the syslog looks after plugging the device in:

Mar 29 00:43:55 raspberrypi kernel: [ 2195.187491] usb 1-1.1: new high-speed USB device number 5 using xhci_hcd
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498546] usb 1-1.1: config 1 interface 0 altsetting 1 endpoint 0x82 has invalid wMaxPacketSize 0
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498896] usb 1-1.1: New USB device found, idVendor=0ccd, idProduct=00b2, bcdDevice= 1.00
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498905] usb 1-1.1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498913] usb 1-1.1: Product: Cinergy HTC Stick
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498921] usb 1-1.1: Manufacturer: TERRATEC 
Mar 29 00:43:55 raspberrypi kernel: [ 2195.498928] usb 1-1.1: SerialNumber: 123456789ABCD
Mar 29 00:43:55 raspberrypi kernel: [ 2195.500116] em28xx 1-1.1:1.0: New device TERRATEC  Cinergy HTC Stick @ 480 Mbps (0ccd:00b2, interface 0, class 0)
Mar 29 00:43:55 raspberrypi kernel: [ 2195.500126] em28xx 1-1.1:1.0: Audio interface 0 found (Vendor Class)
Mar 29 00:43:55 raspberrypi kernel: [ 2195.500134] em28xx 1-1.1:1.0: Video interface 0 found: isoc
Mar 29 00:43:55 raspberrypi kernel: [ 2195.500141] em28xx 1-1.1:1.0: DVB interface 0 found: isoc
Mar 29 00:43:55 raspberrypi kernel: [ 2195.577540] em28xx 1-1.1:1.0: chip ID is em2884
Mar 29 00:43:55 raspberrypi kernel: [ 2195.653890] em28xx 1-1.1:1.0: EEPROM ID = 26 00 00 00, EEPROM hash = 0xfebadddc
Mar 29 00:43:55 raspberrypi kernel: [ 2195.653899] em28xx 1-1.1:1.0: EEPROM info:
Mar 29 00:43:55 raspberrypi kernel: [ 2195.653907] em28xx 1-1.1:1.0: 	microcode start address = 0x0004, boot configuration = 0x00
Mar 29 00:43:56 raspberrypi kernel: [ 2195.660309] em28xx 1-1.1:1.0: 	I2S audio, 5 sample rates
Mar 29 00:43:56 raspberrypi kernel: [ 2195.660317] em28xx 1-1.1:1.0: 	500mA max power
Mar 29 00:43:56 raspberrypi kernel: [ 2195.660326] em28xx 1-1.1:1.0: 	Table at offset 0x27, strings=0x249a, 0x1c6a, 0x1486
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727491] em28xx 1-1.1:1.0: Identified as Terratec Cinergy HTC Stick (card=82)
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727503] em28xx 1-1.1:1.0: Currently, V4L2 is not supported on this model
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727516] em28xx 1-1.1:1.0: dvb set to isoc mode.
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727586] em28xx 1-1.1:1.0: Binding audio extension
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727594] em28xx 1-1.1:1.0: em28xx-audio.c: Copyright (C) 2006 Markus Rechberger
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727602] em28xx 1-1.1:1.0: em28xx-audio.c: Copyright (C) 2007-2016 Mauro Carvalho Chehab
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727889] em28xx 1-1.1:1.0: Endpoint 0x83 high-speed on intf 0 alt 7 interval = 8, size 196
Mar 29 00:43:56 raspberrypi kernel: [ 2195.727897] em28xx 1-1.1:1.0: Number of URBs: 1, with 64 packets and 192 size
Mar 29 00:43:56 raspberrypi kernel: [ 2195.733755] em28xx 1-1.1:1.0: Audio extension successfully initialized
Mar 29 00:43:56 raspberrypi kernel: [ 2195.733770] em28xx 1-1.1:1.0: Binding DVB extension
Mar 29 00:43:56 raspberrypi mtp-probe: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Mar 29 00:43:56 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP device
Mar 29 00:43:56 raspberrypi mtp-probe: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1"
Mar 29 00:43:56 raspberrypi mtp-probe: bus: 1, device: 5 was not an MTP device
Mar 29 00:43:56 raspberrypi systemd-udevd[10263]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
Mar 29 00:43:56 raspberrypi kernel: [ 2196.332715] drxk: status = 0x639260d9
Mar 29 00:43:56 raspberrypi kernel: [ 2196.332725] drxk: detected a drx-3926k, spin A3, xtal 20.250 MHz
Mar 29 00:44:00 raspberrypi kernel: [ 2200.341243] drxk: DRXK driver version 0.9.4300
Mar 29 00:44:00 raspberrypi kernel: [ 2200.372237] drxk: frontend initialized.
Mar 29 00:44:00 raspberrypi kernel: [ 2200.372257] tda18271 12-0060: creating new instance
Mar 29 00:44:00 raspberrypi kernel: [ 2200.374063] tda18271: TDA18271HD/C2 detected @ 12-0060
Mar 29 00:44:01 raspberrypi kernel: [ 2200.838664] dvbdev: DVB: registering new adapter (1-1.1:1.0)
Mar 29 00:44:01 raspberrypi kernel: [ 2200.838678] em28xx 1-1.1:1.0: DVB: registering adapter 0 frontend 0 (DRXK DVB-C DVB-T)...
Mar 29 00:44:01 raspberrypi kernel: [ 2200.838695] dvbdev: dvb_create_media_entity: media entity 'DRXK DVB-C DVB-T' registered.
Mar 29 00:44:01 raspberrypi kernel: [ 2200.840106] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843171] em28xx 1-1.1:1.0: DVB extension successfully initialized
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843195] em28xx 1-1.1:1.0: Registering input extension
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843436] Registered IR keymap rc-nec-terratec-cinergy-xs
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843683] rc rc0: Terratec Cinergy HTC Stick as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/rc/rc0
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843793] rc rc0: lirc_dev: driver em28xx registered at minor = 0, scancode receiver, no transmitter
Mar 29 00:44:01 raspberrypi kernel: [ 2200.843890] input: Terratec Cinergy HTC Stick as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/rc/rc0/input1
Mar 29 00:44:01 raspberrypi kernel: [ 2200.844001] em28xx 1-1.1:1.0: Input extension successfully initialized
Mar 29 00:44:01 raspberrypi kernel: [ 2200.965624] tda18271: performing RF tracking filter calibration
Mar 29 00:44:01 raspberrypi systemd-udevd[10277]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Mar 29 00:44:03 raspberrypi kernel: [ 2203.257110] tda18271: RF tracking filter calibration complete
Mar 29 00:44:03 raspberrypi kernel: [ 2203.257182] em28xx 1-1.1:1.0: DVB: adapter 0 frontend 0 frequency 0 out of range (47000000..864000000)
Mar 29 00:44:03 raspberrypi tvheadend[538]: linuxdvb: adapter added /dev/dvb/adapter0
Mar 29 00:44:03 raspberrypi tvheadend[538]: linuxdvb: adapter 0 setting exclusive flag

But as soon as I use the device with TVHeadend:

Mar 29 00:48:06 raspberrypi tvheadend[538]: http: 192...: using ticket E8843BC38E3603A4A282677A4EA0783EAE4D74BC for /stream/channel/f0cb4698281173175b8cc870dd6b256a
Mar 29 00:48:06 raspberrypi tvheadend[538]: mpegts: 114MHz in DVB-C Network - tuning on DRXK DVB-C DVB-T #0 : DVB-C #0
Mar 29 00:48:06 raspberrypi tvheadend[538]: subscription: 008C: "HTTP" subscribing on channel "SAT.1", weight: 100, adapter: "DRXK DVB-C DVB-T #0 : DVB-C #0", network: "DVB-C Network", mux: "114MHz", provider: "Unitymedia", service: "SAT.1", profile="pass", hostname="192...", client="VLC/3.0.12 LibVLC/3.0.12"
Mar 29 00:48:09 raspberrypi tvheadend[538]: mpegts: mux 114MHz in DVB-C Network old params DVB-C freq 114000000 sym 6900000 mod QAM/256 fec NONE ds 0 plp -1 (00020000)
Mar 29 00:48:09 raspberrypi tvheadend[538]: mpegts: mux 114MHz in DVB-C Network new params DVB-C freq 114000000 sym 6900000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000)
Mar 29 00:48:19 raspberrypi kernel: [ 2459.636774] drxk: ERROR: -32000
Mar 29 00:48:19 raspberrypi kernel: [ 2459.636774]  while sending cmd 0x0205 with params:
Mar 29 00:48:19 raspberrypi kernel: [ 2459.636783] drxk: Error -22 on get_qam_lock_status
Mar 29 00:48:19 raspberrypi kernel: [ 2459.636791] drxk: Error -22 on get_lock_status
Mar 29 00:48:21 raspberrypi tvheadend[538]: TS: DVB-C Network/114MHz/SAT.1 Transport error indicator (total 1)
Mar 29 00:48:21 raspberrypi tvheadend[538]: tbl-pass: pass-eit: -: invalid checksum (len 2865, errors 1)
Mar 29 00:49:14 raspberrypi kernel: [ 2513.805034] drxk: ERROR: -32000
Mar 29 00:49:14 raspberrypi kernel: [ 2513.805034]  while sending cmd 0x0205 with params:
Mar 29 00:49:14 raspberrypi kernel: [ 2513.805043] drxk: Error -22 on get_qam_lock_status
Mar 29 00:49:14 raspberrypi kernel: [ 2513.805051] drxk: Error -22 on get_lock_status
Mar 29 00:49:16 raspberrypi kernel: [ 2515.805226] drxk: ERROR: -32000
Mar 29 00:49:16 raspberrypi kernel: [ 2515.805226]  while sending cmd 0x0205 with params:
Mar 29 00:49:16 raspberrypi kernel: [ 2515.805238] drxk: Error -22 on get_qam_lock_status
Mar 29 00:49:16 raspberrypi kernel: [ 2515.805249] drxk: Error -22 on get_lock_status
Mar 29 00:49:18 raspberrypi kernel: [ 2518.437608] drxk: ERROR: -32000
Mar 29 00:49:18 raspberrypi kernel: [ 2518.437608]  while sending cmd 0x0205 with params:
Mar 29 00:49:18 raspberrypi kernel: [ 2518.437616] drxk: Error -22 on get_qam_lock_status
Mar 29 00:49:18 raspberrypi kernel: [ 2518.437624] drxk: Error -22 on get_lock_status
...
Mar 29 00:55:01 raspberrypi kernel: [ 2860.849255] em28xx 1-1.1:1.0: write to i2c device at 0x52 failed with unknown error (status=17)
Mar 29 00:55:01 raspberrypi kernel: [ 2860.849273] drxk: i2c read error at addr 0x29

System

I had to stop the output because it provides all of the errors again.

pi@raspberrypi:/lib/firmware $ raspinfo
System Information

Raspberry Pi 4 Model B Rev 1.2
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"

Raspberry Pi reference 2020-08-20
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 9a3a10bf1019ebb2d59053564dc6b90068bad27d, stage4

Linux raspberrypi 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux
Revision : c03112
Serial : 10000000693f2381
Model : Raspberry Pi 4 Model B Rev 1.2
Throttled flag : throttled=0x0
Camera : supported=0 detected=0

Videocore information

Feb 25 2021 12:10:40
Copyright (c) 2012 Broadcom
version 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (release) (start)

alloc failures: 0
compactions: 0
legacy block fails: 0

Filesystem information

Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
/dev/root 29384700 7057752 20811224 26% /
devtmpfs 1827468 0 1827468 0% /dev
tmpfs 1959564 0 1959564 0% /dev/shm
tmpfs 1959564 16948 1942616 1% /run
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1959564 0 1959564 0% /sys/fs/cgroup
/dev/mmcblk0p1 258095 48782 209314 19% /boot
tmpfs 391912 0 391912 0% /run/user/1000

Filename Type Size Used Priority
/var/swap file 102396 0 -2

Package version information

raspberrypi-ui-mods:
Installiert: 1.20201210+nmu1
raspberrypi-sys-mods:
Installiert: 20210310
openbox:
Installiert: 3.6.1-8+rpt5
lxpanel:
Installiert: 0.10.0-2+rpt15
pcmanfm:
Installiert: 1.3.1-1+rpt27
rpd-plym-splash:
Installiert: 0.26

Networking Information

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether m.m.m.m txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet x.x.x.x netmask x.x.x.x
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Lokale Schleife)
RX packets 872767 bytes 141408257 (134.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 872767 bytes 141408257 (134.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet x.x.x.x netmask x.x.x.x broadcast x.x.x.x
inet6 y::y.y.y.y prefixlen 64 scopeid 0x20
inet6 y.y.y.y.y.y.y.y prefixlen 64 scopeid 0x0
inet6 2a02:8070:6186:y::y.y.y.y prefixlen 128 scopeid 0x0
ether m.m.m.m txqueuelen 1000 (Ethernet)
RX packets 111379 bytes 29013181 (27.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 411139 bytes 475133028 (453.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

USB Information

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=em28xx, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M

config.txt

arm_freq=1500
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=500
core_freq_min=200
disable_commandline_tags=2
disable_l2cache=1
disable_overscan=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
dvfs=2
enable_gic=1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=500
gpu_freq_min=250
init_uart_clock=0x2dc6c00
lcd_framerate=60
mask_gpu_interrupt0=1024
mask_gpu_interrupt1=0x10000
max_framebuffers=2
over_voltage_avs=-42500
pause_burst_frames=1
program_serial_random=1
total_mem=4096
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
hdmi_pixel_freq_limit:0=0x11e1a300
hdmi_pixel_freq_limit:1=0x11e1a300
device_tree=-
overlay_prefix=overlays/
hdmi_cvt:0=
hdmi_cvt:1=
hdmi_edid_filename:0=
hdmi_edid_filename:1=
hdmi_timings:0=
hdmi_timings:1=

cmdline.txt

coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:AC:E8:E4 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=56f8aff7-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles

raspi-gpio settings

BANK0 (GPIO 0 to 27):
GPIO 0: level=1 fsel=0 func=INPUT pull=UP
GPIO 1: level=1 fsel=0 func=INPUT pull=UP
GPIO 2: level=1 fsel=0 func=INPUT pull=UP
GPIO 3: level=1 fsel=0 func=INPUT pull=UP
GPIO 4: level=1 fsel=0 func=INPUT pull=UP
GPIO 5: level=1 fsel=0 func=INPUT pull=UP
GPIO 6: level=1 fsel=0 func=INPUT pull=UP
GPIO 7: level=1 fsel=0 func=INPUT pull=UP
GPIO 8: level=1 fsel=0 func=INPUT pull=UP
GPIO 9: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 10: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 11: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 12: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 13: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 14: level=1 fsel=0 func=INPUT pull=NONE
GPIO 15: level=1 fsel=0 func=INPUT pull=UP
GPIO 16: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 17: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 18: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 19: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 20: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 21: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 22: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 23: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 24: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 25: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 26: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 27: level=1 fsel=0 func=INPUT pull=DOWN
BANK1 (GPIO 28 to 45):
GPIO 28: level=1 fsel=2 alt=5 func=RGMII_MDIO pull=UP
GPIO 29: level=0 fsel=2 alt=5 func=RGMII_MDC pull=DOWN
GPIO 30: level=0 fsel=7 alt=3 func=CTS0 pull=UP
GPIO 31: level=0 fsel=7 alt=3 func=RTS0 pull=NONE
GPIO 32: level=1 fsel=7 alt=3 func=TXD0 pull=NONE
GPIO 33: level=1 fsel=7 alt=3 func=RXD0 pull=UP
GPIO 34: level=1 fsel=7 alt=3 func=SD1_CLK pull=NONE
GPIO 35: level=1 fsel=7 alt=3 func=SD1_CMD pull=UP
GPIO 36: level=1 fsel=7 alt=3 func=SD1_DAT0 pull=UP
GPIO 37: level=1 fsel=7 alt=3 func=SD1_DAT1 pull=UP
GPIO 38: level=1 fsel=7 alt=3 func=SD1_DAT2 pull=UP
GPIO 39: level=1 fsel=7 alt=3 func=SD1_DAT3 pull=UP
GPIO 40: level=0 fsel=4 alt=0 func=PWM1_0 pull=NONE
GPIO 41: level=0 fsel=4 alt=0 func=PWM1_1 pull=NONE
GPIO 42: level=0 fsel=1 func=OUTPUT pull=UP
GPIO 43: level=1 fsel=0 func=INPUT pull=UP
GPIO 44: level=1 fsel=0 func=INPUT pull=UP
GPIO 45: level=1 fsel=0 func=INPUT pull=UP
BANK2 (GPIO 46 to 53):
GPIO 46: level=0 fsel=0 func=INPUT pull=UP
GPIO 47: level=0 fsel=0 func=INPUT pull=UP
GPIO 48: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 49: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 50: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 51: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 52: level=0 fsel=0 func=INPUT pull=DOWN
GPIO 53: level=0 fsel=0 func=INPUT pull=DOWN

@ChrizZz90
Copy link
Author

@6by9 do you think your comment 3 years ago might solve my issue? I can't see what "pi_patches/rpi-4.14.y-hauppauge" is. Seems like the link to it doesn't work any more.

I also tried to build a new kernel based on linuxtv media build, but after that every other module like Docker, File System Quota or NFS didn't work any more.

@ChrizZz90
Copy link
Author

I am still trying to find a solution and did a test with the Hauppauge DualHD device. I get the same errors like the guys in the support board. It looks like Raspberry Pi (4?) has issues with DVB-C or DVB-T devices in general?!

@Max11223344
Copy link

exactly my problem ....
It still happens on Raspi 4 with updated version: uname -a
Linux raspberrypi 5.10.52-v7l+ #1441 SMP Tue Aug 3 18:11:56 BST 2021 armv7l GNU/Linux.

And -of course (?) - no problems on Pi 3b+ ... :(

@ChrizZz90
Copy link
Author

well, I solved this issue just by testing lots of different devices. There are chips that work and I am using now this one: August DVB-T230 - I don't have errors, sometimes they appear and I have to plug the devices in again and I do a restart of my Pi4.

Oh, one thing I need to add: Yes it is a DVB-T device but DVB-C is also working ;)

Same answer as in #3631

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants