From: postfix@au-79.de
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Problems with WinTV Nova T by Hauppauge USB-stick (id: 2040:7070)
Date: Fri, 11 Jul 2008 17:17:34 +0200 [thread overview]
Message-ID: <4877798E.2030409@au-79.de> (raw)
In-Reply-To: <4841663B.5080105@au-79.de>
Hi,
a short summary after a few weeks testing:
The internal EEprom seems to be broken. I returend the stick to the shop
and got my money back.
Best regards
Robert
postfix@au-79.de schrieb:
> Hi,
>
> a view days ago I bought a dvb-USB stick from Hauppauge (WinTV Nova T).
> I want to use this stick with linux, but I sill have some trubble.
> After a google-search it is clear, that the correct driver is dib0700,
> and the firmware to use is dvb-usb-dib0700-1.10.fw (md5:
> 5878ebfcba2d8deb90b9120eb89b02da)
> Kernel is 2.6.25
>
> lsusb:
> 2040:7070 Hauppauge
>
> If I want to tune to a channel (e.g. with kaffine) the dmesg-log is
> overcrowed with "DiB0070 I2C write failed" and there is no sucessfull
> tuning. The output of kaffeine while searching a channel is:
>
> Using DVB device 0:0 "DiBcom 7000PC"
> tuning DVB-T to 402000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> . LOCKED.
> Transponders: 1/63
>
> Invalid section length or timeout: pid=17
>
> Frontend closed
> Using DVB device 0:0 "DiBcom 7000PC"
> tuning DVB-T to 410000000 Hz
> inv:2 bw:0 fecH:9 fecL:9 mod:6 tm:2 gi:4 hier:4
> . LOCKED.
> Transponders: 2/63
>
> Invalid section length or timeout: pid=17
> .... <and so on>
>
> The output of dmesg while attaching the stick and searching with
> kaffeine and debug enabled is:
>
> usb 1-6: new high speed USB device using ehci_hcd and address 6
> usb 1-6: configuration #1 chosen from 1 choice
> 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-adapter i2c-0: SMBus Quick command not supported, can't probe for chips
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new adapter (Hauppauge Nova-T Stick)
> i2c-adapter i2c-1: SMBus Quick command not supported, can't probe for chips
> DVB: registering frontend 0 (DiBcom 7000PC)...
> DiB0070: Revision: 3
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070: CTRL_LO5: 0x16a4
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C read failed
> DiB0070 I2C write failed
> DiB0070: WBDStart = 0 (Vargen) - FF = 0
> DiB0070: successfully identified
> input: IR-receiver inside an USB DVB receiver as /class/input/input11
> dvb-usb: schedule remote query interval to 150 msecs.
> dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
> usb 1-6: New USB device found, idVendor=2040, idProduct=7070
> usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-6: Product: Nova-T Stick
> usb 1-6: Manufacturer: Hauppauge
> usb 1-6: SerialNumber: 4030980792
> DiB0070: Tuning for Band: 2 (402000 kHz)
> DiB0070 I2C write failed
> DiB0070 I2C read failed
> DiB0070 I2C write failed
> DiB0070: HFDIV code: 5
> DiB0070: VCO = 1
> DiB0070: VCOF in kHz: 4824000 ((6*402000) << 1))
> DiB0070: REFDIV: 1, FREF: 12000
> DiB0070: FBDIV: 67, Rest: 0
> DiB0070: Num: 0, Den: 1, SD: 0
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C write failed
> DiB0070 I2C read failed
> DiB0070: CAPTRIM=64; ADC = 0 (ADC) & 0mV
> DiB0070: CAPTRIM=64 is closer to target (400/3000)
> DiB0070 I2C write failed
> DiB0070 I2C read failed
> DiB0070: CAPTRIM=96; ADC = 0 (ADC) & 0mV
> <and so on...>
>
> Here some more information about the stick:
>
> lsusb -vvvv:
>
> Bus 001 Device 006: ID 2040:7070 Hauppauge
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x2040 Hauppauge
> idProduct 0x7070
> bcdDevice 1.00
> iManufacturer 1
> iProduct 2
> iSerial 3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 46
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xa0
> (Bus Powered)
> Remote Wakeup
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 4
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 0
> bInterfaceProtocol 0
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01 EP 1 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82 EP 2 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 1
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 1
> can't get device qualifier: Operation not permitted
> can't get debug descriptor: Operation not permitted
> cannot read device status, Operation not permitted (1)
>
>
> Thanks for your assistance. If you need any further informations or
> tests, please let me know.
>
> Best regards
>
> Robert
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-07-11 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 14:52 [linux-dvb] Problems with WinTV Nova T by Hauppauge USB-stick (id: 2040:7070) postfix
2008-07-11 15:17 ` postfix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4877798E.2030409@au-79.de \
--to=postfix@au-79.de \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.