Two DVB-T Tuners in Lucid; neither works (Back to 4.1.2)
Posted: Sat 29 Jun 2013, 06:13
Back in early 2012 I eventually got the Nova T-500 DVB-T card working. My method was described here.
This was in puppy 4.1.2.
I am also interested in SDR so recently purchased a Ezcap USB DVB-T tuner.
Details are: Ezcap EzTV645 which has the rtl2832u chip and the FC0013 tuner. This site shows the following for my device ID of 0x0bda 0x2838: Tuner E4000. However the tuner, is in fact, a FC0013. Looking more closely at the information provided by Hardinfo the product ID is 0xbda 0x2838 i.e. not 0x0bda. Even more confused!
Now trying to get them working in Lucid.
No joy yet for the Ezcap as discussed here.
Is it DOA? The dvb-usb-rtl2832u.ko file exists in
/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl2832u.ko
so all seems to be good there at least.
To check I thought I would try the Nova. No joy here either. Check to see that the mt2060.ko file exists.
Yes, in
/lib/modules/2.6.33.2/kernel/drivers/media/common/tuners/mt2060.ko
Totally confused given that the Nova works a treat in 4.1.2.
For the sake of discussion I have part of the output from dmesg:
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
8139too 0000:00:10.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
eth0: RealTek RTL8139 at 0xf8534000, 00:18:4d:e9:9c:55, IRQ 19
DVB: registering adapter 0 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
DVB: registering adapter 1 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_rtl2832u
C-Media PCI 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
dib0700: loaded with support for 14 different device-types
dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 3 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0f.2/usb2/2-1/input/input5
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
Clues/ideas/suggestions please.
EDIT: I would be pleased if anyone with a working USB tuner in their PC would post the equivalent part of the dmesg output so that I may get some idea ...
TIA.
This was in puppy 4.1.2.
I am also interested in SDR so recently purchased a Ezcap USB DVB-T tuner.
Details are: Ezcap EzTV645 which has the rtl2832u chip and the FC0013 tuner. This site shows the following for my device ID of 0x0bda 0x2838: Tuner E4000. However the tuner, is in fact, a FC0013. Looking more closely at the information provided by Hardinfo the product ID is 0xbda 0x2838 i.e. not 0x0bda. Even more confused!
Now trying to get them working in Lucid.
No joy yet for the Ezcap as discussed here.
Is it DOA? The dvb-usb-rtl2832u.ko file exists in
/lib/modules/2.6.33.2/kernel/drivers/media/dvb/dvb-usb/dvb-usb-rtl2832u.ko
so all seems to be good there at least.
To check I thought I would try the Nova. No joy here either. Check to see that the mt2060.ko file exists.
Yes, in
/lib/modules/2.6.33.2/kernel/drivers/media/common/tuners/mt2060.ko
Totally confused given that the Nova works a treat in 4.1.2.
For the sake of discussion I have part of the output from dmesg:
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
8139too 0000:00:10.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
eth0: RealTek RTL8139 at 0xf8534000, 00:18:4d:e9:9c:55, IRQ 19
DVB: registering adapter 0 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
dvb-usb: found a 'RTL2832U DVB-T USB DEVICE' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (RTL2832U DVB-T USB DEVICE)
DVB: registering adapter 1 frontend 0 (Realtek RTL2832 DVB-T RTL2836 DTMB)...
dvb-usb: RTL2832U DVB-T USB DEVICE successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_rtl2832u
C-Media PCI 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
dib0700: loaded with support for 14 different device-types
dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 2 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
DVB: registering adapter 3 frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:0f.2/usb2/2-1/input/input5
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
Clues/ideas/suggestions please.
EDIT: I would be pleased if anyone with a working USB tuner in their PC would post the equivalent part of the dmesg output so that I may get some idea ...
TIA.