-
Notifications
You must be signed in to change notification settings - Fork 123
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
Raspbian Only App to Boot w/ official 7" touchscreen #839
Comments
Well, they are probably loading, just not displaying on the correct screen. Have you tried plugging a HDMI monitor in? You may need to do this anyway in order to configure the OS to use the DSI touchscreen (see below). Raspios does a good job of auto-detecting the DSI display and loading up the correct drivers. Some details for configuring KMS mode can be found here: https://www.raspberrypi.com/documentation/computers/configuration.html#set-the-kms-display-mode Some Legacy (non-kms) options can be found here: https://www.raspberrypi.com/documentation/computers/legacy_config_txt.html#lcd-displays-and-touchscreens Please remember that in PINN's multiboot environment, each OS is completely separate with it's own boot partition and corresponding configuration settings, firmware & kernel etc. So each OS needs to be configured separately. |
I've just installed Kali64, AOSP13 and Raspberry PI OS on my PI4 with the 7" touchscreen. |
Unbelievably helpful thank you so much I'll be attempting this via HDMI
after work. Thanks again!
…On Thu, Sep 12, 2024, 10:43 AM procount ***@***.***> wrote:
Kali and AOS not loading on boot
Well, they are probably loading, just not displaying on the correct
screen. Have you tried plugging a HDMI monitor in? You may need to do this
anyway in order to configure the OS to use the DSI touchscreen (see below).
Raspios does a good job of auto-detecting the DSI display and loading up
the correct drivers.
With other distros, you may have to configure them manually to use the DSI
display.
How you do this depends on the OS and whether it uses KMS display drivers
or not.
For AOSP13, please read KonstaKang's FAQ on:
https://konstakang.com/devices/rpi4/AOSP13/
Some details for configuring KMS mode can be found here:
https://www.raspberrypi.com/documentation/computers/configuration.html#set-the-kms-display-mode
You may need to add an appropriate dtoverlay in config.txt to load the
appropriate DSI driver.
Some Legacy (non-kms) options can be found here:
https://www.raspberrypi.com/documentation/computers/legacy_config_txt.html#lcd-displays-and-touchscreens
Please remember that in PINN's multiboot environment, each OS is
completely separate with it's own boot partition and corresponding
configuration settings, firmware & kernel etc. So each OS needs to be
configured separately.
—
Reply to this email directly, view it on GitHub
<#839 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEKNOPD2NRZWHFSRKT2JI43ZWGSB7AVCNFSM6AAAAABODGPVPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGUYDCMJVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Describe the bug
Complete tech noob trying to setup a cyberdeck with PINN. Loaded PINN via pi imager downloaded Kali Linus full, raspbian full, and aos13 all rpi4 models. Upon boot only raspbian loads, Kali gives black screen, AOS (also tried with retropie) give white screen fades to black with white lines. Using rpi4 official 7" touch display with display cable, I have a USB speaker and USB keyboard plugged into device both drawing some additional power.
To reproduce
Download PINN on SD card with Pi imager
Install Kali Linux full, raspbian full, and aos13
Boot Kali Linux (black screen)
Boot raspbian (loads and functions as expected)
Boot on AOS (screen goes white then fades black)
Actual behaviour
Kali and AOS not loading on boot
System
Add answers to the following questions:
Pi4
3.9
Logs
If applicable, add the relevant output from
/tmp/debug
ordmesg
.Additional context
First time ever posting on git so if this is the wrong place to ask for advice feel free to remove! Thanks for the sweet program!
The text was updated successfully, but these errors were encountered: