I got a new MacBook Air for free. Actually, i’m running on it MacOS 11 (BigSur) and yabai (tiling window manager, similar to some extent to bspwm). But i’m sick of all the hassle with MacOS and Homebrew and would like to get a clean manjaro installation on it.
Now, i can boot from a usb stick attached to the usb3 connectors via an adapter. BUT: Since the built in graphic chip of the MacBook supports an enormous resolution (by default; up to: 2560x1600) so screen appearance (fonts images etc.) on the built-in screen is so small i cannot read (or click) anything.
So, my first question is:
How can i change/reduce the resolution on boot from the installer usb stick to 1440x900?
My second question:
Is there any problem known with this model macbook, something of the basic hardware, not being supported (not yet or absolutely not)? Especially, as i’m aware by sad experiences in the past, for the wireless and bluetooth … (at a first glance, i do not see them in what inxi says (?) ).
This is what ‘inxi -F’ tells:
System: Host: MacBook-Air Kernel: Darwin 20.1.0 x86_64 bits: 64 Desktop: N/A OS: Darwin 20.1.0
Use of uninitialized value in string eq at /usr/local/bin/inxi line 11258.
Machine: Type: Laptop System: Apple product: MacBookAir8,2 v: 1.0 serial: FVFZP82LLYWJ
Mobo: Apple model: Mac-226CB3C6A851A671 serial: FV994561WYMLF07AH BIOS: Apple v: 1554.50.3.0.0 (iBridge rev: 0.1
date: 10/29/2020
Argument "Unknown" isn't numeric in division (/) at /usr/local/bin/inxi line 6787.
Argument "Unknown" isn't numeric in division (/) at /usr/local/bin/inxi line 6791.
Battery: ID-1: BAT0 charge: N/A condition: N/A/0.0 Wh
CPU: Topology: Quad Core model: Intel Core i5-8210Y bits: 64 type: MCP L2 cache: 256 KiB
Speed: 1600 MHz min/max: 400/400 MHz Core speeds (MHz): No speed data found for 4 cores.
Graphics: Message: No Device data found.
Display: server: X.Org 1.18.4 driver: N/A resolution: 1440x900
OpenGL: renderer: Intel UHD Graphics 617 v: 2.1 INTEL-16.0.49
Audio: Message: No Device data found.
Network: Message: No Device data found.
IF-ID-1: en3 state: active speed: 100baseTX duplex: full-duplex mac: ac:de:48:00:11:22
IF-ID-2: ap1 state: inactive speed: N/A duplex: N/A mac: fa:ff:c2:1d:1f:b0
IF-ID-3: en0 state: active speed: N/A duplex: N/A mac: f8:ff:c2:1d:1f:b0
IF-ID-4: en1 state: inactive speed: N/A duplex: full-duplex mac: 82:e7:8a:a4:58:01
IF-ID-5: en2 state: inactive speed: N/A duplex: full-duplex mac: 82:e7:8a:a4:58:00
IF-ID-6: bridge0 state: inactive speed: N/A duplex: unknown type mac: 82:e7:8a:a4:58:01
IF-ID-7: awdl0 state: active speed: N/A duplex: N/A mac: 3e:ea:78:3e:9c:39
IF-ID-8: llw0 state: active speed: N/A duplex: N/A mac: 3e:ea:78:3e:9c:39
Drives: Local Storage: total: dmesg.boot not found used: 95.96 GiB
Drive Report: dmesg.boot not found
Partition: ID-1: / size: 112.71 GiB used: 13.91 GiB (12.3%) fs: apfs dev: /dev/disk1s6s1
Swap: Alert: No Swap data was found.
Sensors: Platform: No Darwin support. Is a comparable sensors tool available?
Or use custom kernel boot parameter with vga code. It seems the 1440x900 would be vga=869 so you add that right after the quiet when you edit the grub before booting. But, you have to use rEFit bootloader and install grub in legacy mode on /boot partition …
This is not a question you should ask us. We don’t deal apple.
Apple did their best to make sure their hardware runs their software and nothing else without a lot of work.
Generally this would answer a lot of questions, but mostly old models https://wiki.archlinux.org/index.php/mac
Or use custom kernel boot parameter with vga code. It seems the 1440x900 would be vga=869 so you add that right after the quiet when you edit the grub before booting. But, you have to use rEFit bootloader and install grub in legacy mode on /boot partition …
Is this due to the vga settings or would that be generally the case - on an iMac i did a simple installation with grub in standard mode?
I know … It was rather a “cry for help” by someone who already did succeed in installing manjaro (or arch) on a MacBook Air. Generally, in the past i had some success in re-enabling older Macs installing on them manjaro o arch. E.g., my desk machine is a 2013 iMac - which works, apparently, flawlessly …
As per arch wiki, the two iMac models presented there require a different approach, so i’m sure that a 2020 MacBook Air will require a different approach too for the install.
Probably because was the same procedure of install as the Mid 2010 iMac, hence required no much fuss, but newer models from apple are quite linux unfriendly …
If the system is ARM based - I bet you will get older and your hair will become grey and fall off before you get Linux working on that one.
But as it apparently is x86_64 - my bet is still a grey haired old daddy - banging his head on wall - - and though it is a challenge - believe me it is not worth it.
For what it’s worth, I am running Manjaro on a MacBook Air 4,2 and it runs smooth as custard, with the exception of one thing (see below). I know I have a much older model, so I am not surprised if things don’t go that well with the newer models. You can see my inxi -F output below and compare.
The only problem I have is related to support for the aux output: When I listen to certain audioformats (I have yet to really look into which, or if there is any fix) I get distortions on all of the sound or on the dialogue. I am pretty sure it’s not the hardware that has broken, as sound from for instance Spotify alwyays works well. And I also assume that it’s linked to the software support for the aux output as there is never any problem when I use the internal speakers or bluetooth pairing. This didn’t use to be a problem, but it has been since an update about a year ago, if I remember correctly. The problem persists after fresh installs, so I guess some extra messing around with it will be necessary when I get time.
Ok, i’m already old and grey haired … May be you’re right: Not that good idea to make the situation even worse. Although, i’d love to run a clean i3 on it …
I don’t think is impossible to install it, but more investigation is required. Without the hands on such device i can only speculate. In some cases the use of acpi_osi=!Darwin was required as kernel boot parameter. Maybe on this new models needs to be different. acpi_osi=!Linux probably would do it, but i have no clue how the power management works on the newer models …
Have you considered trying Architect and collect some logs ?