Hi, Just a hunch, but try 'pal=I' on the tda9887 module... Not quite sure how this whole module param stuff works, I can see that the value is case insensitive, but cannot trace back the keyword stuff to check this...
The "ivtv: i2c client addr: 0x50 not found!" should not be a problem: it is the tveeprom module looking for a hauppauge eeprom... Regards, Stanley. > Hi Stanley > > I am getting only static. > I am trying to receive terrestrial TV from my aerial > I believe the transmitting frequencies are between 471.25 and 847.25 in 8MHz > steps. I also believe locally the relevant frequencies are: > > ITV 487.25MHz > BBC1 511.25MHz > CH4 535.25MHz > BBC2 567.25MHz > CH5 583.25MHz > > I got the above information from http://www.bbc.co.uk/reception and have been > using ptune-ui.pl and the pal-europe setting. I have been stepping through > all the frequencies and have not got any sort of picture yet. > > I reversed the order of loading the tuner and tda9887 modules and tried again > (exactly the same). > > I don't know if it is of any relevance, but I am getting i2c address 0x50 not > found. Below is the dmesg output, maybe that will show something useful. As > you can see the PAL=I option is apparently not working. > > > tda9887: Unknown parameter `PAL' > tuner: Unknown parameter `PAL' > Linux video capture interface: v1.00 > ivtv: Unknown parameter `PAL' > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.3.2 (d) loading > ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv: User specified WinTV PVR 250 card > ivtv: Found an iTVC16 based chip > PCI: Found IRQ 10 for device 0000:00:0e.0 > PCI: Sharing IRQ 10 with 0000:00:05.0 > PCI: Sharing IRQ 10 with 0000:00:07.0 > PCI: Sharing IRQ 10 with 0000:00:09.2 > ivtv: Unreasonably low latency timer, setting to 64 (was 32) > ivtv: VIA PCI device: 0x3099 vendor: 0x1106 > tda9885/6/7: chip found @ 0x86 > ivtv: i2c attach [client=tda9887,ok] > tuner: chip found at addr 0xd6 i2c-bus ivtv i2c driver #0 > ivtv: i2c attach [client=(tuner unset),ok] > tveeprom: Ignoring new-style parameters in presence of obsolete ones > ivtv: i2c client addr: 0x50 not found! > ivtv: Error -19 reading Hauppauge eeprom. > ivtv: Possible causes: the tveeprom module was not loaded, or > ivtv: the eeprom kernel module was loaded before the tveeprom module. > saa7115: Ignoring new-style parameters in presence of obsolete ones > saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) > saa7115: detecting saa7115 client on address 0x42 > saa7115: writing init values > ivtv: i2c attach [client=saa7115[0],ok] > saa7115: status: (1E) 0x40, (1F) 0xc0 > msp3400: Ignoring new-style parameters in presence of obsolete ones > msp34xx: ivtv version > msp34xx: init: chip=MSP3415G-B8, has NICAM support, simple (D) mode, simpler > (G) no-thread mode > msp34xx: $Id$ compiled on: Feb 10 2005 13:11:49 > ivtv: i2c attach [client=MSP3415G-B8,ok] > ivtv: Encoder revision: 0x02030015 > ivtv: Configuring WinTV PVR 250 card with 4 streams > ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total > ivtv: Registered v4l2 device, streamtype 0 minor 0 > ivtv: Create DMA stream 1 > ivtv: Registered v4l2 device, streamtype 1 minor 32 > ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 2 minor 224 > ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 3 minor 24 > saa7115: decoder set input (4) > saa7115: now setting Composite input > ivtv: Setting audio matrix to input 3, output 1 > ivtv: Switching standard to PAL. > ivtv: ivtv_enc_thread: pid = 7479, itv = 0xd0ee6740 > saa7115: decoder set norm PAL > saa7115: set audio: 0x01 > ivtv: Initialized WinTV PVR 250, card #0 > ivtv: ==================== END INIT IVTV ==================== > > Best Regards > > Trev > > > On Friday 11 Feb 2005 08:17, [EMAIL PROTECTED] wrote: > > Hi, > > > > Well, your list of modules looks okay, but try and reverse the order of > > loading the tuner and tda9887 modules. > > (tda9887 should get loaded automatically by the tuner module, but it looks > > as if the PAL mode setting isn't passed into the tda9887 module). > > > > Also not quite sure if your tuner needs this module, but what I've seen > > from a few datasheets is that most modern Philips multistandard tuners (ME > > versions?) use this chip to demodulate the signal into video/audio. > > > > Are you getting any picture? Only static? Just a black screen? > > > > If you're getting only static, is there a part of the frequency range that > > does give a picture? Try this with ivtvctl -r $(({freq_in_MHz}*16)). > > Try frequencies in approx. the following ranges: 50-160MHz (low band), > > 160-442MHz, 442+MHz. > > (these ranges are for my tuner, yours might be 10-20MHz off, don't have the > > datasheet to look up the details). > > > > Of course it will help to have a list of frequencies from your cable > > company... > > > > If this is not a problem, then you won't need to fix it ;-) > > > > Regards, > > Stanley. > > > > > Hi Stanley > > > > > > I have previously not been loading the module tda9887. > > > I have listed the modules that are being loaded below, can you tell me if > > > > I> > > > > > have any others missing. (my current setup works OK with the composite > > > input). NOTE: The adapter is an Adaptec AVC-2410 and I need to set the > > > > car> d > > > > > type to 2 to make it work. > > > > > > msp3400 > > > saa7115 > > > tveeprom > > > ivtv > > > i2c-algo-bit > > > videodev > > > tda9887 > > > tuner > > > > > > I am loading them with: > > > > > > modprobe tuner PAL=I type=52 > > > modprobe tda9887 PAL=I > > > modprobe ivtv cardtype=2 ivtv_std=2 PAL=I > > > > > > then to make the sound run at the correct speed on my card: > > > > > > ivtvctl -g reg=0x0030,val=0x03 > > > ivtvctl -g reg=0x0031,val=0xc0 > > > ivtvctl -g reg=0x0032,val=0x00 > > > > > > ivtvctl -g reg=0x0034,val=0xe7 > > > ivtvctl -g reg=0x0035,val=0x7d > > > ivtvctl -g reg=0x0036,val=0x18 > > > > > > I will have a look at patching the the modules although I'm not quite > > > > certa> in > > > > > how to go about it. > > > > > > Best Regards > > > > > > Trev > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > ivtv-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > ivtv-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
