Dec 06, 2018

KDE Neon on 2017 MacBook Air

I'm a huge fan of Linux-based operating systems, but I've always been smitten with the svelte union of hardware and software that Apple creates. While I haven't been able to bring myself to part with my iOS gadgets (consumption devices), I recently wiped macOS from my MacBook Air (creation device) and installed KDE Neon User Edition.

Spoiler alert: It's awesome!


There are plenty of tutorials out there on how to install Linux, especially Ubuntu, on your machine, including most Macs, so I'll spare you. The current build as of this writing is based on Ubuntu 18.04 LTS. If you're having trouble finding one for the 2017 MacBook Air, search for "MacBook Air 7,2" or any tutorials for the 2015 version (which is also model 7,2).

The only real pain of installation is wireless connectivity, which is to be expected since many laptops have wireless issues on Linux-based operating systems. Fortunately, it is easily remedied in this case.

To activate wireless in the live environment, open a terminal and type:

sudo apt install bcmwl-kernel-source

sudo modprobe -r wl

sudo modprobe wl

This installs kernel modules to support the Broadcom BCM4360 (or similar) wireless chipset. The second and third commands reload the kernel modules (may or may not be required, but doesn't hurt). You will then be able to select a wireless network from the network icon and proceed with a normal Ubuntu-like installation, including the download of updates and installation of 3rd party software, drivers, etc.

Once the installation is complete and you boot into your fresh KDE Neon environment, you won't have wireless again. You need to execute the same commands as above and you have a few options:

  1. Insert installation media and configure apt to recognize it; or
  2. Use a USB or Thunderbolt Ethernet adapter to gain wired connectivity; or
  3. Tether your phone via USB.

Whichever option you choose, follow up by executing the same commands you did in the live environment and you will have wireless connectivity.


KDE is my preferred desktop environment on Linux, so please forgive my bias. After installation, you're greeted with an awesome KDE experience OOTB. Everything works, including the Fn keys, the tilde key... everything! Battery life isn't as good as provided by macOS, but it's decent and workable. Installing and calibrating powertop provided near-macOS battery life. While I didn't run it to zero, I had 60% left after 4 hours of battery use.

There's not much to report. It works great! If I have any major issues to report, I'll update this post.


Why did I do this? Because I could... but mostly because I picked up a brand new 2017 MacBook Air on sale at BestBuy for US$750. It has a dual-core i5, 8GB RAM, and 128GB SSD. A similarly configured KDE Slimbook II was around US$1100 when I was shopping. I would have liked the freedom to expand that the Slimbook offered, but I wasn't willing to pay for it.


Your feedback and tips are always welcome and encouraged! Please share in the comments, on Twitter, or shoot me an email.




  • Built-in webcam does not work.
  • The microphone of headphones with one built-in (i.e. the ones that come with your phone) is not detected. Headphones work fine.


  • HDMI audio out does not work.
Click to read and post comments

Jul 22, 2016

How to use macOS Boot Camp on a USB stick

My equipment:

  1. 13" MacBook Pro, Early-2015.
  2. Windows 10 EDU in VMWare Fusion 8.
  3. 128GB SanDisk UltraFit USB 3.0 (ultimate destination for Boot Camp).
  4. Seagate 750GB SSD/HDD Hybrid in a USB enclosure.

What you'll need:

  1. Windows ISO (I'm using Windows 10, but should also work with 7, 8, or 8.1). You can also use a Windows installation disc.
  2. gimagex.
  3. Existing Windows 7, 8, 8.1, or 10 64-bit installation, physical or virtual machine.
  4. A USB hard drive and a USB stick (yes, both).
  5. Your Mac, of course.

Summary of steps:

  1. Partition the USB hard drive.
  2. Write the install.wim image to the USB hard drive.
  3. Make the USB hard drive bootable.
  4. Clone the USB hard drive contents to the USB stick using dd.

1. Partition the USB hard drive

  • Insert the USB hard drive into the Windows machine and launch Command Prompt (Admin).
  • Type diskpart to launch the DISKPART utility.
  • Type list disk to see the list of attached disks. Note the disk number associated with your USB hard drive. I'll refer to it as X.
  • Type select disk X, then type list disk and confirm an asterisk next to the proper disk.

    WARNING The following step will wipe all data from the USB hard drive:

  • Type clean.

  • Type convert mbr to create a Master Boot Record (MBR) partiton table. I did not get a GPT disk to work with the USB stick.
  • To create a 200MB EFI partition, type make partition primary size=200.
  • Format the EFI partition by typing format fs=FAT32 label=EFI quick.
  • Assign the partition a drive letter: assign.
  • Make the partition bootable by typing active.
  • Create the partition for the Windows installation: create partition primary size=120000.

If you're chops are strong, you can size the your partitions exactly to match the target USB stick size. The cloning process is lengthy and I hate waiting again if I screw it up, so I chose to keep the partitions a little smaller. I'm using a 128GB USB stick, but there's never the "full" amount available, so I sized the partition to 120GB, or 120000MB.

I also tried using a 64GB partition so I could put a Linux distro on the USB stick. Because it's a USB stick and has to be an MBR, I did not successfully add a Linux distro to the stick. Point is, it doesn't pay to save space; just make the main Windows partition the full size of your USB stick. It's also worth noting that you won't be able to change the partition scheme after you've cloned it to the USB stick in later steps.

  • Format the main partition: format fs=ntfs label=Windows quick.
  • Assign the partition a drive letter: assign.
  • You should now have two partitions with drive letters assigned.

2. Write the Windows image to the USB hard drive

  • Download your chosen version of Windows to the Windows machine you'll be working from.
  • Download gimagex. There are also official Windows command line tools, but this one is a GUI.
  • Double-click the ISO to mount it. Windows will assign a drive letter to it.
  • Open gimagex and select the Apply tab.
  • In the Source field, select the mounted ISO and navigate to sources\install.wim.
  • In the Destination field, select the Windows partition on the USB hard drive.
  • Press the Select button directly across from the Image field to select your desired image.

Depending on your installation medium, you may have multiple versions of Windows you can install: Home, Professional, Enterprise, or EDU in 32 or 64-bit flavors. Make sure you choose a 64-bit version for your Mac.

  • Press the Apply button.

Depending on your machine, the apply process may take 15 minutes to a couple hours. Mine typically took about 20-30 mins.

  • While you're waiting for the apply process to complete, download the Boot Camp Windows Support software by opening Boot Camp Assistant on your Mac and selecting Download Windows Support Software from the Action menu.

You can copy the support software to a separate USB stick (not the one you're using for Boot Camp) or you can copy the software over to the Windows machine and place it in your Public Downloads folder after the apply process is complete. If you're reading this tutorial, you're probably savvy enough to figure out how to do this.

3. Make the USB hard drive bootable

  • Once the image has been applied to the USB hard drive, launch Command Prompt (Admin).
  • Type X: where X is the drive where the Windows image was just applied.
  • Type cd Windows\system32.
  • Type bcdboot.exe X:\Windows /s Y: /f ALL where:
    • X is the drive letter for the Windows partition on the USB hard drive and;
    • Y: is the drive letter for the EFI partition on the USB hard drive.

I had some issues with bcdboot making the EFI folders on the Windows partition instead of the EFI partition. Once bcdboot has done its thing, you can copy the EFI folder from the Windows partition to the EFI partition. You may not be able to delete the EFI folder from the Windows partition because of the permissions assigned to it. I haven't had any issues with it remaining there.

At this point, you have an external USB hard drive from which you could run Windows. I recommend you test it to make sure it works up to this point by doing the following:

  • Copy the Windows Support Software into the Public Downloads folder (or anywhere else it's accessible by all users) on the Windows partition of the USB hard drive.
  • Eject the drive from your Windows machine and plug it in to your Mac.
  • Restart your Mac while holding the Option key. Release it once you see Macintosh HD and EFI Boot.
  • Select EFI Boot.
  • Allow Windows to setup. When it restarts, make sure you hold the Option key so you can select EFI Boot.
  • Once Windows finishes its initial setup, install the Windows Support Software (optional).
  • Restart to make sure everything is working.

4. Clone the USB hard drive contents to the USB stick using dd

  • Restart your Mac into OS X/macOS.
  • Insert the USB stick. Both the USB hard drive and stick should be plugged in to your Mac.
  • Open Terminal. Type diskutil list.
  • Make note of the disk numbers for the USB hard drive and the USB stick. I will refer to the hard drive as disk2 and the stick as disk3.
  • Unmount both disks by typing: sudo diskutil unmountDisk /dev/disk2 and sudo diskutil unmountDisk /dev/disk3.
  • Begin the cloning process by typing: sudo dd if=/dev/rdisk2 of=/dev/rdisk3 bs=1m count=121000.

Explanation: dd typically uses 512-byte blocks. Using bs=1m changes it to one megabyte. count= tells dd how many blocks to write. For my 128GB drive, I made a 200MB EFI partition and a 120000MB Windows partition, so I've told dd to write 121,000 blocks. This ensures it captures both the EFI and Windows partitions, plus some extra for the space taken up by the partition tables and offsets. Adjust as your needs dictate.

This can take a significant amount of time, depending on how many blocks you are writing. It took about 2 hours when I was experimenting with the 64GB partition; for the 120GB, I just set it and went to the beach.

Once dd has completed, eject the USB hard drive and restart your Mac, holding the Option key and selecting EFI Boot.


The USB 3.0 stick isn't the fastest way to run Windows on your Mac. If you open up Performance Monitor, you'll see your main Windows partition maxed out at 100% rather frequently. But if you're strapped for space on your Mac, this will get you by.

Helpful Resources

Nowadays, no one is a self-made genius. I found these articles particularly helpful when stumbling through this procedure:

Click to read and post comments