From: "Thomas Goerke" <tom@goeng.com.au>
To: "'Devin Heitmueller'" <devin.heitmueller@gmail.com>,
"'Patrick Boettcher'" <patrick.boettcher@desy.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Hauppauge WinTV-NOVA-T-500 New Firmware (dvb-usb-dib0700-1.20.fw) causes problems
Date: Fri, 29 Aug 2008 08:54:23 +0800 [thread overview]
Message-ID: <008101c90971$ca7e5080$5f7af180$@com.au> (raw)
In-Reply-To: <412bdbff0808281731t7641e4d1kf86058e071c7d5fb@mail.gmail.com>
>
> Wow, that's so early in the loading process for the device, it's hard
> to see how that can have anything to do with my i2c changes.
>
> Patrick, do you have any changelogs that describe the differences
> between 1.10 and 1.20 other than the addition of the new i2c API?
>
> Devin
>
> --
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller
Devin,
I have applied the latest patch, swapped back to the .20firmware and now get
the following output from dmesg:
[ 32.161603] Linux video capture interface: v2.00
--
[ 32.407733] dib0700: loaded with support for 7 different device-types
[ 32.408042] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold
state, will try to load a firmware
[ 32.451939] dvb-usb: downloading firmware from file
'dvb-usb-dib0700-1.20.fw'
[ 32.654066] dib0700: firmware started successfully.
[ 33.157310] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm
state.
[ 33.157342] dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
[ 33.157430] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[ 33.221594] dib0700: i2c write error (status = -32)
[ 33.221595]
[ 33.225841] dib0700: i2c write error (status = -32)
[ 33.225841]
[ 33.237332] DVB: registering frontend 0 (DiBcom 3000MC/P)...
[ 33.237582] dib0700: i2c write error (status = -32)
[ 33.237582]
[ 33.282556] dib0700: i2c write error (status = -32)
[ 33.282557]
[ 33.282559] mt2060 I2C read failed
[ 33.282587] dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
[ 33.282867] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[ 33.284802] DVB: registering frontend 1 (DiBcom 3000MC/P)...
[ 33.285055] dib0700: i2c write error (status = -32)
[ 33.285056]
[ 33.286178] dib0700: i2c write error (status = -32)
[ 33.286179]
[ 33.286180] mt2060 I2C read failed
[ 33.286242] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:1e.0/0000:05:00.2/usb6/6-1/input/input6
[ 33.333182] dvb-usb: schedule remote query interval to 150 msecs.
[ 33.333186] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
initialized and connected.
[ 33.333286] usbcore: registered new interface driver dvb_usb_dib0700
Please note that the tuners are available within MythTV but are unable to
tune to any channel.
Tom
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-08-29 0:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 15:17 [linux-dvb] Hauppauge WinTV-NOVA-T-500 New Firmware (dvb-usb-dib0700-1.20.fw) causes problems Thomas Goerke
2008-08-28 15:24 ` Devin Heitmueller
2008-08-28 23:24 ` Thomas Goerke
2008-08-28 23:38 ` Devin Heitmueller
2008-08-29 0:05 ` Thomas Goerke
2008-08-29 0:31 ` Devin Heitmueller
2008-08-29 0:54 ` Thomas Goerke [this message]
2008-08-29 1:24 ` Devin Heitmueller
2008-08-29 2:05 ` Devin Heitmueller
2008-08-29 2:40 ` Thomas Goerke
2008-08-29 2:50 ` Devin Heitmueller
2008-08-29 3:29 ` Thomas Goerke
2008-08-29 3:43 ` Devin Heitmueller
2008-08-29 3:49 ` Thomas Goerke
2008-08-29 4:25 ` Thomas Goerke
2008-08-29 4:44 ` Devin Heitmueller
2008-08-29 10:25 ` Patrick Boettcher
2008-08-29 13:26 ` Devin Heitmueller
2008-08-28 16:33 ` Nicolas Will
2008-08-28 17:18 ` Devin Heitmueller
2008-08-28 17:38 ` Nicolas Will
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='008101c90971$ca7e5080$5f7af180$@com.au' \
--to=tom@goeng.com.au \
--cc=devin.heitmueller@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=patrick.boettcher@desy.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox