yashsingh1/xdaforums huggingface dataset:
[Windows 8 Development and Hacking] paperWastage:
ubuntu x64 13.04, debuging x-server issues

[ 36.591] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so

[ 36.597] (II) Module fbdev: vendor="X.Org Foundation"

[ 36.597]	compiled for 1.12.99.902, module version = 0.4.3

[ 36.597]	Module class: X.Org Video Driver

[ 36.597]	ABI class: X.Org Video Driver, version 13.0

[ 36.597] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,

i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,

E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,

965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,

4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,

Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),

Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),

Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),

Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),

Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,

Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),

Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),

Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),

Haswell Server (GT2+), Haswell SDV Desktop (GT1),

Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),

Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),

Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),

Haswell SDV Server (GT2), Haswell SDV Server (GT2+),

Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),

Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),

Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),

Haswell ULT Server (GT1), Haswell ULT Server (GT2),

Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),

Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),

Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),

Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),

Haswell CRW Server (GT2), Haswell CRW Server (GT2+),

ValleyView PO board

...

[ 36.762] (II) VESA(0): initializing int10

[ 36.763] (EE) VESA(0): V_BIOS address 0x0 out of range
​

from

http://www.redhat.com/archives/rhl-devel-list/2009-December/msg00372.html

looks like 13.04 is able to recognize and load the necessary drivers, but crashes because our UEFI-only computer doesn't have a BIOS portion... or maybe 13.04 is using older stuff

EDIT: or does that error even matter? trying to force x to configure itself

EDIT2: it matters because VESA is configured to be the default/fallback driver. With the V_BIOS issue, it won't work. Tried to force it to use fbdev driver, but no luck (it loads, but nothing shows up)
[Windows 8 Development and Hacking] paperWastage:
I deleted the vesa_drv.so from /usr/lib/xorg/modules/drivers/ , forced it to start using fbdev... works, very slowly of course

will try the intel driver later

(it's definitely the vesa BIOS bug that's stopping it from working on 13.04... will debug 13.10 later)
[Windows 8 Development and Hacking] paperWastage:
<instructions below should be complete

got ubuntu 13.10 to boot to command prompt (with bootia32.efi and grub.cfg fixes below)

Rufus (GPT for UEFI + FAT + 64 kb+ 13.10 desktop x64 as bootable disk using ISO Image)

Note:

Good behavior:

After you select "Try Ubuntu" in grub, screen goes to blank, (?might appear as well) usb light disappears... wait < 30s, the screen should then show the logs and then cmd line)​

Bad Behavior:

After you select "Try Ubuntu" in grub, screen goes to blank, then the grub menu reappears (but nothing happens when you press arrow keys). (?might appear as well) usb light stays lighted. if you wait >5 minutes, nothing happens. just force reboot machine (hold power button), and reboot into windows, then UEFI and try again
​

/boot/grub/grub.cfg - replace with the text below

if loadfont /boot/grub/font.pf2 ; then
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi

set menu_color_normal=white/black
set menu_color_highlight=black/light-gray

menuentry "Try Ubuntu without installing" {
set gfxpayload=keep
linux	/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper text noacpi nomodeset --
initrd	/casper/initrd.lz
}
menuentry "Install Ubuntu" {
set gfxpayload=keep
linux	/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
initrd	/casper/initrd.lz
}
menuentry "OEM install (for manufacturers)" {
set gfxpayload=keep
linux	/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --
initrd	/casper/initrd.lz
}
menuentry "Check disc for defects" {
set gfxpayload=keep
linux	/casper/vmlinuz.efi boot=casper integrity-check quiet splash --
initrd	/casper/initrd.lz
}

(changes in grub is to disable efifb which causes screen flickering/corruption - video=vesa: off doesn't work, probably because vesa IS the fallback driver)

then boot. After you get to command line, remove the vesa_drv.so module from /usr/lib/xorg/modules/drivers/, type startx

touchscreen works on x64 13.10. still haven't had time to make x86 ISO work with bootia32.efi GRUB
[Windows 8 Development and Hacking] spunker88:
For Android-x86 without EFI support, I wonder if this method courtesy of Tyler Swindell on Youtube would work. This is what he used to get Android-x86 booting on the Surface.
[Windows 8 Development and Hacking] paperWastage:
that might work, forcing android-x86 to boot via grub.. thanks

been using android-ia, which doesn't use grub... uses another efitool, need to play with both android-x86 and android-ia later tonight
[Windows 8 Development and Hacking] Deltido:
Picking up on our conversation from SlickDeals.. I actually ended up buying one of these things and I was able to get an external hard drive recognized just by plugged into my usb OTG cable -- in windows. I even tried a USB mouse which worked perfectly.
[Windows 8 Development and Hacking] paperWastage:
yeah, my usb otg cable works now in windows (detects flash drive). no idea why it didn;t work before (maybe I unpluged it too early while it was detecting/installing the usb driver?)
[Windows 8 Development and Hacking] paperWastage:
got android to boot up, but uglily

need 2 flash drives, and a USB-OTG cable(to be able to connect using the microUSB port)... a USB-hub should work too

(basically, you're piggying back off the ubuntu grub2 bootloader, to load the android kernel and other stuff)

used my (existing & currently working) ubuntu 13.10 x64 bootable USB (made via Rufus, GPT partition with bootia32.efi fix)

copied the contents of android-x86-4.3-20130725.iso into the USB:/android/

modified contents of grub.cfg as per the post by spunker88 with some changes to the resolution

second flash drive had dd if=android-x86-4.3-20130725.iso of=/dev/sdb1

without this second flash drive, the android boot sequence stops at "Detecting Android-x86" and "VFS: could not find a valid V7 on sda1". probably something to do with android/kernel not liking the first drive having FAT instead of ext2/3/4

grub.cfg - add to the end, and select this during grub

submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=x86 video=1366x768 DEBUG=1 SRC=/android/
initrd /android/initrd.img
}
}

boot into USB, then grub, then select android.

android crashes to command line. forcing it to start (type exit twice), leads to the default android start screen, and eventually this

it is SUPER LAGGY. not usable
[Windows 8 Development and Hacking] costcutter:
Progress!! :D

Although its unusable, it's nice to see android on this device. So what do you think needs to be done to get android usable on this?
[Windows 8 Development and Hacking] paperWastage:
for both ubuntu/android, first steps (since it's booting) is to get the graphics driver working. right now, ubuntu is using fbdev and android is (i think) using efifb... both are running at 800x600 and laggy....

either I fix the VESA bug, or find the correct intel driver for the new Bay Trail IGP and use it

then, install ubuntu/android properly on the device, and then debug the rest (instead of through a live USB where changes would not persist from every reboot)
[Windows 8 Development and Hacking] pastime1971:
I'm trying with Fedora 20 alpha, but not much luck so far.

Got the grub2-efi to work with your tutorial (and some digging), but once I start installing Fedora, it seems to freeze.

Gonna try ubuntu over the weekend.
[Windows 8 Development and Hacking] paperWastage:
probably the vesa bug as well (if you are trying to install via gui)

attempting to fully install ubuntu on system and boot from it.... the bootia32.efi / bootx64.efi / grubx64.efi is making a mess here...

managed to get Windows Bootloader AND ubuntu grub listed as boot options... grub has problems though, dumps me into grub shell

EDIT: Think it;s easiest for me to try installing EFI Shell, and tinker from there

http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Efi-shell

EDIT2: For Windows 8 64-bit, the error is "This 64-bit application couldn't load because your PC doesn't have a 64-bit processor"

Looks like we need to enable Virtualization in the UEFI/BIOS... but there isn't such an option (the cpu Z3740 does support VT-x)
[Windows 8 Development and Hacking] Jhong2:
I've updated the howto with the latest patches. Battery & AC plugged-in status now works!

http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/
[Windows 8 Development and Hacking] tydem:
For me, after wiping the whole drive, updating all Windows drivers and BIOS (to 304), and installing Ubuntu GNOME Daily using Jhong2's instructions, Wifi is not working at all.

All correct firmware and NVRAM files are in place and the system does not seem to recognize the wireless card. dmesg shows nothing from the brcmfmac module and loading it manually does nothing either. I also booted an Arch Linux image with rEFInd that I prepared to extract the NVRAM, where I had network before the install. Now it's as if the card was gone. On Windows however it works fine. Which BIOS version are you using? I hope the updates did not break wifi permanently and that it's only some silly mistake on my part...

I also attached the dmesg I obtained when booting the stock Ubuntu kernel.
[Windows 8 Development and Hacking] Jhong2:
Strange, have you tried with a later kernel (try my latest instructions)? There was a change in naming for the firmware/nvram a few kernel versions ago -- they changed from generic names (brcmfmac-sdio.bin/txt to brcmfmacxxxxxx-sdio.txt).

The modules loaded are brcmfmac brcmutil cfg80211 mac80211.

I'm sure you'll be able to get it to work. Don't expect too much though; conection quality is rubbish (I use an external adaptor for now).

---------- Post added at 12:08 PM ---------- Previous post was at 12:05 PM ----------

In other news...

Some new patches adding support and acpi enumeration for the mpu6500 sensor have just appeared (http://www.spinics.net/lists/linux-acpi/msg49590.html)

I'm compiling and will add to the guide if they work. With this and the recent battery support, things will start looking good. Really the only major things missing now are backlight control and suspend/resume.
[Windows 8 Development and Hacking] tydem:
I know the signal is pretty bad, but it was workable with my previous install, especially using Wicd rather than NetworkManager. Said install also used the new path for firmware and nvram, so it's all correct. I compiled a 3.14 kernel from the sources you linked and not only does the issue persist, but it does not add any features like battery monitoring. Also, dumping the NVRAM only gives me garbage data after the BIOS update. Maybe the card is being switched off with no way to power it on from Linux?

I had a look at a kernel log from before the update, and it mentioned a SDIO card being found. Now it doesn't even seem to recognize that. So it's not a driver issue but something at a lower level. In other words, if you want Linux, don't update your BIOS.
[Windows 8 Development and Hacking] Jhong2:
I don't think the bios is your problem -- I updated to bios 304 today, didn't make any difference...
[Windows 8 Development and Hacking] tydem:
Did you update the wireless drivers? I'm at a loss, but maybe they flashed something on my card. I downloaded the latest ones that advertise a power benefit and installed them. Besides that I have no idea what could have caused my card to show up under Linux.

Besides this issue which seems to be specific to my machine, hardware support is pretty good on both Fedora and Ubuntu. Hopefully the final version of Fedora 21 will come with a kernel new enough to work on the T100 out of the box. GNOME 3 with Wayland will be awesome on this thing.
[Windows 8 Development and Hacking] JoinTheRealms:
Finally got around to trying this out, actually very surprised how smooth it is alredy. Many thanks too all involved!

Updated to the 3.14 kernel on jhong2s github, battery indication etc all working great.

[MENTION=2598146]tydem[/MENTION]

Unfortunately i have the same issue as you, so far no trace of a wifi device, ifconfig shows only loopback. I also flashed the broadcom update under windows, on 303 bios. Will keep investigating

edit: updated to 304, no change to wifi
[Windows 8 Development and Hacking] tydem:
Is there no mention at all of brcmfmac in the kernel log (dmesg)? I tried uninstalling the drivers and installing an older one, didn't work. The ASUS Radio Control utility also seems to do nothing. From what I've seen this looks like some powersave feature gone bad.
[Windows 8 Development and Hacking] JoinTheRealms:
Sorry will check dmesg soon, i also tried re-installing previous drivers and nothing. Really need someone else to confirm that there wifi isnt working after broadcom update which seem like a likely situation.
[Windows 8 Development and Hacking] huuuuuh:
Just tried Ubuntu on the T100 and i think, i will try to install it. But one question, is there a way to get internal bluetooth working? Im using a wireless bluetooth mouse, so it would be nice to have it working in ubuntu...
[Windows 8 Development and Hacking] chobit:
does it work if i want to install android os on it? i mean follow the instruction of changing the 32bit bootloader, thx
[Windows 8 Development and Hacking] diablow:
It's more complicated with Android - you'll have to compile your own kernel (e.g. Android x86 4.4.2 uses older kernel witout Bay Trail support). Also, it refuses to boot when placed in Ubuntu install USB, trick is to create additional partition for Android boot files.
[Windows 8 Development and Hacking] Jhong2:
Please can you post your nvram -- would be good to see if it has changed. If you're using "my" kernel, you should be able to access it under /sys/firmware/efi/efivars (you may need to sudo modprobe efivars first).
[Windows 8 Development and Hacking] Jhong2:
Sorry, I mean the content of the nvram-xxxx fike there.

Did you enable the sd card quirks as in the blog? If so, have you tried without?
[Windows 8 Development and Hacking] Jhong2:
Doesn't look like the NVRAM's changed then -- I can do a diff later.

If you do lsmod, is the sdhci module loaded? If not, try loading it. If still no joy, what devices do you have listed in /sys/bus/acpi/devices ? Your SDHCI host controller should be in there.
[Windows 8 Development and Hacking] JoinTheRealms:
[MENTION=5718951]Jhong2[/MENTION]

Built in wifi has just started working *out of the blue*:good: not actually sure what done it, but between enabling sd quirks then in efi settings, changed ubuntu to primary boot, in the next boot wifi is working?

On another note, sound seems fine to me? pretty load, cant hear any distortion from either speakers (i havnt touched alsamixer yet) also tested Minecraft and was blown away at how it performed, about an average 15+ fps increase on windows 8. Also battery drain is pretty much the same as windows, maybe slightly quicker drain on ubuntu.

Huge thanks for your work on this man!, if we can get suspend to ram working(i believe hibernate is working, but i couldn't get it to wake up), im gonna get rid of windows, i feel this tablet is made for Ubuntu/ Linux.
[Windows 8 Development and Hacking] richardyiu:
Intel releases the image for bay-trail, maybe you can try that:

https://download.01.org/android-ia/releases/android-4.4.2_r1-ia0-baytrail_generic-userdebug.zip
[Windows 8 Development and Hacking] nimdae:
Still uses 64 bit bootloader, it appears. It's specifically designed for the Intel NUC. It can probably be hacked and made to work on the T100.
[Windows 8 Development and Hacking] richardyiu:
You can download a 32bit bootloader from this page:

http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/
[Windows 8 Development and Hacking] nimdae:
There are various 32 bit UEFI loaders, but from what I've seen, they're for booting into grub. Intel's Android-AI distribution uses a customized gummiboot. I haven't been able to get a grub based bootloader to boot this distribution.

I have been able to get the Android x86 project to boot, but the experience is much worse than the Ubuntu one right now.

Intel's source provides the ability to build 32 bit stuff, including the UEFI bootloader. I just got my build environment working and waiting for it to build.
[Windows 8 Development and Hacking] Sacob:
good luck :D
[Windows 8 Development and Hacking] nimdae:
Unfortunately my build environment is still not working. I get an error indicating something is missing when it comes to actually building the image, but it doesn't say what. I suspect something failed to build but the build didn't error out on that.

It takes so long to get to that point that troubleshooting is a pain. I'm leaving it to build overnight with some better logging. It's tough for me to put a lot of time in this (thanks, job) so I'm not even sure I'm going to be successful.

If anyone has tips for building Intel's Android distribution in Ubuntu, let me know! It's already been a pain dealing with the fact Intel's build scripts are not in line with the latest AOSP (despite it being 4.4.2).
[Windows 8 Development and Hacking] diablow:
As mentioned in this post https://lists.01.org/pipermail/android-ia/2014-February/000475.html you could build just bootloader. But directions are a bit misleading, so currently I'm trying to build whole Android IA from source too. As far as I see it will take a few hours to download complete source code.
[Windows 8 Development and Hacking] tydem:
Indeed, the SD quirks option fixed the wireless issue (thanks a lot!), but it still has trouble connecting. I'll just remove Ubuntu and replace it with Arch, so as to get a "pure" GNOME 3.12 experience, better Wayland support, and Wicd instead of NetworkManager which worked great on the T100. If it has the same hardware support that Ubuntu has it may well become my daily driver.

To make sure SD and SDIO cards work correctly even on Live USB system, just pass the parameter via kernel command line. I did this to get the WiFi connection I need to install Arch. This is what I append to my kernel now:

video=VGA-1:1368x768e reboot=pci,force sdhci.debug_quirks=0x8000
[Windows 8 Development and Hacking] nimdae:
Getting the 32 bit EFI loader working on Intel's image was as easy as I thought. I now have a booting USB thumb drive. However, I'm not getting past the boot loader.

EFI Handover protocol not supported

Failed to start boot image 'Live Android Session': Invalid Parameter

I have my suspicions why. It'll just take hours to test my suspicions.
[Windows 8 Development and Hacking] Xentar712:
How did you get it to work? Or maybe you can share your build? I'd like to try it on my DV8P
[Windows 8 Development and Hacking] tasadar:
Have U checked that http://pocketnow.com/2014/04/03/64-bit-android and what devs think about it ?

Is that https://download.01.org/android-ia/releases/android-4.4.2_r1-ia0-baytrail_generic-userdebug.zip the coocked AOSP and how to install it ?

Sorry if questions seem dumb to someone !
[Windows 8 Development and Hacking] diablow:
Could you elaborate how to make working 32 bit EFI loader? The default build is 64bit, so I think we might need to compile it in 32bit, to work on a tablet.
[Windows 8 Development and Hacking] Batfink33:
I installed the new Android X86 on my Intel NUC 2820 and it runs brilliantly, super fast and smooth. Dual boot works well with Gummiboot. The only problem I have is I'd really like to install the Play Store and I can't.

Also benchmarked with Antutu and got 25000.
[Windows 8 Development and Hacking] nimdae:
There's a a config file where you can change a variable, then just run the build. It will make the USB drive boot to the UEFI boot loader, but not get you any further. 32 bit UEFI must boot a 32 bit program, and if you are using the hand off protocol from the kernel (as is the case with this image), the kernel must be 32 bit.

<source root>/device/intel/common/BoardConfig.mk

Find the line with "TARGET_UEFI_ARCH" and change the value to "i386"

It's possible you can extract the linux environment from the image and use UEFI enabled grub with fakebios to get past that. I haven't tested it yet so I'm not really sure. It might be worth investigating how Ubuntu (or other distros) make things work on the old Apple hardware with 32 bit EFI since from what I've read, it has the same problem of 32 bit must boot 32 bit.

As is, that image will not work on the T100. If you try to boot it, it will fail. It will likely fail on any device running the same BayTrail platform. The NUC (what this image targets) is BayTrail, but not the same Atom series.

As far as an update on my progress:

Intel's modifications to the kernel are not 32 bit friendly. I've specified a 32 bit build and confirmed in the generated kernel build config that it should be building 32 bit, but there are parts that I suspect are Intel modifications that are 64 bit only and are not wrapped in ifdefs.

I took the generated kernel compile config and imported it in the 3.14 source to test the config against it and it compiled without error, telling me that it is very likely Intel's hacks. I'm not sure what all Intel modified in the kernel and I'm not sure how to approach this for the moment. For now, I can't get it working.
[Windows 8 Development and Hacking] tydem:
Before 3.15 implements native mixed mode support, I think it's a better idea to try with GRUB. I have booted Android-x86 before with it and it should work. Will try making a working Android USB drive, although the lack of efivars on x64 might cause trouble (3.15 will fix that as well).
[Windows 8 Development and Hacking] nimdae:
This is good to know. In my research, rather than finding good solutions, I've mostly seen a lot of resistance in adopting this type of hardware arrangement because "who would do something like that?" or "there's not enough of that out there to invest the time and effort."

I'm actually abandoning my efforts of a pure 32 bit build. There's too much in Intel's source that requires 64 bit. I've started examining how the images are built and will try to put together something using grub.
[Windows 8 Development and Hacking] diablow:
64-bit Ubuntu image boots on my tablet with 32-bit EFI after adding bootia32.efi file, so why there should be problems booting Android IA? I've tried booting Android IA using a chainloader from other boot loader, but couldn't make it work.

There was mentioned, that Android IA baytrail builds are targeted for Celeron CPUs, not Atom, which are found on tablets (http://xdaforums.com/showpost.php?p=51664470&postcount=44) . This actually made me return to Android-x86 and try to build more recent kernel.
[Windows 8 Development and Hacking] nimdae:
The bootia32.efi you are using is a grub boot loader. Intel's Android build uses a modified gummiboot.

Gummiboot loads other EFI programs for handover to the OS. Grub, on the other hand, does not. In fact, grub can fake bios boot for non-EFI enabled kernels.
[Windows 8 Development and Hacking] tydem:
Looks like some efivars-related bug is causing a kernel panic when booting from GRUB. A patched kernel might fix that, but I'm afraid the NUC images as such are useless on the T100.