Dvbsky t330

It needs to be configured if it shows up as tuner C it is menu >> setup>> service scanning >> tuner configuration>>select tuner c >> set to cable >>configure virgin uk back to setup >> choose are you are in then exit and scan with autoboquetmaker
 
It needs to be configured if it shows up as tuner C it is menu >> setup>> service scanning >> tuner configuration>>select tuner c >> set to cable >>configure virgin uk back to setup >> choose are you are in then exit and scan with autoboquetmaker

Thanks for the tips, seems to be a driver issue old drivers no good with this stick, looking round seems to be a few issues with it, I will bite the bullet and buy another sundtek stick instead seems to be better quality.

Does work great on the pc with hadu cam on pc I will say though so not a total loss.
 
There is sure no issue with the DVBSky hardware, the 'issues' you may have recently read about are simply those of various makes/models of receiver which have updated to a newer kernel version meaning for those using the new images needing a later compiled driver (which has been done) and in this case a small update to E2 using vtuners (USB tuners in this case). This can often be the case with new kernel versions requiring driver updates as is the nature of Linux, however it looks like from kernel 3.18 we may see included DVBSky support so may even be a thing of past then...

Bottom line is though the T330 is working very well with the latest OpenViX and ViX4E2PROJECT images (for supported receivers) and I spent much time with DVBSky making sure this was the case, the E2 update mentioned will also be included in OpenATV very soon.

It's almost impossible to say if clone images will work or not as they are by their very nature a mix and match of kernel versions and drivers and there are different versions of clones, but I would guess until such times as support is built into the kernel this is unlikely to change, but shouldn't be confused with being a DVBSky hardware issue, rather a clone image issue, that of course highlights one of the downsides to clones meaning you have to be careful of what image you flash and so what else might or might not be supported, but that's most always been the nature of beast with clones I guess, the upside of course being the cost.
 
There is sure no issue with the DVBSky hardware, the 'issues' you may have recently read about are simply those of various makes/models of receiver which have updated to a newer kernel version meaning for those using the new images needing a later compiled driver (which has been done) and in this case a small update to E2 using vtuners (USB tuners in this case). This can often be the case with new kernel versions requiring driver updates as is the nature of Linux, however it looks like from kernel 3.18 we may see included DVBSky support so may even be a thing of past then...

Bottom line is though the T330 is working very well with the latest OpenViX and ViX4E2PROJECT images (for supported receivers) and I spent much time with DVBSky making sure this was the case, the E2 update mentioned will also be included in OpenATV very soon.

It's almost impossible to say if clone images will work or not as they are by their very nature a mix and match of kernel versions and drivers and there are different versions of clones, but I would guess until such times as support is built into the kernel this is unlikely to change, but shouldn't be confused with being a DVBSky hardware issue, rather a clone image issue, that of course highlights one of the downsides to clones meaning you have to be careful of what image you flash and so what else might or might not be supported, but that's most always been the nature of beast with clones I guess, the upside of course being the cost.

Lets keep it simple like sundtek, get the drivers on here so we can look at them and use them for this stick and the dvbsky family plugin, smells like they are trying to keep this stick for certain boxes.
 
Enigma2 is open source if you want these on certain boxes only use them on closed source boxes only, or make all the software available for us all to see.
 
Enigma2 might well be open source but that doesn't mean every third party piece of hardware you plug in there will have open source drivers, but all that's out there is available for those that care to look. You can't simply 'put the drivers on here', that wouldn't work, it's specific to the receiver and kernel version being used.

Until very recently DVBSky were not even aware there was a call for such a need for us here in Europe with USB tuners on E2 receivers hence they would provide driver support for Linux x86 only (and Windows). I put DVBSky in touch with OpenATV though and hence we have been able to get E2 support for the newer T330 and so any OE-A based image is easily capable of support, I know the VTi images (compiled from Vu+ sources) have also added support and chances are if built in kernel support is added from 3.18 then any images with this kernel version or later will work very easily...

As explained by the very nature of a clone image it would be impossible to say if it will be supported or not without owning the receiver and being able to look at the image but it's sure not something that's being held back for any specific images, that couldn't be further from the truth, the more the merrier!
 
Enigma2 might well be open source but that doesn't mean every third party piece of hardware you plug in there will have open source drivers, but all that's out there is available for those that care to look.

Until very recently DVBSky were not even aware there was a call for such a need for us here in Europe with USB tuners on E2 receivers hence they would provide driver support for Linux x86 only (and Windows). I put DVBSky in touch with OpenATV though and hence we have been able to get E2 support for the newer T330 and so any OE-A based image is easily capable of support, I know the VTi images (compiled from Vu+ sources) have also added support and chances are if built in kernel support is added from 3.18 then any images with this kernel version or later will work very easily...

As explained by the very nature of a clone image it would be impossible to say if it will be supported or not without owning the receiver and being able to look at the image but it's sure not something that's being held back for any specific images, that couldn't be further from the truth, the more the merrier!

Cheers bud, can you put links and all the software in downloads so we can tinker with it all?
 
Yep sure, you can find just the same as I've had access to at the following:

DVBSky Linux support, generally for x86 but Media Tree can be used for cross platform
Code:
You don't have permission to view the code content. Log in or register now.

More relevant to E2 support on the OE-Alliance git here including the all important sit2_op.o firmware file for mips processors - We don't get to see an open source version but they do provide us with this firmware file
Code:
You don't have permission to view the code content. Log in or register now.
 
thanks all compiled now working on a vu solo2 clone with old image of openpli, nice job.
 
thanks all compiled now working on a vu solo2 clone with old image of openpli, nice job.

It was a joke, this tuner will work on vuplus boxes but when you want to change back from satellite to cable on channels change the boxes will lock up, my advice on cable tuners is pay the bit extra for the sundtek one from Germany around 68quid with shipping at the moment they work perfect on any box I have tried and drivers and control centre on most plugins servers.
 
It works perfectly on my solo2 running Vix Apollo 121
Just download the dvb-usb-dvbsky driver from the feeds
Sent from my Blade S6 using Tapatalk
 
It works perfectly on my solo2 running Vix Apollo 121

Sent from my Blade S6 using Tapatalk

must be a dodgy tuner I was sold then, they are flimsy build quality. And I was told by the seller lavro is was a vuplus driver issue so seems I was bullshitted to as I heard they don't like replacing faulty products. Any running solo2 as a quad now with sundteks working flawless.
 
New Vu+ drivers where released yesterday (020315) which to quote Vu+ 'Fix DVB-T tuner detection in new E2 frontend'. I compiled a new ViX4E2PROJECT image for the Vu+ ZERO incorporating the new drivers and have been testing on the DVBSky T330 on DVB-C since around 8PM yesterday evening. I have left running all night and all is still working perfectly this morning, no issues at all with channel change and spinner appearing as with previous drivers, and most surely no issue at all with the build quality.

The infomation you were given was most surely not 'bullshit' hence the new driver release. I am compiling a new build for the Vu+ DUO2 to test as we speak but on the evidence of the ZERO I'm confident it will work. I only have ready access to these two models but will by trying to obtain a DUO and SOLO2 to test with over the next few days.

For anyone wanting to try with other Vu+ models then make sure you go for an image with the latest 020315 drivers and this should hopefully do the trick. I would imagine the latest OpenATV nightly builds will have these in as of today. My ViX4E2PROJECT Vu+ ZERO new build is available for download, I may also release for the DUO2 in the next day or two dependent on how testing goes, and likewise for a few more Vu+ models if and when I have access to them. If you are using clone receivers though I would guess it's probably not a good idea to try the new drivers yet, genuine hardware only.

As the large German distributor is now offering the the same T330 re-badged chances are we will see continued support for T330 drivers with Vu+ products for here on, they will have a much greater influence with Vu+ than you or I.
 
Hello,

I have a DVBSky T330 tuner, but not working with my Venton Unibox Eco+ receiver, the tuner not appears in the tuner list.
The kernel is 3.14.21, and the driver is enigma2-plugin-drivers-dvb-usb-dvbsky_2.0-r5_all.ipk from the plugins menu.
Please help!

The dmesg log:

usb 1-2: dvb_usb_v2: found a 'DVBSky T330 USB Stick' in warm state
usb 1-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (DVBSky T330 USB Stick)
dvbsky_usb MAC address=00:cc:10:a5:33:0c
usb 1-2: dvb_usb_v2: MAC address: 00:cc:10:a5:33:0c
vmalloc: allocation failure: 1479446464 bytes
modprobe: page allocation failure: order:0, mode:0xd2
CPU: 1 PID: 157 Comm: modprobe Tainted: GF O 3.14.21 #3
Stack : 00000000 00000001 0000011b 65646f6d 00000000 00000000 00000000 00000000
8088671a 00000040 80753a20 0000009d 00000001 00000000 807f8667 cdd042b0
80753a20 0000009d 00000001 80883814 cf5b1000 cf5b1000 00000000 806934fc
10008b03 8002d574 000000cc 00000000 80756d54 cdd57aac 00000000 00d57aac
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
Call Trace:
[<8000c16c>] show_stack+0x64/0x7c
[<806940d4>] dump_stack+0xc8/0xfc
[<800a47a0>] warn_alloc_failed+0xe4/0x124
[<800d4f04>] __vmalloc_node_range+0x174/0x260
[<800d527c>] vmalloc+0x40/0x4c
[<804f340c>] dvb_dmx_init+0x34/0x264
[<e162d414>] dvb_usbv2_probe+0x5bc/0xa90 [dvb_usb_v2]
[<80493518>] usb_probe_interface+0xf0/0x28c
[<803abd3c>] really_probe+0x9c/0x2e0
[<803ac0d8>] __driver_attach+0xd0/0xd8
[<803a9cf8>] bus_for_each_dev+0x6c/0xb4
[<803ab3a0>] bus_add_driver+0x17c/0x244
[<803ac5f0>] driver_register+0x84/0x12c
[<80492dbc>] usb_register_driver+0x88/0x1a4
[<800015fc>] do_one_initcall+0x158/0x1ec
[<8009818c>] load_module+0x1d78/0x2374
[<800988fc>] SyS_finit_module+0x88/0xa8
[<800116b4>] handle_sys+0x134/0x158

Mem-Info:
Normal per-cpu:
CPU 0: hi: 90, btch: 15 usd: 72
CPU 1: hi: 90, btch: 15 usd: 56
active_anon:105 inactive_anon:0 isolated_anon:0
active_file:306 inactive_file:2025 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
free:63785 slab_reclaimable:382 slab_unreclaimable:1464
mapped:225 shmem:1 pagetables:14 bounce:0
free_cma:0
Normal free:255140kB min:2144kB low:2680kB high:3216kB active_anon:420kB inactive_anon:0kB active_file:1224kB inactive_file:8100kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:524288kB managed:287904kB mlocked:0kB dirty:0kB writeback:0kB mapped:900kB shmem:4kB slab_reclaimable:1528kB slab_unreclaimable:5856kB kernel_stack:464kB pagetables:56kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 37*4kB (UM) 71*8kB (UEM) 31*16kB (UM) 13*32kB (UM) 5*64kB (UM) 4*128kB (UEM) 3*256kB (EM) 2*512kB (UM) 1*1024kB (M) 2*2048kB (UE) 60*4096kB (MR) = 255132kB
2351 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
131072 pages RAM
0 pages HighMem/MovableOnly
59096 pages reserved
usb 1-2: dvb_usb_v2: dvb_dmx_init() failed=-12
dvb_usb_dvbsky: probe of 1-2:1.0 failed with error -12
usbcore: registered new interface driver dvb_usb_dvbsky
NET: Registered protocol family 10
svc: failed to register lockdv1 RPC service (errno 124).
 
The DVBSky T330 tuner not working with the latest OpenViX image.
How can I cross compile the driver for my Venton Unibox Eco+ (kernel 3.14.21) step by step? I have an Ubuntu 12.04 system.
 
If this does not already work 'out the box' then you will need to contact Venton regarding this as it will be them that need to provide an update before this will work. I have no way of testing this I'm afraid, I know the receiver but have never owned nor have access to one.
 
Last edited:
What version of Openvix works the best with this tuner? It was running fine now I have updated to latest it is freezing box and I cant remember what version I was on previous :-(
 
What version of Openvix works the best with this tuner? It was running fine now I have updated to latest it is freezing box and I cant remember what version I was on previous :-(

What's the model of receiver you are using it with?
 
OK if it's a genuine SOLO2 then the latest OpenViX firmware should be good as it will have the latest drivers in from the start of this month (released 02/03) with better USB tuner support, the latest nightly OpenATV should also be the same. I don't unfortunatly have access to a SOLO2 to test, I do have a DUO2 though which I'll do my best to test with after the weekend.

If it's a clone SOLO2 then afraid I don't have the answer on that one, it'll all depend on the image and the drivers used.
 
Back
Top