saa7134 (card=3) tv card bad composite reception

kilgor · 08-13-2005, 10:40 AM

Hi,

I have a Chronos Shuttle II FM PCI video card with a SAA7130 Phillips chip. I don't care about the tuner, right now I really need to get composite IN working.

ATM I get this picture using tvtime, from a device. It should be in color and look OK. The problem is, it's black and white instead of color and well, screwed up.

I don't have any other devices with composite out, which I could test. Using the same cabling I connected the device to a TV's composite IN and it worked just fine. So the problem has to be with the tv card.

A few years ago I used the composite IN on Windows XP to rip video from a video camera, it worked good enough. I don't have windows installed ATM and was unable to get the card working with Windows XP SP1 nor with SP2 at all.

I'm using an up to date Fedora Core 4, it detected the card during install.

uname -a

Code:

Linux blah.blah 2.6.12-1.1398_FC4 #1 Fri Jul 15 00:52:32 EDT 2005 i686 athlon i386 GNU/Linux

modprobe.conf:

Code:

alias eth0 8139too
alias eth1 forcedeth
alias snd-card-0 snd-emu10k1
options snd-card-0 index=0
options snd-emu10k1 index=0
remove snd-emu10k1 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-emu10k1
alias char-major-81 saa7134
options saa7134 card=3 tuner=23 #### THIS LINE WAS ADDED BY ME.
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
alias ieee1394-controller ohci1394
alias scsi_hostadapter sata_nv
alias char-major-195* nvidia
alias char-major-195* nvidia

card=3 should be correct, it's corresponding to the FlyVideo 2000FM card, which uses the same chip (saa7130). Although when I tried card=2 (FlyVideo 3000 with saa7134 chip) I got the same b&w buggy picture as before. I know that card=3 is OK from google. AFAIK they should be almost identical cards.

As I understand, the tuner doesn't matter. When I removed the tuner option and then manually removed the tuner module, nothing changed for composite input.

lspci -vv:

Code:

01:07.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
        Subsystem: Philips Semiconductors: Unknown device 0000
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (3750ns min, 9500ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at ea080000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [40] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

dmesg, during boot:

Code:

Linux video capture interface: v1.00
saa7130/34: v4l2 driver version 0.2.12 loaded
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [LNK4] -> GSI 11 (level, low) -> IRQ 11
saa7130[0]: found at 0000:01:07.0, rev: 1, irq: 11, latency: 32, mmio: 0xea080000
saa7130[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO2000 [card=3,insmod option]
saa7130[0]: board init: gpio is 31000
saa7130[0]: there are different flyvideo cards with different tuners
saa7130[0]: out there, you might have to use the tuner=<nr> insmod
saa7130[0]: option to override the default value.
saa7130[0]: registered input device for IR
saa7130[0]: Huh, no eeprom present (err=-5)?
tuner 2-0061: chip found @ 0xc2 (saa7130[0])
tuner 2-0061: type set to 23 (Philips PAL_DK (FI1256 and compatibles))
saa7130[0]: registered device video0 [v4l2]
saa7130[0]: registered device vbi0
saa7130[0]: registered device radio0

Is this OK, they all have "IRQ=11"? Some of "dmesg | grep -i irq | grep 11":

Code:

eth0: RealTek RTL8139 at 0xc800, 00:04:61:47:e7:a8, IRQ 11
saa7130[0]: found at 0000:01:07.0, rev: 1, irq: 11, latency: 32, mmio: 0xea080000
ohci_hcd 0000:00:02.0: irq 11, io mem 0xeb002000
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11]  MMIO=[ea083000-ea0837ff]  Max Packet=[2048]

Could the bad picture be a result of some hardware conflict? My motherboard is a Epox nforce2 400 board. It has integrated two NICs, audio, SATA controller and the usual stuff. Besides the Chronos Shuttle I have a Soundblaster Live! Digital audio card in the PCI slots. In the AGP slot there's a NVidia MX440 video card. When I used the composite IN with windows 2+ years ago, I didn't have the Soundblaster and it may or may not have been in another slot.

It can't be tvtime's fault, can it? I tried different settings with tvtime with no change at all, but haven't triend another viewer, like xawtv. It's not in the standard repos nor in livna, so I haven't bothered.

Thanks for any suggestions in advance!

Electro · 08-13-2005, 08:12 PM

The saa7130 to saa7134 has 8 inputs. The code for your card sets up an extra composite. Usually its Composite number 2 not Composite 1 if you get black and white video from Composite 1. It did the same to me too, but I edit the saa7134 code to make it human readable. From the changes I have Television, Composite, and S-Video. Sorry, I do not have pre-made patches, but it is easy after you check the source code. Look for file saa7134-cards.c. Then look for your card and use comments for TV (mono only) and Composite1. I suggest backing up the saa7134 directory in the kernel source code.

I added

Code:

static char name_comp0[]   = "Composite";

to the commly used strings part. To change the name for Composite1 to Composite. Look for name_comp2 for your video capture card and change it to name_comp0. Save and compile. It will feel like Windows again.

I have a Lifeview Flyvideo 3000FM, so the changes should work for your card too.

My VBI changes are at http://www.linuxquestions.org/questi...hreadid=349850. I think the changes will also work PAL too but I do not know.

kilgor · 08-14-2005, 03:51 AM

I should have mentioned that I did use Composite2, Composite1 was blank.

OK, sa what will renaming give me exatly? I don't think it'll give me a good picture. Or did I miss something?

Thnaks!

edit2:

I got the kernel source and had a look at the file:

Code:

--snap--
/* commly used strings */
static char name_mute[]    = "mute";
static char name_radio[]   = "Radio";
static char name_tv[]      = "Television";
static char name_tv_mono[] = "TV (mono only)";
static char name_comp1[]   = "Composite1";
static char name_comp2[]   = "Composite2";
static char name_comp3[]   = "Composite3";
static char name_comp4[]   = "Composite4";
static char name_svideo[]  = "S-Video";
--snap--
        [SAA7134_BOARD_FLYVIDEO2000] = {
                /* "TC Wan" <blahblahblah> */
                .name           = "LifeView FlyVIDEO2000",
                .audio_clock    = 0x00200000,
                .tuner_type     = TUNER_LG_PAL_NEW_TAPC,
                .gpiomask       = 0xe000,
                .inputs         = {{
                        .name = name_tv,
                        .vmux = 1,
                        .amux = LINE2,
                        .gpio = 0x0000,
                        .tv   = 1,
                },{
                        .name = name_comp1, /* No input, just the blank (blue) screen */
                        .vmux = 0,
                        .amux = LINE2,
                        .gpio = 0x4000,
                },{
                        .name = name_comp2,   /* I get the black and white bad picture from here */
                        .vmux = 3,
                        .amux = LINE2,
                        .gpio = 0x4000,
                },{
                        .name = name_svideo,
                        .vmux = 8,
                        .amux = LINE2,
                        .gpio = 0x4000,
                }},
                .radio = {
                        .name = name_radio,
                        .amux = LINE2,
                        .gpio = 0x2000,
                },
                .mute = {
                        .name = name_mute,
                        .amux = LINE2,
                        .gpio = 0x8000,
                },
        },
--snap--

Electro · 08-14-2005, 07:25 AM

I thought you did not test composite 2. You should of said that you tried composite 1 and composite 2.

Make sure you set tvtime to the correct signal (NTSC, PAL, PAL-60, and many others) for your area. If it still gives you a black and white picture, you will have to do some code hacking. In saa7134-cards.c change .vmux to other values for Composite1 and Composite2. You can use 2, 4, 5, 6, 7 which are the unused values for .vmux. You will have to do trial and error until you see color. I suggest using tvtime because xawtv will give you no picture unless you configure it already. Sometimes tvtime will give you no picture after you unload the module and load it up again, so quit it and re-open it until it does.

From the tvtime-output.png file (whew! what a big file), it looks like you need to adjust the video_v_start and video_v_stop variable in saa7134-video.c. I do not suggest doing this until you set tvtime to the correct signal and pick the correct .vmux value.

Quote:

OK, sa what will renaming give me exatly?

It makes it easier to read when you switch to different inputs.

kilgor · 08-14-2005, 09:00 AM

Quote:

Originally posted by Electro
Make sure you set tvtime to the correct signal (NTSC, PAL, PAL-60, and many others) for your area.

Ahh, I have to admit that I'm an idiot. I thought I had tvtime set for PAL, but I didn't double check it and guess what. It was set to NTSC-JP. Blah. Got the picture OK now.

Sorry about the big .png, I used the default tvtime screenshot feature.

Thanks a lot for the info, at least I know a bit about this stuff now.