yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] TomTcom:
Which toolchain do you use to compile jhinta's kernel with?

---------- Post added at 07:32 PM ---------- Previous post was at 06:35 PM ----------

Replying to myself....I'm dumb. I got gcc 4.7 installed and for anyone else who may stumble across this, use the dpkg to find the darn executable, path I have, and the export command:

dpkg -L gcc-arm-linux-gnueabi

/usr/bin/arm-linux-gnueabi-gcc

export CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

making zImage underway now on Jhinta 3.1. I'll see what happens. I have a Raring image from 4/23 and I have already done an update and upgrade. I haven't yet done a dist-upgrade so we'll see out of curiosity if it boots.

---------- Post added at 07:48 PM ---------- Previous post was at 07:32 PM ----------

Replying again. Fail. Got unable to create /dev/kmesg on boot. But it started to boot..lol..I think there was another error or two in there. I'll look again later.
[Eee Pad Transformer Android Development] Boss_Cuco:
Sorry but I'm stuck in the Linux boot screen...

I cant get past this:

http://s3.postimg.org/9tk0kz1nn/WP_002806.jpg

I'm on a SBK2, followed all the instructions and don't know what else to do.

Already checked the MD5, tried booting with/without dock/MicroSD, updated to v4.7 Tubuntu installer...

Thanks
[Eee Pad Transformer Android Development] onmail:
Your Ubuntu version and kernel version?
[Eee Pad Transformer Android Development] Boss_Cuco:
I did everything according to Kingzak34 guide.

Lubuntu v1.2 (12.10) and 2.6.36 kernel.

I've reinstalled over and over again and always get stuck...

After a lot of reboots I'm stuck in a bootloop to this Linux screen and can't even boot android...

I'm really running out of options here :(
[Eee Pad Transformer Android Development] Kingzak34:
You sure you're SBKV2 ? And what bootloop do you have ?

DO you have any error with Tubuntu ?

And if you cant boot android, you did something wrong.

BE sure you followed ALL Steps of my guide
[Eee Pad Transformer Android Development] Boss_Cuco:
I'm B80 so I assume I'm SBK2.

And no, Tububtu does not give any error, always says linux image file sent successfully...

I've done it 3 or 4 times now and I followed every single step in your tutorial.

I could boot android at first but now, after 4 or 5 "long press power button" to restart it just boots back to this screen. I don't even need to press "vol down and then up"...

Do I need to full wipe before Tubuntu or something else?

I'm coming from an EOS4 rom...
[Eee Pad Transformer Android Development] Kingzak34:
Nope Tubuntu should format everything.

If you cant boot Android or Linux, I really dont know.

Be sure img you downloaded are complete and not corrupted. ( Prime img AND ubuntu img )
[Eee Pad Transformer Android Development] Boss_Cuco:
I could boot android, It's just that it stopped booting it and now goes straight to Linux...

I've checked the MD5, is there any other way to do it?

Thanks for your help... I hope I can figure this out :(
[Eee Pad Transformer Android Development] Kingzak34:
DId you let boot android fully and seted it up before going back to ubuntu ?

Did you use Reboot To Recovery in Android ?
[Eee Pad Transformer Android Development] onmail:
try to flash different kernel (I would go for the "stock" from the first page) and if it does not help, try different lubuntu image or try to build your own.
[Eee Pad Transformer Android Development] Boss_Cuco:
Yes, after Tubuntu stopped and Prime was standingby I configured it. I didn't do much, just until it showed the homescreen.

And I always booted to Linux with the voldown + up combo...

I think I'm already using that kernel, it's the same from the tutorial

:(
[Eee Pad Transformer Android Development] Kingzak34:
You can ever try another kernel, but I really dont know what's wrong

If nothing works, you should use mountloop method

---------- Post added at 04:00 PM ---------- Previous post was at 03:33 PM ----------

Tell me anyone, how am I supposed to proceed to use this kernel img in a blob file for mountloop purpose ? I dont know what I need to do ?

( I know how to use abootimg and blobpack/unpack )
[Eee Pad Transformer Android Development] jrohwer:
This should be relatively easy to fix. The initrd on the novaspirit github has a problem as it does not have a /run directory so your kernel can't mount the filesystem on /run. Either you can unpack the boot image with abootimg, then extract the initrd, add the /run folder to the initrd, repack the initrd and repack the boot image with abootimg. If you don't know how to do this you can also try the boot image that I posted earlier in this thread.

---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------

Let us know how this goes :)

---------- Post added at 04:26 PM ---------- Previous post was at 04:23 PM ----------

I used the arm-linux-gnueabihf- toolchain from Ubuntu. However I got compile errors with gcc-4.6 so I used gcc-4.4 (it is in the repos) and compiled successfully. I don't have gcc-4.7 because Im still running Ubuntu 12.04 on my desktop. Did you add the -wnoerror compile flag? Cause mine was failing with gcc-4.6 with some Warnings.

---------- Post added at 04:36 PM ---------- Previous post was at 04:26 PM ----------

The boot loop is actually a boot loop into recovery (as you are loading the ubuntu kernel from the recovery slot). This is a known issue and can be fixed with the following command (either from a terminal or using adb), this clears the MISC partition:

dd if=/dev/zero of=/dev/block/mmcblk0p3

---------- Post added at 04:43 PM ---------- Previous post was at 04:36 PM ----------

You have to edit the command line. It is in the cfg file you get when you unpack the boot image with abootimg. In the command line, change

"root=/dev/mmcblk0p8" (or whatever it was, maybe /dev/mmcblk1p2)

to the following

"root=/dev/mmcblk0p7 loop=/media/ubuntu.img"

This assumes that the ubuntu image is named ubuntu.img and is located in the /sdcard (/data/media) folder under Android. If your folder and/or filename are different, change accordingly. Repack your boot image with abootimg using the modified cfg file, then pack the image to a blob on the LNX partition and you are good to go :)
[Eee Pad Transformer Android Development] Kingzak34:
So I use kernel img as kernelblob.LNX and repack ?

That's what I dont know :)
[Eee Pad Transformer Android Development] TomTcom:
I didn't use that flag. I did compile successfully with gcc 4.7 but my my modules may be out of place, the initrd also has some issues.

I edited the initrd configuration file to use xz compression because the web said 4.7 and 3.1 kernels needed xz compression but it didn't solve the errors. I'll play more later. I'm close to compiling the nvidia source for 16.3 but we'll see how that goes.
[Eee Pad Transformer Android Development] Boss_Cuco:
Thanks for the reply!

I'm not sure about abootimg, can I do it under Windows8 x64?

About the image you were talking, is it this one: http://xdaforums.com/showpost.php?p=41135090&postcount=965

However, you say that it is only for mountloop...

And how is it possible that this only happens to me, if the initrd on the novaspirit github has a problem?
[Eee Pad Transformer Android Development] onmail:
Sorry, have not tried yet but what about this page http://xdaforums.com/showthread.php?p=24399119 I think you already have the kernel.img so it should be no problem...
[Eee Pad Transformer Android Development] themac:
Ok, ok, thanks for the nice reply. I was late cause i had big problems installing twrm recovery on the really hard-time-maker, windows 8 ;)

I was certain about owning an sbk V2 TF101 (it's a B80 one). But indeed it's a SBK V1, so less problems i think. Now recovery is ok.

I was starting with tubuntu flashing , but now i have some question.

1) Can i just use system.img and ubuntu.img and flash it with the fourth option of TUbuntu, (Ubuntu Only ? ) or is the dual boot mandatory to avoid problems ?

If 'd need to come back to Android i will then have to select the third option (Android Only ) . Right?

2) I know you wrote you can't help, but i simply need a linux flavor that allows me to see (and hear) some videos (720p ?) and working on libreoffice.

The less resource demanding will be the chosen one. Any advice ?

Thanks, again :)
[Eee Pad Transformer Android Development] Kingzak34:
Soooo, in fact, SBKV1 devices got some troubles when booting some times, ( kernel panic ). Be sure to have all important data of your TF backed up on your PC btw.

1) If you choose Ubuntu only, you of course, will have only ubuntu and will not able to have android without wiping everything.

But you can choose ubuntu only. Be aware that Lubuntu is great, really, but can have some problems.

Of course if you want to have your tablet as stock with Android Only you should use Android only option.

2) You can have sound working, if you want look 720p vid it's another thing, cause you need 3.1 kernel and Tegra driver, BUT there is no known stable 3.1 kernel except the jrohwer one but you need to edit cmdline ( unblob it, un pack bootimg etc etc ) And even if you have 3.1 kernel I'm note sure that

720p works. ( No flashplayer too )

After having said that, libreoffice works well and you can print document too. I think it's more reliable to have both Android and Ubuntu.

Know that you will need your PC to have a recovery

Noooow I said this, if you want an easy install / remove just for testing before format your tab and erase your data, you can use mountloop method ( You have recovery and you can remove Ubuntu in 2 clicks )
[Eee Pad Transformer Android Development] jrohwer:
Yes just be sure it's the android boot image ( kernel plus ramdisk) not the kernel only. The syntax is

"blobpack blobname partition bootimg"

e.g.

"blobpack myblob LNX boot.img"

To pack the boot.img to the LNX partition in the blob.
[Eee Pad Transformer Android Development] Kingzak34:
So do you know if kernel.img provided here http://xdaforums.com/showpost.php?p=42048220&postcount=1049 contain needed files ?

I dont know how to check into it ..

( Anyway thank you for your answers )
[Eee Pad Transformer Android Development] jrohwer:
Not sure abootimg is available for Windows. I use Linux. The image is the correct one. If you can get abootimg going then you can unpack it, change the cmdline to point to the correct partition and then repack with abootimg. Then it can work with other setup also.

Re the initrd. The older kernels used /var/run and the newer ones use /run. Maybe this initrd was based on the 2.6.36 kernel so it would work there but not on 3.1.10?
[Eee Pad Transformer Android Development] Kingzak34:
I'll see the img extension made me a bit confused but it's just as simple.

Anyway I'll made changes on cmdline and let you know what's going on ;)
[Eee Pad Transformer Android Development] jrohwer:
I still need to test it. The boot image is too big and can't be used without repartitioning, which I can't do because I have TF101G:( Max size is 8 Mb. I want to test the kernel but need to remove the modules from the initrd to make it smaller. You don't need all the modules in the initrd, they can be in the rootfs. Have no time now but will let you know...
[Eee Pad Transformer Android Development] Boss_Cuco:
But does anyone have a boot.img that can be uploaded?

I would apreciate it since I can not edit so easily the boot.img myself...

Thank you :(
[Eee Pad Transformer Android Development] onmail:
abootimg -x kernel.img, this will extract the zImage and initrd. rename initrd.img to initrd.gz and ungzip. remove the modules and repack. and btw. if you want to see or use to compile your own kernel) the config file the kernel was compiled with, go to the folder your kernel source is in, then in folder scripts there is "extract-ikconfig". you can use this to extract the config if it exists in the kernel. extract-ikconfig path_to_zImage >> .config
[Eee Pad Transformer Android Development] Kingzak34:
Thanks for answers onmail and jrohwer I'll do some test tomorrow with an upgrade to 12.10 and then 13.04 and let you know.

---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------

DId you try another kernel provided on 1st post ? ( Replace one of file in images folder and flash the good one ) ( Look at the guide it's all explained )
[Eee Pad Transformer Android Development] Boss_Cuco:
Trust me, I've looked at the guide a hundred times...

But jrohwer says that there is a fold missing! A problem with the novaspirit github...

I give up... I don't know what to do.

Already installed cygwin to unpack the boot image but I don't even know where to search for it let alone edit the initrd...

Maybe, if boot image isn't really working, there should be something on the tutorial saying that this method is not currently working.

:(
[Eee Pad Transformer Android Development] Kingzak34:
This method works I didnt make a guide that doesnt work man... Just try another kernel and if it doesnt work try mountloop version

And kernel provided on op are working, and kernel present on goo too

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] Boss_Cuco:
I'm not saying it doesn't! But if there is a problem with github right now it's not your guide's fault.

Maybe I'll try the mountloop but I was really looking forward to the Dual-Boot.

Thanks for your help anyway! I'm sure many others have enjoyed ubuntu with your help ;)
[Eee Pad Transformer Android Development] Kingzak34:
Github doesn't have anything to do here, kernels have been compiled long time ago and proven working. Github problem is if you want to compile kernel yourself

By the way mountloop is still dual boot you just need to go to recovery to switch between os

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] Boss_Cuco:
Ok, I believe you. Its just my transformer then.

Unless I'm making a stupid mistake (about ten times now...I've lost count of how many times I've flashed it) I don't see any other reason for it not to work.
[Eee Pad Transformer Android Development] Kingzak34:
So, did you try another kernel ?

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] Boss_Cuco:
I didn't because of this:

I'm not sure of how to install the kernel supplements and your guide seemed pretty straightforward with the stable kernel.

(By the way, what drive are we talking about? transformer's?)

Tomorrow I'll see if I go for mountloop or back to EOS4.

Thanks again for your help!
[Eee Pad Transformer Android Development] onmail:
I would recommend you to flash the asus stock firmware (EasyFlasher should do) and then try the Tubuntu flashing to DualBoot again. I have tried it with this guide on 2 SBK2s (couple of times) and no problem. If you have a linux machine, there is another option - collection of scripts (OLiFE) which I use now. But I would definitely recommend the Tubuntu way for the first time (with LUbuntu image and stock kernel 2.6 from the first page).
[Eee Pad Transformer Android Development] Boss_Cuco:
Yes, I've tried it but I get the same error... And I'm on W8.
[Eee Pad Transformer Android Development] onmail:
Hm, sorry, I do not know if it could be win8 problem but I don't think so. But to know it for sure - any chance for you to try on XP? Or you could try with some linux livecd and the OLiFE script...
[Eee Pad Transformer Android Development] Boss_Cuco:
Thank you!!

It booted into Linux! But only when I connected the dock. It gave a few errors when booting I think... and I did not install the kernel complements (only the updated kernel).

I saw the screen and pressed login but now I'm stuck... I just see the wallpaper and the mouse (can't move it...)

Ideas please? :p
[Eee Pad Transformer Android Development] onmail:
Restarting again to linux does not help? If not, the classic answer - try different kernel :) I am not sure if the one I have uploaded will work for you but I have succesfully (more or less) tried it with ubuntu 11.10, 13.04 and even with 13.10. Without dock connected (I have used just the usb keyboard connected to the asus connector to usb converter) I am at least able to login to xsession (gnome or xfce). So you can try...
[Eee Pad Transformer Android Development] Boss_Cuco:
So, with 1.2GHz stock no luck, with 1.4Ghz it boots into desktop but then it freezes.

Now I'm trying:

kernel image - 3.1.10-g6e2783c

kernel supplement - kernel_sup.tar.gz

Just one thing though, where do I copy the supplement to? To the root of the android drive?
[Eee Pad Transformer Android Development] onmail:
no, to the linux partition. basically the tar.gz has modules and firmware you need to copy to /lib/modules and /lib/firmware on the linux partition. If this kernel does not work for you, try http://xdaforums.com/attachment.php?attachmentid=2007000&d=1370012904 This one is the one I am playing with...
[Eee Pad Transformer Android Development] Boss_Cuco:
I see. And how can I do that if I can't get linux to boot? With ADB? I'm not sure how to do it...

Thanks for your help ;)

Do I need the supplements for your kernel? Is there any Kernel without supplements that works with Lubuntu v1.2?

---------- Post added at 12:39 PM ---------- Previous post was at 11:43 AM ----------

With kernel image - 3.1.10-g6e2783c I think it works. It boots into Linux and then it shows the desktop.

However:

- Touchpad does not work

- Freezes after a few seconds

I can not run any command as I don't have time for it during those seconds...

Is it because I don't have the kernel supplement?

I have this file: kernel_sup.tar.gz

How can I copy it to the root of the Linux partion? I'm with Windows 8.
[Eee Pad Transformer Android Development] onmail:
Well I am not sure I can help with that because I am no using win. But you could try to go to normal console window before login to X. On standard keyboard this can be done by Ctrl+Alt+F1 (or F2...). On the dock keyboard you do not have Alt and F buttons but you can do this by pressing Ctrl+Find+"no touchpad" (I think...). If you do this, are you in the normal text mode login? Can you log in or does it freeze again?

And I would recommend you to have Ubuntu instalation somewhere on your PC to prepare your own image. There is a great howto from TomTcom here http://xdaforums.com/showthread.php?t=2183376 and you can even chroot to your "ubuntu image" and prepare everything you need before putting it to your tablet (eg. installing xfce or gnome, network manager, copying those "kernel supplements" to its place. I have made a sh script I run after step 15 of this guide which I use to configure the ubuntu image and installs some usefull files (network manager, xfce,...) before I flash it to TF.
[Eee Pad Transformer Android Development] Kingzak34:
In any way, supplement files shouldnt have consequencies on boot, you should be able to boot without this complement filess ( it's for working wifi etc )

I allways installed complement after booting linux. Now i suggest you to test almost all kernel and see wich works the best ( look at x3maniac's goo too )

Test 1Ghz too I think your tab dont like ubuntu OC, mine workss well at 1.4Ghz

(2.6.XXXXXX) kernels are more stable than 3.1 Except jrohwer kernel, but it need to be adapted for dualboot.

jrower do you allow me to post your kernel for Tubuntu and for mountloop with GUI ?
[Eee Pad Transformer Android Development] Boss_Cuco:
Thank you very much!! It is working now with linux-1.0ghz-2.6.36.4.img from x3maniac's goo!

Now a few questions:p

I've already done: sudo resize2fs /dev/mmcblk0p8

Do I need to do this as well (from your guide):

sudo apt-get purge linux-image-ac100

sudo apt-get purge linux-image-3.1.10-6-ac100

The wifi already detected my home network and the touchpad is working! Do I need to install the complements? If so, which one for this kernel?

Do your Tips from post #3 in your guide still work with this kernel? To get Sound and Software Center working for example.

Thank you again! :D
[Eee Pad Transformer Android Development] Kingzak34:
Soooo, glad to hear that, you see, never give up before trying everything :)

So yes, you need to do the apt-get purge, if not you'll be stuck when installing some software.

No you dont need to install supplement, x3maniac allready installed them for these 2.6 kernels ;) That's why wifi and touchpad etc is working.

And yes all is described in my guide works with this kernel, it's the same as my guide ( only OC change )
[Eee Pad Transformer Android Development] Boss_Cuco:
Ok. I've installed the Ubuntu Software Center so I guess everything is ok now.

And about this kernel, any reason why this is not recommended? It's the only one that worked for me :p

About that other kernel, where we could install the nvidia drivers, any news?

Thank you all again!
[Eee Pad Transformer Android Development] Kingzak34:
Kernel is not "not recommended" but 1.2Ghz is good for almost everyone.

The other kernel are not stable ( I didnt test onmail kernel yet you may try it ) only jrohwer's one is stable but is for mountloop for now, we must change needed things to tubuntu app, but I've no time to play with it for now.
[Eee Pad Transformer Android Development] Kingzak34:
I just blobpacked onmail kernel, will try it and if it works will try upgrade and let you know ;)

Seems to do a kernel panic, will do some test
[Eee Pad Transformer Android Development] TomTcom:
I'm working on creating my own 3.1.10 initrd or trying to modify the one from x3's git. I've learned a lot more again so we'll see what happens soon. :)
[Eee Pad Transformer Android Development] Kingzak34:
The 8MB limit for kernel partition is for all TF ? Cause my kernel blob file iis 8,68MB that's maybe the problem ?

[MENTION=3864537]TomTcom[/MENTION], looking forward to it :)
[Eee Pad Transformer Android Development] jrohwer:
Yes it's for all TF with the default partitioning scheme. The OLiFE script does a repartitioning to increase the boot partition (not sure by exactly how much) in addition to creating an additional partition (/dev/mmcblk0p8) for Ubuntu. Not sure about the Tubuntu installer, but it is nvflash based so in principle it could do the same thing.

All of this is not available on TF101G because we don't have nvflash/wheelie. So I'm stuck on the 8MB limit. And if you haven't repartitioned you'lll be stuck as well. BTW look at your initrd to decrease the blob size. You don't need all the kernel modules in the initrd. It is sufficient if they are present on your rootfs.
[Eee Pad Transformer Android Development] Kingzak34:
Yes tubuntu repartitionate too and create a new partition, I don't know for resizing the boot partition.

Anyway thanks for answer I'll see what can be done

( I'm using mountloop so my tab is in default scheme for now )

Envoyé depuis mon Nexus 4 avec Tapatalk
[Eee Pad Transformer Android Development] Kingzak34:
Here's the initrd of onmail kernel.

How can I know what can I move out to separated supplement folder ?

Sorry for my noob question once again :)

EDIT : I got it, I'll try so ;)

---------- Post added at 02:19 PM ---------- Previous post was at 02:02 PM ----------

So, without /lib/modules/3.1.10, initrd still the same size and my blob too (8.83MB). ( 3.1.10 folder was 920KB )

Does anyone know what can I move safely to supplement file to make it smaller ? ( I can post it if needed and if onmeil give me permission )
[Eee Pad Transformer Android Development] onmail:
As I said before the initrd is from a kernel which I have downloaded and I am not sure where it was... But I think there should be no problem posting it, it is just linux intitrd, no proprietary software or licensed stuff... About deleting things from the initrd, well I am not sure what you "need" and what is not needed. You can test it ;)

And one more thing - you can repack the initrd with LZMA which makes it smaller ( find . | cpio -H newc -o | lzma -c > ../initram.lzm) but you need to set the option CONFIG_RD_LZMA=y when compiling kernel. If you want to try the kernel which I have posted, it is already compiled with this option so you can try to delete just some modules, repack it and make the image again. I am not 100% sure but I think so.