[linux-dvb] WinTV Nova-T PCI 500 new issues (looks like a mt2060 issue)

Chris Murton chris.linuxtv at fruble.co.uk
Mon Aug 6 21:10:35 CEST 2007


Hi Trent,

Chris Murton wrote:
> Hi Trent,
> 
> Trent Piepho wrote:
>> On Mon, 6 Aug 2007, Chris Murton wrote:
>>> The aerial configuration has not changed, I have line of sight to the
>>> transmitter in question and dmesg looks reasonably healthy:
>>>
>>> dib0700: loaded with support for 5 different device-types
>>> usb 3-3: reset full speed USB device using ohci_hcd and address 2
>>> 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 frontend 0 (DiBcom 3000MC/P)...
>>> DVB: Unable to find symbol mt2060_attach()
>>> 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 frontend 1 (DiBcom 3000MC/P)...
>>> DVB: Unable to find symbol mt2060_attach()
>> That is your problem.  You didn't compile the mt2060 module, or it's not
>> installed, or your modprobe information is out of date (run depmod), or
>> your module utils version is too old (need 3.2).
> 
> Thanks for your pointers, I've just taken a look to check :-
> 
> basil:~# modinfo mt2060
> filename: 
> /lib/modules/2.6.21/kernel/drivers/media/dvb/frontends/mt2060.ko
> author:         Olivier DANET
> description:    Microtune MT2060 silicon tuner driver
> license:        GPL
> vermagic:       2.6.21 mod_unload
> depends:
> parm:           debug:Turn on/off debugging (default:off). (int)
> 
> It modprobes fine, but I don't get anything to say it's seen the tuner 
> in dmesg (which looking at the source code of mt2060.c, I should do) and 
> i still have no luck.
> 
> Should mt2060 be manually probed in at some point in the boot process?

Right, I just rolled back to the vanilla kernel modules instead of the 
latest mercurial sources, and..

dib0700: loaded with support for 2 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).
usb 3-3: reset full speed USB device using ohci_hcd and address 2
DVB: registering frontend 0 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb3:2
usbcore: registered new interface driver lirc_mceusb2
eth1: forcedeth.c: subsystem: 01043:816a bound to 0000:00:14.0
ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level, 
low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:10.1 to 64
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 frontend 1 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and 
connected.
usbcore: registered new interface driver dvb_usb_dib0700

And sure enough, tzap is happy:

basil:~# tzap -c 
/usr/share/doc/dvb-utils/examples/channels.conf-dvbt-crystal-palace "BBC 
ONE"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 505833333 Hz
video pid 0x0258, audio pid 0x0259
status 1f | signal a1e0 | snr 0000 | ber 001fffff | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal a1d5 | snr 0000 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal a1fd | snr 0000 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal a1db | snr 0000 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status 1f | signal a1d2 | snr 0000 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK

I just re-obtained the latest mercurial source and compiled, installed 
and rebooted to check the issue remained (and it does).

So it looks like an issue with the current v4l-dvb sources?

Thanks
Chris



More information about the linux-dvb mailing list