yashsingh1/xdaforums huggingface dataset:
[Windows 8 Development and Hacking] TheMoro:
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.
[Windows 8 Development and Hacking] jonpry:
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
[Windows 8 Development and Hacking] TheMoro:
Yeah, I just realized I forgot to copy my NVRAM. and yes, I copied it from /sys/firmware/efi/efivars/nvram-* . Following jfwells instructions in his blog http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/ also fixed the sdcard by adding some magic debug options to the sdhci module. However, I forgot to get wpa_supplicant package while I was installingso Illl post again once I've tested the wifi.
[Windows 8 Development and Hacking] TheMoro:
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.
[Windows 8 Development and Hacking] jonpry:
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
[Windows 8 Development and Hacking] TheMoro:
Seems I didn't build those modules :/ I'll have to go check my kernel configuration..
[Windows 8 Development and Hacking] dvijetrecine:
hey guys, any of you mind to share compiled 3.17 kernel for android by any chance? please?
[Windows 8 Development and Hacking] TheMoro:
I'll see if I can post my kernel later this evening, when I get back home.
[Windows 8 Development and Hacking] Scayris:
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?
[Windows 8 Development and Hacking] jonpry:
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.
[Windows 8 Development and Hacking] Scayris:
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.
[Windows 8 Development and Hacking] jonpry:
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.
[Windows 8 Development and Hacking] TheMoro:
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?
[Windows 8 Development and Hacking] 1212121212121212:
Android would be beast on this machine

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
[Windows 8 Development and Hacking] Scayris:
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..
[Windows 8 Development and Hacking] speculatrix:
didn't read every pages as I am late to this discussion

I assume people have tried the official Intel Android-on-baytrail installers?

https://01.org/android-ia/downloads
[Windows 8 Development and Hacking] hillbeast:
Yeah and they use 64 bit bootloaders and our UEFI is limited to booting 32 bit bootloaders only. You can chainload a 64 bit kernel from a 32 bit bootloader however.
[Windows 8 Development and Hacking] JoinTheRealms:
Im hoping this will work on console os also, first developer release will only be for x64 bootloaders only.
[Windows 8 Development and Hacking] cheatman:
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.
[Windows 8 Development and Hacking] KingLegend:
how did you get dual boot using just the tablet?

p.s i'm using it right now and it's amazing, zero lag
[Windows 8 Development and Hacking] :
I would love to help but have not been able to get my hands on a device yet sadly. When I do get it I can help test theories here aswell. I will also subject it to the Computer engineering class at my university. lol
[Windows 8 Development and Hacking] paperWastage:
btw, if you want a disk cloning / recovery image, I've always liked clonezilla:

you'll need anything on/after 20130807-saucy (this is where they enabled SD card device /dev/mmcblk0). Ubuntu because I've more familiar with it than debian. you'll need the 64-bit version where (U)EFI Grub is automatically included

http://clonezilla.org/downloads/alternative/changelog.php

Cloning my disk using clonezilla-live-20130807-saucy-amd64.iso (no edits/tricks necessary... just use Rufus to create a bootable usb), will let you know if I have any problems (able to boot to UI and mount /dev/mmcblk0)

I've tried the latest clonezilla-live-20131022-saucy-amd64.iso - it didn't have the 32-bit grub2 boot file, so can't use this without tweaking
[Windows 8 Development and Hacking] pastime1971:
I successfully compiled bootia32.efi on fedora and it is bootable, but then it crashes upon starting.

Fedora uses linuxefi and initrdefi while Ubuntu uses linux and initrd, which could be an issue that I am facing.

does anyone know the difference ?

---------- Post added at 07:43 PM ---------- Previous post was at 07:22 PM ----------

also more recently here at https://bugzilla.redhat.com/show_bug.cgi?id=977816
[Windows 8 Development and Hacking] paperWastage:
need to read more about linuxefi and initrdefi.... need more knowledge on linux OS/kernel stuff

I'll try to read more about the V_BIOS (video BIOS) problem later

btw, managed to get grub and windows boot manager to play nicely (somewhat)... will post exact (reproducible) steps and files later once I clean and test it

//basically, inside windows, shrink partition to free up space

you'll need to recompile grub2 with the modules "normal" and "configfile" (will post my files later)

you can boot 13.10 x64 ubuntu from this post, install to disk (create a new partition from the free-up space, install grub2 bootloader onto /dev/mmcblk0p2 or whichever partition has the EFI flag (which is where the EFI bootloader resides)

then you'll need to mount /dev/mmcblk0p2 and copy the fixed bootia32.efi somewhere there

reboot to windows, add the location of bootia32.efi into bcdedit

now, ubuntu boots up with vesa problems, but at least it is loading GUI (fbdev)at native resolution

EDIT2:

Well, the two priorities are getting the graphics driver and wifi driver (or alternatively, bluetooth connection sharing)

graphics: right now, using fbdev, causes the CPU to spike between 25%-50% usage.

http://www.phoronix.com/scan.php?page=news_item&px=MTM1NjI --> this should work

13.10 uses the 3.11 kernel

wifi: Broadcom bcmsdh43xx broadcom 802.11abgn wireless SDIO adapter

I see USB/PCI-based Broadcom BCM43xx drivers, but not for the SDIO... lspci/lsusb doesn't show up anything broadcom related... perhaps there's some internal USB hub that's not correctly configured in ubuntu

EDIT3: trying to test drivers on the T100 without a working internet connection is a pain

going to pop by BestBuy/B&H/Adorama to get a USB->Ethernet dongle (with full linux plug&play support)... hopefully it won't be too expensive

EDIT3.5: going to get a kanex Dualrole Gigabit Ethernet+USB 3.0 3-port hub... only $41 at B&H (surprisingly cheaper than amazon), comes with linux source for drivers, contains a ax88179 chip which is linux-supported as well. according to this, 13.10 should have the driver included in kernel as well

EDIT3.6: decided to get the kanex gigabit ethernet only (not the hub), didn't want the hub to be hanging from the usb port, and most likely hubs require external power

kanex gigabit ethernet works windows and linux(plug and play). on windows, transferring files via samba share is only 9.35MB/s even though both sides report 1.0gbs link... dunno why
[Windows 8 Development and Hacking] paperWastage:
for the intel GPU issue:

looks like the intel driver is getting loaded twice, and eventually gets unloaded, then handed off to VESA (buggy) or fbdev (uses too much CPU)

somewhat similar bug. don't think we can solve it? maybe I'll need to recompile grub2 with the correct modules

https://bugs.freedesktop.org/show_bug.cgi?id=68038

our gpu ->

vendor: 8086 ("Intel Corporation"), device: 0f31 ("ValleyView Gen7"), class: 03 ("Display controller")

probably will go play with android if I can't find a way around these problems right now
[Windows 8 Development and Hacking] paperWastage:
for the wifi driver... still trying to get it working, maybe close?

The wifi module is a Broadcom 4324 (v5?) chip mounted via the SDIO port.

brcmfmac43241b4-sdio.bin

http://git.kernel.org/cgit/linux/ke.../?id=ec24832ca5793c4a20389c29ad5f653bd6a93a84

we need to get this firmware.bin along with nvram to the brcmfmac kernel module... however, I'm still struggling to get the nvram dump (modprobe nvram will give a /dev/nvram that does nothing. nvramtools gives a dump but doesn't seem to work)
[Windows 8 Development and Hacking] paperWastage:
someone managed to get brcmfmac to work (wifi)

that makes since, since ubuntu 13.10 ships with 3.8 kernel, and this page says something that I skipped over before (i didn't use the generic naming convention that <3.13 needs)

http://wireless.kernel.org/en/users/Drivers/brcm80211

I tried his fix (only the file renaming portion, didn't do any blacklist modules), my brcmfmac module detects the wifi card properly and is able to scan and detect my wifi network... but having trouble connecting (WPA2 mode)... after a couple of reboots, disabling "Wireless" and re-enabling "Wireless", can connect to WPA2 network

EDIT2: so the only thing left major is GPU drivers, and sound

Since ubuntu 13.10 uses linux kernel 3.8, and Bay-Trail drivers are integrated only 3.11, I'll try to compile 3.11 for ubuntu, and see if it helps
[Windows 8 Development and Hacking] jesmon:
"you'll need to recompile grub2 with the modules "normal" and "configfile" (will post my files later)"

Thanks for your work on this, I'm impressed. I have been running the livecd but without being able to make changes persistent it feels pointless playing around.

Can you please point me to a guide on how you compiled grub with the required modules?
[Windows 8 Development and Hacking] paperWastage:
http://xdaforums.com/showpost.php?p=46861952&postcount=7

the grub-mkimage step, add the normal and configfile modules there

or use the one attached to this post. my website is down, too lazy to figure out why...
[Windows 8 Development and Hacking] jesmon:
Thanks for that.. I have installed it but I can only get a grub minimal shell.. I can manually boot Ubuntu through the shell. I ran a boot repair which broke my windows boot loader.. I ran refind off a USB and it picked up a windows boot backup so I got windows boot back but I still can only get to grub minimal... I installed grub to mmcblk0p1 which was my efi partition.. Any ideas why it is dumping me to a minimal shell.. Update-grub finds Ubuntu and windows but it isn't reflecting when I boot is my grub install looking in the wrong spot for my config?
[Windows 8 Development and Hacking] paperWastage:
yep... the bootia32.efi (that I built) looks at /boot/grub/ for a grub.cfg....

grub installed in EFI partition had grub.cfg at /EFI/ubuntu/grub.cfg... copy that to /boot/grub in the EFI partition
[Windows 8 Development and Hacking] jesmon:
I'm not sure if I am just showing my inexperience with Linux or not many people are installing Ubuntu on the t100.. You mentioned that you have it running at native resolution.. What's the trick, mine is still 800x400? I am manually adding nomodeset at grub to make it boot.. Should I be adding something else?

Thanks again for your help.
[Windows 8 Development and Hacking] lufasponge:
Has anyone figured out how to get the sound card working in ubuntu?
[Windows 8 Development and Hacking] paperWastage:
on live CDs/USB, it doesn't run native. when I install it and have grub boot properly, it loads up at native. try "video=fbdev nomodeset", and removing the vesa_drv.so from /usr/lib/xorg/modules/driver/

took a quick look this weekend. nothing obvious in the dmesg log. windows device tree doesn't show any useful info like the brcm4xxx SDIO info
[Windows 8 Development and Hacking] lufasponge:
In ubuntu 13.04, the screen was always in the wrong resolution. Ubuntu 13.10 seemed to be native resolution sometimes, but other times it would revert to 800x600. I added "video=fbdev nomodeset --" to the end of grub kernel entry and installed and switched to gnome-session-fallback and it is always in native resolution now.

---------- Post added at 08:06 PM ---------- Previous post was at 07:57 PM ----------

I have not had any luck with the sound card so far at all. Good point about windows info, I'll list it for others to see and so I don't have to reboot to see it.

Windows lists it as Intel SST Audio Device (WDM).

The hardware IDs are as follows:

ACPI\VEN_8086&DEV_0F28&SUBSYS_80867270

ACPI\80860F28

*80860F28

I've had to trouble shoot wireless cards probably 5 or 6 times in linux, but never had an issue with sound, so I don't really know where to start. Anyone have any ideas?
[Windows 8 Development and Hacking] lufasponge:
I read that kernel 3.11 is going to have support for sound on baytrail, but I already have it installed. So, I installed 3.12 per the instructions at http://ubuntuhandbook.org/index.php/2013/11/linux-kernel-3-12-released-install-ubuntu-or-linux-mint/

I rebooted and the sound card is still not found. I just wanted to let everyone know that I tried it with no success. I'm open to suggestions.
[Windows 8 Development and Hacking] jesmon:
In my endeavours to get the native resolution I too had installed the 3.12 kernel.. I was secretly hoping that by some miracle, sound and the rest of the missing drivers would be included but alas still 800x600 even with the grub options you said above.. I have obviously done something wrong.. I will keep enduring with it.

I also tried to use the windows driver for sound with ndiswrapper (I realise it is meant for network drivers but I gave it a shot) a few problems.. The windows driver is 32bit so would unlikely work on 64bit linux and it doesn't use .inf only .sys .. I found a .inf for Intel SST on the net but ndis didn't like it.
[Windows 8 Development and Hacking] jesmon:
I decided to try and compile Android IA from source to hopefully include 32bit UEFI support.

I set the TARGET_KERNEL_ARCH to x86_64 because from what I read that would include 32bit EFI..

it created bootx64.efi, gummiboot.efi, LockDown.efi, MokManager.efi and shim.efi

From external/efitools/Android.mk:

# TODO: support ia32 prebuilt

ifeq ($(TARGET_KERNEL_ARCH),x86_64)

arch_name := x86_64

I am recompiling with the TARGET_KERNEL_ARCH set to i386 and will see what it spits out for me.

any suggestions if that fails? (speak slowly, I am new to this)..

side note: the documentation says it should produce installer.img but I didn't get that, I did get live.img though... I am guessing the documentation is out of date..
[Windows 8 Development and Hacking] jesmon:
The good news is that TARGET KERNEL ARCH i386 did produce a bootia32.efi,, bad news is it won't boot, selecting it from the uefi does nothing, tried to boot it from Refind and.. not sure what I am missing..?

I am happy to upload the live.img (200mb) or just the bootia32.efi if someone else wants to have a go at it (not sure where to upload it?)

or recompile with different settings and try..

I used the core-mesa-userdebug and amended the TARGET_KERNEL_ARCH as above and the TARGET_ARCH_VARIANT is currently set as x86-atom

EDIT: recompiled and bootia32.efi is now recognised. Because I compiled a x86 variant, when it booted it told me only 64bit images are supported then dumped me back to the UEFI.

I then downloaded the prebuilt Androidia image and added my bootia32.efi, it loads to a black screen with cursor (doesn't blink) and doesn't do anything after that...

Next step is compile my own 64bit version.