Re: [linux-dvb] Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
Hi Jason, > Hi Hermann, > > > Hopefully it does help in that other case. that one really counts now. > I have it working now. I had to add a delay of 120 seconds in the > mythtv backend script to allow the driver enough time to scan both > cards and install the firmware properly. Previously the mythtv > backend at startup was trying to talk to the cards before the firmware > was loaded and so they'd fail to work. > > It's not a big hassle but it would seem in spite of a test in the > startup script to ensure udev configuration was complete before > mythbackend was loaded it would seem that udev device configuration Sorry, no time yet to dig into it further, but I seem to hear some faint noise. How sure you are to have original eeprom content on your card ? Some bill, original packing material or similar? On some first impression, l doubt we deal with something it claims to be. Cheers, Hermann > was completing before the firmware was loaded. > > Is there the possibility of adding some feature into the driver to > make sure it fails on opening if the firmware isn't properly loaded? > > Another general question, does V4L sequentially initialise hardware or > does it run in parallel? It would seem to be a good time saver to > have all DVB cards initialised in parallel to speed up booting of a > system. > > I have reverted back to Mythbuntu 10.04 and kernel 2.6.32 and the > cards work fine now (though with the latest v29 of the firmware for > these cards). > > Cheers > Jason > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
Hi Hermann, > Hopefully it does help in that other case. I have it working now. I had to add a delay of 120 seconds in the mythtv backend script to allow the driver enough time to scan both cards and install the firmware properly. Previously the mythtv backend at startup was trying to talk to the cards before the firmware was loaded and so they'd fail to work. It's not a big hassle but it would seem in spite of a test in the startup script to ensure udev configuration was complete before mythbackend was loaded it would seem that udev device configuration was completing before the firmware was loaded. Is there the possibility of adding some feature into the driver to make sure it fails on opening if the firmware isn't properly loaded? Another general question, does V4L sequentially initialise hardware or does it run in parallel? It would seem to be a good time saver to have all DVB cards initialised in parallel to speed up booting of a system. I have reverted back to Mythbuntu 10.04 and kernel 2.6.32 and the cards work fine now (though with the latest v29 of the firmware for these cards). Cheers Jason -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
Hi Jason, Am Samstag, den 12.03.2011, 10:43 +1100 schrieb Jason Hecker: > I just bought a pair of what are a version of the My Cinema 7131 > Hybrid cards. > > The kernel reports it as saa7134: Asus Tiger revision 1.0, subsys > 1043:4857 > > I did inititially try Mythbuntu 10.04 but the firmware upload seemed > to fail fairly consistently. Restarting with v10.10 the firmware > loads but I can't seem to scan the channels with Mythbackend - it has > a 0% signal and 100% signal to noise. I am using MythTV 0.24 with > Avenard's latest patches. > > This version of the card has written on the silkscreen Tiger rev 3.02, > a sticker that says Tiger_8M AA.F7.C0.01 (which would appear to be the > latest firmware for this card on Asus's support site) but there is > only one RF connector on CON1. CON2 is not fitted nor is the IR > receiver. Now I saw mentioned on a list that to get DVB working on > this card in Linux you need to connect the TV antenna to the FM port, > which I suspect is the one not fitted. The latest Windows drivers for > this card is circa 2009. > > Two questions: > - Is there some sort of SAA7134 module argument I need to use to get > the card working on the TV RF input? > - Why does the kernel show the firmware is being reloaded every time > MythTV seems to want to talk to the card? This slows down access as > it seems to take about 30 seconds for the firmware to install each > time. > > I am happy to provide whatever debug dumps or more info if need be. > this hits me only by accident, reading through backlash, but I added that Asus Tiger Revision 1.0 with subsys 1043:4857, with a huge delay only. (approximately 1 1/2 years) The development and testing for the new tuner types was done only much later on freely available stuff, a so called Asus Dual _non_ OEM variant. Not to tell what we did all see thereafter, but that all was at least, with only one exception, valid using the PCI subsystem as unique identifier. Luckily, as far as I can see, we have only a fictional radio device on your "new" variant left over. This can still be very annoying, but won't do any harm, except wasting a users time, bad enough, but at least not any radiation from that sort of radio flaw. Since the PCI subsystem is identical with mine, still around somewhere, with radio support, either take that dead radio device for now or a last chance is to discover, if any eeprom differences are there to eventually filter that minor, but unpleasant shortcoming for those trying in vain on the radio. Cheers, Hermann To restore the power on a failing power plant in urgent need of it seems to be a good idea, after six or seven days ... All my excuses for the failing radio device on that not yet seen OEM stuff, but I can ensure, to piss on it doesn't help any further. Hopefully it does help in that other case. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
Jason Hecker wrote: >I seem to have fixed the problem for now. It's the hoary old problem >of Mythtv's backend coming up and accessing the cards before the >firmware has loaded onto the cards. Adding in a startup delay to >myth-backend's init script has solved the problem, for now. The >firmware seems to load now on Mythbuntu 10.04 without a problem. > >Is there some way to put a lock in the driver or even speed up the >process of loading the firmware with some command line arguments when >the saa7134 driver is loaded? >-- >To unsubscribe from this list: send the line "unsubscribe linux-media" >in >the body of a message to majord...@vger.kernel.org >More majordomo info at http://vger.kernel.org/majordomo-info.html The ivtv and cx18 driver have that sort of logic in them. Look for init_on_first_open and serialized_open functions that set some firmware loading related bit flags. I'm not sure what saa7134 does, but devloping a patch to add something similar shouldn't be rocket science for anyone with time, test hardware, and motivation. -Andy -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
I seem to have fixed the problem for now. It's the hoary old problem of Mythtv's backend coming up and accessing the cards before the firmware has loaded onto the cards. Adding in a startup delay to myth-backend's init script has solved the problem, for now. The firmware seems to load now on Mythbuntu 10.04 without a problem. Is there some way to put a lock in the driver or even speed up the process of loading the firmware with some command line arguments when the saa7134 driver is loaded? -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
I'll add the following kernel debug info for what it's worth: - Mar 12 11:22:51 mythtv kernel: [ 14.025097] saa7130/34: v4l2 driver version 0.2.16 loaded Mar 12 11:22:51 mythtv kernel: [ 14.026609] saa7134 :00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 Mar 12 11:22:51 mythtv kernel: [ 14.026617] saa7133[0]: found at :00:09.0, rev: 209, irq: 17, latency: 32, mmio: 0xec00 Mar 12 11:22:51 mythtv kernel: [ 14.026625] saa7133[0]: subsystem: 1043:4857, board: Asus Tiger Rev:1.00 [card=152,autodetected] Mar 12 11:22:51 mythtv kernel: [ 14.026649] saa7133[0]: board init: gpio is 0 Mar 12 11:22:51 mythtv kernel: [ 14.200257] saa7133[0]: i2c eeprom 00: 43 10 57 48 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 Mar 12 11:22:51 mythtv kernel: [ 14.200268] saa7133[0]: i2c eeprom 10: ff ff ff 0f ff 20 ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200279] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff 00 b6 ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200288] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200298] saa7133[0]: i2c eeprom 40: ff 21 00 c2 96 10 03 32 15 00 ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200307] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200316] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200326] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200335] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200344] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200354] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200363] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200372] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200382] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200391] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.200400] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Mar 12 11:22:51 mythtv kernel: [ 14.660189] tuner 1-004b: chip found @ 0x96 (saa7133[0]) Mar 12 11:22:56 mythtv kernel: [ 21.620280] saa7133[0]: registered device video0 [v4l2] Mar 12 11:22:56 mythtv kernel: [ 21.620403] saa7133[0]: registered device vbi0 Mar 12 11:22:56 mythtv kernel: [ 21.620513] saa7133[0]: registered device radio0 Mar 12 11:23:03 mythtv kernel: [ 28.860185] DVB: registering new adapter (saa7133[0]) - Now on the latest reboot I am getting the below. - Mar 12 11:24:13 mythtv kernel: [ 98.240211] DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)... Mar 12 11:24:13 mythtv kernel: [ 98.48] tda1004x: setting up plls for 48MHz sampling clock Mar 12 11:24:15 mythtv kernel: [ 100.930007] tda1004x: found firmware revision 0 -- invalid Mar 12 11:24:15 mythtv kernel: [ 100.930012] tda1004x: trying to boot from eeprom Mar 12 11:24:16 mythtv kernel: [ 101.180011] tda1004x: found firmware revision 80 -- invalid Mar 12 11:24:16 mythtv kernel: [ 101.180017] tda1004x: firmware upload failed Mar 12 11:24:16 mythtv kernel: [ 102.14] tda1004x: setting up plls for 48MHz sampling clock Mar 12 11:24:18 mythtv kernel: [ 103.480013] tda1004x: found firmware revision 0 -- invalid Mar 12 11:24:18 mythtv kernel: [ 103.480018] tda1004x: waiting for firmware upload... Mar 12 11:24:19 mythtv kernel: [ 104.780010] tda1004x: found firmware revision 0 -- invalid Mar 12 11:24:19 mythtv kernel: [ 104.780015] tda1004x: trying to boot from eeprom Mar 12 11:24:22 mythtv kernel: [ 107.400011] tda1004x: found firmware revision 0 -- invalid Mar 12 11:24:22 mythtv kernel: [ 107.400016] tda1004x: waiting for firmware upload... Mar 12 11:25:22 mythtv kernel: [ 167.160013] tda1004x: found firmware revision 0 -- invalid Mar 12 11:25:22 mythtv kernel: [ 167.160021] tda1004x: firmware upload failed Mar 12 11:25:25 mythtv kernel: [ 170.840045] tda1004x: found firmware revision 80 -- invalid Mar 12 11:25:25 mythtv kernel: [ 170.840051] tda1004x: firmware upload failed -- A previous boot up had the card reporting: Nothing has changed between power cycles. - Mar 12 09:22:15 mythtv kernel: [ 67.010115] DVB: registering new adapter (saa7133[1]) Mar 12 09:22:15 mythtv kernel: [ 67.010121] DVB: registering adapter 0 frontend 0 (Philips TDA10046H DVB-T)... Mar 12 09:22:15 mythtv kernel: [ 67.170007] tda1004x: setting up plls for 48MHz sampling clock Mar 12 09:22:17 myt
Problem with saa7134: Asus Tiger revision 1.0, subsys 1043:4857
I just bought a pair of what are a version of the My Cinema 7131 Hybrid cards. The kernel reports it as saa7134: Asus Tiger revision 1.0, subsys 1043:4857 I did inititially try Mythbuntu 10.04 but the firmware upload seemed to fail fairly consistently. Restarting with v10.10 the firmware loads but I can't seem to scan the channels with Mythbackend - it has a 0% signal and 100% signal to noise. I am using MythTV 0.24 with Avenard's latest patches. This version of the card has written on the silkscreen Tiger rev 3.02, a sticker that says Tiger_8M AA.F7.C0.01 (which would appear to be the latest firmware for this card on Asus's support site) but there is only one RF connector on CON1. CON2 is not fitted nor is the IR receiver. Now I saw mentioned on a list that to get DVB working on this card in Linux you need to connect the TV antenna to the FM port, which I suspect is the one not fitted. The latest Windows drivers for this card is circa 2009. Two questions: - Is there some sort of SAA7134 module argument I need to use to get this particular card working on the TV RF input? - Why does the kernel show the firmware is being reloaded every time MythTV seems to want to talk to the card? This slows down access as it seems to take about 30 seconds for the firmware to install each time. I am happy to provide whatever debug dumps or more info if need be. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
