Hi,
I bought the same usb stick at Conrad (usb id: 2040:7070).
Using current drivers (ver 6690) and changing the usb product id as
Sebastian did produces the following syslog output:
usb 3-4: new high speed USB device using ehci_hcd and address 57
usb 3-4: new device found, idVendor=2040, idProduct=7070
usb 3-4: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 3-4: Product: Nova-T Stick
usb 3-4: Manufacturer: Hauppauge
usb 3-4: SerialNumber: 4030940402
usb 3-4: configuration #1 chosen from 1 choice
dib0700: loaded with support for 5 different device-types
dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to
load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
i2c_core: i2c_register_adapter
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Hauppauge Nova-T Stick)
i2c_core: i2c_register_adapter
DVB: registering frontend 0 (DiBcom 7000PC)...
mt2060 I2C read failed
input: IR-receiver inside an USB DVB receiver as /class/input/input47
evdev: no more free evdev devices
input: failed to attach handler evdev to device input47, error: -23
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
With the new drivers and the firmware 1.10 a frontend is identified and
registered. But the tuner (mt2060) is not identified. Looking into the
sources (mt2060.c), the driver tries to read the REG_PART_REV in
mt2060_attach but this fails.
Any ideas?
Thanks
Meik
Darren Salt wrote:
> I demand that Sebastian may or may not have written...
>
>> I just bought a new USB DVB-T Stick (at Conrad, Germany), the name on the
>> package is WinTV NOVA-T-CE. On the box there is a label which says 'Model
>> 337G', it is put on top of the old 'MODEL 337' mark. I thought it would
>> work out of the box but I realized that the product id is not 0x7050 or
>> 0x7060 (which seem to be supported) but 0x7070. So the stick is not
>> recognized by the kernel - no drivers are being loaded.
>
>> So i tried to tweak the kernel drivers a little (just changed the ID of
>> HAUPPAUGE_NOVA_T_STICK_2 from 0x7060 to 0x7070). When i plug in my stick
>> then the driver gets loaded, and the firmware gets uploaded. But the syslog
>> tells me that there is no frontend to attach to... So it seems not that
>> easy to get it running :-(
>
>> See my syslog:
> [snip]
>> Dec 1 19:40:13 kernel: [ 160.868000] dvb-usb: downloading firmware
>> from file 'dvb-usb-dib0700-01.fw'
> [snip]
>
> That's old firmware; you should try again with newer drivers and newer
> firmware, and report back (to the list only!) whether this works.
>
> [snip]
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
