-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
RasPi Official Display #28
Comments
My hypothesis: You didn't properly shut down the virtual machine. When your Pi tried to shutdown, it took a long time to do so because a default shutdown under SystemD waits for 3 minutes before forcibly unmounting a disk. My suggestion: Before shutting down your Pi, be sure to properly shut down the virtual machine first. There are several ways to do this:
Improper ways to shutdown the virtual machine:
If you forget to properly shutdown vdesktop, it's no big deal. This has happened to me too. I just give my Pi a good 5 minutes to shutdown and it's usually finished by then. |
I did it in the blue terminal. If you watch the video it shows that I type |
I apologize for misunderstanding. Earlier I was unable to watch the video, but this time it played for me. Unfortunately, I am unable to test this myself because I didn't bring a RPi display with me on this trip. As I said, it seems like a /dev device is being mounted to the vm, that is capable of manipulating the GPIO. For others this may be a "feature", but for you it's turned out to be a bug. As I don't have my RPi display with me, I cannot narrow down which bind-mount is allowing this to happen. But you can. For starters, let's try disabling all kernel devices. Please replace the entire contents of the
Try booting your image again, then shut it down, and see if your RPi display still went black. If it did, then the problem lies elsewhere. But if your RPi display remains lit, then congratulations - we've located the proximity of the problem. You could stop here, or you could add back one kernel device mount at a time to figure out which one is causing the problem. |
Not a problem. I just wanted to make sure I did it in the correct terminal. I will have to test that tomorrow or the next day at work. It could be the gpio are getting a turn off signal for an instant to turn the display off but I also wonder if the pi official display has a signal wire (like how some HDMI TV’s can be powered off from the receivers because of HDMI signal pin, for example my old TV could be turned off from my Roku using the TV off option on the Roku and not using the TV remote https://support.roku.com/article/360037934914).
This weird experience makes me wonder if the display cable could be just an HDMI but as a ribbon cable and has the ability to be turned off from a signal. As I said before I’ll try it out tomorrow at work. |
Replacing the file contents with: Did work! Would you like me to try anything else to see if we can find the problem? I did backup the original nspawn file. |
Excellent! I'm relieved that turned out to be the problem. Otherwise, I would have not known where else to look.
Yes please. As-is, without any kernel devices being mounted, a lot of things won't work. For example, the browser, audio, usb devices, shared memory, and hardware acceleration will not work. It would be great if we could narrow down exactly which bind-mount is the troublemaker. To do that, one line needs to be re-added to the file at a time. For convenience, the original nspawn script is located on Github here. To save time, I suggest starting with this nspawn file:
I went through each entry and don't believe any of these entries are capable of manipulating the GPIO or the display cable. |
The script did not turn off the display. It did recognize it though. I also found a blog post that might help:
|
When I was testing this out, It worked great so far but one major problem I ran into is the official Raspberry Pi Display.
I made and img of the SD card and then did the shrink and tried doing the boot option.
This worked and the img booted. Then I went and tried to shutdown the booted img and it turned the raspberry pi official display off. Then when I tried launching it again the display didn't turn on. Next on the pi itself I did a reboot and the display turned back on. The weird part was that through VNC I could still see the desktop and everything but the official pi display was black.
https://drive.google.com/file/d/1hGUlwbbAMU27LAOQduHWGNhIlfA-Wq14/view?usp=sharing
The text was updated successfully, but these errors were encountered: