yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
that would be UDA that you mean there, UBT is added for ubuntu
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Oops, my bad. While I've got you, you wouldn't happen to have any ideas about that kernel panic I mentioned earlier, would you?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
Thank you for the great explanation. But you advise only to use the partition with user data. However, I don't want to install Android from start. I would prefer to have 0-loss. (even the system files)

Isn't that possible ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
It is, but I don't see why you'd want to. You can achieve it by creating a full backup then overwriting some of the files with the ones from the flashkit (incl. linux.img, which has to be generated with abootimg), and resizing UDA to match the new layout.

IMO, there's no point in going through the effort of backing up the system files since they get overwritten anyway when you update to the latest version of Prime ROM/stock Android/etc. It's just additional work. If you want to avoid going through the configuration process that's covered by the settings, and existing applications are stored in a separate partition again, but I really don't see the point in preserving Android itself.
[Eee Pad Transformer Q&A, Help & Troubleshooting] megacoolrock:
i need help with the wpa supplicant, ive tried to do this and i saw a guise for transformer ubuntu, but it was the wrong format, can anyone give me a sudo command or something that will work? the connection i have is a wep
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
thank you.

what is the tool to use for creating a full backup ? (is it nandroid or something else ?)

also, what shall I use for resizing the partition ?

I have :

system.img

data.img

cache.img

on my nandroid backup...
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
yeah, it is a change in the way the ramdisk is handled, it is specific to jhintas initrd for some reason
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
OK, so how do I get an initrd that works with your kernel? Is there some script or command I need to run?

Ok, that should be fine. Run the flash kit, then restore the nandroid backup and you should be fine.

I don't know if you'll need to resize the partition file, since I'm not familiar with how nandroid works. Try it without the resizing and see if it works.

In case you do, here're the instructions:

Use resize2fs then dd to create a copy of the file without the uneeded zeros at the end.

e.g. if you've used resize2fs to reduce it to 4 GB, then 'dd if=original.bin of=smaller.bin bs=1G count=5' (while you probably only really need count=4, I prefer to go a little over in case there's some overhead).

Note that once the file has been restored to the transformer it'll only be 4GB until you use resize2fs under Ubuntu to expand it to fit all available space. This can be avoided by only shrinking it to the new size of the partition instead of the smallest possible size, but increases the amount of time it takes to restore the backup.

(This has to be done under Linux because Windows doesn't understand Linux filesystems).

I'd suggest upgrading to WPA since WEP is extremely insecure, but here're some general instructions on wpa_supplicant and here's an example of how to do wep.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
can you post the bootimg that you are having issues with
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
See attached.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
if that is a boot.img it is amazing it even goes that far, the bootimg is fubard
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
Please excuse me if I'm sounding too novice.

I didn't understand how this works; how will I know which partition file to resize (if it needs to be resized) ?

How can I understand if nandroid needs resizing before I restore ?

Also, I have a few questions before doing that operation and taking the risk of losing my Android ROM:

1. how shall I update Android rom once I have dual boot ? (How to gointo recovery)

2. is there a windows toolkit to use under Windows ? (I only have Linux setup under my VMware environment, would that work with the Linux toolkit ?)

3. Once I have Ubuntu running, shall I be able to upgrade to latest Ubuntu (11.10) ?

Thank you sir...
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Odd, I just used abootimg with the same commands as in the flashkit. We are talking about the file inside zip, right? I ran it on the netbook, but it shouldn't make that much difference...

I've been using the latest copy of abootimg from the git, so I don't think it's that..

0. If none of the files are >5GB, just skip the resizing step. If they are, the biggest is the one to resize.

1. Recovery/CWM works the same as always. It's actually used as an (interim) boot manager.

2. There's a Windows flashkit, and you can use the copy of nvflash included to do backups, etc. if you convert the .sh files into .bat ones. (This is only possible for simple scripts like the backup.)

I'd suggest trying to make it work with the Linux one though (either through the virtual machine or with a live CD) since I had no end of problems getting the drivers for nvflash to work under Windows.

3. You can, though I haven't tried it. To be perfectly honest, you're probably better off just installing 11.10 now. To do so, create an image with rootstock and use it as the root filesystem. After that run the driver injection script, get wifi working, then run 'apt-get install ubuntu-desktop'. (alter as required if you prefer a different desktop environment). Keep in mind you'll need to do all that in the terminal, since until you install it there won't be a GUI.

Alternatively you could use the official rootfs for Tegra 2 systems. That would be a lot easier, but AFAIK no-one's tested it with the transformer yet. Since there are some differences between the systems, I don't know how that would turn out.

For reference, here's the command to create a new root filesystem:

sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
yeah that was a mybad, was using the wrong tool, however I can confirm that your initrd is buggered

lilstevie@lilstevie-VirtualBox:~/android_linux$ file initrd.img.gz
initrd.img.gz: gzip compressed data, from Unix, last modified: Tue Jul 26 14:04:33 2011
lilstevie@lilstevie-VirtualBox:~/android_linux$ gunzip initrd.img.gz

gzip: initrd.img.gz: unexpected end of file
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Ah, so that's how you test it. My original copy of the initrd had gotten corrupted (not sure how), which explains why none of my attempts were working. Redownloading the flashkit fixed it. Thanks for that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
what is "driver injection script" and where can I find it ?

also where can I find rootstock ?

edit: Ok; I got rootstock. But I still don't know what driver injection script is...

problem with rootstock:

root@ubuntu:~/tf/rootfs# sudo rootstock -f TF101 -l user -p mypassword --seed build-essential,openssh-server,nano,aptitude --imagesize 8G --components main,restricted,multiverse,universe --notarball -m http://ports.ubuntu.com/ubuntu-ports -d oneiric

I: Running on a i686 machine

Your debootstrap installation does not seem to have support for the oneiric distribution

root@ubuntu:~/tf/rootfs#
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Driver injection script is in the flashkit.

Are you running rootstock on a 11.10 installation?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
no. I have an old ubuntu installation on VMware.

ubuntu 10
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Try running it off a 11.10 live cd (or installation).
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
no other way ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Regarding kernel patches, I noticed that there are a lot of error messages during bootup regarding the Apparmor 2.4 compatibility patches with the kernel from linux_kernel_TF101. This seems to fix the problem, but I'll leave it to someone who knows what they're doing to commit it to the repo.

Also, a note to anyone who uses the patched kernel: you need to disable the network manager (it's in init.d) to connect with wpa_supplicant).

Honestly, I haven't done it myself - that's just what I'd try. I can't imagine that running a live cd image would take too much effort though.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok; I've downloaded a vmware image for 11.10 and it's working now.

installed rootstock and creating rootfs with the command you've suggested.

I assume the output of this will be an ubuntu.img file to be used with the toolkit and I won't need to use the ubuntu.img given in the first/second post of this thread ?

about the driver injection script, which file is that ?

inject-firmware.sh ?

when shall I run it ? in APX mode juyst after the flashing of Ubuntu ?

edit:

this is an 8GB image , will it fit ?

-rw-r--r-- 1 root root 8589934592 2011-10-23 15:54 qemu-armel-201110231514.img

wtf ?

sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
./images/ubuntu.img is too large for partition
command failure: create failed
root@ubuntu:~/tf/toolkit#
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
After sending the system.img , the script hangs on sending ubuntu.img :

root@ubuntu:~/tf/toolkit# ./flash-linux-android4.sh
reading config file ./ubuntu/bootcfg/bootimg.cfg
reading kernel from ./ubuntu/zImage
reading ramdisk from ./ubuntu/initrd.img
Writing Boot Image linux.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x037c7043424162d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0

sending file: ./images/transformer.bct
- 4080/4080 bytes sent
./images/transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: UBT
creating partition: SOS
creating partition: LNX
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 UBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
sending file: ./images/ubuntu4.img

What is wrong with my setup ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Danzano:
sending file: ./images/ubuntu4.img

[/code]

What is wrong with my setup ?[/QUOTE]

I cant see anything wrong you sure you where not just being impatient i have a quad core laptop and it still took a good 20mins to complete the transfer it is a big file and nvflash communication isnt the quickest
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok; I might be a little impatient, but the counter for sending bytes did not even show up.

in the previous step system.img is being sent and the counter goes through from 0 to 500M.

When sending of the ubuntu.img began, the counter did not start.

And I'm not using the standart rootfs; it's a self created rootfs with rootstock. So I thought there might be something wrong.

Any ideas ?

When should I expect to see the counter ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Yes, yes, and after Ubuntu has been booted.

You'll need to modify your .cfg file to increase the size of the Ubuntu partition. You can either use the one I posted a while ago (if you have a 32 GB drive) or read lilstevie's post on how to edit the file (it's not as simple as you'd think).

It'll take a bit less than an hour to copy, but you should see some feedback indicating that it is.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
no it is too big, nvflash will not transfer an image any larger than the image I posted, that is the maximum allowable transfer size.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
plug headphones in
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Oops, I forgot about that.

@mrmrmrmr, run resize2fs on it to shrink it down then try again. Once it's written to UBT, I think you can use resize2fs under Android to expand it (UBT is mmcblk0p8).

Corrected.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
I'm sorry ; I didn't understand.

So, a 8GB image is too big. Then I have to resize it (to what size ? - can you give the example command for that ?)

On the cfg file what size shall I write for the UBT partition ? What is the correct way of calculating that ?

After written to UBT, on android what command I have to use for expanding ?

what if I don't need a 8GB partition ? For example, can I use a 5GB img file ?

---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------

on which page can I find that post of lilstevie's ?

what should I expect to see on screen when copying the file to UBT ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Here's the post on nvflash partitioning. That'll tell you everything you need to know about setting the size.

5 GB should be fine, 4 GB just seems to be a tad too limited to install many programs. It doesn't matter what size the generated image is, since you'll be shrinking it with resize2fs anyway. The partition just needs to be big enough to hold it.

The partition size isn't that much of a problem as long as it's big enough to hold all the programs you install, since you can easily access the Android files from Ubuntu and vice versa.

The command to run under Android is 'resize2fs /dev/block/mmcblk0p8'. You need to run it as root.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
well 4GB is the largest for the purpose of nvflash, that is the only reason I have 4GB set in the default image. personally I use 6GB or more, at the moment I have 7.5GB for ubuntu, but my dualboot is ubuntu/meego and not ubuntu/android.

also the kernel is compiled with live resize so resize2fs can be invoked from the booted ubuntu, and infact in the next version of the rootfs (oneiric based) it is done on the first boot.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
Hi,

Thanks for your answers. But there's still something I didn't understand well.

Please correct me if I'm wrong:

- I will create a new ubuntu.img with 4 GB size (please tell me if parameter 4G for rootstock is fine)

- I will have to arrange UBT partition size as 5GB (arrange the UBT size accordingly. do you have a suggestion for that)

- I will resize the image from android environment after I boot Android.

is that correct ?

why did I have problem sending the ubuntu.img to UBT part ?

should I expect to see any sign of sending it on console ? (counting of bytes)

btw, I had tried to create a 4G image with rootstock but that failed as well (stuck at sending)

Do I have to go through the kernel compile process on post 1022 (http://xdaforums.com/showpost.php?p=18709367&postcount=1022) ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
nvflash is very very poorly coded. anything over the max transfer size just dies, no error, no anything. the problem you had sending ubuntu.img has just been explained, an image over 4GB cannot be transfered.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok; but how will I create an image within the limits ?

is the parameter 4G fine for this ?

or should I use 4000M ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok;I've found the correct value (4000M) with trial and error (took a lot of time)

now my image is being sent. after the flash, how can I go to recovery ? (I want to try restoring my nandroid backup)

do I have to flash recovery ?

if I flash my previous recovery how can I boot ubuntu ?

btw, are you sure that there is "resize2fs" command under Android ? Where can I find it if there is no resize2fs ?

thx.

edit:

this time I'm stuck at sending the linux.img:

sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
sending file: ./images/system.img
/ 536870912/536870912 bytes sent
./images/system.img sent successfully
sending file: ./images/ubuntu41.img
/ 4194304000/4194304000 bytes sent
./images/ubuntu41.img sent successfully
sending file: linux.img
[Eee Pad Transformer Q&A, Help & Troubleshooting] aldur999:
Ok I did it, but I cannot get it pass the eeepad logo screen. Everything seemed to be fine, how can I investigate further?

EDIT:

And, why not to post the "default and updated" compiled kernel blob? Wouldn't it be easier?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rayko:
Hi, I want to try this to have ubuntu on my transformer. However, I read on other forums that nvflash depends on the serial number of the device, and some nvflash versions won't work on B70+ devices, since the security on boot was changed on newer devices. The procedure for installing ubuntu uses nvflash, right? So, does it work for devices with S/N B70+? Anyone succeded on those devices?

If I need a specific nvflash version, should I modify something on the flash kit to update the nvflash version it uses? (ie replacing the nvflash file)

Finally: for using a specific android rom (dual booting), should I modify the flash-linux-android.sh to point to it?

By the way, this is the first time I try a serious mod on a mobile device. The restore method needs a rom file (original rom) to restore the device to factory settings or the device has somewhere the original rom stored?

After I figure out how to backup everything, I'll put hand to work and try this.

Thanks

Edit: Well, I read a bit further and found a way to check if nvflash can be used on the device on http://xdaforums.com/showpost.php?p=16356361&postcount=50

I just finished the flashing to install ubuntu plus Prime 1.6 on dual boot mode. Both systems started well and no errors so far. The only thing is that during the setup of ubuntu, the touchpad of the dock doesn't seem be working. I'll look into this later, but has someone had a similar issue? I'll add the tegra repositories suggested somewhere on this thread to see if that can fix the problem (maybe some driver).
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
ok.

I got it !

rootfs installed on p8 and resized as recommended.

but driver injection doesn't work.

I try it when ubuntu is booted.

but "adb" command says device not connected.

----

Ok; I got the firmware files by other methods.

but now "modprobe -r bcm4329" gives this error:

FATAL: Could not load /lib/modules/2.6.36.3-tegra-transformer-wifi/modules.dep: No such file or directory

What shall I do ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Rayko:
Hi again. I've been doing more reading about the project (I have so many tabs on my firefox now). As many here had the wifi issue, I just wanted to confirm that the wpa_supplicant method works and I would like to share the configurations for a wep shared network.

Following the tutorial by belzebub40k Here I just digged a bit on wpa_supplicant file parameters and managed to make my network work.

Pretty much my configuration is this:

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1

network={
ssid="NameOfAp"
scan_ssid=1
key_mgmt=NONE
auth_alg=SHARED
wep_tx_keyid0=0
wep_key0="Your key"
}

Saving that to a file called wpa_supplicant.conf on /etc/wpa_supplicant/, then run the command

sudo wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant/wpa_supplicant.conf

Finally get an ip:

sudo dhclient wlan0

I'm not sure why, but I've seen some people using eth0 instead wlan0, maybe some old configuration, but be sure to check the proper interface.

Hope this helps someone. Check links below for more info on wpa_supplicant parameters.

Sources:

http://xdaforums.com/showpost.php?p=15528059&postcount=252

http://linux.die.net/man/5/wpa_supplicant.conf

http://leaf.dragonflybsd.org/cgi/web-man?command=wpa_supplicant.conf&section=5

So far, I think I'm done with the ubuntu on my transformer. After making the wifi work I can breath and use my ubuntu. No touchpad so far, but that can wait, I can use a wirless mouse menwhile. I'll add the repository to see if there are updates. Anyway, now I have my tranformer just as I wanted to.

Thanks to all the devs for the hard work on this one.

By the way, are there any plans to release a clean img in the future with all the patches? or we just apply patch by patch until everything works?
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
If I posted the binary, it would only be a matter of time until it was outdated, and I'd have to support it. (I'm guessing this is why lilstevie didn't post it either).

If it freezes at that stage, then it sounds like there's something wrong with the kernel. I'm no expert, but I'd suggest redownloading the source and following the compilation steps carefully.

Also, make sure you're using the abootimg I suggested, not the one in the Ubuntu repos (it's buggy).

sudo depmod -a

The touchpad doesn't work in the default kernel. You have to recompile the latest copy of the kernel source to get it to work. Refer to the instructions I posted a few days ago.

The missing functionality is all driver related, so the rootfs is irrelevant. There's no need to go looking for individual patches, they've all been tested and merged into lilstevie's git, which is referred to in the instructions I posted.
[Eee Pad Transformer Q&A, Help & Troubleshooting] lilstevie:
The reason I haven't posted it as an actual update is based off the fact that;

1) If you want the update you can build it from source.

2) There is not enough to call it update worthy.

3) The aforementioned random freezes.

4) I am working on bringing over the 2.6.38 kernel that muromec ported.

The rootfs is patched, but only minor, I believe he is referring to the firmware injector script,

If that is what he means, the reason it isn't included is copyright. I do not have the licence to redistribute the Broadcom IP.
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrmrmrmr:
I did that; now it says "module not found" for bcm4329

I tried copying it from the Android partition. It accepted the "modprobe -r bcm4329" command, but this time "modprobe bcm4329 iface_name=wlan0" failed:

Unknown symbol in module, or unknown parameter.
[Eee Pad Transformer Q&A, Help & Troubleshooting] rdnetto:
Post the output of 'modinfo bcm4329'.

Also, are you using the stock kernel?