yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] vhda:
I've never worked with udev scripts before, but I can try to create one if you haven't done that already.

Isn't there anyway of bootstraping the eMMC "directly"? It would be great if we could do something like the following in the flash script:

1. Generate an empty ext3 filesystem with the size just above the required for bootstraping.

2. Flash the empty filesystem.

3. Bootstrap Ubuntu/Debian directly to the empty ext3 filesystem eMMC.

4. Install our own .deb package with tf101 specific configurations (including that script of yours that resizes the root FS).
[Eee Pad Transformer Android Development] lilstevie:
you could, but then there is the problem of requiring to download the whole thing live, which would mean needing to make sure wifi was up early etc.
[Eee Pad Transformer Android Development] vhda:
I was considering that there was an Android running in the tablet and we could send the bootstrap output through adb or something similar.
[Eee Pad Transformer Android Development] lilstevie:
Those of us who run our devices with pure linux do not. :) there is nothing wrong with using an image anyway, the rootfs used is what is done for the beagleboard, in fact... it is the beagleboard image with the tf stuff injected
[Eee Pad Transformer Android Development] vhda:
It seems that disabling combo scan makes bcm4329 more stable and not show any warning messages in syslog anymore. Had to also disable PNO support, whatever this is. I think that brcm80211 in 2.6.38 that you are using already has this disabled. But decided to share the tip, nonetheless :)
[Eee Pad Transformer Android Development] belzebub40k:
I found an interesting article about a compressed swap space in the RAM. It sound interesting and may solve the problem off freezing tablets when running out of memory.

INCREASED PERFORMANCE IN LINUX WITH ZRAM (VIRTUAL SWAP COMPRESSED IN RAM)
[Eee Pad Transformer Android Development] belzebub40k:
I want to try the new U-BOOT bleeding edge version but I have two questions?

1. How safe is it to flash the bootloader? Am I still able to access APX-Mode if I mess up my bootloader.bin?

2. Is it possible two revert to the stock bootloader after flashing U-BOOT?
[Eee Pad Transformer Android Development] lilstevie:
both questions can be answered with a simple yes, APX is in bootrom, not bootloader
[Eee Pad Transformer Android Development] rickatnight11:
For more information about the Transformer's boot process, check out my thread here.
[Eee Pad Transformer Android Development] belzebub40k:
I'm trying to compile U-Boot but is doesn'T work. What is the right way to compile it for the tf101?

I tried the following commands after setting up the arm toolchain but I'am not really shure if they are right.

make ventana_config
make
[Eee Pad Transformer Android Development] lilstevie:
Following muromecs instructions,

make ARCH=arm ventana CROSS_COMPILE=/path/to/arm-linux-gnueabi- DEV_TREE_SRC="tegra2-tf101"
[Eee Pad Transformer Android Development] belzebub40k:
Ok that worked but I the process failes at the following point:

make -C dts/
make[2]: Entering directory `/space/tf101/uboot-tegra/dts'
dtc -R 4 -p 0x1000 -O dtb -o dt.dtb /space/tf101/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts
DTC: dts->dtb on file "/space/tf101/uboot-tegra/board/nvidia/ventana/tegra2-tf101.dts"
/space/tf101/uboot-tegra/board/nvidia/ventana/../../../board/nvidia/seaboard/tegra250.dtsi:3 Couldn't open "skeleton.dtsi": No such file or directory
make[2]: *** [dt.dtb] Error 1
make[2]: Leaving directory `/space/tf101/uboot-tegra/dts'
make[1]: *** [dts/libdts.o] Error 2
make[1]: Leaving directory `/space/tf101/uboot-tegra'
make: *** [ventana] Error 2

Any suggestions why this happens? I am using a fresh copy of your repository.

The file exists under /space/tf101/uboot-tegra/board/nvidia/seaboard/skeleton.dtsi
[Eee Pad Transformer Android Development] fonix232:
Try to edit the calling file (/space/tf101/uboot-tegra/board/nvidia/ventana/../../../board/nvidia/seaboard/tegra250.dtsi) and make a full path call instead of the local one. That should solve it. So, use the absolute path instead of the relative one!
[Eee Pad Transformer Android Development] belzebub40k:
Already tried this but will try again...
[Eee Pad Transformer Android Development] belzebub40k:
Google is your friend :D

This error occurs when using device tree compiler (dtc) in version < 1.3.
[Eee Pad Transformer Android Development] lilstevie:
you need to download and compile device-tree-compiler, the one in both debian and ubuntu trees is 1.2 but the FDT that is supplied here is for 1.3.0

that is a horrible idea :p
[Eee Pad Transformer Android Development] vhda:
Before I embark in the 2.6.38+u-boot adventure, could I ask you guys why you chose this kernel? From its name I can assume it is related with ChromeOS. Why can't we use an upstream kernel and then apply some Tegra patches?

Finally, will your work on these kernel ever reach upstream?
[Eee Pad Transformer Android Development] lilstevie:
The CrOS tree is the only one that has support for the required interfaces needed to get acceleration. Fingers crossed one day the kernel interfaces for acceleration make it into mainline, I will not attempt to get this stuff in until such time.

For now the biggest thing is getting everything together to get it into mainline ubuntu repos and a community image made
[Eee Pad Transformer Android Development] belzebub40k:
Ok as stated before U-Boot builds fine now. But how do I proceed? I flashed the u-boot.bin an d used the flash.cfg from the quoted post and it loads fine but the kernel can nor be loaded.

How do I make a proper u-boot.img from the Image/zImage in "./CrOS-Hybrid-Kernel/arch/arm/boot/". For now I tried reading back the partion "uim" (7) to file, mount it as loopdevice and copy Image to /boot/uImage. After reflashing the partition 7 and rebooting U-Boot fails loading the kernel (see attached picture).
[Eee Pad Transformer Android Development] lilstevie:
you need the uImage not the zImage, and you should have a uInitrd for the ramdisk, uim should be a 42mb ext2 formatted filesystem and you should craft a boot.scr which does ext2load on both the initrd and kernel and setenv bootargs to the kernel command line, then bootm {address kernel is loaded to} {address initrd is loaded to} I will post my u-boot.img in a few hours I lied, more like upload in a few minutes :p :)

u-boot.img.gz
[Eee Pad Transformer Android Development] belzebub40k:
After changing the path for uImage and boot.scr from /boot to / i got the kernel to boot. But I end up with the screen you can see on boot_2.jpg which says "init: plymouth main process (70) killed by SEGV signal". On boot_3.jpg you can see the output on first TTY.

An other issue I have noticed is that the following message occurs sevelral times when reading from eMMC: mmv_prepare_data: "Unaligned data, using slower bounce buffer" (boot_1.jpg)
[Eee Pad Transformer Android Development] lilstevie:
as for the plymouth process being killed, I don't know; I have it a few times, but it has never caused a problem.

as for the mmc_prepare_data it isn't going to go anywhere soon, it is a bug that is coming from places unknown, it occurs on all tegra devices
[Eee Pad Transformer Android Development] belzebub40k:
Damn I'm so dumb! Forgot to edit the fstab. Now it's working...
[Eee Pad Transformer Android Development] vit0oo:
I have this error :

vit0@ubuntu:~/uboot-tegra$ sudo make ARCH=arm ventana CROSS_COMPILE=/home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi- DEV_TREE_SRC="tegra2-tf101"
Configuring for ventana board...
make
make[1]: Entering directory `/home/vit0/uboot-tegra'
Generating include/autoconf.mk
Generating include/autoconf.mk.dep
make[1]: Leaving directory `/home/vit0/uboot-tegra'
make[1]: Entering directory `/home/vit0/uboot-tegra'
/home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x108000 -I/home/vit0/uboot-tegra/include -fno-builtin -ffreestanding -nostdinc -isystem /home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-eabi/4.4.1/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux -mno-thumb-interwork -march=armv5 -Werror -Wall -Wstrict-prototypes -fno-stack-protector \
-o lib/asm-offsets.s lib/asm-offsets.c -c -S
cc1: warnings being treated as errors
In file included from /home/vit0/uboot-tegra/include/config.h:5,
from /home/vit0/uboot-tegra/include/common.h:37,
from lib/asm-offsets.c:18:
[B]/home/vit0/uboot-tegra/include/configs/ventana.h:61: error: "CONFIG_ENV_SIZE" redefined
/home/vit0/uboot-tegra/include/configs/tegra2-common.h:105: note: this is the location of the previous definition
make[1]: *** [lib/asm-offsets.s] Error 1
make[1]: Leaving directory `/home/vit0/uboot-tegra'
make: *** [ventana] Error 2[/B]

Any suggestion ? : )
[Eee Pad Transformer Android Development] belzebub40k:
Comment out line 105 in /home/vit0/uboot-tegra/include/configs/tegra2-common.h to fix the problem.
[Eee Pad Transformer Android Development] vit0oo:
/home/vit0/uboot-tegra/include/configs/tegra2-common.h

105. define CONFIG_ENV_SIZE SZ_4K

And i have :

vit0@ubuntu:~/uboot-tegra$ sudo make ARCH=arm ventana CROSS_COMPILE=/home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi- DEV_TREE_SRC="tegra2-tf101"
Configuring for ventana board...
make
make[1]: Entering directory `/home/vit0/uboot-tegra'
Generating include/autoconf.mk
Generating include/autoconf.mk.dep
make[1]: Leaving directory `/home/vit0/uboot-tegra'
make[1]: Entering directory `/home/vit0/uboot-tegra'
/home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x108000 -I/home/vit0/uboot-tegra/include -fno-builtin -ffreestanding -nostdinc -isystem /home/vit0/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-eabi/4.4.1/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux -mno-thumb-interwork -march=armv5 -Werror -Wall -Wstrict-prototypes -fno-stack-protector \
-o lib/asm-offsets.s lib/asm-offsets.c -c -S
In file included from /home/vit0/uboot-tegra/include/configs/ventana.h:28,
from /home/vit0/uboot-tegra/include/config.h:5,
from /home/vit0/uboot-tegra/include/common.h:37,
from lib/asm-offsets.c:18:
/home/vit0/uboot-tegra/include/configs/tegra2-common.h:105: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'CONFIG_ENV_SIZE'
make[1]: *** [lib/asm-offsets.s] Error 1
make[1]: Leaving directory `/home/vit0/uboot-tegra'
make: *** [ventana] Error 2
[Eee Pad Transformer Android Development] belzebub40k:
You did somthing wrong. After commenting out line 105 it should look like this

/* define CONFIG_ENV_SIZE SZ_4K */
[Eee Pad Transformer Android Development] vit0oo:
yes that's work : ) thanks

edit : plymouth-splash main process terminated with status 2 ..
[Eee Pad Transformer Android Development] lilstevie:
edit your fstab
[Eee Pad Transformer Android Development] lilstevie:
just a question for those who have compiled u-boot from source, are your devices 16 or 32 gb
[Eee Pad Transformer Android Development] belzebub40k:
Mine is a B5O with 16GB
[Eee Pad Transformer Android Development] vit0oo:
we have to create a swap image ? ( can u plz share your fstab :o )
[Eee Pad Transformer Android Development] lilstevie:
the fstab in the ubuntu.img from my server is for running from mmcblk0p8 not mmcblk0p3.

just loop mount the image and edit etc/fstab to reflect the change
[Eee Pad Transformer Android Development] bonesjones:
I know this is off topic, I've spent the past two days researching this project. I wanna get involved but I gotta lot of reading still to do, for now I've got one question, can someone point me in the direction of getting module rtl8150 on my ubuntu, got a usb to ethernet adapter id like to use.
[Eee Pad Transformer Android Development] belzebub40k:
I think changing line 809 in <kernel_dir>/arch/arm/configs/tf101_gnulinux_defconfig will do the job.

[B]Before:[/B]
# CONFIG_USB_RTL8150 is not set
[B]After:[/B]
CONFIG_USB_RTL8150=y
[Eee Pad Transformer Android Development] bonesjones:
Does your post suggest I have to re-compile my own custom kernel?
[Eee Pad Transformer Android Development] belzebub40k:
YES

10 characters
[Eee Pad Transformer Android Development] bonesjones:
Ok thanks, Haven't compiled anything in years, and then it was just basic programs.

But thanks for pointing me in the right direction!
[Eee Pad Transformer Android Development] belzebub40k:
It's very simple just clone the git repository, make the changes and then run build_kernel.sh from inside the repository. The hard job is to make the new u-boot.img. But if you know how it's also easy. Make a loopmount of the image with:

mount -o loop <path-to-img>/u-boot.img /mnt/<whatever>

Then replace the old uImage in /mnt/<whatever> with the new one from <kernel-source-dir>/arch/arm/boot/uImage.

Now unmount the image with:

umount /mnt/<whatever>

Then flash your new u-boot.img with nvflash.
[Eee Pad Transformer Android Development] bonesjones:
I think i follow your first part.

However I'm not using uboot, yet.

Just found this dev this morning, I've done all my work using the "flash-linux-android.sh" methods.

I should probably take a step back, read some more then tackle this with a fresh system.

Also I should play with this uboot stuff and get caught up, like I said at first, I'm way behind on this. lol And my only goal in all this is to emulate a simple windows program.

I currently have to lug my tablet, and netbook around just for the netbook to run a program called PCpro to program phone systems.

It's a simple program and if I can manage Qemu then wine I think that'd work, or maybe virtualbox or something.
[Eee Pad Transformer Android Development] bonesjones:
Err think I just looked stupid. Lol I think I'm good now. Thanks for the direction.

---------- Post added at 03:48 PM ---------- Previous post was at 03:00 PM ----------

Ok I"ve read that there have been improvements, like the touchpad working etc.

Bluetooth working etc, anyway to go ahead and get all those updates before i compile this bad boy?

I want to of course be up to date as possible.

---------- Post added at 04:14 PM ---------- Previous post was at 03:48 PM ----------

Not finding build_kernel.sh anywhere.

*EDIT* Found it, was using the wrong GIT repo. Sorry for flooding.
[Eee Pad Transformer Android Development] belzebub40k:
I thought you are using u-boot with ChromeOS Kernel (https://github.com/lilstevie/CrOS-Hybrid-Kernel)
[Eee Pad Transformer Android Development] bonesjones:
No i'm running ubuntu 11.04 on TF101

---------- Post added at 05:48 PM ---------- Previous post was at 05:34 PM ----------

OK read everything, yeah i went way off topic.

Didn't relize people were compiling chromeOS.

I want to stick with pure ubuntu. Sorry to waste your time.
[Eee Pad Transformer Android Development] belzebub40k:
It's not ChromeOS it's just the Kernel with Ubuntu on it's top. ChromeOS is already ported to tegra based devices which makes it a good base to start building a working Linux kernel for the TF101.
[Eee Pad Transformer Android Development] jholtom:
So where exactly are we?

I've read through the thread but I'm still pretty confused about where we are and the functionality of u-boot and the kernel.

And yes I know how to compile a kernel and clone repos...e.g. I am not a newb

This is mostly so I can figure out how i can most benefit the project
[Eee Pad Transformer Android Development] bonesjones:
Ahhh, neat. I got my kernel ready, ill flash it Monday.
[Eee Pad Transformer Android Development] vhda:
Apparently, brcmfmac is receiving some love in the main kernel tree.

"A Broadcom WiFi driver also made it out of staging. [...]

The Broadcom WiFi drivers leaving the staging area is brcmfmac and brcmsmac. The brcmfmac is for the BCM4329 ASIC. Brcmsmac is the open-source bcrm80211 driver for the BCM4313 (0x4727), BCM43224 (0x0576 and 0x4353), and BCM43225 (0x4357) chips."

From:

http://www.phoronix.com/scan.php?page=news_item&px=MTAwNTY
[Eee Pad Transformer Android Development] vit0oo:
what is the real size of UBT and MPT ? ( size=-1 and size=0xFFFFFFFFFFFFFFFF )

I have to copy my linux.img on UBT or MPT partition ?

thanks
[Eee Pad Transformer Android Development] lilstevie:
UBT is as big as your flash will allow and MPT is not a Partition in the true sense of the word, it is the MBR marker
[Eee Pad Transformer Android Development] vit0oo:
ok so if I add : filename=./images/linux.img, I flash the UBT partition with linux.img, but UBT is /dev/mmcblk0p3 ?
[Eee Pad Transformer Android Development] lilstevie:
if using u-boot linux.img and recovery.img should be ignored as u-boot doesn't read the android bootimage container, the ubuntu.img should be going to UBT, but you need to edit the fstab to indicate that / is mmcblk0p3 not mmcblk0p8
[Eee Pad Transformer Android Development] vit0oo:
yep ok i will try this : )

thanks !

edit : I have ## Unknown partition table and Bad partition 2 3

I have use your u-boot.img on uim id=7
[Eee Pad Transformer Android Development] ilbulgaro89:
It's possible to port this on Transformer?

http://translate.google.it/translat...w.ekoore.com/forum/index.php/topic,347.0.html
[Eee Pad Transformer Android Development] belzebub40k:
It looks like that there is no ARM build availible for Ekoore. As long as ARM builds of a Distro are availible there should be no big problem porting them to the TF101
[Eee Pad Transformer Android Development] lilstevie:
do you have a 32GB device?
[Eee Pad Transformer Android Development] vit0oo:
@lilstevie No 16Gb device
[Eee Pad Transformer Android Development] jerdog:
Guys - as the OP has stated this is not a "please help me because I don't know how to do this!!!" thread. That thread is found here:

[Q&A] Ubuntu on the Transformer (eMMC install)
[Eee Pad Transformer Android Development] vhda:
lilstevie, could you please push the latest version of OLiFE to github? Or is it available somewhere within http://lilstevie.geek.nz?

I've had some stuff that kept me from playing with this in the last weeks, but I want to start again. I'm still trying to figure out how uboot works and looking at OLiFE might provide some clues (.sh files were easier to understand!;).
[Eee Pad Transformer Android Development] belzebub40k:
Current OLiFE is a bunch of Bash-Scripts you can obtain it from the thread over at RootzWiki http://rootzwiki.com/topic/947-ubuntu-on-the-transformer/

There is also a GUI version in development which can be found here http://rootzwiki.com/topic/6986-dev-olife-the-open-source-linux-flashkit-for-tegra/
[Eee Pad Transformer Android Development] jholtom:
with the new olife there is a cros kernel with all sorts of goodies

is it possible to take the image and initrd and use them in the clockwork mod dual boot method where you can flash two different zips to dual boot? or is it limited to using boot
[Eee Pad Transformer Android Development] lilstevie:
the new kernels won't fit in a flashable blob so no
[Eee Pad Transformer Android Development] mitchelln:
Hi.

Has anyone got this working under 64bit Ubuntu 11.10? I put my TF into APX mode and it just doesn't get seen by my system. The OLiFE script doesn't see the device. Running dmesg shows no USB connectivity and adb does not find the TF either (this is when booted with USB debugging enabled).

Any help greatly appreciated!

UPDATE - Okay, I did it with my laptop running 32 bit Ubuntu 11.04. I've never been able to get 64 bit Ubuntu 11.10 to do anything with my TF :(

Anyway, this is so cool :D. Loving my dual boot TF. Now to build my most portable LAMP machine yet :)

UPDATE 2. Unfortunately apache won't run as the kernel does not have shared memory, message queues or semaphore support :(
[Eee Pad Transformer Android Development] mitchelln:
Reluctantly I've had to take this off. It's caused really weird behaviour when booted into Prime.

The screen Home button stopped working. It would change colour when touched, but nothing would happen even when undocked. Also Dock function keys (wifi, bluetooth etc) weren't working and most worrying, the Mobile Dock firmware version was showing as "Not available".

The other odd thing was that I chose Android to be the default OS in the dual boot menu, but Ubuntu was booting by default. The only way to boot Prime was to hold volume down, let the 5 seconds pass and then I was taken to a wipe data screen. Pressing volume down to cancel the wipe then booted Prime.

So I used OLife to flash it back to stock and performed a nandroid restore from a backup I did just before trying all this and all was well. A real pity as I'd just got KDE working!

Has anyone else seen these weird issues?

Thanks.
[Eee Pad Transformer Android Development] brando56894:
I don't know where else to post this: since this replaces CWM how do we apply rom updates?

edit: my apologies..
[Eee Pad Transformer Android Development] Mistar Muffin:
Dude, the link to the Q&A/Help thread was posted by a moderator as little as 6 posts back from yours. In fact, it was on the current page of the thread before your post created a new one.

Meh, now I'm contributing to the problem too.
[Eee Pad Transformer Android Development] conizius:
Hey there,

just wanted to ask if http://developer.nvidia.com/linux-tegra was noticed and if it changes anything. Or is the current release from nvidia the same already used in OLiFE?
[Eee Pad Transformer Android Development] lilstevie:
No, I do not use nVidia releases, they are not nice :) the images I use are official ubuntu images for OMAP then injected with a few little things (modules, init.d scripts, daemon binaries).
[Eee Pad Transformer Android Development] Magnesus:
From what I read on osnews Android drivers are put into main linux kernel, so it should soon be easier to port linux to Android devices. http://www.osnews.com/comments/25457
[Eee Pad Transformer Android Development] lilstevie:
seems rather redundant. the issue is not the drivers missing from the kernel tree, it is interfaces not matching the specs that is the problem.

Also the linux kernel does boot without patches :) the only "patch" is the kernel config to have a kernel maintained /dev
[Eee Pad Transformer Android Development] conizius:
Oh well I didn't knew that... well of course I know that nVidia is not nice to open source, but can't we use some of their work? Maybe some of the hardware acceleration? Or isn't it more than achieved right now?

Sorry I'm still trying to find my way into the topic from the developer perspective...

Btw. nice job done :)
[Eee Pad Transformer Android Development] lilstevie:
Almost no GPU vendor has an open-source driver for acceleration. Ignore everything, nothing ever written on those kinds of sites are developers perspective :)
[Eee Pad Transformer Android Development] rdnetto:
Just in case anyone here missed it, Bluetooth is now working.

I've been doing some work on getting the internal speakers working, so I thought I'd share what I've got.

The (ALSA) device /dev/snd/pcmC0D0p is used for playback regardless for both headphones and the speakers. There is presumably a mechanism for enabling/disabling each output. This is probably managed by the WM8903 audio chip, which may be accessed via the I2C bus /dev/i2c-0 at address 0x1a. The datasheet states pretty clearly which bits have to be toggled to enable an output (see page 63), however I was unable to verify this using i2c-tools as that address is under the control of a kernel driver. Hopefully someone who's more familiar with the kernel will be able to do something with this information.

The interface which exposes the jack detection remains unknown.

Other useful information:

A description of architecture of TI Android systems. - While no such resources are available for the Tegra chips (AFAIK), this is pretty useful for understanding how different hardware may be connected and used under Android.

An index of all known I2C devices in the Transformer (attached). Generated from /sys.