I have compiled and installed zoneminder with no problems.
I configured a monitor through the web front end but when I came to view the image from the webcam there was nothing there.
I started to run through the trouble shooting section of the readme and got up to checking the zmc utility. I think this is failing on my system but not to sure why.
This is a dump of the var/log/messages file when I run the command:-
"zmc --device /dev/video0"
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Debug Level = 0, Debug Log = ]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Got 1 monitors]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [X:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Y:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [W:640]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [H:480]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [P:4]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [D:24]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [B:42496]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [h:32768]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Cl:49152]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Cn:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [vmb.frames = 2]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [vmb.size = 1843216]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [C:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [F:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Fl:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [T:2]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [X:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [Y:0]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [W:352]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [H:288]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [P:4]
Oct 28 22:29:23 mdlinux zmc-d0[4917]: INF [D:24]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [B:42496]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [h:32768]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [Cl:49152]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [Cn:0]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [monitor mode=1]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: INF [shm.size=30413248]
Oct 28 22:29:24 mdlinux zmc-d0[4917]: ERR [Can't shmget: Invalid argument]
Oct 28 22:29:29 mdlinux kernel: vfree(): sleeping in interrupt!!
Oct 28 22:29:29 mdlinux kernel: c02e3f18 c0227060 c65fe5fc c65fe400 c88c4625 c88d3000 001c2010 c65fe5fc
Oct 28 22:29:29 mdlinux kernel: c65fe400 c65fe400 c88c4742 c65fe400 c65fe400 c88c46fc c0329470 c011e6ef
Oct 28 22:29:29 mdlinux kernel: c65fe400 c0330440 00000000 c0329470 00000000 c011b26f c011b1a6 00000000
Oct 28 22:29:29 mdlinux kernel: Call Trace: [<c88c4625>] ov51x_do_dealloc [ov511] 0x45
Oct 28 22:29:29 mdlinux kernel: [<c88c4742>] ov51x_buf_callback [ov511] 0x46
Oct 28 22:29:29 mdlinux kernel: [<c88c46fc>] ov51x_buf_callback [ov511] 0x0
Oct 28 22:29:29 mdlinux kernel: [<c011e6ef>] timer_bh [kernel] 0x20b
Oct 28 22:29:29 mdlinux kernel: [<c011b26f>] bh_action [kernel] 0x1b
Oct 28 22:29:29 mdlinux kernel: [<c011b1a6>] tasklet_hi_action [kernel] 0x52
Oct 28 22:29:29 mdlinux kernel: [<c011afc3>] do_softirq [kernel] 0x47
Oct 28 22:29:29 mdlinux kernel: [<c010992c>] do_IRQ [kernel] 0x90
Oct 28 22:29:29 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:29 mdlinux kernel: [<c0106b74>] default_idle [kernel] 0x0
Oct 28 22:29:29 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:29 mdlinux kernel: [<c0106b97>] default_idle [kernel] 0x23
Oct 28 22:29:29 mdlinux kernel: [<c0106bdc>] cpu_idle [kernel] 0x20
Oct 28 22:29:29 mdlinux kernel:
Oct 28 22:29:29 mdlinux kernel: vfree(): sleeping in interrupt!!
Oct 28 22:29:29 mdlinux kernel: c02e3f1c c0227060 c65fe5fc c65fe400 c88c4641 c8a97000 c65fe5fc c65fe400
Oct 28 22:29:29 mdlinux kernel: c65fe400 c88c4742 c65fe400 c65fe400 c88c46fc c0329470 c011e6ef c65fe400
Oct 28 22:29:29 mdlinux kernel: c0330440 00000000 c0329470 00000000 c011b26f c011b1a6 00000000 00000001
Oct 28 22:29:29 mdlinux kernel: Call Trace: [<c88c4641>] ov51x_do_dealloc [ov511] 0x61
Oct 28 22:29:29 mdlinux kernel: [<c88c4742>] ov51x_buf_callback [ov511] 0x46
Oct 28 22:29:29 mdlinux kernel: [<c88c46fc>] ov51x_buf_callback [ov511] 0x0
Oct 28 22:29:29 mdlinux kernel: [<c011e6ef>] timer_bh [kernel] 0x20b
Oct 28 22:29:29 mdlinux kernel: [<c011b26f>] bh_action [kernel] 0x1b
Oct 28 22:29:29 mdlinux kernel: [<c011b1a6>] tasklet_hi_action [kernel] 0x52
Oct 28 22:29:29 mdlinux kernel: [<c011afc3>] do_softirq [kernel] 0x47
Oct 28 22:29:30 mdlinux kernel: [<c010992c>] do_IRQ [kernel] 0x90
Oct 28 22:29:30 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0106b74>] default_idle [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0106b97>] default_idle [kernel] 0x23
Oct 28 22:29:30 mdlinux kernel: [<c0106bdc>] cpu_idle [kernel] 0x20
Oct 28 22:29:30 mdlinux kernel:
Oct 28 22:29:30 mdlinux kernel: vfree(): sleeping in interrupt!!
Oct 28 22:29:30 mdlinux kernel: c02e3f1c c0227060 c65fe5fc c8a97000 c88c465c c8b7a000 c65fe5fc c65fe400
Oct 28 22:29:30 mdlinux kernel: c65fe400 c88c4742 c65fe400 c65fe400 c88c46fc c0329470 c011e6ef c65fe400
Oct 28 22:29:30 mdlinux kernel: c0330440 00000000 c0329470 00000000 c011b26f c011b1a6 00000000 00000001
Oct 28 22:29:30 mdlinux kernel: Call Trace: [<c88c465c>] ov51x_do_dealloc [ov511] 0x7c
Oct 28 22:29:30 mdlinux kernel: [<c88c4742>] ov51x_buf_callback [ov511] 0x46
Oct 28 22:29:30 mdlinux kernel: [<c88c46fc>] ov51x_buf_callback [ov511] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c011e6ef>] timer_bh [kernel] 0x20b
Oct 28 22:29:30 mdlinux kernel: [<c011b26f>] bh_action [kernel] 0x1b
Oct 28 22:29:30 mdlinux kernel: [<c011b1a6>] tasklet_hi_action [kernel] 0x52
Oct 28 22:29:30 mdlinux kernel: [<c011afc3>] do_softirq [kernel] 0x47
Oct 28 22:29:30 mdlinux kernel: [<c010992c>] do_IRQ [kernel] 0x90
Oct 28 22:29:30 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0106b74>] default_idle [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0105000>] stext [kernel] 0x0
Oct 28 22:29:30 mdlinux kernel: [<c0106b97>] default_idle [kernel] 0x23
Oct 28 22:29:31 mdlinux kernel: [<c0106bdc>] cpu_idle [kernel] 0x20
Oct 28 22:29:31 mdlinux kernel:
"Don't like the look of all them kernel hex numbers!!!"
The webcam I'm using is a USB trust spacec@m 200 which uses the ov511 driver.
The web cam works fine and I am able to capture images using the utility w3com no problems at all.
The system that I'm running is a Redhat 7.3 install
heres a dump from the /proc/version file:-
Linux version 2.4.18-3 (bhcompile@stripples.devel.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 Thu Apr 18 07:31:07 EDT 2002
Anybody have any ideas to what is wrong?
Many thanks
Matt
problem running zmc
Re: problem running zmc
An extra note:
I failed to mention the version of zm I'm running
it is 0.9.15
I failed to mention the version of zm I'm running
it is 0.9.15
Re: problem running zmc
Ok got it working now!
Found out I never had the ARchive::Zip perl module installed.
As I'm not using this feature I commented it out in the zmfilter.pl
Can still replicate the error above though by choosing a value of 640x480 capture size.
Is it somthing to do with amount shared memory available??
Anyway works fine at the lower resolution
Matt
Found out I never had the ARchive::Zip perl module installed.
As I'm not using this feature I commented it out in the zmfilter.pl
Can still replicate the error above though by choosing a value of 640x480 capture size.
Is it somthing to do with amount shared memory available??
Anyway works fine at the lower resolution
Matt
Re: problem running zmc
Oh yes,
Thats another camera to your list
USB: Trust Spacec@m 200
Thats another camera to your list
USB: Trust Spacec@m 200
Re: problem running zmc
The problem is the shared memory.
At 640x480, greyscale, each frame needs 300KB of memory.
For 100 frames (the default buffer size) you'd need almost 30MB of memory.
That's too much shared memory to allocate.
This is discussed in the Troubleshooting section of the README.
You can find out how much shared memory is available:
cat /proc/sys/kernel/shmall
and the most you can allocate in one shot:
cat /proc/sys/kernel/shmmax
Apparently you can change these values too; see http://www.redhat.com/docs/manuals/data ... urces.html
I haven't tried that yet; I've had similar problems with large/color video settings.
Doug.
At 640x480, greyscale, each frame needs 300KB of memory.
For 100 frames (the default buffer size) you'd need almost 30MB of memory.
That's too much shared memory to allocate.
This is discussed in the Troubleshooting section of the README.
You can find out how much shared memory is available:
cat /proc/sys/kernel/shmall
and the most you can allocate in one shot:
cat /proc/sys/kernel/shmmax
Apparently you can change these values too; see http://www.redhat.com/docs/manuals/data ... urces.html
I haven't tried that yet; I've had similar problems with large/color video settings.
Doug.
Re: problem running zmc
I'm running RedHat 8.0 and I had the shmmax problem but I changed it on the fly via ... Mind you I have 128 megs of ram with 4 shared to the video card.
$ echo 134217728 >/proc/sys/kernel/shmall
$ echo 134217728 >/proc/sys/kernel/shmmax
However this did not work... I also edited my /etc/sysctl.conf and added these lines...
kernel.shmall = 134217728
kernel.shmmax = 134217728
Added 256Megs of ram and rebooted... :-P Now it works... I'm pretty sure it;s what I added to to sysctl.conf that fixed the problem.
$ echo 134217728 >/proc/sys/kernel/shmall
$ echo 134217728 >/proc/sys/kernel/shmmax
However this did not work... I also edited my /etc/sysctl.conf and added these lines...
kernel.shmall = 134217728
kernel.shmmax = 134217728
Added 256Megs of ram and rebooted... :-P Now it works... I'm pretty sure it;s what I added to to sysctl.conf that fixed the problem.