[Q&A] Ubuntu on the Transformer (eMMC install)

rdnetto · Feb 21, 2012

BTW, I fixed the audio (the speakers work properly now). It requires a kernel patch, so you can either wait until the next stable release or grab the patch from the dev thread (hopefully lilstevie will merge it into the git soon) and compile it yourself.

CaffeineHead · Feb 22, 2012

So I just found the ac110 has multiboot working. I dont fully understand the asus bootloader howver so I dont know how practical or feasible it is to implement this on the tf.

They have a wiki page explaining it at ac100.grandou.net/multiboot

marshallladd · Feb 22, 2012

Is there anyway to OC the CPU in Ubuntu? In android i run prime at 1.6Ghz, Ubuntu is stuck at 1.0.

Jazztrmpter · Feb 22, 2012

12.04 Upgrade

Hey guys,

I was attempting to update to 12.04 again this morning, and I almost suceeded except for the end when I accidentally clicked to "keep" the 'no-longer needed' packages. I didn't run into the libgtk or unity error like I did last time. I was having some issues with gedit not opening via terminal so I removed it and also the Ubuntu Desktop something went with it during the uninstall. Upgrading to 12.04 seemed to work after that.

Now, when I boot into ubuntu, the screen flashes like it does if you press the lock button, where it flashses code, then back to the desktop. Now I have to reflash my TF again. This got me wondering though... Can I flash 12.04 directly with OLiFE?

shaola · Feb 22, 2012

Jazztrmpter said:
Hey guys,

I was attempting to update to 12.04 again this morning, and I almost suceeded except for the end when I accidentally clicked to "keep" the 'no-longer needed' packages. I didn't run into the libgtk or unity error like I did last time. I was having some issues with gedit not opening via terminal so I removed it and also the Ubuntu Desktop something went with it during the uninstall. Upgrading to 12.04 seemed to work after that.

Now, when I boot into ubuntu, the screen flashes like it does if you press the lock button, where it flashses code, then back to the desktop. Now I have to reflash my TF again. This got me wondering though... Can I flash 12.04 directly with OLiFE?

Yes, you can. You have (at least) two options, you can loop-mount ubuntu.img and chroot and upgrade and you can also loop-mount delete everything and install by debootstraping 12.04 directly, but this one would need more work to tweak up everything like i describe in the other thread where i put the example with debian.

I think the esaiest way is to upgrade.

Asuming you have a linux enviroment in your computer (virtual or native, or even livecd, it doesn't matter) make a copy of ubuntu.img (just in case something goes wrong to be able to repeeat or just keep the older one, but you can always redownload it)

(i asume you are in the folder were you have the copy of ubuntu.img and it's also named ubuntu.img)
then mount-loop in some folder, for example:

create folder

Code:

mkdir target

mount the image

Code:

sudo mount -o loop ubuntu.img target

you have to install qemu-user-static in order to be able to chroot to another architecture enviroment:

Code:

sudo aptitude install qemu-usr-static

and copy the correct binary

Code:

sudo cp /usr/bin/qemu-arm-static target/usr/bin

you may need to mount proc and sys and if you don't mount dev before chroot you won't have /dev/pts and you will get some warnings but they don't mean any problem it's just anoyin

how to mount dev before chroot:

Code:

mount --bind /dev target/dev

EDITED: trick to have enough space and all packagaes needed for upgrading outside the image, so you will have enough space and if you repeat this process you will already downloaded all packages so the upgrade will be much faster

create another folder named temp:

Code:

mkdir -p temp/partial

(partial is a folder needed inside /var/cache/apt/archives)
and then mount it over apt cache folder

Code:

sudo mount --bind temp target/var/cache/apt/archives

/EDITED
and now you can chroot:

Code:

sudo chroot target

mount proc and sys inside chroot

Code:

mount -t proc proc /proc

Code:

mount -t sysfs sysfs /sys

now you can upgrade, but you don't have desktop enviroment so you will have to upgrade in the "server" way

install update-manager-core

Code:

sudo apt-get install update-manager-core

you may need to edit /etc/update-manager/release-upgrades and set Prompt=normal . I don't know it's been a long time since i haven't use ubuntu

and then upgrade:

Code:

sudo do-release-upgrade -d

now unmount proc and sys:

Code:

sudo umount /proc
sudo umount /sys

and exit chroot

Code:

exit

and now unmount dev and aptcache folder

Code:

sudo umount target/dev

Code:

sudo umount target/var/cache/apt/archives

i think i haven't miss anything. Let me know if you have any problem.

EDIT: sure, you should remove all downloaded deb packages for the space (sudo aptitude clean) after finished ONLY IF YOU DON'T DO /varr/cache/apt/archives trick descrived below Because if you mount --bind an external folder it won't affect the original ubuntu.img and you will have all those deb packagess already download if you make another attemp so you will save time downloading things.

And another important thing:

I don't know how much free space is in that image so before upgrading execute df -h to see if you will have enough space to upgrade (i think before attempting the upgrade update-manager will tell you i need to download XXXMb or something like that

if you don't have enough space you can mount --bind another partition/folder/filesystem to give more space to do it, like you mounted /dev

for example, if you have linux installed and enough space in the folder you are working create another folder named temp:

Code:

mkdir -p temp/partial

(partial is a folder needed inside /var/cache/apt/archives)
and then mount it over apt cache folder

Code:

sudo mount --bind temp target/var/cache/apt/archives

now you will have all the space you had in your home folder aviable inside the chroot enviroment located in /var/cache/apt/archives were deb packages are downloaded for the upgrade. Remember you have to do this outside chroot enviroment, if you already are inside open another terminal to do it without exiting:

and remember also to unmount everithing after finished.

braernoch · Feb 22, 2012

You might be able to chroot into the mounted OLiFE ubuntu rootfs from /images, upgrade to 12.04, and flash that. Just watch the size of the image.

Or create your own rootfs from 12.04 and inject initrd, modules, etc. But that would get messy.

It is possible. It's likely not easy.

Sent from my HTC Vivid using Tapatalk

shaola · Feb 23, 2012

braernoch said:
You might be able to chroot into the mounted OLiFE ubuntu rootfs from /images, upgrade to 12.04, and flash that. Just watch the size of the image.

I think that's the easiest way, the size of the image is not going to change, so that is not a problem to nvflash later. The problem could be if there is not enough space to make the upgrade, but bind-mount is the solution as i explained in the previous post

Jazztrmpter · Feb 23, 2012

shaola said:
I think that's the easiest way, the size of the image is not going to change, so that is not a problem to nvflash later. The problem could be if there is not enough space to make the upgrade, but bind-mount is the solution as i explained in the previous post

So all both of these methods do is modify the ubuntu.img included in OLiFE to upgrade to 12.04?

shaola · Feb 23, 2012

Jazztrmpter said:
So all both of these methods do is modify the ubuntu.img included in OLiFE to upgrade to 12.04?

well, not exactly, as braernoch said you can make from scrach your own image, that would be debootstrap option, but i just said to mount ubuntu.img and delete everything inside instead of create your own image file just because i thoug it would be easier for an unexperienced user and you will be sure that the image size will fit later with nvflash.

So you are correct, one option upgrade ubuntu.img and the other one build your own one.

Build your own image is kind of messy as you said, you will have to inject things, modify fstab and those things. I already described the process in another thread. If you haven't read it i recommend you to do it. It may be interesting if you like those things

EDIT: when i say you i meaned braernoch

Jazztrmpter · Feb 23, 2012

shaola said:
I think that's the easiest way, the size of the image is not going to change, so that is not a problem to nvflash later. The problem could be if there is not enough space to make the upgrade, but bind-mount is the solution as i explained in the previous post

shaola said:
well, not exactly, as braernoch said you can make from scrach your own image, that would be debootstrap option, but i just said to mount ubuntu.img and delete everything inside instead of create your own image file just because i thoug it would be easier for an unexperienced user and you will be sure that the image size will fit later with nvflash.

So you are correct, one option upgrade ubuntu.img and the other one build your own one.

Build your own image is kind of messy as you said, you will have to inject things, modify fstab and those things. I already described the process in another thread. If you haven't read it i recommend you to do it. It may be interesting if you like those things

EDIT: when i say you i meaned braernoch

Okay, great. I'll probably try the easier one since it's still all new stuff to me. You probably already have figured out from before that I'm not that great at making huge changes. But hey, one thing at a time.

shaola · Feb 23, 2012

Jazztrmpter said:
Okay, great. I'll probably try the easier one since it's still all new stuff to me. You probably already have figured out from before that I'm not that great at making huge changes. But hey, one thing at a time.

Don't worry, if you follow my instructions it will be easy. let me edit a couple of things before attemting this. i'll let you know in a couple of minutes

Jazztrmpter · Feb 23, 2012

shaola said:
Don't worry, if you follow my instructions it will be easy. let me edit a couple of things before attemting this. i'll let you know in a couple of minutes

Awesome, thanks a lot!

Sent from my iPhone using Tapatalk
ASUS Transformer tf101 32gb + dock.

shaola · Feb 23, 2012

Jazztrmpter said:
Awesome, thanks a lot!

Sent from my iPhone using Tapatalk
ASUS Transformer tf101 32gb + dock.

Ok, now i think it's finished, i haven't omitted anything asuming you would now it, so it should work just copy/pasting commands, but please, read the explanations, i really don't like this kind of howtos. It's better to understand what you are doing and if you find any problem you will be able to ask better for fastest solutions.

Jazztrmpter · Feb 23, 2012

Okay, I don't think I will get to it tonight, but I'll let you know if anything comes up tomorrow, and how it works out.

Sent from my iPhone using Tapatalk
ASUS Transformer tf101 32gb + dock.

tophermackay · Feb 23, 2012

Chromium web Browser

Has anyone had problems where the browser shows the address bar but nothing in the page its just white?

Jazztrmpter · Feb 23, 2012

shaola said:
Yes, you can. You have (at least) two options, you can loop-mount ubuntu.img and chroot and upgrade and you can also loop-mount delete everything and install by debootstraping 12.04 directly, but this one would need more work to tweak up everything like i describe in the other thread where i put the example with debian.

I think the esaiest way is to upgrade.

Asuming you have a linux enviroment in your computer (virtual or native, or even livecd, it doesn't matter) make a copy of ubuntu.img (just in case something goes wrong to be able to repeeat or just keep the older one, but you can always redownload it)

(i asume you are in the folder were you have the copy of ubuntu.img and it's also named ubuntu.img)
then mount-loop in some folder, for example:

create folder

Code:

mkdir target

mount the image

Code:

sudo mount -o loop ubuntu.img target

you have to install qemu-user-static in order to be able to chroot to another architecture enviroment:

Code:

sudo aptitude install qemu-usr-static

and copy the correct binary

Code:

sudo cp /usr/bin/qemu-arm-static target/usr/bin

you may need to mount proc and sys and if you don't mount dev before chroot you won't have /dev/pts and you will get some warnings but they don't mean any problem it's just anoyin

how to mount dev before chroot:

Code:

mount --bind /dev target/dev

EDITED: trick to have enough space and all packagaes needed for upgrading outside the image, so you will have enough space and if you repeat this process you will already downloaded all packages so the upgrade will be much faster

create another folder named temp:

Code:

mkdir -p temp/partial

(partial is a folder needed inside /var/cache/apt/archives)
and then mount it over apt cache folder

Code:

sudo mount --bind temp target/var/cache/apt/archives

/EDITED
and now you can chroot:

Code:

sudo chroot target

mount proc and sys inside chroot

Code:

mount -t proc proc /proc

Code:

mount -t sysfs sysfs /sys

now you can upgrade, but you don't have desktop enviroment so you will have to upgrade in the "server" way

install update-manager-core

Code:

sudo apt-get install update-manager-core

you may need to edit /etc/update-manager/release-upgrades and set Prompt=normal . I don't know it's been a long time since i haven't use ubuntu

and then upgrade:

Code:

sudo do-release-upgrade -d

now unmount proc and sys:

Code:

sudo umount /proc sudo umount /sys

and exit chroot

Code:

exit

and now unmount dev and aptcache folder

Code:

sudo umount target/dev

Code:

sudo umount target/var/cache/apt/archives

i think i haven't miss anything. Let me know if you have any problem.

EDIT: sure, you should remove all downloaded deb packages for the space (sudo aptitude clean) after finished ONLY IF YOU DON'T DO /varr/cache/apt/archives trick descrived below Because if you mount --bind an external folder it won't affect the original ubuntu.img and you will have all those deb packagess already download if you make another attemp so you will save time downloading things.

And another important thing:

I don't know how much free space is in that image so before upgrading execute df -h to see if you will have enough space to upgrade (i think before attempting the upgrade update-manager will tell you i need to download XXXMb or something like that

if you don't have enough space you can mount --bind another partition/folder/filesystem to give more space to do it, like you mounted /dev

for example, if you have linux installed and enough space in the folder you are working create another folder named temp:

Code:

mkdir -p temp/partial

(partial is a folder needed inside /var/cache/apt/archives)
and then mount it over apt cache folder

Code:

sudo mount --bind temp target/var/cache/apt/archives

now you will have all the space you had in your home folder aviable inside the chroot enviroment located in /var/cache/apt/archives were deb packages are downloaded for the upgrade. Remember you have to do this outside chroot enviroment, if you already are inside open another terminal to do it without exiting:

and remember also to unmount everithing after finished.

Turns out I'm staying up a little extra past normal to get this done...I was just too interested. So far the only thing not the same was installing qemu. The command did not find the package, so I installed qemu-kvm-extras-static from synaptic pm. It mentioned ARM user mode so I hope that will be fine.

I will update any differences/obstacles along the way.

EDIT

Okay, ran into something... when trying to chroot, I get this error. I am going to try installing the main qemu package.

Code:

root@bt:~/Documents# chroot target
qemu: fatal: cp15 insn ee1d7f70

R00=4009f960 R01=00000852 R02=000150e8 R03=0d696914
R04=0001d7cc R05=0009ff58 R06=000153e8 R07=00000000
R08=00000000 R09=000a005c R10=4009f000 R11=00000000
R12=000a005c R13=4007f5d0 R14=42090e80 R15=4008b062
PSR=20000030 --C- T usr32

Installing main qemu package did not work...same error as above. I don't have the same qemu package that you listed, and I could not find it online either.
I am running Backtrack 5R1 on a regular hard disk installation (no live cd/usb), and the directory target is in /root/Documents/.

shaola · Feb 23, 2012

Jazztrmpter said:
Turns out I'm staying up a little extra past normal to get this done...I was just too interested. So far the only thing not the same was installing qemu. The command did not find the package, so I installed qemu-kvm-extras-static from synaptic pm. It mentioned ARM user mode so I hope that will be fine.

I will update any differences/obstacles along the way.

EDIT

Okay, ran into something... when trying to chroot, I get this error. I am going to try installing the main qemu package.

Code:

root@bt:~/Documents# chroot target qemu: fatal: cp15 insn ee1d7f70 R00=4009f960 R01=00000852 R02=000150e8 R03=0d696914 R04=0001d7cc R05=0009ff58 R06=000153e8 R07=00000000 R08=00000000 R09=000a005c R10=4009f000 R11=00000000 R12=000a005c R13=4007f5d0 R14=42090e80 R15=4008b062 PSR=20000030 --C- T usr32

Installing main qemu package did not work...same error as above. I don't have the same qemu package that you listed, and I could not find it online either.
I am running Backtrack 5R1 on a regular hard disk installation (no live cd/usb), and the directory target is in /root/Documents/.

In wich version of ubuntu is based backtrac?
qemu-usr-static package is aviable in natty, oneiric and precise:
http:// packages.ubuntu.com/search?keywords=qemu-user-static

braernoch · Feb 23, 2012

Jazztrmpter said:
Installing main qemu package did not work...same error as above. I don't have the same qemu package that you listed, and I could not find it online either.
I am running Backtrack 5R1 on a regular hard disk installation (no live cd/usb), and the directory target is in /root/Documents/.

I read somewhere that you should be able to enable current main Ubuntu repositories in Synaptic in BT5. Have you already added those repos? Once done, you should have access to everything.

rdnetto · Feb 23, 2012

CaffeineHead said:
So I just found the ac110 has multiboot working. I dont fully understand the asus bootloader howver so I dont know how practical or feasible it is to implement this on the tf.

They have a wiki page explaining it at ac100.grandou.net/multiboot

Thanks for this. The AC100 is also a Tegra 2 system, so in theory the same changes should work.
Unfortunately, I've tried applying them to no avail - it still freezes when trying to execute the new kernel.

See dev thread for further discussion.

marshallladd said:
Is there anyway to OC the CPU in Ubuntu? In android i run prime at 1.6Ghz, Ubuntu is stuck at 1.0.

Not at present. This is considered a low priority, so no one is currently working on it.

Jazztrmpter · Feb 23, 2012

shaola said:
In wich version of ubuntu is based backtrac?
qemu-usr-static package is aviable in natty, oneiric and precise:
http:// packages.ubuntu.com/search?keywords=qemu-user-static

Hey, BT5 is Lucid, 10.04. I have a virtual machine already setup which is running Ubuntu 11.10 I believe, but I tend to use the real installation (backtrack) on another hard drive for most tasks.

Sent from my iPhone using Tapatalk
ASUS Transformer tf101 32gb + dock.

[Q&A] Ubuntu on the Transformer (eMMC install)

Senior Member

Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Similar threads

Top Liked Posts