[FAQ] Asus T100: Installing custom OS (android/ubuntu/*nix/Windows 7/Windows 8 x64)

Search This thread

TheMoro

Member
Dec 22, 2013
21
14
Just finished compiling the new kernel, and its working great! backlight is finally adjustable, and it doesn't freeze up like it used to do on 3.16 kernels. Though I don't seem to have the wifi or SD card reader working. Were there any steps needed to make these work? It seems like the wifi driver is loading, as I have the brcmfmac listed with lsmod, but no network device is shown.
 

jonpry

Senior Member
Apr 22, 2010
58
110
Just finished compiling the new kernel, and its working great! backlight is finally adjustable, and it doesn't freeze up like it used to do on 3.16 kernels. Though I don't seem to have the wifi or SD card reader working. Were there any steps needed to make these work? It seems like the wifi driver is loading, as I have the brcmfmac listed with lsmod, but no network device is shown.

Sdcard reader isn't tested. Probably won't work.

Wifi should work. Make sure your firmware has been copied into /lib/firmware/3.17.0/brcm/
Don't use any of the "modded" nvram files. That stuff is a crock. Get yours from efi vars or one of the non modded ones available.

Similar thing is going on with sound. The firmware name has changed though. http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/intel
 

TheMoro

Member
Dec 22, 2013
21
14

TheMoro

Member
Dec 22, 2013
21
14

jonpry

Senior Member
Apr 22, 2010
58
110
I have all the firmware in the /lib/firmware/intel directory, but no modules are loading.. What modules should be loading up to use sound? maybe I can modprobe them in? All I get right now is no sound card detected.

one of these probably loads the others but i dunno which one. all automatic here.

sound/soc/intel/snd-soc-sst-acpi.ko
sound/soc/intel/snd-soc-sst-baytrail-pcm.ko
sound/soc/intel/snd-soc-sst-byt-rt5640-mach.ko
sound/soc/intel/snd-soc-sst-dsp.ko

check dmesg for errors
 

Scayris

Member
Feb 14, 2014
18
1
Ljubljana
I've I've reinstalled Ubuntu Utopic x64 on my t100 yesterday (once again following the pdf tutorial from here and using provided drivers: https://plus.google.com/u/0/communities/117853703024346186936) and put vanilla 3.17.0 with Jonpry's (thanks again) kernel patches on it. Took it to college today and here are my findings.

Let's do the good part first. WiFi works perfectly. It never once dropped connection and even managed to connect and stay connected to the obscurity that is Eduroam network (which I haven't managed to achieve on t100 with any kernel before now). Screen brightness works correctly (it's a bit low after boot and doesn't remember last value on reboot but I could barely care less about that right now) and screen seems to turn off completely as well once it locks (tested with gnome-session-flashback and Unity). Keyboard shortcuts for brightness don't work, but settings utility does. Filesystem seems to work fine, I've been getting some funny errors with APT, but that's probably due to a non-Ubuntu kernel and not filesystem corruption. Since I've seen it mentioned in an earlier post - SD card works out of the box and has continued to do so on every kernel I tried out.

Now for the bad parts.. I'm comparing this to 3.17.0 built by Ubuntu team and using the drivers from the above mentioned tutorial. Graphics drivers seem to be somewhat broken as all the touchscreen input becomes extremely laggy. Same movements worked perfectly on Ubuntu kernel and mouse input still seems to do on this one, but the touchscreen is terribly slow. (I'm talking dragging around windows, scrolling webpages on Chromium, pulling around icons on Unity and drawing squares on desktop, it's all the same). This works nicely even on Ubuntu live session, so we're probably just missing a driver in kconfig. Next, I couldn't get the sound to work , while it worked perfectly on Ubuntu kernel. I've messed around with alsamixer a bit, but only managed to get it to produce some terribly distorted sounds so I ended up just resetting it to the settings given through sound.state file in tutorial. It doesn't work, but at least it's safe (earlier attempts with sound broke stuff if I recall correctly). Last one is the power button, which is also dead, though it worked before. You can use it for hard reset naturally, but OS won't register it.

Overall the system is much more useful for what I mainly use it for (which is to take notes and write code on it 6 or so hours a day). Now I'm a newbie at all this, but I think that by using the combination of these patches and the files provided in tutorial I linked this could come close to being fully functional in laptop mode. I'm guessing it's just a matter of tweaking kernel configuration?
 

jonpry

Senior Member
Apr 22, 2010
58
110
I haven't had any problem with sound. The firmware file is different on 3.17. Need the latest one from linux-firmware.git. Name has changed and the files themselves seem to be substantially different. I used the asound.state from jwfhome.com and had no problems. At some point I noticed bad sound from some pulse clients and changed the pulse audio config to only use 48khz. Really seems to depend on the program though. Gnome/firefox/flash all seem to work without that. Was just some random audio player that was barfing.

I would like to get battery monitor working. Something is not right with the acpi-i2c support in 3.17. Yet to figure out exactly what and it is not the only problem. I have some kludge but no dice.

Edit:
WRT APT errors. Keep in mind that every kernel except mine, 3.17 or not, is blowing up your data. The only exception may be 32bit builds but I haven't personally confirmed this. Every file/directory on emmc is all at risk when you are running those kernels. There is no telling how much damage has accumulated from that stuff. I ended up having to do fresh install with my kernel because I just couldn't repair what all happened to my FS.
 
Last edited:

Scayris

Member
Feb 14, 2014
18
1
Ljubljana
Well, turns out that even with your patches it screwed up the filesystem. Won't start up normally anymore, so I'll have to reinstall it again. May I ask which distro you're running? I'd like to try and go with that so that we're on a similar setup.
 

jonpry

Senior Member
Apr 22, 2010
58
110
Well, turns out that even with your patches it screwed up the filesystem. Won't start up normally anymore, so I'll have to reinstall it again. May I ask which distro you're running? I'd like to try and go with that so that we're on a similar setup.

Hmm thats not good. I ran debsums hundred times or so and wasn't able to find any more errors. I'm using Debian Jessie. There is no reasonable installer for this and I have been setting stuff up pretty manually with debootstrap and manual grub.cfg. At some point in this thread I linked to a jessie disk image i made. It is for USB disk but could be modified. It is also possible to debootstrap a debian install from an ubuntu one, and even to dist-upgrade between the two. I have doubts that userspace would cause disk corruption. Thing is that if your filesystem has ever been touch by the bad kernel you can be in for a real wild ride. The filesystem tables themselves become corrupted at some point. So things can appear to be working normally, but in fact a file, say some important one, is mapped to filesystem blocks that are not marked as allocated in the bitfields. Then when some new file is written, a block being used by the important file may be reallocated and then overwritten with data belonging to the new file. This leads to utter destruction and there is no indication of when it is going to happen. Fschk seems to only figure this out once it is too late.

Been down that road, fixed the filesystem and then filesystem still exploded on me. Since running a system installed and only ever used with good kernel it has stopped.
 

TheMoro

Member
Dec 22, 2013
21
14
Well, my filesystem blew up again... After an fsck check, run at boot, a buch of files got lost, and as a result I can no longer boot. What's strange is that it was working flawlessly before, and since then, I've been using windows to do some work. Last time this happened, I was getting strange crashes and such long before the whole thing blew up.

This was an Arch system, created with VirtualBox with a raw virtual disk, to setup the filesystem, the kernel, etc using pacstrap (sort of like debootstrap). However, I still needed to boot into a liveCD in order to make the initramfs. Is there a way around using the liveCD (which does not have the patched kernel) ? As far as I can remember, thats the only time the patched kernel was not used.

Over the weekend, I may try cross compiling a 32bit kernel, and checking if that fares any better. Is there anything I can provide/any way that I can help solve this?
 

1212121212121212

Senior Member
Aug 5, 2011
136
15
Android would be beast on this machine

Well, turns out that even with your patches it screwed up the filesystem. Won't start up normally anymore, so I'll have to reinstall it again. May I ask which distro you're running? I'd like to try and go with that so that we're on a similar setup.



Dobro Dan :)

My mom is from Maribor. The most beautiful place I have ever been. You live in the greatest country on earth :)

Greetings from Canada
 

Scayris

Member
Feb 14, 2014
18
1
Ljubljana
I hear they're working on that over at Console OS.

Also, thanks :) I'm not from Maribor myself but I do have a couple of friends up there :D

As far as my installation attempts go, it'll probably take me a few weeks, since college is keeping me real busy right now..
 

cheatman

Senior Member
May 21, 2007
589
2,161
Migration Institute
Ok guys, let me jump in on the bandwagon. Here's my take on various improvements I made to running Android on the T100.
First off, I am running the T100 image update posted on the Android-x86 goup, here: https://groups.google.com/forum/#!msg/android-x86/FUiFCtrgc6I/Fqt8Rg-fpQkJ

What I managed to hack together up to now to improve usability:
- Dual-boot Android and Windows 8 using just the tablet (undocked, boot from Windows directly to Android and vice-versa)
- Install the Android-x86 system image in read/write mode (Titanium Backup runs fine etc.)
- Fix the Android key layout to use the dock F-keys to control volume (F11 & F12), power (F1) and mute (F10). Tablet buttons not working - no driver
- Manual rotation using scripts (solution sucks, better to use Play store apps)

I can provide info on any of the above, let me know what details are required.

Lastly, I see the backlight problem has been fixed in recent kernel patches. Would any of you guys mind sharing the compiled kernel image with backlight working? I'm really not up to setting up a kernel building environment as I don't plan on making kernel tweaks and I don't want to wait for a new complete build just for this improvement.

PS: I'm looking for a kernel build with just the backlight solved, without the SD card fix.

Thanks,
C.
 
  • Like
Reactions: feduss

KingLegend

Member
Aug 3, 2012
41
5
Ok guys, let me jump in on the bandwagon. Here's my take on various improvements I made to running Android on the T100.
First off, I am running the T100 image update posted on the Android-x86 goup, here: https://groups.google.com/forum/#!msg/android-x86/FUiFCtrgc6I/Fqt8Rg-fpQkJ

What I managed to hack together up to now to improve usability:
- Dual-boot Android and Windows 8 using just the tablet (undocked, boot from Windows directly to Android and vice-versa)
- Install the Android-x86 system image in read/write mode (Titanium Backup runs fine etc.)
- Fix the Android key layout to use the dock F-keys to control volume (F11 & F12), power (F1) and mute (F10). Tablet buttons not working - no driver
- Manual rotation using scripts (solution sucks, better to use Play store apps)

I can provide info on any of the above, let me know what details are required.

Lastly, I see the backlight problem has been fixed in recent kernel patches. Would any of you guys mind sharing the compiled kernel image with backlight working? I'm really not up to setting up a kernel building environment as I don't plan on making kernel tweaks and I don't want to wait for a new complete build just for this improvement.

PS: I'm looking for a kernel build with just the backlight solved, without the SD card fix.

Thanks,
C.

how did you get dual boot using just the tablet?
p.s i'm using it right now and it's amazing, zero lag
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    [4 April 2014]I haven't had time to play with my device or update fully the info in this post
    Jhong2 has an updated post on how to get ubuntu working on the Asus T100
    http://forum.xda-developers.com/showpost.php?p=51291244&postcount=181
    http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/

    (do search for the specific topic headers to jump to them)
    Post 1: Global Info
    UEFI:
    Bootloader auto-detection path:
    Secure Boot
    Partition Table for Live USB sticks:
    How to boot from USB stick
    Info for various operating systems:
    Hardware info:
    /cpu/cpuinfo:

    Post 2: <backup/ archived infomation>

    Post 3: Files
    grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32​




    ---------------------------------------------------------------------------------------


    Global information
    for BIOS 214 (2013.09.25), version loaded on retail T100 units

    UEFI:

    Bootloader auto-detection path:
    (bootloader is only 32-bit compatible)
    /efi/BOOT/bootia32.efi
    WILL NOT pick up the x64 location /efi/BOOT/bootx64.efi

    Secure Boot

    You should disable Secure Boot in UEFI/Setup-Utility-Menu-> Security tab-> Secure Boot Menu -> Disable


    Partition Table for Live USB sticks:
    GPT or MBR works
    Use Rufus (works for Windows/Unix ISOs) or Windows 7 USB Download Tool (works for Windows 7 / Windows 8)

    How to boot from USB stick

    NOTE:

    If you don't see the USB drive on the boot list or the UEFI/Setup-utility, this means you have a badly prepped USB live drive, or the boot-list/UEFI/Setup-utility was loaded before the USB drive was read.
    If you are on the boot list, boot into UEFI/Setup-utility. Then, go to the last tab, save changes and restart while holding F2 (to force the next reboot to go back into UEFI/Setup-utility). If you still don't see the USB drive after doing this multiple times, then you have a badly prepped USB drive.

    I find using Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image) to consistently get a working bootable USB drive

    Option 1a) Boot to UEFI USB drive from Windows (works only if your USB is correctly prepped)
    1. Boot into Windows
    2. Swipe from right, click on settings.
    3. Click on Power. Press and hold the shift key, and then click on Restart
    4. A Blue menu should show up. Click on Use a device->click on the device name (might not show up if USB isn't prepped properly)
    5. Device should reboot into the USB

    Option 1b) Boot to UEFI/Setup-Utility-menu from Windows (easiest, and almost no way to screw it up)
    1. Boot into Windows
    2. Swipe from right, click on settings.
    3. Click on Power. Press and hold the shift key, and then click on Restart
    4. A Blue menu should show up. Click on Troubleshoot-> Advanced Options-> UEFI Firmware Settings
    5. Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive

    NOTE:
    For options 2a and 2b, if you see the ASUS logo and circle loading icon, you either:
    • Pressed button (ESCAPE/F2) too late. Solution: Reboot and try again
    • Have Fast startup enabled, and did the steps with the device in shutdown mode. Windows will cache the kernel/other stuff, and you might not be able to get to UEFI. Solution: Reboot from Windows and try again(reboot does not trigger caching). Or disable Fast Startup


    Option 2a) Boot to UEFI/Setup-Utility-menu
    1. Inside Windows, restart system. Press and hold the F2 key
    2. You should get into the Aptio Setup Utility screen
    3. Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive

    Option 2b) Boot Menu
    1. Inside Windows, restart system. When screen goes blank, press and hold the ESCAPE key (if you press it too early, Windows might interpret you as cancelling the restart process)
    2. You should get a list of bootable devices
    3. If you see the ASUS logo, you've pressed the ESCAPE key too late. Restart and retry

    Info for various operating systems:

    You should backup the recovery partition to a separate USB key. Alternatively, you can do it with this ASUS utility Backtracker that HatesForums pointed me to

    Windows:



    Windows 8.1

    • x86: (Status: Works but missing drivers)
      Used Windows 7 USB Download Tool or Rufus to create bootable USB. Using en_windows_8_1_x86_dvd_2707392 from MSDN (x86 8.1 Regular & Pro ISO), able to install W8.1 x86 and boot to it (missing a few drivers, eg touch screen doesn't work, no sound). Windows is automatically activated without need for key. First boot had 25.7GB free out of 33.6GB.
    • x64: (Status: Not yet working)
      Used Windows 7 USB Download Tool or Rufus to create bootable USB. ISO does not contain bootia32.efi. Copied that file from the x86 ISO to USB, able to boot, but the installer complains that the processor isn't 64-bit compatible
    Windows 7

    • x86: (Status: unknown)
      ISO does not contain efi
    • x64: (Status: unknown
      ISO only contains x64 efi
    Unix:

    Ubuntu:

    You need an EFI-compatible distro. For ubuntu, x64 EFI is enabled since 12.04-2. However, we'll need to include x86 EFI because our bootloader only reads x86 EFIs
    • 13.04 x64 desktop- (Status: boots to GUI using fbdev)
      Used Rufus(GPT for UEFI + FAT + 64 kb+ raring x64 as bootable disk using ISO Image) to create bootable USB. Copied over the bootia32 to /efi/boot/
      there is a bug in VESA where it queries for a BIOS-only command and crashes. Forcing xserver to use fbdev fixes this problem
    • 13.10 x64 desktop- (Status: boots to GUI using fbdev
      Same problems as 13.04 x64 plus one addition efifb problem
      see post for more details - touchscreen works, but no wifi

    Android:
    • android-ia - (Status: No x86 UEFI bootloader)
      Generic UEFI Installer android-4.2.2_r1-ia3 does not come with x86 UEFI bootloader. it does not use grub, so can't just use ubuntu's x86 grub2 efi. Need to compile it from source
    • android-x86 - (Status: Bootable but slow)
      Uses grub, can piggy-back on the ubuntu x64 13.10 bootia.efi grub. Some workarounds needed, see this post
      external/efitools/Android.mk
      # TODO: support ia32 prebuilt

      ifeq ($(TARGET_KERNEL_ARCH),x86_64)

      arch_name := x86_64


    /cpu/cpuinfo:
    taken from a x64 13.04 live USB
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 0
    cpu cores : 4
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 1
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 1
    cpu cores : 4
    apicid : 2
    initial apicid : 2
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 2
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 2
    cpu cores : 4
    apicid : 4
    initial apicid : 4
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 3
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 3
    cpu cores : 4
    apicid : 6
    initial apicid : 6
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:


    Hardware info:

    • The microUSB slot is USB-HOST-capable (i.e. with a USB OTG cable or Y cable, you can connect a USB flash drive to the microUSB slot
    • Amazon.de and Asus.de posted a T100 version with 500GB drive on the keyboard base. No pictures yet
    • Internal eMMC, 108MB/s 44MB/s read/write on sequential. CrystalDiskMark here
    • External microSD(HC/XC) reader is NOT UHS-1 compatible. Someone over at liliputing comments posted his atto benchmark

      64GB Samsung microSDXC card came in the mail today, I did some ATTO disk tests using the T100's built-in microSD reader and a USB 3.0 reader from Transcend.

      Unfortunately, it looks like the built-in reader is connected via USB 2.0. It maxed out at 23.8 MB/s read and 17.2 MB/s write, while the USB 3.0 reader maxed out at 71.3 MB/s read and 21.3 MB/s write. The card is rated at 70 MB/s read and 20 MB/s write.
    7
    Android good news and bad

    Well, after a few more very late nights, i was able to get to the android main screen, once. Unfortunately, its completely unrepeatable. After a lot of looking around, I think the main problem is that the drivers for the graphics that are in android-x86 are just not new enough. I did find here, repositories for the latest intel graphics driver sources. https://01.org/linuxgraphics/community?qt-projects_aggregated_links=2.

    However, I talked to a friend at Intel who works on android and according to him, Intel is going to be releasing a public beta for android on Bay Trail in the next 3 weeks. So I'm going to wait for that before I try again.

    If anyone wants to work on it before then, the main change I made to get the i915 driver to at least load and work for text console was in kernel/driver/gpu/drm/i915/i915_drv.c.
    around line 118, change
    Code:
    unsigned int i915_preliminary_hw_support __read_mostly = 0;
    to 
    unsigned int i915_preliminary_hw_support __read_mostly = [B]1[/B];
    I couldn't find another way to change this besides changing the source.

    Here is a pic of the one time i got to the main android screen.

    Android_on_t100_small.jpg
    7
    The i915 GPU driver does work fine *almost* out of the box for the 3.12 kernels. I havn't tested 3.13 yet, but the problem may be similar. The garbled screen is simply due to an incorrect resolution. It doesn't seem to detect our native resolution right. Using the boot parameter video=VGA-1:1366x768 works, at least when I tested it on Arch. For Ubuntu, the same boot parameter worked, but only for the console.The X session was still bad. From there I had to use xrandr to create a new video mode, and somehow manage to use the (still garbled) screen to access a terminal window. It worked, but I wouldn't recommend it ;) You might also be able to setup an Xorg config to set the resolution on startup.
    Just letting folks know, the GPU works at least in 3.12 kernels.
    6
    Made a fair bit of progress.

    Managed to get 3.14-rc2 booting no problem, and grub installed properly, so am booting up normally; it just needs the video=VGA-1:1366x768e parameter.

    Xrandr works fine, so screen rotation will be no problem once we have the accelerometer / orientation sensor cracked.

    I got wifi working using the brcmfmac43241b4-sdio driver, but signal strength was weak. I believe this was because the nvram obtained through nvramtool was not correct; AFAIK (and I'm still learning on this), since uefi is 32-bit, access to uefi / nvram vars is unavailable from within a 64-bit linux. So instead I tried to extract nvram from a uefi shell, and converted the hexdump to ascii. This seems to work much better. I've attached the nvram as brcmfmac4321b4-sdio.txt. This just needs to be copied to /lib/firmware/brcm along with the firmware.

    All ACPI is basically still broken, but I'll see what we can get.

    Sound seems a long way off. ACPI IDs have been added for the "Intel SST audio device" since kernel 3.13, but Intel hasn't provided a driver yet. Haven't looked closely yet.

    It seems someone is working on the battery monitor.

    WYgvptb.jpg
    6
    Iconia8 source

    I started messing with 3.17 kernel to see if anything works better. Had lots of trouble getting my kconfig correct of all things, but looks like some positive progress. 3.17 combined with some code i ripped from iconia8 gives me 100% good wifi and also the eMMC is working much better and is now in HS200 mode. Apparently chip can not enter C6 during eMMC write. This is very difficult to ensure using acpi_idle driver. I have something hacked together by accessing /dev/cpu_dma_latency but it wastes a lot of power and isn't a permanent solution.

    If only I could get backlight control to work :/ Would also be nice to have the two finger scroll function. No scroll on the small screen is a serious pain.

    Edit:

    Have a reasonable solution to the c6 wake lock. Also got some backlight control working. Can adjust, still missing stuff for completely turning it off/on. Code here on top of vanilla 3.17. https://github.com/jonpry/t100_patches Doesn't include battery, everything else works pretty good. I wrote couple hundred GB to eMMC without error. No problems with wifi either. I think there is one more eMMC patch we need but only effects samsung chips which i apparently don't have. Use included kconfig or you will have problems!