video device not found

[rob]

root@lakepdock:/home/rob# zmu -d 0 -q -v
Error, failed to open video device 0: No such file or directory

this is strange -- i have used this card before with the previous zm ver 1.21.3
the card is found after an options line in modprobe.d see dmesg snip below.
i'm using a 2.6.13 debian kernel and for the most part sid(2.6.13-kanotix-17)
dmesg shows all caputre ports found and registered and /dev
shows video0 -video3 -- what should i be looking at or for?


bttv0: Bt878 (rev 17) at 0000:03:08.0, irq: 10, latency: 32, mmio: 0xcfafe000
bttv0: using: GrandTec Multi Capture Card (Bt878) [card=77,insmod option]
bttv0: gpio: en=00000000, out=00000000 in=00ff9100 [init]
bttv0: using tuner=-1
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bt878: Unknown symbol bttv_read_gpio
bt878: Unknown symbol bttv_write_gpio
bt878: Unknown symbol bttv_gpio_enable
bttv0: registered device vbi0

[zoneminder]

Assuming you are on 1.21.4 this note from the changelog is probably relevant

o FIX – References to the video device files are now expressed as full file paths rather than just numbers. This allows files other than /dev/videoX to be used easily.

In other words do

Code: Select all

zmu -d /dev/video0 -q -v

now instead of just using 0.

Phil

[rob]

thanks phil zdm now gives a full report but i have only the blue overlay screen
for a picture display (zdm output below)

ZM_STRICT_VIDEO_CONFIG is off -- i have had to do this before
all zm logs look good -- the only error is in syslog
any suggestions ?

Nov 17 15:18:44 lakepdock zmc_dvideo0[11713]: INF [Debug Level = 0, Debug Log = <none>]
Nov 17 15:18:44 lakepdock zmc_dvideo0[11713]: INF [Starting Capture]
Nov 17 15:18:44 lakepdock zmc_dvideo1[11718]: INF [Debug Level = 0, Debug Log = <none>]
Nov 17 15:18:44 lakepdock zmc_dvideo1[11718]: ERR [Failed to set picture attributes: Invalid argument]
Nov 17 15:18:44 lakepdock zmc_dvideo1[11718]: ERR [Failed to set window attributes: Invalid argument]
Nov 17 15:18:44 lakepdock zmc_dvideo1[11718]: INF [Starting Capture]
Nov 17 15:19:18 lakepdock zmc_dvideo0[11713]: INF [New: 1000 - Capturing at 29.41 fps]
Nov 17 15:19:19 lakepdock zmc_dvideo1[11718]: INF [New2: 1000 - Capturing at 28.57 fps]
Nov 17 15:19:52 lakepdock zmc_dvideo0[11713]: INF [New: 2000 - Capturing at 29.41 fps]
Nov 17 15:19:53 lakepdock zmc_dvideo1[11718]: INF [New2: 2000 - Capturing at 29.41 fps]

zdm log

Video Capabilities
Name: BT878 video (GrandTec Multi Cap
Type: 171
Can capture
Can tune
Overlay onto frame buffer
Can clip
Scalable
Video Channels: 4
Audio Channels: 0
Maximum Width: 768
Maximum Height: 480
Minimum Width: 48
Minimum Height: 32
Window Attributes
X Offset: 0
Y Offset: 0
Width: 320
Height: 240
Picture Attributes
Palette: 4 - 24bit RGB
Colour Depth: 24
Brightness: 32768
Hue: 32768
Colour :32768
Contrast: 32768
Whiteness: 0
Channel 0 Attributes
Name: Composite0
Channel: 0
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 1 - NTSC
Channel 1 Attributes
Name: Composite1
Channel: 1
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 1 - NTSC
Channel 2 Attributes
Name: Composite2
Channel: 2
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 1 - NTSC
Channel 3 Attributes
Name: Composite3
Channel: 3
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 1 - NTSC

[cordel]

Nov 17 15:18:44 lakepdock zmc_dvideo1[11718]: ERR [Failed to set window attributes: Invalid argument]

Is usually the result of the wrong image size or palate is configured.
Also make sure you restart ZM after each time you change any of these settings.

regards,
Cordel

[rob]

ok i still have the syslog errors
Nov 17 18:34:57 lakepdock zmc_dvideo1[2297]: ERR [Failed to set picture attributes: Invalid argument]
Nov 17 18:34:57 lakepdock zmc_dvideo1[2297]: ERR [Failed to set window attributes: Invalid argument]
i thought it might have been a bad camera -- i borrowed one that had worked
with this board same story. i googled for setting debug levels --do i have to
compile in a higher level?
thanks rob

[cordel]

Try something like 384x240 since it detects that your cards max is
Maximum Width: 768
Maximum Height: 480

Regards,
Cordel

[rob]

i have been setting them to 320x 240 yuv420p and ntsc -- that was the settings for 1.21.3 -- i can get access to a 1.21.3 zm -- is there a file i can compare to for diff's -- not sure on the kernel i could try a zm upgrade
on the 1.21.3 but it is a 2.4.27. the camera is a stock commercial dome
i have used it before -- zoneminder is a fine "not me detector"
is there a way to increase the debug level so i can see where zm is
choking
thanks
rob

[jameswilson]

not t hat i know but i dont use yuv on my pallette just 24bit, dont supposed you tried it?

[rob]

yep i tried that and grey also

[jameswilson]

damn lol.
sorry mate cant help then

[zoneminder]

The errors in syslog are errors, but not necessarily fatal as you have strict video config off. The blue screen implies that ZM is capturing and presenting correctly but what it is getting from the card is blue, or that the card has no input. Have you tried using xawtv to check the input first and then doing a snapshot from xawtv and seeing what you get?

The is an easier method of increasing debug in 1.21.4 as detailed int he changelog. The simplest thing is to go to Options->Tools and look at the help in the ZM_EXTRA_DEBUG settings. Your EXTRA_DEBUG_TARGET will probably want to be either _zmc (for all zmc processes) or zmc_dvideo1 for your specific device. Don't forget to restart ZM when you change these settings. However I suspect you won't find anything. As I said a blue screen usually means that the card (or driver) is not outputting anything, incorrect settings often produce garbage rather than blue screen.

Phil