Well I’ve set up another Arch system with camera attached and changing the gpu values was not needed.CatherineH wrote:I did this, and borked my installation (it just hangs at the raspberry pi image).
I'm guessing I was either supposed to install X first, or that I was supposed to comment out the other gpu_mem lines in config.txt... Any possible explanations would be helpful. Meanwhile I'm going to mount my SD card on another arch installation and see if can edit config.txt without borking it further.
Code: Select all
start_file = start_x.elf
Put it the module name into a file under /etc/modprobe.dSeiduna wrote:hello towolf,
oh man, thanks, driver loaded and shooting!
follow up Q on that, is there a way to do that on boot?
I think you need minimum 64Mbig time Q:
-how does gpu_mem efects camera module?
That snippet is talking about the *user space* v4l driver that was advertised here earlier. The official kernel mode driver is structured differently and it exposes most of the functionality of raspivid minus some special features like segmented writing or listening to trigger signals. Much of that can be achieved differently with software that supports V4L natively. For example, you can write segments using ffmpeg -f ssegment.-if I have camera module in /dev/video0 will ffmpeg lack behind raspivid (as stated here)?