boring man
New Member
I'm experiencing a persistent and specific display issue when running Linux on an old MacBook Air and have run out of debugging ideas.
· Problem: Persistent screen corruption (vertical lines, pixelation, distortion) appears only on the right side of the built-in display.
· Critical Detail: The corruption starts as soon as the screen switches from the firmware/GRUB menu to the Linux kernel's initialization phase (the text-mode or early graphical boot messages). Crucially, it continues throughout the entire graphical session, regardless of the desktop environment.
· The Key Clue for Diagnosis: The corruption disappears completely when I boot into:
· macOS Recovery Mode
· The native macOS system (High Sierra/Catalina)
· A Windows PE environment
This confirms it is not a hardware failure.
· Distributions Affected: I have confirmed this issue on Debian 12/13 and Ubuntu Kylin (both Debian/Ubuntu-based). It occurs both in live USB environments and after installation. I have NOT yet tested Arch-based (e.g., Manjaro) or RedHat-based (e.g., Fedora) distributions.
· Hardware: MacBook Air A1370 (Late 2010/Early 2011) with an Intel Core 2 Duo and an NVIDIA GeForce 320M GPU.
What I've Already Tried & Verified (All failed):
1. GRUB/Kernel Parameters: nomodeset, nouveau.modeset=0.
2. Driver Configuration: Created an Xorg configuration file for the nouveau driver with Option "AccelMethod" "none" and Option "SWCursor" "true".
3. Environment: Tested with different desktop environments (XFCE, GNOME).
Core Question to the Community:
Given that the issue appears at the earliest stage of kernel graphics initialization and persists, this strongly points to an incompatibility between the Linux kernel's framebuffer/console driver and the NVIDIA 320M GPU in this specific Apple hardware.
· Has anyone successfully run a modern Linux kernel on a MacBook Air A1370 (2011, NVIDIA 320M) without this graphical corruption? If so, what kernel version and parameters are you using?
· Are there any known fixes, kernel boot parameters, or framebuffer driver quirks (efifb, vesafb) for this particular Apple/NVIDIA hybrid setup?
· Would testing an Arch-based distro (like Manjaro) with a different kernel base and configuration approach be a promising next step?
Any insight or pointer would be immensely helpful. Thank you!
· Problem: Persistent screen corruption (vertical lines, pixelation, distortion) appears only on the right side of the built-in display.
· Critical Detail: The corruption starts as soon as the screen switches from the firmware/GRUB menu to the Linux kernel's initialization phase (the text-mode or early graphical boot messages). Crucially, it continues throughout the entire graphical session, regardless of the desktop environment.
· The Key Clue for Diagnosis: The corruption disappears completely when I boot into:
· macOS Recovery Mode
· The native macOS system (High Sierra/Catalina)
· A Windows PE environment
This confirms it is not a hardware failure.
· Distributions Affected: I have confirmed this issue on Debian 12/13 and Ubuntu Kylin (both Debian/Ubuntu-based). It occurs both in live USB environments and after installation. I have NOT yet tested Arch-based (e.g., Manjaro) or RedHat-based (e.g., Fedora) distributions.
· Hardware: MacBook Air A1370 (Late 2010/Early 2011) with an Intel Core 2 Duo and an NVIDIA GeForce 320M GPU.
What I've Already Tried & Verified (All failed):
1. GRUB/Kernel Parameters: nomodeset, nouveau.modeset=0.
2. Driver Configuration: Created an Xorg configuration file for the nouveau driver with Option "AccelMethod" "none" and Option "SWCursor" "true".
3. Environment: Tested with different desktop environments (XFCE, GNOME).
Core Question to the Community:
Given that the issue appears at the earliest stage of kernel graphics initialization and persists, this strongly points to an incompatibility between the Linux kernel's framebuffer/console driver and the NVIDIA 320M GPU in this specific Apple hardware.
· Has anyone successfully run a modern Linux kernel on a MacBook Air A1370 (2011, NVIDIA 320M) without this graphical corruption? If so, what kernel version and parameters are you using?
· Are there any known fixes, kernel boot parameters, or framebuffer driver quirks (efifb, vesafb) for this particular Apple/NVIDIA hybrid setup?
· Would testing an Arch-based distro (like Manjaro) with a different kernel base and configuration approach be a promising next step?
Any insight or pointer would be immensely helpful. Thank you!
