So recently I installed Garuda Mokka in my old Macbook pro early 2015, but the result is pretty bad. After installing Garuda by calamares, I opened it up, it showed login screen and after logged in successfully, the screen turned completely black and the macbook shut down. Although I tried again many times, they still had the same result. How to fix this?
I used Macbook Pro early 2015 and it can still open live boot in usb and completely install, how did SGS tag me in unsupported hardware and dual boot topic? I only have Garuda OS in that macbook, I deleted macos come on?
Did you use ventoy.net and grub2 for installation?
Did you check sha256sum on USB-Stick?
Did you try Xfce with LTS kernel or dragonized with LTS kernel?
Live ISO works, if you play around with some apps or did it crash too after some time?
Please also post garuda-inxi (from live ISO, from terminal or Garuda Rani).
1 Like
Is not supported. That did not mean that the forum did no try tot help 
1 Like
I dont really undetstand what are u saying, since im stupid at decoding slangs. If you dont mind, no abbreviation please
of course no, live usb cannot save data. I switched to linux because of the redundant of windows and the oppressiveness of macos, so it’s my main OS. I used Rufus to create live usb btw
Search the forum about ventoy, it works, maybe on Mac too.
A few users here in the forum have installed Garuda on Mac. But none of the Garuda team uses Apple for reasons, so the team can’t help you with your hardware.
I’m familiar with the spec sheet for your Intel MacBook, but I can’t find anything that could cause a blackscreen.
I’ve already installed several Garudas on my MacBook (2012) (Dragonized, Mokka, KDE Lite, etc.), but I’ve never encountered a blackscreen.
I’m very curious about the garuda-inxi from the ISO.
1 Like
It really weird and unbalanced when I’m newbie and instead of choosing Ubuntu or simple environment, I chose Arch-based linux because… it’s beautiful, that’s all. And this question I can feel it really stupid but what is garuda inxi and how to check it?
I think this is explained in the template you deleted before posting the first post.
Boot the Garuda ISO, open the console/terminal, which you’ll find at the bottom left of the panel.
Enter the command garuda-inxi.
Copy the output and format it with three tildes (~~~) above and below the text.
Text
From the web:
inxi shows system hardware, CPU, drivers, Xorg, Desktop, Kernel, gcc version(s), Processes, RAM usage, and a wide variety of other useful information.
1 Like
result:
garuda-inxi
System:
Kernel: 6.13.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64
lang=en_US keytable=us tz=UTC misobasedir=garuda
root=miso:LABEL=GARUDA_MOKKA_BROADWING quiet systemd.show_status=1
checksum=y driver=free nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: Apple product: MacBookPro12,1 v: 1.0
serial: <superuser required> Chassis: type: 9 v: Mac-E43C1C25D4880AD6
serial: <superuser required>
Mobo: Apple model: Mac-E43C1C25D4880AD6 v: MacBookPro12,1
serial: <superuser required> uuid: <superuser required> UEFI: Apple
v: 489.0.0.0.0 date: 10/07/2023
Battery:
ID-1: BAT0 charge: 0% condition: 3.4/74.8 Wh (4.5%) volts: 7.3 min: 11.4
model: SMP bq20z451 type: Li-ion serial: N/A status: full cycles: 634
CPU:
Info: model: Intel Core i5-5287U bits: 64 type: MT MCP arch: Broadwell
gen: core 5 level: v3 note: check built: 2015-18 process: Intel 14nm
family: 6 model-id: 0x3D (61) stepping: 4 microcode: 0x2F
Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2
smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
Speed (MHz): avg: 500 min/max: 500/3300 scaling: driver: intel_cpufreq
governor: schedutil cores: 1: 500 2: 500 3: 500 4: 500 bogomips: 23200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Iris Graphics 6100 vendor: Apple driver: i915 v: kernel
arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: eDP-1
empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:162b
class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1600 s-dpi: 96 s-size: 677x423mm (26.65x16.65")
s-diag: 798mm (31.43")
Monitor-1: eDP-1 model: Apple Color LCD built: 2014 res: mode: 2560x1600
hz: 60 scale: 100% (1) dpi: 227 gamma: 1.2 size: 286x179mm (11.26x7.05")
diag: 337mm (13.3") ratio: 16:10 modes: 2560x1600
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Graphics 6100 (BDW
GT3) device-ID: 8086:162b memory: 3.74 GiB unified: yes
API: Vulkan v: 1.4.304 layers: 4 device: 0 type: integrated-gpu name: Intel
Iris Graphics 6100 (BDW GT3) driver: N/A device-ID: 8086:162b
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Broadwell-U Audio vendor: Apple driver: snd_hda_intel
v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
Device-2: Intel Wildcat Point-LP High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0
class-ID: 0403
Device-3: Broadcom 720p FaceTime HD Camera driver: N/A pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:1570 class-ID: 0480
API: ALSA v: k6.13.5-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Broadcom BCM43602 802.11ac Wireless LAN SoC vendor: Apple
driver: brcmfmac v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 14e4:43ba class-ID: 0280
IF: wlp3s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Apple Bluetooth Host Controller driver: btusb,hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:3
chip-ID: 05ac:8290 class-ID: fe01
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 473.42 GiB used: 4.58 GiB (1.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Apple model: SSD SM0512G
size: 465.92 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: SA0Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Silicon Motion model: FLASH JVJ
size: 7.5 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.0
spd: 480 Mb/s lanes: 1 mode: 2.0 tech: SSD serial: <filter> fw-rev: 1100
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.66 GiB used: 256 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 4
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 58.0 C pch: 54.5 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 8 GiB available: 7.66 GiB used: 2.28 GiB (29.8%)
Processes: 196 Power: uptime: 5h 36m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.03 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1282 libs: 358 tools: octopi,paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.0 running-in: konsole
inxi: 3.3.37
warning: database file for 'garuda' does not exist (use '-Sy' to download)
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.7.2-1):
System install date: 2025-07-17
Last full system update: 2025-07-17 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: <superuser required>
Failed units: snapper-cleanup.service
garuda@garuda-mokka in ~ as 🧙 took 4s434ms
Desktop: KDE Plasma v: 6.3.2
We now use KDE Plasma v: 6.4.2
warning: database file for ‘garuda’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘core’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘extra’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘multilib’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘[chaotic-aur](https://aur.chaotic.cx)’ does not exist (use ‘-Sy’ to download)
Last full system update: 2025-07-17 ↻
Windows dual boot: Yes or no?
Failed units: snapper-cleanup.service
I leave the analysis of the errors to those who can do it better than me 
2 Likes
so what have I to do now?
(I know this situation is pretty rare, so it’s hard to fix too)
You can find the answer in garuda-inxi
(use ‘-Sy’ to download)
How that’s supposed to work if you can’t access the TTY, I don’t know 
1 Like
darn “-Sy” doesn’t work
Sorry, it should be sudo pacman -Sy.
Then resync and update
garuda-update
… you mean: sudo pacman -Syy? Nah it has so many errors. Thank you guys for your helps but it seems like it can’t be fixed
pacman -Sy (without sudo?)
First:
Pls format your posted garuda-inxi with three tildes (~~~) above and below the text.
If you see this icon ↻ = reboot your system. You see also a icon for this if rani is open.
warning: database file for ‘garuda’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘core’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘extra’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘multilib’ does not exist (use ‘-Sy’ to download)
warning: database file for ‘[chaotic-aur](https://aur.chaotic.cx)’ does not exist (use ‘-Sy’ to download)
Default after install the os and you start this system you have the choice to install some apps/kernels/etc and then run “automatic” a script to make a system update. If you do nothing / have closed this app, you must run self the update.
To do: use rani or open konsole command garuda-update. If finished → reboot →
result = ?
2 Likes
um it kinda like youre fixing the live usb more than the mainos. The usb is normal without any issues, and the mainos installed by calamares was stuck in black screen (and forced shut down also)