Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patched v4l-dvb to include the streaming and reception patches that was included a while back. (I´ll check the date of my v4l-dvb tree). I think I have LNA and maybe I disable the remote to, but i need to check and get back about the modprob-d options. /Henrik On Wed, Mar 12, 2008 at 8:48 PM, Patrik Hansson <[EMAIL PROTECTED]> wrote: > 2008/3/12 Henrik Beckman <[EMAIL PROTECTED]>: > > 2.6.22-14 with patches, stable for me. > > > > /Henrik > > > > > > > > > > On Tue, Mar 11, 2008 at 12:07 PM, <[EMAIL PROTECTED]> wrote: > > > Not sure if this helps or adds that much to the discussion... (I think > > this was concluded before) > > > But I finally switched back to kernel 2.6.22.19 on March 5th (with > current > > v4l-dvb code) and haven't had any problems with the Nova-t 500 since. > > Running mythtv with EIT scanning enabled. > > > > > > Looking in the kernel log I see a single mt2060 read failed message on > > March 6th and 9th and a single mt2060 write failed on March 8th. These > > events didn't cause any problems or cause the tuner or mythtv to fail > > though. > > > > > > Ivor. > > > > > > > > > ___ > > > 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 > > > > Henrik: > What options (if any) are you using in modprobe.d ? > Do you mean that you have patched the kernel or the v4l-dvb tree ? > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
2.6.22-14 with patches, stable for me. /Henrik On Tue, Mar 11, 2008 at 12:07 PM, <[EMAIL PROTECTED]> wrote: > Not sure if this helps or adds that much to the discussion... (I think > this was concluded before) > But I finally switched back to kernel 2.6.22.19 on March 5th (with current > v4l-dvb code) and haven't had any problems with the Nova-t 500 since. > Running mythtv with EIT scanning enabled. > > Looking in the kernel log I see a single mt2060 read failed message on > March 6th and 9th and a single mt2060 write failed on March 8th. These > events didn't cause any problems or cause the tuner or mythtv to fail > though. > > Ivor. > > > ___ > 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
[linux-dvb] Fwd: VP-2033
I think I have one, I´ll try to install it and give it a go, just need an f-connector and some spare time. Btw is there any progress on the CAM module? /Henrik On Jan 23, 2008 11:27 AM, Hans Werner < [EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > Can someone test whether the VP-2033 works from this > > tree: http://jusst.de/hg/mantis > > > > Regards, > > Manu > > > > Sorry, I can't help with the VP-2033. > > I was just wondering why the VP-1041 code is not in that tree. I know > working code exists. Is it possible to add it? > > Thanks, > Hans > -- > Release early, release often. > > Pt! Schon vom neuen GMX MultiMessenger gehört? > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger > > ___ > 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
Re: [linux-dvb] dib7000p tuning problem solved
I´m on it to =) /Henrik On Jan 21, 2008 9:14 PM, Nicolas Will <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-01-21 at 21:09 +0100, Soeren Moch wrote: > > > > Janne Grunau wrote: > > > On Monday 21 January 2008 18:07:06 Soeren Moch wrote: > > >> Hello! > > >> > > >> The attached patch solves all my vdr tuning problems on a dib7000p > > >> nova-t stick as far as I could check within the last weekend. > > >> > > >> Perhaps this patch can also help nova-t-500 users. > > > > > > It won't help the nova-t 500 since it uses dib300mc frontend but > > > attached patch might. > > > > > > Janne > > > > > > > Since this patch was not sent to the list and I have no access to a > > nova-t 500 card: Can somebody else check Janne's patch!? > > OK, will do > > Nico > > > ___ > 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
Re: [linux-dvb] DVB scan fails with Nova-TD - please help?
IIRC, on my TD stick the first tuner is the connector on the side of the stick, the one thats need the tiny adaptor. The TD doesn´t have an onboard amp so the LNA parameter does nothing. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NOVA-TD odd behaviour.
I inserted my Nova-T 500 SVTOLD == Channel A Tuner 0 [EMAIL PROTECTED]:~# tzap -a2 -c scan_file-HB SVT1OLD using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 62600 Hz video pid 0x03fb, audio pid 0x03fa status 0f | signal 8f03 | snr | ber 001f | unc 0013 | status 1f | signal 8ed5 | snr | ber | unc 008a | FE_HAS_LOCK status 1f | signal 8f18 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 8f3e | snr | ber | unc | FE_HAS_LOCK status 1f | signal 8f34 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 8f3f | snr | ber | unc | FE_HAS_LOCK status 1f | signal 8f78 | snr | ber | unc | FE_HAS_LOCK Tuner1 [EMAIL PROTECTED]:~# tzap -a3 -c scan_file-HB SVT1OLD using '/dev/dvb/adapter3/frontend0' and '/dev/dvb/adapter3/demux0' tuning to 62600 Hz video pid 0x03fb, audio pid 0x03fa status 07 | signal 9658 | snr | ber 001f | unc 0015 | status 1f | signal 967a | snr | ber | unc 00bd | FE_HAS_LOCK status 1f | signal 95c3 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 95e3 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 95b5 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 95ea | snr | ber | unc | FE_HAS_LOCK status 1f | signal 95af | snr | ber | unc | FE_HAS_LOCK status 1f | signal 9551 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 958a | snr | ber | unc | FE_HAS_LOCK status 1f | signal 95f3 | snr | ber | unc | FE_HAS_LOCK /Henrik On Jan 10, 2008 5:43 PM, Henrik Beckman <[EMAIL PROTECTED]> wrote: > > Hi, > > This is from my NovaTD stick, is something is odd. > > > Sometimes when I tune a different channel on tuner1, reception on tuner 0 > _seems_ to be affected. > status 1f | signal 72b3 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7229 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7260 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7322 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 70fe | snr | ber ebd0 | unc | > FE_HAS_LOCK > status 1f | signal 7134 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 714a | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7080 | snr | ber | unc | > FE_HAS_LOCK > *status 1f | signal 7051 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 6fda | snr | ber | unc | > FE_HAS_LOCK * > status 1f | signal 6fcb | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 6fc7 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 6fbc | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 6f1b | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 6fc7 | snr | ber | unc | > FE_HAS_LOCK > > So I started poking around a bit. > > Same channel (A), channel on both tuners at the same time. > Tuner 0 > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > > Tuner 1 > status 1f | signal 716e | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7183 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 71d8 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7174 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7170 | snr | ber | unc | > FE_HAS_LOCK > > A different channel (B), but same on both tuners. > Tuner 0 > status 1f | signal 75ec | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 75e2 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7575 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7567 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7576 | snr | ber | unc | > FE_HAS_LOCK > status 1f | signal 7317 | snr | ber | unc | > FE_HAS_LOCK > > Tuner 1 > status 1f | signal 71f8
[linux-dvb] NOVA-TD odd behaviour.
Hi, This is from my NovaTD stick, is something is odd. Sometimes when I tune a different channel on tuner1, reception on tuner 0 _seems_ to be affected. status 1f | signal 72b3 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7229 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7260 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7322 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 70fe | snr | ber ebd0 | unc | FE_HAS_LOCK status 1f | signal 7134 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 714a | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7080 | snr | ber | unc | FE_HAS_LOCK *status 1f | signal 7051 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 6fda | snr | ber | unc | FE_HAS_LOCK* status 1f | signal 6fcb | snr | ber | unc | FE_HAS_LOCK status 1f | signal 6fc7 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 6fbc | snr | ber | unc | FE_HAS_LOCK status 1f | signal 6f1b | snr | ber | unc | FE_HAS_LOCK status 1f | signal 6fc7 | snr | ber | unc | FE_HAS_LOCK So I started poking around a bit. Same channel (A), channel on both tuners at the same time. Tuner 0 status 1e | signal | snr | ber | unc | FE_HAS_LOCK status 1e | signal | snr | ber | unc | FE_HAS_LOCK status 1e | signal | snr | ber | unc | FE_HAS_LOCK status 1e | signal | snr | ber | unc | FE_HAS_LOCK Tuner 1 status 1f | signal 716e | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7183 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 71d8 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7174 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7170 | snr | ber | unc | FE_HAS_LOCK A different channel (B), but same on both tuners. Tuner 0 status 1f | signal 75ec | snr | ber | unc | FE_HAS_LOCK status 1f | signal 75e2 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7575 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7567 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7576 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7317 | snr | ber | unc | FE_HAS_LOCK Tuner 1 status 1f | signal 71f8 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7262 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 71f3 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 71e2 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 71f1 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7172 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7170 | snr | ber | unc | FE_HAS_LOCK So I figure my splitter is the cause of the problem. Antenna straight into the tuner, no splitter, channel A Tuner 0 status 1f | signal | snr | ber | unc | FE_HAS_LOCK status 1f | signal | snr | ber | unc | FE_HAS_LOCK status 1f | signal | snr | ber | unc | FE_HAS_LOCK status 1f | signal | snr | ber | unc | FE_HAS_LOCK status 1f | signal | snr | ber | unc | FE_HAS_LOCK Tuner 1 status 1f | signal 798b | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7988 | snr | ber | unc | FE_HAS_LOCK status 1f | signal 78ad | snr | ber | unc | FE_HAS_LOCK status 1f | signal 783c | snr | ber | unc | FE_HAS_LOCK status 1f | signal 7900 | snr | ber | unc | FE_HAS_LOCK Channel A, SVT1OLD:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1019:1018:1010 Channel B TV4 Uppland:47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1049:1048:6100 I´m lost. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] WinTV-NOVA-T-500 Status
Would that patch also affect the nova-td stick, I have had issues with both. My problems are isolated to one channel, as long as I don´t record on that specific channel everything is solid. Reception on the problem channel is worse, if it´s any help to anyone just specify what tests you need and I will try to deliver. /Henrik On Jan 8, 2008 10:52 AM, Paul Elliott <[EMAIL PROTECTED]> wrote: > Hi Patrick, > > On 08/01/2008, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > The new year starts well, maybe: We found something which was in our > > drivers from the beginning and nobody saw it. See attached. > > I'm not sure whether it fixes something, but it might be possible. Can > > everyone try it please? > > I'll give it a whirl over the next few days, thanks. > > -- > Paul Elliott (omahn) > Systems Engineer, Option-C Services > [EMAIL PROTECTED] > > ___ > 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
Re: [linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
Hi, I assume that it´s me you mention. I have my htpc running with a nova-TD and it´s working ok with the exception of SVT1 which for some reasons occasionaly generates disconnects as seen on the Nova-T 500. To note here is that I have a VIA usb card, using my onboard nvidia USB led to hard hangs within ~4 hours with the nova-TD. Reception is a tad better with the nova-T 500 (which also chokes on SVT1). Contact me if you need more detailed information about my kernel . /Henrik On Dec 16, 2007 5:07 PM, Tomas <[EMAIL PROTECTED]> wrote: > Hello, > > I'm having problems tuning my Hauppauge WinTV Nova-TD USB DVB > receiver. > > Scanning for channels works fine with the 'scan' utility, I have > compared the result with the result from a scan performed using > my Twinhan DTV Alpha USB stick (7045, not 7045A, which is another > story...) and they are identical. > > But when it's time to record, using the same program I use with > the Twinhan stick, I get (almost) no output, just a ridiculously > high bit error rate (2097151) and SNR=0. I'm very surprised by > this, as the channel scanning works just fine. > > As far as I understand, and as previously reported by Henrik > Backman, the Nova-TD should work with the DVB-T broadcasts here > in Sweden. > > Could my problems be caused by the important bug mentioned > yesterday by Patrick Boettcher? If so, is there an earlier > version of the driver which doesn't have this bug? > > The command used to test recording: > > ~# /usr/local/bin/dvbstream -f 49 -p V -s 27500 -c 0 -o:test.ts 1029 > 1028 > dvbstream v0.6 - (C) Dave Chapman 2001-2004 > Released under the GPL. > Latest version available from http://www.linuxstb.org/ > Processing -o:test.ts > Open file test.ts > Using DVB card "DiBcom 7000PC" > tuning DVB-T (Stockholm Nacka) to 49000 Hz, Bandwidth: 8 > polling > Getting frontend event > FE_STATUS: > polling > Getting frontend event > FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC > Event: Frequency: 49000 > Bit error rate: 2097151 > Signal strength: 65535 > SNR: 0 > FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC > MAP 0, file test.ts: From -1 secs, To -1 secs, 2 PIDs - 1029 1028 > dvbstream will stop after -1 seconds (71582788 minutes) > Setting filter for PID 1029 > Setting filter for PID 1028 > Using 224.0.1.2:5004:2 > version=2 > Streaming 2 streams > Caught signal 2 - closing cleanly. > ~# ls -la test.ts > -rw-r--r-- 1 ath ath 188 Dec 16 16:43 test.ts > ~# > > (I'm terminating the program by pressing Ctrl-C). Whether I get > any packets at all seems totally random. In this attempt I got > one single packet from several minutes of running dvbstream! > > A sample from the scan output: > > ~# grep '^SVT2:' .dvb_channels > > SVT2:49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5060 > ~# > > I have also tried tuning with tzap and recording using cat, but > tzap gives this: > > ~# tzap -a 0 -c ~/.dvb_channels 'SVT2' > using '/dev/dvb/adapter0/frontend0' and > '/dev/dvb/adapter0/demux0' > tuning to 49000 Hz > video pid 0x0405, audio pid 0x0404 > status 0f | signal b496 | snr | ber 001f | unc | > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > status 1e | signal | snr | ber | unc | > FE_HAS_LOCK > ... > > ~# tzap -a 1 -c ~/.dvb_channels 'SVT2' > using '/dev/dvb/adapter1/frontend0' and > '/dev/dvb/adapter1/demux0' > tuning to 49000 Hz > video pid 0x0405, audio pid 0x0404 > status 1a | signal | snr | ber 001f | unc | > FE_HAS_LOCK > status 1a | signal | snr | ber 001f | unc | > FE_HAS_LOCK > status 1a | signal | snr | ber 001f | unc | > FE_HAS_LOCK > ... > > And the 'cat' command gives just as little TS data as dvbstream > does. > > I'm using Linux kernel 2.6.22.6, and updated the dvb drivers from > the hg sources about two hours ago. Relevant dmesg output: > > [ 1293.235000] usb 1-2: new high speed USB device using ehci_hcd and > address 2 > [ 1293.35] usb 1-2: configuration #1 chosen from 1 choice > [ 1293.432000] dib0700: loaded with support for 5 different device-types > [ 1293.44] dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV > Diversity' in cold state, will try to load a firmware > [ 1293.858000] dvb-usb: downloading firmware from file ' > dvb-usb-dib0700-1.10.fw' > [ 1294.146000] dib0700: firmware started successfully. > [ 1294.648000] dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV > Diversity' in warm state. > [ 1294.649000] dvb-usb: will pass the complete MPEG2 transport stream to > the software demuxer. > [ 1294.649000] DVB: registering new adapter (Hauppauge Nova-TD > Stick/Elgato Eye-TV Diversity) > [ 1294.875000] DVB: registering frontend 0 (DiBcom 7000PC)... > [ 1294.907000] MT2266: successfully identified > [ 1295.06] dvb-usb: w
Re: [linux-dvb] Problem with Hauppauge Nova-TD
You need both antenna connectors connected if you intend to use both tuners (dual tuner mode). Tuner 0 seems to be the side connector and tuner 1 the top connector. /Henrik On Dec 14, 2007 8:49 AM, Nicolas Will <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-12-13 at 23:24 +0100, Luca wrote: > > Well... the device seem working properly after I put the firmware in > > /lib/firmware... maybe before I was using the wrong one... mah! Now > > dib0700 module say me that loads the firmware at ... (really two > > different firmwares, 1.10 and 03-pre). > > > As the wiki page says, you need to either: > > rename the 1.10 firmware file to the 03-pre name > symlink 1.10 to 03-pre > > You are not using the 03-pre at all, but you need the name as the code > did not change the hard-coded file name. > > As with every firmware change, you need to cold boot the device, by > either unplugging the stick, or by *shutting off* (not just a reboot) > the machine. > > > > > I don't know if it can work with both antennas... I'm playing with > > them, > > because I think it's an antenna problems... > > The diversity feature (2 antennas) is certainly *not* supported at this > time. > > > > > > Kaffein is awesome! But sadly I cannot find any channel... sigh... > > > Make sure you are using the right firmware. > > Nico > > > ___ > 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
[linux-dvb] bad reception causes disconnects?
mt2266 writes fail on NOVA-TD, reception based problem? Seems to be one channel only, and very occasionaly. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] MT2266 I2C write failed
I´ve started to get these on my nova-td stick, Nov 9 22:31:32 media kernel: [ 8706.753630] usb 4-3: USB disconnect, address 3 Nov 9 22:31:32 media kernel: [ 8706.766091] MT2266 I2C write failed Nov 9 22:31:32 media kernel: [ 8706.766542] MT2266 I2C write failed their as fatal to recording as the nova-t 500 errors. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: [mythtv-users] Nova-T 500 musings...
-- Forwarded message -- From: James Fidell <[EMAIL PROTECTED]> Date: Oct 28, 2007 12:44 AM Subject: [mythtv-users] Nova-T 500 musings... To: Discussion about mythtv <[EMAIL PROTECTED]> Anyone else have a Nova-T500 tuner and still getting mt2060 I2C write errors? I'm running CentOS5 (2.6.18 kernel + RedHat updates) with new v4l-dvb drivers taken from linuxtv.org a couple of weeks ago and the latest firmware. I still get mt2060 I2C read and write errors. As far as I can tell the read errors don't seem that serious, but the write errors seem to break tuning somehow so that I end up with a failed recording. Thus far I've resolved this by stopping mythbackend and unloading and reloading all the dvb modules whenever I've seen a writer error. This seems to work ok, but it's a pita. Yesterday, more out of irritation than any real understanding of the code, I changed the mt2060 driver code that calls write_regs to retry if the first attempt fails. Thus far I've had a couple of fails that have worked ok on the second attempt and I've had no failed recordings. I'll be watching things over the next few days to see what happens. What I've done is without doubt a hack rather than a genuine fix, but if it mostly resolves the problem for me, I think I can live with that until such time as someone who understands the problem properly can do the job right. James ___ mythtv-users mailing list [EMAIL PROTECTED] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Twinhan 20330 mantis
Hi, I recently got a 20330 mantis card from a friend, is it possible to get it working with or without the CI ? I´ve got 2.6.23 and it looks like twinhan/azurwaves driver only supports upt to 2.6.18, does the OSS driver support CI, or is there any generic CI drivers? TIA /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] solved problem with nova-TD hangs, usb related
Hi, Added a VIA usb controller card and attached my TD stick to that instead of the nforce 430 controller and since it has been 100% stable. If it´s a bug in any driver or if it´s my hardware that´s bad I don´t know. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with Hauppauge WinTV Nova-TD USB Stick
1. grep init /var/log/kern.log (or /var/logmessages) Should among other things return the following line, dvb-usb: Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity successfully initialized and connected. Else, your card isn´t detected. 2.Using kaffein you can scan for channels, select the ones you want. If your card is not detected the dvb field won´t show. http://docs.kde.org/development/en/extragear-multimedia/kaffeine/dvbwindow.html /Henrik On 10/22/07, Cornelius Horstmann <[EMAIL PROTECTED]> wrote: > But how can I use those tuners? > How can I use it with Kaffeine as example? > > *greez* Cornelius > > 2007/10/19, Henrik Beckman <[EMAIL PROTECTED]>: > > This might be it, the first tuner is the antenna on the side on the stick, > > second tuner is the standard connector on the end of the stick. > > This assumes that you have the correct drivers, try grep for Haupaugge in > > messages or kern.log for confirmation. > > > > /Henrik > > > > > > On 10/18/07, Cornelius Horstmann > > <[EMAIL PROTECTED] > wrote: > > > > > > Hello, > > > > > > i tried to get this stick running. > > > On this page: > > > > > http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick > > > are no really "how-To"s to get it running. > > > I copied the firmware from: > > > > > http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-Stick#Firmware > > > to /lib/firmware > > > but even if, i don't know how to get my stick running. > > > > > > Need Help, please. > > > > > > *greez* Cornelius > > > > > > ___ > > > linux-dvb mailing list > > > linux-dvb@linuxtv.org > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > > > > > > > -- > www.webwork-archiv.de > Das Wissens-Archiv für Webdesigner. > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware problems
My guess is reception, mine was working ok and then startet getting errors after 2 months. If the numbers from mythtv is to be trusted something is odd with my Nova-t 500 since it reports ~60% quality and the almost always 100% /Henrik On 10/16/07, Simon Lundell <[EMAIL PROTECTED]> wrote: > > > > On 9/26/07, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > it seems that there still problems related to USB with the latest > > firmware. > > > > In order to figure out what is the problem I would like to gather some > > information about the affected systems: > > > > Can everyone (people who still have the disconnects and the ones who > > don't) please reply directly to this email giving the following > > information: > > > > I grep-ed for keywords to try to figure out when my last nova-t failure > occured, and it seems to have been sometime in august-september. I do not > know what happend then, as I have made a lo of small changes (improved > reception, the broadcaster has changed frequencies). But it seems to be > quite stable at least. > > Is there any good keywords to grep for? I have tried: > "m2060 I2C" > "Oops" > "EIP" > and the last problem seems to have been th 14th of august. > > ... A little research shows that i upgraded my kernel to 2.6.22-gentoo-r2that > date, (probably hg dvb-modules), and have not had any problem scince! > > firmware is dvb-usb-dib0700-03-pre1.fw > //Simon > > > > > ___ > 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
[linux-dvb] Nova TD problem
My Nova-td diversity stick is behaving strange. After roughly 3 hours of poweron, everything USB related dies except video, every USB device except the USB stick I suppose dies. Nothing is logged, if init 6 is given the machine says /var/log/kern.log Oct 13 09:20:13 media kernel: [ 5406.722093] timeout: still 8 active urbs.. And hangs on shutdown. Any good ideas? /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
I´m an idiot, it never occured to me that the stick needed dual antennas in dual tuner mode, the when using the second tuner on the card I get reception /Henrik On 10/5/07, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > On Thu, 4 Oct 2007, Henrik Beckman wrote: > > > Hi, > > > > I´ve posted some yesterday and I´ve done some more poking around and it > just > > doesn´t find any signal in linux > > I´ve tried with two different antenna feeds who both works with windows, > if > > I spilt my primary feed I can still run the t-500 PCI card > > but no matter what the TD stick never finds anything. > > The current driver even in latest hg has no VHF support meaning it does > not support frequencies below 470 MHz. > > I have a patch pending - if I will find the time, I will commit it later > that day. > > Patrick. > > -- > Mail: [EMAIL PROTECTED] > WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
Eg using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' initial transponder 72200 0 2 9 3 1 2 0 initial transponder 57800 0 2 9 3 1 2 0 initial transponder 73000 0 2 9 3 1 2 0 initial transponder 76200 0 2 9 3 1 2 0 >>> tune to: 72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 72200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 57800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 57800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 76200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 76200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. On 10/5/07, Henrik Beckman <[EMAIL PROTECTED]> wrote: > > No DVB-T should be below 474MHz in Sweden, it´s more like there doesn´t > exist any signal on the stick, either reception in linux is extremly bad > compared to windows or something has changed on the inside of the Nova-TD > stick, or the stick is quirky. > w_scan doesn´t find anything, tzap with the nova-t 500 channels.confdoesn´t > find anything. > I´ll try with kaffeine and create and a brand new channesl.conf consisting > of only auto values and see if I can find and recive something. > > > /Henrik > > On 10/5/07, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > > > On Thu, 4 Oct 2007, Henrik Beckman wrote: > > > > > Hi, > > > > > > I´ve posted some yesterday and I´ve done some more poking around and > > it just > > > doesn´t find any signal in linux > > > I´ve tried with two different antenna feeds who both works with > > windows, if > > > I spilt my primary feed I can still run the t-500 PCI card > > > but no matter what the TD stick never finds anything. > > > > The current driver even in latest hg has no VHF support meaning it does > > not support frequencies below 470 MHz. > > > > I have a patch pending - if I will find the time, I will commit it later > > that day. > > > > Patrick. > > > > -- > > Mail: [EMAIL PROTECTED] > > WWW: > > http://www.wi-bw.tfh-wildau.de/~pboettch/<http://www.wi-bw.tfh-wildau.de/%7Epboettch/> > > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Warning, there seems to be a new Nova TD stick out!!
No DVB-T should be below 474MHz in Sweden, it´s more like there doesn´t exist any signal on the stick, either reception in linux is extremly bad compared to windows or something has changed on the inside of the Nova-TD stick, or the stick is quirky. w_scan doesn´t find anything, tzap with the nova-t 500 channels.conf doesn´t find anything. I´ll try with kaffeine and create and a brand new channesl.conf consisting of only auto values and see if I can find and recive something. /Henrik On 10/5/07, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > On Thu, 4 Oct 2007, Henrik Beckman wrote: > > > Hi, > > > > I´ve posted some yesterday and I´ve done some more poking around and it > just > > doesn´t find any signal in linux > > I´ve tried with two different antenna feeds who both works with windows, > if > > I spilt my primary feed I can still run the t-500 PCI card > > but no matter what the TD stick never finds anything. > > The current driver even in latest hg has no VHF support meaning it does > not support frequencies below 470 MHz. > > I have a patch pending - if I will find the time, I will commit it later > that day. > > Patrick. > > -- > Mail: [EMAIL PROTECTED] > WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Warning, there seems to be a new Nova TD stick out!!
Hi, I´ve posted some yesterday and I´ve done some more poking around and it just doesn´t find any signal in linux I´ve tried with two different antenna feeds who both works with windows, if I spilt my primary feed I can still run the t-500 PCI card but no matter what the TD stick never finds anything. Found DVB-T frontend. Using adapter /dev/dvb/adapter2/frontend0 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend DiBcom 7000PC supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ initial_tune:1379: Setting frontend parameters failed f17750 bw7initial_tune:1379: Setting frontend parameters failed f18450 bw7initial_tune:1379: Setting frontend parameters failed f19150 bw7initial_tune:1379: Setting frontend parameters failed f19850 bw7initial_tune:1379: Setting frontend parameters failed f20550 bw7initial_tune:1379: Setting frontend parameters failed f21250 bw7initial_tune:1379: Setting frontend parameters failed f21950 bw7initial_tune:1379: Setting frontend parameters failed f22650 bw7474000: 482000: ^C /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-TD model 1180, not working in linux ?
Hi, My nova-TD came in a box with a sticker over the model 1175, saying 1180. It doesn´t seem to work, I use the latest fw since I also have a nova-t 500. w_scan says Found DVB-T frontend. Using adapter /dev/dvb/adapter2/frontend0 -_-_-_-_ Getting frontend capabilities-_-_-_-_ frontend DiBcom 7000PC supports INVERSION_AUTO QAM_AUTO TRANSMISSION_MODE_AUTO GUARD_INTERVAL_AUTO HIERARCHY_AUTO FEC_AUTO -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ initial_tune:1379: Setting frontend parameters failed f17750 bw7initial_tune:1379: Setting frontend parameters failed f18450 bw7initial_tune:1379: Setting frontend parameters failed f19150 bw7initial_tune:1379: Setting frontend parameters failed f19850 bw7initial_tune:1379: Setting frontend parameters failed f20550 bw7initial_tune:1379: Setting frontend parameters failed f21250 bw7initial_tune:1379: Setting frontend parameters failed f21950 bw7initial_tune:1379: Setting frontend parameters failed f22650 bw7474000: Then it finds nothing, channels.conf and tzap doesn´t find any channels. Please give me hope. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 device report
Hi,
Can I ask you a few questions about the TD stick,
1. How is reception compared to the nova-t 500
2. What firmware do you use for it
I bought and returned a TD yesterday, it didn´t find a single channel, tried
both in windows and
in linux, kaffein detected all channels but none worked, w_scan didn´t find
a single channel.
I have 60% signal strenght on my t-500 but I suspect that somnething else
was wrong.
/Henrik
On 9/29/07, Jonas Anden <[EMAIL PROTECTED]> wrote:
>
> 1) system (uname -a)
> Linux ragnyr.garth.anden.nu 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT
> 2007 i686 i686 i386 GNU/Linux
>
> 2) lspci-output
> 00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller
> Hub (rev 02)
> 00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port
> (rev 02)
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
> Definition Audio Controller (rev 01)
> 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
> Port 1 (rev 01)
> 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
> Controller #1 (rev 01)
> 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
> Controller #2 (rev 01)
> 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
> Controller #3 (rev 01)
> 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
> Controller #4 (rev 01)
> 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI
> Controller (rev 01)
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
> 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC
> Interface Bridge (rev 01)
> 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
> Controller (rev 01)
> 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA
> IDE Controller (rev 01)
> 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller
> (rev 01)
> 01:00.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
> 100] (rev 04)
> 01:01.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB
> 1.1Controller (rev 61)
> 01:01.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB
> 1.1Controller (rev 61)
> 01:01.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
> 03:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600]
> (rev a2)
>
> 2.5) "lsusb | grep Hauppauge" output
> Bus 008 Device 002: ID 2040:9950 Hauppauge
> Bus 007 Device 006: ID 2040:7050 Hauppauge
> Bus 007 Device 005: ID 2040:9580 Hauppauge
>
> 3) DiB0700 device name (USB Stick, Nova-T 500)
> Nova-T 500 ("PCI")
> Nova-T Stick (USB)
> Nova-T Diversity Stick (USB)
>
> 4) Application using the device (MythTV, VDR etc)
> MythTV
>
> 5) Symptoms (unusable, disconnect after x days, no problem)
>
> I have only had the Nova-T Stick connected to the box for the past month
> and that has been stable. Using multiple tuners have caused problems
> (MPEG decoding failures, channel lock failures, USB disconnects) in the
> past. I just put the Nova-T 500 card back in the box today and upgraded
> the firmware + drivers. For the past month, I have only had the Nova-T
> Stick connected and have had no problems (this device has always been
> the most stable). This machine is on 24/7,and MythTV has EIT scanning
> enabled (so there's a whole lot of channel switching going on).
>
> With the latest drivers and firmware (downloaded and compiled today),
> all adapters appear to be working. The Nova-TD Stick failed to tune with
> the previous firmware (03-pre1), but now it appears to work.
>
> MythTV has (so far) only been configured for one adapter. I'm going to
> configure all tuners in MythTV and see what happens. Stand by for more
> updates.
>
> // J
>
>
> ___
> 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
Re: [linux-dvb] DiB0700 firmware problems
Hmm, It seems like it only happens while recording on both tuners. I´ll dig some more and see if there is any pattern with MUXes or other. /Henrik On 9/26/07, Patrick Boettcher <[EMAIL PROTECTED]> wrote: > > Hi all, > > it seems that there still problems related to USB with the latest > firmware. > > In order to figure out what is the problem I would like to gather some > information about the affected systems: > > Can everyone (people who still have the disconnects and the ones who > don't) please reply directly to this email giving the following > information: > > 1) system (uname -a) > 2) lspci-output > 3) DiB0700 device name (USB Stick, Nova-T 500) > 4) Application using the device (MythTV, VDR etc) > 5) Symptoms (unusable, disconnect after x days, no problem) > > Please make sure that you are using the latest firmware (version 1.10) . > > thanks and regards, > Patrick. > > -- > Mail: [EMAIL PROTECTED] > WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ > > ___ > 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
[linux-dvb] nova-t 500
1) system (uname -a) Linux media 2.6.22.1 #1 SMP Mon Jul 16 19:58:53 CEST 2007 x86_64 GNU/Linux 2) lspci-output [EMAIL PROTECTED]:~# lspci 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 04:08.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 04:08.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 61) 04:08.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 04:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) 3) DiB0700 device name (USB Stick, Nova-T 500) Nova-T 500 4) Application using the device (MythTV, VDR etc) MythTV 5) Symptoms (unusable, disconnect after x days, no problem) Disconnects, usualy when recording ocn both tuners. Semi random. Currenly once a week, was once a month for a while. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] RE : nova-t 500, again.
In my case it more or less only happens on one MUX, it´s also the MUX with the highest bitrate channels. Also it more ore less always fail while recording "the wire", or some desired show and alway works for test stuff I schedule to test stability. /Henrik On 9/24/07, Thierry Lelegard <[EMAIL PROTECTED]> wrote: > > *> That doesn´t by any chance happen to be channels with high bitrate ? > * > How can a specific service bitrate cause the disconnect since the device > (and its driver) passes the complete TS to the software demux in the kernel? > Even if the service has a variable bitrate inside the TS, the TS bitrate > remains constant. > > I experience the same problems with a custom application (not MythTV, > Kaffeine, or any TV watching software). My application always reads the > complete TS: > > struct dmx_pes_filter_params filter; > ... > filter.pid = 0x2000;// Means "all PID's" > filter.input = DMX_IN_FRONTEND; // Read from frontend device > filter.output = DMX_OUT_TS_TAP; // Redirect TS packets to DVR device > filter.pes_type = DMX_PES_OTHER;// Any type of PES > filter.flags = DMX_IMMEDIATE_START; // Start capture immediately > ioctl (demux_fd, DMX_SET_PES_FILTER, &filter); > > > The DTTV TS have all a constant bitrate, although not the same for all TS > (depends on FEC). > > -Thierry > > -Message d'origine- > *De :* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > *De la part de* Henrik Beckman > *Envoyé :* samedi 22 septembre 2007 13:50 > *À :* Dan Harper; linux-dvb > *Objet :* Re: [linux-dvb] nova-t 500, again. > > Hi, > > That doesn´t by any chance happen to be channels with high bitrate ? > > /Henrik > > On 9/22/07, Dan Harper < [EMAIL PROTECTED]> wrote: > > > > Hi Henrik, > > I have a sneaking suspicion that the problem is related to either > > reception or the content that is being passed down on a particular channel > > at a particular time. I've noticed that attempting to record some of the > > same shows each week cause the card to disconnect (on one of my favourite > > shows too.. grrr). > > > > This is totally unproven, but I have a suspicion that it's related. > > > > Dan > > > > > > On 22/09/2007, at 5:51 PM, Henrik Beckman wrote: > > > > Hi, > > > > I´m running 2.6.22.1 (x86_64) > > > > I upgraded the kernel 2007-07-16 and haven´t had a disconnect since, > > until 2007-09-20. > > I have been running the kernel source drivers until 2007-09-05 when I > > upgraded to the lates HG and the dvb-usb-dib0700-03-pre1.fw > > firmware. Suffering the disconnects on the 20 I upgraded firmware to > > dvb-usb-dib0700-1.10.fw but suffered to disconnects again the 21. > > > > Nothing has changed in the system the days prior to the disconnects, > > here is what has changed lately. > > > > Fall is here, colder and wetter outside, reception may have been > > changed. > > Slightly more uptime on the machine, instead off just waking up and > > recording it might have been on a few hours and running playbacks or > > just sitting there instead of just waking up and recording. > > > > I realy thought I had this problem behind me, is there any dual dvb-t > > card for pci or pci-e that is flawless in linux? > > > > Sep 21 21:20:12 media -- MARK -- > > Sep 21 21:40:12 media -- MARK -- > > Sep 21 22:00:12 media -- MARK -- > > Sep 21 22:20:13 media -- MARK -- > > Sep 21 22:40:13 media -- MARK -- > > Sep 21 22:59:13 media kernel: [ 9272.837486 ] usb 3-1: USB disconnect, > > address 2 > > Sep 21 22:59:13 media kernel: [ 9272.838165] mt2060 I2C write failed > > Sep 21 22:59:13 media kernel: [ 9272.846396] hald-addon-keyb[5204] > > general protection rip:2ad4e99c221b rsp:7fffc17cbf70 error:0 > > > > > > Mythlog is ugly, but points at it being reception based. > > > > I have _a lot_ of > > [mpeg2video @ 0x2b331f003fd0]00 motion_type at 10 23 > > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 5 9 > > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 41 35 > > [mpeg2video @ 0x2b331f003fd0]00 motion_type at 5 2 > > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 0 0 > > > > That hasn´t occured earlier in the log it records two channels for ~30 > > minutes before disconnecting, I strongly suspect that recording on both > > tuners paired with bad reception? has triggered the disconnects. > > > > So what´s more needed in the logs? > > > > /Henrik > > > > >
[linux-dvb] dualtuner dvb-t questions
Hi, Does the "DiB7700P, Dib 7000P, 2 * MT2266" based sticks also suffer from disconnects or are they ok. Is there any plans for diversity support. Is any "DiB7700P, Dib 7000P, 2 * MT2266" design superior in any way reception wise, has a LNA or is just more sensitive. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500, again.
Hi, That doesn´t by any chance happen to be channels with high bitrate ? /Henrik On 9/22/07, Dan Harper <[EMAIL PROTECTED]> wrote: > > Hi Henrik, > I have a sneaking suspicion that the problem is related to either > reception or the content that is being passed down on a particular channel > at a particular time. I've noticed that attempting to record some of the > same shows each week cause the card to disconnect (on one of my favourite > shows too.. grrr). > > This is totally unproven, but I have a suspicion that it's related. > > Dan > > > On 22/09/2007, at 5:51 PM, Henrik Beckman wrote: > > Hi, > > I´m running 2.6.22.1 (x86_64) > > I upgraded the kernel 2007-07-16 and haven´t had a disconnect since, > until 2007-09-20. > I have been running the kernel source drivers until 2007-09-05 when I > upgraded to the lates HG and the dvb-usb-dib0700-03-pre1.fw > firmware. Suffering the disconnects on the 20 I upgraded firmware to > dvb-usb-dib0700-1.10.fw but suffered to disconnects again the 21. > > Nothing has changed in the system the days prior to the disconnects, here > is what has changed lately. > > Fall is here, colder and wetter outside, reception may have been changed. > Slightly more uptime on the machine, instead off just waking up and > recording it might have been on a few hours and running playbacks or > just sitting there instead of just waking up and recording. > > I realy thought I had this problem behind me, is there any dual dvb-t card > for pci or pci-e that is flawless in linux? > > Sep 21 21:20:12 media -- MARK -- > Sep 21 21:40:12 media -- MARK -- > Sep 21 22:00:12 media -- MARK -- > Sep 21 22:20:13 media -- MARK -- > Sep 21 22:40:13 media -- MARK -- > Sep 21 22:59:13 media kernel: [ 9272.837486 ] usb 3-1: USB disconnect, > address 2 > Sep 21 22:59:13 media kernel: [ 9272.838165] mt2060 I2C write failed > Sep 21 22:59:13 media kernel: [ 9272.846396] hald-addon-keyb[5204] general > protection rip:2ad4e99c221b rsp:7fffc17cbf70 error:0 > > > Mythlog is ugly, but points at it being reception based. > > I have _a lot_ of > [mpeg2video @ 0x2b331f003fd0]00 motion_type at 10 23 > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 5 9 > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 41 35 > [mpeg2video @ 0x2b331f003fd0]00 motion_type at 5 2 > [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 0 0 > > That hasn´t occured earlier in the log it records two channels for ~30 > minutes before disconnecting, I strongly suspect that recording on both > tuners paired with bad reception? has triggered the disconnects. > > So what´s more needed in the logs? > > /Henrik > > > ___ > 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 > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] nova-t 500, again.
Hi, I´m running 2.6.22.1 (x86_64) I upgraded the kernel 2007-07-16 and haven´t had a disconnect since, until 2007-09-20. I have been running the kernel source drivers until 2007-09-05 when I upgraded to the lates HG and the dvb-usb-dib0700-03-pre1.fw firmware. Suffering the disconnects on the 20 I upgraded firmware to dvb-usb-dib0700-1.10.fw but suffered to disconnects again the 21. Nothing has changed in the system the days prior to the disconnects, here is what has changed lately. Fall is here, colder and wetter outside, reception may have been changed. Slightly more uptime on the machine, instead off just waking up and recording it might have been on a few hours and running playbacks or just sitting there instead of just waking up and recording. I realy thought I had this problem behind me, is there any dual dvb-t card for pci or pci-e that is flawless in linux? Sep 21 21:20:12 media -- MARK -- Sep 21 21:40:12 media -- MARK -- Sep 21 22:00:12 media -- MARK -- Sep 21 22:20:13 media -- MARK -- Sep 21 22:40:13 media -- MARK -- Sep 21 22:59:13 media kernel: [ 9272.837486] usb 3-1: USB disconnect, address 2 Sep 21 22:59:13 media kernel: [ 9272.838165] mt2060 I2C write failed Sep 21 22:59:13 media kernel: [ 9272.846396] hald-addon-keyb[5204] general protection rip:2ad4e99c221b rsp:7fffc17cbf70 error:0 Mythlog is ugly, but points at it being reception based. I have _a lot_ of [mpeg2video @ 0x2b331f003fd0]00 motion_type at 10 23 [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 5 9 [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 41 35 [mpeg2video @ 0x2b331f003fd0]00 motion_type at 5 2 [mpeg2video @ 0x2b331f003fd0]ac-tex damaged at 0 0 That hasn´t occured earlier in the log it records two channels for ~30 minutes before disconnecting, I strongly suspect that recording on both tuners paired with bad reception? has triggered the disconnects. So what´s more needed in the logs? /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] PVR-150 sound issue
Hi, I downloaded the latest hg the fifth and after that the audio on my pvr-150 has had a bunch of cracklings and pitch issues that has made it useless, backed ivt to Hans DMA fix release, think I downloaded that late july, voila audio is ok. Is there anything broken in the hg regarding the pvr-150, I haven´t made more than two recordings since the fifth and been tinkering a bit with audio levels from my cablebox. I might have provoced something by have to strong input signal, I adjusted this also on the fifth, what ever it was went away after a downgrade and a reboot. If I get the time I´ll upgrade again to see if it reoccurs. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] feedback, nova-t 500
Haven´t tried that. But I will update to the latest code and firmware next week and do a check if the reception patch is still needed and general functionality test. /Henrik On 8/2/07, Nicolas Will <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-08-02 at 18:54 +0200, Henrik Beckman wrote: > > * MT1060_IF1_freq_set.diff - 2.3K > > * Sets the MT2060 IF1 frequency according to the > calibration values stored in the EEPROM. It is supposed to enhance the > signal quality > > * Olivier Danet > > > > * Post: > http://linuxtv.org/pipermail/linux-dvb/2006-December/014926.html > > > > > > > > As said before, has worked fine for me and is needed to achive good > enough reception oc tuner two on some frequencies. > > Even with the latest code and firmware? > > Nico > > > ___ > 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
[linux-dvb] feedback, nova-t 500
* MT1060_IF1_freq_set.diff - 2.3K * Sets the MT2060 IF1 frequency according to the calibration values stored in the EEPROM. It is supposed to enhance the signal quality * Olivier Danet * Post: http://linuxtv.org/pipermail/linux-dvb/2006-December/014926.html As said before, has worked fine for me and is needed to achive good enough reception oc tuner two on some frequencies. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Wiki page [was [PATCH] Add remote control support for Hauppauge Nova-T 500]
-- Forwarded message -- From: Henrik Beckman <[EMAIL PROTECTED]> Date: Jul 30, 2007 3:06 PM Subject: Re: [linux-dvb] Wiki page [was [PATCH] Add remote control support for Hauppauge Nova-T 500] To: Nicolas Will <[EMAIL PROTECTED]>, Discussion about mythtv < [EMAIL PROTECTED]> It works, I need it to have acceptable reception on one mux for tuner number 2. /Henrik On 7/30/07, Nicolas Will < [EMAIL PROTECTED]> wrote: > > On Mon, 2007-07-30 at 12:33 +0100, Torgeir Veimo wrote: > > Don't forget this patch! > > > > http://linuxtv.org/pipermail/linux-dvb/2006-December/014926.html > > > > Was there any feedback? > > Nico > > > ___ > 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
Re: [linux-dvb] Wiki page [was [PATCH] Add remote control support for Hauppauge Nova-T 500]
Is the reception patch made by Olivier Danet included in the HG ? /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Fix Hauppauge Nova-T 500 USB disconnects
There is hotplug support, atleast my disconnects doesn´t kill my machine, mythtvbackend needs a restart though. Before the hotplug support I where lucky if my guardian script where able to reboot the machine before it hang. /Henrik On 7/29/07, Peter Magellan <[EMAIL PROTECTED]> wrote: > > On 7/29/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote: > > > > > > It was designe`d before dvb usb devices hit the market. > > > > That's a lame excuse, specially considering Linux DVB has been worked on > for at least 4 years, and there were attempts to refactor things left and > right. > > 4 years is PLENTY of time to properly support "device removal". There was > at least 1 USB device in 2003/4, the Hauppauge Dec2000-t. > > > > > > > ___ > 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
Re: [linux-dvb] Pinnacle Dual DVB-T diversity
Interesting, does the diversity feature with dual antennas work? Let us know if it works better than the nova-t 500, I suspect it should (or atleast be machine dependand) since it´s a USB stick and don´t have it´s own USB controller. /Henrik On 7/15/07, Janne Grunau <[EMAIL PROTECTED]> wrote: On Friday 23 February 2007 09:30:30 [EMAIL PROTECTED] wrote: > Hi > > A patch for the "Pinnacle Dual DVB-T diversity" USB device > can be found at > "www.chez.com/treza/mt2266.htm" attached are two simple patches. The first one adds support for the Hauppauge Nova TD USB stick and the second one is a kconfig fix to select the MT2266 if dib0700 is enabled. Janne ___ 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
[linux-dvb] Fwd: Twinhan vp7045, fighting for a lost cause ?
Hi,
The code to make it work already is in the DVB-T tree, somebody "just" needs
to glue the TDA10046 frontend to the existing VP7045 backend code, Steward
has started this work but I don´t know if he has progressed further than the
attached diff.
The firmware needs to be extracted from the windows driver, I have the
information needed for that, but hopefully we will be allowed to
redistribute the firmware instead.
I think Chris has both the new and the old stick, so he would be a perfect
tester.
That is about all I know.
/Henrik
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/Makefile
--- a/linux/drivers/media/dvb/dvb-usb/Makefile Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/Makefile Thu Sep 7 03:11:12 2006
@@ -1,7 +1,7 @@
dvb-usb-objs = dvb-usb-firmware.o dvb-usb-init.o dvb-usb-urb.o dvb-usb-i2c.o dvb-usb-dvb.o dvb-usb-remote.o
obj-$(CONFIG_DVB_USB) += dvb-usb.o
-dvb-usb-vp7045-objs = vp7045.o vp7045-fe.o
+dvb-usb-vp7045-objs = vp7045.o
obj-$(CONFIG_DVB_USB_VP7045) += dvb-usb-vp7045.o
dvb-usb-vp702x-objs = vp702x.o vp702x-fe.o
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/dvb-usb-firmware.c
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-firmware.c Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-firmware.c Thu Sep 7 03:11:12 2006
@@ -52,27 +52,30 @@
ret = usb_cypress_writemem(udev,hx.addr,hx.data,hx.len);
if (ret != hx.len) {
- err("error while transferring firmware "
-"(transferred size: %d, block size: %d)",
+ printk("error while transferring firmware "
+"(transferred size: %d, block size: %d)\n",
ret,hx.len);
ret = -EINVAL;
break;
}
}
if (ret < 0) {
- err("firmware download failed at %d with %d",pos,ret);
+ printk("firmware download failed at %d with %d\n",pos,ret);
return ret;
}
if (ret == 0) {
/* restart the CPU */
reset = 0;
+ printk("restarting cpu\n");
if (ret || usb_cypress_writemem(udev,cypress[type].cpu_cs_register,&reset,1) != 1) {
- err("could not restart the USB controller CPU.");
+ printk("could not restart the USB controller CPU.\n");
ret = -EINVAL;
}
- } else
+ } else {
+ printk("returning eio\n");
ret = -EIO;
+ }
return ret;
}
@@ -110,7 +113,7 @@
ret = -EINVAL;
break;
}
-
+ printk("done, releasing firmware\n");
release_firmware(fw);
return ret;
}
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/dvb-usb-i2c.c
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-i2c.c Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-i2c.c Thu Sep 7 03:11:12 2006
@@ -12,10 +12,13 @@
int ret = 0;
if (!(d->props.caps & DVB_USB_IS_AN_I2C_ADAPTER))
+ {
+ printk("no cap\n");
return 0;
+ }
if (d->props.i2c_algo == NULL) {
- err("no i2c algorithm specified");
+ printk("no i2c algorithm specified\n");
return -EINVAL;
}
@@ -31,7 +34,7 @@
i2c_set_adapdata(&d->i2c_adap, d);
if ((ret = i2c_add_adapter(&d->i2c_adap)) < 0)
- err("could not add i2c adapter");
+ printk("could not add i2c adapter\n");
d->state |= DVB_USB_STATE_I2C;
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/dvb-usb-init.c
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-init.c Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-init.c Thu Sep 7 03:11:12 2006
@@ -69,11 +69,16 @@
if (d->props.power_ctrl)
d->props.power_ctrl(d,1);
- if ((ret = dvb_usb_urb_init(d)) ||
- (ret = dvb_usb_dvb_init(d)) ||
- (ret = dvb_usb_i2c_init(d)) ||
- (ret = dvb_usb_fe_init(d))) {
+ ret = dvb_usb_urb_init(d);
+ err("init urb %d", ret);
+ ret |= dvb_usb_dvb_init(d);
+ err("init dvb %d", ret);
+ ret |= dvb_usb_i2c_init(d);
+ err("init i2c %d", ret);
+ ret |= dvb_usb_fe_init(d);
+ if(ret) {
dvb_usb_exit(d);
+ err("failed initing. urb, dvb, i2c, fe %d", ret);
return ret;
}
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/dvb-usb.h
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb.h Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb.h Thu Sep 7 03:11:12 2006
@@ -327,6 +327,9 @@
struct module *owner;
void *priv;
+
+ u8 last_result[32]; // hack
+ u8 c; /* transaction counter, wraps around... */
};
extern int dvb_usb_device_init(struct usb_interface *, struct dvb_usb_properties *, struct module *, struct dvb_usb_device **);
diff -r 443f5b4e2365 linux/drivers/media/dvb/dvb-usb/vp7045.c
--- a/linux/drivers/media/dvb/dvb-usb/vp7045.c Sun Sep 3 16:33:10 2006
+++ b/linux/drivers/media/dvb/dvb-usb/vp7045.c Thu Sep 7 03:11:12 2006
@@ -13,6 +13,7 @@
* see Documentation/dvb/README.dvb-usb for more information
*/
#include "vp7045.h"
+#include "tda1004x.h"
/* debug */
int dvb_usb_vp7045_debug;
@@ -168,6 +169,22 @@
{
return vp7045_read_eeprom(d,mac, 6, MAC_0_ADDR);
}
+/*
+static int philips_tdm1316l_request_firmware(struct dvb_frontend* fe, const struct firmware **fw, char* name)
+{
+ struct ttusb* ttusb = (struct ttusb*) fe->dvb->priv;
+
+ return request_firmware(fw, name, &ttusb->
[linux-dvb] Re: dvb breaks ivtv ?
Solved,
Skipped v4l while configuring and only added dvb and let the kernel keep its
original ivtv driver, works now.
/Henrik
On 5/5/07, Henrik Beckman <[EMAIL PROTECTED]> wrote:
Hi,
I´ve added a Hauppage PVR 150 to my machine and it seems as the dvb driver
breakes the ivtv driver.
I have one Nova-T 500 and one PVR 150, if i reset my edgy to the stock
kernel it detects the 150 card, if
i compile the dvb drivers for the Nova-T card the ivtv module refuses to
install, forcing it leads to
May 5 09:19:43 media kernel: [ 344.639208] ivtv:
START INIT IVTV
May 5 09:19:43 media kernel: [ 344.639213] ivtv: version 0.7.4 (tagged
release) loading
May 5 09:19:43 media kernel: [ 344.639215] ivtv: Linux version:
2.6.17-10-generic SMP mod_unload gcc-4.1
May 5 09:19:43 media kernel: [ 344.639218] ivtv: In case of problems
please include the debug info between
May 5 09:19:43 media kernel: [ 344.639220] ivtv: the START INIT IVTV
and END INIT IVTV lines, along with
May 5 09:19:43 media kernel: [ 344.639222] ivtv: any module options,
when mailing the ivtv-users mailinglist.
May 5 09:19:43 media kernel: [ 344.640095] ivtv0: Autodetected Hauppauge
WinTV PVR-150 card (cx23416 based)
May 5 09:19:43 media kernel: [ 344.776951] tuner 6-0043: chip found @
0x86 (ivtv i2c driver #0)
May 5 09:19:43 media kernel: [ 344.805633] tuner 6-0061: chip found @
0xc2 (ivtv i2c driver #0)
May 5 09:19:43 media kernel: [ 344.998220] cx25840 6-0044: cx25843-24
found @ 0x88 (ivtv i2c driver #0)
May 5 09:19:50 media kernel: [ 350.980694] wm8775 6-001b: chip found @
0x36 (ivtv i2c driver #0)
May 5 09:19:51 media kernel: [ 351.743578] ivtv0: loaded
v4l-cx2341x-enc.fw firmware (376836 bytes)
May 5 09:19:51 media kernel: [ 351.938255] ivtv0: Encoder revision:
0x02060039
May 5 09:19:51 media kernel: [ 351.938380] Modules linked in: wm8775
cx25840 tda9887 tuner ivtv binfmt_misc powernow_k8 cpufreq_userspace
cpufreq_stats freq_table cpufreq_powersave cpufreq_ondemand
cpufreq_conservative video tc1100_wmi sony_acpi sbs pcc_acpi i2c_ec hotkey
dev_acpi container button battery asus_acpi ac ipv6 w83627ehf lm92 eeprom
i2c_isa imon_vfd sbp2 parport_pc lp parport af_packet mt2060 tsdev
dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc sr_mod
evdev i2c_algo_bit cdrom sg tveeprom videodev v4l2_common psmouse serio_raw
dibx000_common usbhid v4l1_compat lirc_mceusb2 lirc_dev snd_hda_intel
snd_hda_codec pcspkr snd_pcm_oss snd_mixer_oss floppy snd_pcm snd_timer
nvidia i2c_core shpchp pci_hotplug snd soundcore snd_page_alloc ext3 jbd
ohci_hcd ehci_hcd uhci_hcd usbcore ohci1394 ieee1394 forcedeth ide_generic
generic amd74xx sd_mod sata_nv libata scsi_mod thermal processor fan vesafb
capability commoncap vga16fb cfbcopyarea vgastate cfbimgblt cfbfillrect
fbcon tileblit font
May 5 09:19:51 media kernel: [ 351.938529]
{:ivtv:ivtv_reg_dev+260}
{:ivtv:ivtv_streams_setup+308}
May 5 09:19:51 media kernel: [ 351.938567]
{:ivtv:ivtv_probe+6209}
{try_to_wake_up+844}
May 5 09:19:51 media kernel: [ 351.938657]
{:ivtv:module_start+247}
{sys_init_module+199}
May 5 09:27:43 media kernel: [ 50.932336] ivtv: disagrees about version
of symbol video_unregister_device
May 5 09:27:43 media kernel: [ 50.932342] ivtv: Unknown symbol
video_unregister_device
May 5 09:27:43 media kernel: [ 50.932380] ivtv: disagrees about version
of symbol video_device_alloc
May 5 09:27:43 media kernel: [ 50.932382] ivtv: Unknown symbol
video_device_alloc
May 5 09:27:43 media kernel: [ 50.932425] ivtv: disagrees about version
of symbol video_register_device
May 5 09:27:43 media kernel: [ 50.932427] ivtv: Unknown symbol
video_register_device
May 5 09:27:43 media kernel: [ 50.932618] ivtv: disagrees about version
of symbol video_device_release
May 5 09:27:43 media kernel: [ 50.932620] ivtv: Unknown symbol
video_device_release
May 5 09:27:43 media kernel: [ 50.935089] ivtv: disagrees about version
of symbol video_unregister_device
May 5 09:27:43 media kernel: [ 50.935094] ivtv: Unknown symbol
video_unregister_device
May 5 09:27:43 media kernel: [ 50.935132] ivtv: disagrees about version
of symbol video_device_alloc
May 5 09:27:43 media kernel: [ 50.935134] ivtv: Unknown symbol
video_device_alloc
May 5 09:27:43 media kernel: [ 50.935177] ivtv: disagrees about version
of symbol video_register_device
May 5 09:27:43 media kernel: [ 50.935179] ivtv: Unknown symbol
video_register_device
May 5 09:27:43 media kernel: [ 50.935370] ivtv: disagrees about version
of symbol video_device_release
May 5 09:27:43 media kernel: [ 50.935372] ivtv: Unknown symbol
video_device_release
Normaly during boot this happens
[EMAIL PROTECTED]:~$ grep ivtv /var/log/dmesg
[ 50.932336] ivtv: disagrees about version of symbol
video_unregister_device
[ 50.932342] ivtv: Unknown symbol video_unregister_device
[ 50.932380] ivtv: disagrees about version of symbol video_device
[linux-dvb] dvb breaks ivtv ?
Hi,
I´ve added a Hauppage PVR 150 to my machine and it seems as the dvb driver
breakes the ivtv driver.
I have one Nova-T 500 and one PVR 150, if i reset my edgy to the stock
kernel it detects the 150 card, if
i compile the dvb drivers for the Nova-T card the ivtv module refuses to
install, forcing it leads to
May 5 09:19:43 media kernel: [ 344.639208] ivtv:
START INIT IVTV
May 5 09:19:43 media kernel: [ 344.639213] ivtv: version 0.7.4 (tagged
release) loading
May 5 09:19:43 media kernel: [ 344.639215] ivtv: Linux version:
2.6.17-10-generic SMP mod_unload gcc-4.1
May 5 09:19:43 media kernel: [ 344.639218] ivtv: In case of problems
please include the debug info between
May 5 09:19:43 media kernel: [ 344.639220] ivtv: the START INIT IVTV and
END INIT IVTV lines, along with
May 5 09:19:43 media kernel: [ 344.639222] ivtv: any module options, when
mailing the ivtv-users mailinglist.
May 5 09:19:43 media kernel: [ 344.640095] ivtv0: Autodetected Hauppauge
WinTV PVR-150 card (cx23416 based)
May 5 09:19:43 media kernel: [ 344.776951] tuner 6-0043: chip found @ 0x86
(ivtv i2c driver #0)
May 5 09:19:43 media kernel: [ 344.805633] tuner 6-0061: chip found @ 0xc2
(ivtv i2c driver #0)
May 5 09:19:43 media kernel: [ 344.998220] cx25840 6-0044: cx25843-24
found @ 0x88 (ivtv i2c driver #0)
May 5 09:19:50 media kernel: [ 350.980694] wm8775 6-001b: chip found @
0x36 (ivtv i2c driver #0)
May 5 09:19:51 media kernel: [ 351.743578] ivtv0: loaded
v4l-cx2341x-enc.fw firmware (376836 bytes)
May 5 09:19:51 media kernel: [ 351.938255] ivtv0: Encoder revision:
0x02060039
May 5 09:19:51 media kernel: [ 351.938380] Modules linked in: wm8775
cx25840 tda9887 tuner ivtv binfmt_misc powernow_k8 cpufreq_userspace
cpufreq_stats freq_table cpufreq_powersave cpufreq_ondemand
cpufreq_conservative video tc1100_wmi sony_acpi sbs pcc_acpi i2c_ec hotkey
dev_acpi container button battery asus_acpi ac ipv6 w83627ehf lm92 eeprom
i2c_isa imon_vfd sbp2 parport_pc lp parport af_packet mt2060 tsdev
dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc sr_mod
evdev i2c_algo_bit cdrom sg tveeprom videodev v4l2_common psmouse serio_raw
dibx000_common usbhid v4l1_compat lirc_mceusb2 lirc_dev snd_hda_intel
snd_hda_codec pcspkr snd_pcm_oss snd_mixer_oss floppy snd_pcm snd_timer
nvidia i2c_core shpchp pci_hotplug snd soundcore snd_page_alloc ext3 jbd
ohci_hcd ehci_hcd uhci_hcd usbcore ohci1394 ieee1394 forcedeth ide_generic
generic amd74xx sd_mod sata_nv libata scsi_mod thermal processor fan vesafb
capability commoncap vga16fb cfbcopyarea vgastate cfbimgblt cfbfillrect
fbcon tileblit font
May 5 09:19:51 media kernel: [ 351.938529]
{:ivtv:ivtv_reg_dev+260}
{:ivtv:ivtv_streams_setup+308}
May 5 09:19:51 media kernel: [ 351.938567]
{:ivtv:ivtv_probe+6209}
{try_to_wake_up+844}
May 5 09:19:51 media kernel: [ 351.938657]
{:ivtv:module_start+247}
{sys_init_module+199}
May 5 09:27:43 media kernel: [ 50.932336] ivtv: disagrees about version
of symbol video_unregister_device
May 5 09:27:43 media kernel: [ 50.932342] ivtv: Unknown symbol
video_unregister_device
May 5 09:27:43 media kernel: [ 50.932380] ivtv: disagrees about version
of symbol video_device_alloc
May 5 09:27:43 media kernel: [ 50.932382] ivtv: Unknown symbol
video_device_alloc
May 5 09:27:43 media kernel: [ 50.932425] ivtv: disagrees about version
of symbol video_register_device
May 5 09:27:43 media kernel: [ 50.932427] ivtv: Unknown symbol
video_register_device
May 5 09:27:43 media kernel: [ 50.932618] ivtv: disagrees about version
of symbol video_device_release
May 5 09:27:43 media kernel: [ 50.932620] ivtv: Unknown symbol
video_device_release
May 5 09:27:43 media kernel: [ 50.935089] ivtv: disagrees about version
of symbol video_unregister_device
May 5 09:27:43 media kernel: [ 50.935094] ivtv: Unknown symbol
video_unregister_device
May 5 09:27:43 media kernel: [ 50.935132] ivtv: disagrees about version
of symbol video_device_alloc
May 5 09:27:43 media kernel: [ 50.935134] ivtv: Unknown symbol
video_device_alloc
May 5 09:27:43 media kernel: [ 50.935177] ivtv: disagrees about version
of symbol video_register_device
May 5 09:27:43 media kernel: [ 50.935179] ivtv: Unknown symbol
video_register_device
May 5 09:27:43 media kernel: [ 50.935370] ivtv: disagrees about version
of symbol video_device_release
May 5 09:27:43 media kernel: [ 50.935372] ivtv: Unknown symbol
video_device_release
Normaly during boot this happens
[EMAIL PROTECTED]:~$ grep ivtv /var/log/dmesg
[ 50.932336] ivtv: disagrees about version of symbol
video_unregister_device
[ 50.932342] ivtv: Unknown symbol video_unregister_device
[ 50.932380] ivtv: disagrees about version of symbol video_device_alloc
[ 50.932382] ivtv: Unknown symbol video_device_alloc
[ 50.932425] ivtv: disagrees about version of symbol video_register_device
[ 50.932427] ivtv: Unknown symbol video_register_device
[ 50
Re: [linux-dvb] 2.6.20 with latest hg drivers and dib0700
I´ve been asking this before, but ... Does anyone know if the problem occurs in windows to or is it a linux exclusive, if it´s ok in windows it´s fixabel. Also does anyone know if the hauppage driver includes it own, as in special USB controller driver for the onboard usb controller ? Someone mentioned that the revision of the usb controller on the card is very old, maybe it has a hardware bug that needs special attention ? /Henrik On 4/26/07, Mike H <[EMAIL PROTECTED]> wrote: The disconnect problem is the exact same problem I keep getting. I've tried to ask on the linux-usb lists, but I was told that i "had faulty hardware if I keep getting disconnects" - I don't think so as a lot of us Nova-T users seem to be getting the exact same disconnect problem. Hope someone comes up with a fix soon, or at least can help us figure out what's causing it! Cheers, Mike Chris Murton wrote: > So i've been testing various scenarios since my last post, none of > which have improved matters to any extent with my Hauppage WinTV > Nova-T 500 PCI. > > I thought I'd go back to latest v4l drivers against 2.6.20, but with > these.. nothing locks on MythTV. I'm just getting constant "(L_s) > Partial Lock"s on every single channel I have. This is with both > dvb-usb-dib0700-01.fw and dvb-usb-dib0700-02-rc1.fw. The only way I > can get picture back is to revert to the kernel drivers against either > the old firmware or the rc1 firmware (which both work.. for a while). > > Is there light at the end of the Nova-T 500 PCI card tunnel? > > Thanks, > Chris > > Chris Murton wrote: >> Hi, >> >> I upgraded to the latest hg drivers against a 2.6.20 kernel for my >> Nova-T 500 USB and whilst the Oopses went away, the driver now >> appears to disconnect more frequently than it did before - I'm also >> seeing more frequent partial locks in MythTV (L_s instead of LMS). >> >> Apr 21 10:44:46 basil kernel: usb 2-1: USB disconnect, address 2 >> Apr 21 10:46:44 basil kernel: dvb-usb: could not submit URB no. 0 - >> get them all back >> Apr 21 10:46:44 basil kernel: dvb-usb: error while enabling fifo. >> Apr 21 10:50:10 basil kernel: dvb-usb: error while stopping stream. >> >> I tried the latest firmware that I could find >> (dvb-usb-dib0700-02-rc1.fw) and that gave me similar results with no >> noticeable improvement. >> >> I'm now trying a different approach, using the 2.6.20 kernel drivers >> with the latest firmware.. the partial locks have gone away and no >> disconnects yet but it's only been running for 30 minutes! >> >> Also, I don't know if anyone else has had this but when the USB >> disconnects occur it does not reconnect, but as soon as I reboot >> something must trigger the USB device to come back on as I can see it >> being re-probed and brought online as the box is going down - any >> thoughts? >> >> Thanks >> Chris >> >> ___ >> 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 > ___ 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
Re: [linux-dvb] Oops with Nova-T 500 Dual Tuner
Hi, Does anyone know if this is a linux only issue, or is it present in windows to ? If it´s broken in windows to it´s probably a dead end =( Otherwise I think atleast one nova-t 500 owner on this list had contacts with the linux-usb list, don´t know if it yielded anything but iirc the problem is usb related not dvb driver related. Does any pursue this or did it just die at not dvb related ? /Henrik On 4/18/07, Mike H <[EMAIL PROTECTED]> wrote: On 4/17/2007, "Janne Grunau" <[EMAIL PROTECTED]> wrote: >I can't speak for VDR but you have to restart MythTV's backend daemon at >the moment. But it will change in the future. > >Janne > Thanks for your replies and I will try the latest software as soon as I get chance to set up a dev environment. I really hate to sound like a whiny ungrateful user, but how soon in the future is the bad behaviour likely to change? When I was sold the Nova-T 500 I was told it was supported in the latest kernel and suitable for MythTV. If that means "You can load the module but it disconnects randomly and you have to restart" then the hardware isn't fit for purpose and I should be able to return the card. Plus, I am going away on holiday in a few weeks time and don't want to miss Doctor Who ;) Thanks for any help you can give! Mike ___ 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
Re: [linux-dvb] Twinhan vp7045, fighting for a lost cause ?
Are we allowed to redistribute the new firmware, otherwise we probably need to use dvb_get_firmware.pl ? Would be nice to know if the new firmware works with the old stick, I can take it upon me to write a patch for the perlscript that extract the firmware, but I´d like to know if there is need for two different firmwares or not. The work is already done if we are allowed to redistribute the firmware. Stewart I´ve been looking at your C patch and It´s _atleast_ a 2 weeks of learning ahead of me, so I probably can´t contribute anything meaningful, but I´ll start to relearn a bit C anyway so I´ll gladly accept any further version of the code. TIA /Henrik On 4/16/07, Stewart Smith <[EMAIL PROTECTED]> wrote: (okay, it's been a little while since I played with this... work and life got busy... I intend to get back to it "any week now" :) On Sat, 2007-04-14 at 21:18 +0200, Henrik Beckman wrote: > I`m currently writing a parser in perl that converts the new firmware > that ´ve extracted from the windows file > to the "same" format that is used in the old vp7045 card. I've attached the C code i wrote to do it, as well as the output from it (and a non-working, no-longer-applying patch that gets a little bit closer). > I´ve enhanced the dvb_usb_get_firmware.pl to download and extract the > new vp7045 firmware from the windows driver, but either the load code > needs to be rewritten or the firmware reformatted, both will probably > work but I don´t know wich one is the best way to go. > The new stick has a lowpower version of the FX2 usb controller, so the > current loader "should" work, but I think it needs to load the > firmware > in chunks of 64 bytes (this is how windows does it) instead of one > 8192 byte chunk as the current formatting tells windows (this is why > I´m converting the firmware, to verify this theory). hrrm... now I'm a bit hazy on the details.. but i think that my fw.c does actually make the firmware loader do that. > > "Based on usb snoop data, I was able to write a patch to the dvb-usb > code > so it could distinguish between the two devices. That was as far as I > got. I don't know of anyone else who has gone any further." Mine did that a bit IIRC. > That patch would be very very good for me. > > Any information you can supply me with is greatly appriciated. > Also do the old cards work with the new firmware ? that i don't know - i just have a new card. > If or when we get a firmware on the stick do we need to attach > another modified frontend to handle the TDA10046 or will that > be the end it ? there's existing drivers for the frontend... so it's just gluing them together... which i've had a bit of a go at, but didn't finish (or get working). > > /Henrik > > > On 4/13/07, Chris Wylie <[EMAIL PROTECTED]> wrote: > Henrik Beckman wrote: > > > > I´m prepared to pour more time into this, but I´d like to > know > > Henrik, > > I have just read all of your posts. I have one of these > devices and the > same problems. In fact I have a pair of vp7045 tuners, one > with the > mt352 and one with the tda10046 (very useful to make > comparisons). I > tried to make it work last year. I got some good information > but no > solution and had to put the project aside due to lack of time > and expertise. > > Here is what I know. > > The vp7045 with tda10046 needs a firmware download that the > current > dvb-usb code does not know about. Patrick Boettcher > <[EMAIL PROTECTED]> knows the existing vp7045 code and > was able > to assist by getting some limited information from TwinHan. We > also > exchanged some emails with Stewart Smith > <[EMAIL PROTECTED]> who > also has one of these devices. > > The firmware can be extracted from the available Windows > driver files. I > think I wrote a script to do this. > > Based on usb snoop data, I was able to write a patch to the > dvb-usb code > so it could distinguish between the two devices. That was as > far as I > got. I don't know of anyone else who has gone any further. > > The next step would be to write the code to download the new > firmware to > the device. My understanding of the existing code base was too > limited > to be able to write this in a reasonable amount of time. > > I wish I had more time and skills for this but perhaps you can > make some > headway. You can have my code patch if it helps. > > Regards, > > Chris > -- Stewart Smith ([EMAIL PROTECTED]) http://www.flamingspork.com/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Twinhan vp7045, fighting for a lost cause ?
Perfect, I`m currently writing a parser in perl that converts the new firmware that ´ve extracted from the windows file to the "same" format that is used in the old vp7045 card. I´ve enhanced the dvb_usb_get_firmware.pl to download and extract the new vp7045 firmware from the windows driver, but either the load code needs to be rewritten or the firmware reformatted, both will probably work but I don´t know wich one is the best way to go. The new stick has a lowpower version of the FX2 usb controller, so the current loader "should" work, but I think it needs to load the firmware in chunks of 64 bytes (this is how windows does it) instead of one 8192 byte chunk as the current formatting tells windows (this is why I´m converting the firmware, to verify this theory). "Based on usb snoop data, I was able to write a patch to the dvb-usb code so it could distinguish between the two devices. That was as far as I got. I don't know of anyone else who has gone any further." That patch would be very very good for me. Any information you can supply me with is greatly appriciated. Also do the old cards work with the new firmware ? If or when we get a firmware on the stick do we need to attach another modified frontend to handle the TDA10046 or will that be the end it ? /Henrik On 4/13/07, Chris Wylie <[EMAIL PROTECTED]> wrote: Henrik Beckman wrote: > > I´m prepared to pour more time into this, but I´d like to know Henrik, I have just read all of your posts. I have one of these devices and the same problems. In fact I have a pair of vp7045 tuners, one with the mt352 and one with the tda10046 (very useful to make comparisons). I tried to make it work last year. I got some good information but no solution and had to put the project aside due to lack of time and expertise. Here is what I know. The vp7045 with tda10046 needs a firmware download that the current dvb-usb code does not know about. Patrick Boettcher <[EMAIL PROTECTED]> knows the existing vp7045 code and was able to assist by getting some limited information from TwinHan. We also exchanged some emails with Stewart Smith <[EMAIL PROTECTED]> who also has one of these devices. The firmware can be extracted from the available Windows driver files. I think I wrote a script to do this. Based on usb snoop data, I was able to write a patch to the dvb-usb code so it could distinguish between the two devices. That was as far as I got. I don't know of anyone else who has gone any further. The next step would be to write the code to download the new firmware to the device. My understanding of the existing code base was too limited to be able to write this in a reasonable amount of time. I wish I had more time and skills for this but perhaps you can make some headway. You can have my code patch if it helps. Regards, Chris ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Twinhan vp7045, fighting for a lost cause ?
Not that I really get the meaning of "I demand that Henrik Beckman may or may not have written..." But thanks for the /usr/include/asm-generic/errno.h, trying to wrap ones to that good at C brain around this is a bit much to me, btw it was in /usr/include/asm-generic/errno-base.h. /Henrik On 4/11/07, Darren Salt <[EMAIL PROTECTED]> wrote: I demand that Henrik Beckman may or may not have written... > I´m prepared to pour more time into this, but I´d like to know [snip] > 3. What is error 22 ? [snip] > Apr 10 19:37:29 media kernel: [ 2746.986554] dvb_usb_vp7045: probe of 2-6: > 1.0 failed with error -22 [snip] EINVAL, according to /usr/include/asm-generic/errno.h. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL. "It'll drive the conspiracy nuts crazy, but WTH." ___ 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
[linux-dvb] Twinhan vp7045, fighting for a lost cause ?
I´m prepared to pour more time into this, but I´d like to know 1. Is this a lost cause/impossible since _no one_ seems to be able or interested in helping ( I´ll accept that it might be my own ignorance). 2. Does the change from zt352 to tda10046 hide behind the firmware layer or do I need to attach another frontend ? 3. What is error 22 ? The VP7045 is available from many online retailers where I live and it is priced competitivly so I don´t feel that getting it to work is for nothing. TIA /Henrik I have snooped initialization of the stick in both windows with working driver and in linux with the non working driver. I figure that it should start like this. 00 20 00 00 02 15 which I decode as 8192 bytes starting with 02 15, what the second 00 00 does I don´t know. The current linux firmware starts with 10 00 00 00 02 14. The firmware looks like it ends with a bunch of aa aa aa aa aa, then C4 4C, cutting there gives a firmware with 8192. Filesize is then 8196 with 00 20 00 00 in the head. This is how it looks in the snoop logs, current version 01 Transfer 40 a0 00 e6 00 00 01 00Setup Packet 02 14 30 c2 b7 00 00 00 d2 b6 00 00 00 d2 b7 00Transfer The newer revision is 01 Transfer 40 a0 00 e6 00 00 01 00Setup Packet, correct ?? 02 15 8a c2 b7 00 00 00 d2 b6 00 00 00 d2 b7 00Transfer Trying to initialize the stick gives, Apr 10 19:37:29 media kernel: [ 2746.966139] dvb-usb: found a 'Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)' in cold state, will try to load a firmware Apr 10 19:37:29 media kernel: [ 2746.974549 ] dvb-usb: downloading firmware from file 'dvb-usb-vp7045-01.fw' Apr 10 19:37:29 media kernel: [ 2746.986554] dvb_usb_vp7045: probe of 2-6: 1.0 failed with error -22 Apr 10 19:37:29 media kernel: [ 2746.987120] usbcore: registered new driver dvb_usb_vp7045 This version of the stick has a TDA10046 inside, I´m stuck. Help /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 reception differencies between the two tuners
Seems ok to me now, everuthing seem better with the patch. I get ~55-60% signal strenght on both tuners for all channels, my LNA seems to always be 1, but I suspetct that it doesn´t work. /Henrik On 4/8/07, Henrik Beckman <[EMAIL PROTECTED]> wrote: Hi, Reception on primary tuner seems to be worse, more glitches in decoding (haven´t run tzap), could be foilage or lack of LNA though. I´m not realy dependent upon LNA since my reception is ok, but I´ll verify if LNA is working without manual module load. On the other hand the secondary tuner is now usable for all channels. Anything I can do to help improving this patch further ? /Henrik On 4/7/07, Simon Lundell <[EMAIL PROTECTED]> wrote: > > Hi, > > It did not solve the problem here. I upgraded to the latest hg version, > applied the patch, make:d and make install:ed. The signal strength > dropped from around a700 to 8000 in tzap. The second tuner is even > worse. The thing is that forcing lna activation does not seem to have > any effect (via boot parameter or modules.autoload). It worked before I > upgraded and this might explain the drop in signal strength. If i rmmod > > dvb_usb_dib0700 && modprobe dvb_usb_dib0700 force_lna_activation=1 I get > a higher signal strength. The second tuner is still worse than the first > (b800 compared to 9e00). Both tuner gets better signal strength than > before. > > Best regards, > Simon > > > > [EMAIL PROTECTED] ~ $ cat > /sys/module/dvb_usb_dib0700/parameters/force_lna_activation > 0 > > > Henrik Beckman skrev: > > Hi, =) > > > > The patch seems to solve the problem for me, I´ll have to run it for a > > > week or so to be 100%. > > > > Great work !! > > > > /Henrik > > > > These are my channels, the ones in bold had problems on tuner 2 before > > the patch. > > > > SVT2 > > > ABC:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTER > > > VAL_1_8:HIERARCHY_NONE:1029:1028:5060 > > SVT24 > > > ABC:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTE > > RVAL_1_8:HIERARCHY_NONE:1249:1248:5170 > > SVT2 > > > Tvärsnytt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD > > > > _INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5050 > > SVT2 Tal > > > txt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_I > > > > > NTERVAL_1_8:HIERARCHY_NONE:1299:1026:1290 > > > Barn/Kunskapsk.:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUAR > > > > D_INTERVAL_1_8:HIERARCHY_NONE:879:878:870 > > > SVT1:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_ > > > > 1_8:HIERARCHY_NONE:1019:1018:1010 > > SVT1 Tal > > > txt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_I > > > > > NTERVAL_1_8:HIERARCHY_NONE:1289:1016:1280 > > TV4 > > > Uppland:47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_IN > > > > TERVAL_1_8:HIERARCHY_NONE:1049:1048:6100 > > > TV6:47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1 > > _8:HIERARCHY_NONE:1079:1078:1070 > > > > > > > > On 4/4/07, *olivier danet* < [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Hello > > > > I posted a while ago (15 dec. 2006 ) a patch for the Nova-T 500 > > which may reduce your problem. > > > > Search "[linux-dvb] [PATCH] Tuner calibration for some Nova-T > > devices" > > > > Regards > > DO > > > > > > */Avez-vous déjà en pensé d`envoyer des SMS de l`internet?/* > > Lorsque vous entrez ce Code Promo *14071789* dans l`ordre du grand > > paquet de 70 extra SMS sous « SMS hors-forfait » dans « mon > > compte », vous recevrez au prix une remise de *20%.* L`offre est > > valable jusqu`au 1. mai 2007 > > Cliquez-ici pour vous inscrire chez Caramail > > <http://caramail.lycos.fr/> > > > > > > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] can someone explain this to me, vp7045 firmware
I have snooped initialization of the stick in both windows with working driver and in linux with the non working driver. I figure that it should start like this. 00 20 00 00 02 15 which I decode as 8192 bytes starting with 02 15, what the second 00 00 does I don´t know. The current linux firmware starts with 10 00 00 00 02 14. The firmware looks like it ends with a bunch of aa aa aa aa aa, then C4 4C, cutting there gives a firmware with 8192. Filesize is then 8196 with 00 20 00 00 in the head. This is how it looks in the snoop logs, current version 01 Transfer 40 a0 00 e6 00 00 01 00Setup Packet 02 14 30 c2 b7 00 00 00 d2 b6 00 00 00 d2 b7 00Transfer The newer revision is 01 Transfer 40 a0 00 e6 00 00 01 00Setup Packet, correct ?? 02 15 8a c2 b7 00 00 00 d2 b6 00 00 00 d2 b7 00Transfer Trying to initialize the stick gives, Apr 10 19:37:29 media kernel: [ 2746.966139] dvb-usb: found a 'Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II)' in cold state, will try to load a firmware Apr 10 19:37:29 media kernel: [ 2746.974549] dvb-usb: downloading firmware from file 'dvb-usb-vp7045-01.fw' Apr 10 19:37:29 media kernel: [ 2746.986554] dvb_usb_vp7045: probe of 2-6: 1.0 failed with error -22 Apr 10 19:37:29 media kernel: [ 2746.987120] usbcore: registered new driver dvb_usb_vp7045 This version of the stick has a TDA10046 inside, I´m stuck. Help /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 reception differencies between the two tuners
Hi, Reception on primary tuner seems to be worse, more glitches in decoding (haven´t run tzap), could be foilage or lack of LNA though. I´m not realy dependent upon LNA since my reception is ok, but I´ll verify if LNA is working without manual module load. On the other hand the secondary tuner is now usable for all channels. Anything I can do to help improving this patch further ? /Henrik On 4/7/07, Simon Lundell <[EMAIL PROTECTED]> wrote: Hi, It did not solve the problem here. I upgraded to the latest hg version, applied the patch, make:d and make install:ed. The signal strength dropped from around a700 to 8000 in tzap. The second tuner is even worse. The thing is that forcing lna activation does not seem to have any effect (via boot parameter or modules.autoload). It worked before I upgraded and this might explain the drop in signal strength. If i rmmod dvb_usb_dib0700 && modprobe dvb_usb_dib0700 force_lna_activation=1 I get a higher signal strength. The second tuner is still worse than the first (b800 compared to 9e00). Both tuner gets better signal strength than before. Best regards, Simon [EMAIL PROTECTED] ~ $ cat /sys/module/dvb_usb_dib0700/parameters/force_lna_activation 0 Henrik Beckman skrev: > Hi, =) > > The patch seems to solve the problem for me, I´ll have to run it for a > week or so to be 100%. > > Great work !! > > /Henrik > > These are my channels, the ones in bold had problems on tuner 2 before > the patch. > > SVT2 > ABC:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTER > VAL_1_8:HIERARCHY_NONE:1029:1028:5060 > SVT24 > ABC:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTE > RVAL_1_8:HIERARCHY_NONE:1249:1248:5170 > SVT2 > Tvärsnytt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD > > _INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5050 > SVT2 Tal > txt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_I > > NTERVAL_1_8:HIERARCHY_NONE:1299:1026:1290 > Barn/Kunskapsk.:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUAR > > D_INTERVAL_1_8:HIERARCHY_NONE:879:878:870 > SVT1:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_ > > 1_8:HIERARCHY_NONE:1019:1018:1010 > SVT1 Tal > txt:62600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_I > > NTERVAL_1_8:HIERARCHY_NONE:1289:1016:1280 > TV4 > Uppland:47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_IN > > TERVAL_1_8:HIERARCHY_NONE:1049:1048:6100 > TV6:47400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1 > _8:HIERARCHY_NONE:1079:1078:1070 > > > > On 4/4/07, *olivier danet* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hello > > I posted a while ago (15 dec. 2006 ) a patch for the Nova-T 500 > which may reduce your problem. > > Search "[linux-dvb] [PATCH] Tuner calibration for some Nova-T > devices" > > Regards > DO > > > */Avez-vous déjà en pensé d`envoyer des SMS de l`internet?/* > Lorsque vous entrez ce Code Promo *14071789* dans l`ordre du grand > paquet de 70 extra SMS sous « SMS hors-forfait » dans « mon > compte », vous recevrez au prix une remise de *20%.* L`offre est > valable jusqu`au 1. mai 2007 > Cliquez-ici pour vous inscrire chez Caramail > <http://caramail.lycos.fr/> > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 reception differencies between the wto tuners
Hi, It doesn´t seem to have anything to do with the LNA. I smell a bug. /Henrik On 4/2/07, Simon Lundell <[EMAIL PROTECTED]> wrote: Henrik Beckman skrev: > Hi, > > I just realised that I on the first tuner on the card has flawless > reception on all channels right now but tuner two has very bad > reception (as in not usable) > on several channels. > Is this a known hardware limitation and/or bug or have I´ve just > stumbled on something. > > I have the LNA activated. I am experiencing the same thing. Also have LNA activated. //Simon ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] nova-t 500 reception differencies between the wto tuners
Hi, I just realised that I on the first tuner on the card has flawless reception on all channels right now but tuner two has very bad reception (as in not usable) on several channels. Is this a known hardware limitation and/or bug or have I´ve just stumbled on something. I have the LNA activated. TIA /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Random Oops
Yes, soft disconnect caused by something in the USB communication chain, exactly what I don´t know. Try a later or latest version of the dvb drivers or even start with a newer kernel and then newer dvb. Also check cables and other sources of interference. Search the archive for nova-t 500 and there will be al lot of threads about soft disconnects. /Henrik On 3/14/07, Benjamin Gillam <[EMAIL PROTECTED]> wrote: My card has not been (physically) disconnected from my computer for over 5 weeks, whilst this crash happened yesterday. Is it perhaps a "soft" disconnect (not sure of correct term)? If so, what can I do to prevent it from "soft" disconnecting in future? Is it issue with the card, or my computers USB ports, or USB controller chipset, or what? Any ideas gratefully received! Kind regards, and thank you for your fast response, Benjie Gillam Henrik Beckman wrote: > Hi, > > [17267534.12] usb 1-3: USB disconnect, address 2 > [17267534.12] dvb-usb: bulk message failed: -22 (1/-909000848) > [17267534.124000] dvb-usb: WideView WT-220U PenType Receiver > (Typhoon/Freecom) > successfully deinitialized and disconnected. > > Your DVB card is disconnected and that isn´t handled gracefully, DVB > doesn´t handle hotplug. > Then your mythbackend bites the dust. This happens when there is a > disconnct during use, the disconnect is the problem. > > For someone to come with something useful, lsusb, kernelversion and > hardware information probably need to be included, but I´m no expert. > > /Henrik > > > > > > > On 3/13/07, *Benjamin Gillam* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Why am I getting these random kernel Oops? Is it DVB's fault or > something else? > I have no knowledge of DVB or kernel internals... > > Kind regards, > > Benjie. > > > [17267534.12] ehci_hcd :00:10.4 : fatal error > [17267534.12] ehci_hcd :00:10.4: HC died; cleaning up > [17267534.12] usb 1-3: USB disconnect, address 2 > [17267534.12] dvb-usb: bulk message failed: -22 (1/-909000848) > [17267534.124000 ] dvb-usb: WideView WT-220U PenType Receiver > (Typhoon/Freecom) > successfully deinitialized and disconnected. > [17267534.132000] BUG: unable to handle kernel paging request at > virtual address > 2d31005f > [17267534.132000 ] printing eip: > [17267534.132000] f8d89b7e > [17267534.132000] *pde = > [17267534.132000] Oops: [#1] > [17267534.132000] SMP > [17267534.132000] Modules linked in: lirc_serial binfmt_misc ipt_TCPMSS > xt_tcpudp ip_nat_irc ip_nat_ftp iptable_nat cpufreq_userspace > cpufreq_stats > freq_table cpufreq_powersave cpufreq_ondemand cpufreq_conservative video > tc1100_wmi sbs sony_acpi i2c_ec asus_acpi it87 hwmon_vid eeprom > i2c_isa ipaq > usbserial ppp_async ppp_generic crc_ccitt ip6table_filter ip6_tables > sbp2 > lirc_dev bt878 tvaudio saa7134_alsa tda9887 tuner snd_seq_dummy > snd_seq_oss > snd_seq_midi snd_seq_midi_event snd_seq nvidia bttv dvb_usb_dtt200u > dvb_usb > saa7134 snd_bt87x snd_via82xx dvb_core dvb_pll snd_cmipci > snd_opl3_lib snd_hwdep > snd_mpu401_uart snd_via82xx_modem snd_ac97_codec snd_ac97_bus > snd_pcm_oss > snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device video_buf > v4l1_compat > ir_kbd_i2c ir_common analog via_agp agpgart pcspkr v4l2_common > tveeprom videodev > gameport snd soundcore snd_page_alloc usbhid vesafb fbcon tileblit > font bitblit > softcursor vga16fb vgastate capability commoncap fan thermal > processor sata_via > libata sd_mod generic ide_disk ide_cd cdrom ohci1394 ieee1394 > uhci_hcd ehci_hcd > ide_generic reiserfs evdev sg shpchp pci_hotplug btcx_risc i2c_algo_bit > i2c_viapro compat_ioctl32 serio_raw skge psmouse sk98lin floppy > tsdev slhc > i2c_dev i2c_core usb_storage scsi_mod libusual usbtest usbcore > af_packet md_mod > dm_mod ipv6 via82cxxx ext2 ext3 jbd hotkey dev_acpi ac pcc_acpi > button container > battery lp parport_pc ppdev parport iptable_filter xt_state > ip_conntrack_ftp > ip_conntrack_irc ipt_REJECT ipt_TOS ipt_MASQUERADE ip_nat > ip_conntrack nfnetlink > ipt_LOG iptable_mangle ip_tables xt_limit x_tables rfcomm l2cap > bluetooth > [17267534.132000] CPU:0 > [17267534.132000] EIP:0060:[]Tainted: PF VLI > [17267534.132000] EFLAGS: 00010246 (2.6.17-11-generic #2) > [17267534.132000] EIP is at dvb_dvr_poll+0x3e/0x90 [dvb_core] > [17267534.132000] eax: ebx: 0106 ecx: f8d89b40 >
Re: [linux-dvb] Random Oops
Hi, [17267534.12] usb 1-3: USB disconnect, address 2 [17267534.12] dvb-usb: bulk message failed: -22 (1/-909000848) [17267534.124000] dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully deinitialized and disconnected. Your DVB card is disconnected and that isn´t handled gracefully, DVB doesn´t handle hotplug. Then your mythbackend bites the dust. This happens when there is a disconnct during use, the disconnect is the problem. For someone to come with something useful, lsusb, kernelversion and hardware information probably need to be included, but I´m no expert. /Henrik On 3/13/07, Benjamin Gillam <[EMAIL PROTECTED]> wrote: Why am I getting these random kernel Oops? Is it DVB's fault or something else? I have no knowledge of DVB or kernel internals... Kind regards, Benjie. [17267534.12] ehci_hcd :00:10.4: fatal error [17267534.12] ehci_hcd :00:10.4: HC died; cleaning up [17267534.12] usb 1-3: USB disconnect, address 2 [17267534.12] dvb-usb: bulk message failed: -22 (1/-909000848) [17267534.124000] dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully deinitialized and disconnected. [17267534.132000] BUG: unable to handle kernel paging request at virtual address 2d31005f [17267534.132000] printing eip: [17267534.132000] f8d89b7e [17267534.132000] *pde = [17267534.132000] Oops: [#1] [17267534.132000] SMP [17267534.132000] Modules linked in: lirc_serial binfmt_misc ipt_TCPMSS xt_tcpudp ip_nat_irc ip_nat_ftp iptable_nat cpufreq_userspace cpufreq_stats freq_table cpufreq_powersave cpufreq_ondemand cpufreq_conservative video tc1100_wmi sbs sony_acpi i2c_ec asus_acpi it87 hwmon_vid eeprom i2c_isa ipaq usbserial ppp_async ppp_generic crc_ccitt ip6table_filter ip6_tables sbp2 lirc_dev bt878 tvaudio saa7134_alsa tda9887 tuner snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq nvidia bttv dvb_usb_dtt200u dvb_usb saa7134 snd_bt87x snd_via82xx dvb_core dvb_pll snd_cmipci snd_opl3_lib snd_hwdep snd_mpu401_uart snd_via82xx_modem snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device video_buf v4l1_compat ir_kbd_i2c ir_common analog via_agp agpgart pcspkr v4l2_common tveeprom videodev gameport snd soundcore snd_page_alloc usbhid vesafb fbcon tileblit font bitblit softcursor vga16fb vgastate capability commoncap fan thermal processor sata_via libata sd_mod generic ide_disk ide_cd cdrom ohci1394 ieee1394 uhci_hcd ehci_hcd ide_generic reiserfs evdev sg shpchp pci_hotplug btcx_risc i2c_algo_bit i2c_viapro compat_ioctl32 serio_raw skge psmouse sk98lin floppy tsdev slhc i2c_dev i2c_core usb_storage scsi_mod libusual usbtest usbcore af_packet md_mod dm_mod ipv6 via82cxxx ext2 ext3 jbd hotkey dev_acpi ac pcc_acpi button container battery lp parport_pc ppdev parport iptable_filter xt_state ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_TOS ipt_MASQUERADE ip_nat ip_conntrack nfnetlink ipt_LOG iptable_mangle ip_tables xt_limit x_tables rfcomm l2cap bluetooth [17267534.132000] CPU:0 [17267534.132000] EIP:0060:[]Tainted: PF VLI [17267534.132000] EFLAGS: 00010246 (2.6.17-11-generic #2) [17267534.132000] EIP is at dvb_dvr_poll+0x3e/0x90 [dvb_core] [17267534.132000] eax: ebx: 0106 ecx: f8d89b40 edx: 2d310063 [17267534.132000] esi: ec931960 edi: 2d310033 ebp: f70c5e9c esp: f70c5c10 [17267534.132000] ds: 007b es: 007b ss: 0068 [17267534.132000] Process mythbackend (pid: 30166, threadinfo=f70c4000 task=f2726030) [17267534.132000] Stack: c012b7c0 f2726030 0020 ec931960 c017e085 f70c5c54 f70c5fac [17267534.132000]a39fe3f4 a39fe3fc f70c5e94 f70c5e94 0001 0001 [17267534.132000]f70c5e94 c017ed60 0001 ec931960 f2726030 [17267534.132000] Call Trace: [17267534.132000] process_timeout+0x0/0x10 do_sys_poll+0x205/0x400 [17267534.132000] __pollwait+0x0/0xf0 default_wake_function+0x0/0x10 [17267534.132000] qh_append_tds+0x133/0x540 [ehci_hcd] qh_urb_transaction+0xca/0x320 [ehci_hcd] [17267534.132000] ehci_urb_enqueue+0xf4/0xd00 [ehci_hcd] dvb_dmx_swfilter_packet+0x34d/0x370 [dvb_core] [17267534.132000] usb_submit_urb+0x199/0x200 [usbcore] hcd_submit_urb+0x1dd/0x930 [usbcore] [17267534.132000] dvb_dmxdev_ts_callback+0xa4/0xd0 [dvb_core] dvb_dmx_swfilter_packet+0x34d/0x370 [dvb_core] [17267534.132000] rb_insert_color+0x71/0xd0 usb_submit_urb+0x199/0x200 [usbcore] [17267534.132000] dvb_usb_urb_complete+0x88/0x100 [dvb_usb] do_timer+0x39/0x360 [17267534.132000] mark_offset_pmtmr+0x22/0xee0 timer_interrupt+0x6e/0xb0 [17267534.132000] __do_IRQ+0xc5/0x110 do_IRQ+0x1e/0x30 [17267534.132000] common_interrupt+0x1a/0x20 copy_to_user+0x39/0x70 [17267534.132000] dvb_ringbuffer_read+0xcf/0x100 [dvb_core] dvb_dmxdev_buffer_read+0x5f/0x1b0 [dvb_core] [17267534.132000] ehci_irq+0x11e/0x190 [ehci_hcd] vfs_read+0x119/0x180 [17267
Re: [linux-dvb] Nova-T 500 Channel scanning + EIT + Kernel oops...
EIT seems to "trigger" the event, but it will happen even with EIT disabled,
but much less frequent.
EIT forces the adapter to be constantly active.
/Henrik
On 3/11/07, Juha Ruotsalainen <[EMAIL PROTECTED]> wrote:
I'm using VDR. Could someone with more understanding tell me, can EIT
be disabled in VDR? Or, alternatively, give an educated guess why
enabling EIT causes USB disconnects?
On 3/11/07, Eduard Huguet <[EMAIL PROTECTED]> wrote:
> >
> > From: Antti P Miettinen <[EMAIL PROTECTED]>
> > To: linux-dvb@linuxtv.org
> > Date: Sat, 10 Mar 2007 21:44:37 +0200
> > Subject: [linux-dvb] Re: Nova-T 500 Channel scanning + EIT + Kernel
> > oops...
> > "Henrik Beckman" <[EMAIL PROTECTED]> writes:
> > > Are there any differences in the windows stream ?
> >
> > Well, I've only managed to look at the beginning so far, but there
> > seem to be at least some minor differences.
> >
> > The trace starts (after some descriptor reads) with firmware
> > loading. The firmware seems to be in more or less Intel hex record [1]
> > format and checked against that assumption I think what I extracted
> > from the trace should be more or less OK. At least the record wise
> > checksums match.
> >
> > There are some messages for which I cannot find any counterparts in
> > the linux driver code. Before the firmware download starts the windows
> > driver sends a five byte bulk packet to EP1:
> >
> > 02 a1 00 00 08
> >
> > and receives eight byte bulk packet:
> >
> > d0 40 20 50 99 00 01 05
> >
> > Then the firmware is sent just like in linux. Before the jumpram
> > message, there is one 12 byte read:
> >
> > 00 00 00 00 70 00 00 00 06 11 60 d4
> >
> > Looks like this contains the start address, maybe some kind of
> > checksum.
> >
> > Then some decsriptor reading, setting configs, and then something that
> > looks like the GPIO setting in the linux driver, but there's a small
> > difference from what is done in bristol_frontend_attach(). If I'm
> > interpreting the log correctly the windows driver is doing the
> > equivalent of:
> >
> > dib0700_set_gpio(adap->dev, GPIO6, GPIO_OUT, 1);
> > dib0700_set_gpio(adap->dev, GPIO9, GPIO_OUT, 0);
> > dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 0);
> > msleep(10);
> > dib0700_set_gpio(adap->dev, GPIO10, GPIO_OUT, 1);
> >
> > And then I got tired :-)
> >
> > I'll try deciphering the log more later.
> >
> > [1] http://en.wikipedia.org/wiki/Intel_HEX
> >
> > --
> > http://www.iki.fi/~ananaza/ <http://www.iki.fi/%7Eananaza/>
> >
>
>
>
> Just as a matter of update, I've reenabled EIT scanning in MythTV just
for
> testing. It took less than 5 min to get a kernel oops due to the USB
> disconnect ("dmesg | grep disconn" was explicit enough...).
>
> I don't know if this can help you in any way, but in my case the
equation is
> pretty clear:
>
>- EIT = USB disconnect
>- No EIT = No USB disconnect
>
> :D
>
> Cheers, and thank you again for your hard work.
> Eduard
>
--
jussi
___
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
Re: [linux-dvb] Re: Nova-T 500 Channel scanning + EIT + Kernel oops...
Hi, No problem, hopefully someone will take a peek. www.struct.se/vp7045a.html me struggling with firmwares, probably the same technique, but anyway. Are there any differences in the windows stream ? /Henrik On 3/9/07, Antti P Miettinen <[EMAIL PROTECTED]> wrote: I got this off list, Henrik I hope you don't mind me going back to the list.. From: "Henrik Beckman" <[EMAIL PROTECTED]> > If someone could run usbsnoop on their windows installed nova-t 500 it might > be useful to look on how it looks in the windows stream ? Since I have another PC with windows installed I put the card to the windows machine, installed the 3.3c drivers from www.hauppauge.co.uk and took a trace with SniffUsb 2.0 [1]. The trace is a bit large (over 600M compressed), but it is available at http://brigitte.dna.fi/~apm/UsbSnoop.log.gz - will take over an hour to tricle over my link and the machine can go down whenever I need to e.g. power cycle to get new firmware loaded or something. There is also a version processed with the parser.pl from the mbrechberger hg repo as http://brigitte.dna.fi/~apm/UsbSnoop.txt.gz which is "only" a bit over 200M. If someone wants the logs mail me so I know not to reboot during transfer. I tried to extract also firmware from the trace with very questionable method of inspecting the start and end patterns of the firmwares I have and just cutting the matching part from the traffic. The result is at http://brigitte.dna.fi/~apm/dvb-usb-dib0700-h3.3c.fw, but with this fw the frontend does not attach, i.e. not very useful, probably broken. [1] http://www.pcausa.com/Utilities/UsbSnoop/default.htm -- http://www.iki.fi/~ananaza/ ___ 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
[linux-dvb] Re: twinhan alpha vp7045A newer rev, firmware
Making progress, I´ve managed to parse and upload data to the device /Henrik On 2/23/07, Henrik Beckman <[EMAIL PROTECTED]> wrote: Hi, I have managed to capture some traffic with usbsnoop, I´ve captured from insertion of the stick to a few seconds of tuning. The snoop can be found here, http://www.struct.se/usbsnoop.log-1.bz2 Any hints on extracting the firmware ? http://www.isely.net/pvrusb2/utils.html been looking at the code but nothing further yet. Anyone ? /Henrik On 2/22/07, Henrik Beckman <[EMAIL PROTECTED]> wrote: > > Hi, > > Anyone had any succes with getting the newer alphas to work ? > http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html > > If not I will try to extract the firmware from the latest windows > driver, can anyone help me with hints on how to do this. > Would it be possible to initialize the stick in windows and then without > deinitializing it connect it to linux and download the firmware ? > (thinking vmware or a powered hub here). > > TIA > /Henrik > > > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: twinhan alpha vp7045A newer rev, firmware
Hi, I have managed to capture some traffic with usbsnoop, I´ve captured from insertion of the stick to a few seconds of tuning. The snoop can be found here, http://www.struct.se/usbsnoop.log-1.bz2 Any hints on extracting the firmware ? http://www.isely.net/pvrusb2/utils.html been looking at the code but nothing further yet. Anyone ? /Henrik On 2/22/07, Henrik Beckman <[EMAIL PROTECTED]> wrote: Hi, Anyone had any succes with getting the newer alphas to work ? http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html If not I will try to extract the firmware from the latest windows driver, can anyone help me with hints on how to do this. Would it be possible to initialize the stick in windows and then without deinitializing it connect it to linux and download the firmware ? (thinking vmware or a powered hub here). TIA /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] best usb stick for linux?
Hi, Anyone know if WinTV Nova-TD USB is supported in linux. Or WinTV Nova-T USB Also is it possible to recieve the entire mux with a USB stick, to get acces to several channels simultaionsly in VDR. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] twinhan alpha vp7045A newer rev, firmware
Hi, Anyone had any succes with getting the newer alphas to work ? http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014202.html If not I will try to extract the firmware from the latest windows driver, can anyone help me with hints on how to do this. Would it be possible to initialize the stick in windows and then without deinitializing it connect it to linux and download the firmware ? (thinking vmware or a powered hub here). TIA /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Another Nova-T 500 Dual DVB-T Oops
A script that collects logfiles and reboots after an disconnect does both save your recording and collect data in an orderly way ; ) Unfortunatly I´m not able to change kernel right know so I can´t contribute =( /Henrik On 1/25/07, Matt Doran <[EMAIL PROTECTED]> wrote: Henrik Beckman wrote: > Hi, > > On my myth box I have a simple script that checks messages every 10sec > and reboots if the usb disconnect line appears, I collect timestamped > copies of the messages files. > A distinct pattern i still to occur, but some channels are worse than > others, but that might be time of day caused reception variations. > > Starting recording 3min ahead gives the box time to reboot and resume > recording. > > /Henrik > > Thanks, but Oops' are bad and should never happen. I'd like to work with the driver developers on this list to resolve the issue. I'd like to provide as much info as possible in the hope that we can get this fixed properly. Thanks, Matt ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Another Nova-T 500 Dual DVB-T Oops
Hi, On my myth box I have a simple script that checks messages every 10sec and reboots if the usb disconnect line appears, I collect timestamped copies of the messages files. A distinct pattern i still to occur, but some channels are worse than others, but that might be time of day caused reception variations. Starting recording 3min ahead gives the box time to reboot and resume recording. /Henrik On 1/24/07, Matt Doran <[EMAIL PROTECTED]> wrote: Matt Doran wrote: Torgeir Veimo wrote: Can you include some output from /var/log/messages before the oops itself? In my case I see USB disconnects, then an oops from something unrelated just after that. You're right. There's a USB disconnect before this occurs. The messages are attached. The same occurs with the other set oops's I've seen too. Thanks, Matt This oops seems to be fairly regular. I got another one today. I see the USB disconnect again, but a slightly different stack. See attached. Some more info: - From the timing of this oops, I know that Myth was just about to start recording with this tuner. - My machine is a dual core AMD 3600+ AM2. Thanks, Matt usb 2-1: USB disconnect, address 2 mt2060 I2C write failed mt2060 I2C write failed dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully deinitialized and disconnected. BUG: unable to handle kernel paging request at virtual address 322e384c printing eip: f8ac3bc3 *pde = Oops: [#1] SMP Modules linked in: binfmt_misc rfcomm l2cap bluetooth powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative video sbs i2c_ec dock button battery container ac asus_acpi backlight mt352 saa7134_dvb video_buf_dvb tda1004x lirc_imon(F) lirc_dev sbp2 ieee1394 lp mt2060 ipv6 saa7134_alsa dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common snd_hda_intel snd_hda_codec saa7134 sg video_buf compat_ioctl32 ir_kbd_i2c ir_common videodev v4l2_common psmouse snd_pcm_oss snd_mixer_oss snd_mpu401 snd_mpu401_uart snd_rawmidi snd_seq_device v4l1_compat serio_raw snd_pcm snd_timer snd analog gameport ata_generic i2c_nforce2 floppy parport_pc parport pcspkr evdev shpchp pci_hotplug soundcore snd_page_alloc k8temp nvidia(P) agpgart i2c_core usbhid hid ext3 jbd mbcache uhci_hcd forcedeth ohci_hcd ehci_hcd usbcore ide_generic ide_cd cdrom sd_mod sata_nv libata scsi_mod generic amd74xx thermal process fan fbcon tileblit font bitblit softcursor vesafb capability commoncap CPU:1 EIP:0060:[pg0+946133955/1069057024]Tainted: PF VLI EFLAGS: 00010282 (2.6.20-4-generic #2) EIP is at dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] eax: 322e384c ebx: 322e384c ecx: aa243008 edx: 0800 esi: edi: f44bbfa0 ebp: 002b07a0 esp: f44bbf34 ds: 007b es: 007b ss: 0068 Process mythbackend (pid: 13886, ti=f44ba000 task=ca50da90 task.ti=f44ba000) Stack: f44bbf68 aa243008 0800 f44bbf68 c02e5862 0001 f44bbf68 f44bbfa0 aa243008 f44bbfa0 002b07a0 f8ac3d81 002b07a0 f44bbfa0 cf7f6440 aa243008 c017331c f44bbfa0 f8ac3d50 cf7f6440 fff7 a348826c Call Trace: [do_nanosleep+82/112] do_nanosleep+0x52/0x70 [pg0+946134401/1069057024] dvb_dvr_read+0x31/0x40 [dvb_core] [vfs_read+188/400] vfs_read+0xbc/0x190 [pg0+946134352/1069057024] dvb_dvr_read+0x0/0x40 [dvb_core] [sys_read+65/112] sys_read+0x41/0x70 [sysenter_past_esp+95/137] sysenter_past_esp+0x5f/0x89 === Code: c7 04 24 18 e3 ac f8 e8 8c 10 66 c7 eb 9c 8d 76 00 8d bc 27 00 00 00 00 55 57 56 31 f6 53 89 c3 83 ec 20 89 54 24 08 89 4c 24 04 <8b> 10 85 d2 0f 84 f7 00 00 00 8b 40 10 85 c0 0f 85 e3 00 00 00 EIP: [pg0+946133955/1069057024] dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] SS:ESP 0068:f44bbf34 <6>usb 2-1: new high speed USB device using ehci_hcd and address 3 usb 2-1: configuration #1 chosen from 1 choice 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). ___ 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
[linux-dvb] twinhab 7045A info
Hi, I have mailed Gunther Mayer pictures (including internals) and some other information on the stick, hopefullyhe will include it in his gallery.If I can be of any further help in providing support for this piece of hardware do not hesitate to contact me. /Henrik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] twinhan VP7045A new version ?
Hi, I just got this instead of a VP7045 Twinhan 7045A, Twinhan DTV Alpha Windows, Arrived with V1.0.4.0 drivers, no channels detected. Latest Twinhan driver detects channels. Linux, No channels detected. Only filter timeouts, I´m 100% certain that the arial is ok. After some investigation, it seems like later windows drivers add support for: Samsung PH10046 channel decoder Fix MT353 issue The following strings are in the XP driver 1.06.3 CheckDemodulator: Ph10046 CheckDemodulator: MT353 CheckDemodulator: MT352 This looks like there are several different version of the stick, any possibility to get it working on linux ? Anything one can do to help, I´m a lousy coder =( /Henrik Below is an Cut an Past of the windows Revision History. Revision History, Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.6.3 1. Fix issue: System crash when Win2000 install driver. 2. Modify HID driver for MCE application. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.6.2 1. Fix issue: Driver fail to init when update driver from device manager. 2. HID issue: Reduce HID driver installation process. Add registry key "RC_Report" in UDTT2HID.inf ;0:Twinhan Hotkey table only, 1:All RC table 3. Modify (Merge) HID INF fiiles. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.6.1 1. Fix issue: System crash when install driver. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.6.0 1. Add MCE remote control device support. To support MCE RC, please set the following registry keys in UDTT2BDA_HID.INF, ; //IR Stanard (NEC:0x01, RC-6:0x04) HKR,"DriverData","IR_Standard",0x00010001, 0x04,0x00,0x00,0x00 ; //IR system code checklist1 (NEC:0x00FF, MCE:0x0004) HKR,"DriverData","IRSYSCODECHECK1",0x00010001, 0x04,0x00,0x00,0x00 Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.9 1. Fix issue: THDTV can't get driver information when filter is in the running state. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.8 1. Fix MT353 issue: Update tuner control code with new Samsung latest sample code. 2. Fix MT353 issue: Modify signal quality presentation. 3. Modify device plug/unplug event only on the second driver loading time. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.7 1. Fix MT353 issue: Add more time to check locked status when frequnecy is shift +-125. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.6 1. Fix MT353 issue: Device #2 can't playback when THDTV3.0 first startup. 2. Fix MT353 issue: Can't lock non-integral frequency. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.5 1. Fix THDTV sometimes playback fail issue by modify PH10046 lock function. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.4 1. Add new THBDACmd32 for x64 2. Modify PH10046 checking lock status function. Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.3 1. Fix tuner power control bug that will cause fail to lock at first time. 2. Update HID driver to 1.0.1.2 (Ctrl+'n' for Play) Twinhan BDA driver for VP7045/VP7046 DVB-T v 1.0.5.2 1. Support Samsung PH10046 channel decoder ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
