This board is now closed. The Blackhole image ended in 2020. The board will remain available in Read Only Mode, so all the posts from the last 15+ years are not lost. We thank you for being part of the community for the last 15+ years. You can join the OpenBh board if you have not already done so at www.openbh.net.

USB dual Tuner

D

developer69

Vu+ Newbie
Hello, I had a REDI PC 100 USB tuner for 2 years and had no problems at all.

But this USB tuner stopped working. I think is dead. So I have to buy another USB tuner to see terrestrial channels.

I would like now to buy a USB dual tuner. What USB dual tuners are supported on latest black hole image?

Please suggest me a USB dual tuner to buy. Not very expensive please.

Thanks you.
 
developer69 said:
Hello, I had a REDI PC 100 USB tuner for 2 years and had no problems at all.

But this USB tuner stopped working. I think is dead. So I have to buy another USB tuner to see terrestrial channels.

I would like now to buy a USB dual tuner. What USB dual tuners are supported on latest black hole image?

Please suggest me a USB dual tuner to buy. Not very expensive please.

Thanks you.
Click to expand...

Hauppauge WinTV Nova-TD device
 
Hi again, I just tested my crypto redi pc 250.

Worked but not very well.

Some times when I am zapping the tuner stop working. The only solution to work again is to reboot complete the Vu+ Duo.

Can you help me find a solution?
 
I am posting the lsusb:

root@bm750:~# lsusb
Bus 001 Device 002: ID 0951:1607
Bus 001 Device 003: ID 15a4:9016
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001

and the dmesg is in uploaded file...
 

Attachments

developer69 said:
Any help? Please..
Click to expand...

I've seen your dmesg but it's correct without errors.
I can only suppose there is some problems around your power supply for USB devices and your dual tuner device needs more power to work properly.
Try with a pwoered hub USB. I haven't a device with your specs but I've two devices with same hardware (single tuner). I can try with them if all works correctly for some time.
 
Hmm... I have to find a powered usb hub to test it.

angelofsky1980, I just put out the usb tuner and pluged in again to get dmesg again.

Please see again my dmesg again:
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=2
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d507 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d330 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d507 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d330 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d417 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=2
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c wr failed=-19 reg=d417 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
mxl5007t_soft_reset: 521: failed!
mxl5007t_tuner_init: error -140 on line 535
mxl5007t_set_params: error -140 on line 667
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
 
developer69 said:
Hmm... I have to find a powered usb hub to test it.

angelofsky1980, I just put out the usb tuner and pluged in again to get dmesg again.

Please see again my dmesg again:
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=2
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d507 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d330 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d507 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d330 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d417 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c rd failed=-19 reg=d07c len=2
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
i2c i2c-0: af9013: i2c wr failed=-19 reg=d417 len=1
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
mxl5007t_soft_reset: 521: failed!
mxl5007t_tuner_init: error -140 on line 535
mxl5007t_set_params: error -140 on line 667
usb 1-2: dvb_usb_v2: usb_bulk_msg() failed=-19
Click to expand...

Ok these errors are more specific.
 
Do you see (understand) on these specific errors that I need to buy a USB hub with external power or not?

I you have in mind what could be the problem please tell me because I have no usb hub and I would like not to buy one for nothing.

Thank you very much for your help.
 
Hi angelofsky1980.

I borrowed a USB hub powered by AC Adapter but the results is the same.
The USB tuner still failed after some zapping. No image until reboot.

I just wondered if you can make a script that can unload the modules, stop the usbtuner and start them all again. This way I can execute this script, so the wait time to start the tuner will be less that waiting to reboot the vu+ duo.

I am waiting for your support, thank you.
 
You must log in or register to reply here.
Back
Top