yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] conizius:
Well best would be to update the drivers first :)

X-Server will not start if you configured to load nvidia drivers in xorg.conf until you update the kernel, BUT you can easily flash the kernel with a non working ubuntu, but it's harder to update the driver without visuals ;) (well ssh, or chroot will work fine but it should work without it).

So:

1. update to 12.04 (optional)

2. remove pulseaudio (only for 12.04 because it causes crashes)

3. install nvidia drivers (use --abi 11 for 12.04)

4. flash kernel

If the x-server does not start after flashing the kernel, it will probably be because of a false kernel, or some library not installed.

You can then always revert back to not using nvidia driver by renaming xorg.conf.

Good luck :)

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

Oh and does anyone else get strange screen tearings in 12.04 with jhintas kernel?

Looks if some part of the window is not updated.

The result looks like I used a scissor on my part of my window, especially when selecting text. And sometimes buttons will first appear when hovering over it.
[Eee Pad Transformer Android Development] Jhinta:
Do a display detect when it looks scrambeld.

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] conizius:
it removes the tearing for one time, but they come back just as fast most of the time. Is there any way to fix it any longer?

Got some other strange bug: when I plug in an usb mouse(for investigation with the java backspace/arrowbuttons bug) my keyboard stops working.

Now strage is that evtest sees the events without problems.
[Eee Pad Transformer Android Development] Jhinta:
Finaly got main nv up with commits , will add some patches and tomarow i will start testing to build a more clean setup
[Eee Pad Transformer Android Development] kennyMC:
mount ubuntu partition

can somebody tell me how i can mount the ubuntu partition under android?

thx in advance
[Eee Pad Transformer Android Development] Ke1evraTi:
It really depends on your setup because partitions can be different. I recommend searching the thread for explanations of how others have done it. You could try mounting /dev/mmcblk0p8.
[Eee Pad Transformer Android Development] conizius:
from a terminal type:

su

mount /dev/block/mmcblk0p8 /sdcard/mnt

And if you want to change into the ubuntu system (kind of)

chroot /sdcard/mnt/ /bin/bash

Viel Spaß!
[Eee Pad Transformer Android Development] jrohwer:
3.1.10 kernel (Jhinta) boot image and initrd for SBKv2 devices

Disclaimer: as always use at your own risk, I am not responsible for any bricks! Make sure you know what you are doing before flashing new kernels, etc.!

I haven't seen them posted on this forum so I'm posting the kernel, modules and Initrd for Jhinta's latest kernel (3.1.10) with the latest asusec patch, compiled for use in SBKv2 devices.

CWM flashable zip which will install ubuntu kernel

kernel modules

initrd source

Notes:

This is a loop mount setup for use in SBKv2 devices. It assumes that your ubuntu partition lives in a file /sdcard/ubuntu.img under Android.

The kernel image can be extracted from the kernelblob in the CWM zip file with the standard blob tools.

Extract modules.tar.gz into /lib/modules in your ubuntu root filesystem.

Initrd is compiled into the kernel image as the kernel is too big to load the initrd separately and we can't repartition SBKv2 devices with larger boot image. As described elsewhere in this thread (CONFIG_INITRAMFS_SOURCE). The initrd is confirmed working and source attached separately.

The android data partition is ready mounted under /mnt/androiddata under Ubuntu so you can access all your files.

This is for running off internal storage, if you want to loopmount the Ubuntu image from MicroSD, you'll have to edit the init script in the initrd source to point to /dev/mmcblk1p1, and you'll have to recompile the kernel with your modified initrd. See this thread.

Thanks to Jhinta, lilstevie, rdnetto, shaola, jozka.1, ssciberras and all the others for making this possible :)
[Eee Pad Transformer Android Development] aldur999:
I'm sorry but I really can't understand this initrd thing. I know what it is and what it does, bum I'm on a v1 devices with Ubuntu in mountloop on internal SD. I tried your kernel and I've got kernel panic, what am I missing? I tried the kernel that Jhinta preoviously posted in the other topic (Ubuntu on sbkv2) and it works.
[Eee Pad Transformer Android Development] jrohwer:
If you're on a SBKv1 device than there is no need for this and you can use Jhinta's kernel directly and use the OLIFE script and nvflash to flash ubuntu. It is much easier.
[Eee Pad Transformer Android Development] aldur999:
Ok, but I'd like to keep my datas in internal storage, so I decided to use mount-loop image. So I have to consider myself as a SBKv2?
[Eee Pad Transformer Android Development] jrohwer:
No you should of course be able to use it with a sbkv1 :-)

The kernel panic most probably stems from the fact that the kernel can't find the root file system and this will happen if the loop mount is not setup correctly. Where is your loopmounted image located (in Android) and what is the filename?

Can you post a screenshot of the kernel panic?
[Eee Pad Transformer Android Development] aldur999:
Sure :) My loopmounted-image is located in /sdcard/ubuntu.img.

And here is the screen

Umh it doesn't show anything, arrowkey are just shown, but in Eclipse I can't get them working.

Is there a way to log "multi" key pressed togheter? Neither fn shows anything.
[Eee Pad Transformer Android Development] linuques:
I've tried your kernel on my sbkv2 and got the same kernel panic of the friend above.

Ubuntu 12.04, img on /sdcard/ubuntu.img
[Eee Pad Transformer Android Development] jozka.1:
What do you solve?

Kernel (for mount loop - sdcard/ubuntu.img) with last update is here: http://xdaforums.com/showthread.php?p=23428126
[Eee Pad Transformer Android Development] jrohwer:
I am not aware of a compiled kernel with the latest asusec patch (which gets all the keys on the keyboard working) being posted before. I am also following the thread you are referring to above and did not come across the post. In case I may have missed the post - my apologies! I never claimed to do something new, just posted the kernel to save someone else from having to compile it themselves....

Also there have been requests (can't find the exact post now) to post an initrd that works for SBKv2 devices. Thats why I posted the initrd source incase someone wants to incorporate it into their own kernel compile.
[Eee Pad Transformer Android Development] Jhinta:
Update:

git will be done today , working on it ( compile testing )

BTW compiling with a 8 core :eek:damn that was fast.

:mad: they have proxy on my work cant upload to a lot of things !
[Eee Pad Transformer Android Development] jrohwer:
How did you install the kernel? Did you flash the zip I posted with CWM? Or did you extract the kernel from the kernelblob and make your own bootimage (maybe with your own initrd)?

I have never seen the "run-init: nuking initramfs contents" error. The bootimage I prepared has an empty initrd since the initrd is already compiled into the kernel.
[Eee Pad Transformer Android Development] aldur999:
No in fact you did a great job :) I tried inserting you zImage in the blob I previously had working and I've got the same kernel panic, so I don't think is caused by initrd, but from the same kernel. Where is the asusec patch? Is it already in the git?
[Eee Pad Transformer Android Development] Jhinta:
give me some time , ill will have git fully running . it will be today
[Eee Pad Transformer Android Development] conizius:
Yeah it must be something higher than evtest shows us. As I said before: it must have something todo with the touchscreen, because if you don't use it, eclipse just works fine.

I found a bug report about this behaviour for eclipse, but it was old and said to be fixed (or rather not a problem of eclipse but swt).

In that particular bug report the conclusion was, that it occurs if a mouse button is pressed while pressing the keys.

Because if you bind the keys through eclipse to some other function, it will work.

It is only the native swt input, that does not get (the right) input.

evtest gives no "mouse button" events for the touch screen, it must be a higher layer.

xev on the other side sees the button1 events, but also releases them.

It must be an other button event... But I have no clue which one gets stuck.
[Eee Pad Transformer Android Development] Jhinta:
can you please sen me your evtest for the touch screen , forgot how to fix the touch screen ( for git )

just do evtest with 1 touch and copy past
[Eee Pad Transformer Android Development] aldur999:
Sorry, I've read the post just now.

No I tried first (at the time I posted here) to flash your CWM zip.

Then, I tried excracting the blob, or better the zImage, and updating the blob I had working, I think by Jhinta.

It's really weird, I've made some googling and I didn't find anything relevant. So the initrd is in the same zImage? I saw another user with the same problem, so there has to be something wrong there.

Sure, thank you :) I have a moderate knowledge of Linux and C, so if there's something I can do to help, just tell me..
[Eee Pad Transformer Android Development] Jhinta:
got my touchscreen fixed looking to OC and iḿ done
[Eee Pad Transformer Android Development] linuques:
Waiting for the OC patch. Thanks!
[Eee Pad Transformer Android Development] Jhinta:
git is up git://github.com/Jhinta/TF101-GNU-kernel.git

only have to add OC but git works.

---------- Post added 24th May 2012 at 12:26 AM ---------- Previous post was 23rd May 2012 at 11:39 PM ----------

got a compile error on OC but i need to sleep .

so iḿ off
[Eee Pad Transformer Android Development] jrohwer:
Yes, I see that, but it's funny because the blob works perfectly on my own system and I don't get the kernel panic, so I don't understand it. What model TF do you have? I have a TF101G, but the kernel was compiled on my Linux box with the codesourcery cross compiler. Well if you have another kernel working then it's not critical for you at least.

Once the OC patch is available on git I'll recompile and post my result.
[Eee Pad Transformer Android Development] conizius:
Here are the logs from evtest and the same click/touch in xev

Totally different question and not that important: is there a way to get to ttys? Using ctrl+alt+[some function key that maps to some F-key] it changes but I get a black screen. I can type commands, so it changed to tty, but have no visual :(
[Eee Pad Transformer Android Development] Jhinta:
what is you console=??

tnx btw but was fixed already
[Eee Pad Transformer Android Development] conizius:
well I changed it to tty1, if I remember right (not at home at the moment)

Does that mean I can only use tty1 for later usage? Used F2 therefore tty2 till now :)

Boot messages are shown just fine.

Will try it a little later. Can I change some key to F1 with xmodmap, or is it catched at some earlier point where xmodmap will do nothing good?

Edit: oh and touchscreen already fixed? great :)

It's in the git?

Have to look into how I compile it when I get home.
[Eee Pad Transformer Android Development] delphiki:
Hi folks,

I saw all the progress made here and wanted to try ubuntu on my tf101 again (tried it severals months ago, all went fine, but I still got rid of it).

I flashed it in dualboot using OLife.

All the flashing process went fine, and Android is working nicely.

But on first boot on Ubuntu, I got this screen with these warnings about "the util fdisk doesn't support GPT" and partitions table :

After waiting a couple of minutes it finally booted up.

But when I wanted to manually inject bluetooth and wifi firmwares, /dev/mmc0p7 was nowhere to be found...

I tried reflashing it severals time, redownloaded the rootfs, Olife, etc. but same result.

Note : I never succeeded to detect my SBK version properly (I'm guessing it's a v1 since all went fine the first time I tried Ubuntu).
[Eee Pad Transformer Android Development] Jhinta:
You downloaded rootfs olife etc ?

What is etc ?

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] delphiki:
etc stands for etcetera, should have write "..." instead, sorry :rolleyes:

I meant nvflashable rom, backups...
[Eee Pad Transformer Android Development] Jhinta:
What is etc ?

as what you did more

So you have Q and rootfs , well oke

My point being that you dint read and thats wehre you are now , and for us to help you we need a litle more then i got Q and rootfs and it doent work.

Dit you get the correct files?

Dit you changed your config?

Dit you select the correct menu when you have the files?

what is you cmdline?

How do you want to run it roofs or native partition?
[Eee Pad Transformer Android Development] delphiki:
I checked md5sum of OLife and rootfs, both OK.

And I used boot.img & system.img from my android backup.
[Eee Pad Transformer Android Development] Jhinta:
1 READ !!!!

2 download a zImage , some pages back ( READ !!!!! )

3 download initrd ( again READ !!!! )

4 change config to do tty on 1 (console=tty1)

5 Remove 2368-initrd and 2368-zImage in Q and replace it whit the on you donloaded ( same name !!!! )

6 flash from 3-5-1 i belief

7 READ !!!!!

---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------

il will reedit Q , or is somone already doing this?
[Eee Pad Transformer Android Development] delphiki:
Sorry mate, didn't know the wiki wasn't up-to-date or the method had issues (that's what I followed).

I'm one of the first to be upset when someone didn't read the topic, so I know the feeling, my bad.

Will do as you say, thanks. ;)
[Eee Pad Transformer Android Development] lilstevie:
The firmware injector should not mention anything about /dev/mmc0p7 what are you doing?
[Eee Pad Transformer Android Development] delphiki:
I just followed the manual firmware injection as described on the wiki here (didn't have access to my pc to use OLife at that time) : http://xdaforums.com/wiki/ASUS_Eee_...ntu/Ubuntu_Install#Post_install_configuration
[Eee Pad Transformer Android Development] lilstevie:
wow no idea who wrote that, those instructions will never work.

I will be updating things soon, holidays start in a few weeks
[Eee Pad Transformer Android Development] jrohwer:
HW acceleration under KDE

For everyone running KDE, if you want to get HW accelleration going using Jhinta's latest 3.1.10 kernel, do the following.

$ sudo apt-get install kde-window-manager-gles

Make a file $HOME/.kde/env/set_window_manager.sh and make it executable (chmod 755), with the following content:

#!/bin/bash
export KDEWM=kwin_gles

Restart KDE. Under SystemSettings -> Desktop Effects -> "Advanced" tab, select Compositing type OpenGL and then you should be able to enable desktop effects with HW accel.

(I have not investigated Unity or Gnome and don't know if they are shipped compiled with GLES support).
[Eee Pad Transformer Android Development] delphiki:
Thanks. Now I know I'm not crazy.
[Eee Pad Transformer Android Development] Jhinta:
just boot to ubuntu and look on the android partitions for the files its the same
[Eee Pad Transformer Android Development] aldur999:
I've a classic TF101 16Gb and no it's not critical, but it's really weird, I'll investigate further.

Perfect, thanks :)

And just another question, while it boot (even if I have all modules located in the correct folder, and loaded on boot), modprobe complains something like "FATAL: can't find modules in kerneldir". Is it normal?
[Eee Pad Transformer Android Development] Jhinta:
could you create a rootfs for kde only ?
[Eee Pad Transformer Android Development] delphiki:
Actually I'll wait and use OLife once I get home this evening. Will be easier.

Thank you both anyway.
[Eee Pad Transformer Android Development] jrohwer:
I can try but you'll have to give me some time. I started out from lilstevie's 11.04 rootfs and then upgraded to 12.04 and installed KDE-desktop. So my current rootfs needs to be trimmed down I guess...
[Eee Pad Transformer Android Development] aldur999:
Trying to compile from git,

arch/arm/mach-tegra/board-tf101.c tries to include linux/i2c/fm34_voice_processor.h, but it's not included in the git. Is there something I'm missing? :P
[Eee Pad Transformer Android Development] Jhinta:
just got home ,ill look add it

---------- Post added at 07:26 PM ---------- Previous post was at 07:16 PM ----------

File added compile again please

---------- Post added at 08:14 PM ---------- Previous post was at 07:26 PM ----------

whyyyyyy :mad::mad::mad::mad::mad:

My AC is DEAD cant power on anymore and back up ac is like 100km away

:(:(:(:(:(

Soo cant do anything but work on ubuntu for my HoX :p
[Eee Pad Transformer Android Development] ssciberras:
Finally got 12.04 on tf.

had tried using minimal install from jozka, but failed.

Then finally, bit the bullet and updated my 11.10 image. Took ages, and lost wifi - but now everything back to normal ( thanks to backup images !)

Now main issue is the kb - some keys like | are not recognised.

How can i proceed to map them? or possibly help to map them?

And some one posted about adobe reader on the tf - but i cannot find it in any package, i do not believe there is an arm version. or is there?
[Eee Pad Transformer Android Development] aldur999:
WTF, it's a shame :(

Btw, it compiles, even if I had to comment /arch/arm/mach-tegra/headsmp.S's line 301 because it prevented me to compile, I googled a bit and I found it's useless. Now I'm having some troubles with initrd and kernel panic, but except this, it's a little step :P
[Eee Pad Transformer Android Development] Jhinta:
witch corsscompiler are you using ?
[Eee Pad Transformer Android Development] jrohwer:
Are you using the latest 3.1.10 kernel from Jhinta with the asusec patch? I had some issues with keys not recognised before that, but I think "|" was not one of them. It was Fn-up (=PgUp) and Fn-down (=PgDn) as well as some others but with the asusec pach all the keys are recognised.

I attach my .xmodmaprc but you may modify it depending on personal taste. Top row I have mapped to F1...F12, as well as some other special keys in the rest of the keyboard (e.g. R-Alt and Menu to Ins and Del). Note this file only works with asusec patch, without the patch, the mappings are completely different.
[Eee Pad Transformer Android Development] aldur999:
I'm using arm-linux-gnueabi-.

Ok my problem is: what kind of initrd image should I use? Inside or outside zImage? I'm making various try, but I always get a kernel panic, using the CWM zip you posted in SBKv2 thread updated with new zImage, and compiling initrd within the kernel I get "bio too big device loop0".

Where am I wrong?
[Eee Pad Transformer Android Development] Jhinta:
from what i read is that they include it in to the kernel , but i dont have sbk2 so cant say anything bout it but fix sould be there
[Eee Pad Transformer Android Development] jrohwer:
FWIW I attach my kernel config - maybe diff it with yours to see if there are any obvious differences. This is with codesourcery cross compiler (arm-none-linux-gnueabi-). You'll only have to edit CONFIG_INITRAMFS_SOURCE to the path of your initrd. I posted my initrd yesterday and it works with this config. But as you said my kernel image gives you kernel panic which I don't understand...maybe if you compile it yourself?

What is the size of your ubuntu.img? Mine is 6.0G.
[Eee Pad Transformer Android Development] Jhinta:
btw how did you create boot.img? -r xxxx?
[Eee Pad Transformer Android Development] jrohwer:
I used mkbootimg from the AndroidRoot Boot Tools (https://github.com/AndroidRoot/BootTools), not abootimg. mkbootimg automatically calculates the size of your boot image and you don't have to specify it in the config file.

mkbootimg --kernel zImage --ramdisk initrd.img --cmdline "nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty1 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/loop0 ro quiet text" -o bootimage

Then pack up boot image into a blob for flashing:

blobpack kernelblob LNX bootimage

Empty initrd.img created from empty directory as follows (because initrd is already compiled into kernel, but you need initrd.img for mkbootimg command).

mkdir initrd
cd initrd
find . | cpio --quiet -o -H newc | gzip > ../initrd.img
[Eee Pad Transformer Android Development] aldur999:
Ok I'm compiling right now, I'll try with mkbootimage and your initrd and we'll se :) Thank you anyway

EDIT: nothing to do, I keep on having that unsolvable kernel panic. I swear, I don't know other things to do!
[Eee Pad Transformer Android Development] 090:
driver update?

Hi,

I did the driver update based on this guide.

How do I know that the driver have been updated successfully?

I'm trying to flash 3.1.10 kernel based on this wiki. But I'm stuck at step 3 since the download link is dead. I searched the thread but couldn't get it from anywhere.

With friendly greeting!
[Eee Pad Transformer Android Development] conizius:
you can have a loot at the xorg.log to see if the driver is loaded correctly.

You'll finde it in /var/log/

And to see if all libraries are loaded correctly you can try to start chromium with the gles option

Edit: Oh well just saw that you struggle at flashing... Well the drivers can not work without that kernel. Therefore there is no need to test it :)
[Eee Pad Transformer Android Development] ssciberras:
thanks your xmodmaprc works nicely.

except that my fn keys and the backslash do not work. Maybe am using wrong patch? i am using jozka.1 's ubuntu31-patch for sbkv2
[Eee Pad Transformer Android Development] lilstevie:
now that the secret project that we (AndroidRoot.mobi) have been working on has been released (Wheelie) I am going to update the installer to use wheelie and gain sbkv2 support soon
[Eee Pad Transformer Android Development] jrohwer:
I used the patch directly that Jhinta posted here:

http://xdaforums.com/showpost.php?p=26149064&postcount=2048

All the keys are now working on my keyboard.

I then compiled my own kernel from Jhinta's source with the INITRD compiled into the kernel (as I am using a sbkv2 device). I posted my kernel here

http://xdaforums.com/showpost.php?p=26456276&postcount=2112

but some people have been having kernel panic issues with it, and we haven't yet been able to figure out why.
[Eee Pad Transformer Android Development] ssciberras:
I have seen that. unfortunately, even I am having kernel panics with that.

I had thought jozka.1 had updated the zip file - i have a sbkv2, and had run into similar probs when compiling, and his always worked nicely.

Am checking if I have all the necessary drivers.

It is one of the few last things that is troubling me.

EDIT ----> added mtrack driver, no effect on keyboard layout.

---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------

Compared to the mount-loop method, this would mean erasing all data, am i correct.

would you use it similar to the olife scripts?
[Eee Pad Transformer Android Development] Jhinta:
You stil got loop to big failer ?

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] Jhinta:
Btw how big is you loop file ?

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] ssciberras:
I can boot using jozka.1 latest kernel ( Ubuntu31.zip and Ubuntu31-patch, although I do not know what is the difference yet)

I have upgraded to 12.04 as well.

It is only this keyboard issue that is bothering me at present - there are some issues with graphics at times, and with hdmi (occassionally locks keyboard)

USB now works all the time

My loop image is 6.5gb, with some 1gb to spare. Cleaning up extra stuff always works.
[Eee Pad Transformer Android Development] Jhinta:
USB got fixed when end where ?
[Eee Pad Transformer Android Development] jozka.1:
Yes, I noted too USB is work but I don't know why :D
[Eee Pad Transformer Android Development] Jhinta:
Witch kernel ? From git ?
[Eee Pad Transformer Android Development] Jhinta:
So you can reconnect USB devices ? And they work then also ?