undefined | Better HN

0 pointsbadpun7y ago0 comments

> Picking hardware that has direct kernel support will save you a bunch of headaches.

Yep, that seems key. I've just spend full 5 days (I'm in between contracts, so I have the time) trying to install Arch on my Early 2013 15" MacbookPro. I turned out that, due to buggy/nonstandard hardware, a fully functional dual boot with Windows is not possible (if your disk is GPT, you won't have sound on Windows and if it's MBR, the DisplayPort monitor won't come back from suspend on Arch). Just coming to that conclusion took around 4 days of experiments. I've spend one more day trying to set up wireless, and have just given up. There are more interesting things to do with computers than finding workarounds for a minefield of hardware/firmware/drivers bugs.

0 comments

wasted_intel7y ago

I had a late 2013 MBP and went with the XPS 13 for that reason. The process to dual boot (or even wholesale replace) a MBP on Linux looked really scrappy. I get it, Apple's UEFI firmware is essentially a black box with zero configurability. If that's how the process starts, I can't imagine how painful the rest of it is.

kevinherron7y ago

Don't install Arch, install Antergos or some other Arch derivative that packages it up with an installer.

High school me would have loved installing Arch (I did LFS back then). Current me doesn't have time for that bullshit.

j / k navigate · click thread line to collapse