This little tablet comes with Windows 8.1 installed and clearly has all the right drivers available for the OEM operating system to support the hardware. Regrettably, the same cannot be said for Linux. While various users are getting close to a working system, installing Linux on the T100 is fraught with difficulties – and some dangers!
While I have installed a number of versions of Ubuntu Linux on this machine, recently I found that the installers for a number of distros (notably Versions 15.04 beta, 14.10 and 14.04) were not completing properly. This culminated in my T100 no longer booting into grub – nor Windows. Even worse, neither F2 (setup) nor F9 (recovery) produced any flicker of life on the screen. My T100 was bricked!
I spent a couple of days trying to revive the tablet to no avail. It required a trip to an Asus service centre for major surgery.
The machine was returned restored to factory settings, and was soon back running Windows 8.1. However, I am afraid that I have lost considerable faith in the T100’s ability to support Linux, and I’m not sure that I want to continue the experiment on this hardware platform. In my view, one shouldn’t be able to crash a machine beyond the point of normal recovery simply by installing software, but it would appear that I may have managed this on the T100.
So, for now at least, I plan to take a break from playing with Linux on the T100. For those of you who are braver, the Asus T100 Ubuntu Google+ group is working hard to make things happen. So, check out their web site (https://plus.google.com/communities/117853703024346186936) for current details. For now, I will be lurking on the site to see how things progress!
I recently installed Linux Mint 17 (Rebecca) on a Dell Inspiron laptop that had Windows 8.1 pre-installed and hence was using the Unified Extensible Firmware Interface (UEFI), GUID Partition Table (GPT), and had Secure Boot enabled by default. My first attempt, using a more-or-less “conventional” installation method ended up with Mint booting immediately once the computer was restarted, i.e. no grub boot menu was displayed to optionally load Windows. A few tweaks to the system settings and this problem was easily resolved.
While a kernel patch for the mmcblk0rpmb timeout errors experienced on the T100’s solid state drive is available, the fix hasn’t yet made it into a Linux distro. Consequently, one has to suffer through the long delays produced by the timeouts while installing Linux, before being able to replace the kernel with a patched version that eliminates the timeouts in all future operations. At least, one had to do this before a temporary fix was suggested.
The second thing to do after installing the 64-bit daily build of Ubuntu Linux Version 15.04 (Vivid Vervet), and updating the Wi-Fi network connection, was to replace the Linux kernel with a patched version specific to the T100.
After installing a 64-bit daily build of Ubuntu Linux Version 15.04 (Vivid Vervet). As described in the previous post, I switched the Internet connection from the temporary use of a wireless USB adapter to the T100’s on-board wireless card. I followed the instructions given earlier (Establishing Wi-Fi connectivity on the T100) with one exception.
In a previous post (Installing Linux on the Asus Transformer Book T100) I provided details of how to install a specific 32-bit distro of Ubuntu Linux on the T100. Subsequently, many people have spent a lot of time improving the available software in order to get most of the T100’s hardware features (e.g. touch screen, battery monitor) to work. In particular, it is possible to install a 64-bit version of Ubuntu, with a 32-bit bootloader, on the T100. This includes the current release, Utopic Unicorn (Version 14.10), or even the development version of Vivid Vervet (Version 15.04). However, the steps required to do this are somewhat different than for the custom ISO, so this posting attempts to consolidate all the required instructions in a single place.
Synchronizing my dedicated data partition with my external USB backup drive has always been problematic when daylight saving time (DST) comes and goes. The problem is that – instantly – all the files on the external (FAT) drive appear to become one hour older (or younger) than the same files on the hard drive. Some versions of FreeFileSync have a fix for this issue. An alternative is to reset the time stamp on the files on the external drive.