-
Notifications
You must be signed in to change notification settings - Fork 2
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
Potential issues with Elixir 1.9 or Nerves 1.5 #2
Comments
That's not good. The display width and height look suspicious in the log messages. Maybe a clue? |
I got a minimal test-case that seems to confirm it as part of 1.8 -> 1.9 or OTP 21 to 22. |
Clean nerves-project on Erlang 22.0 and Elixir 1.9 OTP 22. Just added the RpiFbCapture dependency and then I just pushed the firmware and ran from iex:
|
Ah, RingLogger gave me a bit more story:
|
I can reproduce. I've narrowed it down to the rpi-firmware version update from https://github.com/raspberrypi/firmware. Cherry-picking through releases now... |
This is the commit that where I start getting "Unable to open primary display": raspberrypi/firmware@64b5649. It could be that there's some setting or something that we need to do now. |
Apparently it works better with the latest: raspberrypi/firmware@38e81f2. The "Unable to open primary display" message goes away. There's a scenic error with no info for me now - may be unrelated. |
This fixes an error from vc_dispmanx_display_open. See pappersverk/rpi_fb_capture#2 for details.
Ok, things seem to work. After a clean build the scenic error went away. I made a nerves_system_br update (v1.8.5) with the fix. You can create a custom nerves_system_rpi0 and bump the version of nerves_system_br in it to get the fix. Or you can wait. I think that it will take a day or two to get new official system releases out. |
I'll wait for the release. Good job :) |
I had a user get in touch about some issues with our Inky scenic driver which uses this where this module would end up sending a crash message because the port crashed.
I haven't confirmed that this is related to the updates but I figured I'd give a heads up in case you have something off of the top of your head about what might cause such an issue. Otherwise I'll follow up if I get more info.
I received this log:
The text was updated successfully, but these errors were encountered: