yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] lilstevie:
do you know how to use nvflash to extract the contents of a partition?
[Eee Pad Transformer Android Development] kkttt:
Am I the only one who can't download the "TF101 Ubuntu rootfs" in OP?

The torrent in 2Shared can't be downloaded, got a 302 Moved Temporarily error. Mirror download link shows a message "Parameter 'out' is required." :confused:
[Eee Pad Transformer Android Development] nfusion77:
I was able to download it, i zipped it for you. Hope that helps :)
[Eee Pad Transformer Android Development] kkttt:
Thanks! :)
[Eee Pad Transformer Android Development] rdnetto:
Sorry if this is a bit off-topic, but I've run into an odd problem. The boot.img you provided works fine, but if I unpack it and then repack it without making any changes, the tablet freezes at the boot screen and reboots if I try to shut it down (was able to get out of it via CWM). I checked and the MD5 hashes of the resulting files are different too. When you unpack and repack an image, do the hashes match up?

Here are the commands I've been using:

./unpack-bootimg.pl boot-new.img
./repack-bootimg.pl boot-new.img-kernel.gz boot-new.img-ramdisk boot-new2.img

EDIT: Never mind, I was able to get it working with abootimg.
[Eee Pad Transformer Android Development] vit0oo:
.. ? yes i know, but i just use the archive ready to use and run ./flash.sh ...

i have try to run nvflash manualy ( without the flash .sh script ) i have flash successful on screen but always this error ..
[Eee Pad Transformer Android Development] Aerox912:
Still no luck, redownloaded both the bootloader and the rootfs, formatted microsd card and checked for errors or bad sectors, still nothing.

I'm now moving the rootfs to my microsd card from my phone to test if that works maybe..
[Eee Pad Transformer Android Development] Jedi223:
Same here.

microSD I had was brand new. Kingston 16Gb Class 10 :(

Edit:

microSD from my phone doesn't work either...

btw

In the line "mount -t vfat -o fmask=0000,dmask=0000,rw,flush,noatime,nodiratime /dev/$partition1 /sdcard" ,nodiratime isn't necessary, noatime has that function already. (not that this is going to solve the problem tho :) )

Oh and try using umask=0000 instead of fmask=0000,dmask=0000

I have no tools here atm to compile my own boot.img. Could you make a init which mounts the sdcard as ext2? Like to try if that solves the problem.
[Eee Pad Transformer Android Development] Aerox912:
Used a second microsd card now.

Now it says there is a difference between the boot sector and it's backup.

Now i really don't get it anymore.

I'm going to try the old bootloader see if that still works

EDIT: Ok weird **** is happening.

through cwm i made a ext2 partition and a swap on my microsd, and after I formatted the fat32 and copied the rootfs again, but this time booted into mac, before i was running on windows 7.

and all of a sudden it just boots..

Don't know if it has something to do with the ext2/swap partition i made on my sd. I'll delete them and see what happens.

EDIT2: Deleted ext2 and swap partition, still booting.

Only thing i can think that could be causing the problems is something that was wrong with my MicroSD or in my windows drivers for the apple card reader.
[Eee Pad Transformer Android Development] rdnetto:
Has anyone tried building the exportfs kernel module? (I'm trying to get XFS support working.) Whenever I try to load it with modprobe, it segfaults.

Actually, it looks like any module I build segfaults... :(
[Eee Pad Transformer Android Development] Jhinta:
First needs to be fat as windows needs it !! But i can put it on auto , ill will look if its still working then.

second Partition is mounted as auto .
[Eee Pad Transformer Android Development] Backwardsblade:
Apologies if this has been addressed, is option to boot from mmc limited to the tablet micro sd slot?

A dock SD card option could be beneficial for many users, as the rootfs is several GB and many may only use an 8 gb micro card. My questions are, (1) would this be possible in the first place and, if so, (2) what level of customization would be required? Lastly, (3) are there plans to boot straight from the internal memory that would make this not worth pursuing?

This is a very exciting move for this tablet, I'm very happy to see development like this. If I could utilize this often neglected dock SD slot that would be fantastic :).
[Eee Pad Transformer Android Development] MatthewJackal:
When I try to boot Ubuntu the boot sequence is looping all the time, every each time it says: "Reboot in 1 sec...".

What did I do wrong? Or what I should now? My device is not rooted.
[Eee Pad Transformer Android Development] rdnetto:
If the kernel detects the SD card slot, then you should be able to just replace mmcblk1 with mmcblk2 (or whatever it's called) in the init script (use abootimg [from the Ubuntu natty repositories] to extract and update boot-new.img). It would probably work. (To find out the name, plug in the SD card and see if any new devices turn up in /dev, or look at `tail /var/log/syslog`)

It doesn't seem worth it, though. Up to about 16 or 32 GB, microSD and SD cards are priced the same (e.g. Patriot class-10 16 GB is $35). Using a SD card would force you to leave the tablet docked, and when the dock battery runs out, the system would crash. (This is even more likely since we don't have a working battery meter yet.)

Using the internal memory will either mean repartitioning (risky) or a loop mount (hard since there's no yaffs2 kernel module in existence right now, and slower than directly mounting the partition anyway).

You're better off just using a microSD card. But even so, 8 GB is plenty for Ubuntu. A full install (ubuntu-desktop) usually takes up about 4 GB, and the provided rootfs uses half that. Even if you install a lot of large packages, you'll probably be under 6 GB. If you need the extra storage for documents/music/movies, then there's nothing stopping you from just plugging an SD card or USB drive into the dock, AFAIK.
[Eee Pad Transformer Android Development] ZerkerEOD:
Anyone willing to install there favorite c+ + compiler and IDE to see if it can write programs yet? I need this soon.
[Eee Pad Transformer Android Development] lilstevie:
I have been running on the internal, and there isn't that much risk to repartitioning the eMMC, just if you don't do it right you loose your dual boot ability without using a custom kernel mapped to the new mapping, or till you restore with nvflash
[Eee Pad Transformer Android Development] lilstevie:
I don't know if this is really that helpful, but everything that I have been using on the device that is not on the ubuntu repos I have been compiling, but as for IDE's I don't use one, I stick with vim or if I am feeling lazy nano/pico
[Eee Pad Transformer Android Development] rdnetto:
It was losing dual boot that I was referring to. On that note, how would you repartition it while preserving Android? I presume you'd have to shrink an existing partition somehow...

Given that the current installation doesn't even detect the partitions on mmcblk0, it seems kind of moot though.
[Eee Pad Transformer Android Development] Jedi223:
Weird **** indeed.

Did the same thing you described. Ubuntu boots like a charm :D
[Eee Pad Transformer Android Development] Backwardsblade:
Thanks for the in-depth answer, I asked because I had class 10 SD cards readily available and debated on whether or not to purchase a class 10 micro. From the sound of this thread, I may just hold off until internal becomes a more noob-friendly option.
[Eee Pad Transformer Android Development] Jhinta:
i will only enable internel is its faster then class 10 and when roomfs is done like touchpad working ( maby gui wifi) and bluetooth, because i can see all of the noobs formating there nands from ubuntu by miss type or what ever
[Eee Pad Transformer Android Development] Jhinta:
will be added in future
[Eee Pad Transformer Android Development] rdnetto:
From what I've seen, it's about the same, maybe slightly faster (not by much though). If you do know how to enable it though, could just mention the details here? It wouldn't be accessible to the noobs, but it would be useful to those of us working on other things. e.g. using the internal memory and micro SD card to form a RAID
[Eee Pad Transformer Android Development] salacc:
so, any plans yet for classic dual-boot?

I presume it can be done without much hassle using recovery partition for ubuntu kernel, though i dont have any particular idea how to do that :) Not that i didnt compile standard linux kernel alot in the past, just not sure what is the parition layout on transformer nor i have any clue what CWM recovery actually does when 'recovery' mode is chosen.

It doesnt look too hard, but i reckon i can be deluded :)
[Eee Pad Transformer Android Development] CelticWebSolutions:
I'm sat on the fence waiting for it. Be. The dogs dangles with duel boot!
[Eee Pad Transformer Android Development] ZerkerEOD:
So the programs are compiling right? I need it for a programming class this coming year, or I need to go out and buy a laptop
[Eee Pad Transformer Android Development] r2DoesInc:
i about **** my pants when i saw you were working on the lilstevie. i sold my tab right before you started working on ubuntu for the 7inch. i was pissed :(
[Eee Pad Transformer Android Development] Jhinta:
i already have that , but it will not mount the sdcard

its mounted like ,

mount -t ext2 /dev/block/mmcblk1p1 /sdcard

but doesnt work dir does not exist

looking add /sys/devices/xxxxxx..

the sdcard is there. is there a way to mount it from that?

? so is my makedev incorrect ?
[Eee Pad Transformer Android Development] lilstevie:
I will post instructions tonight, there is something major you are missing, give me a few hours to get acquainted with some of the caveats of the tegra 2. My transformer only arrived today
[Eee Pad Transformer Android Development] Kevincod:
Maybe silly but usually when mount gives the error that a directory does not exist, it is the mount point not the device. Have you tried mkdir /sdcard , then mount?

If /dev/block/mmcblk1 was missing, it would say "no such device", not "directory does not exist"
[Eee Pad Transformer Android Development] Jhinta:
yep :cool: its the same sript i use for my phone , think its still the makdev major thing . add work now cant test anything till tonight:(
[Eee Pad Transformer Android Development] lilstevie:
I don't mean to be an arse, but I will be booted by then :)

yes it is a makedev thing, but not in the way you think.

if you enable devtmpfs in your kernel config you do not need to maintain the devnodes yourself (the way it is meant to be) and also /dev/block does not exist outside of android.

the address you have been looking for is /dev/mmcblk*p*
[Eee Pad Transformer Android Development] Jhinta:
that makes sens , i will be happy to see it boot ready when i'm home :D
[Eee Pad Transformer Android Development] Jhinta:
tnx got it working , trying to fix xorg now
[Eee Pad Transformer Android Development] gnagnone:
are you saying that it's booting linux and the only missing thing is xorg??? if yes this is a great new!!!
[Eee Pad Transformer Android Development] lilstevie:
great to hear, I am a little tired and only just started compiling kernels lol
[Eee Pad Transformer Android Development] Jhinta:
i do realy know what you mean , it thakes a lot of time , man iḿ even compiling on a aspire one 751h thats like :eek::eek: sloooowwww

Trying to build a standard rootfs , as thee hd2 was locked and dont know loging info.

And to all , yes we got native ubuntu running but no desktop only cli xorg fails

i will but a boot.img pack for all to try , and help fixing things.

Rootfs is needed build your own or use hd2 file and mod it .

the only rootfs i will post is a working one !!!!!
[Eee Pad Transformer Android Development] brandon...:
It'd be great if you guys uploaded current codes and build environments as to get others working along side you. I know I would contribute if you got me up to speed on where you are now :)
[Eee Pad Transformer Android Development] Jhinta:
tools are in OP and you only need a rootfs download the hd2 rootfs or build one.

we have ubuntu working till login in , it oops out becuase of xorg needs to be setup.
[Eee Pad Transformer Android Development] brandon...:
oh i thought you guys had to do a lot more than just that to get to where you are now. Great, i'll flash over tonight when I get home and dig into xorg and see what I can find. Can you post any info on what you've found so far with failed xorg initialization?
[Eee Pad Transformer Android Development] Jhinta:
Whel actualy nothing , realy i need to sleep , tomarow ill will look again .

I was already glad whe had it booting
[Eee Pad Transformer Android Development] paow:
Glad to hear that you've come so far, its quite amazing what some people can do in so short time :eek:

Will anyone of you, lilstevie or Jhinta, work on dualbooting Ubuntu and Android once you get it running?
[Eee Pad Transformer Android Development] lilstevie:
I have looked at some preliminary work on porting u-boot, but that is a long way off, using the recovery partition we probably could, but that is at the sacrifice of losing recovery
[Eee Pad Transformer Android Development] plasmastrike:
But would you be able to flash back through nvflash in abd mode:confused:
[Eee Pad Transformer Android Development] commandersafi:
Yup. If it comes to using the recovery partition as Ubuntu then that just means you'll loose the ability to boot CWM. You would boot into Ubuntu by doing what you would normally do to get to CWM now (booting holding Vol. down then up when it tells you to)
[Eee Pad Transformer Android Development] lilstevie:
If you flash an alternative bootloader such as u-boot you will always be able to reflash a default system with nvflash in APX mode, I have already started testing bootloaders on te devices but it does need a bit of work, so far all i have is the code executing, nothing else
[Eee Pad Transformer Android Development] rdnetto:
I'd be cautious about removing CMW - if you get stuck in a boot loop, it's the only (reliable) way of getting out of it, AFAIK. Some kind of chainloader would probably work better.

Yes, they compile. Why haven't you just tried it instead of repeatedly asking?
[Eee Pad Transformer Android Development] belzebub40k:
Thats not right. We have access to bootloader with nvflash which is on a lower level as the recovery. Even if you are in a bootloop you can access APX mode to do a full reset.

I also like a chainloader much more I am playing around with kexec but hadn't any success. I'll keep trying.
[Eee Pad Transformer Android Development] Jhinta:
did you got it even booting with kexec enabled?
[Eee Pad Transformer Android Development] belzebub40k:
I have successfuly compiled a kernel with kexec and got it to boot. Even loading the kernel and initrd into RAM worked. But it freezed after I tried to execute the loaded kernel. Hadn't much time to test yesterday.
[Eee Pad Transformer Android Development] Jhinta:
can you share with me please , and what you did with kernel source
[Eee Pad Transformer Android Development] belzebub40k:
Just used the same kernel sources as you and added the following two lines to the kernel configfile (.config) which I extracted from your kernel (zcat /proc/config.gz).

CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y

after that I installed the package kexec-tools which gives you the tool kexec. According to many wikis and mailinglists kexec generally works for ARM achitechture.
[Eee Pad Transformer Android Development] Jhinta:
i think the problem your having is memory loading address

http://xdaforums.com/archive/index.php/t-1079097.html

http://www.ibm.com/developerworks/linux/library/l-kexec/index.html
[Eee Pad Transformer Android Development] belzebub40k:
As said I hadnt much time to test the kernel maybe i did something wrong. Will try more in a few hours. Thanks for pointing me to this thread hope this will help.

I think kexec would be a great benefit not only for booting linux also for android with multiple kernels (e.g. stock and overclocked) :D.
[Eee Pad Transformer Android Development] ZerkerEOD:
The only Internet access i have currently is my phone and if I screw up its going to be annoying having to download everything to fix it through my phone. So I am just doing research for when I get back to school where I will feel alot safer.
[Eee Pad Transformer Android Development] rdnetto:
OK, I finally figured out how to compile kernel modules. I'll post the instructions here for anyone who needs to add support for another file system, etc.

Note that if you load an incorrectly built kernel module, the system will not work properly until you reboot. If you install an incorrectly built module, you will have to format your SD card and re do the installation (unless you can remove it from the image). Do not attempt this if you do not understand what you are doing.

These instructions should be run on the Transformer while in Ubuntu.

Install build-essential and libncurses5-dev

Get the kernel source code from the first post and extract it. 'cd' to the root of the source

Download the FB patch from the first post and apply it by running 'patch -p1 < FB_path.patch'

Load the config used for the current kernel with 'zcat /proc/config.gz > .config'

Enable any modules you want built by running 'make menuconfig'

Also clear the value of General Setup->Cross-compiler tool prefix.

Build the code (takes ~10-15 min): 'make prepare && make -j2'

'cd' to the folder within the the source containing the module (e.g. ./fs/xfs)

Open a separate terminal and run 'tail -f /var/log/syslog'. This will tell you if there are any problems when your module loads. (You may want to remove extraneous output by piping it through sed and/or grep)

Check if the module has any dependencies you need to load first with 'modinfo xfs.ko'

(if it does, perform this step and the next for the dependencies first).

Load the module with 'sudo insmod xfs.ko'. Run 'lsmod' to check if it has loaded successfully.

Test the module's functionality. e.g. mount an XFS file system

If the module crashes at any point, you will need to reboot.

Do not proceed to the next step if your module is not working!

Go to /lib/modules and symlink 2.6.36.3 to 2.6.36.4. (The source code version differs from the version of the active kernel very slightly.)

Go into the folder of each module you have tested (e.g. src/fs/xfs) and run:

make -j2 -C /tmp/src M=$(pwd) modules

sudo make -j2 -C /tmp/src M=$(pwd) modules_install

sudo depmod -a #(this step may be unnecessary)

where /tmp/src is the path containing the kernel source code.

Add the names of the modules to /etc/modules.

Reboot

Note: the UDF and YAFFS modules do not work. UDF depends on a CRC module which isn't there (or maybe I'm not looking hard enough?), and the YAFFS code doesn't compile. You can get YAFFS working by deleting the folder, downloading a snapshot from the YAFFS GIT repository (see yafffs.net), and running the kernel patch script in it. However, this isn't enough to mount mmcblk0 - I think you need to manually provide a partition table some how.

EDIT: The difference in the version numbers means that the kernel will be unstable and prone to crashing. Avoid using these instructions for now.
[Eee Pad Transformer Android Development] belzebub40k:
I think the branch ASUS_OFFICIAL is not the one Jhinta used for his kernel. You may run into problems using modules for a different kernel version.
[Eee Pad Transformer Android Development] rdnetto:
It was the one he linked to, so I figured they should match up. Plus, they all seem to working fine so far. At any rate, it's only a difference in the build number, so I imagine the interfaces between the various components should be the same. Then again, I know next to nothing about how the kernel actually works...
[Eee Pad Transformer Android Development] belzebub40k:
I know that he linked to this git branch, but his compiled kernel is definitely 2.6.36.4 and not 2.6.36.3. As I have a bit experience in compiling linux kernels for my desktop systems I can say that I had problems with modules for different kernel version.

I dont think we should compile kernel modules this way if we have the ability to use the right sources.
[Eee Pad Transformer Android Development] almaalma74:
totally waste of time... good luck
[Eee Pad Transformer Android Development] rdnetto:
Well, mine just crashed. Looks like you were right after all.

So, which source is the right one then?
[Eee Pad Transformer Android Development] belzebub40k:
I think patch8445 or patch8445_rev is the right one. I don't know what _rev mean.
[Eee Pad Transformer Android Development] Jhinta:
my bad , iḿ trying diff kernels , so totaly forgot the modules , i will add them today
[Eee Pad Transformer Android Development] Jhinta:
uploading to git hope this will go oke as itś my first git.
[Eee Pad Transformer Android Development] belzebub40k:
This would help a lot. No more guessing which kernel you are using.
[Eee Pad Transformer Android Development] Jhinta:
https://github.com/Jhinta/Asus-TF101-GNU-Linux

boot.img will be recompiled to make sure its this kernel , and modules.zp will be added ( compiling !! )
[Eee Pad Transformer Android Development] rdnetto:
If anyone's working on the problem with the speakers, take a look at the output of

'amixer'. It might be a useful starting point.
[Eee Pad Transformer Android Development] rdnetto:
I've remapped the keyboard to something a little more usable - just copy the file to /etc/X11/Xmodmap and restart X.

If you're using KDE, the other 2 files will add equivalent functionality for Super+F_ - import them in System Settings -> Global/Custom Shortcuts.

Modified Keyboard Layout:

Top Row: [Esc] [F1] ... [F16]

Bottom Row: [Ctrl] [Fn] [Super] [Alt] [Space] [Alt] [Del] [Ctrl]
[Eee Pad Transformer Android Development] belzebub40k:
Nice one! Are you also planning to remap the keys on the console?
[Eee Pad Transformer Android Development] Jhinta:
tnx i will test it and add it to rootfs

about touchpad it seems the driver is build for andoid .

/kernel/drivers/input/asusec/elan_i2c_asus.c if we want touchpad this is the file we need to mod.

about the sound output i did try some of those setting , but correct me if i iḿ wrong , i thing the speakers is enabled when there is a config file for that , trying to find out what that is.
[Eee Pad Transformer Android Development] belzebub40k:
Nearly every function of the touchpad works fine. The only problem is that you have to use two fingers to move the courser. Also tap to click with one (left click) or two (right click) fingers works. Yust waiting for BlueDragonX (developer of the mtrack driver) two answer mmy question what we can du to change this behaviour.

EDIT: found this little tool: https://wiki.edubuntu.org/DebuggingTouchpadDetection/evtest

May be helpful in determinating whats wrong with the touchpad events.
[Eee Pad Transformer Android Development] vit0oo:
I have again the same error with the new boot.img ...

I forget something ?
[Eee Pad Transformer Android Development] Jhinta:
did you installed the latest rom like prime 1.6 aka (8.4.4.11) ? because i have and i cant get ramdisk working again , and tryed many kernels with default setting .

i can still boot it with native partition. have to look into this
[Eee Pad Transformer Android Development] rdnetto:
Hey, it looks like the current linux flashing script is corrupt. The MD5 matches, but nvflash segfaults under 64-bit linux (worked fine before). Flashing the images with the nvflash in the previous version works, but the transformer won't boot.

I tried before, but they weren't producing any output on 'showkey -s', so I wasn't sure how to go about remapping them. I'll try again once I have the 'right' kernel, and post back if I get anywhere.

There is a workaround to access the consoles though: F3,F6 and F9 (under my remapping) are normally mapped to F2-F4 in the console, so you can use the Alt+Ctrl on the right side with one of those to enter one. 'chvt 7' will return to the X console (it also works from within an X terminal emulator, but requires root).