yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Kingzak34:
Do you think desktop armhf version can also work with our TF ? I tried almost every mountloop kernel but if failed, and it failed with an old working ( it should ) img so I dont know
[Eee Pad Transformer Android Development] jrohwer:
I'm running 12.04 armhf on my TF101G using the 3.1.10 kernel (compiled myself from Jhinta's source tree). I also compiled the kernel with the arm-linux-gnueabihf- toolchain. This is mountloop and the ubuntu image lives on /data/media on my TF. Happy to share kernel and modules if interested.
[Eee Pad Transformer Android Development] Kingzak34:
Yes of course ! It will be great

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] jrohwer:
Here you go. Install Ubuntu-3.1.10-7.hf.zip via CWM or TWRP recovery. This just installs the Linux kernel. This assumes that your Ubuntu image is located at

under Android. Rename and/or move accordingly. Alternatively you can blobunpack the boot image from the blob in the zip, then unpack the boot image, change the command line to your liking and repack.

The modules tar.gz should be extracted into /lib/modules of your Ubuntu image. This can be done by loop-mounting the image e.g. under Android or on your Linux desktop.

After first boot run

and reboot, so your modules will be loaded at boot (otherwise wifi won't work).
[Eee Pad Transformer Android Development] interw:
It would be great if you could also share the 3.1.10 kernel you compiled from Jhinta's source tree for 12.04 armhf. Thanks.
[Eee Pad Transformer Android Development] jrohwer:
See previous post :)
[Eee Pad Transformer Android Development] Kingzak34:
Thanks a lot, I'll try that ASAP :)
[Eee Pad Transformer Android Development] jrohwer:
Forgot to mention that this ZIP will install the Linux kernel to the LNX partition (i.e. normal boot). If you want to boot back to Android you'll have to reflash the Android kernel from within recovery. Some people prefer a setup where the Linux kernel is booted from the recovery partition, leaving the normal boot partition for the Android kernel. But that means that you lose recovery (your "recovery" boot then becomes ubuntu). The latter setup is also possible, you'll have to blobunpack my kernelblob, and just blobpack it again to the SOS (recovery) partition. Just be aware that you lose CWM or TWRP (whatever your recovery is) in that case.

With nvflash it is no problem, but I have a TF101G for which nvflash/wheelie is NOT available so you've got to make triple sure what you're doing, as there is no "unbricking tool".
[Eee Pad Transformer Android Development] Kingzak34:
Yup, I understood ;) That's exactly what I was looking for ! Dualboot is good but take too much space for me, and no recovery is a bit hard, so have a mountloop is easier :)
[Eee Pad Transformer Android Development] interw:
Would like to use your kernel as described above rather than the mount-loop method. Being a relative newbie, find it hard to work out the blobunpack and blobpack to the recovery partition described above. It would be great if the kernel were available in the standard linux.img format with the supplement modules for flashing with tubuntu installer.
[Eee Pad Transformer Android Development] Kingzak34:
You have kernels in OP
[Eee Pad Transformer Android Development] interw:
Thanks. Would like to try jrohwer's kernel if possible. Have an SKBv1 device and have difficulties with kernels in the OP, except Jhinta kernel, hence the interest.
[Eee Pad Transformer Android Development] DjDill:
How does this kernel go with Docking and undocking the dock? and USB hotplug? - Also how stable it it?

Thanks for Sharing!
[Eee Pad Transformer Android Development] jrohwer:
Here it is as a standard Android boot image. Rename to linux.img or whatever you need to for the Tubuntu installer. I haven't used the Tubuntu installer myself and don't know how it works as I can't use nvflash on my device (TF101G)!

Note: This boot image is still set up for mountloop. If you want to set it up that it loads from a dedicated partition on your device, you'll have to unpack the boot image, change the cmdline, and re-pack the boot image. No change to the kernel or initrd itself should be needed. If you don't know what I'm talking about you probably shouldn't be messing with this....
[Eee Pad Transformer Android Development] jrohwer:
Undocking and re-docking is fine. I haven't set up the on-screen keyboard as I don't use it and almost always run Ubuntu with my tablet on the dock.

USB hotplug does not work, this is a known bug of Jhinta kernel. Either have the device plugged in from boot, and it works. OR (and this is what I use) plug in your device, run "sudo lsusb -v" from a console, and the device is recognised. So it is a little inconvenience, but at least I can plug in and use USB devices while it is booted up.

It is very stable and I have not had any issues. Overclock is compiled in to 1.6GHz, but I run mine at 1.5GHz max (manage with cpufreq-utils, which you can install from Ubuntu repos). I have had no stability issues at all and use this kernel daily.
[Eee Pad Transformer Android Development] Kingzak34:
I'm now testing your mountloop kernel with 13.04 armhf desktop version :)

Will be back shortly !

Yup, 13.04 desktop img doesnt seem to boot, I'll try my old 12.04 img
[Eee Pad Transformer Android Development] Kingzak34:
Does anyone know if any of them here should work ? http://cdimage.ubuntu.com/releases/13.04/release/
[Eee Pad Transformer Android Development] jrohwer:
And did it work with the old 12.04 image?

---------- Post added at 05:30 PM ---------- Previous post was at 05:21 PM ----------

The boot images will definitely *NOT* work. It may be that the file system images will work, as they are generic armhf Ubuntu file system images. You'll have to get the TF101 boot images/kernel however. To get the (accelerated) graphics going, you'll have to install the Linux4Tegra drivers:

https://developer.nvidia.com/linux-tegra

The TF101 has a Tegra2 (ventana) board.

I originally got my armhf image from this thread:

http://xdaforums.com/showthread.php?t=1852702

It looks like development has stopped on that thread, but it was a nice place to get the file system image. I've also *NOT* used that installer but did things by hand because I like to know what I'm doing (running Linux on my desktop as well). So I just grabbed the file system image (I think it has L4T drivers installed).

Another option is to use "debootstrap" on a running Ubuntu desktop as in this thread:

http://xdaforums.com/showthread.php?t=1476835

(should work equally well for Ubuntu as for debian). But then you'll have to copy over the firmware and bluetooth config files by hand. See also the Ubuntu TF wiki:

http://xdaforums.com/wiki/How_to_install_Ubuntu_on_an_Asus_EEEPad_Transformer

HTH. I have not tried upgrading my 12.04 image to 12.10 or 13.04, basically because things are working and I am happy with it. Nice thing about a mountloop disk image is that you can copy it as a backup and when the upgrade screws up you can just go back to what you had. :o
[Eee Pad Transformer Android Development] Kingzak34:
I was talking about system img, but it doesnt seems to want to boot.
[Eee Pad Transformer Android Development] Kingzak34:
Hey jrohwer, with your kernel I allways boot in text mod, is it normal ?

Anyway, I tried to blobunpack your kernel, and I only got a kernelblob.LNX and that's all, I should have more files huh ? ( First time I unpack a blob )

Thanks in advance man !

EDIT : Got it, that's good ! ;)

EDIT 2 : Yuuuueaaaaah, Got 12.04 Unity 2D working perfeclty with sound bluetooth and all ! :)

Thanks to you jrohwer for your kernel ! ( The one you gave boots text mod, if someone wants GUI mod let know )

BTW, does anyone have news from x3maniac ?
[Eee Pad Transformer Android Development] TomTcom:
X3's been busy with work and home. I don't think he's had a lot of time to do more.

The kernel source he has for 3.1 isn't working well.
[Eee Pad Transformer Android Development] jrohwer:
Glad it's working :laugh:

After blobunpacking you are supposed to only get one file. This is the Android boot image and contains the kernel zImage as well as the ramdisk (initrd.img). If you want to extract the kernel and ramdisk you'll have to use something like abootimg.

I'm aware of the text mode boot. I had to change it because I could not get graphics mode boot to work on my TF. What you can do is extract kernelblob.LNX with abootimg, this will give you the zImage and ramdisk plus a cfg file with parameters. In there is cmdline. At the end you will see "ro quiet text", change this to "ro quiet splash" and re-pack the boot image with abootimg. Then you should have graphical boot.

This will not actually give you the Ubuntu boot animation, it will just start the graphical login manager. There is no space in the boot partition to have the full graphical Ubuntu boot animation. For that you'll have to re-partition your NAND with nvflash as lilstevie has done with his OLiFE script. But I can't do that because I can't use nvflash on my TF101G.
[Eee Pad Transformer Android Development] Kingzak34:
Yup thats what I done ( I used ro quiet gui ) :) I'm glad to see how this kernel is stable never had a freez and all is working.

Does anyone know if its necessary to update nvidia L4T package if I applied last 16.3 binaries ( in synaptic its v15 package installed but I updated binaries to 16.3)

BTW I'm now trying to update and upgrade to 12.10 and then 13.04

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] jrohwer:
:good::laugh:

No, the synaptic package is outdated, so if you update binaries to 16.3 from L4T then that should be enough

Let me know if this works and if it is any better than 12.04!!!
[Eee Pad Transformer Android Development] Kingzak34:
Yep, I will ;)

A last question, if I update and upgrade, do I need to apply Nvidia binaries again ? I mean, xabi should change when upgrade, so ... ?

( BWT How to check current xabi version ? I know that 12.04 is 11, but dont know for others )
[Eee Pad Transformer Android Development] Kingzak34:
Aaaaaaand it doesnt boot anymore It asked me to do a partial upgrade in order to apply updates, downloaded about 1500 packages and here's the result. ( Fiuu, I have backup )

It stucks on this :

http://cjoint.com/13mi/CEiopJY5q5Y_sans_titre.png
[Eee Pad Transformer Android Development] transformador:
Hey guys, i have a raring image (and 12.04 and arch), can someone point me at how to install tegra drivers from the binarys? (Cant install it like in 12.10)
[Eee Pad Transformer Android Development] Kingzak34:
Donwload ventana driver, extract it and go to the folder in terminal then :

sudo ./apply_binaries.sh -r / --xabi 11

for 12.04
[Eee Pad Transformer Android Development] jrohwer:
Yes the abi changes so you have to re apply Nvidia binaries again with the correct abi version.

Run "sudo apt-cache show xserver-xorg-core |grep abi" and see string xorg-video-abi-xx (xx is your abi).

---------- Post added at 02:44 PM ---------- Previous post was at 02:41 PM ----------

Sorry can't help you there - I get similar messages when my kernel boots but it does complete. But a partial update is problematic. Do you have enough disk space for your 1500 downloaded packages? How do you upgrade? On the gui or on the command line? I have had best experiences with running "sudo do-release-upgrade" on the command line.

---------- Post added at 02:46 PM ---------- Previous post was at 02:44 PM ----------

See above for getting the correct xabi version.
[Eee Pad Transformer Android Development] x3maniac:
since thanks giving is coming up will be very busy with family gatherings. so i hope to release a preview version within the next few hours to keep you guys happy. comes with new kernel 1.2ghz OC and cleaned up a lot of complains with boot. does boot within 5 -7 seconds now. even tho i noticed a few more complains, it's prob due to the new kernel i have. i'll post up a change log once i type it out :D

edit

got the new version up. remember to flash with my kernel when done uploading rootfs to take advantage of overclocking. i dropped it back down to 1.2ghz.. it's more stable without having to OV(over volt).

my ultimate goal for the speed will be 2.0ghz. i ran my android with 2.0ghz so i know it's possible.

going to try to compile 3.1.10 kernels for future releases. 2.6 don't support nvidia tegra that well. 3.1 is eaiser to grab codes from nvidia.com

due to the holidays. my next release will be a bit later. hopefully sooner better then later
[Eee Pad Transformer Android Development] i9apps:
Thank you, but i will wait for now because i saw chrome still broken...

I don't know a lot about Linux and i didn't understand the workaround or how to install Firefox if i have no browser LOL
[Eee Pad Transformer Android Development] djlenoir:
Enjoy your Thanksgiving and time with your family. I will give the new release a spin but will also be busy with family. I will provide feedback when I can. I will probably be busy on "Black Friday" too shopping for stuff I probably do not need because I get such a good deal. :)
[Eee Pad Transformer Android Development] x3maniac:
would you like me to build a version in the future with more programs pre-installed? like office and gimp(GNU Image Manipulation Program)? wont be anytime soon but. i can if you want a full feature linux
[Eee Pad Transformer Android Development] lahegry:
That would be freaking awesome!!!!!!!
[Eee Pad Transformer Android Development] LoneGrenade:
Lubuntu was running pretty smoothly on my device. However, when I booted into Linux, it resized my root partition and made android unbootable. I was able to boot into android twice, once with the initial flash, then a cold boot. After I booted into Linux, I was only able to boot into Linux. I'm not as sharp when it comes to the boot process, but could it have resized the Linux partition and corrupted the android partition or changed a boot flag or something?
[Eee Pad Transformer Android Development] x3maniac:
what was the command you issued to resize the partition?

i use

resize2fs `mount -l | grep " / " | awk '{print $1}'`

if you made ubuntu on recovery partition. usually it should be /dev/mmcblk0p8

ultimately the code is

resize2fs /dev/mmcblk0p8
[Eee Pad Transformer Android Development] i9apps:
Hi x3maniac,

can u maybe make a little guide how to install Firefox?

I have no idea how to do it without a browser or a application store...

Thank you!
[Eee Pad Transformer Android Development] st0nedpenguin:
I'd imagine apt-get install firefox should work.
[Eee Pad Transformer Android Development] x3maniac:
Open the lxterminal locales in applications.

Type

sudo apt-get install firefox -y

That should do it

Wait until everything get processed then u will see the application in the menu/internet/firefox
[Eee Pad Transformer Android Development] Konfuddle:
So, just for clarification: After Ubuntu is installed and working, we can flash a newer rom over Prime? Let's say RaymanFX's CM10 or ARHD 3.6?

Anyways, thanks for you hard work. I've been waiting a while for an SBK2 Ubuntu.

Enjoy your thanksgiving!
[Eee Pad Transformer Android Development] djlenoir:
Yes, you can flash another ROM after you have Ubuntu running. Keep in mind that to run Lubuntu, the recovery partition (Where CWM or TWRP is loaded) is replaced with a Linux bootloader. So, you have to connect the Transformer back to your PC, run the Tubuntu again and flash TWRP into the recovery partition, then load up the ROM of your choice like you normally would, and finally run Tubuntu again to flash the linux bootloader over TWRP so you can dual boot again.
[Eee Pad Transformer Android Development] x3maniac:
just a little quick update:

since i had a day off for thanksgiving i ended up staying up till 3:30am playing with the 3.1.10 kernel. and i got it load and nvidia tegra drivers to load, yes google chrome works and flash does to. also i overclocked it 1.2ghz for testing. will up going up soon. also got zram working and cifs. screen dimming work, and changed the governer to performance.don't know how to get the sound working yet. still trying to get that working. umm debating if i should install conky with a global config?
[Eee Pad Transformer Android Development] i9apps:
WOW!! Awesome dude!

Cant wait :) there is anyway to add more languages? like Hebrew?

BTW, If you've done OC, why not higher like 1.54GHz?
[Eee Pad Transformer Android Development] djlenoir:
Wow, I am impressed. You have made significant progress. Conky would be cool, but it is just a system monitoring program right? I would recommend spending your time on the remaining issues, like audio or whatever, before investing time in conky. However, I know that it is also fun to learn and getting conky to work might just be worth if for the challenge alone. :)

In any case, I look forward to your next release on the 3.1.10 kernel. I bet with that kernel, zram and overclock (which is a safe and reasonable overclock) that Lubuntu screams.
[Eee Pad Transformer Android Development] x3maniac:
well my goal is 2.0ghz... im' currently running 3.1.10 at 1.504ghz but not stable. graphics crashes. don't know if it's the drivers not liking the overclock. it's slightly different the running android when overclocking a OS.

as far as languages look at http://lubuntu.net/. i am using there IMG so you should be able to install new languages following there guides

edit:

https://help.ubuntu.com/community/Lubuntu/Documentation/LanguageSupport i have not tried this. but should work. let me know =).
[Eee Pad Transformer Android Development] DerSandmann:
Hi x3maniac!

Just want to thank you for the great job you're doing here! Having a SBKV1, before I was glad to have the good model. Now I'm a bit jealous of the

updated

windows

tool that you are making. Any chances to make it work whith SBKV1? I know your answer will be "You have OLife and Frank's tools it's the same!" But the half of the links are dead.

All the best, Sandmann.
[Eee Pad Transformer Android Development] x3maniac:
I can release one but I can't test it. Since I have the source codes from franks tool its almost the same. Let me know if want to be a beta tester I can do it. I just don't want to release a code I cant test and get blamed for stuff. :(
[Eee Pad Transformer Android Development] x3maniac:
[Q] after i get a stable version out. should i make a new thread for a HOW TO on the lubuntu installation? or should i make it on the 1st post? or i shouldn't even bother =)
[Eee Pad Transformer Android Development] lahegry:
If I was you, I would just update the first post with the how to.
[Eee Pad Transformer Android Development] Kingzak34:
I updated by GUI, it said that it needs to do partial upgrade, then yes and lets go !

My IMG is 5GB so I think there is enough space ( almost everything went Ok when upgrading never said there is no enough space )

I'll try another time by terminal. But I first tried to apply updates and not to upgrade to 12.10

If you have suggestion, I'll glad to hear it before I relaunch it
[Eee Pad Transformer Android Development] jrohwer:
OK you should always first install updates before upgrading to a new version. I wouldn't try to do both at once.

sudo apt-get update (updates your sources)

sudo apt-get upgrade (installs the updates)

I have been updating my image all the time, this has never caused it not to boot (but of course it's still 12.04, only with security and bugfixes).
[Eee Pad Transformer Android Development] Kingzak34:
Yes, but it's the update process that needed to do a partial upgrade then crashed :P

Anyway, I'll give another try by terminal

EDIT when rebooting old img, I saw that the thing that should take time when I though it was stuck was maybe fsck cause it does a check just when it was stuck, that was maybe that.

Let's see

Sooooo, updates went fine then reboot then do release upgrade gave me a fatal error and don't want to start and now I've 971 updates.

So I ran apt-get upgrade once again and let's see

Last edit : screen goes off during install process ( I don't know why I just touched it to avoid sleep a ) and didn't want to go On so reboot and stuck at same place. I'll give another try

LAST LAST edit : After a succesfull upgrade, doesnt boot, same problem, so I'll stuck with 12.04 for now.
[Eee Pad Transformer Android Development] onmail:
13.04 and 3.1

I have tried couple of 3.1 kernels with raring (even compiled from sources) and I was not able to succesfully boot. I have checked some logs and there seems to be a problem with mounting /run. I have tried to compile the kernel with different configs but still no luck..
[Eee Pad Transformer Android Development] jrohwer:
Thanks for all your testing. I'll see if I can come up with something on my side if I have some time.
[Eee Pad Transformer Android Development] Kingzak34:
Yep, I think this kernel doesnt like Ubuntu >12.04 cause all img I tried in 13.04 and 12.10 didnt boot, almost same problem that stuck at same time.

I didnt try x3maniac lubuntu, I will if I got some times.
[Eee Pad Transformer Android Development] jrohwer:
OK I decided to create a new Raring disk image from scratch using debootstrap. I then injected the firmware, etc. and tried to boot with my kernel. No luck :( Hangs after the first 8 lines or so after the penguin logo.

At first I thought it might have been the initrd. So I mounted the raring disk image on my desktop, chrooted into it and made a new initrd using Ubuntu's mkinitramfs. However, no luck either, hangs at the same spot :confused:

In case anyone wants to test (although it didn't work for me) I attach the boot image with the new initrd; remember this is for mountloop with the image living on /data/media/ubuntu.hf.img under Android. If you want a different setup you must unpack the boot image e.g. with abootimg and change the cmdline.
[Eee Pad Transformer Android Development] Kingzak34:
That's what I had even with official IMG

So I don't know

But that's sad cause your kernel is very good

I hope you'll find what's wrong

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] jrohwer:
OK I can't get raring to boot :mad: Tried different 3.1.10 kernels, also from my older ones which I compiled while jhinta was still actively developing his kernel. I managed to recover the kernel boot logs, and attach both (precise, which boots successfully, and raring, which just hangs). The logs look very similar to me and I can't find anything which indicates what the problem might be. The root filesystem /dev/loop0 seems to mount successfully in both cases.

I'm afraid I don't know how to debug this further :(

I don't have any C programming skills and can't debug kernel source (although I'm perfectly happy compiling kernels).

Anyone wanting to take this further - most welcome and I'd be happy to help testing!!!!
[Eee Pad Transformer Android Development] Kingzak34:
We must test on a real dualboot method maybe, without mountloop, but I dont have time ti repartitionate my tab again

---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------

There is only these lines that are different

May 10 13:29:52 jr-tf101 kernel: [ 4.434391] fm34 0-0060: Performing initialization
May 10 13:29:52 jr-tf101 kernel: [ 4.593342] tegra-i2c tegra-i2c.0: I2c error status 0x00000008
May 10 13:29:52 jr-tf101 kernel: [ 4.593366] tegra-i2c tegra-i2c.0: no acknowledge from address 0x60
May 10 13:29:52 jr-tf101 kernel: [ 4.593386] tegra-i2c tegra-i2c.0: Packet status 0x00010009
May 10 13:29:52 jr-tf101 kernel: [ 4.593566] fm34 0-0060: Failed to access device

No error on precise log, but I'm not able to do something too..

And I evend dont know what fm34 is

EDIT: It's the sound driver or something like this
[Eee Pad Transformer Android Development] jrohwer:
Unfortunately I can't help you with that because I can't run real dualboot. Have a TF101G and therefore nvflash/wheelie is NOT available, so I can't repartition my tab.... :(