Arch Linux on Matebook X Pro
Table of Contents
Recently, I got a new laptop, Huawei Matebook X Pro. It has an i7 8th Gen. Intel CPU, 16Gib of RAM, 512Gib of SSD storage, Nvidia MX150 GPU with 2Gib of DRAM, and a beautiful HiDPI and touchscreen. It also comes with a fingerprint sensor. The first thing I did was installing Arch Linux, because well I am a Linux user! In the end, everything was working properly except:
Two out of four speakers.See UPDATE1 down below
- The fingerprint sensor.
Some keys in the Fn row.See UPDATE2
The installation was very straightforward and like every other Arch Linux installation process. I followed their installation guide. After the installation is complete, everything was working properly except for some minor issues.
First, disable secure boot from the BIOS menu by pressing F2 while booting. Then have your Arch Linux installation media ready, then you can access the boot menu by holding F12 while booting. Once you boot into Arch Linux live boot image, you will notice that the font is too small, you can change that to use a large font with
setfont latarcyrheb-sun32, or you could use any other font you like.
Multi-lib repositories #
You probably want to enable multi-lib repos to support 32-bit software. Just uncomment that in
/etc/pacman.conf or add the following:
[multilib] Include = /etc/pacman.d/mirrorlist
I used Grub for the bootloader. Obviously, you want to use Grub for UEFI systems. For the ESP location, I had mine set to
/boot/efi just to follow other Linux distors approach. Because of the HiDPI screen that comes with this laptop, Grub would very tiny to see, a quick fix is to set the
GRUB_GFXMODE variable to something like
1600x1200x32. The available values can be fetched from Grub command line by executing
videoinfo. Edit your
/etc/default/grub file to include these lines:
If you are dual-booting you should install the package
os-prober to make Grub detect Windows partitions.
don’t forget to regenerate
sudo grub-mkconfig -o /boot/grub/grub.cfg
After Installation #
Because I have a dual-boot setup with Windows, I ran into a little problem after partitioning Windows partition. However, it was easily fixed using
ntfs-3g package which includes the tool
ntfsfix. After you complete the installation and boot into Arch, just run the tool with
-b to fix bad sectors and
-d to clear dirty flag:
sudo ntfsfix -b -d /dev/nvme0n1p3
In my case, my Windows partition was
/dev/nvme0n1p3, you should change that based on your partition name. You can use
blkid to list all your partitions.
AUR helper #
One of Arch Linux beauties is AUR, where you can easily get any Linux package installed with ease. I used the tool
aurman which is IMO one of the safest ones out there. Here is the full list of AUR helpers. To install aurman:
git clone https://aur.archlinux.org/aurman.git cd aurman makepkg -si
Desktop Environment #
Since this device comes with a touch-enabled and HiDPI screen, I decided to go with Gnome because it supports these two things pretty well.
sudo pacman -S gnome gnome-extra
This would automatically install Gnome with Wayland. Wayland doesn’t require any further configuration or drivers.
Nvidia driver & Bumblebee #
The MBXP comes with Intel UHD Graphics 620 and NVIDIA Geforce MX150. If you are planning to use the Nvidia card for gaming, rendering, or anything your best two options are using Prime technology with Nouveau (open source NVIDIA driver), or use NVIDIA proprietary driver with Bumblebee. I decided to go with the later because it offers better performance. Install Bumblebee
sudo pacman -S bumblebee bbswitch nvidia mesa acpi_call lib32-virtualgl lib32-nvidia-utils
Enable Bumblebee service and add user to Bumblebee group:
sudo systemctl enable bumblebeed.service sudo gpasswd -a $USER bumblebee
You probably need to Enable NVIDIA card during shutdown to avoid issues with using it.
Now we need to tell Bumblebee to use bbswitch for card switching. Edit
/etc/bumblebee/bumblebee.conf to include this:
Sometimes Bumblebee doesn’t detect the card which results in an error. You need to define the card BusID in
/etc/bumblebee/xorg.conf.nvidia, just uncomment the line where it has “BusID” and set it to the actual device ID. You can get that using
lspci. In my case, it was “PCI:01:00:0”.
Power Saving #
sudo pacman -S tlp tlp-rdw
sudo systemctl enable tlp.service sudo systemctl enable tlp-sleep.service sudo systemctl mask systemd-rfkill.service sudo systemctl mask systemd-rfkill.socket sudo systemctl enable NetworkManager-dispatcher.service
And since TLP enables NetworkManager by default, there is no need to enable that. You want to set TLP default mode to the battery. Edit
/etc/default/tlp to have these settings:
# Operation mode when no power supply can be detected: AC, BAT. TLP_DEFAULT_MODE=BAT # Operation mode select: 0=depend on power source, 1=always use TLP_DEFAULT_MODE TLP_PERSISTENT_DEFAULT=1
Also since we are using Bumblebee with Nvidia you have to make sure that TLP doesn’t enable power management for the card which can break auto switching with Bumblebee. You should avoid using
powertop --auto-tune since it enables power management resulting in breaking Bumblebee. Make sure you have these lines in
/etc/default/tlp to exclude the Nvidia card from power management:
RUNTIME_PM_BLACKLIST="01:00.0" RUNTIME_PM_DRIVER_BLACKLIST="amdgpu nouveau nvidia radeon"
Again make sure that you have the correct bus id for your card.
/etc/modprobe.d/audio_powersave.conf add to enable audio power saving:
options snd_hda_intel power_save=1
Since this laptop comes with Intel Wireless 8265, we can use
iwlwifi power saving options. Add these options in
options iwlwifi power_save=1 d0i3_disable=0 uapsd_disable=0 options iwldvm force_cam=0
Intel GPU #
Power saving options for Intel GPU, just stick this line in
options i915 enable_guc=3 enable_fbc=1
Suspend and Hibernate #
Personally, I prefer hibernating my machine whenever I do not use it for a long time, that is why I use suspend-then-hibernate. Suspend to RAM works out of the box, but hibernate requires some work. First, make sure you have either a swap partition or swap file. I went with swap file just because it does not require partitioning. According to Redhat Recommended System Swap Space, 1.5 of system RAM is the recommended amount of swap for hibernation which is 24Gb in this case.
sudo fallocate -l 24G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile
Now define that within
/etc/fstab for auto mounting:
/swapfile none swap defaults 0 0
In order for hibernate to work, you have to define where the system should look for the resume image in your Linux partition. You can define that in the kernel parameter in your bootloader
resume=UUID=ce6dd35a-08d5-4b49-a46c-eff1de8937ce. Here I am using partition UUID, you can get that with
sudo blkid. Since I am using a swap file, I also have to define a
resume_offset=645120 which is the location of the swap file in the partition. You can get that using
sudo filefrag -v /swapfile. Finally, add
resume hook after
i915 module in
/etc/mkinitcpio.conf. Regenerate initramfs
sudo mkinitcpio -P.
pcie_aspm=forcekernel parameter to enable ASPM (Active State Power Management).
- Disable watchdog, add
- Take a look at Improving Performance and Power Management.
- Regenerate initramfs
sudo mkinitcpio -P.
- Regenerate grub.cfg
sudo grub-mkconfig -o /boot/grub/grub.cfg.
- Install Plymouth.
- Enable auto-brightness
aurman -S iio-sensor-proxy.
- Config files used in this post etc.zip.
UPDATE 1 - fix sound #
You can fix the sound issue with
hdajackretask which is part of
alsa-tools package then follow this picture and click on “Install boot override”:
You might need to set “connectivity” to “internal” to get it working. Finally, recreate your initramfs
sudo mkinitcpio -P and reboot.
UPDATE 2 #
- Missing hotkeys
micmute, wlan, and pc managernow work using this driver. It will be part of linux 4.21 along with the speakers fix and micmute LED.
- Some people reported slow network connection with the above settings. To fix that, drop
- Also if you were using full disk encryption, don’t forget to add the speakers fix firmware files to
Disclaimer: This is a personal weblog. The opinions expressed here represent my own and not those of any entity with which I have been, am now, or will be affiliated.
- Run native C/C++ code in the browser using Emscripten 18 Nov 2020
- Dynamic DNS using DDclient 16 Feb 2019
- Writing a Chip-8 emulator 17 Sep 2018