Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: somthing strange (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Mon, 5 Oct 2020 10:03:38 +0300
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] somthing strange
Message-ID:
<cachtdwto4hp1k+wpy+rgr50of+2mb8q9od7ca0dba6mwvsm...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
You wrote "4.3 is BROKEN", but if you really want to make sure the
version is broken or not, you have two options:
1. install 4.3.1 on your C2 (compile from sources or build deb package
https://github.com/Motion-Project/motion-packaging)
2. connect back the camera to XU4 and try to investigate "dmesg"
errors related to USB or uvcvideo
On Sat, Oct 3, 2020 at 10:24 PM Richard Bown <[email protected]> wrote:
>
> motion 4.0 not 4.9
>
> On 03/10/2020 20:14, Richard Bown wrote:
> > Hi not the easiest to do now as I disabled motion on the Odriod XU4
> > after installing motion 4.9 on the Odroid C2 (like a RPI3B+ )
> >
> > and moving all three cameras to tat device, the Odriod XU4 was running
> > ubuntu 18.04LTS but was giving problems with the Logitech c270.
> >
> > If power was lost at any time I had to keep power cycling the XU4
> > until the camera was recognised again.
> >
> > Hence one reason for moving it to Ubuntu 20.04LTS, Ubuntu18 was using
> > kernel 4.18, ubuntu20 uses kernel 5.4
> >
> > checked through /var/log
> >
> > at the end of dmesg.0 , which was at startup with the logitech C270
> > cam connected on the XU4
> >
> > 16.254326] kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825)
> > [ 16.374212] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Extension 4 was not initialized!
> > [ 16.374224] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Extension 6 was not initialized!
> > [ 16.374233] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Extension 7 was not initialized!
> > [ 16.374242] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Processing 2 was not initialized!
> > [ 16.374251] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Extension 3 was not initialized!
> > [ 16.374262] kernel: uvcvideo 3-1.1:1.0: Entity type for entity
> > Camera 1 was not initialized!
> > [ 16.375035] kernel: input: UVC Camera (046d:0825) as
> > /devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.8.auto/usb3/3-1/3-1.1/3-1.1:1.0/input/input1
> > [ 16.384878] kernel: usbcore: registered new interface driver uvcvideo
> > [ 16.384885] kernel: USB Video Class driver (1.1.1)
> > [ 17.649687] kernel: usb 3-1.1: set resolution quirk: cval->res = 384
> > [ 17.650117] kernel: usbcore: registered new interface driver
> > snd-usb-audio
> > [ 19.431607] kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link
> > becomes ready
> > [ 19.433111] kernel: r8152 6-1:1.0 eth0: carrier on
> > [ 23.970837] kernel: usb 3-1.1: reset high-speed USB device number 3
> > using xhci-hcd
> > [ 25.551673] kernel: fuse: init (API version 7.31)
> >
> > The Odroid XU4 is an Octal core ARM SBC, I checked dmesg.1.gz and that
> > is the same
> >
> > On the working Odroid C2 running motion v4.0 on Ubuntu18.04
> >
> > [ 12.554761] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825)
> > [ 12.577137] usbcore: registered new interface driver btusb
> > [ 12.652518] input: UVC Camera (046d:0825) as
> > /devices/dwc2_b/usb1/1-1/1-1.2/1-1.2:1.0/input/input2
> > [ 12.652764] usbcore: registered new interface driver uvcvideo
> > [ 12.652774] USB Video Class driver (1.1.1)
> >
> > On both machines motion is started as service
> >
> > I don't think Deb10 uses kernel 5 yet , last time I looked it was
> > still using kernel 4,
> >
> > I looked at that recently for another machine as mysql has a nasty
> > memory leak which has not been fixed on the version supplied with
> > ubuntu 20
> >
> > It has been partially fixed on the community version of mysql.
> >
> > Thanks
> >
> > HTH
> >
> > Richard
> >
> >
> >
> >
> > On 03/10/2020 19:16, tosiara wrote:
> >> Can you post output of dmesg on the XU4 right after trying to start
> >> motion there?
> >>
> >> On Sat, Oct 3, 2020, 16:16 Richard Bown <[email protected]
> >> <mailto:[email protected]>> wrote:
> >>
> >> The plot thickens
> >>
> >> I downloaded from the odroid ubuntu 18 repo v4.0, on a Odroid C2,
> >> like a
> >> RPi3B
> >>
> >> and
> >>
> >> ------------------------
> >> cap.driver: "uvcvideo"
> >> cap.card: "UVC Camera (046d:0825)"
> >> cap.bus_info: "usb-dwc2_b-1.2"
> >> cap.capabilities=0x84000001
> >> ------------------------
> >> [0:web_control] [NTC] [STR] [Oct 03 13:52:13] httpd_run: Started
> >> motion-httpd server on port 8080 (auth Disabled)
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_get_capability: -
> >> VIDEO_CAPTURE
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_get_capability: -
> >> STREAMING
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_select_input: name =
> >> "Camera
> >> 1", type 0x00000002, status 00000000
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_select_input: - CAMERA
> >> [1:ml1] [WRN] [VID] [Oct 03 13:52:13] v4l2_select_input: Device
> >> doesn't
> >> support VIDIOC_G_STD
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: Config
> >> palette index 17 (YU12) doesn't work.
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: Supported
> >> palettes:
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: (0)
> >> YUYV (YUV
> >> 4:2:2 (YUYV))
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: 0 - YUV
> >> 4:2:2
> >> (YUYV) (compressed : 0) (0x56595559)
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: (1)
> >> MJPG (MJPEG)
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format: 1 - MJPEG
> >> (compressed : 1) (0x47504a4d)
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_set_pix_format Selected
> >> palette YUYV
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_do_set_pix_format:
> >> Testing
> >> palette YUYV (320x240)
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_do_set_pix_format: Using
> >> palette YUYV (320x240) bytesperlines 640 sizeimage 153600 colorspace
> >> 00000008
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: found
> >> control
> >> 0x00980900, "Brightness", range 0,255
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls:
> >> "Brightness",
> >> default -8193, current 128
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: found
> >> control
> >> 0x00980901, "Contrast", range 0,255
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls:
> >> "Contrast",
> >> default 57343, current 32
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: found
> >> control
> >> 0x00980902, "Saturation", range 0,255
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls:
> >> "Saturation",
> >> default 57343, current 32
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: found
> >> control
> >> 0x00980918, "Power Line Frequency", range 0,2
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: "Power
> >> Line
> >> Frequency", default 2, current 2
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: found
> >> control
> >> 0x00980913, "Gain", range 0,255
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] v4l2_scan_controls: "Gain",
> >> default 57343, current 0
> >> [1:ml1] [NTC] [VID] [Oct 03 13:52:13] vid_v4lx_start: Using V4L2
> >> [1:ml1] [NTC] [ALL] [Oct 03 13:52:13] image_ring_resize: Resizing
> >> pre_capture buffer to 1 items
> >> [1:ml1] [NTC] [STR] [Oct 03 13:52:14] http_bindsock: listening on
> >> any
> >> IPv4 address port 8081
> >> [1:ml1] [NTC] [ALL] [Oct 03 13:52:14] motion_init: Started
> >> motion-stream
> >> server on port 8081 (auth Disabled)
> >>
> >>
> >>
> >> So now it move all the config from the XU4 SBC on to an old Odroid
> >> C2 ,
> >> which I use for Kodi, I've only got 22GB of mem on that SBC
> >>
> >> so I will have to be careful on file storage , so v 4.3 is BROKEN
> >>
> >> Richard
> >>
> >>
> >> On 03/10/2020 12:15, Richard Bown wrote:
> >> > HI Chuck
> >> >
> >> > log level set to 7
> >> >
> >> > [0:motion] [NTC] [ALL] [Oct 03 12:03:01] main: Motion thread 1
> >> restart
> >> > [0:motion] [NTC] [ALL] [Oct 03 12:03:01] motion_start_thread:
> >> Camera
> >> > ID: 1 is from /etc/motion/camera2.conf
> >> > [0:motion] [NTC] [ALL] [Oct 03 12:03:01] motion_start_thread:
> >> Camera
> >> > ID: 1 Camera Name: (null) Device: /dev/video0
> >> > [1:ml1] [NTC] [ALL] [Oct 03 12:03:01] motion_init: Camera 1
> >> started:
> >> > motion detection Enabled
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:01] vid_start: Opening V4L2
> >> device
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:01] v4l2_device_open: Using
> >> > videodevice /dev/video0 and input -1
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:01] v4l2_device_capability: -
> >> STREAMING
> >> > [1:ml1] [ERR] [VID] [Oct 03 12:03:01] v4l2_device_capability:
> >> Device
> >> > does not support capturing.
> >> > [1:ml1] [ERR] [VID] [Oct 03 12:03:01] vid_start: V4L2 device
> >> failed to
> >> > open
> >> > [1:ml1] [WRN] [ALL] [Oct 03 12:03:01] motion_init: Could not fetch
> >> > initial image from camera
> >> > [1:ml1] [WRN] [ALL] [Oct 03 12:03:01] motion_init: Motion
> >> continues
> >> > using width and height from config file(s)
> >> > [1:ml1] [NTC] [ALL] [Oct 03 12:03:01] image_ring_resize: Resizing
> >> > pre_capture buffer to 1 items
> >> > [1:ml1] [NTC] [ALL] [Oct 03 12:03:01] image_ring_resize: Resizing
> >> > pre_capture buffer to 4 items
> >> > [1:ml1] [WRN] [ALL] [Oct 03 12:03:10] mlp_retry: Retrying until
> >> > successful connection with camera
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:10] vid_start: Opening V4L2
> >> device
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:10] v4l2_device_open: Using
> >> > videodevice /dev/video0 and input -1
> >> > [1:ml1] [NTC] [VID] [Oct 03 12:03:10] v4l2_device_capability: -
> >> STREAMING
> >> > [1:ml1] [ERR] [VID] [Oct 03 12:03:10] v4l2_device_capability:
> >> Device
> >> > does not support capturing.
> >> > [1:ml1] [ERR] [VID] [Oct 03 12:03:10] vid_start: V4L2 device
> >> failed to
> >> > open
> >> >
> >> > Camera work fine on the laptop with the other linux programs
> >> >
> >> > I'm beginning to wonder if motion has changed and is now asking
> >> the
> >> > camrea to do something it cant whereas before
> >> >
> >> > it would accept the stream, looks like its now telling the
> >> camera to
> >> > capture and failing , very weird
> >> >
> >> > Richard
> >> >
> >> > On 03/10/2020 11:52, chuck elliot wrote:
> >> >> You could try upping the log level to get more clues
> >> >>
> >> >> as to what is happening... I assume that you've checked that
> >> >>
> >> >> videodevice is set to /dev/video0?
> >> >>
> >> >> Will the camera work with xawtv or cheese etc?
> >> >>
> >> >>
> >> >>
> >> >> On 03/10/2020 10:43 am, Richard Bown wrote:
> >> >>> Thanks Chuck
> >> >>>
> >> >>> Just tried that and still not playing, it has been working for a
> >> >>> couple of years +
> >> >>>
> >> >>> I can plug the C270 in to the USB skt on the laptop which is
> >> running
> >> >>> Linux Mint 20, which is based on Ubuntu 20.04LTS
> >> >>>
> >> >>> which is what the Odroid XU4 SBC is running, it was playing up
> >> >>> before the OS was upgraded from ubuntu 18.04LTS to ubuntu
> >> 20.04LTS
> >> >>>
> >> >>> odroid@odroid:~$ lsusb
> >> >>>
> >> >>> Bus 003 Device 003: ID 046d:0825 Logitech, Inc. Webcam C270
> >> >>>
> >> >>> odroid@odroid:~$ tail /var/log/motion/motion.log
> >> >>> [1:ml1] [WRN] [ALL] [Oct 03 10:22:10] mlp_retry: Retrying until
> >> >>> successful connection with camera
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:10] v4l2_device_capability:
> >> Device
> >> >>> does not support capturing.
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:10] vid_start: V4L2 device
> >> failed
> >> >>> to open
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:11] v4l2_device_capability:
> >> Device
> >> >>> does not support capturing.
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:11] vid_start: V4L2 device
> >> failed
> >> >>> to open
> >> >>> [1:ml1] [WRN] [ALL] [Oct 03 10:22:11] motion_init: Could not
> >> fetch
> >> >>> initial image from camera
> >> >>> [1:ml1] [WRN] [ALL] [Oct 03 10:22:11] motion_init: Motion
> >> continues
> >> >>> using width and height from config file(s)
> >> >>> [1:ml1] [WRN] [ALL] [Oct 03 10:22:20] mlp_retry: Retrying until
> >> >>> successful connection with camera
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:20] v4l2_device_capability:
> >> Device
> >> >>> does not support capturing.
> >> >>> [1:ml1] [ERR] [VID] [Oct 03 10:22:20] vid_start: V4L2 device
> >> failed
> >> >>> to open
> >> >>> odroid@odroid:~$ ps ax|grep motion
> >> >>> 753 ? SLsl 0:09 /usr/bin/motion -d 5 -n -c
> >> >>> /etc/motion/motion.conf
> >> >>> odroid@odroid:~$ id odroid
> >> >>> uid=1000(odroid) gid=1000(odroid)
> >> >>>
> >> groups=1000(odroid),4(adm),5(tty),6(disk),7(lp),15(kmem),20(dialout),21(fax),22(voice),24(cdrom),25(floppy),27(sudo),29(audio),37(operator),44(video),46(plugdev),
> >> >>>
> >> >>>
> >> 50(staff),60(games),100(users),104(input),105(crontab),108(ssh),109(netdev),112(bluetooth),114(lightdm),115(nopasswdlogin),117(nm-openvpn),118(lpadmin),120(scanner),123(pulse),124(pulse-access)
> >>
> >> >>>
> >> >>>
> >> >>> odroid@odroid:~$ ls -l /dev/video0
> >> >>> crw-rw----+ 1 root video 81, 0 Oct 3 10:13 /dev/video0
> >> >>>
> >> >>> I'm pulling my hair out with this one, I cant see any reason why
> >> >>> this has stopped working, the SBC has 3 USB ports, all have
> >> been tried.
> >> >>>
> >> >>> Motion is started as a service, so its not running as a user
> >> >>>
> >> >>> any ideas why?
> >> >>>
> >> >>> This cam is needed as it covers the front door
> >> >>>
> >> >>> TIA Richard
> >> >>>
> >> >>> On 03/10/2020 09:39, chuck elliot wrote:
> >> >>>> I have same camera. If you run motion without the
> >> >>>>
> >> >>>> palette setting it chooses type 1 (MJPG) saying 0 is
> >> >>>>
> >> >>>> also compatible. This works fine.
> >> >>>>
> >> >>>> CE
> >> >>>>
> >> >>>>
> >> >>>> On 03/10/2020 9:13 am, Richard Bown wrote:
> >> >>>>> motion v 4.3.1
> >> >>>>>
> >> >>>>> I have a logitech 270 usb camera
> >> >>>>>
> >> >>>>> up to recently its been working fine
> >> >>>>>
> >> >>>>> on v4l2_pallete 8
> >> >>>>>
> >> >>>>> but now if I reboot or a power failure its a pig to get
> >> video from
> >> >>>>> it with motion
> >> >>>>>
> >> >>>>> ,using a Odroid XU4 octal core ARM SBC and its headless, so
> >> all
> >> >>>>> video from it it on the http ports
> >> >>>>>
> >> >>>>> once its running its fine, sometimes fixed by power cycling
> >> the
> >> >>>>> SBC , which I dont like doing
> >> >>>>>
> >> >>>>> Am I using the correct v4l2 pallette for this USB camera.
> >> >>>>>
> >> >>>>> OS on the SBC is ubuntu 20.04LTS
> >> >>>>>
> >> >>>>> any ideas
> >> >>>>>
> >> >>>>> on the video feed via http its just the grey screen with
> >> "unable
> >> >>>>> to open video device"
> >> >>>>>
> >> >>>>>
> >> >>>>> Thanks
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>> _______________________________________________
> >> >>>> Motion-user mailing list
> >> >>>> [email protected]
> >> <mailto:[email protected]>
> >> >>>> https://lists.sourceforge.net/lists/listinfo/motion-user
> >> >>>> https://motion-project.github.io/
> >> >>>>
> >> >>>> Unsubscribe:
> >> https://lists.sourceforge.net/lists/options/motion-user
> >> >>>
> >> -- Best wishes /73
> >> Richard Bown
> >>
> >> Email : [email protected] <mailto:[email protected]>
> >>
> >> HTTP : http://www.g8jvm.com
> >>
> >> ######################################################################
> >>
> >> Ham Call: G8JVM . QRV: 50-432 MHz + Microwave
> >> Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
> >> QRV 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W,
> >> Microwave 1296MHz 110W, 2320MHz 100W, 5760MHz 10W & 10368MHz 5W
> >> OS: Linux Mint 19.3 x86_64 Tricia, on a Dell Inspiron 3580 laptop
> >> ######################################################################
> >>
> >>
> >>
> >> _______________________________________________
> >> Motion-user mailing list
> >> [email protected]
> >> <mailto:[email protected]>
> >> https://lists.sourceforge.net/lists/listinfo/motion-user
> >> https://motion-project.github.io/
> >>
> >> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> >>
> >>
> >>
> >> _______________________________________________
> >> Motion-user mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/motion-user
> >> https://motion-project.github.io/
> >>
> >> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> >
> --
> Best wishes /73
> Richard Bown
>
> Email : [email protected]
>
> HTTP : http://www.g8jvm.com
>
> ######################################################################
>
> Ham Call: G8JVM . QRV: 50-432 MHz + Microwave
> Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
> QRV 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W,
> Microwave 1296MHz 110W, 2320MHz 100W, 5760MHz 10W & 10368MHz 5W
> OS: Linux Mint 19.3 x86_64 Tricia, on a Dell Inspiron 3580 laptop
> ######################################################################
>
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 172, Issue 5
*******************************************
