Re: [linux-dvb] MT2266 I2C write failed, usb disconnet, WinTV Nova-TD stick, remote
Il giorno mer, 12/03/2008 alle 21.40 +, Philip Pemberton ha scritto: Bernhard Albers wrote: [ 628.492000] hub 4-0:1.0: port 9 disabled by hub (EMI?), re-enabling... [ 628.492000] usb 4-9: USB disconnect, address 2 [ 628.50] MT2266 I2C write failed [ 628.50] MT2266 I2C write failed [ 650.208000] dvb-usb: error while stopping stream. Maybe it is a problem of the mainboard. It is an Asus m2a-vm hdmi (amd690g chipset and ati x1250 onboard graphics) with the latest Bios (1604). Interesting theory... I'm seeing the same thing on a Biostar TA690G mainboard, which uses the same I've already told it to Bernard but not yet in the list: Notice that this one seems to be a known issue (even to windows people) related to an incompatibility between 690g mainboard (more precisely sb600 southbridge) and nova td stick. It seems that it causes usb disconnect when the stick works in dual mode (always in linux) using both tuners at the same time. People reported the problem can be solved with a pci usb expansion or using the stick with another mainboard. There is also a note about it in the linuxtv wiki (NOVA-TD Stick page). It's interesting to note that both you and Bernard experienced the problem even with just one tuner. Some link: http://209.85.165.104/search?q=cache:3LygRMoeRqUJ:www.hauppauge.co.uk/board/showthread.php%3Ft%3D14152+nova+td+690ghl=itct=clnkcd=1 http://209.85.165.104/search?q=cache:KWnzteJ-zZkJ:www.hauppauge.co.uk/board/archive/index.php%3Ft-14247.html+nova+td+690ghl=itct=clnkcd=2 http://209.85.165.104/search?q=cache:-UJFsa42dsEJ:www.hauppauge.co.uk/board/archive/index.php%3Ft-14152.html+nova+td+sb600hl=itct=clnkcd=4 http://209.85.165.104/search?q=cache:tcwgQWV-jEUJ:www.hauppauge.co.uk/board/showthread.php%3Fp%3D63962+nova+td+sb600hl=itct=clnkcd=3 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem with new Terratec Cinergy C
Hello. I've been running a MythTV-box on top of Ubuntun Feisty for a year now without a hitch, using Technotrend C-1500 Budget card. Now I bought the new Terratec Cinergy C and installed the Mantis drivers I got from http://jusst.de/hg/mantis/summary. After this I got everything working fine in my Myth, but after a few days I there appeared to be a pattern where the whole machine just stops responding. This occurs every 12-24 hours and the source of it is quite hard to make out because obviously theres nothing in the logs. I have tried with another Cinergy-card but the result is the same, it can't be a hardware problem. I dunno if the problem is the driver of the cinergy or perhaps the installation of mantis somehow broke the TT-card.. Help would be much appreaciated. Here's dmeg from the box. [ 30.139218] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x4c00 [ 30.139267] i2c_adapter i2c-1: nForce2 SMBus adapter at 0x4c40 [ 30.28] saa7146: register extension 'budget_ci dvb'. [ 30.200624] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 [ 30.200636] ACPI: PCI Interrupt :04:09.0[A] - Link [APC2] - GSI 17 (lev el, low) - IRQ 17 [ 30.200665] saa7146: found saa7146 @ mem c207a000 (revision 1, irq 17 ) (0x13c2,0x1010). [ 30.200673] saa7146 (0): dma buffer size 192512 [ 30.200676] DVB: registering new adapter (TT-Budget-C-CI PCI) [ 30.207133] lirc_dev: IR Remote Control driver registered, at major 61 [ 30.220252] lirc_mceusb2: no version for lirc_get_pdata found: kernel taint ed. [ 30.220817] [ 30.220818] lirc_mceusb2: Philips eHome USB IR Transciever and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.25 $ [ 30.220822] lirc_mceusb2: Daniel Melander [EMAIL PROTECTED], Martin Blatter [EMAIL PROTECTED] [ 30.246198] adapter has MAC addr = 00:d0:5c:67:c3:51 [ 30.246541] input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/inpu t2 [ 30.395167] input: PC Speaker as /class/input/input3 [ 30.397327] DVB: registering frontend 0 (ST STV0297 DVB-C)... [ 30.398064] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 30.398075] ACPI: PCI Interrupt :04:08.0[A] - Link [APC1] - GSI 16 (lev el, low) - IRQ 16 [ 30.398102] irq: 16, latency: 32 [ 30.398103] memory: 0xfdaff000, mmio: 0xc207c000 [ 30.398106] found a VP-2040 PCI DVB-C device on (04:08.0), [ 30.398108] Mantis Rev 1 [153b:1178], irq: 16, latency: 32 [ 30.398112] memory: 0xfdaff000, mmio: 0xc207c000 [ 30.401025] MAC Address=[00:08:ca:1c:76:40] [ 30.401103] mantis_alloc_buffers (0): DMA=0x3520 cpu=0x81003520 s ize=65536 [ 30.40] mantis_alloc_buffers (0): RISC=0x37514000 cpu=0x810037514000 size=1000 [ 30.401115] DVB: registering new adapter (Mantis dvb adapter) [ 30.402068] ACPI: PCI Interrupt Link [APC7] enabled at IRQ 16 [ 30.402072] ACPI: PCI Interrupt :00:05.0[A] - Link [APC7] - GSI 16 (lev el, low) - IRQ 16 [ 30.402081] PCI: Setting latency timer of device :00:05.0 to 64 [ 30.414831] hdb: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(66 ) [ 30.414839] Uniform CD-ROM driver Revision: 3.20 [ 30.461051] usb 2-4: reset full speed USB device using ohci_hcd and address 2 [ 30.487089] parport: PnPBIOS parport detected. [ 30.487121] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [ 30.692119] lirc_dev: lirc_register_plugin: sample_rate: 0 [ 30.696827] lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb2:2 [ 30.696863] usbcore: registered new interface driver lirc_mceusb2 [ 30.952465] mantis_frontend_init (0): Probing for CU1216 (DVB-C) [ 30.954581] mantis_frontend_init (0): found Philips CU1216 DVB-C frontend (TD A10023) @ 0x0c [ 30.954584] mantis_frontend_init (0): Mantis DVB-C Philips CU1216 frontend at tach success [ 30.954590] DVB: registering frontend 1 (Philips TDA10023 DVB-C)... [ 30.954776] NVRM: loading NVIDIA Linux x86_64 Kernel Module 1.0-9631 Thu No v 9 17:35:27 PST 2006 [ 30.956655] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22 [ 30.956661] ACPI: PCI Interrupt :00:10.1[B] - Link [AAZA] - GSI 22 (lev el, low) - IRQ 22 [ 30.956683] PCI: Setting latency timer of device :00:10.1 to 64 [ 31.512368] lp0: using parport0 (interrupt-driven). [ 31.579263] /home/user/imon/imon_vfd.c: Driver for Soundgraph iMON VFD, v0. 1a1 [ 31.579267] /home/user/imon/imon_vfd.c: Venky Raju [EMAIL PROTECTED] [ 31.632597] /home/user/imon/imon_vfd.c: imon_probe: found IMON device [ 31.634115] /home/user/imon/imon_vfd.c: imon_probe: iMON device on usb2:3 initialized [ 31.634135] usbcore: registered new interface driver imon [ 38.091485] mantis_ack_wait (0): Slave RACK Fail ! [ 38.161365] it87: Found IT8716F chip at 0x290, revision 1 [ 38.161376] it87: in3 is VCC (+5V) [ 38.161377] it87: in7 is VCCH (+5V Stand-By) [ 38.313108] Adding 1951888k swap on /dev/disk/by-uuid/3aa3c26c-72d8-48e1-9811 -0381f0a69f84. Priority:-1 extents:1
Re: [linux-dvb] Elgato EyeTV Hybrid
On 3/13/08, Craig Marshall [EMAIL PROTECTED] wrote: Hi, Does anyone know if it's possible to use the Elgato EyeTV Hybrid (a mac device) with Linux? The device should be supported as far as I know, it's an Empiatech based device. Go to mcentral.de for further information. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Elgato EyeTV Hybrid
Hi, Does anyone know if it's possible to use the Elgato EyeTV Hybrid (a mac device) with Linux? Thanks, Craig ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Implementing support for multi-channel
-Original Message- From: Tero Pelander [mailto:[EMAIL PROTECTED] Sent: 13 March 2008 07:29 To: Ben Backx Subject: Re: [linux-dvb] Implementing support for multi-channel On Wed, Mar 12, 2008 at 12:19:58PM -, Stephen Rowles wrote: I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? One such program that is easy to understand due to modularity is dvbyell. It has separate code for tuner part and separate code for splitting MPTS (multiple program transport stream) into many single program transport streams. http://www.dvbyell.org/ Thank you everybody for the answers so far, I do have enough software-based solutions to start testing. However, there's still the question: can filtering be done in the driver? Are there any drivers that support this or which dvb-api-functions need to be implemented? Regards, Ben ___ 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
On Tue, Mar 11, 2008 at 04:55:24PM +0100, Patrik Hansson wrote: Have you applied any patches to the v4l-dvb source before compiling ? No patches applied to v4ldvb or kernel source. On 3/11/08, Nicolas Will [EMAIL PROTECTED] wrote: What changed between 2.6.22 and 2.6.24? huh... funny, heh? So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have a planned upgrade to it in about a month's time. In fact I saw failures against linux-2.6.23.12 I've diffed the two trees and am browsing (at leisure) the changes to see if anything leaps out. Just enabled mythtv multirec too to see if I can put a bit more stress on the system, still no failures. When I have time I'll flip back to 2.6.11.19 and see how easy/quickly I can get it to fail again. Cheers, Ivor. ___ 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
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] Any chance of help with v4l-dvb-experimental / Avermedia A16D please?
Hi Richard, On Tue, 12 Feb 2008 18:15:09 + Richard (MQ) [EMAIL PROTECTED] wrote: Sorry for a late answer. Too busy from my side :( please forward the errors that it might produce. You may forward the full dmesg errors to me in priv directly. I prefer if you don't generate a tarball, since makes easier for me to comment, the results, if needed. Feb 12 18:03:26 DevBox2400 klogd: saa7133[0]: i2c scan: found device @ 0x1e [???] Feb 12 18:03:26 DevBox2400 klogd: saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] The issue here is that tuner-xc3028 weren't detected. It should have found a device at 0xc2. This could happen on two cases: 1) Some saa713x GPIO is needed before we can see xc3028. The better would be to take a look on what windows driver is doing with GPIO's. This link helps you to understand what should be done on windows: http://www.linuxtv.org/v4lwiki/index.php/GPIO_pins 2) You need to open an i2c gate on your demod chip. In this case, some commands need to be sent to your demod for it to open the i2c gate. I suspect that, on your case, it is (1). Please try the enclosed patch. --- Enable GPIO's for AV A16D From: Mauro Carvalho Chehab [EMAIL PROTECTED] Signed-off-by: Mauro Carvalho Chehab [EMAIL PROTECTED] diff -r 3580392c30da linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Mar 13 10:57:22 2008 -0300 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Mar 13 11:43:45 2008 -0300 @@ -5499,6 +5499,7 @@ int saa7134_board_init1(struct saa7134_d case SAA7134_BOARD_AVERMEDIA_CARDBUS_506: case SAA7134_BOARD_AVERMEDIA_M115: case SAA7134_BOARD_BEHOLD_COLUMBUS_TVFM: + case SAA7134_BOARD_AVERMEDIA_A16D: /* power-up tuner chip */ saa_andorl(SAA7134_GPIO_GPMODE0 2, 0x, 0x); saa_andorl(SAA7134_GPIO_GPSTATUS0 2, 0x, 0x); Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with lspci and PCIe slots - HVR-1800 not seen
Timothy D. Lenz wrote: I just put my new HVR-1800 in and restarted and found lspci dosen't see it. I have not redone drivers yet. They are still built only for the Nexus. I have searched all the logs for ref to the chip used, but nothing. Google came back with a lot of people having problems with lspci and PCIe cards. Some mis-named, some not showing at all. Going ahead with trying to build multiproto drivers and se what happens lspci always shows the HVR1800 and other PCIe cards for me. - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re : TT S2-3200 vlc streaming
manu wrote: On 03/11/2008 02:27:31 AM, Vladimir Prudnikov wrote: I'm getting late buffers with vlc on some transponders (DVB-S, same parameters, good signal guaranteed) while everything is fine with others. Using multiproto and TT S2-3200. Anyone having same problems? Can you give the frequencies of the good and bad transponders, mine are as follows: I can receive from 4 transponders (DVB-S): 11093, 11555, 11635, 11675 MHz. any channel on 11093: fast lock, perfect picture. any channel on 11555: lock a bit slower and corrupted stream (lots of blocky artifacts, myhttv complains about corrupted stream) any channel on 11635,11675: no lock. Please provide: * parameters that you use for tuning each of these transponders * logs from the stb0899 and stb6100 modules both loaded with verbose=5, for each of these transponders Hope it might shed some light into your problems. Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Implementing support for multi-channel
-Original Message- Thank you everybody for the answers so far, I do have enough software-based solutions to start testing. However, there's still the question: can filtering be done in the driver? Have you read my last post? http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024456.html When I talk about filter, demux, dvr, this is all in the kernel driver for the dvb. You can find here an example of how to open the demux to get 1 PID. You can run it multiple times and get as many streams as you want http://www.audetto.pwp.blueyonder.co.uk/dvb.cpp Are there any drivers that support this or which dvb-api-functions need to be implemented? If you want to extend the driver for the dvb, I'd like to be able to set a filter in the demux for more that 1 pid at a time. Good luck. Andrea ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Working HVR-4000 (as of 2008-03-13) patch for multiproto ?
Hello, I didn't follow the change in multiproto and I don't understand them so this patch might be completely wrong... it allow me to compil support for my HVR-4000 and it seems to work. But take it as not really tested... It would be great if someone more knowledged could review it, and maybe finally integrate it in multiproto, which will make lots of people gaining lots ot time ;-) -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre HVR-4000-2008-03-13.diff.bz2 Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 1:20 PM, Jarryd Beck [EMAIL PROTECTED] wrote: On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) -Mike Sorry I'm unsure where to set debug. Jarryd. I added initial support for this tda-tuner to the driver. Jarryd, can you test? http://linuxtv.org/hg/~anttip/af9015_new/ There is debug switch in af9013 module that may be helpful if it does not work. You can enable it as described or if it is too hard to play with modprobe just edit af9013.c file in frontend directory and set debug=1 by hard coding. If it does not work you can also try set GPIO3 setting (af9015) to 0xb instead 0x3 used currently. Also try to change rf-spectral inversion to see if it helps. Firmware should be ok and all other settings as well as I can see from usb-sniffs. With little lucky it should start working. regards Antti -- http://palosaari.fi/ Thanks, but now for some reason all I get is this: usb 2-10: new high speed USB device using ehci_hcd and address 6 usb 2-10: configuration #1 chosen from 1 choice input: Leadtek WinFast DTV Dongle Gold as /class/input/input8 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: usbcore: registered new interface driver dvb_usb_af9015 Jarryd. I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Any chance of help with v4l-dvb-experimental / Avermedia A16D please?
Hi Mauro, Improved, but still no tuner-xc3028, no dvb. Relevant part of my dmesg: [ 14.612000] /build/buildd/linux-source-2.6.22-2.6.22/drivers/input/joystick/xpad.c: driver for Xbox controllers v0.1.6 [ 14.78] Linux video capture interface: v2.00 [ 14.832000] saa7130/34: v4l2 driver version 0.2.14 loaded [ 14.832000] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 [ 14.832000] ACPI: PCI Interrupt :04:09.0[A] - Link [APC2] - GSI 17 (level, low) - IRQ 21 [ 14.832000] saa7133[0]: found at :04:09.0, rev: 209, irq: 21, latency: 32, mmio: 0xfdbff000 [ 14.832000] saa7133[0]: subsystem: 1461:f936, board: AVerMedia Hybrid TV/Radio (A16D) [card=137,autodetected] [ 14.832000] saa7133[0]: board init: gpio is f000 [ 14.992000] saa7133[0]: i2c eeprom 00: 61 14 36 f9 00 00 00 00 00 00 00 00 00 00 00 00 [ 14.992000] saa7133[0]: i2c eeprom 10: ff ff ff ff ff 20 ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 01 00 08 ff 00 0e ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 40: ff 65 00 ff c2 1e ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 14.992000] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 15.12] tuner' 2-0061: chip found @ 0xc2 (saa7133[0]) [ 15.12] tuner' 2-0061: tuner type not set [ 15.12] tuner' 2-0061: tuner type not set [ 15.12] saa7133[0]: registered device video0 [v4l2] [ 15.12] saa7133[0]: registered device vbi0 [ 15.12] saa7133[0]: registered device radio0 [ 15.12] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22 [ 15.12] ACPI: PCI Interrupt :00:10.1[B] - Link [AAZA] - GSI 22 (level, low) - IRQ 17 [ 15.12] PCI: Setting latency timer of device :00:10.1 to 64 [ 15.136000] saa7134 ALSA driver for DMA sound loaded [ 15.136000] saa7133[0]/alsa: saa7133[0] at 0xfdbff000 irq 21 registered as card -2 To match with other firmware, I did chmod 644 xc3028-v27.fw 16 -rw-r--r-- 1 root root 16382 2007-10-13 13:43 v4l-cx25840.fw 8 -rw-r--r-- 1 root root 8192 2007-10-13 13:43 v4l-pvrusb2-24xxx-01.fw 8 -rw-r--r-- 1 root root 8192 2007-10-13 13:43 v4l-pvrusb2-29xxx-01.fw 72 -rw-r--r-- 1 root root 66220 2008-03-14 09:27 xc3028-v27.fw 4 drwxr-xr-x 2 root root 4096 2008-03-14 17:48 zd1211 [EMAIL PROTECTED]:/lib/firmware/2.6.22-14-generic$ Regards, Tim On Thu, 2008-03-13 at 11:46 -0300, Mauro Carvalho Chehab wrote: Hi Richard, On Tue, 12 Feb 2008 18:15:09 + Richard (MQ) [EMAIL PROTECTED] wrote: Sorry for a late answer. Too busy from my side :( please forward the errors that it might produce. You may forward the full dmesg errors to me in priv directly. I prefer if you don't generate a tarball, since makes easier for me to comment, the results, if needed. Feb 12 18:03:26 DevBox2400 klogd: saa7133[0]: i2c scan: found device @ 0x1e [???] Feb 12 18:03:26 DevBox2400 klogd: saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] The issue here is that tuner-xc3028 weren't detected. It should have found a device at 0xc2. This could happen on two cases: 1) Some saa713x GPIO is needed before we can see xc3028. The better would be to take a look on what windows driver is doing with GPIO's. This link helps you to understand what should be done on windows: http://www.linuxtv.org/v4lwiki/index.php/GPIO_pins 2) You need to open an i2c gate on your demod chip. In this case, some commands need to be sent to your demod for it to open the i2c gate. I suspect that, on your case, it is (1). Please try the enclosed patch. --- Enable GPIO's for AV A16D From: Mauro Carvalho Chehab [EMAIL PROTECTED] Signed-off-by: Mauro Carvalho Chehab [EMAIL PROTECTED] diff -r 3580392c30da linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Mar 13 10:57:22 2008 -0300 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Mar 13 11:43:45 2008
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this: Mar 14 13:42:17 localhost kernel: af9015: af9015_rw_udev: receiving failed: -22 Mar 14 13:42:17 localhost kernel: dvb-usb: error while querying for an remote control event. I also tried changing the rf_spec_inv and gpio3 but that didn't seem to do anything. It seems like it's the tuner, from dmesg the rest seems to be working fine. Here is dmesg with debug enabled on af9013 too: usb 2-10: new high speed USB device using ehci_hcd and address 7 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this: Mar 14 13:42:17 localhost kernel: af9015: af9015_rw_udev: receiving failed: -22 Mar 14 13:42:17 localhost kernel: dvb-usb: error while querying for an remote control event. I also tried changing the rf_spec_inv and gpio3 but that didn't seem to do anything. It seems like it's the tuner, from dmesg the rest seems to be working fine. Here is dmesg with debug enabled on af9013 too: usb 2-10: new high speed USB device using ehci_hcd and address 7 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state:
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this: Mar 14 13:42:17 localhost kernel: af9015: af9015_rw_udev: receiving failed: -22 Mar 14 13:42:17 localhost kernel: dvb-usb: error while querying for an remote control event. I also tried changing the rf_spec_inv and gpio3 but that didn't seem to do anything. It seems
Re: [linux-dvb] NXP 18211HDC1 tuner
On Fri, Mar 14, 2008 at 2:22 PM, Jarryd Beck [EMAIL PROTECTED] wrote: On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Fri, Mar 14, 2008 at 11:13 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: I found the problem, the driver I had set .no_reconnect = 1 in af9015_properties, the one in af9015_new didn't. So after I changed that I tried again, it still didn't work. I enabled debugging and tried to tune to a channel and this is what I got in dmesg. I know this no_reconnect problem. But haven't found proper correction yet. Looks like sometimes with some hw / sw configuration it reconnects USB-bus after firmware download and sometimes not. When there is no_reconnect set it is possible that driver loads twice (two adapters) and it causes race condition when two drivers are accessing same hw same time and it hangs (remote polling causes hangs very soon after plug). You can help and test if it is OK set no_reconnect=0 and remove #if 0 -killed code by changing it to #if 1 in line where is comment firmware is running, reconnect device in the usb bus. This forces AF9015 chipset reconnect USB. usb 2-10: new high speed USB device using ehci_hcd and address 27 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input39 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input40 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_tune: freq = 21950, ifc = 380, bw = 700, std = 0x1d tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 tda18271_init_regs: initializing registers for device @ 5-00c0 tda18271_set_standby_mode: sm = 1, sm_lt = 0, sm_xt = 0 There is no debug logs from af9013 demodulator module. You can enable logs by modprobe af9013 debug=1. Remember rmmod modules first from memory rmmod dvb_usb_af9015 af9013 mt2060 dvb_usb dvb_core af9013 debug should log rather much useful data when tuning to channel. Did you try change GPIO3 as mentioned earlier? regards Antti -- http://palosaari.fi/ I tried what you said, it works with no_reconnect = 1 and #if 0, and it also works with no_reconnect = 0 and #if 1, but no_reconnect = 0 and #if 0 doesn't work. It has a fit if I use no_reconnect = 1 and #if 1. It gives me a lot of this:
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: and when I try to tune it I get this: af9013_init af9013_reset af9013_power_ctrl: onoff:1 af9013_set_adc_ctrl: adc_clock:28000 af913_div: a:2800 b:100 x:19 af913_div: a:0 b:100 x:19 r:14680064 r:e0 af9013_init: load ofsm settings af9013_init: load tuner specific settings af9013_init: setting ts mode af9013_lock_led: onoff:1 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 tda18271_init_regs: initializing registers for device @ 5-00c0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 the last two lines are repeated about another 30 times and it just sits there doing nothing. Also for some reason it makes my keyboard really slow to respond just while it's tuning. Sounds weird. tda18271 driver does own i2c transaction for every register write / read. Thats why it opens and closes i2c-gate of the af9013 (about i2c-gate: tuner is wired to demodulator and demodulator keeps gate that should be open and close every time when access to tuner is needed). I don't know if this really takes so much cpu-time from af9013/5 that it slows down or so much disk IO from your computer to write all logs to disk. Anyhown, i2c-bus of the af9015/3 can be increased from driver. It is 400kHz currently if I remember correctly. There is still missing all best information from your logs. I put here successful case with logs where AF9015 + MT2060 (tuner) is tuned to channel. I need same kind information to see if demodulator is programmed correctly. There could be even bug because I have only 8MHz BW and you have 7MHz, maybe there is no test for 7MHz at all. Mar 14 06:11:27 crope-laptop kernel: [15962.068300] usb 2-1: new high speed USB device using ehci_hcd and address 19 Mar 14 06:11:27 crope-laptop kernel: [15962.120712] usb 2-1: configuration #1 chosen from 1 choice Mar 14 06:11:27 crope-laptop kernel: [15962.126234] input: Afatech DVB-T 2 as /devices/pci:00/:00:02.1/usb2/2-1/2-1:1.1/input/input26 Mar 14 06:11:27 crope-laptop kernel: [15962.143945] input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-:00:02.1-1 Mar 14 06:11:27 crope-laptop kernel: [15962.185417] af9015_usb_probe: Mar 14 06:11:27 crope-laptop kernel: [15962.186118] af9015_identify_state: reply:01 Mar 14 06:11:27 crope-laptop kernel: [15962.186123] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware Mar 14 06:11:27 crope-laptop kernel: [15962.191522] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' Mar 14 06:11:27 crope-laptop kernel: [15962.191526] af9015_download_firmware: Mar 14 06:11:27 crope-laptop kernel: [15962.228754] usbcore: registered new interface driver dvb_usb_af9015 Mar 14 06:11:27 crope-laptop kernel: [15962.228878] usb 2-1: USB disconnect, address 19 Mar 14 06:11:27 crope-laptop kernel: [15962.231248] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Mar 14 06:11:27 crope-laptop kernel: [15962.334815] usb 2-1: new high speed USB device using ehci_hcd and address 20 Mar 14 06:11:28 crope-laptop kernel: [15962.471565] usb 2-1: configuration #1 chosen from 1 choice Mar 14 06:11:28 crope-laptop kernel: [15962.483220] af9015_usb_probe: Mar 14 06:11:28 crope-laptop kernel: [15962.484851] af9015_identify_state: reply:02 Mar 14 06:11:28 crope-laptop kernel: [15962.484857] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. Mar 14 06:11:28 crope-laptop kernel: [15962.484910] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Mar 14 06:11:28 crope-laptop kernel: [15962.485346] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) Mar 14 06:11:28 crope-laptop kernel: [15962.485557] af9015_eeprom_dump: Mar 14 06:11:28 crope-laptop kernel: [15962.538409] 00: 2c 75 9b 0b 00 00 00 00 a4 15 16 90 00 02 01 02 Mar 14 06:11:28 crope-laptop kernel: [15962.765844] 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 31 30 30 Mar 14 06:11:28 crope-laptop kernel: [15962.629342] 20: 34 30 36 30 30 30 30 31 ff ff ff ff ff ff ff ff Mar 14 06:11:28 crope-laptop kernel: [15962.672188] 30: 00 00 3a 01 00 08 02 00 1d 8d c4 04 82 ff ff ff Mar 14 06:11:28 crope-laptop kernel: [15962.696172] 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff Mar 14 06:11:28 crope-laptop kernel: [15962.729650] 50: ff ff ff ff ff 24 00 00 04 03 09 04 10 03 41 00 Mar 14 06:11:28 crope-laptop kernel: [15962.760627] 60: 66 00 61 00 74 00 65 00 63 00 68 00 10 03 44 00 Mar 14 06:11:28 crope-laptop kernel: [15962.791231] 70: 56 00 42 00 2d 00 54 00 20 00 32 00 20 03 30 00 Mar 14 06:11:28 crope-laptop kernel: [15962.823208] 80: 31 00 30 00 31 00 31 00 30 00 30 00 34 00 30 00 Mar 14 06:11:28 crope-laptop kernel: [15962.855187] 90: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff Mar 14 06:11:28 crope-laptop kernel:
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Fri, Mar 14, 2008 at 2:22 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Here is dmesg with debug enabled on af9013 too: usb 2-10: new high speed USB device using ehci_hcd and address 7 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 2 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_tda18271_tuner_attach: tda18271 5-00c0: creating new instance af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 TDA18271HD/C1 detected @ 5-00c0 tda18271_init_regs: initializing registers for device @ 5-00c0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 [...] af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 input: IR-receiver inside an USB DVB receiver as /class/input/input9 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input10 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 and when I try to tune it I get this: af9013_init af9013_reset af9013_power_ctrl: onoff:1 af9013_set_adc_ctrl: adc_clock:28000 af913_div: a:2800 b:100 x:19 af913_div: a:0 b:100 x:19 r:14680064 r:e0 af9013_init: load ofsm settings af9013_init: load tuner specific settings af9013_init: setting ts mode af9013_lock_led: onoff:1 tda18271_set_standby_mode: sm = 0, sm_lt = 0, sm_xt = 0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 tda18271_init_regs: initializing registers for device @ 5-00c0 af9013_i2c_gate_ctrl: enable:1 af9013_i2c_gate_ctrl: enable:0 the last two lines are repeated about another 30 times and it just sits there doing nothing. Also for some reason it makes my keyboard really slow to respond just while it's tuning. Jarryd. The tda18271c1 driver does many i2c transactions during a tune request. This involves image rejection filter calibration, if it hasnt already been done at least once, and rf tracking filter calibration on every tune. This all happens very quickly on the hardware that I've tested ( a cx23887-based pcie card and a cypress fx2-based usb device). I've also heard good reports on saa713x-based pci cards. Is the i2c slow in the af9013 driver? The tuner driver is programmed to use 7mhz dvbt with IF centered at 3.8 mhz -- is the demod set to the same? -Mike How do I find out about the demod? Is the speed of af9013 a question for me because I have no idea. Somewhere along the way demod_address in a struct is set to AF9015_I2C_DEMOD which is 0x38. Is that what you wanted? I was hoping that Antti might know the answers those questions. Anyhow, there is something else related to the tuner that we can try. In the snoop log, I see that no i2c transactions are longer than 16 bytes. The linux driver writes 39 registers at once during its
Re: [linux-dvb] NXP 18211HDC1 tuner
Michael Krufky wrote: This all happens very quickly on the hardware that I've tested ( a cx23887-based pcie card and a cypress fx2-based usb device). I've also heard good reports on saa713x-based pci cards. Is the i2c slow in the af9013 driver? I will check this later, probably it is possible to speed up. I need to take look of the usb-sniffs. The tuner driver is programmed to use 7mhz dvbt with IF centered at 3.8 mhz -- is the demod set to the same? hmm, good point. I don't know. There is parameter tuner IF that is set to 36125 kHz. Any idea or help? regards Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: Somewhere along the way demod_address in a struct is set to AF9015_I2C_DEMOD which is 0x38. Is that what you wanted? No, it is demodulator i2c-address. Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
looks like possible bug found! Jarryd Beck wrote: On Fri, Mar 14, 2008 at 2:19 PM, Michael Krufky [EMAIL PROTECTED] wrote: This all happens very quickly on the hardware that I've tested ( a cx23887-based pcie card and a cypress fx2-based usb device). I've also heard good reports on saa713x-based pci cards. Is the i2c slow in the af9013 driver? Just checked from code and it looks like it is 60 kHz currently. It is not clear for me how kHz correlates to value written to register so let is be this time. The tuner driver is programmed to use 7mhz dvbt with IF centered at 3.8 mhz -- is the demod set to the same? hmm, I think there is bug now. I compared eeprom dumps and found that my MT2060 has IF1 = 36125 and eeprom of this device says it should be IF1 = 4300. Is 4.3 Mhz close enough (we are speaking same thing?)? Jerryd, change .tuner_if = 36125 to 4300 . It can be found from af9015 module. How do I find out about the demod? Is the speed of af9013 a question for me because I have no idea. One thing to test speed is also commenting out program tuner part from af9013 so it does not ask tuner to go frequency. It did not tune then. But, I still needs debug logs of the af9013. Then I can compare much more easier usb-sniff and debug values got from driver. Antti -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
