Qengineering / Qengineering/RPi-image
"ERROR: the system appears to be configured for the legacy camera stack"
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 138
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I wonder why tools like libcamera-hello do not work with the RPi-image. The libcamera-tools missing first, but I installed them with:
$ sudo apt install libcamera-apps
$ libcamera-hello
ERROR: the system appears to be configured for the legacy camera stack
In raspi-config, the camera is enabled. I also gave the GPU 256 MB memory in raspi-config.
$ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
/dev/video10
/dev/video11
/dev/video12
/dev/video18
bcm2835-isp (platform:bcm2835-isp):
/dev/video13
/dev/video14
/dev/video15
/dev/video16
mmal service 16.1 (platform:bcm2835-v4l2-0):
/dev/video0
It tried using the RasPi Camera module v2 and the RasPi HQ Camera module. But this does not change anything.
Has anyone here observed the same issue and/or an idea how to solve it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with libcamera-hello and inspect the camera setting in raspi-config. Compare the result with the devices reported by v4l2-ctl --list-devices; done means the Raspberry Pi camera modules work with the libcamera tools rather than reporting the legacy camera stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, raspberry-pi
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100