Tag Archives: window manager

The Switch to Linux: Day 1

This post is not only going to be brief, but also rather uninformative. My brand new ASUS ux305 arrived in the mail today and I spent a majority of the day playing with it. The laptop is beautiful. It has a very high quality build and feels extremely similar to the Macbook Air. One of the things I loved about the two months I spent with a macbook air was the keyboard. Well, I must admit, ASUS has done a great job at matching the quality of that keyboard. The size, the battery life, the weight.. everything about this laptop is perfect.

The first thing I did was go ahead and install Linux on this machine. My distro of choice is Arch Linux, so naturally I decided to put the Arch install .iso onto a flashdrive using Rufus. I then stuck the USB drive in and rebooted into the BIOS (Which is the del key for the ux305). Once in the BIOS, I noticed that it did not immediately detect the flashdrive as a boot device. No worries, I added an entry to the BIOS boot menu and pointed it at launch.efi on the flash drive. Everything went smoothly from there.

I simply followed the beginner’s guide, noting that I was setting up things for a UEFI system. This meant that I needed to do a few special things such as use GPT for my partition tables instead of the MBR I used on all of my other machines to allow for dual-booting.

Everything went great until I was required to install a bootloader. For some reason, the first time I installed gummiboot, I could not boot into Arch Linux because I was missing the file varlinuz-linux. I then tried to install GRUB. Same issue. I went ahead and cleared the partitioning scheme and formatted the drive and started all over again. It worked after that. I’m not entirely sure what happened, but if you encounter the issue, it can be solved by clearning the drive and recreating the partitions.

Now that ArchLinux was installed, I had to choose my software. I decided to go with Xorg for my display (Using the open-source intel video drivers). I also tried lightDM as my display manager; however, I did not like the look/feel of it, so I decided to resort to SLiM and its archlinux-simplyblack theme. I also tried to use bspwm and awesome window managers; however, I failed to find them as suitable replacements for i3 and went ahead with my tried and true i3 setup. After that, everything has been going smoothly. I will post more details later about the specifics of my setup. I am too tired to post it now.

The major problem I encountered during this install was connecting to the internet. For whatever reason, during the install process, I could not connect to the university WiFi. I used the wpa-configsection example for netctl, but couldn’t get anything to work for my wireless adapter. I ended up just using the USB to Ethernet adapter that came with the laptop in order to get a stable wired connection to complete the install. Maybe this is what contributed to the missing linux kernel file during the first boot-manager install. After I finished installing, however, the netctl profile I created worked no-problem. I guess there were just issues while using the install USB. Again, I’m not really sure why.

So far, it looks like I will for sure be sticking with Linux this time. I hope.

The Switch to Arch: Day 1

One of the things that I’ve wanted to do for as long as I’ve known about Linux is make the switch to Linux full time. I wanted to understand how the operating system functioned, how I could use it, how I could alter it, and how I could get it installed on all of my machines. I have taken many baby steps to get to that point. For instance, from 2013-2014, I only had Lubuntu installed on my laptop and forced myself to use Linux for every task that came to mind. Of course, I also had my trusty desktop with a Windows installation. Although I definitely learned about Linux this way, I found myself often coming back to my Windows machine in order to edit with Photoshop, play some video games, or even do things without trying to make them compatible with Linux.

Just recently I decided to really push for the conversion process by taking a dive into Arch Linux and putting it onto my laptop. After about 2 days of struggling to get it installed and working as I wanted, I felt super happy and super confident. If you are unfamiliar with using Arch Linux, I highly recommend it. It is a great way to learn about how Linux works and it is a great experience (and very rewarding).

Anywho, so I got ArchLinux running on my laptop. I decided to choose Slim as my display manager, X as my display server, and i3 as my window manager. I really enjoy the tiling nature of i3 and the simplicity of its dynamic windows. I have tried Awesome and bspwm, but I just cannot get away from i3 and its charm. I think my favorite part about running ArchLinux is its system resource usage. While idling, Arch on my laptop uses 150MB of its 8GB of RAM. This is definitely something that not even Windows nor Lubuntu could pull off. Maybe I am missing some precious functionality that existed in those operating systems, but I definitely don’t feel like I’m missing much.

Inspired by the switch on my laptop, I decided to do the same thing on my desktop. Of course, this is a little more risky because video games have a reputation of not working all that well on Linux, but I am confident that my beast of a machine can pull off at least 30fps on the latest games running under WiNE, so I decided to give it a shot.

After the hours it took to install Arch on my desktop (experience from my laptop install definitely came in handy), I am very pleased with the results. The thing I had most difficulty with was getting my internet to work. For whatever reason, my WiFi  card could see the network but wouldn’t complete the DHCP handshake. The same thing would happen with a wired connection. Thinking it may have been a problem with the WiFi card, I even bought a new card. After messing with this for a few days, it turns out that in order to get internet working for PCI and Mobo adapters in Linux with a GIGABYTE motherboard, you have to enable the IOMMU setting in the BIOS. What IOMMU stands for, I have no clue. For more details on this situation, you can take a look at the ArchLinux forum post I made regarding the issue: https://bbs.archlinux.org/viewtopic.php?pid=1459970#p1459970

In short, I am loving this so far. I intend on posting a more detailed guide to getting Arch perfectly setup on machines that have a similar setup to mine. For now, I will just say that I am a very happy man.

The ArchLinux setup on my desktop machine

The ArchLinux setup on my desktop machine