-
Notifications
You must be signed in to change notification settings - Fork 60
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
Support Apcsilmic Dot 1 (Snapdragon Qualcomm 7c/SC7180) #117
Comments
Here's in Armbian in action, notice this version of Grub did not have the corruption, but others (even latest Arch boot) do. 2024-10-05.18-55-22.mp4 |
Here's in OpenBSD. You can see that it boots well until USB was all gone. I would say we need to fix up the USB port enumerations in ACPI first. Should be reported back to OpenBSD people as well. 2024-10-05.18-00-56.mp4 |
Hi, I'm also highly interested in this, however I have virtually 0 knowledge on how to even approach investigating this. But, if there's anything I can do to help, let me know. |
Right, can you try to install more ARM64 UEFI iso images on that little box? I'm also looking for a way to dump the serial and boot log |
The current status quo: Grub actually boots, but it displays garbled text after starting countdown -- a sign of video buffer corruption.
After that, Linux unpacked itself in memory and then UEFI transitioned from Boot Service to Runtime Service -- after that point things went south -- No video output, no USB power, whole thing just turns off with no capability for debugging, probably an indication of both GOP video mode selection failure and a kernel panic at the same time,
For FreeBSD it has the same fate, but on OpenBSD it surprising boots. However, I wasn't able to get through the installation menu since the USB keyboard lost connectivity, but at least the kernel did not go FUBAR.
Maybe I should start with ACPI entry dumps in Windows and see what we can do about it. I really want this thing to run Linux for a long time since it is a really capable machine for running as an IoT device center control terminal with its 4G and other network connectivity.
The text was updated successfully, but these errors were encountered: