81 replies to this topic

[WanWizard]

just an assumption:

enigma2-plugin-drivers-ct2-usb-dvbsky-t330 also provided a kernel module "dvb_usb_dvbsky" (in release 8.3)

 

I'll compare the two.

 

If 8.3 has that extra dependency, it probably means it auto-installs hmp-usb-dvb-t2-c-arm, as that provides that module according to the control file.

[WanWizard]

The dependency is there, but opkg doesn't see that hmp-usb-dvb-t2-c-arm provides that dependency, even though it is listed in its control file.

 

Maybe because it contains the kernel version?

Package: hmp-usb-dvb-t2-c-arm
Version: V160430-r1.3
Depends: kernel-module-dvb-usb-dvbsky-4.1.45-1.17, kernel-module-dvb-usb-v2-media-tree-4.1.45-1.17, kernel-module-dvbsky-m88ds3103-4.1.45-1.17, kernel-module-dvbsky-m88rs6000-4.1.45-1.17, kernel-module-sit2fe-4.1.45-1.17
Provides: kernel-module-dvb-usb-dvbsky-4.1.45-1.17, kernel-module-dvb-usb-v2-media-tree-4.1.45-1.17, kernel-module-dvbsky-m88ds3103-4.1.45-1.17, kernel-module-dvbsky-m88rs6000-4.1.45-1.17, kernel-module-sit2fe-4.1.45-1.17
Section: kernel/modules
Architecture: vuduo4k
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
MD5Sum: c74868003dbcb21afec1e87c07a65e02
Size: 76040
Filename: hmp-usb-dvb-t2-c-arm_V160430-r1.3_vuduo4k.ipk
Source: hmp-usb-dvb-t2-c-arm_160430.bb
Description: media tree drivers for hmp-usb-dvb-t2-c
OE: hmp-usb-dvb-t2-c-arm
HomePage: http://linuxtv.org/
License: GPLv2
Priority: optional

 

 

[paneologist]

with this installed I get a kernel oops while starting, enigma2 not coming up.

 stb1debuglog11.txt   83.42KB   0 downloads

2023-08-20T09:20:54+02:00 stb1.swabian.net kernel: [   21.852064] Unable to handle kernel NULL pointer dereference at virtual address 00000020
2023-08-20T09:20:54+02:00 stb1.swabian.net kernel: [   21.860202] pgd = c0003000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.862931] [00000020] *pgd=80000000004003, *pmd=00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.868388] Internal error: Oops: 207 [#1] SMP ARM
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.873184] Modules linked in: bluetooth ipv6 brcmfb(O) dvb_bcm7444(PO) dvb_base(PO) bcm_event(PO) procmk(O) sit2fe(O) sr_mod dvb_usb_dvbsky(O) dvb_usb_v2_media_tree(O) cdrom fuse
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.889371] CPU: 1 PID: 1519 Comm: kdvb-ad-1-fe--6 Tainted: P           O    4.1.45-1.17 #1
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.897731] Hardware name: Broadcom STB (Flattened Device Tree)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.903657] task: d64d5180 ti: d33b0000 task.ti: d33b0000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.909068] PC is at dvb_usb_fe_init+0x24/0x174 [dvb_usb_v2_media_tree]
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.915694] LR is at dvb_frontend_init+0x34/0xc4
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.920317] pc : [<bf02dfd4>]    lr : [<c046d544>]    psr: a0040013
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.920317] sp : d33b1ee0  ip : 00000000  fp : 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.931806] r10: 00000000  r9 : 00000000  r8 : bf031368
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.937036] r7 : 00000438  r6 : d6780000  r5 : d5e0c000  r4 : d6780000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.943570] r3 : fffffd80  r2 : 00000000  r1 : 000001da  r0 : d6780000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.950105] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.957420] Control: 30c5387d  Table: 131fcbc0  DAC: 55555555
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.963171] Process kdvb-ad-1-fe--6 (pid: 1519, stack limit = 0xd33b0210)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.969967] Stack: (0xd33b1ee0 to 0xd33b2000)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.974329] 1ee0: c0874880 d64d5180 d33b1f1c d6780000 d5e0c000 d6780000 d5e0c198 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.982516] 1f00: 00000000 c046d544 d53db740 c087868c d33b1f54 c05fe228 d6780000 c046eff4
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.990702] 1f20: 00000000 d5ed5d58 d5ed5d5c 00000001 c046efa0 d33b0000 00000000 d6780000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   21.998889] 1f40: c046efa0 d3d10f40 00000000 d6780000 c046efa0 00000000 00000000 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.007075] 1f60: 00000000 c0040bf8 d33b1f7c 00000000 d64d5180 d6780000 00000000 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.015261] 1f80: d33b1f80 d33b1f80 00000000 00000000 d33b1f90 d33b1f90 d33b1fac d3d10f40
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.023447] 1fa0: c0040b0c 00000000 00000000 c000ffa8 00000000 00000000 00000000 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.031633] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.039819] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 b89368a0 24f876eb
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.048018] [<bf02dfd4>] (dvb_usb_fe_init [dvb_usb_v2_media_tree]) from [<c046d544>] (dvb_frontend_init+0x34/0xc4)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.058383] [<c046d544>] (dvb_frontend_init) from [<c046eff4>] (dvb_frontend_thread+0x54/0x728)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.067094] [<c046eff4>] (dvb_frontend_thread) from [<c0040bf8>] (kthread+0xec/0xf4)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.074852] [<c0040bf8>] (kthread) from [<c000ffa8>] (ret_from_fork+0x14/0x2c)
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.082083] Code: e34b8f03 e3007438 e30011da e24dd00c (e5925020) 
2023-08-20T09:20:55+02:00 stb1.swabian.net kernel: [   22.088244] ---[ end trace ebe3633871aa0eaf ]---

but at least, the kernel module is loaded and used:

root@stb1:~# lsmod
Module                  Size  Used by
bluetooth             397033  4
ipv6                  289640  64
brcmfb                  1467  2
dvb_bcm7444          2002616  2 brcmfb
dvb_base             5478453  5 dvb_bcm7444
bcm_event               2899  5 dvb_bcm7444
procmk                  2104  2 dvb_bcm7444,bcm_event
sit2fe                 48194  1
sr_mod                 11676  0
dvb_usb_dvbsky          9423  1
dvb_usb_v2_media_tree    21220  1 dvb_usb_dvbsky
cdrom                  42256  1 sr_mod
fuse                   75343  3

 

 

[paneologist]

sounds funny:

[eRCDeviceInputDev] device "DVBSky T330 USB Stick" is a remotecontrol

and I see in the log, that the tuner becomes available :-) 1st time.

 

found this thread: https://www.tbsdtv.c...p?f=194&t=25022

might give a clue. someone had the same error and rebuilt some modules and then it worked.

or maybe some dependency missing?

Edited by paneologist, 20 August 2023 - 10:48.

[WanWizard]

No idea, I don't use USB tuners myself, and as this discussion proves again, more trouble than they're worth...

[paneologist]

it's so close...

where can I get in touch with the maintainer?

 

alternative solution would be a different DVB-T2 stick, which is guaranteed to work (without flaws) on the Vu+ Duo 4K SE - release and develop.

[WanWizard]

I've personally never seen a guaranteed good USB tuner solution.

 

The maintainer of what? VU+ doesn't have any developers active anymore, not since mid 2021...

[Dimitrij]

paneologist

I think it will work in the VTI image.

For Duo 4K SE multiboot available(install VTI).

 

https://forums.openp...-dvb-ct2-setup/

Edited by Dimitrij, 21 August 2023 - 17:45.

[paneologist]

I've personally never seen a guaranteed good USB tuner solution.

that's unfortunate. Anyone else having experience?

The maintainer of what? VU+ doesn't have any developers active anymore, not since mid 2021...

I meant the maintainer of the failing module dvb_usb_dvbsky. Hm. I assume it's not built specifically for set top boxes, but linux in general.
Only find references to it in gethub. Or is it that: https://github.com/t...usb-v2/dvbsky.c
or maybe better, the maintainer of the enigma2-package.

paneologist
I think it will work in the VTI image.
For Duo 4K SE multiboot available(install VTI).
 
https://forums.openp...-dvb-ct2-setup/

thanks for the tip. but seeking a solution specifically for OpenPLi.
Either make this work (nearly there. tuner gets found, but that kernel oops)
or find a working USB DVB-T2 stick.

Edited by paneologist, 23 August 2023 - 12:44.

[mimisiku]

I think it has absolutely nothing to do with OpenPli 8.3.. Just reconnected the DVB-C/T2 USB TurboSE v2 stick to the GigaBlue Trio 4K and rebooted into OpenPli 8.3. Downloaded the driver and rebooted again. Configured DVB-C (in my case Ziggo) and connected a coax to the USB tuner. Working fine… As extra proof I started a 5 minute recording and switched to another DVB-C channel from the list.. Both recording and live produced a perfect picture.. Amazingly the channel on the USB tuner decoded as well via OScam (I was told it would never because the ECM wouldn’t pass through USB)…

Driver used: ct2-usb-dvbsky-t330 (1.0-r0.3)

Attached Files

•  IMG_2321.jpeg   97.43KB   0 downloads
•  IMG_2319.png   195.71KB   0 downloads

Edited by mimisiku, 23 August 2023 - 13:24.

[WanWizard]

kernel_module_dvb_usb_dvbsky is part of the linux kernel, so maintained by Linus and friends .

 

But: VU+ doesn't use it, they use https://github.com/O...ipes-driver/hmp. These packages download a tarball from the VU+ servers, which contains (I presume patched) binary versions of the kernel driver.

 

Which means we can't do anything, we don't have the source.

[WanWizard]

I think it has absolutely nothing to do with OpenPli 8.3.. Just reconnected the DVB-C/T2 USB TurboSE v2 stick to the GigaBlue Trio 4K and rebooted into OpenPli 8.3. Downloaded the driver and rebooted again. Configured DVB-C (in my case Ziggo) and connected a coax to the USB tuner. Working fine… As extra proof I started a 5 minute recording and switched to another DVB-C channel from the list.. Both recording and live produced a perfect picture.. Amazingly the channel on the USB tuner decoded as well via OScam (I was told it would never because the ECM wouldn’t pass through USB)…

 

The problem is that VU+ has a custom / patched kernel-module-dvb-usb-dvbsky, with no idea why.

 

So the fact that it works on box A is no guarantee that it will work on box B too...

[paneologist]

I think it has absolutely nothing to do with OpenPli 8.3.. Just reconnected the DVB-C/T2 USB TurboSE v2 stick to the GigaBlue Trio 4K and rebooted into OpenPli 8.3. Downloaded the driver and rebooted again. Configured DVB-C (in my case Ziggo) and connected a coax to the USB tuner. Working fine… As extra proof I started a 5 minute recording and switched to another DVB-C channel from the list.. Both recording and live produced a perfect picture.. Amazingly the channel on the USB tuner decoded as well via OScam (I was told it would never because the ECM wouldn’t pass through USB)…
Driver used: ct2-usb-dvbsky-t330 (1.0-r0.3)

I do not doubt that it works on different boxes and or with other openPLi revisions. WanWizard already stated.
I still have hope. It also seems to work, as being detected as tuner. But that kernel oops.
 
tried again without rebooting. installed driver, loaded module, restarted enigma2.
tuner detected, but than that oops

[ 4789.159255] usb 4-1: dvb_usb_v2_media_tree: found a 'DVBSky T330 USB Stick' in warm state
[ 4789.167787] usb 4-1: dvb_usb_v2_media_tree: will pass the complete MPEG2 transport stream to the software demuxer
[ 4789.178282] DVB: registering new adapter (DVBSky T330 USB Stick)
[ 4789.185618] dvbsky_usb MAC address=00:cc:10:a5:33:0c
[ 4789.190599] usb 4-1: dvb_usb_v2_media_tree: MAC address: 00:cc:10:a5:33:0c
[ 4789.203462] usb 4-1: DVB: registering adapter 1 frontend -696754056 (Sit2 DVB-T2/C)...
[ 4789.211779] Registered IR keymap rc-dvbsky
[ 4789.216862] input: DVBSky T330 USB Stick as /devices/platform/rdb/f0470500.ehci_v2/usb4/4-1/rc/rc0/input1
[ 4789.226829] rc0: DVBSky T330 USB Stick as /devices/platform/rdb/f0470500.ehci_v2/usb4/4-1/rc/rc0
[ 4789.235916] usb 4-1: dvb_usb_v2_media_tree: schedule remote query interval to 300 msecs
[ 4789.243982] usb 4-1: dvb_usb_v2_media_tree: 'DVBSky T330 USB Stick' successfully initialized and connected
[ 4789.253819] usbcore: registered new interface driver dvb_usb_dvbsky
[ 4833.621405] [AUD]: AUDIO_STOP 0
[ 4833.624685] [AUD]: AUDIO_CONTINUE 0 0 aph=0x0
[ 4833.629072] [AUD]: AUDIO_CONTINUE aph=0 0 0
[ 4837.862545] [VID]: VIDEO_SET_STREAMTYPE 1
[ 4837.866695] [VID]: VIDEO_SELECT_SOURCE 1 0
[ 4837.872313] [VID]: VIDEO_PLAY 1 5 0
[ 4837.883469] [VID]: VIDEO_CONTINUE 1 1
[ 4837.887342] [VID]: VIDEO_CLEAR_BUFFER 1 1 0
[ 4838.048292] [VID]: VIDEO_STOP 0 1
[ 4838.052589] [VID]: VIDEO_SELECT_SOURCE 0 0
[ 4838.560993] >>cid=0, sid=0 r=4 s=0
[ 4838.601643] Unable to handle kernel NULL pointer dereference at virtual address 00000020
[ 4838.609761] pgd = c0003000
[ 4838.612484] [00000020] *pgd=80000000004003, *pmd=00000000
[ 4838.617933] Internal error: Oops: 207 [#1] SMP ARM
[ 4838.622730] Modules linked in: sit2fe(O) dvb_usb_dvbsky(O) dvb_usb_v2_media_tree(O) bluetooth ipv6 brcmfb(O) dvb_bcm7444(PO) dvb_base(PO) bcm_event(PO) procmk(O) sr_mod cdrom fuse
[ 4838.638919] CPU: 1 PID: 4418 Comm: kdvb-ad-1-fe--6 Tainted: P O 4.1.45-1.17 #1
[ 4838.647278] Hardware name: Broadcom STB (Flattened Device Tree)
[ 4838.653205] task: d64d4180 ti: d14f6000 task.ti: d14f6000
[ 4838.658616] PC is at dvb_usb_fe_init+0x24/0x174 [dvb_usb_v2_media_tree]
[ 4838.665243] LR is at dvb_frontend_init+0x34/0xc4
[ 4838.669867] pc : [<bf014fd4>] lr : [<c046d544>] psr: a00a0013
sp : d14f7ee0 ip : 00000000 fp : 00000000
[ 4838.681356] r10: 00000000 r9 : 00000000 r8 : bf018368
[ 4838.686585] r7 : 00000438 r6 : d16fd800 r5 : d147d800 r4 : d16fd800
[ 4838.693118] r3 : fffffd80 r2 : 00000000 r1 : 000001da r0 : d16fd800
[ 4838.699654] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 4838.706971] Control: 30c5387d Table: 10a25880 DAC: 55555555
[ 4838.712723] Process kdvb-ad-1-fe--6 (pid: 4418, stack limit = 0xd14f6210)
[ 4838.719517] Stack: (0xd14f7ee0 to 0xd14f8000)
[ 4838.723880] 7ee0: c0874880 d64d4180 c0874880 d16fd800 d147d800 d16fd800 d147d998 00000000
[ 4838.732067] 7f00: 00000000 c046d544 00000000 c087868c d14f7f54 c05fe228 d16fd800 c046eff4
[ 4838.740254] 7f20: 00000000 cc42fd58 cc42fd5c 00000001 c046efa0 d14f6000 00000000 d16fd800
[ 4838.748441] 7f40: c046efa0 d218fb00 00000000 d16fd800 c046efa0 00000000 00000000 00000000
[ 4838.756626] 7f60: 00000000 c0040bf8 d64e8ef0 00000000 d14f7f70 d16fd800 00000000 00000000
[ 4838.764813] 7f80: d14f7f80 d14f7f80 00000000 00000000 d14f7f90 d14f7f90 d14f7fac d218fb00
[ 4838.772999] 7fa0: c0040b0c 00000000 00000000 c000ffa8 00000000 00000000 00000000 00000000
[ 4838.781185] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 4838.789371] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[ 4838.797573] [<bf014fd4>] (dvb_usb_fe_init [dvb_usb_v2_media_tree]) from [<c046d544>] (dvb_frontend_init+0x34/0xc4)
[ 4838.807938] [<c046d544>] (dvb_frontend_init) from [<c046eff4>] (dvb_frontend_thread+0x54/0x728)
[ 4838.816651] [<c046eff4>] (dvb_frontend_thread) from [<c0040bf8>] (kthread+0xec/0xf4)
[ 4838.824408] [<c0040bf8>] (kthread) from [<c000ffa8>] (ret_from_fork+0x14/0x2c)
[ 4838.831640] Code: e34b8f01 e3007438 e30011da e24dd00c (e5925020)
[ 4838.837781] ---[ end trace 44ba2dfea25bd31b ]---

as what i've found internet searching about that, I believe some dependency is not satisfied. but cannot be sure about. what might it be.

unfortunately I don't have a build environment to test around with the kernel.

 

but as mentioned, I would be fine buying another dvb-t2 tuner stick - but don't want to waste more money, if it doesn't work.

 

edit, interesting similiar oops on rmmod
 

[ 5315.479794] usbcore: deregistering interface driver dvb_usb_dvbsky
[ 5315.491919] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[ 5315.500040] pgd = d0e213c0
[ 5315.502768] [00000000] *pgd=12149003, *pmd=a2d90003
[ 5315.507716] Internal error: Oops: 207 [#2] SMP ARM
[ 5315.512512] Modules linked in: sit2fe(O) dvb_usb_dvbsky(O-) dvb_usb_v2_media_tree(O) bluetooth ipv6 brcmfb(O) dvb_bcm7444(PO) dvb_base(PO) bcm_event(PO) procmk(O) sr_mod cdrom fuse
[ 5315.528786] CPU: 1 PID: 4434 Comm: rmmod Tainted: P      D    O    4.1.45-1.17 #1
[ 5315.536276] Hardware name: Broadcom STB (Flattened Device Tree)
[ 5315.542202] task: d6445080 ti: d5db4000 task.ti: d5db4000
[ 5315.547614] PC is at exit_creds+0x14/0x88
[ 5315.551632] LR is at __put_task_struct+0x40/0xfc
[ 5315.556254] pc : [<c00428ec>]    lr : [<c0024378>]    psr: 80080013
               sp : d5db5cb0  ip : 00000000  fp : d678668c
[ 5315.567743] r10: d678668c  r9 : fffffd80  r8 : d6785e50
[ 5315.572972] r7 : bf017758  r6 : 0000000b  r5 : d64d4188  r4 : d64d4180
[ 5315.579506] r3 : 00000000  r2 : 00000000  r1 : d64002c0  r0 : 00000000
[ 5315.586041] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[ 5315.593183] Control: 30c5387d  Table: 10e213c0  DAC: 55555555
[ 5315.598935] Process rmmod (pid: 4434, stack limit = 0xd5db4210)
[ 5315.604860] Stack: (0xd5db5cb0 to 0xd5db6000)
[ 5315.609221] 5ca0:                                     d64d4180 c0024378 d64d4180 d64d4188
[ 5315.617407] 5cc0: 0000000b c0040d48 d147d800 d16fd800 bf018368 bf017758 d6785e50 c046dff4
[ 5315.625593] 5ce0: d147d800 d16fd800 bf018368 c046e518 d5e86800 00000000 bf018368 d5dd9c00
[ 5315.633778] 5d00: c0010084 c047485c d6786000 d6786288 d6786000 bf014810 d69a7e80 c087fa00
[ 5315.641965] 5d20: d6786280 c006e01c d69a7f40 d6786000 d5dd9c00 bf57881c d5dd9c00 c0010084
[ 5315.650152] 5d40: d5de0c68 00000000 00038ef0 bf014a8c 200b0193 d5db5d68 d67d1868 d6598300
[ 5315.658337] 5d60: d5de3a80 d5dd9c2c d5de2014 d67d1870 d648db00 c088fc20 d5ddaa88 00000011
[ 5315.666523] 5d80: 00000007 00000000 c0898594 00000000 00000000 d5de0ca4 d5de0ca4 d6445080
[ 5315.674710] 5da0: 00000000 c08986e8 c0898dd8 00000000 00000000 00000000 00000082 000c000c
[ 5315.682896] 5dc0: d5dd9c88 d5de2070 7fffffff 00010001 d5de0ce0 d5de0ce0 00000000 00000000
[ 5315.691082] 5de0: 00000000 00000000 00000000 d69a43c0 c033af80 d5de0c68 ffffffff 00000000
[ 5315.699268] 5e00: ffffffe0 d5de0d14 d5de0d14 c033b4a8 00000000 d5de0d24 d5de0d24 00000002
[ 5315.707454] 5e20: 00000001 00000400 00000000 00000000 00000000 000007d0 0044803f 00000000
[ 5315.715639] 5e40: 00000000 fffb772e 00000000 00000000 00000000 00000000 d65ab118 00000000
[ 5315.723825] 5e60: 00000000 00000000 00000000 00000000 d5de0d80 d5de0d80 00000000 00000000
[ 5315.732011] 5e80: 00000000 00000000 00000000 00000000 0bd00181 00000000 00000000 d5de0dac
[ 5315.740197] 5ea0: d5de0dac 00000000 00000000 00000000 00000000 00000000 c0898958 00000000
[ 5315.748383] 5ec0: 00000000 00000000 d5dd9c20 bf5789c0 d5dd9c20 c03f2b34 d5dd89a8 bf5789c0
[ 5315.756568] 5ee0: 00000001 ffffffed d5de0c00 00000004 600b0013 d5dd9c20 bf5789c0 d5dd9c28
[ 5315.764754] 5f00: 00000081 c0010084 d5db4000 00000000 00038ef0 c03315b8 d5dd9c20 bf5789c0
[ 5315.772939] 5f20: d5dd9c54 c0331e64 bf5789c0 bf5789c0 bf57898c c03311c8 bf57898c c05fb11c
[ 5315.781125] 5f40: bf578c80 00000000 00000000 00000081 c0010084 c00887c0 d0558108 5f627664
[ 5315.789311] 5f60: 5f627375 73627664 0000796b 00000000 c08c409c d6445080 c0010084 d5db4000
[ 5315.797496] 5f80: 00038ef0 c003f2c0 d5db4000 c0010084 d5db5fb0 00000006 c0010084 00000000
[ 5315.805683] 5fa0: 00038190 c000ff00 00000000 00038190 00038f2c 00000800 b6f67754 00000000
[ 5315.813869] 5fc0: 00000000 00038190 00000000 00000081 be858ea4 00000002 00000001 00038ef0
[ 5315.822056] 5fe0: b6f30690 be858b7c 0001de6c b6f3069c 600b0010 00038f2c 00000000 00000000
[ 5315.830252] [<c00428ec>] (exit_creds) from [<c0024378>] (__put_task_struct+0x40/0xfc)
[ 5315.838094] [<c0024378>] (__put_task_struct) from [<c0040d48>] (kthread_stop+0x9c/0xa4)
[ 5315.846112] [<c0040d48>] (kthread_stop) from [<c046dff4>] (dvb_frontend_stop+0x60/0xc8)
[ 5315.854128] [<c046dff4>] (dvb_frontend_stop) from [<c046e518>] (dvb_unregister_frontend+0x3c/0x100)
[ 5315.863190] [<c046e518>] (dvb_unregister_frontend) from [<bf014810>] (dvb_usbv2_mediatree_exit+0xb4/0x2d0 [dvb_usb_v2_media_tree])
[ 5315.874947] [<bf014810>] (dvb_usbv2_mediatree_exit [dvb_usb_v2_media_tree]) from [<bf014a8c>] (dvb_usbv2_mediatree_disconnect+0x60/0xb4 [dvb_usb_v2_media_tree])
[ 5315.889311] [<bf014a8c>] (dvb_usbv2_mediatree_disconnect [dvb_usb_v2_media_tree]) from [<c03f2b34>] (usb_unbind_interface+0x80/0x2a8)
[ 5315.901326] [<c03f2b34>] (usb_unbind_interface) from [<c03315b8>] (__device_release_driver+0x94/0x108)
[ 5315.910645] [<c03315b8>] (__device_release_driver) from [<c0331e64>] (driver_detach+0xb0/0xd0)
[ 5315.919268] [<c0331e64>] (driver_detach) from [<c03311c8>] (bus_remove_driver+0x60/0xd4)
[ 5315.927370] [<c03311c8>] (bus_remove_driver) from [<c05fb11c>] (usb_deregister+0x64/0xcc)
[ 5315.935563] [<c05fb11c>] (usb_deregister) from [<c00887c0>] (SyS_delete_module+0x158/0x1f8)
[ 5315.943927] [<c00887c0>] (SyS_delete_module) from [<c000ff00>] (ret_fast_syscall+0x0/0x3c)
[ 5315.952201] Code: e1a04000 e3a03000 e59022e8 e59002e4 (e5922000) 
[ 5315.958369] ---[ end trace 44ba2dfea25bd31c ]---

 

Edited by paneologist, 23 August 2023 - 13:46.

[mimisiku]

 

 

The problem is that VU+ has a custom / patched kernel-module-dvb-usb-dvbsky, with no idea why.

Why continuously referring to dvbsky as it is the wrong device.. The hmp version is used for the Turbo v2 (that old black brick). The dvbsky-t330 is completely different! But you are right about one thing; they did patch it for the older Mipsel boxes running kernel 3.14 (if memory serves me right)

It requires kernel 3.15> so even on the VU+Ultimo4K it couldn’t work… The Duo4K (not the SE) has a 4.x kernel which should work, I don’t own a VU+Duo4Kse so I don’t know which kernel it has…

[WanWizard]

Both use the kernel-module-dvb-usb-dvbsky driver.

 

In the VU+ kernel defconfig, building this driver from the kernel source is blocked, but is instead built from source from dvbsky.net and patched. So all devices, including the dvbsky-t330, will use this custom module.

Edited by WanWizard, 23 August 2023 - 14:06.

[mimisiku]

Ahh, that’s clear… So dvb-usb-dvbsky is considered the core?

[WanWizard]

It is a standard linux kernel module since 3.18: https://cateee.net/l...USB_DW2102.html

[paneologist]

got a cheap used OPTI-Combo DVB-T2/C USB Stick.
Seems to be the same hardware "Bus 004 Device 002: ID 0572:0320 Conexant Systems (Rockwell), Inc. DVBSky T330 DVB-T2/C tuner" :-(

 

but the package enigma2-plugin-drivers-dvb-usb-opticombo doesn't have "hmp-usb-dvb-t2-c-arm" as dependency either:

Package: enigma2-plugin-drivers-dvb-usb-opticombo
Version: 2.0-r6
Recommends: kernel-module-si2168, kernel-module-dvbsky-m88rs6000, firmware-dvb-usb-s660, firmware-dvb-fe-ds3000, kernel-module-dvb-usb-dvbsky, kernel-module-dvb-usb-v2, kernel-module-dvbsky-m88ds3103, firmware-dvb-fe-si2168, kernel-module-si2157, kernel-module-sit2fe, firmware-dvb-fe-ds3xxx
Status: install ok installed

both kernel-module-dvb-usb-dvbsky, kernel-module-dvb-usb-v2 aren't available in the feeds for the box in develop image.

 

any chance, that one of these packages contain something, what hmp-usb-dvb-t2-c-arm doesn't?

[WanWizard]

No, because the meta package is generic, for all boxes, while VU+ is the only brand that has disabled the standard kernel driver to do something different for their own devices.

 

Perhaps someone should test both VU+ USB tuners on a non-VU+ box. If those work, we should remove the hmp drivers from the bsp and reinstate the original kernel drivers (for the kernel versions that support it).

[paneologist]

No, because the meta package is generic, for all boxes, while VU+ is the only brand that has disabled the standard kernel driver to do something different for their own devices.

now I understood

Perhaps someone should test both VU+ USB tuners on a non-VU+ box. If those work, we should remove the hmp drivers from the bsp and reinstate the original kernel drivers (for the kernel versions that support it).

that sounds like a good way to go.
mimisiku tried the T330 on GigaBlue Trio 4K working
don't know anything about the other Vu+ stick