How do I get to the TTY terminal on a MacBook pro mid 2015? I tried the shortcuts provided in this forum but they didn’t work.
I don’t know, so I asked https://www.perplexity.ai/
Accessing TTY on a MacBook Pro Running Linux
Switching to a TTY:
- On a MacBook Pro running Linux, you can access a virtual console (TTY) using keyboard shortcuts similar to standard PC keyboards, but with some Mac-specific adjustments.
- Typically, to switch to a TTY, you use
Ctrl+Alt+F1throughF6on most Linux distributions. On MacBook keyboards, especially those with a Touch Bar or where function keys require theFnmodifier, you often need to add theFnkey to the combination[2][5][8]. - For example, try:
Fn+Ctrl+Option(Alt) +F3
This should take you to TTY3. The specific key may vary depending on your Linux distribution and configuration[2][5][8].
Special Cases:
- On some MacBook models (especially newer ones or those with Touch Bar), you may need to emulate function keys using the
Fnkey, or use the Touch Bar to access the F-keys[5]. - In some distributions, the graphical session may occupy TTY1, so you may need to use
F2,F3, or higher to access a text TTY[2][7].
Summary Table:
| Action | Typical Shortcut on MacBook Pro Linux |
|---|---|
| Switch to TTY2 | Fn + Ctrl + Option + F2 |
| Switch to TTY3 | Fn + Ctrl + Option + F3 |
| Return to GUI (if on TTY2/TTY1) | Fn + Ctrl + Option + F1 (or F2, depending on distro) |
Notes:
- If you are using an external keyboard, ensure it is set to Windows mode for standard Linux key mappings[2].
- On some distributions or with certain hardware, you may need to experiment with the exact key combinations due to differences in how function keys are mapped[5][8].
Troubleshooting:
- If switching TTYs does not work, check your Linux keyboard settings, and verify whether the function keys require the
Fnmodifier. - On macOS (not Linux), only one TTY is available and you typically access a terminal via the GUI or by booting into Single User Mode, but this does not apply when running Linux natively[3][8].
In summary:
To access a TTY on a MacBook Pro running Linux, use Fn + Ctrl + Option + F[1-6], adjusting the function key as needed for your distribution and hardware[2][5][8].
[1] https://apple.stackexchange.com/questions/428840/does-recent-macos-have-ttys-enabled-if-not-is-it-possible-to-enable
[2] https://askubuntu.com/questions/1043333/how-do-i-access-a-console-tty-on-a-macbook
[3] Does recent macos have TTYs enabled? If n… - Apple Community
[4] [SOLVED] Macbook Pro 13,1 - Wrong Resolution in TTY / Newbie Corner / Arch Linux Forums
[5] Reddit - The heart of the internet
[6] Mac's and serial TTY's
[7] Using multiple command-line terminals (tty 1-5) on a m1 macbook air - #7 by sigadore
[8] https://stackoverflow.com/questions/800210/tty-switch-for-ctrl-alt-f1-and-alt-f1-f6-in-mac-os-x
A fix (reversion) for this issue has been proposed to be merged upstream in mesa - Making sure you're not a bot!
Hopefully this will reach Fedora in a few days,
P.S. Yet again, I am not a bot 
2 Likes
That worked, thank you very much.
Nchimunya Masenke
1 Like
here is an updated mesa 25.0.7-2 build with this commit reverted
I can’t test this myself due to lack of hw.
1 Like
It works here on my suitable hardware. Thank you.
1 Like
As you know, the problem is with the current version of mesa - 25.0.7-1 - and that I downgrade to the previous version - 25.0.2-3 - provides a workaround until a fixed version is available.
$ rpm -q mesa-dri-drivers mesa-filesystem mesa-libEGL mesa-libgbm mesa-libGL mesa-va-drivers mesa-vulkan-drivers
mesa-dri-drivers-25.0.2-3.fc42.x86_64
mesa-filesystem-25.0.2-3.fc42.x86_64
mesa-libEGL-25.0.2-3.fc42.x86_64
mesa-libgbm-25.0.2-3.fc42.x86_64
mesa-libGL-25.0.2-3.fc42.x86_64
mesa-va-drivers-25.0.2-3.fc42.x86_64
mesa-vulkan-drivers-25.0.2-3.fc42.x86_64
The problem affects Fedora Workstation 42 GNOME, i.e. with Wayland, not not GNOME with Xorg. It does not appear to otherwise depend on graphics architecture.
A reboot is not needed after downgrading the mesa packages.
Other updates can be installed without updating the mesa packages by excluding them, i.e.
$ sudo dnf upgrade --exclude="mesa-*"
1 Like
It also affects Fed 42 KDE Plasma 6 Wayland. 
had the same issue, worked for me thanks!
Worked like a charm after my latest F41 upgrade. Thanks 
This update fixes the regression for F42:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-df3c68a7ce
Corresponding update for F41:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1a91411755
2 Likes
The only strange thing here is that mesa-va-drivers-freeworld.x86_64 from rpmfusion in in lower 25.0.7-1.fc41 version when all others are 25.0.7-2.fc41 what can be source of problem in my case.
Got into this issue after upgrade to:
Installed packages
mesa-dri-drivers.x86_64 25.0.7-2.fc41 updat
mesa-filesystem.x86_64 25.0.7-2.fc41 updat
mesa-libEGL.x86_64 25.0.7-2.fc41 updat
mesa-libGL.x86_64 25.0.7-2.fc41 updat
mesa-libGLU.x86_64 9.0.3-5.fc41 fedor
mesa-libgbm.x86_64 25.0.7-2.fc41 updat
mesa-libxatracker.x86_64 25.0.7-2.fc41 updat
mesa-va-drivers-freeworld.x86_64 25.0.7-1.fc41 rpmfu
mesa-vulkan-drivers.x86_64 25.0.7-2.fc41 updat
Had do downgrade by:
$ sudo dnf downgrade ‘mesa*’ --refresh
to versions:
mesa-dri-drivers.x86_64 24.2.4-1.fc41 fedora
mesa-filesystem.x86_64 24.2.4-1.fc41 fedora
mesa-libEGL.x86_64 24.2.4-1.fc41 fedora
mesa-libGL.x86_64 24.2.4-1.fc41 fedora
mesa-libGLU.x86_64 9.0.3-5.fc41 fedora
mesa-libgbm.x86_64 24.2.4-1.fc41 fedora
mesa-libglapi.x86_64 24.2.4-1.fc41 fedora
mesa-libxatracker.x86_64 24.2.4-1.fc41 fedora
mesa-va-drivers-freeworld.x86_64 24.2.4-1.fc41 rpmfusion-free
mesa-vulkan-drivers.x86_64 24.2.4-1.fc41 fedora
$ inxi -CGzxx
CPU:
Info: quad core model: Intel Core i5-3570K bits: 64 type: MCP
arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1851 min/max: 1600/3800 cores: 1: 1851 2: 1851 3: 1851
4: 1851 bogomips: 27200
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: ASRock driver: i915
v: kernel arch: Gen-7 ports: active: HDMI-A-1,HDMI-A-3 empty: DP-1, DP-2,
DP-3, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0162
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: gnome-shell v: 47.6 driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi gpu: i915
display-ID: 0
Monitor-1: HDMI-A-1 model: Samsung SMBX2231 res: 1920x1080 dpi: 102
diag: 547mm (21.5")
Monitor-2: HDMI-A-3 model: Samsung SMBX2231 res: 1920x1080 dpi: 102
diag: 547mm (21.5")
API: OpenGL v: 4.2 vendor: intel mesa v: 24.2.4 glx-v: 1.4 es-v: 3.0
direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
device-ID: 8086:0162 display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
1 Like
RPM Fusion can only re-build their package (if/when required) when the Fedora package has hit the “updates” repository (i.e., the update has been pushed to “stable”). So there’s usually a bit of a lag. The RPM Fusion -freeworld package being older here has not caused any issues on my system—has it on yours? If it hasn’t, there’s nothing to worry about, it’ll get updated eventually.
The RPM Fusion -freeworld package being older here has not caused any issues on my system—has it on yours? If it hasn’t, there’s nothing to worry about, it’ll get updated eventually.
After update to the versions listed I got into exactly same issue as described in this thread: black rectangles instead of terminal windows, black and white rectangles instead of EasyEffects window. That is why I had to downgrade. Luckily I still had old GNOME Terminal and was able to use it and quickly downgrade mesa.
the previous version was 25.0.6-1 not 25.0.2
Thanks @burgess-m this worked for me too 
Thanks also to Andrew @ajcxz0 this also worked for me
Link to my thread in case it helps anyone
https://discussion.fedoraproject.org/t/blank-empty-system-apps-after-removing-unnecessary-vb-repo/
And thanks once again to @pg-tips
1 Like
The 25.0.2 version was the version at release time. In general, you only have the release version and the update version available. All update version up to but not including the latest are not available in the updates repository.
By the way, I see the current version is
mesa-filesystem.x86_64 25.0.7-1.fc42 updates
so version 25.0.7-2 seems to have been withdrawn.
1 Like
you can find in this thread instructions, how do downgrade to the previous 25.0.6 and not the version that was available at F42’s GA.
I had the same problem, but I only had issues with flatpak apps. I resolved this by just updating flatpak
Thanks to all who helped solve this issue. Started for me yesterday after an ‘dnf update’ I was gathering info on the issue and then went to ‘Ask Fedora’ and found the isse and the solutions. Thanks again to all.
4 Likes