MihaiS

Totally understandable, thanks for your info. I guess i will have to wait then, or buy another device that is oficially supported

Yea I have seen some posts related to this but the bad part is none of them have a solution unfortunately. I have tried to debug this issue with Gemini and the answer i got so far is the following : "I tested the card=92 parameter, and while it successfully forced the driver to change its board profile from KWorld to PCTV, it still crashed in the exact same way during the USB transfer buffer pre-allocation. Here is the log after forcing the device with card=92: [ 2563.147430] em28xx 1-3:1.0: unknown em28xx chip ID (148) [ 2563.582550] em28xx 1-3:1.0: unknown eeprom format or eeprom corrupted ! [ 2563.646359] em28xx 1-3:1.0: Identified as PCTV DVB-S2 Stick (461e) (card=92) [ 2563.654866] em28xx 1-3:1.0: Binding DVB extension [ 2563.654869] em28xx 1-3:1.0: no endpoint for DVB mode and transfer type 0 [ 2563.654870] em28xx 1-3:1.0: failed to pre-allocate USB transfer buffers for DVB. It looks like because Chip ID 148 is completely missing from the em28xx source code (specifically in em28xx.h and em28xx-cards.c), the driver doesn't know how to query the physical endpoints for this newer revision of the Empia silicon. It panics and fails to allocate the USB buffers before the card= override can even be utilized. Would it be possible to patch the kernel source for the LibreELEC package to recognize Chip ID 148? It likely just needs to be mapped to one of the modern Empia chip architectures (like the em28174 or em28178) so it stops failing the initial hardware validation check."

I have done as requested: root@Tower:~# ls -ltrh /boot/config/modprobe.d/em28xx.conf -rw------- 1 root root 23 Jun 4 07:41 /boot/config/modprobe.d/em28xx.conf root@Tower:~# cat /boot/config/modprobe.d/em28xx.conf options em28xx card=92 root@Tower:~# ls -ltr /dev/dvb/ total 0 root@Tower:~# dmesg | grep -i -E "em28xx|dvb|firmware|2040" [ 8.025448] rc.S: Verifying boot/bzfirmware checksum ... tower-diagnostics-20260604-1055.zip

Is there any other log/diag that i can send in order to narrow down the issue ?

With LibreELEC was the only one that showed a message, but nothing more than that. Also it manages to mount /dev/dvb but it is empty.

Done, thanks tower-diagnostics-20260603-1714.zip

Hello, I have recently bought a Hauppauge WinTV-HVR-935 and I'm trying to get it to work. I installed the DVB-Driver plugin and went through all the 4 packages available with no luck at all. Here is the dmesg output that i'm getting: [ 505.655019] em28xx 1-3:1.0: New device HCW HVR-935 Audio @ 480 Mbps (2040:8360, interface 0, class 0) [ 505.655022] em28xx 1-3:1.0: Video interface 0 found: bulk isoc [ 505.705901] em28xx 1-3:1.0: unknown em28xx chip ID (148) [ 506.246622] em28xx 1-3:1.0: unknown eeprom format or eeprom corrupted ! [ 506.309829] em28xx 1-3:1.0: Identified as KWorld USB ATSC TV Stick UB435-Q V3 (card=93) [ 506.317902] em28xx 1-3:1.0: Binding DVB extension [ 506.317904] em28xx 1-3:1.0: no endpoint for DVB mode and transfer type 0 [ 506.317905] em28xx 1-3:1.0: failed to pre-allocate USB transfer buffers for DVB. Is there any solution to this issue currently that i might try ? Thank you