Create a record for this exact machine
Before installing Linux on an ARM laptop, record the full model, processor, memory configuration and firmware version. Then find the distribution's or platform maintainer's instructions. A product family can contain different processors, so the marketing name alone is not enough.
Create a small table with the project guidance, applicable version, your own result and remaining issues for each function. Mark missing evidence as unverified rather than assuming support. Ubuntu's Snapdragon FAQ and Fedora's device directory both show why platform and model details matter.
First check the display, then networking
Begin with the internal display: resolution, scaling, brightness and whether settings survive signing out and back in. If you use external monitors, test your actual ports and dock, including an extended desktop, unplugging and reconnecting. A working login screen does not verify the entire display setup.
For networking, connect to the Wi-Fi network you need, browse and download a file, then test reconnecting and resuming from sleep. An installation completed using Ethernet does not prove the internal Wi-Fi adapter works. Record those connections separately and retain a working way to obtain updates.
Check audio and the camera independently
An audio device appearing in Settings is only a starting point. Play a recognizable sound and check speakers, headphones and the microphone. Make a short recording and play it back to find missing input or an incorrect input selection. Start at a low volume and follow any model-specific audio restrictions.
Check the camera in your normal meeting application, together with microphone permissions and screen sharing. Success in a standalone camera application establishes only that path. If meetings are essential, rehearse a complete call before migrating your work.
Check sleep, wake and storage access
Save your work, close the lid, wake the machine and reconnect to the network. Confirm that the keyboard, touchpad and audio return. Note whether the laptop is on battery or external power. Repeat this during a few normal work sessions rather than relying on one successful wake or an unrelated stress test.
Keep storage checks non-destructive. Confirm the disk model and capacity shown by the installer, then save and reopen files in your own test directory. For encrypted partitions, establish support and the unlocking method first. Do not format a partition containing data merely to test whether it is recognized.
Choose a sensible test sequence
If the model supports a live session from installation media, use it for an initial hardware check before choosing an installation plan. A live session and an installed system may use different kernels, firmware or packages. Label the test environment and repeat relevant checks after installation.
When something fails, look for reports involving the same model and release. Record distribution, kernel and firmware versions plus the preceding steps. Remove unnecessary personal details from logs before submitting them. Avoid piling fixes intended for unrelated machines onto a primary computer.
Use the results to decide when to migrate
Consider these six checks alongside your applications. If a required feature is missing, keep the existing environment and retest when its issue is resolved. If a limitation has an acceptable workaround, document that dependency as part of your setup.
ARM64 support is a starting point. The useful conclusion is what this model can do on this release, and what still does not work. This article provides a test method; it is not a claim that ARMPE has tested the listed platforms.
Sources and verification
This article draws on published documentation and editorial guidance. Unless explicitly stated, it does not report our own hardware tests. Sources checked: September 27, 2026.