| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 43 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 97:24:54 |
| Calls: | 290 |
| Files: | 904 |
| Messages: | 76,468 |
On 10 Oct 2024 10:41:13 +0100 (BST)
Theo <theom+news@chiark.greenend.org.uk> wrote:
Davey <davey@example.invalid> wrote:
Ok, let's try the Euresys drivers. The one for the card is
Multicam, which I downloaded, followed the instructions for
installation, and it kept on failing for lack of something or
other. Every attempt prompted an Uninstall to clean the system.
It wanted Memento, and it actually said 'install Memento', but
with no clue as to where to find it. I eventually did, buried
deep in the website, and downloaded the documentation and
installer for that. I tried to install it, but it fails:
The first rule is never ever use vendor drivers, they are the route
to much pain and suffering.
Supposedly the chip supports the 'bttv' driver: https://www.linuxtv.org/wiki/index.php/Bttv
which in theory should work out of the box.
See:
https://www.kernel.org/doc/html/v4.14/media/v4l-drivers/index.html specifically the bttv section.
You might need to install a package containing the 'bttv.ko' kernel
module - you may need a linux-modules-extra-... package. eg to
install for your current kernel version:
$ sudo apt install linux-modules-extra-$(uname -r)
(you may need to repeat the command when your kernel version gets
updated, not sure if there's a way to keep them in sync)
Theo
Ok. I sent some time on this today. As far as I can see, all the
required modules etc are loaded. I can find nothing to be missing,
but I am not familiar with this.
It looks as though all the components are there, the PC recognises the
card, but I can't get Zoneminder to open a channel. I'm leaving it
alone overnight.
In order to test the card, I have dug out an unused camera, by
Defender Security. It worked when I bought it and tested it, but I
can't now get it to function correctly when attached to the empty
input on the old PC. It may be that I tested it on the independent
Swann CCTV system. It has a resolution of 976 x 496, but if I set it
to that, I get a sliced and angled image. If I try some other setups,
all the other inputs go crazy, so my attempt to use a known good
camera on the new PC fails. I will have to temporarily remove one of
the working cameras from its place, use it for testing, and then
replace it. If I can get the PC and the card to talk turkey, that is.
And just to confuse me, Euresys replied to my earlier message about
Memento and Multicam, saying that Memento is not needed, and is old,
and suggesting I try Multicam alone. In direct contravention of their
own instruction manual!
it looks like a busy weekend at the workbench.
Any suggestions welcome.
Davey wrote:
Any suggestions welcome.
Does "lspci" show the brooktree card(s)?
does "ls /dev/video*" show the devices?
ls: cannot access '/dev/video*': No such file or directory
Now, I know I saw video0 somewhere before, I specically looked for it. I can't remember if it was in /dev. Then, I followed the instructions in HOW-TO-etc, and it was there before I rebooted. Now it's not. I need to
do some more route retracing.
Davey wrote:
ls: cannot access '/dev/video*': No such file or directory
Now, I know I saw video0 somewhere before, I specically looked for
it. I can't remember if it was in /dev. Then, I followed the
instructions in HOW-TO-etc, and it was there before I rebooted. Now
it's not. I need to do some more route retracing.
The entries under /dev would only appear if a driver had loaded,
normally PnP would handle it, but maybe some furtling with modprobe
or insmod required?
Probably look first for clues with "dmesg | grep -i -e bt878 -e brook"
Davey wrote:
ls: cannot access '/dev/video*': No such file or directory
Now, I know I saw video0 somewhere before, I specically looked for
it. I can't remember if it was in /dev. Then, I followed the
instructions in HOW-TO-etc, and it was there before I rebooted. Now
it's not. I need to do some more route retracing.
The entries under /dev would only appear if a driver had loaded,
normally PnP would handle it, but maybe some furtling with modprobe
or insmod required?
Probably look first for clues with "dmesg | grep -i -e bt878 -e brook"
On Sun, 13 Oct 2024 11:18:48 +0100
Andy Burns <usenet@andyburns.uk> wrote:
Davey wrote:
ls: cannot access '/dev/video*': No such file or directory
Now, I know I saw video0 somewhere before, I specically looked for
it. I can't remember if it was in /dev. Then, I followed the
instructions in HOW-TO-etc, and it was there before I rebooted.
Now it's not. I need to do some more route retracing.
The entries under /dev would only appear if a driver had loaded,
normally PnP would handle it, but maybe some furtling with modprobe
or insmod required?
Probably look first for clues with "dmesg | grep -i -e bt878 -e
brook"
"dmesg | grep -i -e bt878 -e brook"
produced no results. Hmm.
I ran "$ sudo dmesg | less" again, it had previously produced lines
showing that bttv was loaded. This time it did not.
I then ran "$ sudo modprobe -v bttv", and then the dmesg showed the
bttv entries again. So modprobe is needed, at least at the moment.
Then, again, the dmesg | grep instruction shows:
~$ sudo dmesg | grep -i -e bt878 -e brook
[16854.002864] bttv: 0: Bt878 (rev 17) at 0000:04:00.0, irq: 19,
latency: 32, mmio: 0x83401000
So things are heading in the right direction, even if for now manual configuration is needed.
Then $lsmod
"Module Size Used by
bttv 176128 0
tveeprom 24576 1 bttv
tea575x 20480 1 bttv
videobuf2_dma_sg 20480 1 bttv
videobuf2_memops 16384 1 videobuf2_dma_sg
videobuf2_v4l2 36864 1 bttv
videobuf2_common 81920 4 bttv,videobuf2_v4l2,videobuf2_dma_sg,videobuf2_memops rc_core
73728 1 bttv i2c_algo_bit 16384 1 bttv
videodev 356352 3 tea575x,bttv,videobuf2_v4l2
mc 81920 3
videodev,videobuf2_v4l2,videobuf2_common"
which shows an entry for v4l2.
Then:
$ ls /dev/video*
/dev/video0
So far, so good, it looks. But Zoneminder still does not see anything.
Still puzzled, with at least a list of what to do on boot to load
things.
it is only as
part of 'videobuf2'
Another thing that puzzles me:
I can locate bttv.ko, the module to load the driver, but I can't read
it, I get some strange script as though I need a different language.
Davey wrote:
Another thing that puzzles me:
I can locate bttv.ko, the module to load the driver, but I can't
read it, I get some strange script as though I need a different
language.
Curious why you think it ought to be readable? It's compiled code.
It's ages since I dabbled with ZM, so nothing I can say about
persuading it to use cameras.
can you get ffmpeg, gstreamer or vlc to capture from the camera?
I can try. Not my normal area of expertise, but anything is worth
trying.
More later, thanks for thoughts.
Davey <davey@example.invalid> wrote:
I can try. Not my normal area of expertise, but anything is worth
trying.
More later, thanks for thoughts.
It's worth looking at logs from Zoneminder, vlc or anywhere else
that's relevant. It's possible they're complaining about something
that is stopping the card from being accepted.
In the olden days the logfiles lived in /var/log (some still do), but nowadays you need to interact with 'journalctl', eg 'journalctl -x -e'
If you find a log line that's relevant, google the message and see
what comes up.
Theo
I must automate the required actions that I
know about to make bootup easier.
Davey wrote:
I must automate the required actions that I
know about to make bootup easier.
You ought to be able to force the equivalent of the insmod/modprobe
you're doing, by putting entries into /etc/modprobe.conf
Or at worst, adding the module name to the kernel command line in
your grub.cfg
On Mon, 14 Oct 2024 16:59:45 +0100
Andy Burns <usenet@andyburns.uk> wrote:
Davey wrote:
I must automate the required actions that I
know about to make bootup easier.
You ought to be able to force the equivalent of the insmod/modprobe
you're doing, by putting entries into /etc/modprobe.conf
Or at worst, adding the module name to the kernel command line in
your grub.cfg
As an aside, I was wondering whether to load Ubuntu 24.04 onto the new
PC, alongside the 22.04 that I am currently using, and see if
installing that, with the videocard already in place, might be worth a
try.
I installed 22.04 because 24.04 seemed to be lacking some programmes
that I use, whereas 22.04 is familiar with them. If 22.04 works, then
that would be fine, as the PC's main purpose is to run Zoneminder.
Davey wrote:
I must automate the required actions that I
know about to make bootup easier.
You ought to be able to force the equivalent of the insmod/modprobe
you're doing, by putting entries into /etc/modprobe.conf
Or at worst, adding the module name to the kernel command line in
your grub.cfg
Davey <davey@example.invalid> wrote:
I can try. Not my normal area of expertise, but anything is worth
trying.
More later, thanks for thoughts.
It's worth looking at logs from Zoneminder, vlc or anywhere else
that's relevant. It's possible they're complaining about something
that is stopping the card from being accepted.
In the olden days the logfiles lived in /var/log (some still do), but nowadays you need to interact with 'journalctl', eg 'journalctl -x -e'
If you find a log line that's relevant, google the message and see
what comes up.
Theo
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0: Permission denied]"
Davey <davey@example.invalid> wrote:
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0:
Permission denied]"
which gives a reason for failure.
On Ubuntu 24.04 I get:
$ ls -l /dev
...
crw-rw----+ 1 root video 81, 0 Oct 9 09:13 video0
crw-rw----+ 1 root video 81, 1 Oct 9 09:13 video1
crw-rw----+ 1 root video 81, 2 Oct 9 09:13 video2
crw-rw----+ 1 root video 81, 3 Oct 9 09:13 video3
so only those in the 'video' group get access to the video device.
Have you checked that your user is in the 'video' group?
Maybe it might be worth removing and reinstalling Zoneminder after
getting the ./MAKEDEV and modprobe -v bttv processes completed. I
seem to be just spinning my wheels here.
./MAKEDEV is a very old way of doing things. These days the tool is
'udev' and you have udev rules which say how the devices are made as
things are hotplugged. I have pre-existing rules in various files:
$ grep -r video /lib/udev/rules.d/
/lib/udev/rules.d/95-cd-devices.rules:# video cameras /lib/udev/rules.d/95-cd-devices.rules:SUBSYSTEM=="video4linux", ENV{ID_V4L_PRODUCT}!="", ENV{COLORD_DEVICE}="1",
ENV{COLORD_KIND}="camera" /lib/udev/rules.d/60-persistent-v4l.rules:SUBSYSTEM!="video4linux",
GOTO="persistent_v4l_end" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*",
ENV{ID_SERIAL}=="?*", SYMLINK+="v4l/by-id/$env{ID_BUS}-$env{ID_SERIAL}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*",
ENV{ID_PATH}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*",
ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH_WITH_USB_REVISION}-video-index$attr{index}" /lib/udev/rules.d/70-uaccess.rules:SUBSYSTEM=="video4linux",
TAG+="uaccess" /lib/udev/rules.d/70-uaccess.rules:# DRI video
devices /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="video4linux", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="graphics", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="drm", KERNEL!="renderD*",
GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="dvb", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="media", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="cec", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="firewire", TEST=="units", ENV{IEEE1394_UNIT_FUNCTION_VIDEO}=="1",
GROUP="video" /lib/udev/rules.d/70-camera.rules:SUBSYSTEM=="video4linux", ENV{ID_BUS}="usb",
\ /lib/udev/rules.d/80-debian-compat.rules:KERNEL=="lirc[0-9]*", GROUP="video"
You shouldn't edit those rules, but put new rules in /etc/udev/rules.d
However I don't think you need new rules, just putting your user in
the 'video' group and then logging out and back in again should fix
it.
Theo
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0: Permission denied]"
which gives a reason for failure.
Maybe it might be worth removing and reinstalling Zoneminder after
getting the ./MAKEDEV and modprobe -v bttv processes completed. I seem
to be just spinning my wheels here.
Davey <davey@example.invalid> wrote:
I'm sort of lost here, any help welcome.
Have a look at USB adapters. SD video is not that high bit rate,
especially if the adapter is compressing. No idea of the marketplace, although I have a $7 composite video USB capture that's probably
awful. BNC is just composite video I think - do they power from there
or external power?
If you have a lot of USB devices consider extra USB PCIe cards, but 4
behind a USB 3 hub is probably ok.
Theo
Ok, let's try the Euresys drivers. The one for the card is Multicam,
which I downloaded, followed the instructions for installation, and it
kept on failing for lack of something or other. Every attempt prompted
an Uninstall to clean the system. It wanted Memento, and it actually
said 'install Memento', but with no clue as to where to find it. I
eventually did, buried deep in the website, and downloaded the
documentation and installer for that. I tried to install it,
but it fails:
Davey <davey@example.invalid> wrote:
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0:
Permission denied]"
which gives a reason for failure.
On Ubuntu 24.04 I get:
$ ls -l /dev
...
crw-rw----+ 1 root video 81, 0 Oct 9 09:13 video0
crw-rw----+ 1 root video 81, 1 Oct 9 09:13 video1
crw-rw----+ 1 root video 81, 2 Oct 9 09:13 video2
crw-rw----+ 1 root video 81, 3 Oct 9 09:13 video3
so only those in the 'video' group get access to the video device.
Have you checked that your user is in the 'video' group?
Maybe it might be worth removing and reinstalling Zoneminder after
getting the ./MAKEDEV and modprobe -v bttv processes completed. I
seem to be just spinning my wheels here.
./MAKEDEV is a very old way of doing things. These days the tool is
'udev' and you have udev rules which say how the devices are made as
things are hotplugged. I have pre-existing rules in various files:
$ grep -r video /lib/udev/rules.d/
/lib/udev/rules.d/95-cd-devices.rules:# video cameras /lib/udev/rules.d/95-cd-devices.rules:SUBSYSTEM=="video4linux", ENV{ID_V4L_PRODUCT}!="", ENV{COLORD_DEVICE}="1",
ENV{COLORD_KIND}="camera" /lib/udev/rules.d/60-persistent-v4l.rules:SUBSYSTEM!="video4linux", GOTO="persistent_v4l_end" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*", ENV{ID_SERIAL}=="?*", SYMLINK+="v4l/by-id/$env{ID_BUS}-$env{ID_SERIAL}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*", ENV{ID_PATH}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*", ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH_WITH_USB_REVISION}-video-index$attr{index}"
/lib/udev/rules.d/70-uaccess.rules:SUBSYSTEM=="video4linux",
TAG+="uaccess" /lib/udev/rules.d/70-uaccess.rules:# DRI video devices /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="video4linux", GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="graphics",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="drm",
KERNEL!="renderD*", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="dvb",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="media",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="cec",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="firewire",
TEST=="units", ENV{IEEE1394_UNIT_FUNCTION_VIDEO}=="1", GROUP="video" /lib/udev/rules.d/70-camera.rules:SUBSYSTEM=="video4linux", ENV{ID_BUS}="usb", \ /lib/udev/rules.d/80-debian-compat.rules:KERNEL=="lirc[0-9]*",
GROUP="video"
You shouldn't edit those rules, but put new rules in /etc/udev/rules.d
However I don't think you need new rules, just putting your user in
the 'video' group and then logging out and back in again should fix
it.
Theo
Davey wrote:
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0:
Permission denied]"
Can you use sudo or su to run whatever you're running?
Maybe chmod/chown the /dev/video0 device
run vlc, with su or sudo
from within the gui choose Media / Open Capture Device
and for video device use /dev/video0
leave audio device as 'none'
Davey <davey@example.invalid> wrote:
I just tried again, and then looked for the log. And the first thing
that comes up is:
"FAT [zmc_dvideo0] [Failed to open video device /dev/video0:
Permission denied]"
which gives a reason for failure.
On Ubuntu 24.04 I get:
$ ls -l /dev
...
crw-rw----+ 1 root video 81, 0 Oct 9 09:13 video0
crw-rw----+ 1 root video 81, 1 Oct 9 09:13 video1
crw-rw----+ 1 root video 81, 2 Oct 9 09:13 video2
crw-rw----+ 1 root video 81, 3 Oct 9 09:13 video3
so only those in the 'video' group get access to the video device.
Have you checked that your user is in the 'video' group?
Maybe it might be worth removing and reinstalling Zoneminder after
getting the ./MAKEDEV and modprobe -v bttv processes completed. I
seem to be just spinning my wheels here.
./MAKEDEV is a very old way of doing things. These days the tool is
'udev' and you have udev rules which say how the devices are made as
things are hotplugged. I have pre-existing rules in various files:
$ grep -r video /lib/udev/rules.d/
/lib/udev/rules.d/95-cd-devices.rules:# video cameras /lib/udev/rules.d/95-cd-devices.rules:SUBSYSTEM=="video4linux", ENV{ID_V4L_PRODUCT}!="", ENV{COLORD_DEVICE}="1",
ENV{COLORD_KIND}="camera" /lib/udev/rules.d/60-persistent-v4l.rules:SUBSYSTEM!="video4linux", GOTO="persistent_v4l_end" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*", ENV{ID_SERIAL}=="?*", SYMLINK+="v4l/by-id/$env{ID_BUS}-$env{ID_SERIAL}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*", ENV{ID_PATH}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH}-video-index$attr{index}" /lib/udev/rules.d/60-persistent-v4l.rules:KERNEL=="video*|vbi*", ENV{ID_PATH_WITH_USB_REVISION}=="?*", SYMLINK+="v4l/by-path/$env{ID_PATH_WITH_USB_REVISION}-video-index$attr{index}"
/lib/udev/rules.d/70-uaccess.rules:SUBSYSTEM=="video4linux",
TAG+="uaccess" /lib/udev/rules.d/70-uaccess.rules:# DRI video devices /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="video4linux", GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="graphics",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="drm",
KERNEL!="renderD*", GROUP="video" /lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="dvb",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="media",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="cec",
GROUP="video"
/lib/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="firewire",
TEST=="units", ENV{IEEE1394_UNIT_FUNCTION_VIDEO}=="1", GROUP="video" /lib/udev/rules.d/70-camera.rules:SUBSYSTEM=="video4linux", ENV{ID_BUS}="usb", \ /lib/udev/rules.d/80-debian-compat.rules:KERNEL=="lirc[0-9]*",
GROUP="video"
You shouldn't edit those rules, but put new rules in /etc/udev/rules.d
However I don't think you need new rules, just putting your user in
the 'video' group and then logging out and back in again should fix
it.
Theo
"crw-rw----+ 1 root video 81, 0 Oct 16 10:09 /dev/video0"
Why is the day's date the 0 of the month?
But vlc still fails on Permission refused! What am I doing wrong?
Davey wrote:
"crw-rw----+ 1 root video 81, 0 Oct 16 10:09 /dev/video0"
Why is the day's date the 0 of the month?
the 81, 0 are the major and minor device numbers, the date is the 16 following the month name :-)
But vlc still fails on Permission refused! What am I doing wrong?
I know it's not really the done thing, but will Ubuntu actually let
you log on as root to test it does work that way? Not suggesting
it's an actual fix.
On Wed, 16 Oct 2024 15:56:30 +0100
Andy Burns <usenet@andyburns.uk> wrote:
Davey wrote:
"crw-rw----+ 1 root video 81, 0 Oct 16 10:09 /dev/video0"
Why is the day's date the 0 of the month?
the 81, 0 are the major and minor device numbers, the date is the
16 following the month name :-)
But vlc still fails on Permission refused! What am I doing
wrong?
I know it's not really the done thing, but will Ubuntu actually let
you log on as root to test it does work that way? Not suggesting
it's an actual fix.
I tried that yesterday, but it replied that vlc would not work with
root.
Good idea, though!
To elaborate on this: I can run vlc without any problem. I can watch a different camera on my Swann system via rtsp. It is this /dev/video(0) permission problem that is stopping it working with the Zoneminder
cameras.
On Wed, 16 Oct 2024 17:29:18 +0100
Davey <davey@example.invalid> wrote:
On Wed, 16 Oct 2024 15:56:30 +0100
Andy Burns <usenet@andyburns.uk> wrote:
Davey wrote:
"crw-rw----+ 1 root video 81, 0 Oct 16 10:09 /dev/video0"
Why is the day's date the 0 of the month?
the 81, 0 are the major and minor device numbers, the date is the
16 following the month name :-)
But vlc still fails on Permission refused! What am I doing
wrong?
I know it's not really the done thing, but will Ubuntu actually
let you log on as root to test it does work that way? Not
suggesting it's an actual fix.
I tried that yesterday, but it replied that vlc would not work with
root.
Good idea, though!
To elaborate on this: I can run vlc without any problem. I can watch a different camera on my Swann system via rtsp. It is this /dev/video(0) permission problem that is stopping it working with the Zoneminder
cameras.
Davey <davey@example.invalid> wrote:
Ok, let's try the Euresys drivers. The one for the card is Multicam,
which I downloaded, followed the instructions for installation, and
it kept on failing for lack of something or other. Every attempt
prompted an Uninstall to clean the system. It wanted Memento, and
it actually said 'install Memento', but with no clue as to where to
find it. I eventually did, buried deep in the website, and
downloaded the documentation and installer for that. I tried to
install it, but it fails:
The first rule is never ever use vendor drivers, they are the route
to much pain and suffering.
Supposedly the chip supports the 'bttv' driver: https://www.linuxtv.org/wiki/index.php/Bttv
which in theory should work out of the box.
See:
https://www.kernel.org/doc/html/v4.14/media/v4l-drivers/index.html specifically the bttv section.
You might need to install a package containing the 'bttv.ko' kernel
module - you may need a linux-modules-extra-... package. eg to
install for your current kernel version:
$ sudo apt install linux-modules-extra-$(uname -r)
(you may need to repeat the command when your kernel version gets
updated, not sure if there's a way to keep them in sync)
Theo
Many thanks. I tried the instructions that came with the original bttv
driver card, but got nowhere. But that was for an early version of
Ubuntu, so I was not surprised.
I will try your suggestions, thanks.
Davey <davey@example.invalid> wrote:
Many thanks. I tried the instructions that came with the original
bttv driver card, but got nowhere. But that was for an early
version of Ubuntu, so I was not surprised.
I will try your suggestions, thanks.
Anyway, it appears Memento is completely the wrong thing for your application:
"Memento is an advanced event message logging system that greatly
facilitates the debugging of machine vision applications using
Euresys frame grabbers.
Memento is a set of software tools allowing:
* Kernel drivers and user space applications –
Memento Contributors – to inject trace messages – Memento Messages – into a common memory area – the Memento Ring Buffer.
* Memento Contributors to time-stamp Memento messages
using a common time scale – Memento Time Scale.
* To view selected sets of recent- or past- Memento
Messages using the Memento Viewer function
* To dump Memento data from the Memento Ring Buffer
to disk using the Memento Dump function
The Memento software package has two main components:
* A kernel-mode driver: Memento Driver.
* A user-mode application: Memento Application." https://documentation.euresys.com/Products/Memento/Memento_9_4/Content/01%20Getting%20Started/Abstract.htm
I don't think you're debugging a machine vision application, so what
you were trying to install seems like a complete red herring.
"su -" wants a Password. Where do I find that? It won't accept mine, obviously.it's root's
Davey wrote:
To elaborate on this: I can run vlc without any problem. I can
watch a different camera on my Swann system via rtsp. It is this /dev/video(0) permission problem that is stopping it working with
the Zoneminder cameras.
can you show the output of "id" when logged in as davey
and again after running "su -"
Davey wrote:
"su -" wants a Password. Where do I find that? It won't accept mine,it's root's
obviously.
alternatively you could use "sudo su -" and your own password
Davey wrote:
"su -" wants a Password. Where do I find that? It won't accept mine, obviously.it's root's
alternatively you could use "sudo su -" and your own password
Davey <davey@example.invalid> wrote:
Ok, let's try the Euresys drivers. The one for the card is Multicam,
which I downloaded, followed the instructions for installation, and
it kept on failing for lack of something or other. Every attempt
prompted an Uninstall to clean the system. It wanted Memento, and
it actually said 'install Memento', but with no clue as to where to
find it. I eventually did, buried deep in the website, and
downloaded the documentation and installer for that. I tried to
install it, but it fails:
The first rule is never ever use vendor drivers, they are the route
to much pain and suffering.
Supposedly the chip supports the 'bttv' driver: https://www.linuxtv.org/wiki/index.php/Bttv
which in theory should work out of the box.
See:
https://www.kernel.org/doc/html/v4.14/media/v4l-drivers/index.html specifically the bttv section.
You might need to install a package containing the 'bttv.ko' kernel
module - you may need a linux-modules-extra-... package. eg to
install for your current kernel version:
$ sudo apt install linux-modules-extra-$(uname -r)
(you may need to repeat the command when your kernel version gets
updated, not sure if there's a way to keep them in sync)
Theo