Академический Документы
Профессиональный Документы
Культура Документы
work is licensed under the Creative Commons Attribution 4.0 International License. To view a
copy of this license, visit http://creativecommons.org/licenses/by/4.0/ or send a letter to Creative
Commons, PO Box 1866, Mountain View, CA 94042, USA.
The problem with step by step guides. The information is only accurate for up to a few months.
Follow this guide with a grain of salt. Check if something is working before trying to repair it. After fixing it,
verify if it is really working.
Most importantly, backup your data. You already do it monthly, don't you?
Source repository
Contribute to the guide here: https://github.com/5bentz/linux-asus-t100
Resources
Asus T100 Ubuntu group. Ask your questions here!
https://plus.google.com/communities/117853703024346186936
Various tutorials with screenshots https://tutorials.ubuntu.com/tutorial/
Linuxium and Isorespin: customize Ubuntu ISOs!
https://linuxiumcomau.blogspot.com/2017/06/customizing-ubuntu-isos-documentation.html
(2016) Guide for the T100 Ubuntu 16.04:
https://drive.google.com/drive/folders/0B4s5KNXf2Z36QW9acnY4RXd3bW8
Ubuntu: https://www.ubuntu.com/download/desktop
Xubuntu: https://xubuntu.org/download
Other torrents: http://torrent.ubuntu.com/
Note: Download the 64 bit version. 32 bit versions may fail to boot.
On Windows
The defaults should be alright, I'd just recommend setting the partition scheme to GTP UEFI, since ASUS
T100 and Windows 10 are compatible with it. Make sure you are flashing the correct device.
3. Add the bootable GRUB file for our IA32-powered ASUS T100.
Copy the bootia32.efi file in the EFI/BOOT directory. This directory should already contain various EFI
files: probably BOOTx64.EFI and grubx64.efi .
If, like jfwells, you would like to build bootia32.efi by yourself, follow his guide (primarily for Linux Ubuntu
and other Linux Debian-derivatives): https://github.com/jfwells/linux-asus-t100ta/tree/master/boot
4. Boot
Note: The flag -b is necessary in this tutorial. It tells ubiquity not to install a bootloader. Without this flag,
ubiquity would crash when trying to install it (Thanks Steven Andrew Mielke!). The bootloader is installed in
the section Bootloader Installation below.
For novice users, follow Ubuntu's tutorial. But do not reboot at the end of the installation. Press the button
Continue testing instead.
When you are done with Ubuntu's tutorial, jump to the section Bootloader Installation in this document.
For more advanced users, choose the last installation type: Something else. And jump to the next section
Partitioning.
5. Partitioning
The changes done in this section are not effectively written on the disk.
The actual partitioning will happen when we'll run the installation. Therefore, you can go back at any time and
try again.
Note: A new ESP's filesystem is displayed as ext4 in ubiquity when partitioning, before install. This is a
display bug. The ESP is a VFAT or FAT32 partition.
Note: Ignore the device with a single partition of 8014 MB, namely /dev/mmcblk0 .
Keep Windows
Ditch Windows
Delete each partition, except the ESP. The ESP is probably one of the first partition, its size is 100 MB,
and may be labeled SYSTEM .
Select the partition you want to delete
Press the - button to delete it.
Note: Alternatively, if you know what you are doing, you can create a new partition table and a new ESP.
Backup the old ESP, just in case.
6. Installation
Make sure 'Device for bootloader installation' is the right device, probably /dev/mmcblk2
Install now
…Installation…
When finished, Continue testing
7. Bootloader Installation
From now onward, we will run the commands as root. To obtain superuser privileges, execute
sudo -s
Do not use sudo for each command, since it fails with some commands ( for and > ).
Enable WiFi
/!\ Theses filenames are for T100TA and T100CHI only. Other T100's (T100TAF and 100H*) have other
brcmfmac numbers. See the troubleshooting section No WiFi at the end of this document.
/!\ The filename ends with sdio.txt. Do not overwrite the file ending with sdio.bin.
Find the EFI System Partition. This should be the VFAT partition next to /target
In the example below, it is mmcblk2p1
If you are unsure, check its size with lsblk , it should be about 100M.
lsblk -f
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
loop0 squashfs /rofs
sda
└─sda1 ntfs Restore 0A32F68B32F67AD1
sdb
└─sdb1 vfat XUBUNTU_18_ D85F-FC95 /cdrom
mmcblk2
├─mmcblk2p1 vfat 1DA4-A881
└─mmcblk2p2 ext4 a1994fa2-ddf3-...ff /target
mmcblk2boot0
mmcblk2boot1
mmcblk0
└─mmcblk0p1 vfat 9016-4EF8 /media/xubuntu/9016-4EF8
Here we go!
chroot /target /bin/bash
Verify that /dev /dev/pts /proc /run /sys and /boot/efi are mounted
findmnt
TARGET
/
├─/dev
│ └─/dev/pts
├─/proc
├─/run
├─/sys
└─/boot/efi
Install grub for EFI-IA32 architecture, and update its config file
apt update
apt install grub-efi-ia32 #grub-pc removed is normal behavior
grub-install --efi-directory /boot/efi
update-grub
Run efibootmgr to see if ubuntu is in BootCurrent and if it is first in BootOrder, as shown below:
$ efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0002
Boot0001* ubuntu
Boot0002* UEFI: USB stick
8. Boot options
Boot options must be edited in the file /etc/default/grub
nano /etc/default/grub
Power saving
If you want the system to boot faster, let's say 1 second after the GRUB boot screen
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
$ ll /usr/share/alsa/ucm/bytcr-rt5640
total 16
-rw-r--r-- 1 root root 8552 Aug 1 21:35 HiFi
-rw-r--r-- 1 root root 118 Aug 1 21:35 bytcr-rt5640.conf
pavucontrol
Configuration pane
Card Name: off
Built-in audio: Play HiFi quality music
Input device: ignore it, this is for your micro.
Output device
Port: Headphones or speaker playback
You are good!
If you still have no sound, see the troubleshooting section No Sound at the end of this document.
With hardware video decoding, a video player should use around 25% CPU when playing a 720p, h264 video
fullscreen, instead of 70-100% without hardware decoding.
14. Bluetooth
/!\ Same warning as Sound and WiFi, the following file is for T100TA and T100CHI only. Other T100's
(T100TAF and T100H*) have other Bluetooth device numbers.
Bluetooth should already partially work. For a better support, e.g. pairing and bonding, we need the firmware
file BCM4324B3.hcd in the folder /lib/firmware/brcm/ .
Troubleshooting
1. No WiFi
We have to find out which file your system needs.
Run dmesg
sudo dmesg
Find the following line, ignore the ...
brcmfmac ...: Direct firmware load for brcm/brcmfmacVWXYZ-sdio.bin for chip ...
For example, a T100TAF needs brcmfmac43340-sdio.txt .
You can download it on the ASUS group:
https://drive.google.com/drive/folders/0B4s5KNXf2Z36cUpzSURqaTk1TE0
2. No Sound
For any software, the rule of thumb is to override the configuration by creating a new .conf file in
/etc/software/directory.conf.d/ instead. In this way, the system won't complain during an upgrade of the
configuration file (Here daemon.conf for pulseaudio).
3. T100TAM Touchscreen
History
20181125
20181024
20180815
20180802
First version