-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
Kernel 6.6.47 changed the GPIO chip definition on Raspberry 5 and broke Seatalk1 #1788
Comments
Grrr :( I will add a check for kernel version (/proc/version, or Python's platform.version from a quick search). |
Why not make that configurable? |
IMO the issue is a bit too low-level to confront users with.. even having to select the GPIO library is already border-line. Seeing the error message reported in the OpenMarine forum, I think the simplest approach is to check for the file I will verify that with my Pi 5 later today. |
Ok, looks a bit more complicated. |
Agree, this is a lot to ask to users because there is not much information documenting this. It seems that there is a symlink /dev/gpiochip-rpi I will test this in different scenarios too. |
Unless they just introduced it, I don't think /dev/gpiochip-rpi is available on a stock Pi image. At least its not present on my non-updated Pi 5. |
@sailoog can you run this script on a system with the update?
on my non-updated Pi 5 it returns
|
I made a new image for the Pi 5. Of course, the script above doesn't work with gpiod v1.x. Here's the same script for v1.x:
on fresh new image, GPIO still is on gpiochip4:
My kernel version is 6.6.31.. will try to update that after lunch |
Ok, that was quicker than expected. After running rpi-update I'm on kernel 6.6.50, and
So yes, I can reproduce. |
Tested on Raspberry 4 and 5, kernel 6.6.47 (stable), gpiod 1 and 2. No issues. |
Fixed by #1789 |
In previous kernels the GPIO chip definition was "gpiochip0" for Raspberry Pi 4 and "gpiochip4" for Raspberry Pi 5. Now both are "gpiochip0" in latest kernel. Seatalk1 in Signal K is broken for Raspberry Pi 5 right now. We should just change this to get it working again:
signalk-server/packages/streams/gpiod-seatalk.js
Line 47 in febea55
Waiting for @astuder to wake up to confirm :)
The text was updated successfully, but these errors were encountered: