ZoneMinder Forums

Yes, my cards and cameras worked with zoneminder under gentoo.
I've tested it few months ago.

Now, I've decided to install it under gentoo because I'm more experienced with this distro, so my question is not actual.
Maybe, when I'll have some free time, I will try with FreeBSD again.

Nevertheless, thanks for Your reply

Regards
mch

mch wrote:Yes, my cards and cameras worked with zoneminder under gentoo.
I've tested it few months ago.

Now, I've decided to install it under gentoo because I'm more experienced with this distro, so my question is not actual.
Maybe, when I'll have some free time, I will try with FreeBSD again.

Nevertheless, thanks for Your reply

Regards
mch

you didnt answer some basic questions,
i think you should do a more thorough study, and then decide which os you will go with.
If it is a major driver issue, or you are not feeling technically familiar to FreeBSD then yes go to linux.
Otherwise it would be worth giving it a second try.

Hello

Has anyone using Freebsd and pico 2000 card [1]?? I have compiled the port attache on this topic succesfull. In linux i have used with no problem with 4 channels avaiable.
My system was detected the device when i load the driver bktr but i will give a blank image, not the blue when have signal. My chipset is conexant bt848 with same than [1]. With xawtv i will see the image.

My zoneminder config
device path /dev/bktr0
channel 0

Dmesg

bktr0: <BrookTree> mem 0xcfeff000-0xcfefffff irq 17 at device 1.0 on pci3
bktr0: [GIANT-LOCKED]
bktr0: [ITHREAD]
bktr0: Warning - card vendor 0x0000 (model 0x0000) unknown.
bktr0: Detected a DPL34-1@-@0 at 0x84
bktr0: Intel Smart Video III/VideoLogic Captivator PCI, <no> tuner, dpl3518a dolby.

[1] http://www.eduardolanhouse.com.br/media ... co2000.jpg

gianrubio wrote:Hello

Has anyone using Freebsd and pico 2000 card [1]?? I have compiled the port attache on this topic succesfull. In linux i have used with no problem with 4 channels avaiable.
My system was detected the device when i load the driver bktr but i will give a blank image, not the blue when have signal. My chipset is conexant bt848 with same than [1]. With xawtv i will see the image.

My zoneminder config
device path /dev/bktr0
channel 0

Dmesg

bktr0: <BrookTree> mem 0xcfeff000-0xcfefffff irq 17 at device 1.0 on pci3
bktr0: [GIANT-LOCKED]
bktr0: [ITHREAD]
bktr0: Warning - card vendor 0x0000 (model 0x0000) unknown.
bktr0: Detected a DPL34-1@-@0 at 0x84
bktr0: Intel Smart Video III/VideoLogic Captivator PCI, <no> tuner, dpl3518a dolby.

[1] http://www.eduardolanhouse.com.br/media ... co2000.jpg

if xawtv plays ok, then you should have no problem with zoneminder.
Did you play with channel/format/color?
Try to start with one camera only. Time division multiplexing could be a little tricky.
single chip cards like these can capture only 1 full-rate camera actually @ 25fps.
With two cameras it drops to 5fps and with four to less than 2.5fps

When i open zm to show cameras my messages show
Oct 1 12:13:29 centro zms[30884]: ERR [Got signal (Floating point exception: , crashing

I hava increased the debug level, but no more information on this.

gianrubio wrote:When i open zm to show cameras my messages show
Oct 1 12:13:29 centro zms[30884]: ERR [Got signal (Floating point exception: , crashing

I hava increased the debug level, but no more information on this.

in Config->Paths you have defined /cgi-bin/zms or /cgi-bin/nph-zms ?
Did you try with both?
If you dont find an easy answer, you will have to
% gdb <path to zms> <name of zms program>.core
somewhere in your system you should fine the core file.

Also you might want to take a look at here:
http://www.zoneminder.com/forums/viewto ... +exception
and here
http://www.zoneminder.com/wiki/index.ph ... do_I_do.3F
also try to check out all ZM logs in your system, (usually /tmp/zm*.log), or
if you use syslog wherever your local1 points to.
So you gotta get some debugging info first.

I have posted this thread to the freebsd mailing list but thought i might be good to put it here too.

----- Jeremy Chadwick <koitsu> wrote:
> On Mon, Oct 13, 2008 at 09:20:34PM -0600, RYAN vAN GINNEKEN wrote:
> > Trying to install zoneminder port but getting this error
> > Using this version on Freebsd
> >
> > FreeBSD pcbsd 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #42: Thu Sep 11 09:07:25 EDT 2008 root@pcbsd:/usr/obj/usr/src/sys/PCBSD i386
> >
> > cd . && /bin/sh /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/missing --run autoheader
>
> I have no such port on my system, and the FreeBSD web site agrees:
>
> # cd /usr/ports/multimedia/zoneminder
> /usr/ports/multimedia/zoneminder: No such file or directory.
> # grep -i zoneminder /usr/ports/INDEX-7
> #
>
You are correct this is not a native FreeBSD port i downloaded this port from here http://www.zoneminder.com/forums/viewto ... sc&start=0

> http://www.freebsd.org/cgi/cvsweb.cgi/p ... zoneminder
>
> I'm not sure how much support you'll get here for that.
>
> > aclocal.m4:14: error: this file was generated for autoconf 2.61.
> > You have another version of autoconf. If you want to use that,
> > you should regenerate the build system entirely.
> > aclocal.m4:14: the top level
> > autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63
> > autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63
>
> This indicates whoever made the port Makefile is making use of the wrong
> version of autoconf. The following line should be added or changed in
> the port Makefile:
>
> USE_AUTOTOOLS=

autoconf:261:env
I tried adding this to the Makefile but get this error instead
USE_AUTOTOOLS=

autoconf:261:env

make
===> zoneminder-1.23.3,1 cannot install: unknown AUTOCONF version: 261.
*** Error code 1

Stop in /usr/ports/multimedia/zoneminder.

So i tried to find out which version i was using and got this

autoconf --version
autoconf (GNU Autoconf) 2.62
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.


Next i tried changeing the line below and it was back to the exact same error above
USE_AUTOTOOLS=

autoconf:262:env

I dont think i ever used any *wrong* version of autoconf,
neither did i explicitly deal with autoconf/autotools issues as far as
i remember.
The acinclude.m4, aclocal.m4 files are from the stock Zoneminder tarball,
downloaded from http://www2.zoneminder.com/downloads/

having said that,
my respective ports are:

c0mputerking wrote:.....

I has the same error.
What I do is find the place in this port, where it compares you version with 2.61 and change this to 2.62
that's all

Achix I'm experiencing the exact same problems as the last few posters. On a fresh install of FreeBSD 7.0 Release.

The output of make install is:

/bin/cp /usr/ports/multimedia/zoneminder/files/zm_fbsd_camera.h /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/src
cd . && true
cd . && /usr/local/bin/autoheader-2.62
aclocal.m4:14: error: this file was generated for autoconf 2.61.
You have another version of autoconf. If you want to use that,
you should regenerate the build system entirely.
aclocal.m4:14: the top level
autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63
autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63
*** Error code 63

Stop in /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3.
*** Error code 1

Stop in /usr/ports/multimedia/zoneminder.
[root@diesel /usr/ports/multimedia/zoneminder]#


You cannot simply update the Makefile to use autoconf 2.62 since the port was built with 2.61. Autoconf 2.61 is no longer available in the ports collection, would it be possible for you to remake the port with the newer version of the Autoconf tool?

Jimmy wrote:Achix I'm experiencing the exact same problems as the last few posters. On a fresh install of FreeBSD 7.0 Release.

The output of make install is:

/bin/cp /usr/ports/multimedia/zoneminder/files/zm_fbsd_camera.h /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3/src
cd . && true
cd . && /usr/local/bin/autoheader-2.62
aclocal.m4:14: error: this file was generated for autoconf 2.61.
You have another version of autoconf. If you want to use that,
you should regenerate the build system entirely.
aclocal.m4:14: the top level
autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 63
autoheader-2.62: '/usr/local/bin/autom4te-2.62' failed with exit status: 63
*** Error code 63

Stop in /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3.
*** Error code 1

Stop in /usr/ports/multimedia/zoneminder.
[root@diesel /usr/ports/multimedia/zoneminder]#


You cannot simply update the Makefile to use autoconf 2.62 since the port was built with 2.61. Autoconf 2.61 is no longer available in the ports collection, would it be possible for you to remake the port with the newer version of the Autoconf tool?

Can you please, go to /usr/ports/multimedia/zoneminder/work/ZoneMinder-1.23.3
and run autoconf-2.62 by hand?
This way it should generate a new build system (configure,etc...)
And then try to proceed to the make as usual
cd ../..
make
what happens?

Hi Achix, thanks for replying. Only later did I realise you were using the aclocal.m4 and acinclude.m4 from the originally packaged distribution of zoneminder. I did try rebuilding the build system myself but without success see my thread here:

http://forums.freebsd.org/showthread.php?t=169

I actually managed to get it working in the end (I think) by downloading the new aclocal.m4 and acinclude.m4 from the 1.24 beta in the forums and placing the files in the work/Zoneminder/src directory, as well as adding the following to the makefile:

MAKE_ARGS= ACLOCAL="${TRUE}" AUTOCONF="${TRUE}" AUTOMAKE="${TRUE}"
USE_AUTOTOOLS= autoconf:262:env
USE_AUTOTOOLS= aclocal:110 /usr/local/bin/autoheader:262

Since I don't have a good understanding of the build systems, there's a good chance that a lot of this is bad/wrong, but it does work!

I also had to modify work/Zoneminder-1.23.3/src/zm_mpeg.cpp lines 281 and 283 from:

url_fclose(&ofc->pb);

to read:

url_fclose(ofc->pb);

since the url_fclose parameter was apparently already receiving a pointer and compilation would fail otherwise, this is with ffmpeg version: ffmpeg-2008.07.27_7

Again this is a fresh installation of FreeBSD 7.0-Release, so all the ports are current.

The makefile required some further modification since I'm using mod_perl2 with apache22 instead of mod_perl and also mysql51-server (latest available).

Compiling now, hope it finishes.
[/code]

Just to confirm, now compiled and working, just gotta set up the cameras, what a carry on though!

Great!!
Thanx for letting us know.
The point is, i didnt bother get into automake and autoconf, etc...,
so i dont have a clue how the configure system works.
Add to it the issues caused by other software like new versions of ffmpeg,
and i would say that i bet that it is very hard to build a port that gets
compiled in 100% of the cases.

The right thing (TM) would be to update the port to always work
with the newer libraries/rest of ports, but i doubt any of us has that time resources to do it.

We must keep the port in this unofficial state, helping each other in good
spirit, and be aware of all corner cases that would prevent future users from
using it.

This knowledge also might help in the next port of 1.24.

Hi Achix,

I have the Kodicom KMC-4400R and have compiled Mark T's patch into the kernel, dmesg is showing as having detected bktr0 - bktr3 although a pciconf -lv lists the cards as being unknown vendor, which makes me question is Marks patch having the desired effect with the crossbar on the card?

I've tried all sorts of camera settings and still can't get any input other than a blue background with a timestamp, have you tried this card and got it working? If so what settings did you use?

Thanks

Jimmy