[linux-dvb] Leadtek WinFast HDTV Cinema
Any word on if this card (Leadtek WinFast HDTV Cinema) is supported or not? http://www.leadtek.com/eng/tv_tuner/overview.asp?lineid=6pronameid=359 Thanks, John M. Drescher ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Leadtek WinFast HDTV Cinema
Good news, bad news situation. John Drescher wrote: Any word on if this card (Leadtek WinFast HDTV Cinema) is supported or not? http://www.leadtek.com/eng/tv_tuner/overview.asp?lineid=6pronameid=359 Bad news: Turning to the wiki, you will see that it is currently unsupported -- http://www.linuxtv.org/wiki/index.php/ATSC_PCI_Cards Good news: Glancing at the card, it is evident that: - it is using the Philips TUV1236D NIM - the shape of the decoder/bridge looks to be the saa7135 - 18 pin IC which I assume is for the remote. - there is a 8 pin eeprom on the back (and having a eeprom is always a good thing) Therefore, other then being low profile, the card looks to be very similar in block design as other supported cards -- specifically, the KWorld 11x cards. At this point (based upon my visual inspection), I would say that odds are pretty good that it would be fairly trivial to add support for this device. Here's where you can help if you have such a device already: - confirm the identity of the decoder/bridge IC ... I can't make it out from the pics on Leadtek's site or newegg, but like I said, I imagine its the saa7135 ... might be using NXP's logo now instead of the former Philips - identify the 18 pin IC to the right of the tuner module and above the decoder/bridge IC . this may very well be the same as the one used on the KWorld cards ... unfortunately, the IC on the KWorld cards is labelled only with an entirely non-identifiable KS007 no one has been able to ascertain the true identity of the IC, and potentially find a datasheet for it ... finding a datasheet for it would likely be very beneficial ... support for the KWorld cards' remote has never been finalized because, although patches exist, said support is not perfect and appears to conflict with some other devicesit certainly would be nice to bring some closure to that end if possible. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] offline descrambling of encrypted capture-files ?
Jean-Claude Repetto wrote: Luc Brosens wrote : I sent a question to technical support at KNCOne.de, and they confirm the bad news that Manu Abraham gave me : the CAM/CI on the TV-Station DVB-S can only be fed data from the tuner, not from a file. Pondering my options, I see two of them : (1) obtain a PCMCIA slot, and stuff my CAM in there. This may be the easiest route to take, as the CAM will still be there to do most of the work. I would be loosing a PCI slot however, and the capability of using two tuners (anyone know of a PCI-Express based adapter card ?) Won't work. (2) get a smartcard programmer, connected serially or through USB, and port poor man's cam. It looks like I wouldn't be able to use the CAM in this scenario, and it would need to be emulated (which, as I understand it, is the bulk of poor man's cam coding). are there more - easier - options ? I see another option : use a WinTV-CI from Hauppauge. The only problem is that the Linux driver does not exist yet, but may be for your application you don't need a driver, a user level application should be enough. Jean-Claude Jean-Claude, thanks for your reply. I didn't know of the existence of the WinTV-CI yet, but it looks like it could solve my problem. I'm going to try to find one and have a look at it sincerely, Luc ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Leadtek WinFast HDTV Cinema
On Dec 12, 2007 11:23 AM, CityK [EMAIL PROTECTED] wrote: Good news, bad news situation. John Drescher wrote: Any word on if this card (Leadtek WinFast HDTV Cinema) is supported or not? http://www.leadtek.com/eng/tv_tuner/overview.asp?lineid=6pronameid=359 Bad news: Turning to the wiki, you will see that it is currently unsupported -- Thanks. I did not see that page when I searched. I guess I used the wrong search terms. Good news: Glancing at the card, it is evident that: - it is using the Philips TUV1236D NIM - the shape of the decoder/bridge looks to be the saa7135 - 18 pin IC which I assume is for the remote. - there is a 8 pin eeprom on the back (and having a eeprom is always a good thing) Therefore, other then being low profile, the card looks to be very similar in block design as other supported cards -- specifically, the KWorld 11x cards. At this point (based upon my visual inspection), I would say that odds are pretty good that it would be fairly trivial to add support for this device. Here's where you can help if you have such a device already: No, I do not have the card. I was considering purchasing this card or an kworld 115 http://www.newegg.com/Product/Product.aspx?Item=N82E16815260005 - confirm the identity of the decoder/bridge IC ... I can't make it out from the pics on Leadtek's site or newegg, but like I said, I imagine its the saa7135 ... might be using NXP's logo now instead of the former Philips - identify the 18 pin IC to the right of the tuner module and above the decoder/bridge IC . this may very well be the same as the one used on the KWorld cards ... unfortunately, the IC on the KWorld cards is labelled only with an entirely non-identifiable KS007 no one has been able to ascertain the true identity of the IC, and potentially find a datasheet for it ... finding a datasheet for it would likely be very beneficial ... support for the KWorld cards' remote has never been finalized because, although patches exist, said support is not perfect and appears to conflict with some other devicesit certainly would be nice to bring some closure to that end if possible. Other than the problems with remote do the Kworld cards work well? I am mostly concerned with HD content over QAM256. John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Compiler error in tda18271.h
On Dec 12, 2007 3:11 PM, Andrea [EMAIL PROTECTED] wrote:
One of the last commits has broken this header file.
http://linuxtv.org/hg/v4l-dvb/rev/bbbc4fc359e9
diff -r d9e0f35279d4 linux/drivers/media/dvb/frontends/tda18271.h
--- a/linux/drivers/media/dvb/frontends/tda18271.h Wed Dec 12 00:40:19
2007 -0200
+++ b/linux/drivers/media/dvb/frontends/tda18271.h Wed Dec 12 20:09:20
2007 +
@@ -38,7 +38,7 @@ static inline struct dvb_frontend *tda18
static inline struct dvb_frontend *tda18271_attach(struct dvb_frontend *fe,
u8 addr,
struct i2c_adapter *i2c,
- enum tda18271_i2c_gate
gate);
+ enum tda18271_i2c_gate
gate)
{
printk(KERN_WARNING %s: driver disabled by Kconfig\n, __FUNCTION__);
return NULL;
Oops! Thanks for pointing this out. I'll fix this now :-)
Cheers,
Mike
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] NEW scan file - nz-waiatarua
We have the official DVB-T frequencies now for Waiatarua Auckland, plus test transmissions are in place. Can you please add the following scan file # Waiatarua, Auckland NZ # # Channel allocation details for NZ can be found at # http://www.rsm.govt.nz/cms/policy-and-planning/current-projects/broadcasting/digital-television-2007-frequency-plan # # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # Multiplex DA T 53800 8MHz 3/4 3/4 QAM64 8k 1/16 NONE # Multiplex DB T 57000 8MHz 3/4 3/4 QAM64 8k 1/16 NONE # Multiplex DC T 66600 8MHz 3/4 3/4 QAM64 8k 1/16 NONE Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] new driver for: Twinhan Hybrid DTV-DVB 3056 PCI [1822:0022] as card=118 in cardlist.saa7134
Strange I received this message... my ISP do not use 212. ips...
Hermann I resend the email.
___
Hi Hermann,
I have been a little busy... but I did the test as you said.
Before to procede with the test and install the patch I have cleared my
sys as follow:
1. Cleared all previous files under /src/usr/v4l-dvb following:
sudo make clean
sudo make distclean
2. Cleared aliases with sudo gedit /etc/modprobe.d/aliases to the origin as:
alias char-major-81 * videodev
alias char-major-81-* saa7134
3. Cleared the modprobe option with sudo gedit /etc/modprobe.d/options
to the origin as:
# Enable double-buffering so gstreamer et. al. work
options quickcam compatible=2
# Default hostap to managed mode
options hostap_pci iw_mode=2
options hostap_cs iw_mode=2
4. Cleared the previous saa7134 script under /etc/modprobe.d with sudo
rm saa*
5. Cleared all the dir V4l-dvb and v4l-app under /usr/src
6. Rebooted the sys...
and this is the virgin dmesg of my Twinhan:
[EMAIL PROTECTED]:~$ dmesg | grep saa
[ 37.551793] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 37.553908] saa7133[0]: found at :02:09.0, rev: 209, irq: 18,
latency: 32, mmio: 0xed00
[ 37.553917] saa7133[0]: subsystem: 1822:0022, board: UNKNOWN/GENERIC
[card=0,autodetected]
[ 37.553934] saa7133[0]: board init: gpio is 4
[ 37.751425] saa7133[0]: i2c eeprom 00: 22 18 22 00 54 20 1c 00 43 43
a9 1c 55 d2 b2 92
[ 37.751443] saa7133[0]: i2c eeprom 10: 00 01 fb 00 ff 20 ff ff ff ff
ff ff ff ff ff ff
[ 37.751458] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff
00 10 ff ff ff ff
[ 37.751472] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751486] saa7133[0]: i2c eeprom 40: ff 21 00 c2 84 10 03 32 15 50
ff ff ff ff ff ff
[ 37.751501] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751515] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751530] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751544] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751558] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751573] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751587] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751602] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751616] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751630] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.751645] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 37.753643] saa7133[0]: registered device video0 [v4l2]
[ 37.753880] saa7133[0]: registered device vbi0
[ 38.044982] saa7134 ALSA driver for DMA sound loaded
[ 38.045031] saa7133[0]/alsa: saa7133[0] at 0xed00 irq 18
registered as card -2
[EMAIL PROTECTED]:~$
Fine,
soon after I tested the Hermann-Sioux collaboration patch as follow:
1. Reinstalled virgin v4l-dvb and dvb-app with HG clone
2. copied the patch in /usr/src/v4l-dvb and renamed it as sioux.patch
3. launched the command: sudo patch --dry-run -p1 sioux.patch (see
below the rsults)
[EMAIL PROTECTED]:/usr/src/v4l-dvb$ sudo patch --dry-run -p1 sioux.patch
patching file linux/drivers/media/video/saa7134/saa7134-cards.c
Hunk #1 succeeded at 3601 (offset 1 line).
Hunk #2 succeeded at 4400 (offset 1 line).
Hunk #3 succeeded at 4820 (offset 2 lines).
patching file linux/drivers/media/video/saa7134/saa7134-dvb.c
Hunk #1 succeeded at 779 (offset 1 line).
Hunk #2 succeeded at 1059 (offset 1 line).
patching file linux/drivers/media/video/saa7134/saa7134.h
[EMAIL PROTECTED]:/usr/src/v4l-dvb$
Ok, I diden't see errors... than I made this command: sudo patch -p1
sioux.patch (see below the rsults)
[EMAIL PROTECTED]:/usr/src/v4l-dvb$ sudo patch -p1 sioux.patch
patching file linux/drivers/media/video/saa7134/saa7134-cards.c
Hunk #1 succeeded at 3601 (offset 1 line).
Hunk #2 succeeded at 4400 (offset 1 line).
Hunk #3 succeeded at 4820 (offset 2 lines).
patching file linux/drivers/media/video/saa7134/saa7134-dvb.c
Hunk #1 succeeded at 779 (offset 1 line).
Hunk #2 succeeded at 1059 (offset 1 line).
patching file linux/drivers/media/video/saa7134/saa7134.h
[EMAIL PROTECTED]:/usr/src/v4l-dvb$
I made some check in saa7134.h, saa7134-cards.c, saa7134-dvb.c with
gedit and searching for 3056... and this is what I sow:
saa7134.h
starting row 250
#define SAA7134_BOARD_TWINHAN_DTV_DVB_3056 118
_
saa7134-cards.c
starting row 3604
[SAA7134_BOARD_TWINHAN_DTV_DVB_3056] = {
.name = Twinhan Hybrid DTV-DVB 3056 PCI,
.audio_clock= 0x00187de7,
.tuner_type = TUNER_PHILIPS_TDA8290,
.radio_type = UNSET,
.tuner_addr=
[linux-dvb] Problem with Hauppauge Nova-TD
I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: dmesg reports: ... Dec 12 22:02:25 sirius kernel: dib0700: loaded with support for 2 different device-types Dec 12 22:02:25 sirius kernel: usbcore: registered new interface driver dvb_usb_dib0700 ... The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I'm so sad... I don't know if it's a software bug, and wrong firmware or something else. I have installed a linux kernel 2.6.22-14. What am I missing? Many thanks to everyone. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] m920x device: Genius TVGo DVB-T02Q
Hi, There are bad and good news. The bad ones are the device is not working properly yet. The -somewhat- good ones: I've got a few REAL bytes, from a real channel, through the stick. Still, I don't know what I'm doing right or wrong, so I'll share with you all what I've done to get here, to see if anyone can help me. After enabling all kinds of debugging parameters for the modules, disabling USB 2.0 (rmmod ehci_usb), and playing a lot with .stream parameters, I finally got this dmesg log (while running scan): Dec 12 21:25:47 zeus kernel: [ 1530.769183] 47 c0 04 20 ba 42 ac cd 8e 0b 6e c1 b9 91 37 ec 83 6f d0 9b Dec 12 21:25:47 zeus kernel: [ 1530.777530] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.777539] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:47 zeus kernel: [ 1530.786593] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.786601] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:47 zeus kernel: [ 1530.813085] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.813096] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:47 zeus kernel: [ 1530.837277] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.837286] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:47 zeus kernel: [ 1530.864707] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.864716] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:47 zeus kernel: [ 1530.911682] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.911693] 47 c0 04 20 ba 42 ac cd 8e 0b 6e c1 b9 91 37 ec 83 6f d0 9b Dec 12 21:25:47 zeus kernel: [ 1530.923155] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:47 zeus kernel: [ 1530.923165] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:48 zeus kernel: [ 1530.937747] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1530.937756] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:48 zeus kernel: [ 1530.946456] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1530.946465] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:48 zeus kernel: [ 1530.954475] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1530.954484] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:48 zeus kernel: [ 1530.968440] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1530.968451] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Dec 12 21:25:48 zeus kernel: [ 1530.974350] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1530.974358] 47 c0 04 20 ba 42 ac cd 8e 0b 6e c1 b9 91 37 ec 83 6f d0 9b Dec 12 21:25:48 zeus kernel: [ 1531.014879] 'isoc' urb completed. status: 0, length: 0/564, pack_num: 1, errors: 0 Dec 12 21:25:48 zeus kernel: [ 1531.014888] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Worth noting is the part that says length: 0/564 (BTW, during all my tests, I've always had a 0 here).But following that, some of the urb-transfer_buffer dumps seemed to have something significant. So I hacked usb-urb.c to dump more than 20 bytes, and after getting them from syslog, I passed them to hexdump: 47 c0 12 15 00 61 f0 0f 04 22 c1 30 b8 00 02 22 |Ga0...| 0010 d4 30 61 0d 4d 09 9f ff ff ff ff ff ff ff ff ff |.0a.M...| 0020 ff ff ff ff ff ff ff ff ff ff ff aa ff ff ff ff || 0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || 0040 ff ff ff ff ff ff 3f ff ff ff ff ff ff ff ff ff |..?.| 0050 ff ff ff ff ff ff ff ff ff ff ff ff b9 ff ff ff || 0060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || * 0080 ff ff ff ff ff ff ff ff ff ff f4 ff ff ff 08 ff || 0090 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || 00a0 ff ff ff ff fe ff ff ff ff ff ff ff ff ff ff ff || 00b0 ff ff ff ff ff ff ff ff ff 4e ff ff 47 c0 12 1a |.N..G...| 00c0 00 4f f0 0f 01 2c c9 00 01 00 0a 22 d4 04 4f 38 |.O...,...O8| 00d0 20 8e 1b ff 0f ff ff ff ff ff ff ff ff ff ff ff | ...| 00e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || 00f0 ff ff 76 ff ff 3f ff ff ff ff ff ff ff ff ff ff |..v..?..| 0100 ff ff ff ff ff ff
[linux-dvb] mt2060 I2C read/write failed, Hauppauge Nova-T 500 PCI
Hello! I have browsed a half year back in archives but didn't find any solution to this. I have setup a Hauppauge Nova-T 500 PCI under Kubunt 7.10using v4l-dvb from svn 2007-12-07. Every day I get I2C read/write failed errors and need to reload the module (dvb-usb-dib0700). In worst case the module won't reload because they are in use (but no program is running, mythbackend stopped, etc). Last time this (as in in use) happened was when I seeked (right arrow) when playing /dev/dvb/adapter0/dvr0 in mplayer after tzap -r. Some info: [EMAIL PROTECTED]:~$ dmesg | grep -i mt2060\|dvb [ 32.644274] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. [ 32.644305] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 32.644422] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.000139] DVB: registering frontend 0 (DiBcom 3000MC/P)... [ 33.045331] MT2060: successfully identified (IF1 = 1220) [ 33.603278] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 33.603459] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) [ 33.609153] DVB: registering frontend 1 (DiBcom 3000MC/P)... [ 33.613900] MT2060: successfully identified (IF1 = 1220) [ 34.169059] input: IR-receiver inside an USB DVB receiver as /class/input/input6 [ 34.169099] dvb-usb: schedule remote query interval to 150 msecs. [ 34.169103] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected. [ 34.169363] usbcore: registered new interface driver dvb_usb_dib0700 [ 258.929698] mt2060 I2C read failed [ 265.935059] mt2060 I2C read failed [ 1168.898547] mt2060 I2C read failed [ 1341.069358] mt2060 I2C read failed [ 1352.251714] mt2060 I2C read failed [ 1377.450039] mt2060 I2C read failed [ 2299.923845] mt2060 I2C write failed (len=6) [ 3074.045737] mt2060 I2C read failed [ 3242.035822] mt2060 I2C write failed (len=2) [ 5217.376468] mt2060 I2C read failed [ 5220.170838] mt2060 I2C read failed [ 5256.550148] mt2060 I2C write failed (len=6) etc... I am using this firmware: [EMAIL PROTECTED]:~$ md5sum /lib/firmware/dvb-usb-dib0700-1.10.fw 5878ebfcba2d8deb90b9120eb89b02da /lib/firmware/dvb-usb-dib0700-1.10.fw [EMAIL PROTECTED]:~$ ls -al /lib/firmware/dvb-usb-dib0700-1.10.fw -rw-r--r-- 1 root root 34306 2007-12-07 19:39 /lib/firmware/dvb- usb-dib0700-1.10.fw This version of linux: [EMAIL PROTECTED]:~$ cat /proc/version Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 The IR-receiver is not connected. I appreciate any help! /D ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Nova-TD Stick too sensitive?
I have a strange problem with my Nova-TD Stick (USB ID 2040:9580). A couple of months ago, I rebuilt my antenna setup and replaced all the cables, the amplifier and splitter by high-quality versions, and since then all the other cards (one Nova-T 500 and one Nova-T Stick) have gotten much improved signal quality. But for some reason, the Nova-TD Stick won't lock. MythTV claims 100% signal strength but doesn't achieve a lock. Since I really don't *need* the TD tuners (I got the TD before I got the simple T stick and before there was any hint of any Linux drivers for it, and three tuners really ought to be enough for anybody[tm]), I was content with leaving the TD stick unconnected. Yesterday, however, my system crashed again (due to i2c errors), and I went to work updating the box to the latest (F7) kernel, updated the hg tree and recompiled all the dvb drivers (haven't seen any i2c errors since then, btw -- Yay!). Just for the fun of it, I plugged in the TD stick to see if the situation had improved. It hadn't. I tested using the MythTV suggestions; use tzap -r to set it to streaming, and cat video.mpg. tzap claims it gets a lock, but I receive no data from the stick. The tzap output looks like this: # tzap -r -a 4 'TV6' using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0' tuning to 64200 Hz video pid 0x0437, audio pid 0x0436 status 0a | signal | snr | ber 001f | unc | 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 status 1a | signal | snr | ber 001f | unc | FE_HAS_LOCK Being a bit careless, I accidentally left the cat and tzap running while unplugging the device from the amplifier. Lo and behold, the signal level dropped, and it started feeding data into the mpg file. Only temporarily while the cable was aimed in the wrong direction, but yet -- the dvr0 device actually generated data! Once I completely disconnected the signal cable, the signal dropped down to 0 (pretty much expected): # tzap -r -a 4 'TV6' using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0' tuning to 64200 Hz video pid 0x0437, audio pid 0x0436 status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | status 00 | signal | snr | ber 001f | unc | Interesting, I thought. So I dug out the little mobile antenna that comes with the stick. I didn't expect to get anything working, but with that antenna I *do* get a lock even though the signal strength and quality for that is *much* worse than through the active antenna and high-quality amplifier. MythTV can tune, claiming ~20-40% signal quality (depending on which multiplex I tune to). The picture works just fine, and tzap is displaying something in between the two outputs above: # tzap -r -a 4 'TV6' using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0' tuning to 64200 Hz video pid 0x0437, audio pid 0x0436 status 07 | signal 6343 | snr | ber 001f | unc 0046 | status 1f | signal 634f | snr | ber 02b0 | unc | FE_HAS_LOCK status 1f | signal 634b | snr | ber 0220 | unc | FE_HAS_LOCK status 1f | signal 6358 | snr | ber 0290 | unc | FE_HAS_LOCK status 1f | signal 634e | snr | ber 0420 | unc | FE_HAS_LOCK Conclusion: The Nova-TD stick doesn't like when the signal is too strong. Is there anything in the driver code that makes this happen? I'm thinking perhaps noone ever thought of receiving a '' value for the signal strength and use that as a kind of error signal? Stranger things have happened... ;) AntennaSignal Data feed ----- - None 0% No data Passive38% Data Active 100% No data Active + Amp 100% No data Does anybody have any idea of how to get the TD stick operational with its antennas fed from a strong signal? I've tried everything I could think of... // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] new driver for: Twinhan Hybrid DTV-DVB 3056 PCI [1822:0022] as card=118 in cardlist.saa7134
Hi Sioux,
Am Mittwoch, den 12.12.2007, 22:16 +0100 schrieb sioux:
Hi Hermann,
I have been a little busy... but I did the test as you said.
Before to procede with the test and install the patch I have cleared
my sys as follow:
1. Cleared all previous files under /src/usr/v4l-dvb following:
sudo make clean
sudo make distclean
2. Cleared aliases with sudo gedit /etc/modprobe.d/aliases to the
origin as:
alias char-major-81 * videodev
alias char-major-81-* saa7134
3. Cleared the modprobe option with sudo gedit /etc/modprobe.d/options
to the origin as:
# Enable double-buffering so gstreamer et. al. work
options quickcam compatible=2
# Default hostap to managed mode
options hostap_pci iw_mode=2
options hostap_cs iw_mode=2
4. Cleared the previous saa7134 script under /etc/modprobe.d with sudo
rm saa*
5. Cleared all the dir V4l-dvb and v4l-app under /usr/src
6. Rebooted the sys...
and this is the virgin dmesg of my Twinhan:
[EMAIL PROTECTED]:~$ dmesg | grep saa
[ 37.551793] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 37.553908] saa7133[0]: found at :02:09.0, rev: 209, irq: 18,
latency: 32, mmio: 0xed00
[ 37.553917] saa7133[0]: subsystem: 1822:0022, board:
UNKNOWN/GENERIC [card=0,autodetected]
[ 37.553934] saa7133[0]: board init: gpio is 4
[ 37.751425] saa7133[0]: i2c eeprom 00: 22 18 22 00 54 20 1c 00 43
43 a9 1c 55 d2 b2 92
[ 37.751443] saa7133[0]: i2c eeprom 10: 00 01 fb 00 ff 20 ff ff ff
ff ff ff ff ff ff ff
[ 37.751458] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08
ff 00 10 ff ff ff ff
[ 37.751472] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751486] saa7133[0]: i2c eeprom 40: ff 21 00 c2 84 10 03 32 15
50 ff ff ff ff ff ff
[ 37.751501] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751515] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751530] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751544] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751558] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751573] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751587] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751602] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751616] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751630] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.751645] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff ff
[ 37.753643] saa7133[0]: registered device video0 [v4l2]
[ 37.753880] saa7133[0]: registered device vbi0
[ 38.044982] saa7134 ALSA driver for DMA sound loaded
[ 38.045031] saa7133[0]/alsa: saa7133[0] at 0xed00 irq 18
registered as card -2
[EMAIL PROTECTED]:~$
Fine,
soon after I tested the Hermann-Sioux collaboration patch as follow:
1. Reinstalled virgin v4l-dvb and dvb-app with HG clone
2. copied the patch in /usr/src/v4l-dvb and renamed it as sioux.patch
3. launched the command: sudo patch --dry-run -p1 sioux.patch (see
below the rsults)
[EMAIL PROTECTED]:/usr/src/v4l-dvb$ sudo patch --dry-run -p1
sioux.patch
patching file linux/drivers/media/video/saa7134/saa7134-cards.c
Hunk #1 succeeded at 3601 (offset 1 line).
Hunk #2 succeeded at 4400 (offset 1 line).
Hunk #3 succeeded at 4820 (offset 2 lines).
patching file linux/drivers/media/video/saa7134/saa7134-dvb.c
Hunk #1 succeeded at 779 (offset 1 line).
Hunk #2 succeeded at 1059 (offset 1 line).
patching file linux/drivers/media/video/saa7134/saa7134.h
[EMAIL PROTECTED]:/usr/src/v4l-dvb$
Ok, I diden't see errors... than I made this command: sudo patch -p1
sioux.patch (see below the rsults)
[EMAIL PROTECTED]:/usr/src/v4l-dvb$ sudo patch -p1 sioux.patch
patching file linux/drivers/media/video/saa7134/saa7134-cards.c
Hunk #1 succeeded at 3601 (offset 1 line).
Hunk #2 succeeded at 4400 (offset 1 line).
Hunk #3 succeeded at 4820 (offset 2 lines).
patching file linux/drivers/media/video/saa7134/saa7134-dvb.c
Hunk #1 succeeded at 779 (offset 1 line).
Hunk #2 succeeded at 1059 (offset 1 line).
patching file linux/drivers/media/video/saa7134/saa7134.h
[EMAIL PROTECTED]:/usr/src/v4l-dvb$
I made some check in saa7134.h, saa7134-cards.c, saa7134-dvb.c with
gedit and searching for 3056... and this is what I sow:
saa7134.h
starting row 250
#define SAA7134_BOARD_TWINHAN_DTV_DVB_3056 118
_
saa7134-cards.c
starting row 3604
[SAA7134_BOARD_TWINHAN_DTV_DVB_3056] = {
.name = Twinhan Hybrid DTV-DVB 3056 PCI,
.audio_clock= 0x00187de7,
.tuner_type = TUNER_PHILIPS_TDA8290,
Re: [linux-dvb] Problem with Hauppauge Nova-TD
I demand that Luca may or may not have written... I have this DVB-T USB device: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick It seem supported by difference sources: http://cateee.net/lkddb/web-lkddb/DVB_USB_DIB0700.html (PCI ID 2040:9580). I tried to find the correct firmware, I loaded/unloaded drivers for all the day (dib0700 is the correct one, right?), but nothing happens: [snip] The firmware name is dvb-usb-dib0700-01.fw and it's located to /lib/firmware/`uname -r`/... Putting it in /lib/firmware works well enough. I'm not sure I have the correct firmware (I tried to get it from Windows driver installation and from web, but I didn't found anything intersting). I've found firmware before, but I've never founded any... ;-) [snip] I have installed a linux kernel 2.6.22-14. What am I missing? Newer firmware and newer drivers. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys) 2B or not 2B - that is FF. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
