Lifeview Flytv DVB-T hybrid - Cardbus
- From: Peter Missel <peter.missel (at) onlinehome.de>
- Date: Thu, 2 Mar 2006 17:32:47 +0100
Hi GD!
card=55 is the desktop PCI DVB-T Duo. You need to use the Cardbus DUO's
number, which is card=60.
But you really should use a later release of the v4l driver set, since quite a
bit of work has gone into supporting the finer details of these LifeView
cards recently.
regards,
Peter
On Thursday 02 March 2006 14:55, G D wrote:
> Hi again,
> without recompiling the kernel, but simply putting card=55 in the modprobe
> options, the card is indeed reco
> gnized as
>
>
> Mar 2 14:24:06 localhost kernel: [4479898.741000] saa7130/34: v4l2 driver
> version 0.2.12 loaded
> Mar 2 14:24:06 localhost kernel: [4479898.742000] ACPI: PCI Interrupt
> 0000:03:00.0[A] -> GSI 20 (level, low) -> IRQ 20
> Mar 2 14:24:06 localhost kernel: [4479898.742000] saa7133[0]: found at
> 0000:03: 00.0, rev: 208, irq: 20, latency: 64, mmio: 0x20800000
> Mar 2 14:24:06 localhost kernel: [4479898.742000] saa7133[0]: subsystem:
> 5168:3502, board: LifeView FlyDVB-T DUO [card=55,insmod option]
> Mar 2 14:24:06 localhost kernel: [ 4479898.742000] saa7133[0]: board init:
> gpio is 8210000
> Mar 2 14:24:06 localhost kernel: [4479898.743000] saa7133[0]: dsp access
> wait timeout [bit=WRR]
> Mar 2 14:24:06 localhost kernel: [4479898.743000] saa7133[0]: dsp access
> wait timeout [bit=WRR]
> Mar 2 14:24:07 localhost kernel: [4479898.856000] saa7133[0]: i2c eeprom
> 00: 68 51 02 35 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> Mar 2 14:24:07 localhost kernel: [4479898.856000] saa7133[0]: i2c eeprom
> 10: 00 00 62 08 ff 20 ff ff ff ff ff ff ff ff ff ff
> Mar 2 14:24:07 localhost kernel: [4479898.856000] saa7133[0]: i2c eeprom
> 20: 01 40 01 03 03 01 01 03 08 ff 01 14 ff ff ff ff
> Mar 2 14:24:07 localhost kernel: [4479898.856000] saa7133[0]: i2c eeprom
> 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> Mar 2 14:24:07 localhost kernel: [4479898.915000] saa7133[0]: registered
> device video0 [v4l2]
> Mar 2 14:24:07 localhost kernel: [4479898.927000] saa7133[0]: registered
> device vbi0
>
> I see various input sources, both with kdetv and tvtime ... namely:
> * television
> * composite 1 and 2
> * S-Video
>
> tvtime: with television
> input as source, no signal ... even no "snow" ... nothing at all ...
>
> kdetv: with v4l plugin I see al the three leds "green", that
> is "vbi decoder available", "signal power plugin" , "scan available".
> But scanning gives no channel available ... sigh
>
> Changing to the v4l2 plugin, I get the following output
>
> ALSA lib control.c:739:(snd_ctl_open_noupdate) Invalid CTL
> kdetvv4lsetup: using X11 display :0
> dga: version 2.0
> mode: 1280x768, depth=16, bpp=16, bpl=4096, base=0xe8020000
> seteuid(root): Operation not permitted
> kdetv: WARNING: v4ldev: kdetvv4lsetup had some trouble. Trying to continue
> anyway.
> kdetv: WARNING: v4ldev: V4L and KVIDEOIO disagree about the depth of the
> display. Is kdetvv4lsetup installed suid root? Overlay disabled.
> kdetv: WARNING: (I think it should be 16, v4l says: 0)
> Creating vbi proxy client, rev.
> $Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
> proxy_msg: connect: error 2, No such file or directory
> kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connessione via
> socket fallita, server non attivo.
> Try to open V4L2 0.20 VBI device, libzvbi interface rev.
> $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
> Opened /dev/vbi0
> Try to open V4L2 2.6 VBI device, libzvbi interface rev.
> $Id: io-v4l2k.c,v 1.28 2005/05/25 02:26:41 mschimek Exp $
> Opened /dev/vbi0
> /dev/vbi0 (LifeView FlyDVB-T DUO) is a v4l2 vbi device,
> driver saa7134, version 0x0000020c
> Using streaming interface
> Current scanning system is 625
> Querying current vbi parameters... success
> VBI capture parameters supported: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> VBI capture parameters granted: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> Nyquist check passed
> Request decoding of services 0x2000041f, strict level -1
> Will capture services 0x0000041f, added 0x41f commit:1
> Requesting 16 streaming i/o buffers
> Mapping 16 streaming i/o buffers
> Successful opened /dev/vbi0 (LifeView FlyDVB-T DUO)
> kdetv: WARNING: MainWindow::setupInfraRed(): Lirc not available
> kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying
> SourceManager
> kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying
> SourceManager
> kdetv: WARNING: V4L2Dev: VIDIOC_DQBUF failed: Input/output error
> kdetv: WARNING: IO error - requeuing buffer
> kdetv: WARNING: V4L2Dev::enqueueBuffer(): buffer already queued: 0
> Suspending stream...
> Creating vbi proxy client, rev.
> $Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
> proxy_msg: connect: error 2, No such file or directory
> kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connessione via
> socket fallita, server non attivo.
> Try to open V4L2 0.20 VBI device, libzvbi interface rev.
> $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
> Opened /dev/vbi0
> Try to open V4L2 2.6 VBI device, libzvbi interface rev.
> $Id: io-v4l2k.c,v 1.28 2005/05/25 02:26:41 mschimek Exp $
> Opened /dev/vbi0
> /dev/vbi0 (LifeView FlyDVB-T DUO) is a v4l2 vbi device,
> driver saa7134, version 0x0000020c
> Using streaming interface
> Current scanning system is 525
> Querying current vbi parameters... success
> VBI capture parameters supported: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 10...21, F2 272...283, flags 00000000
> VBI capture parameters granted: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 10...21, F2 272...283, flags 00000000
> Nyquist check passed
> Request decoding of services 0x2000041f, strict level -1
> Will capture services 0x00000000, added 0x0 commit:1
> v4l2k_new: failed with errno=22, msg='Spiacente, /dev/vbi0 (LifeView
> FlyDVB-T DUO) impossibile catturare ognuno dei servizi di dati richiesto.'
> guess=''
> kdetv: WARNING: VBIDecoder: vbi_capture_v4l2_new error: Spiacente,
> /dev/vbi0 (LifeView FlyDVB-T DUO) impossibile catturare ognuno dei servizi
> di dati richiesto.
> Try to open v4l vbi device, libzvbi interface rev.
> $Id: io-v4l.c,v 1.28 2004/12/30 02:23:59 mschimek Exp $
> Opened /dev/vbi0
> Driver name 'LifeView FlyDVB-T DUO'
> Attempt to guess the videostandard
> Driver supports VIDIOCGTUNER: mode 1 (0=PAL, 1=NTSC, 2=SECAM)
> Videostandard is NTSC
> /dev/vbi0 (LifeView FlyDVB-T DUO) is a v4l vbi device
> Hinted video standard 0, guessed 525
> Driver supports VIDIOCGVBIFMT, guessed videostandard 525
> VBI capture parameters supported: format 0000000c, 27000000 Hz, 2048 bpl,
> F1 10+12, F2 272+12, flags 00000000
> VBI capture parameters granted: format 0000000c, 27000000 Hz, 2048 bpl, F1
> 10+12, F2 272+12, flags 00000000
> Accept current vbi parameters
> Nyquist check passed
> Request decoding of services 0x2000041f, strict level -1
> Will capture services 0x00000000, added 0x0 commit:1
> kdetv: WARNING: VBIDecoder: vbi_capture_v4l_new error: Spiacente, /dev/vbi0
> (LifeView FlyDVB-T DUO) impossibile catturare ognuno dei servizi di dati
> richiesto.
> kdetv: WARNING: [VBIDecoder::restart()] failed to initialize device
>
>
> whereas, using the v4l plugin I get
>
> ALSA lib control.c:739:(snd_ctl_open_noupdate) Invalid CTL
> kdetvv4lsetup: using X11 display :0
> dga: version 2.0
> mode: 1280x768, depth=16, bpp=16, bpl=4096, base=0xe8020000
> seteuid(root): Operation not permitted
> kdetv: WARNING: v4ldev: kdetvv4lsetup had some trouble. Trying to continue
> anyway.
> kdetv: WARNING: v4ldev: V4L and KVIDEOIO disagree about the depth of the
> display. Is kdetvv4lsetup installed suid root? Overlay disabled.
> kdetv: WARNING: (I think it should be 16, v4l says: 0)
> Creating vbi proxy client, rev.
> $Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
> proxy_msg: connect: error 2, No such file or directory
> kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connessione via
> socket fallita, server non attivo.
> Try to open V4L2 0.20 VBI device, libzvbi interface rev.
> $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
> Opened /dev/vbi0
> Try to open V4L2 2.6 VBI device, libzvbi interface rev.
> $Id: io-v4l2k.c,v 1.28 2005/05/25 02:26:41 mschimek Exp $
> Opened /dev/vbi0
> /dev/vbi0 (LifeView FlyDVB-T DUO) is a v4l2 vbi device,
> driver saa7134, version 0x0000020c
> Using streaming interface
> Current scanning system is 625
> Querying current vbi parameters... success
> VBI capture parameters supported: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> VBI capture parameters granted: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> Nyquist check passed
> Request decoding of services 0x2000041f, strict level -1
> Will capture services 0x0000041f, added 0x41f commit:1
> Requesting 16 streaming i/o buffers
> Mapping 16 streaming i/o buffers
> Successful opened /dev/vbi0 (LifeView FlyDVB-T DUO)
> kdetv: WARNING: MainWindow::setupInfraRed(): Lirc not available
> kdetvv4lsetup: using X11 display :0
> dga: version 2.0
> mode: 1280x768, depth=16, bpp=16, bpl=4096, base=0xe8020000
> seteuid(root): Operation not permitted
> kdetv: WARNING: v4ldev: kdetvv4lsetup had some trouble. Trying to continue
> anyway.
> kdetv: WARNING: v4ldev: V4L and KVIDEOIO disagree about the depth of the
> display. Is kdetvv4lsetup installed suid root? Overlay disabled.
> kdetv: WARNING: (I think it should be 16, v4l says: 0)
> kdetvv4lsetup: using X11 display :0
> dga: version 2.0
> mode: 1280x768, depth=16, bpp=16, bpl=4096, base=0xe8020000
> seteuid(root): Operation not permitted
> kdetv: WARNING: v4ldev: kdetvv4lsetup had some trouble. Trying to continue
> anyway.
> kdetv: WARNING: v4ldev: V4L and KVIDEOIO disagree about the depth of the
> display. Is kdetvv4lsetup installed suid root? Overlay disabled.
> kdetv: WARNING: (I think it should be 16, v4l says: 0)
> kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying
> SourceManager
> kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying
> SourceManager
> Suspending stream...
> Creating vbi proxy client, rev.
> $Id: proxy-client.c,v 1.9 2005/01/20 20:56:11 mschimek Exp $
> proxy_msg: connect: error 2, No such file or directory
> kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connessione via
> socket fallita, server non attivo.
> Try to open V4L2 0.20 VBI device, libzvbi interface rev.
> $Id: io-v4l2.c,v 1.31 2004/12/30 02:24:11 mschimek Exp $
> Opened /dev/vbi0
> Try to open V4L2 2.6 VBI device, libzvbi interface rev.
> $Id: io-v4l2k.c,v 1.28 2005/05/25 02:26:41 mschimek Exp $
> Opened /dev/vbi0
> /dev/vbi0 (LifeView FlyDVB-T DUO) is a v4l2 vbi device,
> driver saa7134, version 0x0000020c
> Using streaming interface
> Current scanning system is 625
> Querying current vbi parameters... success
> VBI capture parameters supported: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> VBI capture parameters granted: format 59455247 [GREY], 27000000 Hz, 2048
> bpl, offs 256, F1 7...22, F2 319...334, flags 00000000
> Nyquist check passed
> Request decoding of services 0x2000041f, strict level -1
> Will capture services 0x0000041f, added 0x41f commit:1
> Requesting 16 streaming i/o buffers
> Mapping 16 streaming i/o buffers
> Successful opened /dev/vbi0 (LifeView FlyDVB-T DUO)
>
> and "green leds"
>
> Anyway, a good thing would be for sure upgrading the kernel, so that is
> what I'm currently going to do
> Any hint will be appreciated.
> Greetings,
> G.D. Fiamazo
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list