-
Notifications
You must be signed in to change notification settings - Fork 924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v4l2-related tracedump appears in kernel log (dmesg) during boot #3306
Comments
What kernel version have you tested with on Raspberry Pi OS? It's a shot in the dark but you can try the latest dev build to see if it's resolved - it is using Linux 6.6.20, which should be the same the current Pi OS is using. Also, how do you use the camera? I think it won't work out of the box without any changes in |
Thank you for your response.
HA OS: I'll try to extract and replace required files in
As per https://gist.github.com/enegaard/a57af286205914bd912270c89650fb1b I added the following lines to
In Raspbian
I cannot reproduce the same in HA OS:
|
Replacing the files in the startup partition resulted in a boot loop so I went with a fresh install on another SD card. The tracedump is gone, it even seems that picamera is recognized:
But unfortunately neither |
Describe the issue you are experiencing
During boot process the system logs the following lines:
The message repeats several times. I think this may be the reason why HA OS is not detecting a locally connected Pi camera while it works fine in the latest Raspbian on the same board.
What operating system image do you use?
rpi5-64 (Raspberry Pi 5 64-bit OS)
What version of Home Assistant Operating System is installed?
12.2
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Boot the system, check the logs.
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: