xawtv - no picture

xawtv - no picture

[Ian Davidson]

I am trying to run xawtv (or actually streamer) to capture video - but 
at the moment, it is not working.

For details of my system, please see 
http://www.smolts.org/client/show_all/pub_86fd06ee-583b-40d2-b23b-92749309023b

I have a K-World DVB-T 210SE card which I hope will allow me to capture 
the video (although that is not very evident in the above link)

Here is a section of the dmesg output
Linux video capture interface: v2.00
saa7130/34: v4l2 driver version 0.2.14 loaded
ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64, mmio: 
0xfebff800
saa7133[0]: subsystem: 17de:7253, board: UNKNOWN/GENERIC 
[card=0,autodetected]
saa7133[0]: board init: gpio is 100
parport_pc 00:07: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[0]: registered device video0 [v4l2]
saa7133[0]: registered device vbi0
ppdev: user-space parallel port driver

When I try to run xawtv, this is what I get
[Ian@localhost ~]$ xawtv
This is xawtv-3.95, running on Linux/i686 (2.6.25.10-86.fc9.i686)
xinerama 0: 1440x900+0+0
WARNING: No DGA support available for this display.
WARNING: couldn't find framebuffer base address, try manual
         configuration ("v4l-conf -a <addr>")
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: 
VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: 
VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
[Ian@localhost ~]$

Also, the screen is black, although the camera was turned on.

I feel that it is trying to tell me something - but I do not understand 
what it is saying.  Is there any hope?

Ian

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: xawtv - no picture

[hermann pitton]

Hi Ian,

Am Sonntag, den 27.07.2008, 16:21 +0100 schrieb Ian Davidson:
> I am trying to run xawtv (or actually streamer) to capture video - but 
> at the moment, it is not working.
> 
> For details of my system, please see 
> http://www.smolts.org/client/show_all/pub_86fd06ee-583b-40d2-b23b-92749309023b
> 
> I have a K-World DVB-T 210SE card which I hope will allow me to capture 
> the video (although that is not very evident in the above link)
> 
> Here is a section of the dmesg output
> Linux video capture interface: v2.00
> saa7130/34: v4l2 driver version 0.2.14 loaded
> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64, mmio: 
> 0xfebff800
> saa7133[0]: subsystem: 17de:7253, board: UNKNOWN/GENERIC 

that board seems to be not reported yet.

> [card=0,autodetected]

That card=0 has only input on videomux 0 enabled.
This is on most boards composite over the s-video connector.

On KWORLD_DVBT_210 card=114, which is likely close to it or even fully
compatible, the composite over s-video connector is not enabled yet.

Only composite on vmux = 3 and s-video on vmux = 8. Depending on how
composite is connected through the breakout cable, we might need a
section with composite2 vmux = 0 in saa7134-cards.c.

> saa7133[0]: board init: gpio is 100
> parport_pc 00:07: reported by Plug and Play ACPI
> parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> ppdev: user-space parallel port driver
> 
> When I try to run xawtv, this is what I get
> [Ian@localhost ~]$ xawtv
> This is xawtv-3.95, running on Linux/i686 (2.6.25.10-86.fc9.i686)
> xinerama 0: 1440x900+0+0
> WARNING: No DGA support available for this display.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> WARNING: couldn't find framebuffer base address, try manual
>          configuration ("v4l-conf -a <addr>")
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> ioctl: 
> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: 
> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> Invalid argument
> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> [Ian@localhost ~]$
> 
> Also, the screen is black, although the camera was turned on.
> 
> I feel that it is trying to tell me something - but I do not understand 
> what it is saying.  Is there any hope?
> 
> Ian
> 

On most binary video-card drivers you can't set overlay preview mode
anymore.

You might try to force xawtv -remote -nodga -c /dev/video0 on card=114
to have it in mmap/grabdisplay mode.

Please test whatever you can that we might add the card to auto
detection.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: xawtv - no picture

[Ian Davidson]

The card has 4 sockets on the back
- FM Antenna
- UHF/VHF antenna
- S-Video
- Remote sensor.

This time, I tried plugging the camera into the S-Video (rather than the 
FM antenna - oops!) but it didn't help - still a black screen.

I ran xawtv with the -v 1 option and got this

[Ian@localhost ~]$ xawtv -remote -nodga -c /dev/video on card=114 -v 1
This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
visual: id=0x21 class=4 (TrueColor), depth=24
visual: id=0x22 class=5 (DirectColor), depth=24
visual: id=0x5b class=4 (TrueColor), depth=32
x11: color depth: 24 bits, 3 bytes - pixmap: 4 bytes
x11: color masks: red=0x00ff0000 green=0x0000ff00 blue=0x000000ff
x11: server byte order: little endian
x11: client byte order: little endian
main: dga extention...
main: xinerama extention...
xinerama 0: 1440x900+0+0
main: xvideo extention [video]...
main: xvideo extention [image]...
main: init main window...
main: install signal handlers...
main thread [pid=2619]
main: open grabber device...
x11: remote display (overlay disabled)
vid-open: trying: v4l2-old...
vid-open: failed: v4l2-old
vid-open: trying: v4l2...
v4l2: open
v4l2: device info:
  saa7134 0.2.14 / UNKNOWN/GENERIC @ PCI:0000:04:02.0
vid-open: ok: v4l2
main: checking wm...
wmhooks: netwm state above
wmhooks: netwm state fullscreen
main: creating windows ...
main: init frequency tables ...
freq: reading /usr/share/xawtv/Index.map
main: read config file ...
xt: checking for randr extention ...
xrandr: 1440x900 1400x1050 1280x1024 1280x960 1152x864 1024x768 832x624 
800x600 640x480 720x400
xt: checking for vidmode extention ...
xt: checking for lirc ...
lirc: not enabled at compile time
xt: checking for joystick ...
xt: checking for midi ...
xt: adding kbd hooks ...
main: mapping main window ...
main: initialize hardware ...
main: parse channels from config file ...
xt: handle_pending:  start ...
gd: init
blit: init
blit: gl: init
blit: gl: DRI=Yes
blit: gl: texture max size: 2048
blit: resize 384x288
gd: config 384x288 win=3c00060
blit: gl: extention GL_EXT_bgra is available
blit: gl: extention GL_EXT_bgra is available
v4l2: new capture params (384x288, BGR3, 331776 byte)
setformat: 24 bit TrueColor (LE: bgr) (384x288): ok
grabdisplay: using "24 bit TrueColor (LE: bgr)"
xt: handle_pending:  ... done
cmd: "setfreqtab" "europe-west"
freq: newtab 5
freq: reading /usr/share/xawtv/europe-west.list
freq: reading /usr/share/xawtv/ccir-i-iii.list
freq: reading /usr/share/xawtv/ccir-sl-sh.list
freq: reading /usr/share/xawtv/ccir-h.list
freq: reading /usr/share/xawtv/uhf.list
cmd: "capture" "overlay"
gd: start [7]
v4l2: new capture params (384x288, BGR3, 331776 byte)
setformat: 24 bit TrueColor (LE: bgr) (384x288): ok
ioctl: VIDIOC_REQBUFS(count=2;type=VIDEO_CAPTURE;memory=MMAP): Success
v4l2: buf 0: video-cap 0x0+331776, used 0
v4l2: buf 1: video-cap 0x51000+331776, used 0
main: setting defaults
xt: enter main event loop...
v4l2: start ts=1217446410590289000
blit: gl: extention GL_EXT_bgra is available
blit: gl: frame=384x288, texture=512x512
blit: 384x288/[24 bit TrueColor (LE: bgr)] => OpenGL
expose count=4
expose count=3
expose count=2
expose count=1
expose count=0
keypad: timeout
cmd: "capture" "off"
gd: stop
v4l2: buf 0: video-cap 0x0+331776, used 331776
v4l2: buf 1: video-cap 0x51000+331776, used 331776
v4l2: new capture params (384x288, BGR4, 442368 byte)
setformat: 32 bit TrueColor (LE: bgr-) (384x288): ok
v4l2: new capture params (384x288, BGR4, 442368 byte)
v4l2: close
[Ian@localhost ~]$

-
I have been writing programs for almost 44 years - but I blunder round 
linux like a newbie.  I appreciate all the help you can give me.  Please 
let me know what else I can do to get this working.

Ian

hermann pitton wrote:
> Hi Ian,
>
> Am Sonntag, den 27.07.2008, 16:21 +0100 schrieb Ian Davidson:
>   
>> I am trying to run xawtv (or actually streamer) to capture video - but 
>> at the moment, it is not working.
>>
>> For details of my system, please see 
>> http://www.smolts.org/client/show_all/pub_86fd06ee-583b-40d2-b23b-92749309023b
>>
>> I have a K-World DVB-T 210SE card which I hope will allow me to capture 
>> the video (although that is not very evident in the above link)
>>
>> Here is a section of the dmesg output
>> Linux video capture interface: v2.00
>> saa7130/34: v4l2 driver version 0.2.14 loaded
>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64, mmio: 
>> 0xfebff800
>> saa7133[0]: subsystem: 17de:7253, board: UNKNOWN/GENERIC 
>>     
>
> that board seems to be not reported yet.
>
>   
>> [card=0,autodetected]
>>     
>
> That card=0 has only input on videomux 0 enabled.
> This is on most boards composite over the s-video connector.
>
> On KWORLD_DVBT_210 card=114, which is likely close to it or even fully
> compatible, the composite over s-video connector is not enabled yet.
>
> Only composite on vmux = 3 and s-video on vmux = 8. Depending on how
> composite is connected through the breakout cable, we might need a
> section with composite2 vmux = 0 in saa7134-cards.c.
>
>   
>> saa7133[0]: board init: gpio is 100
>> parport_pc 00:07: reported by Plug and Play ACPI
>> parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> saa7133[0]: registered device video0 [v4l2]
>> saa7133[0]: registered device vbi0
>> ppdev: user-space parallel port driver
>>
>> When I try to run xawtv, this is what I get
>> [Ian@localhost ~]$ xawtv
>> This is xawtv-3.95, running on Linux/i686 (2.6.25.10-86.fc9.i686)
>> xinerama 0: 1440x900+0+0
>> WARNING: No DGA support available for this display.
>>     
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>   
>> WARNING: couldn't find framebuffer base address, try manual
>>          configuration ("v4l-conf -a <addr>")
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> ioctl: 
>> VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: 
>> VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
>> Invalid argument
>> ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
>> [Ian@localhost ~]$
>>
>> Also, the screen is black, although the camera was turned on.
>>
>> I feel that it is trying to tell me something - but I do not understand 
>> what it is saying.  Is there any hope?
>>
>> Ian
>>
>>     
>
> On most binary video-card drivers you can't set overlay preview mode
> anymore.
>
> You might try to force xawtv -remote -nodga -c /dev/video0 on card=114
> to have it in mmap/grabdisplay mode.
>
> Please test whatever you can that we might add the card to auto
> detection.
>
> Cheers,
> Hermann
>
>
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: xawtv - no picture

[hermann pitton]

Hi,

Am Mittwoch, den 30.07.2008, 20:07 +0100 schrieb Ian Davidson:
> The card has 4 sockets on the back
> - FM Antenna
> - UHF/VHF antenna
> - S-Video
> - Remote sensor.
> 
> This time, I tried plugging the camera into the S-Video (rather than
> the FM antenna - oops!) but it didn't help - still a black screen.
> 
> I ran xawtv with the -v 1 option and got this
> 
> [Ian@localhost ~]$ xawtv -remote -nodga -c /dev/video on card=114 -v 1
> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
> visual: id=0x21 class=4 (TrueColor), depth=24
> visual: id=0x22 class=5 (DirectColor), depth=24
> visual: id=0x5b class=4 (TrueColor), depth=32
> x11: color depth: 24 bits, 3 bytes - pixmap: 4 bytes
> x11: color masks: red=0x00ff0000 green=0x0000ff00 blue=0x000000ff
> x11: server byte order: little endian
> x11: client byte order: little endian
> main: dga extention...
> main: xinerama extention...
> xinerama 0: 1440x900+0+0
> main: xvideo extention [video]...
> main: xvideo extention [image]...
> main: init main window...
> main: install signal handlers...
> main thread [pid=2619]
> main: open grabber device...
> x11: remote display (overlay disabled)
> vid-open: trying: v4l2-old... 
> vid-open: failed: v4l2-old
> vid-open: trying: v4l2... 
> v4l2: open
> v4l2: device info:
>   saa7134 0.2.14 / UNKNOWN/GENERIC @ PCI:0000:04:02.0
> vid-open: ok: v4l2
> main: checking wm...
> wmhooks: netwm state above
> wmhooks: netwm state fullscreen
> main: creating windows ...
> main: init frequency tables ...
> freq: reading /usr/share/xawtv/Index.map
> main: read config file ...
> xt: checking for randr extention ...
> xrandr: 1440x900 1400x1050 1280x1024 1280x960 1152x864 1024x768
> 832x624 800x600 640x480 720x400
> xt: checking for vidmode extention ...
> xt: checking for lirc ...
> lirc: not enabled at compile time
> xt: checking for joystick ...
> xt: checking for midi ...
> xt: adding kbd hooks ...
> main: mapping main window ...
> main: initialize hardware ...
> main: parse channels from config file ...
> xt: handle_pending:  start ...
> gd: init
> blit: init
> blit: gl: init
> blit: gl: DRI=Yes
> blit: gl: texture max size: 2048
> blit: resize 384x288
> gd: config 384x288 win=3c00060
> blit: gl: extention GL_EXT_bgra is available
> blit: gl: extention GL_EXT_bgra is available
> v4l2: new capture params (384x288, BGR3, 331776 byte)
> setformat: 24 bit TrueColor (LE: bgr) (384x288): ok
> grabdisplay: using "24 bit TrueColor (LE: bgr)"
> xt: handle_pending:  ... done
> cmd: "setfreqtab" "europe-west"
> freq: newtab 5
> freq: reading /usr/share/xawtv/europe-west.list
> freq: reading /usr/share/xawtv/ccir-i-iii.list
> freq: reading /usr/share/xawtv/ccir-sl-sh.list
> freq: reading /usr/share/xawtv/ccir-h.list
> freq: reading /usr/share/xawtv/uhf.list
> cmd: "capture" "overlay"
> gd: start [7]
> v4l2: new capture params (384x288, BGR3, 331776 byte)
> setformat: 24 bit TrueColor (LE: bgr) (384x288): ok
> ioctl: VIDIOC_REQBUFS(count=2;type=VIDEO_CAPTURE;memory=MMAP): Success
> v4l2: buf 0: video-cap 0x0+331776, used 0
> v4l2: buf 1: video-cap 0x51000+331776, used 0
> main: setting defaults
> xt: enter main event loop... 
> v4l2: start ts=1217446410590289000
> blit: gl: extention GL_EXT_bgra is available
> blit: gl: frame=384x288, texture=512x512
> blit: 384x288/[24 bit TrueColor (LE: bgr)] => OpenGL
> expose count=4
> expose count=3
> expose count=2
> expose count=1
> expose count=0
> keypad: timeout
> cmd: "capture" "off"
> gd: stop
> v4l2: buf 0: video-cap 0x0+331776, used 331776
> v4l2: buf 1: video-cap 0x51000+331776, used 331776
> v4l2: new capture params (384x288, BGR4, 442368 byte)
> setformat: 32 bit TrueColor (LE: bgr-) (384x288): ok
> v4l2: new capture params (384x288, BGR4, 442368 byte)
> v4l2: close
> [Ian@localhost ~]$ 
> 
> -
> I have been writing programs for almost 44 years - but I blunder round
> linux like a newbie.  I appreciate all the help you can give me.
> Please let me know what else I can do to get this working.
> 
> Ian


for sure I know you are not around the first time.

Despite of the camera, please try card=114 and provide all dmesg stuff
you can gather for it and the tuner.

Kworld has nothing in the eeprom one could eventually start guessing on,
but I know for sure they are not mad and keep a line and you likely find
someone even responding on linux.

Likely we don't need to moleste anyone, if we have the logs.

Cheers,
Hermann


> hermann pitton wrote: 
> > Hi Ian,
> > 
> > Am Sonntag, den 27.07.2008, 16:21 +0100 schrieb Ian Davidson:
> >   
> > > I am trying to run xawtv (or actually streamer) to capture video - but 
> > > at the moment, it is not working.
> > > 
> > > For details of my system, please see 
> > > http://www.smolts.org/client/show_all/pub_86fd06ee-583b-40d2-b23b-92749309023b
> > > 
> > > I have a K-World DVB-T 210SE card which I hope will allow me to capture 
> > > the video (although that is not very evident in the above link)
> > > 
> > > Here is a section of the dmesg output
> > > Linux video capture interface: v2.00
> > > saa7130/34: v4l2 driver version 0.2.14 loaded
> > > ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
> > > saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64, mmio: 
> > > 0xfebff800
> > > saa7133[0]: subsystem: 17de:7253, board: UNKNOWN/GENERIC 
> > >     
> > 
> > that board seems to be not reported yet.
> > 
> >   
> > > [card=0,autodetected]
> > >     
> > 
> > That card=0 has only input on videomux 0 enabled.
> > This is on most boards composite over the s-video connector.
> > 
> > On KWORLD_DVBT_210 card=114, which is likely close to it or even fully
> > compatible, the composite over s-video connector is not enabled yet.
> > 
> > Only composite on vmux = 3 and s-video on vmux = 8. Depending on how
> > composite is connected through the breakout cable, we might need a
> > section with composite2 vmux = 0 in saa7134-cards.c.
> > 
> >   
> > > saa7133[0]: board init: gpio is 100
> > > parport_pc 00:07: reported by Plug and Play ACPI
> > > parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
> > > saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> > > saa7133[0]: registered device video0 [v4l2]
> > > saa7133[0]: registered device vbi0
> > > ppdev: user-space parallel port driver
> > > 
> > > When I try to run xawtv, this is what I get
> > > [Ian@localhost ~]$ xawtv
> > > This is xawtv-3.95, running on Linux/i686 (2.6.25.10-86.fc9.i686)
> > > xinerama 0: 1440x900+0+0
> > > WARNING: No DGA support available for this display.
> > >     
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> >   
> > > WARNING: couldn't find framebuffer base address, try manual
> > >          configuration ("v4l-conf -a <addr>")
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > ioctl: 
> > > VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: 
> > > VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=3;fmt.win.w.top=48;fmt.win.w.width=384;fmt.win.w.height=288;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x9414cb4;fmt.win.clipcount=1;fmt.win.bitmap=(nil)): 
> > > Invalid argument
> > > ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
> > > [Ian@localhost ~]$
> > > 
> > > Also, the screen is black, although the camera was turned on.
> > > 
> > > I feel that it is trying to tell me something - but I do not understand 
> > > what it is saying.  Is there any hope?
> > > 
> > > Ian
> > > 
> > >     
> > 
> > On most binary video-card drivers you can't set overlay preview mode
> > anymore.
> > 
> > You might try to force xawtv -remote -nodga -c /dev/video0 on card=114
> > to have it in mmap/grabdisplay mode.
> > 
> > Please test whatever you can that we might add the card to auto
> > detection.
> > 
> > Cheers,
> > Hermann
> > 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: xawtv - no picture

[hermann pitton]

Am Donnerstag, den 31.07.2008, 00:44 +0200 schrieb hermann pitton:
> Hi,
> 
> Am Mittwoch, den 30.07.2008, 20:07 +0100 schrieb Ian Davidson:
> > The card has 4 sockets on the back
> > - FM Antenna
> > - UHF/VHF antenna
> > - S-Video
> > - Remote sensor.
> > 
> > This time, I tried plugging the camera into the S-Video (rather than
> > the FM antenna - oops!) but it didn't help - still a black screen.
> > 

Oops, you are serious about thaT ;) ?

for what I read you are missing to use the breakout cable ...

on that low profile.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: xawtv - no picture

[hermann pitton]

Hi Ian,

Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
> Hi Hermann,
> 
> 1) I have changed my email "Reply-To" as emails were getting lost in
> the system.
> 
> 2) I searched for modprobe.conf and found one (only)
> in /usr/share/logwatch/default.conf/services.  I opened it and saw
> that it was empty (apart from comments) and added the options line.  I
> then saved it and copied it to /etc and ran depmod.  After rebooting,
> this is what I get in dmesg (extract)
> 
> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> ppdev: user-space parallel port driver
> Linux video capture interface: v2.00
> saa7130/34: v4l2 driver version 0.2.14 loaded
> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
> saa7133[0]: setting pci latency timer to 64
> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
> mmio: 0xfebff800
> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
> [card=114,insmod option]
> saa7133[0]: board init: gpio is 100
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
> 0x4401
> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff
> saa7133[0]: i2c scan: found device @ 0x10  [???]
> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
> (0x14/0x15/0x16/0x17/0x0)
> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
> (0x0/0x0/0x0/0x0/0x0)
> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
> (0x1b/0x0/0x0/0x0/0x0)
> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
> line=0x1a, fline=0x0, cd=0x0, aux=0x0
> saa7133[0]: i2c scan: found device @ 0x96  [???]
> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
> Playback Volume, skipped
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> Playback Volume, skipped
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> Volume, skipped
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
> Playback Volume, skipped
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> Playback Switch, skipped
> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> Switch, skipped
> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
> tda8290 1-004b: setting tuner address to 61
> tda8290 1-004b: type set to tda8290+75a
> saa7133[0]: registered device video0 [v4l2]
> saa7133[0]: registered device vbi0
> saa7133[0]: registered device radio0
> DVB: registering new adapter (saa7133[0])
> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
> tda1004x: setting up plls for 48MHz sampling clock
> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
> NET: Registered protocol family 10
> lo: Disabled Privacy Extensions
> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
> tda1004x: timeout waiting for DSP ready
> tda1004x: found firmware revision 0 -- invalid
> tda1004x: trying to boot from eeprom
> tda1004x: timeout waiting for DSP ready
> device-mapper: multipath: version 1.0.5 loaded
> tda1004x: found firmware revision 0 -- invalid
> tda1004x: waiting for firmware upload...
> tda1004x: no firmware upload (timeout or file not found?)
> tda1004x: firmware upload failed
> loop: module loaded
> EXT3 FS on dm-0, internal journal
> kjournald starting.  Commit interval 5 seconds
> 
> And, when I run xawtv I got this.
> 
> [Ian@localhost ~]$ xawtv -hwscan
> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
> looking for available devices
> /dev/video0: OK                         [ -device /dev/video0 ]
>     type : v4l2
>     name : KWorld DVB-T 210
>     flags: overlay capture tuner 
> 
> [Ian@localhost ~]$ 
> 
> SO I ran xawtv again (with -remote -nodga) and saw that I could select
> Composite1 an a source.  Then I ran streamer, specifying Composite1
> and I captured an AVI file.  However, as you predicted, the images
> captured are all Black and White.  (We went through all the camera
> options to make sure it wasn't the camera set to BW!)
> 
> Definitely a long way forward.
> 
> Ian
> 
> PS - last time I tried, I am able to record audio through the mobo
> sound system.  I did not seemto be able to tune in the tuner yet.
> 
> 
> hermann pitton wrote: 
> > Hi Ian,
> > 
> > become root !
> > 

definitely a long way, not to talk about lost mails, but on module stuff
you must be root.

That is nothing new at all :) and took much too long.

Since I don't have neither the prior card nor the actual one,
it is time to go back to lists, others might be helpful as well.

Cheers,
Hermann




--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
use this card simply to capture video from the Composite input - the 
tuner is redundant.  With help from Hermann, I now am able to capture 
video - but the video is always Black and White.  I would much prefer it 
to be colour.

I would appreciate suggestions as to what to try next.

Ian


hermann pitton wrote:
> Hi Ian,
>
> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
>   
>> Hi Hermann,
>>
>> 1) I have changed my email "Reply-To" as emails were getting lost in
>> the system.
>>
>> 2) I searched for modprobe.conf and found one (only)
>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
>> that it was empty (apart from comments) and added the options line.  I
>> then saved it and copied it to /etc and ran depmod.  After rebooting,
>> this is what I get in dmesg (extract)
>>
>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
>> ppdev: user-space parallel port driver
>> Linux video capture interface: v2.00
>> saa7130/34: v4l2 driver version 0.2.14 loaded
>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
>> saa7133[0]: setting pci latency timer to 64
>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
>> mmio: 0xfebff800
>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
>> [card=114,insmod option]
>> saa7133[0]: board init: gpio is 100
>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
>> 0x4401
>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> ff ff
>> saa7133[0]: i2c scan: found device @ 0x10  [???]
>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
>> (0x14/0x15/0x16/0x17/0x0)
>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
>> (0x0/0x0/0x0/0x0/0x0)
>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
>> (0x1b/0x0/0x0/0x0/0x0)
>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
>> saa7133[0]: i2c scan: found device @ 0x96  [???]
>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
>> Playback Volume, skipped
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>> Playback Volume, skipped
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>> Volume, skipped
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
>> Playback Volume, skipped
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>> Playback Switch, skipped
>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>> Switch, skipped
>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
>> tda8290 1-004b: setting tuner address to 61
>> tda8290 1-004b: type set to tda8290+75a
>> saa7133[0]: registered device video0 [v4l2]
>> saa7133[0]: registered device vbi0
>> saa7133[0]: registered device radio0
>> DVB: registering new adapter (saa7133[0])
>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
>> tda1004x: setting up plls for 48MHz sampling clock
>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
>> NET: Registered protocol family 10
>> lo: Disabled Privacy Extensions
>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>> tda1004x: timeout waiting for DSP ready
>> tda1004x: found firmware revision 0 -- invalid
>> tda1004x: trying to boot from eeprom
>> tda1004x: timeout waiting for DSP ready
>> device-mapper: multipath: version 1.0.5 loaded
>> tda1004x: found firmware revision 0 -- invalid
>> tda1004x: waiting for firmware upload...
>> tda1004x: no firmware upload (timeout or file not found?)
>> tda1004x: firmware upload failed
>> loop: module loaded
>> EXT3 FS on dm-0, internal journal
>> kjournald starting.  Commit interval 5 seconds
>>
>> And, when I run xawtv I got this.
>>
>> [Ian@localhost ~]$ xawtv -hwscan
>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
>> looking for available devices
>> /dev/video0: OK                         [ -device /dev/video0 ]
>>     type : v4l2
>>     name : KWorld DVB-T 210
>>     flags: overlay capture tuner 
>>
>> [Ian@localhost ~]$ 
>>
>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
>> Composite1 an a source.  Then I ran streamer, specifying Composite1
>> and I captured an AVI file.  However, as you predicted, the images
>> captured are all Black and White.  (We went through all the camera
>> options to make sure it wasn't the camera set to BW!)
>>
>> Definitely a long way forward.
>>
>> Ian
>>
>> PS - last time I tried, I am able to record audio through the mobo
>> sound system.  I did not seemto be able to tune in the tuner yet.
>>
>>
>> hermann pitton wrote: 
>>     
>>> Hi Ian,
>>>
>>> become root !
>>>
>>>       
>
> definitely a long way, not to talk about lost mails, but on module stuff
> you must be root.
>
> That is nothing new at all :) and took much too long.
>
> Since I don't have neither the prior card nor the actual one,
> it is time to go back to lists, others might be helpful as well.
>
> Cheers,
> Hermann
>
>
>
>
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

I do have the (Windows) driver disk.

Is there any information on that that could assist with making the card 
card work under linux?

Ian

Ian Davidson wrote:
> I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
> use this card simply to capture video from the Composite input - the 
> tuner is redundant.  With help from Hermann, I now am able to capture 
> video - but the video is always Black and White.  I would much prefer 
> it to be colour.
>
> I would appreciate suggestions as to what to try next.
>
> Ian
>
>
> hermann pitton wrote:
>> Hi Ian,
>>
>> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
>>  
>>> Hi Hermann,
>>>
>>> 1) I have changed my email "Reply-To" as emails were getting lost in
>>> the system.
>>>
>>> 2) I searched for modprobe.conf and found one (only)
>>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
>>> that it was empty (apart from comments) and added the options line.  I
>>> then saved it and copied it to /etc and ran depmod.  After rebooting,
>>> this is what I get in dmesg (extract)
>>>
>>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
>>> ppdev: user-space parallel port driver
>>> Linux video capture interface: v2.00
>>> saa7130/34: v4l2 driver version 0.2.14 loaded
>>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
>>> saa7133[0]: setting pci latency timer to 64
>>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
>>> mmio: 0xfebff800
>>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
>>> [card=114,insmod option]
>>> saa7133[0]: board init: gpio is 100
>>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
>>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
>>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
>>> 0x4401
>>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>> ff ff
>>> saa7133[0]: i2c scan: found device @ 0x10  [???]
>>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
>>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
>>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
>>> (0x14/0x15/0x16/0x17/0x0)
>>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
>>> (0x0/0x0/0x0/0x0/0x0)
>>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
>>> (0x1b/0x0/0x0/0x0/0x0)
>>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
>>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
>>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
>>> saa7133[0]: i2c scan: found device @ 0x96  [???]
>>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
>>> Playback Volume, skipped
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>> Playback Volume, skipped
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>> Volume, skipped
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
>>> Playback Volume, skipped
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>> Playback Switch, skipped
>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>> Switch, skipped
>>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
>>> tda8290 1-004b: setting tuner address to 61
>>> tda8290 1-004b: type set to tda8290+75a
>>> saa7133[0]: registered device video0 [v4l2]
>>> saa7133[0]: registered device vbi0
>>> saa7133[0]: registered device radio0
>>> DVB: registering new adapter (saa7133[0])
>>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
>>> tda1004x: setting up plls for 48MHz sampling clock
>>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
>>> NET: Registered protocol family 10
>>> lo: Disabled Privacy Extensions
>>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>>> tda1004x: timeout waiting for DSP ready
>>> tda1004x: found firmware revision 0 -- invalid
>>> tda1004x: trying to boot from eeprom
>>> tda1004x: timeout waiting for DSP ready
>>> device-mapper: multipath: version 1.0.5 loaded
>>> tda1004x: found firmware revision 0 -- invalid
>>> tda1004x: waiting for firmware upload...
>>> tda1004x: no firmware upload (timeout or file not found?)
>>> tda1004x: firmware upload failed
>>> loop: module loaded
>>> EXT3 FS on dm-0, internal journal
>>> kjournald starting.  Commit interval 5 seconds
>>>
>>> And, when I run xawtv I got this.
>>>
>>> [Ian@localhost ~]$ xawtv -hwscan
>>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
>>> looking for available devices
>>> /dev/video0: OK                         [ -device /dev/video0 ]
>>>     type : v4l2
>>>     name : KWorld DVB-T 210
>>>     flags: overlay capture tuner
>>> [Ian@localhost ~]$
>>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
>>> Composite1 an a source.  Then I ran streamer, specifying Composite1
>>> and I captured an AVI file.  However, as you predicted, the images
>>> captured are all Black and White.  (We went through all the camera
>>> options to make sure it wasn't the camera set to BW!)
>>>
>>> Definitely a long way forward.
>>>
>>> Ian
>>>
>>> PS - last time I tried, I am able to record audio through the mobo
>>> sound system.  I did not seemto be able to tune in the tuner yet.
>>>
>>>
>>> hermann pitton wrote:    
>>>> Hi Ian,
>>>>
>>>> become root !
>>>>
>>>>       
>>
>> definitely a long way, not to talk about lost mails, but on module stuff
>> you must be root.
>>
>> That is nothing new at all :) and took much too long.
>>
>> Since I don't have neither the prior card nor the actual one,
>> it is time to go back to lists, others might be helpful as well.
>>
>> Cheers,
>> Hermann
>>
>>
>>
>>
>>
>>  
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>   
>

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Mittwoch, den 06.08.2008, 21:35 +0100 schrieb Ian Davidson:
> I do have the (Windows) driver disk.
> 
> Is there any information on that that could assist with making the card 
> card work under linux?
> 
> Ian

seems nobody else has this revision of the new Kworld 210SE yet.

You need firmware for the tda10046a in lib firmware for DVB-T.

You can find some long winded thread with timf on the linux-dvb ML,
where we tried to settle some issues for firmware loading and AGC
switching on the prior 210RF, but without full success yet. (June 2008)

Hopefully it does not hit you too.

For the composite input, you are mostly interested, the .inf files might
have some hints, but usually manufacturers keep what they previously
had.

If you get the v4l-dvb source from mercurial at linuxtv.org installed,
the composite input in saa7134-cards.c can be on vmux 0,1,2,3 or 4.

You can just add that much composite sections in the card's entry and
try them, or look for other cards offering them.

On a PAL card it was not seen yet, that none of them works, only NTSC
cards are know to might have a video enhancer to transform the signal to
s-video, which is at the higher vmuxes you see in saa7134-cards.c then.

The amux is either the LINE1 or the LINE2 pair, if not blocked by an
external gpio switched mux in between.

If you don't have analog audio out to the sound card, you depend on
saa7134-alsa and should read about it on the v4l wiki at linuxtv.org.

Good Luck,
Hermann


> Ian Davidson wrote:
> > I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
> > use this card simply to capture video from the Composite input - the 
> > tuner is redundant.  With help from Hermann, I now am able to capture 
> > video - but the video is always Black and White.  I would much prefer 
> > it to be colour.
> >
> > I would appreciate suggestions as to what to try next.
> >
> > Ian
> >
> >
> > hermann pitton wrote:
> >> Hi Ian,
> >>
> >> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
> >>  
> >>> Hi Hermann,
> >>>
> >>> 1) I have changed my email "Reply-To" as emails were getting lost in
> >>> the system.
> >>>
> >>> 2) I searched for modprobe.conf and found one (only)
> >>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
> >>> that it was empty (apart from comments) and added the options line.  I
> >>> then saved it and copied it to /etc and ran depmod.  After rebooting,
> >>> this is what I get in dmesg (extract)
> >>>
> >>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> >>> ppdev: user-space parallel port driver
> >>> Linux video capture interface: v2.00
> >>> saa7130/34: v4l2 driver version 0.2.14 loaded
> >>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
> >>> saa7133[0]: setting pci latency timer to 64
> >>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
> >>> mmio: 0xfebff800
> >>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
> >>> [card=114,insmod option]
> >>> saa7133[0]: board init: gpio is 100
> >>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
> >>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> >>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
> >>> 0x4401
> >>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>> ff ff
> >>> saa7133[0]: i2c scan: found device @ 0x10  [???]
> >>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
> >>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
> >>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
> >>> (0x14/0x15/0x16/0x17/0x0)
> >>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
> >>> (0x0/0x0/0x0/0x0/0x0)
> >>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
> >>> (0x1b/0x0/0x0/0x0/0x0)
> >>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
> >>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
> >>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
> >>> saa7133[0]: i2c scan: found device @ 0x96  [???]
> >>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
> >>> Playback Volume, skipped
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> >>> Playback Volume, skipped
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> >>> Volume, skipped
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
> >>> Playback Volume, skipped
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> >>> Playback Switch, skipped
> >>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> >>> Switch, skipped
> >>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
> >>> tda8290 1-004b: setting tuner address to 61
> >>> tda8290 1-004b: type set to tda8290+75a
> >>> saa7133[0]: registered device video0 [v4l2]
> >>> saa7133[0]: registered device vbi0
> >>> saa7133[0]: registered device radio0
> >>> DVB: registering new adapter (saa7133[0])
> >>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
> >>> tda1004x: setting up plls for 48MHz sampling clock
> >>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
> >>> NET: Registered protocol family 10
> >>> lo: Disabled Privacy Extensions
> >>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
> >>> tda1004x: timeout waiting for DSP ready
> >>> tda1004x: found firmware revision 0 -- invalid
> >>> tda1004x: trying to boot from eeprom
> >>> tda1004x: timeout waiting for DSP ready
> >>> device-mapper: multipath: version 1.0.5 loaded
> >>> tda1004x: found firmware revision 0 -- invalid
> >>> tda1004x: waiting for firmware upload...
> >>> tda1004x: no firmware upload (timeout or file not found?)
> >>> tda1004x: firmware upload failed
> >>> loop: module loaded
> >>> EXT3 FS on dm-0, internal journal
> >>> kjournald starting.  Commit interval 5 seconds
> >>>
> >>> And, when I run xawtv I got this.
> >>>
> >>> [Ian@localhost ~]$ xawtv -hwscan
> >>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
> >>> looking for available devices
> >>> /dev/video0: OK                         [ -device /dev/video0 ]
> >>>     type : v4l2
> >>>     name : KWorld DVB-T 210
> >>>     flags: overlay capture tuner
> >>> [Ian@localhost ~]$
> >>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
> >>> Composite1 an a source.  Then I ran streamer, specifying Composite1
> >>> and I captured an AVI file.  However, as you predicted, the images
> >>> captured are all Black and White.  (We went through all the camera
> >>> options to make sure it wasn't the camera set to BW!)
> >>>
> >>> Definitely a long way forward.
> >>>
> >>> Ian
> >>>
> >>> PS - last time I tried, I am able to record audio through the mobo
> >>> sound system.  I did not seemto be able to tune in the tuner yet.
> >>>
> >>>
> >>> hermann pitton wrote:    
> >>>> Hi Ian,
> >>>>
> >>>> become root !
> >>>>
> >>>>       
> >>
> >> definitely a long way, not to talk about lost mails, but on module stuff
> >> you must be root.
> >>
> >> That is nothing new at all :) and took much too long.
> >>
> >> Since I don't have neither the prior card nor the actual one,
> >> it is time to go back to lists, others might be helpful as well.
> >>
> >> Cheers,
> >> Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

Hi Hermann,

I am sorry for being slow - but I have some questions.

1) When you say "you need firmware ...for DVB-T", would that only be if 
I want to use the tuner?

2) I have the mercurial and I can see the details in saa7134-cards.c and 
I have seen the entry for the 'close match'.  I appreciate that, since 
it was not auto-detected, the match may not be close enough.  I can see 
the vmux entry there.  Presumably, 'vmux' is 'Video Multiplex' and 
'amux' is 'Audio Multiplex' (or something similar) - but what would I 
change to try different values.  Currently, the file saa7134-cards.c is 
in the folder I downloaded to - would linux know that it was supposed to 
look there?  Do I need to put the settings somewhere else (such as the 
modeprobe.conf?)

3) Incidentally, I happened to notice that just after boot, I get some 
messages that there is a problem with modprobe. The messages were wiped 
off the screen before I could record them reliably.  Is there some way 
of seeing what those messages were, once linux is up and running.

Ian

hermann pitton wrote:
> Hi Ian,
>
> Am Mittwoch, den 06.08.2008, 21:35 +0100 schrieb Ian Davidson:
>   
>> I do have the (Windows) driver disk.
>>
>> Is there any information on that that could assist with making the card 
>> card work under linux?
>>
>> Ian
>>     
>
> seems nobody else has this revision of the new Kworld 210SE yet.
>
> You need firmware for the tda10046a in lib firmware for DVB-T.
>
> You can find some long winded thread with timf on the linux-dvb ML,
> where we tried to settle some issues for firmware loading and AGC
> switching on the prior 210RF, but without full success yet. (June 2008)
>
> Hopefully it does not hit you too.
>
> For the composite input, you are mostly interested, the .inf files might
> have some hints, but usually manufacturers keep what they previously
> had.
>
> If you get the v4l-dvb source from mercurial at linuxtv.org installed,
> the composite input in saa7134-cards.c can be on vmux 0,1,2,3 or 4.
>
> You can just add that much composite sections in the card's entry and
> try them, or look for other cards offering them.
>
> On a PAL card it was not seen yet, that none of them works, only NTSC
> cards are know to might have a video enhancer to transform the signal to
> s-video, which is at the higher vmuxes you see in saa7134-cards.c then.
>
> The amux is either the LINE1 or the LINE2 pair, if not blocked by an
> external gpio switched mux in between.
>
> If you don't have analog audio out to the sound card, you depend on
> saa7134-alsa and should read about it on the v4l wiki at linuxtv.org.
>
> Good Luck,
> Hermann
>
>
>   
>> Ian Davidson wrote:
>>     
>>> I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
>>> use this card simply to capture video from the Composite input - the 
>>> tuner is redundant.  With help from Hermann, I now am able to capture 
>>> video - but the video is always Black and White.  I would much prefer 
>>> it to be colour.
>>>
>>> I would appreciate suggestions as to what to try next.
>>>
>>> Ian
>>>
>>>
>>> hermann pitton wrote:
>>>       
>>>> Hi Ian,
>>>>
>>>> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
>>>>  
>>>>         
>>>>> Hi Hermann,
>>>>>
>>>>> 1) I have changed my email "Reply-To" as emails were getting lost in
>>>>> the system.
>>>>>
>>>>> 2) I searched for modprobe.conf and found one (only)
>>>>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
>>>>> that it was empty (apart from comments) and added the options line.  I
>>>>> then saved it and copied it to /etc and ran depmod.  After rebooting,
>>>>> this is what I get in dmesg (extract)
>>>>>
>>>>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
>>>>> ppdev: user-space parallel port driver
>>>>> Linux video capture interface: v2.00
>>>>> saa7130/34: v4l2 driver version 0.2.14 loaded
>>>>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
>>>>> saa7133[0]: setting pci latency timer to 64
>>>>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
>>>>> mmio: 0xfebff800
>>>>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
>>>>> [card=114,insmod option]
>>>>> saa7133[0]: board init: gpio is 100
>>>>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
>>>>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
>>>>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
>>>>> 0x4401
>>>>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>> ff ff
>>>>> saa7133[0]: i2c scan: found device @ 0x10  [???]
>>>>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
>>>>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
>>>>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
>>>>> (0x14/0x15/0x16/0x17/0x0)
>>>>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
>>>>> (0x0/0x0/0x0/0x0/0x0)
>>>>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
>>>>> (0x1b/0x0/0x0/0x0/0x0)
>>>>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
>>>>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
>>>>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
>>>>> saa7133[0]: i2c scan: found device @ 0x96  [???]
>>>>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
>>>>> Playback Volume, skipped
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>>>> Playback Volume, skipped
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>>>> Volume, skipped
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
>>>>> Playback Volume, skipped
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>>>> Playback Switch, skipped
>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>>>> Switch, skipped
>>>>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
>>>>> tda8290 1-004b: setting tuner address to 61
>>>>> tda8290 1-004b: type set to tda8290+75a
>>>>> saa7133[0]: registered device video0 [v4l2]
>>>>> saa7133[0]: registered device vbi0
>>>>> saa7133[0]: registered device radio0
>>>>> DVB: registering new adapter (saa7133[0])
>>>>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
>>>>> tda1004x: setting up plls for 48MHz sampling clock
>>>>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
>>>>> NET: Registered protocol family 10
>>>>> lo: Disabled Privacy Extensions
>>>>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>>>>> tda1004x: timeout waiting for DSP ready
>>>>> tda1004x: found firmware revision 0 -- invalid
>>>>> tda1004x: trying to boot from eeprom
>>>>> tda1004x: timeout waiting for DSP ready
>>>>> device-mapper: multipath: version 1.0.5 loaded
>>>>> tda1004x: found firmware revision 0 -- invalid
>>>>> tda1004x: waiting for firmware upload...
>>>>> tda1004x: no firmware upload (timeout or file not found?)
>>>>> tda1004x: firmware upload failed
>>>>> loop: module loaded
>>>>> EXT3 FS on dm-0, internal journal
>>>>> kjournald starting.  Commit interval 5 seconds
>>>>>
>>>>> And, when I run xawtv I got this.
>>>>>
>>>>> [Ian@localhost ~]$ xawtv -hwscan
>>>>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
>>>>> looking for available devices
>>>>> /dev/video0: OK                         [ -device /dev/video0 ]
>>>>>     type : v4l2
>>>>>     name : KWorld DVB-T 210
>>>>>     flags: overlay capture tuner
>>>>> [Ian@localhost ~]$
>>>>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
>>>>> Composite1 an a source.  Then I ran streamer, specifying Composite1
>>>>> and I captured an AVI file.  However, as you predicted, the images
>>>>> captured are all Black and White.  (We went through all the camera
>>>>> options to make sure it wasn't the camera set to BW!)
>>>>>
>>>>> Definitely a long way forward.
>>>>>
>>>>> Ian
>>>>>
>>>>> PS - last time I tried, I am able to record audio through the mobo
>>>>> sound system.  I did not seemto be able to tune in the tuner yet.
>>>>>
>>>>>
>>>>> hermann pitton wrote:    
>>>>>           
>>>>>> Hi Ian,
>>>>>>
>>>>>> become root !
>>>>>>
>>>>>>       
>>>>>>             
>>>> definitely a long way, not to talk about lost mails, but on module stuff
>>>> you must be root.
>>>>
>>>> That is nothing new at all :) and took much too long.
>>>>
>>>> Since I don't have neither the prior card nor the actual one,
>>>> it is time to go back to lists, others might be helpful as well.
>>>>
>>>> Cheers,
>>>> Hermann
>>>>         
>
>
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Donnerstag, den 07.08.2008, 22:50 +0100 schrieb Ian Davidson:
> Hi Hermann,
> 
> I am sorry for being slow - but I have some questions.

no problem, but it is unfortunately time we have to waste all and
sometimes it is better someone more used to test some new cards tries to
give the status under current conditions, but who can buy all the new
cards, only to shuffle them to a pile, since already no free PCI slots
since long.

That stuff is still under full production, but might vanish soon in the
future at all, since PCI is outdated and on new machines you hardly find
a slot left.

> 1) When you say "you need firmware ...for DVB-T", would that only be if 
> I want to use the tuner?

It even means you need firmware only, if you want the frontend being
usable for DVB-T. You don't need it for analog TV tuning.

> 2) I have the mercurial and I can see the details in saa7134-cards.c and 
> I have seen the entry for the 'close match'.  I appreciate that, since 
> it was not auto-detected, the match may not be close enough.  I can see 
> the vmux entry there.  Presumably, 'vmux' is 'Video Multiplex' and 
> 'amux' is 'Audio Multiplex' (or something similar) - but what would I 
> change to try different values.  Currently, the file saa7134-cards.c is 
> in the folder I downloaded to - would linux know that it was supposed to 
> look there?  Do I need to put the settings somewhere else (such as the 
> modeprobe.conf?)

Yes, that is exactly latest linux in this case.

Changing the code is still prior to modprobe options,
but we discussed once to get the complete cards configurations into
userspace and almost all agreed.

On top of v4l-dvb try
"make"
become root
"make rmmod"
"make rminstall"
"make install"
"modprobe -v saa7134"

If you still have black and white only on the composite input,
you now change the code and save it, simplest is to add all 5 possible
composite inputs from vmux=0 to four to the card's entry.

Now you just do the same for
"make"
"make rmmod"
"make install"
"modprobe -v saa7134"

That is still some major part of what it is all about.
Change the code if needed.

> 3) Incidentally, I happened to notice that just after boot, I get some 
> messages that there is a problem with modprobe. The messages were wiped 
> off the screen before I could record them reliably.  Is there some way 
> of seeing what those messages were, once linux is up and running.

Such modprobe related messages you always find later with "dmesg",
since they come fairly late and all logging and udev is already up.

Happy hacking,

Hermann

> Ian
> 
> hermann pitton wrote:
> > Hi Ian,
> >
> > Am Mittwoch, den 06.08.2008, 21:35 +0100 schrieb Ian Davidson:
> >   
> >> I do have the (Windows) driver disk.
> >>
> >> Is there any information on that that could assist with making the card 
> >> card work under linux?
> >>
> >> Ian
> >>     
> >
> > seems nobody else has this revision of the new Kworld 210SE yet.
> >
> > You need firmware for the tda10046a in lib firmware for DVB-T.
> >
> > You can find some long winded thread with timf on the linux-dvb ML,
> > where we tried to settle some issues for firmware loading and AGC
> > switching on the prior 210RF, but without full success yet. (June 2008)
> >
> > Hopefully it does not hit you too.
> >
> > For the composite input, you are mostly interested, the .inf files might
> > have some hints, but usually manufacturers keep what they previously
> > had.
> >
> > If you get the v4l-dvb source from mercurial at linuxtv.org installed,
> > the composite input in saa7134-cards.c can be on vmux 0,1,2,3 or 4.
> >
> > You can just add that much composite sections in the card's entry and
> > try them, or look for other cards offering them.
> >
> > On a PAL card it was not seen yet, that none of them works, only NTSC
> > cards are know to might have a video enhancer to transform the signal to
> > s-video, which is at the higher vmuxes you see in saa7134-cards.c then.
> >
> > The amux is either the LINE1 or the LINE2 pair, if not blocked by an
> > external gpio switched mux in between.
> >
> > If you don't have analog audio out to the sound card, you depend on
> > saa7134-alsa and should read about it on the v4l wiki at linuxtv.org.
> >
> > Good Luck,
> > Hermann
> >
> >
> >   
> >> Ian Davidson wrote:
> >>     
> >>> I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
> >>> use this card simply to capture video from the Composite input - the 
> >>> tuner is redundant.  With help from Hermann, I now am able to capture 
> >>> video - but the video is always Black and White.  I would much prefer 
> >>> it to be colour.
> >>>
> >>> I would appreciate suggestions as to what to try next.
> >>>
> >>> Ian
> >>>
> >>>
> >>> hermann pitton wrote:
> >>>       
> >>>> Hi Ian,
> >>>>
> >>>> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
> >>>>  
> >>>>         
> >>>>> Hi Hermann,
> >>>>>
> >>>>> 1) I have changed my email "Reply-To" as emails were getting lost in
> >>>>> the system.
> >>>>>
> >>>>> 2) I searched for modprobe.conf and found one (only)
> >>>>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
> >>>>> that it was empty (apart from comments) and added the options line.  I
> >>>>> then saved it and copied it to /etc and ran depmod.  After rebooting,
> >>>>> this is what I get in dmesg (extract)
> >>>>>
> >>>>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> >>>>> ppdev: user-space parallel port driver
> >>>>> Linux video capture interface: v2.00
> >>>>> saa7130/34: v4l2 driver version 0.2.14 loaded
> >>>>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
> >>>>> saa7133[0]: setting pci latency timer to 64
> >>>>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
> >>>>> mmio: 0xfebff800
> >>>>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
> >>>>> [card=114,insmod option]
> >>>>> saa7133[0]: board init: gpio is 100
> >>>>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
> >>>>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> >>>>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
> >>>>> 0x4401
> >>>>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >>>>> ff ff
> >>>>> saa7133[0]: i2c scan: found device @ 0x10  [???]
> >>>>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
> >>>>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
> >>>>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
> >>>>> (0x14/0x15/0x16/0x17/0x0)
> >>>>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
> >>>>> (0x0/0x0/0x0/0x0/0x0)
> >>>>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
> >>>>> (0x1b/0x0/0x0/0x0/0x0)
> >>>>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
> >>>>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
> >>>>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
> >>>>> saa7133[0]: i2c scan: found device @ 0x96  [???]
> >>>>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
> >>>>> Playback Volume, skipped
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> >>>>> Playback Volume, skipped
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> >>>>> Volume, skipped
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
> >>>>> Playback Volume, skipped
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
> >>>>> Playback Switch, skipped
> >>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
> >>>>> Switch, skipped
> >>>>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
> >>>>> tda8290 1-004b: setting tuner address to 61
> >>>>> tda8290 1-004b: type set to tda8290+75a
> >>>>> saa7133[0]: registered device video0 [v4l2]
> >>>>> saa7133[0]: registered device vbi0
> >>>>> saa7133[0]: registered device radio0
> >>>>> DVB: registering new adapter (saa7133[0])
> >>>>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
> >>>>> tda1004x: setting up plls for 48MHz sampling clock
> >>>>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
> >>>>> NET: Registered protocol family 10
> >>>>> lo: Disabled Privacy Extensions
> >>>>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
> >>>>> tda1004x: timeout waiting for DSP ready
> >>>>> tda1004x: found firmware revision 0 -- invalid
> >>>>> tda1004x: trying to boot from eeprom
> >>>>> tda1004x: timeout waiting for DSP ready
> >>>>> device-mapper: multipath: version 1.0.5 loaded
> >>>>> tda1004x: found firmware revision 0 -- invalid
> >>>>> tda1004x: waiting for firmware upload...
> >>>>> tda1004x: no firmware upload (timeout or file not found?)
> >>>>> tda1004x: firmware upload failed
> >>>>> loop: module loaded
> >>>>> EXT3 FS on dm-0, internal journal
> >>>>> kjournald starting.  Commit interval 5 seconds
> >>>>>
> >>>>> And, when I run xawtv I got this.
> >>>>>
> >>>>> [Ian@localhost ~]$ xawtv -hwscan
> >>>>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
> >>>>> looking for available devices
> >>>>> /dev/video0: OK                         [ -device /dev/video0 ]
> >>>>>     type : v4l2
> >>>>>     name : KWorld DVB-T 210
> >>>>>     flags: overlay capture tuner
> >>>>> [Ian@localhost ~]$
> >>>>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
> >>>>> Composite1 an a source.  Then I ran streamer, specifying Composite1
> >>>>> and I captured an AVI file.  However, as you predicted, the images
> >>>>> captured are all Black and White.  (We went through all the camera
> >>>>> options to make sure it wasn't the camera set to BW!)
> >>>>>
> >>>>> Definitely a long way forward.
> >>>>>
> >>>>> Ian
> >>>>>
> >>>>> PS - last time I tried, I am able to record audio through the mobo
> >>>>> sound system.  I did not seemto be able to tune in the tuner yet.
> >>>>>
> >>>>>
> >>>>> hermann pitton wrote:    
> >>>>>           
> >>>>>> Hi Ian,
> >>>>>>
> >>>>>> become root !
> >>>>>>
> >>>>>>       
> >>>>>>             
> >>>> definitely a long way, not to talk about lost mails, but on module stuff
> >>>> you must be root.
> >>>>
> >>>> That is nothing new at all :) and took much too long.
> >>>>
> >>>> Since I don't have neither the prior card nor the actual one,
> >>>> it is time to go back to lists, others might be helpful as well.
> >>>>
> >>>> Cheers,
> >>>> Hermann
> >>>>         


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

Hi Hermann,

I got errors in the 'make' (see below).  Presumably, there is something 
else I need to install/download?

Ian

[Ian@localhost ~]$ cd v4l-dvb/
[Ian@localhost v4l-dvb]$ make
make -C /home/Ian/v4l-dvb/v4l
make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
No version yet, using 2.6.25.11-97.fc9.i686
make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
scripts/make_makefile.pl
Updating/Creating .config
Preparing to compile for kernel version 2.6.25
File not found: /lib/modules/2.6.25.11-97.fc9.i686/build/.config at 
./scripts/make_kconfig.pl line 32, <IN> line 4.
make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
Updating/Creating .config
Preparing to compile for kernel version 2.6.25
File not found: /lib/modules/2.6.25.11-97.fc9.i686/build/.config at 
./scripts/make_kconfig.pl line 32, <IN> line 4.
make[1]: *** No rule to make target `.myconfig', needed by 
`config-compat.h'.  Stop.
make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
make: *** [all] Error 2
[Ian@localhost v4l-dvb]$

hermann pitton wrote:
> Hi Ian,
>
> Am Donnerstag, den 07.08.2008, 22:50 +0100 schrieb Ian Davidson:
>   
>> Hi Hermann,
>>
>> I am sorry for being slow - but I have some questions.
>>     
>
> no problem, but it is unfortunately time we have to waste all and
> sometimes it is better someone more used to test some new cards tries to
> give the status under current conditions, but who can buy all the new
> cards, only to shuffle them to a pile, since already no free PCI slots
> since long.
>
> That stuff is still under full production, but might vanish soon in the
> future at all, since PCI is outdated and on new machines you hardly find
> a slot left.
>
>   
>> 1) When you say "you need firmware ...for DVB-T", would that only be if 
>> I want to use the tuner?
>>     
>
> It even means you need firmware only, if you want the frontend being
> usable for DVB-T. You don't need it for analog TV tuning.
>
>   
>> 2) I have the mercurial and I can see the details in saa7134-cards.c and 
>> I have seen the entry for the 'close match'.  I appreciate that, since 
>> it was not auto-detected, the match may not be close enough.  I can see 
>> the vmux entry there.  Presumably, 'vmux' is 'Video Multiplex' and 
>> 'amux' is 'Audio Multiplex' (or something similar) - but what would I 
>> change to try different values.  Currently, the file saa7134-cards.c is 
>> in the folder I downloaded to - would linux know that it was supposed to 
>> look there?  Do I need to put the settings somewhere else (such as the 
>> modeprobe.conf?)
>>     
>
> Yes, that is exactly latest linux in this case.
>
> Changing the code is still prior to modprobe options,
> but we discussed once to get the complete cards configurations into
> userspace and almost all agreed.
>
> On top of v4l-dvb try
> "make"
> become root
> "make rmmod"
> "make rminstall"
> "make install"
> "modprobe -v saa7134"
>
> If you still have black and white only on the composite input,
> you now change the code and save it, simplest is to add all 5 possible
> composite inputs from vmux=0 to four to the card's entry.
>
> Now you just do the same for
> "make"
> "make rmmod"
> "make install"
> "modprobe -v saa7134"
>
> That is still some major part of what it is all about.
> Change the code if needed.
>
>   
>> 3) Incidentally, I happened to notice that just after boot, I get some 
>> messages that there is a problem with modprobe. The messages were wiped 
>> off the screen before I could record them reliably.  Is there some way 
>> of seeing what those messages were, once linux is up and running.
>>     
>
> Such modprobe related messages you always find later with "dmesg",
> since they come fairly late and all logging and udev is already up.
>
> Happy hacking,
>
> Hermann
>
>   
>> Ian
>>
>> hermann pitton wrote:
>>     
>>> Hi Ian,
>>>
>>> Am Mittwoch, den 06.08.2008, 21:35 +0100 schrieb Ian Davidson:
>>>   
>>>       
>>>> I do have the (Windows) driver disk.
>>>>
>>>> Is there any information on that that could assist with making the card 
>>>> card work under linux?
>>>>
>>>> Ian
>>>>     
>>>>         
>>> seems nobody else has this revision of the new Kworld 210SE yet.
>>>
>>> You need firmware for the tda10046a in lib firmware for DVB-T.
>>>
>>> You can find some long winded thread with timf on the linux-dvb ML,
>>> where we tried to settle some issues for firmware loading and AGC
>>> switching on the prior 210RF, but without full success yet. (June 2008)
>>>
>>> Hopefully it does not hit you too.
>>>
>>> For the composite input, you are mostly interested, the .inf files might
>>> have some hints, but usually manufacturers keep what they previously
>>> had.
>>>
>>> If you get the v4l-dvb source from mercurial at linuxtv.org installed,
>>> the composite input in saa7134-cards.c can be on vmux 0,1,2,3 or 4.
>>>
>>> You can just add that much composite sections in the card's entry and
>>> try them, or look for other cards offering them.
>>>
>>> On a PAL card it was not seen yet, that none of them works, only NTSC
>>> cards are know to might have a video enhancer to transform the signal to
>>> s-video, which is at the higher vmuxes you see in saa7134-cards.c then.
>>>
>>> The amux is either the LINE1 or the LINE2 pair, if not blocked by an
>>> external gpio switched mux in between.
>>>
>>> If you don't have analog audio out to the sound card, you depend on
>>> saa7134-alsa and should read about it on the v4l wiki at linuxtv.org.
>>>
>>> Good Luck,
>>> Hermann
>>>
>>>
>>>   
>>>       
>>>> Ian Davidson wrote:
>>>>     
>>>>         
>>>>> I have a KWorld DVB-T 210SE card which is not autodetected.  I want to 
>>>>> use this card simply to capture video from the Composite input - the 
>>>>> tuner is redundant.  With help from Hermann, I now am able to capture 
>>>>> video - but the video is always Black and White.  I would much prefer 
>>>>> it to be colour.
>>>>>
>>>>> I would appreciate suggestions as to what to try next.
>>>>>
>>>>> Ian
>>>>>
>>>>>
>>>>> hermann pitton wrote:
>>>>>       
>>>>>           
>>>>>> Hi Ian,
>>>>>>
>>>>>> Am Sonntag, den 03.08.2008, 17:05 +0100 schrieb Ian Davidson:
>>>>>>  
>>>>>>         
>>>>>>             
>>>>>>> Hi Hermann,
>>>>>>>
>>>>>>> 1) I have changed my email "Reply-To" as emails were getting lost in
>>>>>>> the system.
>>>>>>>
>>>>>>> 2) I searched for modprobe.conf and found one (only)
>>>>>>> in /usr/share/logwatch/default.conf/services.  I opened it and saw
>>>>>>> that it was empty (apart from comments) and added the options line.  I
>>>>>>> then saved it and copied it to /etc and ran depmod.  After rebooting,
>>>>>>> this is what I get in dmesg (extract)
>>>>>>>
>>>>>>> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
>>>>>>> ppdev: user-space parallel port driver
>>>>>>> Linux video capture interface: v2.00
>>>>>>> saa7130/34: v4l2 driver version 0.2.14 loaded
>>>>>>> ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 18 (level, low) -> IRQ 18
>>>>>>> saa7133[0]: setting pci latency timer to 64
>>>>>>> saa7133[0]: found at 0000:04:02.0, rev: 209, irq: 18, latency: 64,
>>>>>>> mmio: 0xfebff800
>>>>>>> saa7133[0]: subsystem: 17de:7253, board: KWorld DVB-T 210
>>>>>>> [card=114,insmod option]
>>>>>>> saa7133[0]: board init: gpio is 100
>>>>>>> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
>>>>>>> PCI: Setting latency timer of device 0000:00:1b.0 to 64
>>>>>>> ALSA sound/pci/hda/hda_intel.c:1810: chipset global capabilities =
>>>>>>> 0x4401
>>>>>>> saa7133[0]: i2c eeprom 00: de 17 53 72 ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>>>>>>> ff ff
>>>>>>> saa7133[0]: i2c scan: found device @ 0x10  [???]
>>>>>>> ALSA sound/pci/hda/hda_intel.c:749: codec_mask = 0x1
>>>>>>> hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
>>>>>>> ALSA sound/pci/hda/hda_codec.c:2857: autoconfig: line_outs=4
>>>>>>> (0x14/0x15/0x16/0x17/0x0)
>>>>>>> ALSA sound/pci/hda/hda_codec.c:2861:    speaker_outs=0
>>>>>>> (0x0/0x0/0x0/0x0/0x0)
>>>>>>> ALSA sound/pci/hda/hda_codec.c:2865:    hp_outs=1
>>>>>>> (0x1b/0x0/0x0/0x0/0x0)
>>>>>>> ALSA sound/pci/hda/hda_codec.c:2866:    mono: mono_out=0x0
>>>>>>> ALSA sound/pci/hda/hda_codec.c:2874:    inputs: mic=0x18, fmic=0x19,
>>>>>>> line=0x1a, fline=0x0, cd=0x0, aux=0x0
>>>>>>> saa7133[0]: i2c scan: found device @ 0x96  [???]
>>>>>>> saa7133[0]: i2c scan: found device @ 0xa0  [eeprom]
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Headphone
>>>>>>> Playback Volume, skipped
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>>>>>> Playback Volume, skipped
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>>>>>> Volume, skipped
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Line-Out
>>>>>>> Playback Volume, skipped
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Speaker
>>>>>>> Playback Switch, skipped
>>>>>>> ALSA sound/pci/hda/hda_codec.c:1073: Cannot find slave Mono Playback
>>>>>>> Switch, skipped
>>>>>>> tuner' 1-004b: chip found @ 0x96 (saa7133[0])
>>>>>>> tda8290 1-004b: setting tuner address to 61
>>>>>>> tda8290 1-004b: type set to tda8290+75a
>>>>>>> saa7133[0]: registered device video0 [v4l2]
>>>>>>> saa7133[0]: registered device vbi0
>>>>>>> saa7133[0]: registered device radio0
>>>>>>> DVB: registering new adapter (saa7133[0])
>>>>>>> DVB: registering frontend 0 (Philips TDA10046H DVB-T)...
>>>>>>> tda1004x: setting up plls for 48MHz sampling clock
>>>>>>> SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
>>>>>>> NET: Registered protocol family 10
>>>>>>> lo: Disabled Privacy Extensions
>>>>>>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>>>>>>> tda1004x: timeout waiting for DSP ready
>>>>>>> tda1004x: found firmware revision 0 -- invalid
>>>>>>> tda1004x: trying to boot from eeprom
>>>>>>> tda1004x: timeout waiting for DSP ready
>>>>>>> device-mapper: multipath: version 1.0.5 loaded
>>>>>>> tda1004x: found firmware revision 0 -- invalid
>>>>>>> tda1004x: waiting for firmware upload...
>>>>>>> tda1004x: no firmware upload (timeout or file not found?)
>>>>>>> tda1004x: firmware upload failed
>>>>>>> loop: module loaded
>>>>>>> EXT3 FS on dm-0, internal journal
>>>>>>> kjournald starting.  Commit interval 5 seconds
>>>>>>>
>>>>>>> And, when I run xawtv I got this.
>>>>>>>
>>>>>>> [Ian@localhost ~]$ xawtv -hwscan
>>>>>>> This is xawtv-3.95, running on Linux/i686 (2.6.25.11-97.fc9.i686)
>>>>>>> looking for available devices
>>>>>>> /dev/video0: OK                         [ -device /dev/video0 ]
>>>>>>>     type : v4l2
>>>>>>>     name : KWorld DVB-T 210
>>>>>>>     flags: overlay capture tuner
>>>>>>> [Ian@localhost ~]$
>>>>>>> SO I ran xawtv again (with -remote -nodga) and saw that I could select
>>>>>>> Composite1 an a source.  Then I ran streamer, specifying Composite1
>>>>>>> and I captured an AVI file.  However, as you predicted, the images
>>>>>>> captured are all Black and White.  (We went through all the camera
>>>>>>> options to make sure it wasn't the camera set to BW!)
>>>>>>>
>>>>>>> Definitely a long way forward.
>>>>>>>
>>>>>>> Ian
>>>>>>>
>>>>>>> PS - last time I tried, I am able to record audio through the mobo
>>>>>>> sound system.  I did not seemto be able to tune in the tuner yet.
>>>>>>>
>>>>>>>
>>>>>>> hermann pitton wrote:    
>>>>>>>           
>>>>>>>               
>>>>>>>> Hi Ian,
>>>>>>>>
>>>>>>>> become root !
>>>>>>>>
>>>>>>>>       
>>>>>>>>             
>>>>>>>>                 
>>>>>> definitely a long way, not to talk about lost mails, but on module stuff
>>>>>> you must be root.
>>>>>>
>>>>>> That is nothing new at all :) and took much too long.
>>>>>>
>>>>>> Since I don't have neither the prior card nor the actual one,
>>>>>> it is time to go back to lists, others might be helpful as well.
>>>>>>
>>>>>> Cheers,
>>>>>> Hermann
>>>>>>         
>>>>>>             
>
>
>
>  
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Freitag, den 08.08.2008, 20:02 +0100 schrieb Ian Davidson:
> Hi Hermann,
> 
> I got errors in the 'make' (see below).  Presumably, there is something 
> else I need to install/download?
> 
> Ian
> 
> [Ian@localhost ~]$ cd v4l-dvb/
> [Ian@localhost v4l-dvb]$ make
> make -C /home/Ian/v4l-dvb/v4l
> make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
> No version yet, using 2.6.25.11-97.fc9.i686
> make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
> make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
> scripts/make_makefile.pl
> Updating/Creating .config
> Preparing to compile for kernel version 2.6.25
> File not found: /lib/modules/2.6.25.11-97.fc9.i686/build/.config at 
> ./scripts/make_kconfig.pl line 32, <IN> line 4.
> make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
> make[1]: Entering directory `/home/Ian/v4l-dvb/v4l'
> Updating/Creating .config
> Preparing to compile for kernel version 2.6.25
> File not found: /lib/modules/2.6.25.11-97.fc9.i686/build/.config at 
> ./scripts/make_kconfig.pl line 32, <IN> line 4.
> make[1]: *** No rule to make target `.myconfig', needed by 
> `config-compat.h'.  Stop.
> make[1]: Leaving directory `/home/Ian/v4l-dvb/v4l'
> make: *** [all] Error 2
> [Ian@localhost v4l-dvb]$
> 

yes, you need at least the exported object tree to compile or configured
custom kernel source if not on a vanilla kernel.

Try "yum install kernel-devel".

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

Hi Hermann,

I thought I had had success - but no.

I did the makes as you described - no difference, so I made the changes 
to the code.
I left Composite1 as vmux=3 and assigned Composite and Composite 2-4 to 
the other vmux values and 'maked' again.  When I went into xawtv, I 
thought that I saw colour (true colour, not false colour) - but next 
time I looked, it saw only Black and White.  The changes certainly were 
applied correctly, because I could choose from all 5 Composite choices - 
but only Composite1 showed me any picture.

What is gpio? Does it have anything to do with the colour?

Below is some extracts from the .inf file on the Windows driver disk.  I 
see (from the third line) that my card is "3xHybridQ" - based on the 4 
bytes being reported from the eeprom .  Based on that, certain values 
would be loaded into the registry - but I have no idea what those values 
represent.  I don't know if it is of any help.

You will get some peace from me for a week.  I will be away on business.

Ian



%Hybrid.DeviceDescSilicon% 
=3xHybridP.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_735117DE

%Hybrid.DeviceDescSilicon% 
=3xHybridO.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_735217DE

%Hybrid.DeviceDescSilicon% 
=3xHybridQ.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_725317DE


[3xHybridO.AddReg]

HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x18,0x00,0x00,0x00 ; 
Tuner ID

HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
Tuner slave addr.

HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x00,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data5",0x00010001,0xFF,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x55,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x55,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x55,0x00,0x00,0x00 ; 
FM radio mode.

HKR, "AudioDecoder", "CVBS Channel",0x00010001,3

HKR, "AudioDecoder", "SVHS Channel",0x00010001,3

HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1


[3xHybridP.AddReg]

HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x18,0x00,0x00,0x00 ; 
Tuner ID

HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
Tuner slave addr.

HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x00,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x03,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x21,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x00,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x00,0x00,0x00,0x00 ; 
FM radio mode.

HKR, "AudioDecoder", "CVBS Channel",0x00010001,3

HKR, "AudioDecoder", "SVHS Channel",0x00010001,3

HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1


[3xHybridQ.AddReg]

HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x21,0x00,0x00,0x00 ; 
Tuner ID

HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
Tuner slave addr.

HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x96,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x10,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x03,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x32,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x15,0x00,0x00,0x00 ; 
Tuner IF PLL slave addr.

HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x50,0x00,0x00,0x00 ; 
FM radio mode.

HKR, "AudioDecoder", "CVBS Channel",0x00010001,3

HKR, "AudioDecoder", "SVHS Channel",0x00010001,3

HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1



--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Samstag, den 09.08.2008, 11:54 +0100 schrieb Ian Davidson: 
> Hi Hermann,
> 
> I thought I had had success - but no.
> 
> I did the makes as you described - no difference, so I made the changes 
> to the code.
> I left Composite1 as vmux=3 and assigned Composite and Composite 2-4 to 
> the other vmux values and 'maked' again.  When I went into xawtv, I 
> thought that I saw colour (true colour, not false colour) - but next 
> time I looked, it saw only Black and White.  The changes certainly were 
> applied correctly, because I could choose from all 5 Composite choices - 
> but only Composite1 showed me any picture.

hmm, was Composite with vmux = 0 tested as well? Seems so.

This is usually used for Composite over the s-video input connector.
Some cards have only this one and S-Video.

> What is gpio? Does it have anything to do with the colour?

Usually not at all. We have some about gpio pins on the v4l wiki and you
can read about more saa713x details in publicly available documentation.

In case external vmux chips, video enhancers or Low Noise Amplifiers are
involved, they can play a role and are also on other chips of recent
cards.

The current 210RF has an inconsistency for LNA configuration, since in
saa7134-dvb.c tuner_config = 2 is set, but not in saa7134-cards.c. 

> Below is some extracts from the .inf file on the Windows driver disk.  I 
> see (from the third line) that my card is "3xHybridQ" - based on the 4 
> bytes being reported from the eeprom .  Based on that, certain values 
> would be loaded into the registry - but I have no idea what those values 
> represent.  I don't know if it is of any help.

Mostly the i2c addresses of chips we have already detected, but not
listed, audio connections and a few I don't know exactly either, but are
for sure the same like for a fully operational card=78, Asus P7131 Dual.

For the 0x50 for FM mode I'm not sure, but radio amux is TV.

For antenna input and AGC switching on gpio21, some recent cards use it
also the other way round. Don't see a reason to change it, but
interaction between production plants and multiple manufacturers is
complex.

If you get nothing from radio and TV tuner,
you can also try to swap the gpio values for these keeping the gpio mask
unchanged.

> You will get some peace from me for a week.  I will be away on business.
> 
> Ian

According to the recent Philips driver Kworld distributes, all our vmux
settings are correct as well and follow the previous 210RF card.

But damned again, all silicon tuner cards have amux LINE2 for composite
and s-video, only can tuners have LINE1. This is wrong on 210 and 220RF.
If it is true with the can tuners, the ATSC110/115 is wrong too the
other way round. 

Only cards with a video enhancer, usually a big well visible NEC chip,
have vmux TV = 9, Composite = 4 and S-Video = 6.

>From the driver's side I'm out of ideas for now.

Have a nice week,

Hermann

> 
> 
> %Hybrid.DeviceDescSilicon% 
> =3xHybridP.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_735117DE
> 
> %Hybrid.DeviceDescSilicon% 
> =3xHybridO.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_735217DE
> 
> %Hybrid.DeviceDescSilicon% 
> =3xHybridQ.NTx86,PCI\VEN_1131&DEV_7133&SUBSYS_725317DE
> 
> 
> [3xHybridO.AddReg]
> 
> HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x18,0x00,0x00,0x00 ; 
> Tuner ID
> 
> HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
> Tuner slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x00,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data5",0x00010001,0xFF,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x55,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x55,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x55,0x00,0x00,0x00 ; 
> FM radio mode.
> 
> HKR, "AudioDecoder", "CVBS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "SVHS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1
> 
> 
> [3xHybridP.AddReg]
> 
> HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x18,0x00,0x00,0x00 ; 
> Tuner ID
> 
> HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
> Tuner slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x86,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x00,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x03,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x21,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x00,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x00,0x00,0x00,0x00 ; 
> FM radio mode.
> 
> HKR, "AudioDecoder", "CVBS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "SVHS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1
> 
> 
> [3xHybridQ.AddReg]
> 
> HKR, "I2C Devices", "Device 0, Data1",0x00010001,0x21,0x00,0x00,0x00 ; 
> Tuner ID
> 
> HKR, "I2C Devices", "Device 0, Data2",0x00010001,0xC2,0x00,0x00,0x00 ; 
> Tuner slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data3",0x00010001,0x96,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data4",0x00010001,0x10,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data5",0x00010001,0x03,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data6",0x00010001,0x32,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data7",0x00010001,0x15,0x00,0x00,0x00 ; 
> Tuner IF PLL slave addr.
> 
> HKR, "I2C Devices", "Device 0, Data8",0x00010001,0x50,0x00,0x00,0x00 ; 
> FM radio mode.
> 
> HKR, "AudioDecoder", "CVBS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "SVHS Channel",0x00010001,3
> 
> HKR, "AudioDecoder", "FM Radio Channel",0x00010001,1
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Sonntag, den 17.08.2008, 21:25 +0100 schrieb Ian Davidson:
> Hi Hermann,
> 
> Success.  I did nothing of any significance.  What I did do was to add 
> some more lines to saa7134-cards.c (to add vmux 5, 6 and 7) - and then 
> went through the make process again.
> 
> Then, I ran xawtv and started by selecting Composite1 - and I got a 
> colour image.
> 
> I also ran streamer to capture the video signal (using Composite1) and 
> that also captured a colour image.
> 
> I hope it stays that way.
> 
> One other question - but this is probably not the correct place to ask. 
> In the 'help' for streamer, it describes the use of 'lav2wav' to strip 
> the audio out of a video file (that is, to create a separate WAV file 
> using the audio in a particular AVI file).  I do not seem to have 
> lav2wav on my system - and it does not appear to be something that yum 
> acknowledges (using Fedora repositories).  Where might I find lav2wav or 
> something similar?
> 
> Ian
> 

as I told you previously already, please stay on the lists.

I don't even have a minimum consense about how to submit 5 to 7 patches
currently within a kernel release cycle, but I'm very sure about that I
don't like to be included in 24/7 games and would expect at least kernel
level agreements for contributions still valid. Mauro?

So, you are on your own to get it in and further, but people on the
lists are always helpful.

Cheers,
Hermannn


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

Arrrrgh!

My capture has gone back to Black and White.

Since being able to capture video in colour, I have been attempting to 
install mjpegtools.  Today, having been pointed at the livna repository, 
I have succeeded.  When I tried a video capture (for regression testing 
purposes), I found that it was, once again, Black and White.

Having said that, I get occasional glimpses of colour - and when I do, 
it is the real colour of whatever the camera is pointing at.  Having 
made a brief study, it would seem that occasional frames get colour at 
the top half of the picture.  I have checked (broken and reconnected) 
the connections between the camera and the computer, but is does not 
seem to make any difference.

Any ideas where I go from here?

Ian





hermann pitton wrote:
> Hi Ian,
>
> Am Sonntag, den 17.08.2008, 21:25 +0100 schrieb Ian Davidson:
>   
>> Hi Hermann,
>>
>> Success.  I did nothing of any significance.  What I did do was to add 
>> some more lines to saa7134-cards.c (to add vmux 5, 6 and 7) - and then 
>> went through the make process again.
>>
>> Then, I ran xawtv and started by selecting Composite1 - and I got a 
>> colour image.
>>
>> I also ran streamer to capture the video signal (using Composite1) and 
>> that also captured a colour image.
>>
>> I hope it stays that way.
>>
>> One other question - but this is probably not the correct place to ask. 
>> In the 'help' for streamer, it describes the use of 'lav2wav' to strip 
>> the audio out of a video file (that is, to create a separate WAV file 
>> using the audio in a particular AVI file).  I do not seem to have 
>> lav2wav on my system - and it does not appear to be something that yum 
>> acknowledges (using Fedora repositories).  Where might I find lav2wav or 
>> something similar?
>>
>> Ian
>>
>>     
>
> as I told you previously already, please stay on the lists.
>
> I don't even have a minimum consense about how to submit 5 to 7 patches
> currently within a kernel release cycle, but I'm very sure about that I
> don't like to be included in 24/7 games and would expect at least kernel
> level agreements for contributions still valid. Mauro?
>
> So, you are on your own to get it in and further, but people on the
> lists are always helpful.
>
> Cheers,
> Hermannn
>
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>   

-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Dienstag, den 26.08.2008, 19:35 +0100 schrieb Ian Davidson:
> Arrrrgh!
> 
> My capture has gone back to Black and White.
> 
> Since being able to capture video in colour, I have been attempting to
> install mjpegtools.  Today, having been pointed at the livna
> repository, I have succeeded.  When I tried a video capture (for
> regression testing purposes), I found that it was, once again, Black
> and White.
> 
> Having said that, I get occasional glimpses of colour - and when I do,
> it is the real colour of whatever the camera is pointing at.  Having
> made a brief study, it would seem that occasional frames get colour at
> the top half of the picture.  I have checked (broken and reconnected)
> the connections between the camera and the computer, but is does not
> seem to make any difference.
> 
> Any ideas where I go from here?
> 
> Ian
> 

please excuse, but you are on some limit for random issues.

We have, within what is hidden, about two hundreds saa713x cards.

I'll pull some of my analog stuff out of the trash bin once more and
check, but I don't like it to do it again and it will not happen
endlessly.

You will need some companions claiming still having the same after it.

If you have a chance to test on the Philips/NXP m$ driver, fine there ?

I don't know what more to debug here and gave already all hints in all
directions i can think about.

Maybe they have done something really not recommended, but I can't tell.

Cheers,
Hermann





> 
> 
> 
> hermann pitton wrote: 
> > Hi Ian,
> > 
> > Am Sonntag, den 17.08.2008, 21:25 +0100 schrieb Ian Davidson:
> >   
> > > Hi Hermann,
> > > 
> > > Success.  I did nothing of any significance.  What I did do was to add 
> > > some more lines to saa7134-cards.c (to add vmux 5, 6 and 7) - and then 
> > > went through the make process again.
> > > 
> > > Then, I ran xawtv and started by selecting Composite1 - and I got a 
> > > colour image.
> > > 
> > > I also ran streamer to capture the video signal (using Composite1) and 
> > > that also captured a colour image.
> > > 
> > > I hope it stays that way.
> > > 
> > > One other question - but this is probably not the correct place to ask. 
> > > In the 'help' for streamer, it describes the use of 'lav2wav' to strip 
> > > the audio out of a video file (that is, to create a separate WAV file 
> > > using the audio in a particular AVI file).  I do not seem to have 
> > > lav2wav on my system - and it does not appear to be something that yum 
> > > acknowledges (using Fedora repositories).  Where might I find lav2wav or 
> > > something similar?
> > > 
> > > Ian
> > > 
> > >     
> > 
> > as I told you previously already, please stay on the lists.
> > 
> > I don't even have a minimum consense about how to submit 5 to 7 patches
> > currently within a kernel release cycle, but I'm very sure about that I
> > don't like to be included in 24/7 games and would expect at least kernel
> > level agreements for contributions still valid. Mauro?
> > 
> > So, you are on your own to get it in and further, but people on the
> > lists are always helpful.
> > 
> > Cheers,
> > Hermannn
> > 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Mittwoch, den 27.08.2008, 01:15 +0200 schrieb hermann pitton:
> Hi Ian,
> 
> Am Dienstag, den 26.08.2008, 19:35 +0100 schrieb Ian Davidson:
> > Arrrrgh!
> > 
> > My capture has gone back to Black and White.
> > 
> > Since being able to capture video in colour, I have been attempting to
> > install mjpegtools.  Today, having been pointed at the livna
> > repository, I have succeeded.  When I tried a video capture (for
> > regression testing purposes), I found that it was, once again, Black
> > and White.
> > 
> > Having said that, I get occasional glimpses of colour - and when I do,
> > it is the real colour of whatever the camera is pointing at.  Having
> > made a brief study, it would seem that occasional frames get colour at
> > the top half of the picture.  I have checked (broken and reconnected)
> > the connections between the camera and the computer, but is does not
> > seem to make any difference.
> > 
> > Any ideas where I go from here?
> > 
> > Ian
> > 
> 
> please excuse, but you are on some limit for random issues.
> 
> We have, within what is hidden, about two hundreds saa713x cards.
> 
> I'll pull some of my analog stuff out of the trash bin once more and
> check, but I don't like it to do it again and it will not happen
> endlessly.
> 
> You will need some companions claiming still having the same after it.
> 
> If you have a chance to test on the Philips/NXP m$ driver, fine there ?
> 
> I don't know what more to debug here and gave already all hints in all
> directions i can think about.
> 
> Maybe they have done something really not recommended, but I can't tell.
> 

as promised, I did waste my late Sunday afternoon running with a VCR
back from the trash bin and a cam over four revived machines with lots
of saa713x stuff.

There have been lots of regressions during the last kernels, mostly
fully announced previously, but not that one.

I can't confirm your issues.

Try to find others with the same.

Cheers,
Hermann



> 
> 
> 
> > 
> > 
> > 
> > hermann pitton wrote: 
> > > Hi Ian,
> > > 
> > > Am Sonntag, den 17.08.2008, 21:25 +0100 schrieb Ian Davidson:
> > >   
> > > > Hi Hermann,
> > > > 
> > > > Success.  I did nothing of any significance.  What I did do was to add 
> > > > some more lines to saa7134-cards.c (to add vmux 5, 6 and 7) - and then 
> > > > went through the make process again.
> > > > 
> > > > Then, I ran xawtv and started by selecting Composite1 - and I got a 
> > > > colour image.
> > > > 
> > > > I also ran streamer to capture the video signal (using Composite1) and 
> > > > that also captured a colour image.
> > > > 
> > > > I hope it stays that way.
> > > > 
> > > > One other question - but this is probably not the correct place to ask. 
> > > > In the 'help' for streamer, it describes the use of 'lav2wav' to strip 
> > > > the audio out of a video file (that is, to create a separate WAV file 
> > > > using the audio in a particular AVI file).  I do not seem to have 
> > > > lav2wav on my system - and it does not appear to be something that yum 
> > > > acknowledges (using Fedora repositories).  Where might I find lav2wav or 
> > > > something similar?
> > > > 
> > > > Ian
> > > > 
> > > >     
> > > 
> > > as I told you previously already, please stay on the lists.
> > > 
> > > I don't even have a minimum consense about how to submit 5 to 7 patches
> > > currently within a kernel release cycle, but I'm very sure about that I
> > > don't like to be included in 24/7 games and would expect at least kernel
> > > level agreements for contributions still valid. Mauro?
> > > 
> > > So, you are on your own to get it in and further, but people on the
> > > lists are always helpful.
> > > 
> > > Cheers,
> > > Hermannn
> > > 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[Ian Davidson]

I am about to give up with this KWorld card as I do not have the time - 
I need to get something that works.  So 2 questions - one for a 'last 
try' and one for 'Plan B'.

Q1. Initially, the card was not recognised automatically, but under 
guidance form Hermann, forcing Linux to treat it as card=114, I was able 
to capture video.  Unfortunately, normally Black and White rather than 
colour.  I understand that  normally Linux would sniff the eeprom and 
determine the type of card from information found in there.  I have the 
.inf files that describe the various KWorld cards to that other 
operating system and I can see that the first 4 bytes of the eeprom, 
albeit swapped about (Big Endian/Little Endian) are used in that .inf to 
identify the card.  Various parameters are apparently put into the 
Registry, depending on the card type and I thought I would compare the 
parameters for my card with the parameters for the 'Real 114'.  I assume 
that there is a file somewhere which says "If the eeprom says 'xxxx' 
then the card is type 'n'".  Where can I see that file which identifies 
the card type?

Q2. Assuming that I am unable to make any difference, I will need to use 
a different card - and hopefully, one that is supported.  In order to 
make the current card do anything, I had to issue a couple of commands

"modprobe -vr saa7134-dvb saa7134-alsa saa7134 tuner"

"modprobe -v saa7134 card=114 i2c_scan=1"

so presumably, I would need to 'undo' the effect of those lines to let Linux auto-detect.  What do I need to do?

Ian


-- 
Ian Davidson
239 Streetsbrook Road, Solihull, West Midlands, B91 1HE
-- 
Facts used in this message may or may not reflect an underlying objective reality. 
Facts are supplied for personal use only. 
Recipients quoting supplied information do so at their own risk. 
Facts supplied may vary in whole or part from widely accepted standards. 
While painstakingly researched, facts may or may not be indicative of actually occurring events or natural phenomena. 
The author accepts no responsibility for personal loss or injury resulting from memorisation and subsequent use.


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: KWorld DVB-T 210SE - Capture only in Black/White

[hermann pitton]

Hi Ian,

Am Freitag, den 05.09.2008, 20:23 +0100 schrieb Ian Davidson:
> I am about to give up with this KWorld card as I do not have the time - 
> I need to get something that works.  So 2 questions - one for a 'last 
> try' and one for 'Plan B'.
> 
> Q1. Initially, the card was not recognised automatically, but under 
> guidance form Hermann, forcing Linux to treat it as card=114, I was able 
> to capture video.  Unfortunately, normally Black and White rather than 
> colour.  I understand that  normally Linux would sniff the eeprom and 
> determine the type of card from information found in there.  I have the 
> .inf files that describe the various KWorld cards to that other 
> operating system and I can see that the first 4 bytes of the eeprom, 
> albeit swapped about (Big Endian/Little Endian) are used in that .inf to 
> identify the card.  Various parameters are apparently put into the 
> Registry, depending on the card type and I thought I would compare the 
> parameters for my card with the parameters for the 'Real 114'.  I assume 
> that there is a file somewhere which says "If the eeprom says 'xxxx' 
> then the card is type 'n'".  Where can I see that file which identifies 
> the card type?

the manufacturers always need to improve their products to stay
competitive.

So we continuously see new card revisions with some small changes.
That likely is the same for your card, the 210SE.

>From what I'm aware of, I'm for sure not of all, we can neither gather
from the .inf files nor from the eeprom dump additional information.

Admittedly the previous 210RF had already previously reports of some
instability for DVB-T usage and reasons are unknown and since no more
users came in, the base is a singular report.

Your report to have sometimes color on the composite input and sometimes
only black and white is very unusual, since this also should not be
related to an additional external LNA, but I asked you to try with
tuner_config = 2 for the card in saa7134-cards.c, since it hangs around
in saa7134-dvb.c for it, and if possible, also on the some other OS.

> 
> Q2. Assuming that I am unable to make any difference, I will need to use 
> a different card - and hopefully, one that is supported.  In order to 
> make the current card do anything, I had to issue a couple of commands
> 
> "modprobe -vr saa7134-dvb saa7134-alsa saa7134 tuner"
> 
> "modprobe -v saa7134 card=114 i2c_scan=1"
> 
> so presumably, I would need to 'undo' the effect of those lines to let Linux auto-detect.  What do I need to do?
> 
> Ian

Your card is a new revision, the manufacturer changed the PCI subsystem
ID in the eeprom for it. That might have a reason.

At least that is the reason why it is not auto detected yet and why you
have to use "modprobe -v" for loading the likely most matching card,
that should be its previous revision.

Anyway, someone must go through all details, not only external inputs,
but also radio, analog TV and DVB-T before we can add that card to auto
detection.

Depending of the results of that work, we have to decide if it can use
the same entry as the previous card has or if it needs a new one,
because something substantial has changed.

You find the auto detection in saa7134-cards.c, the card enumeration in
saa7134.h and all is mirrored in Documentation/CARDLIST.saa7134.

As already explained, there is nothing to "undo" after "modprobe",
except you like to unload and try with different options again.

The -v option can be helpful, since it can find settings some system
setup helper tool might have written for you overriding your command
line for module options, but there is no indication in that direction.

Sorry, we have a very poor result here, but thanks for all your efforts
so far.

It becomes obvious, that manufacturers actively supporting GNU/Linux on
the more complex devices we have these days, but which are in most cases
still easy to set up within the framework we have, but not for every
single first customer, are clearly winners.

And that is fully OK.

Cheers,
Hermann






--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list