On 10/04/2019 22:02, Freek de Kruijf wrote:
> Op woensdag 10 april 2019 16:22:06 CEST schreef Matthias Brugger:
>> On 10/04/2019 12:36, Freek de Kruijf wrote:
>>> Op donderdag 4 april 2019 21:01:07 CEST schreef Freek de Kruijf:
>>>> I searched on the Internet for the answer. Did not find even the
>>>> question.
>>>>
>>>> Is there any support for a Raspberry Pi camera, bcm2835, on a Rasphberry
>>>> Pi
>>>> in an openSUSE system?
>>>
>>> Started with the latest Tumbleweed image for the Raspberry Pi 3B
>>> (aarch64).
>>> This one contains kernel version 4.20.13-1.1.
>>> Did find some information, even found that the kernel module bcm2835-v4l2
>>> is present in the kernel-default package.
>>> Also found that gpu_mem in /boot/efi/config.txt needs to be at least 128.
>>> Did give the command "modprobe -i bcm2835-v4l2 which indeed loaded the
>>> module together with other modules.
>>> However got the warning:
>>> bcm2835_v4l2: module is from the staging directory, the quality is
>>> unknown,
>>> you have been warned.
>>> And the error messages:
>>> bcm2835-v4l2: error -1 while loading driver
>>> bcm2835-camera: probe of bcm2835-camera failed with error -1
>>
>> I had a quick glance at the source and it is not clear to me where this
>> error comes from. You could try to install the kernel from our Kernel:HEAD
>> repository and retry:
>> https://download.opensuse.org/repositories/Kernel:/HEAD/ARM/
> 
> Still the same problem. Output:
> media: Linux media interface: v0.10
> videodev: Linux video capture interface: v2.00
> bcm2835_v4l2: module is from the staging directory, the quality is unknown, 
> you have been warned.
> bcm2835_v4l2: vchiq_mmal_component_init: failed to create component -1 (Not 
> enough GPU mem?)
> bcm2835-v4l2: bcm2835_mmal_probe: mmal init failed: -1
> bcm2835-camera: probe of bcm2835-camera failed with error -1

Well that give us at least some more hints. :)

> 
> Before installation of kernel-default-5.1.rc4-1.1.g1478096 I changed gpu_mem 
> to 128, however it was back to 32 afterwards. So I changed it first to 128 
> and 
> later 192 (max). Did not help.

How did you changed it? What do you mean with "it was back to 32 afterwards"?

Regards,
Matthias
-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Reply via email to