search

motioneye-project / motioneye

A web frontend for the motion daemon.
GNU General Public License v3.0
3.95k stars 650 forks source link

Pi 4b Cam not detected #1939

Closed DPBiff closed 3 years ago

DPBiff commented 3 years ago

I have turned my brain to mush trying to get this sorted.

I own a RPi 4b, 8Gram, 129Gb, SD SanDisk, Arducam 1/4 Inch 5 Megapixels Sensor Camera Module with Flex Cable for Raspberry Pi Model A/B/B+, Pi 2 and Raspberry Pi 3, 3B+, 4 OS: Buster cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian

I have:

Installing motioneye myself results in a failure to create a web interface Installing Docker motioneye results in a web interface that can't find a cam Installing motioneye via pp results in a failure to create a web interface

Results of motion -h: motion Version 4.2.2, Copyright 2000-2019 Jeroen Vreeken/Folkert van Heusden/Kenneth Lavrsen/Motion-Project maintainers

Raspi-config: cam enabled

Raspistill captures .jpg

Raspivid captures video

Motion captures video

ls /dev/video* returns: ls /dev/video01

vcgencmd get_camera returns: supported=1 detected=1

network: wifi and / or ethernet

sudo rpi-eeprom-update

I've run out of ideas -- help? Please?

DPBiff commented 3 years ago

Ok, always grateful for the help & suggestions... I have purchased a new 64Gb sdcard, installed a fresh install of Raspbian, and a fresh install of Motioneye. It works. It works just fine. I have concluded that there must be some other piece of software on the original install that's grabbing control of the camera. The only other significant piece of s/w I have going is Openplotter. OP includes:

starbasessd commented 3 years ago

Did you enable the camera in raspi-config?

On Wed, Nov 4, 2020 at 6:09 PM DPBiff notifications@github.com wrote:

Ok, always grateful for the help & suggestions... I have purchased a new 64Gb sdcard, installed a fresh install of Raspbian, and a fresh install of Motioneye. It works. It works just fine. I have concluded that there must be some other piece of software on the original install that's grabbing control of the camera. The only other significant piece of s/w I have going is Openplotter. OP includes:

  • I2c
  • CAN bus
  • Signal K
  • SDR VHF
  • AIS
  • ADS-B
  • CQRX
  • DAV
  • DBTV Does that ring any bells for anyone?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneye/issues/1939#issuecomment-722023329, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHPRTAY4VZWYRPUUJNDSOHNI5ANCNFSM4TFS7KRA .

-- Thanks

Kevin Shumaker

Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel

N38° 19' 56.52" W85° 45' 8.56"

Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?

DPBiff commented 3 years ago

Did you enable the camera in raspi-config? As noted in the OP, yes.

I have, in the mean time, figured it out. It was an install issue.

Before anyone suggests that I didn't run pip as sudo - - - - I did. Something went hinky in the install but addressing the errors thrown when running "systemctl status motioneye" did the trick.