After running libcamera-hello I've always this error (I've Raspbian GNU/Linux 11 (bullseye))
Made X/EGL preview window
[0:01:17.403440281] [1320] INFO Camera camera_manager.cpp:293 libcamera v0.0.0
ERROR: *** no cameras available ***
What can I edit on config.txt !! Is there any modification on raspi-config???
I don't know if you have already checked the issue in the repository, I attach it just in case, anyway I will make a summary:
verify that your system detects the camera with the command sudo vcgencmd get_camera.
in the /boot/config.txt file remove the # or add the following
dtoverlay=vc4-fkms-v3d
dtoverlay=imx219
Reboot your Raspberry
Good luck
Issue: https://github.com/raspberrypi/libcamera-apps/issues/125
I manage to resolve this problem finally:
so if you've debian bullseye raspberry pi os First install the camera software and drivers if they don't exist then in config.txt: check that you uncomment camera_auto_detect=1 and add dtoverlay=vc4-kms-v3d
In interface options if you run sudo raspi-config: do not enable the lagacy camera but navigate to Advanced Options and enable Glamor graphic acceleration then reboot
If you run sudo vcgencmd get_camera it's unneeded to detect you camera with this command it's not neccesary with bullseye version
Related
I tried to install the FLIR Lepton library on Raspberry Pi zero w but as i was theFLIR Lepton (sudo apt-get install qt4-dev-tools)in pi this error message show up
Get:105 http://archive.raspberrypi.org/debian buster/main armhf vlc-plugin-video-splitter armhf 3.0.12-0+deb10u1+rpt1 [140 kB]
Get:106 http://archive.raspberrypi.org/debian buster/main armhf vlc-plugin-visualization armhf 3.0.12-0+deb10u1+rpt1 [142 kB]
E: Failed to fetch http://mirror1.ku.ac.th/raspbian/raspbian/pool/main/b/base-files/base-files_10.3+rpi1+deb10u8_armhf.deb 404 Not Found [IP: ---------]
E: Failed to fetch http://mirror1.ku.ac.th/raspbian/raspbian/pool/main/s/systemd/systemd-sysv_241-7~deb10u6+rpi1_armhf.deb 404 Not Found [IP: ---------]
this is an example there are 100+ line of these
as i trying to troubleshoot the error i found out that not just the upgrading that has an error. there is the same 404 error with upgrade and update as well. Is there any problem with the raspberry pi or maybe my internet?
PS. The raspberry pi is brand new, and i use ssh to connect to the raspberry pi
PS.2 I just reinstall the OS the result is the same
PS.3 I randomly choose the link in the terminal. it direct me in to the ERROR 404 web as well
1 . Erase the sdcard you are using (if it is not carrying some data you don't want to lose)
2. Download a previous version of pios or upgrade the current one
my answer is that there are some problem in mirror1.ku what i need to do is go to
sudo nano /etc/apt/sources.list
then add
deb http://mirror1.ku.ac.th/raspbian buster main contrib non-free rpi
in the last line then its all fine. the reason is that my raspberry is redirecting into the wrong directory and that's the reason for 404 error
This is because your raspberry is not updated, still pointing to old repos. For fix it you should update it, you can follow the instructions here. After that all work as expected for me and not more 404. raspberrypi.com/documentation/computers/os.html
A fastest and safest way is: installing a new LTS OS rather than trying to fix a lot of issues on that obsolete/outdated raspbian OS. Ubuntu for Raspberry Pi is the best choice (very long time support). It takes around 5-8 minutes to download and install the OS.
Backup important data on your Pi.
Use your laptop/PC, download 1GB Ubuntu server image.
Use application Raspberry Pi Imager to burn the image to your SD card with pre-configured wifi, SSH key, username/password.
Plug SD card to your Pi and enjoy.
I drill down to the folder where bfgminer.exe lives on my Raspberry Pi with Raspbian OS and issue this command:
screen -S Mining .bfgminer –o http://mint.bitminter.com:3333 –u username.myname –p 123
I get a command not found message. I have tried everything I can think of to get the syntax correct. Where am I going wrong
You need to install screen if it's not installed by default:
sudo apt-get install screen
After I used apt-get upgrade earlier today, my Raspberry Pi (Raspbian Jessie) stopped being able to automount my external harddrives anymore. Automounting worked perfectly fine before apt-get upgrade, but now I can't even manually mount my external HDDs anymore.
This is the error message I received:
pi#raspberrypi:~ $ sudo mount /dev/sda1 /mnt
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.26-v7+/modules.dep.bin'
ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root
'modprobe fuse' gives me the same error message:
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.26-v7+/modules.dep.bin'
I reinstalled the kernel and bootloader using this command:
sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel
But this did not help.
From reading other forum posts, it may look like my kernel and fuse might not be compatible - but how would that have happened? I feel I'm a bit out of my depth here.
Some forum posts suggested a restart will help, but this didn't solve the issue for me.
Alternatively, I also found a post from drownboat on Reddit from two years ago that looks promising - but to be honest, I have no idea if this is just another red herring or if this is indeed the problem I'm facing. In any case, I'm not sure what exactly/how drownboat did it:
I suspect that what is happening is that updates to the kernel and
grub config are being written to the /boot folder, but not onto the
boot device. This has caused the modules and the kernel to go out of
sync. [...]
I fixed it by adding /boot back to /etc/fstab, rebooting to another kernel where the modules were still working, thus mounting /boot, and finally reinstalling apt-get install --reinstall linux-image-3.16.0-4-amd64.
I would greatly appreciate any help!
Some more info:
uname -a
Linux raspberrypi 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016
armv7l GNU/Linux
dpkg -s fuse
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 103
Maintainer: Laszlo Boszormenyi (GCS)
Architecture: armhf
Version: 2.9.3-15+deb8u2
Depends: libc6 (>= 2.4), libfuse2 (= 2.9.3-15+deb8u2), adduser, mount (>= 2.19.1), sed (>= 4), udev | makedev
Conffiles:
/etc/fuse.conf 298587592c8444196833f317def414f2
Description: Filesystem in Userspace
Filesystem in Userspace (FUSE) is a simple interface for userspace programs to
export a virtual filesystem to the Linux kernel. It also aims to provide a
secure method for non privileged users to create and mount their own filesystem
implementations.
Homepage: http://fuse.sourceforge.net/
I FOUND THE SOLUTION (see further below for details)! It turned out that the boot partition was not mounted and the operating system reverted to the old kernel before the apt-get upgrade. So I just had to make sure that /boot was automounted at startup so the correct kernel was used.
Further steps in my error analysis ():
OK so I managed to fix the issue myself. It really just turned out that the /boot partition was not mounted and thus my Raspberry Pi reverted to the old kernel instead of the fancy new one that came with apt-get upgrade.
I found the problem by using uname -r, which gave me '4.9.35-v7+' as an answer. This was strange because the original error message had a different version number:
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could
not open moddep file '/lib/modules/4.4.26-v7+/modules.dep.bin'
(My emphasis)
When I navigated to /lib/modules using cd /lib/modules I also saw this:
pi#raspberrypi:/lib/modules $ ls
4.9.35+ 4.9.35-v7+
So the error message about a fuse device missing really seemed to have something to do with a mismatch of kernel and fuse versions. The discrepancy between version numbers led me to believe that the wrong kernel was being used (like drownboat also stated in their Reddit post two years ago).
This is how I fixed the problem (SOLUTION):
sudo nano /etc/fstab/
Then I added the following lines to fstab:
# automount /boot partition at startup
/dev/mmcblk0p6 /boot vfat defaults 0 2
After rebooting, I used sudo raspi-config to check if the boot partition was mounted properly (raspi-config will only let you enter its menu if the partition is mounted, otherwise it will tell you that you need to mount the boot partition first).
Then I ran sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel again to doubly ensure that the latest kernel was installed on the boot partition too - but I don't know if this was a crucial step.
Finally, after another restart, I was able to mount/automount my external harddrives again.
Hope this helps anyone else out there having the same issue as me! :)
In my situation, the solution is pretty simple.
I run apt update and apt upgrade -y and then apt install ntfs-3g, after these, I try to mount the disk and met this error.
The solution is just reboot
After reboot, try to mount again, and thing worked well.
I had the same issue trying to get Open Media Vault working. There were missing or unmatched kernel files, outdated libraries etc. I ran the updates in the link below and got it working.
Update system's package list
sudo apt-get update
upgrade all installed packages to their latest versions:
sudo apt-get dist-upgrade
https://www.raspberrypi.org/documentation/raspbian/updating.md
I had this problem trying to mount a FAT32 USB on Buster Lite with
pmount /dev/disk/by-label/<my-usb-label>
The messages implied the system was trying to mount an ntfs device. 'NTFS signature missing' etc.
Before trying anything clever, I tried #Kenneth's suggestion of a reboot. It fixed the problem.
Worrying to see Linux behaving like Windows 8-{
Crash after kernel upgrading
apt-get update & dist-upgrade
impossible to mount ntfs usb disk
modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.87-v7+
ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root
Thanks a lot for this workaround :
sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel
I am working on raspberry pi B. OS is rasbian and ı have installed ros indigo using this tutorials on raspberry pi. Now ı want to work with raspberry pi + kinect. When ı run
roslaunch openni_launch openni.launch
ı had an error like this
[openni.launch] is neither a launch file in package [openni_launch] nor is [openni_launch] a launch file name The traceback for the exception was written to the log file
Then ı try to install openni but ı had an error is below.
pi#raspberrypi ~ $ sudo apt-get install ros-indigo-openni-kinect
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ros-indigo-openni-kinect
How can ı run kinect on raspberry pi. pls help??
You could have had a look at ROS Answer before asking.
Anyway, as it is explained there, openni-kinect is deprecated and it is suggested to use openni-launch instead.
To install this package:
sudo apt-get install ros-indigo-openni-launch
The only solution I know to get the kinect working on the Raspberry pi? You can retrieve the depth map and the rgb matrix with this library, basically all you need.
Check this out:
https://github.com/xxorde/librekinect
Maybe StackEchange is a friendly zone but in this case ROS answer is the most suited place to ask.
I have the beaglebone connected to my PC running virtual Ubuntu (12.10) via VMware. I tried to debug my C++ codes on beaglebone using Eclipse (Version 3.8).
I followed the youtube video :http://www.youtube.com/watch?v=vFv_-ykLppo. But I was not able to get the debugging work properly. Can somebody help me?
Below is what I did and what I got. Note: My host PC's IP is 192.168.1.105. The beaglebone's IP is 192.168.102.
Beaglebone is conntec to PC through USB and ethernet. I was able to open the connection with Beaglebone in the embedded terminals of Eclipse.
I successfully installed gdb-multiarch in my local PC by entering this command in the PC's terminal: sudo apt-get install gdb-multiarch.
I successfully installed gdbserver on beaglebone by entering this command in the beaglebone's terminal : sudo apt-get install gdbserver
I CD to the application folder and entered this command in the beaglebone's terminal: gdbserver [hostPC's IP]:12346 HelloWorldTest4
I got this response:
Processing HelloWorldTest4 created; pid=1035
Listening on port 12346
In Eclipse, I go to Run->Debug Configurations->, Below is what I configured and they are also shown in the attached screen shots.
Main - > Build(if required ) before launching: Build configurations: Debug; Use workspacesettings
Debugger-> Main-> GDB debugger: gdb-multiarch
GDB command file : .gdbinit
Debugger-> Gdbserver Settings-> Gdbserver name: [beaglebone's IP address]
Port number :12346
Then I clicked Debug, I got the following errors.
POP-UP windows: 'Launching HelloWorldTest4 Debug' has encountered a problem. Error in final launch sequence:
In Console: warning: Architecture rejected target-supplied description
Questions:
1. Is this problem related to gdb-multiarch? How to fix it?
2. Is my IP addresses specified corectly?
Thank you in advance.
I fixed the same problem by creating a .gdbinit file with the following content in my project folder:
set architecture arm
then point the Debug Configuration -> Debugger -> GDB command file entry to this new .gdbinit file and debug
I also had same problem,
I download gdb source code, recompiled for target arm, and copy gdb to arm-linux-gnueabi-gdb and in eclipese I changed gdb to arm-linux-gnueabi-gdb. And everything started working.
get gdb (7.8) sources and extract them
./configure --target=arm-none-linux-gnueabi --with-expat=/usr/local/lib/
make
cd gdb/gdbserver
/configure --host=arm-none-linux-gnueabi --with-expat=/usr/local/lib/
make