yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] jozka.1:
Yes.

Not from GIT, the kernel is with the last update: http://xdaforums.com/showpost.php?p=26149064&postcount=2048
[Eee Pad Transformer Android Development] ssciberras:
I confirm - when using jozka.1 kernel, it works.

However, keyboard still does not work properly on my tf with his kernel
[Eee Pad Transformer Android Development] Jhinta:
Please can anyone compile the git and test becuase i think you all using the old zimage , i cant compile now. Please test this

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] jrohwer:
I was waiting for the overclock to be included. Does it work now? The last time you posted it was giving compile errors. What is else the difference between your git kernel and what you posted here:

http://xdaforums.com/showpost.php?p=26149064&postcount=2048
[Eee Pad Transformer Android Development] Jhinta:
sorry i realy dont have time , IF i get a change ill try. but realy buzzy on work
[Eee Pad Transformer Android Development] Jhinta:
:D 1.6 interactive

please test and let me know.

Back to work :(
[Eee Pad Transformer Android Development] jrohwer:
Sorry can't test - have a sbkv2 and need to compile INITRD into kernel :mad:

Do you have a patch I can apply and so that I can compile kernel on my own? Will gladly do so....
[Eee Pad Transformer Android Development] ssciberras:
remind me, why do we need the initrd compiled? is it just because of space issue?

It was easier when the initrd was separate and we needed to make the kernelblob, rather than compile the whole lot.
[Eee Pad Transformer Android Development] jozka.1:
So, think it up! :P

E: but now, when we have nvflash for sbkv2...
[Eee Pad Transformer Android Development] Jhinta:
git updated
[Eee Pad Transformer Android Development] Jhinta:
Don't you need \ for windows ?
[Eee Pad Transformer Android Development] tortilaman:
as in for the paths? After changing that it got one command farther I think, here's output from the command line:

sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully

C:\Users\Nick\Desktop\nvflashtf>"nvflash.exe" --resume --getpartitiontable nvfla
shbackup\partitiontable.txt
Nvflash started
[resume mode]
file create failed NvError 0x4
failed executing command 19 NvError 0x4
command failure: get partition table failed

C:\Users\Nick\Desktop\nvflashtf>"nvflash.exe" --resume --read 5 nvflashbackup\05
_SOS_raw.img
Nvflash started
[resume mode]

my slightly edited tf-backup.bat:

cd %~dp0
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
"nvflash.exe" --resume --getpartitiontable nvflashbackup\partitiontable.txt
"nvflash.exe" --resume --read 5 nvflashbackup\05_SOS_raw.img
"nvflash.exe" --resume --read 6 nvflashbackup\06_LNX_raw.img
"nvflash.exe" --resume --read 9 nvflashbackup\09_APP_raw.img
[Eee Pad Transformer Android Development] Jhinta:
Remove get partition line you only need boot recovery and system

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] tortilaman:
Similar difficulties with that line removed. I think I'm going to virtualize ubuntu as that might just be easier to do than this. Either way here's the output I got now:

sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully

C:\Users\Nick\Desktop\nvflashtf>"nvflash.exe" --resume --read 5 nvflashbackup\05
_SOS_raw.img
Nvflash started
[resume mode]
receiving file: nvflashbackup\05_SOS_raw.img, expected size: 5242880 bytes
file create failed NvError 0x4
command failure: read failed

C:\Users\Nick\Desktop\nvflashtf>"nvflash.exe" --resume --read 6 nvflashbackup\06
_LNX_raw.img
Nvflash started
[resume mode]
[Eee Pad Transformer Android Development] Jhinta:
It cant create the file , try apsolute path. C:

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] tortilaman:
At this point, I just want to have some kind of ice cream sandwich, are there any nvflashable ICS roms? I am having difficulty finding one. I give up on getting cm at this point.
[Eee Pad Transformer Android Development] jrohwer:
Yes just because of the space issue...

But unfortunately not for TF101G which has a sbkv3... so I'll have to stick to the previous methods :mad:
[Eee Pad Transformer Android Development] Thing O Doom:
Don't know of any NvFlashable ics roms, but NvFlash rouge then you can CWM flash a ROM --http://xdaforums.com/showthread.php?t=1446019
[Eee Pad Transformer Android Development] jrohwer:
Does the directory nvflashbackup actually exist as a subfolder of nvflashtf? If not, then your bat file obviously can't write to it...
[Eee Pad Transformer Android Development] lilstevie:
TF101G does not have sbkv3 AFAIK there is only 1 secure boot key for them, they are a different device that just happens to share the same hardware base, it is outside of the scope of the sbkv* nonclementure. if anything, it should be called sbkv1 again, as it is the first iteration for that device
[Eee Pad Transformer Android Development] jrohwer:
OK thanks for clarification. Does that mean that if the sbk were to become available, I would be able to use the current nvflash scripts just substituting the new sbk or would they have to be modified? E.g. different BCT and PT as compared to TF101?
[Eee Pad Transformer Android Development] lilstevie:
theoretically they should be the same, but we would have to see at the time
[Eee Pad Transformer Android Development] kennyMC:
Compiling Jhintas Kernel

when i try to compile your kernel from git, i get this error:

/tmp/cccRqGVO.s: Assembler messages:

/tmp/cccRqGVO.s: Error: .size expression for __tegra_cpu_reset_handler_data does not evaluate to a constant

make[1]: *** [arch/arm/mach-tegra/headsmp.o] Error 1

make: *** [arch/arm/mach-tegra] Error 2

is it my fault or a problem with git?
[Eee Pad Transformer Android Development] jozka.1:
Which cross compiler do you use?

I had similar problem when I used arm-linux-gnueabi-gcc. My solution is to use: https://sourcery.mentor.com/GNUToolchain/release1039?lite=arm
[Eee Pad Transformer Android Development] Jhinta:
does usb work correctly from git ?
[Eee Pad Transformer Android Development] jozka.1:
I tried compile it - successful but it doesn't boot. No errors etc, only it freeze on boot screen.

I haven't time it solve - examinations.
[Eee Pad Transformer Android Development] Jhinta:
True not working , git reseted to working one so no OC for now !!
[Eee Pad Transformer Android Development] TF101-Wizard:
Jhinta's Kernel Installing Nvidia Drivers for 12.04

How do i go about setting up the nvidia drivers because every time i try to apply the bin's it says "fuction not found. A guide on how to apply this would be helpful because i have been trying to install this for days now and the nvida developer guide doesn't explain how to install it all that well

Thanks TF101-Wizard
[Eee Pad Transformer Android Development] Jhinta:
how do you run it ?
[Eee Pad Transformer Android Development] TF101-Wizard:
Nvida tegra drivers

im trying to apply it from the tablet by mounting the ubuntu FS of the tablet to the RootFS folder then running it by /Linux_for_Tegra$ sh apply_binaries.sh

but i get apply_binaries.sh: 39: apply_binaries.sh: function: not found
[Eee Pad Transformer Android Development] NoDiskNoFun:
when i try to use olife with wheelie i run in many trouble i'd to overcome ... first i need to edit linux.cfg to work :

[device]
type=hsmmc
instance=3

[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=./images/bootloader.bin

[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=9265152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=./images/recovery.img

[partition]
name=LNX
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=9265152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=./images/boot.img

[partition]
name=GP1
id=7
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=UBT
id=8
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554720302
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0

[partition]
name=PAD
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=1024
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PA2
id=10
type=data
allocation_policy=sequential
filesystem_type=basic
size=1024
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=USP
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=GPT
id=12
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

i changend basic=filesystem_type to filesystem_type=basic

and in partion 8 filesystem_type=ext3c to filesystem_type=ext3

but now the device doesn't start ... it does nothing.

only on APX mode when flashing is finished and i hit the power button three or four times i can shortly see the linux boot-screen which ends with reboot (1) (Picture) ... and then it does nothing anymore.

anyone could help?

EDIT:

it automaticlly starts back into APX mode ...
[Eee Pad Transformer Android Development] jrohwer:
3.1.10 oc working

I did manage to compile the kernel from git with overclocking (before Jhinta reset it) and the kernel compiles and boots :D

Haven't yet noticed any errors. Obvious stuff (networking, hw accel, sound, keyboard) all working.

The overclock frequencies are all listed under

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

but I haven't stress tested it to see how OC performs.

Please download and test:

http://www.2shared.com/file/nTX6hRGX/3110-oc.html

Note, this is a zip file containing:

kernel image

initrd image

packed kernelblob for flashing (this is prepared for mountloop on /dev/loop0 with ubuntu.img on /sdcard in Android. If you use another setup you'll have to make your own blob.

the kernel config I used for compilation. Compiled with codesourcery crosscompiler (arm-none-linux-gnueabi-)

modules (extract into /lib/modules of your root filesystem)

Also, because this is a pared down kernel config compared to the previous one, the zImage is smaller and it is again possible to make a regular boot image with the initrd separate. No longer needed to compile initrd into kernel. Also on sbkv2 devices / TF101G. (I have TF101G).

Edit: Hot plug USB still not working...
[Eee Pad Transformer Android Development] aldur999:
Ok I think I'm in love with you :P

BTW, I finally solved my kernel panic problems, I post because it could be usefull for other users.

I hadn't folder /mnt/androiddata, so initrd couldn't mount root fs. I just created it and voila :)
[Eee Pad Transformer Android Development] Jhinta:
? how it didnt boot with me.:confused:

any way lasting i will look into is usb
[Eee Pad Transformer Android Development] kxs783kms:
Do I install this from Windows 7? Through the Transformer itself? Or from a Linux machine? I've read multiple pages, but I haven't found any clear cut instructions on how to use and install this kernel from Windows. Thanks in advance!!
[Eee Pad Transformer Android Development] MrMuffin24:
This is the result I get directly after flashing the kernel Jhinta posted. Would you like me to upload a video showing the kernel being flashed and then uname being run?
[Eee Pad Transformer Android Development] lilstevie:
doesn't change the fact that the running kernel is my kernel, that I am 100% sure of with that uname -a pic
[Eee Pad Transformer Android Development] jozka.1:
MrMuffin24: do you have SBKv2 and do you try org. kernel by jhinta? This can't work.

Initrd must be modified for loop mount and kernelblob by jhinta is greater than partition - you see flash blob (blue line), but it has no effect.

It's right?
[Eee Pad Transformer Android Development] MrMuffin24:
Yes! It's sbkv2 but not a loop mount, I just dd the rootfs using the method shaola posted. So this can't be done on my TF, sorry for the trouble.
[Eee Pad Transformer Android Development] Jhinta:
:eek: ahhhhhhhhh
[Eee Pad Transformer Android Development] jozka.1:
I've tried compile kernel and boot, but no success.

Which initrd do you use in your kernelblob, jhinta?

I'm begginer with linux kernel, so sorry.
[Eee Pad Transformer Android Development] schwigi:
Hi,

great work Jhinta, installed your Kernel and works like a charm.

Found a few things that are still missing.

I had a few Problems with the touchpad, but was able to fix it with the ubuntu 12.04 mtrack driver. Had to add an InputClass to the xorg.conf though

Section "InputClass"
Identifier "Touchpads"
Driver "mtrack"
MatchDevicePath "/dev/input/event4"
EndSection

I replaced the fb.c with the one from the latest Nvidia Kernel. As far as I can tell GLES ist working. Nice thing is ubuntu 12.04 has an nvidia-tegra package.

Wifi works with Networkmanager.

Sound is not working for me with the new Kernel. I'm not sure wether it's the new Kernel Driver or the Ubuntu update. Sound with aplay is still working using lilstevie's Kernel. But pulseaudio makes some pthread_mutex_unlock(...) assertion. So I guess it's both the Ubuntu update and kernel driver.
[Eee Pad Transformer Android Development] Ke1evraTi:
I just tried installing the kernel and have run into some issues. I installed l4t r12beta harmony drivers, copied over the modules, and flashed the 3d kernel. When ubuntu begins to load all I see on the screen is tux. The screen then briefly (>1sec) turns off and then turns back on, completely black. I have no command prompt and no ui.

I have a feeling this is due to installing the wrong l4t drivers but am not sure. Any ideas?
[Eee Pad Transformer Android Development] schwigi:
Hi,

The X-Server is not starting. I can think of 2 things you can check.

there should be a section in the file /etc/X11/xorg.conf

Section "Device"
Identifier "Tegra"
Driver "Tegra"
EndSection

the other thing is a bit more complicated. Flash the old Kernel, install openssh-server, try to connect to your pad with ssh, flash the new kernel an try to connect after the screen flickered.

You will propably find what's wrong in /var/log/Xorg.0.log. My guess is the Nvidia script detected the wrong X abi and installed to wrong version. If thats the case you can try to install an the remote console again or you have to copy the correct tegra_drv.so manually.
[Eee Pad Transformer Android Development] Ke1evraTi:
Thanks, it was a l4t driver issue. I put the original kernel back on, reinstalled the l4t drivers again, and then flashed the 3d kernel. It now works.
[Eee Pad Transformer Android Development] lilstevie:
The nVidia script does not detect X abi version, you need to manually specify it if it is not version 10
[Eee Pad Transformer Android Development] Jhinta:
your working on nvidia mainline right?

Also about ABI one can specify ignore AEB version in xorg.conf dont realy know if it works, and there is no 12 version -> nvida still has to make it.
[Eee Pad Transformer Android Development] lilstevie:
I will be, I am busy with another project at the moment. anyway, abi version 11 is what is used in precise and oneiric uses 10
[Eee Pad Transformer Android Development] Ke1evraTi:
How do I manually specify my abi version? I just did a clean reinstall of ubuntu, upgraded to 12.04, and now I cant install the nvidia package.
[Eee Pad Transformer Android Development] PierreZabell:
Update on Ubuntu for TFP

Hello forum,

How is it going with ubuntu for transformer prime atm?

Anyone can give an update status?

Been trying for weeks to run it properly, but i haven't got the needed expertise. :(

Thanks for any help :)
[Eee Pad Transformer Android Development] rmaniac:
My misc participation in this thread was in hopes of getting a nice Ubuntu setup on my Transformer. I, unfortunately, also have an sbkv2 version. So, if the kernal blob currently being tested (Ubuntu-3D.zip) is too large for the partition, is that ever fixable? Maybe I misunderstand the problem, but could we modularize a few more things, so it can fit in the standard partition and allow it to work on the sbkv2 devices? Let me know if I am barking up the wrong tree or if I should setup a build enviroment and see what I can do. I have not compiled an android kernel yet, so I will have a little learning curve. I have compiled standard linux kernels for a few archs, and have done some cross compiling before, so I am sure it is within my grasp.
[Eee Pad Transformer Android Development] Jhinta:
You can make it smaller more modules , beter compression . Just try and find out

---------- Post added at 11:26 AM ---------- Previous post was at 11:21 AM ----------

Give me the config of the system /proc/config.gz

I dont have the system but if your willing to try ill send you a kernel.

As always use at own risk
[Eee Pad Transformer Android Development] Ke1evraTi:
I tried to change the xorg.conf to ignore the abi version but it didnt seem to have an effect.
[Eee Pad Transformer Android Development] lilstevie:
I am in the process of writing an installer, at the moment the install method is not the best and trying to improve it to be a little better
[Eee Pad Transformer Android Development] atc3030:
Does this have USB host mode so i can use say a USB keyboard or wireless mouse
[Eee Pad Transformer Android Development] Jhinta:
i still have to update OP , i will do this in the weekend.

also will i create a live-xbmc image thats the line i want to go. pure xbmc.
[Eee Pad Transformer Android Development] conizius:
Well I got the same error, regardless of the compiler (ubuntu package arm-linux-gnueabi and arm-none-linux-gnueabi tried).

This page helped me to get grip of the problem.

Now here is a simple patch to get rid of this problem.

--- a/arch/arm/mach-tegra/headsmp.S
+++ b/arch/arm/mach-tegra/headsmp.S
@@ -298,6 +298,6 @@ __tegra_cpu_reset_handler_data:
.rept TEGRA_RESET_DATA_SIZE
.long 0
.endr
- .size __tegra_cpu_reset_handler_data, .-tegra_cpu_reset_handler_data
+ .size __tegra_cpu_reset_handler_data, .-__tegra_cpu_reset_handler_data
.align L1_CACHE_SHIFT
ENTRY(__tegra_cpu_reset_handler_end)

Now it's compiling further :)

Hope it helps
[Eee Pad Transformer Android Development] rdnetto:
Once you've compiled the kernel, use OLiFE (from liilstevie's thread) to flash it.
[Eee Pad Transformer Android Development] kxs783kms:
Thanks for the response guys!! Is OLife a Linux based installment? I have it downloaded and all of the necessary files, but I may not be understanding it because of that very reason. Will definitely be looking forward to those instructions this weekend.
[Eee Pad Transformer Android Development] kxs783kms:
What commands do i type in terminal to install the new nvidia drivers? I upgraded to 12.04. Did the new drivers already install themselves then?
[Eee Pad Transformer Android Development] 4512jth:
I'm constantly refreshing this post to see when you have finished it and I just have to say thank you very much for releasing this guide to allow us to put on our tablet any Ubuntu fork we want as well as being able to customize our kernel. Thank you!
[Eee Pad Transformer Android Development] Jhinta:
Still have to add some stuf but if you read all you can bulld easly now .

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] rdnetto:
Clarification for anyone who's a little lost on how to determine the ABI version of the X server:

Run the following command under the (Debian-based) Linux distro you're planning to use:

aptitude show xserver-xorg-core | grep abi

This will tell you which ABIs the X server supports. Use the latest supported ABI where possible. Note that the drivers currently only support ABIs ver. 5-12.

Also be aware that if you're using a rolling release distro like Debian, an update to the X server could theoretically break compatibility.

(@Jhinta, you might want to add a link to this post (or just copy it) to the OP.)

Why? As I understand it, -j specifies the no. of threads used in compilation. Using more than the no. of cores just makes it slower due to the increased overhead of context switching.
[Eee Pad Transformer Android Development] ssciberras:
is usb now working on your kernel, ie hotplug?

Still don't understand what is different between jozka and jhinta kernel.

And finally, if i do not use mount-loop method, but use wheelie to use nvflash, is there any major difference?
[Eee Pad Transformer Android Development] Jhinta:
No usb yet.

also about loop its all the same , its just a way to mount something.

it works like tis

bootloader->kernel->initrd-> init-mounts root parttion-> chainroot it -> and run init

with loop you get this.

bootloader->kernel->initrd-> init-mounts loop file some where -> make it root-> chainroot it ->init.

as you can see , its the same , its just a way of mounting something somewhere. (as we dont have a initrd that will do both , thats why we have 2 initrds )

iḿ trying to build one initrd that will do that loop or native.
[Eee Pad Transformer Android Development] rdnetto:
Just because you read something on the internet, doesn't mean it's right. :P

I imagine the logic behind it was something about using and unused processing power, but from what I've observed when compiling the kernel things run pretty close to 100% as it is. From a practical perspective, the difference will be negligible - you'll get a far greater reduction in compile time by using a tmpfs. (Mine compiles in just under 2 min on a Phenom II x6 using that approach).

Besides, under most circumstances you'd want there to be some available processing power to keep things responsive. If you were going to try and put every clock cycle to use, you'd want to use nice as well, either to max the priority or lower it to ensure the DE still has enough time to render.
[Eee Pad Transformer Android Development] Jhinta:
:eek: jealous of you :o only atom in de weekend , compile time like 30min+ but soon i will upgrade to a new system.
[Eee Pad Transformer Android Development] smithisize:
Looking forward to the completed op! Would love a more functional ubuntu w/ this :)
[Eee Pad Transformer Android Development] Jhinta:
updated some parts also , can anyone test the loop file mode please read op for that
[Eee Pad Transformer Android Development] rdnetto:
If it's any consolation, it overheats everytime it does. :p (I think I might need to add another fan...)

Not sure how much RAM you have, but a ~1.5 GB tmpfs results in something like a 5x speed-up if you're not already using it. From memory, I think it actually sped things up more than using all the cores...
[Eee Pad Transformer Android Development] ssciberras:
just compiled kernel.

what about initrd -> I thought it was compiled in the kernel?

thanks

stephen