yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] outpox:
I did't think to apt-cache search, you're right ^^"

But according to my terminal I'm told it was already installed :

sudo apt-get install libblkid1
Reading package lists... Done
Building dependency tree
Reading state information... Done
libblkid1 est déjà la plus récente version disponible.
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires*:
libxcb1:i386 libxau6:i386 libice6:i386 libxdmcp6:i386 libjpeg62:i386
libx11-6:i386 libsm6:i386 libxext6:i386 nvidia-settings
Veuillez utiliser «*apt-get autoremove*» pour les supprimer.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 11 non mis à jour.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
do you have x86 or x86_64 system? have you read carefully? the binary provides are for x86

EDIT: I have abootimg for amd64 but you will have to compile blobpack

http://dl.dropbox.com/u/60048492/abootimg-x86_64

http://dl.dropbox.com/u/60048492/AndroidRoot-BlobTools-feeab2e.zip
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
thanks

may i ask where i can find the kernelblob in the zip file of the rom? am looking throughout, but only found blob.

edit: sorry, had to refresh before posting....
[Eee Pad Transformer Q&A, Help & Troubleshooting] outpox:
Damn I'm sorry all my OS are x64 (that means Mint x64, Windows 7 x64, Windows Vista x64) ><

Do you think it will work with a x86 ubuntu live cd ? I think/hope yes :p
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
you don't need, i've posted abootimg for x64 and compile blobtols is so easy, and fast, see my previous post
[Eee Pad Transformer Q&A, Help & Troubleshooting] outpox:
I give it a look.

EDIT : I'm kinda newb, but when I try

make Makefile

I have :

make: Nothing to be done for `Makefile'.

I think I'm not doing it right, but I don't really understand :(
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
just "make" no "make Makefile"
[Eee Pad Transformer Q&A, Help & Troubleshooting] outpox:
Yeah, I had to download g++ but I've successfully compiled blobpack and blobunpack.

Thanks !

EDIT :

./abootimg-x86_64 --create boot.img -f boot.cfg -k 2636-zImage -r initrd.img
bash: ./abootimg-x86_64: Permission denied

sudo ./abootimg-x86_64 --create boot.img -f boot.cfg -k 2636-zImage -r initrd.img
sudo: ./abootimg-x86_64: command not found

EDIT2 : Just forgave to

chmod +x abootimg-x86_64

This step worked :p

EDIT 3 : Do I have to change the kernelblob in Android.zip and Ubuntu.zip with the one I created ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
So I have replaced kernelblob with the one from revolver ROM. There is a difference in size, the original in Android.zip was 3.5M, the new one is only 1.5M. Furthermore, unblobpack says it is EBT, not LNX

FROM Revolver ROM

Header size: 60

1 partitions starting at offset 0x3C

Blob version: 65536

Partition 0

Name: EBT

Offset: 76 (0x4C)

Size: 1454712 (0x163278)

Writing file ../kernelblob.EBT (1454712 bytes)

ORIGINAL FROM ANDROID.ZIP

Header size: 60

1 partitions starting at offset 0x3C

Blob version: 65536

Partition 0

Name: LNX

Offset: 76 (0x4C)

Size: 3518464 (0x35B000)

Writing file ../kernelblob.LNX (3518464 bytes)

Is it still safe to proceed? I would like to first flash this file before going to ubuntu, as a precaution

stephen
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
well, EBT is bootloader partition, so no, i think is not safe to proceed because that blob is bootloader and not the kernel, try to find another blob that is LNX, or maybe the ting is that latest REVOLVER still uses the same kernel so that's why is not the kernel present.

Maybe this is a cuestion to ask to revolver developer. I would not mess if bootloader is involved
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
How to run linuxrc in initrd? I added linuxrc to initrd / but after starting it doesn't run.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
did you chmod it to give running permissions?
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Yes, it has chmod 777.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
that does not give it permission to be executable, chmod +x
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
His permission is

-rwxrwxrwx 1 jozka1 jozka1 267 2012-03-10 12:46 linuxrc
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
thanks, will do that. he is using the standard kernels from asus, as it is based on the asus update, but better to confirm.

on another note, I have actually flashed Ubuntu on my tf101, but got start at bootup - the booting failed and failed to a busybox terminal. I used the Ubuntu.img as mentionned in the first possts, the 500mb, so now will be trying with the oife 2gb one. The zip used was the one provided for multiboot.

I then had to go back to revolver using the full rom version, so lost some data. could have used my nandroid backup, but am not sure if it backups up the kernl part as well.

thanks
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
The ubuntu.zip provided in the first post is jus for the microsd install but i didn't test it, so if you dd over the microsd and used that ubuntu.zip and didn't work more info would be necesary to debug this.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
What i did was the following:

1) placed ubuntu.zip in Microsd card

2) placed ubuntu.img (500Mb) in same microsd

3) flashed with cqm ubuntu.zip

and it failed to busybox.

Now am getting the olife image and will try this.

am i doing it correctly? will take a screenshot of the booting image.

I cannot afford to wipe all my android data - wife and kid are hijacking it too much. So I need to have ubuntu as a secondary os.

Stephen
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
that's the problem, that method requires dd the image over de microsd, it won't boot the ubuntu.img.

so, you have to dd if=ubuntu.img of=/dev/microsdpartition

you can do that in linux machine or trough adb shell in cwm recovery. YOU WILL LOSE ALL THE DATA IN THE MICROSD

booting ubuntu.img file from the microsd is not worth it. booting directly the image file is the purpose of the third method if i ever figure out how to do it, and the purpose is to have the advantage of the speed of the internal sdcard without loosing the android data partition.

So, if i succes it will be posible also to boot the image directly from the microsd but as i said is not worth it

EDIT: of course you will have to copy ubuntu.zip after dd the image or have another microsd tu flash ubuntu.zip. The last cwm have acces to the internal sd or you could also mount manually the internal sd also to to that. Meet me if you want in the irc for further instructions
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Please, can you send me your initrd with functionality linuxrc? THX in advance.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
hahaha, i would if i had one, but nope, is not working, is not being executed either in my initrd
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
OK, now i start getting it... I had previously helped in PCLinux on the eeepc, and was spoilt with getting a number of squashfs with different systems booting from one SD CARD from grub.

In the meantime, I am creating a new image from rootstock from ubuntu, so as to check my image, and also got the kernel blob from the asus update zip. (Although I can unblobpack it, am not sure what to do with this blob - do I rename and place in Android.zip?)

But I have to get hold of a smaller microSD card, or help in figuring out how to boot the image from a file. I note from the other thread that some help was available, but it is still not clear how to do it.

from a linux perspective, once i fallback to busybox, can i mount the image file, and then take it from there? I understand this is a dirty trick, but at least it would get me started.

thanks
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
What? I don't understand. I thought that linuxrc woks for you.

http://xdaforums.com/showpost.php?p=23441418&postcount=1723
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
Why don't you just use android.zip I posted in the first post?

You can try, i was thinking about doing that to see what happens.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
it wasn't i had the same results without the linuxrc, and when internalsdcard is mounted the path to the ubuntu.img is /media/data/media/ubuntu.img (don't ask me why)

anyway, i had try so many things that i don't know exactly were i am. I have to step back and start over.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Do we understand each other clearly? You also have problem with linuxrc, that it will not start when you set up kernel?
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
would this work with an ics rom? that is why i was going to use a kernelblob from an ics rom, rather that from hc.

---------- Post added at 02:56 PM ---------- Previous post was at 02:39 PM ----------

found this thread:

xdaforums.com/showpost.php?p=3402947&postcount=687

Looks promising, but am going through more links to see how far this can go. Will also try to load ubuntu img file from emmc using terminal to get an idea of the commands necessary, but i am no expert here...
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
I have pseudo dualboot on emmc! :) E: maybe

A few minutes...
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
good, i was going to try some things right now.... actually was doing a nandroid backup, as the wife and kid are in bed, and have my TF back...
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
http://www.mediafire.com/?92cvx59zyh4yv3o

This is kernel for boot system from ubuntu.img (you have image in /data/media/ubuntu.img).

I edit init file in initrd:

for:

mount -t devpts -o noexec,nosuid,gid=5,mode=0620 none /dev/pts || true
> /dev/.initramfs-tools
mkdir /dev/.initramfs

I added:

mount /dev/mmcblk0p7 /media/

losetup /dev/loop0 /media/media/ubuntu.img
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
So, the linuxrc file seems is obsoleted...

where exactly in the file did you add those lines?
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
28-30, there where it end "mkdir /dev/.initramfs"
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
Good job, i will update soon the guide.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Why we need latest kernel 2.6.38?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
what?

the kernel 2.38 is the crome os bassed one for uboot mode, only aviable with nvflash
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
it did not work for me, it got stuck not finding the ubuntu image file. where exactly do you place it?

i copied it to /data/media, which happens to be my home directory.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
I haven't test it yet, but the ubuntu.img is supposed to be in the root of sdcard

so, inside android with file explorer in /sdcard/ubuntu.img
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
that is where it s placed.

the ubuntu booting fails to a busybox terminal. It complains that it cannot find the img file after mounting /media

With the shell, i can mount mmmcblk0p7 to media, then look for ubuntu img in /media/media, and it is there.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
The image of Ubuntu must be in internal memory > /sdcard/ubuntu.img (it is symbolic link to /data/media/ )

I'm sorry my fail,but I see file from CWM in /data/media/.

"Why we need latest kernel 2.6.38?"

:D

I wanted write, Why we haven't latest kernel.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
Actually, it is stuck on mounting mmcblk0p7, to media. It claims that the file or directory does not exist. On going to busybox, i can mount with no prob.

Am still with ubuntu booting, so if you need to ask anything now is a good time.

By the way, how do i boot from the terminal after mounting the image?
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
http://www.mediafire.com/?92cvx59zyh4yv3o

~ # ls /data/media | grep ubuntu
ubuntu.img

It works for me.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
I understand.

But in my case, it is not mounting mmcbl0p7, but i cannot understand why. It is saying /media does not exist.

Then when i get to terminal, ls shows it nicely, i can losetup the ubuntu.img without probs, and mount the other directories. that done, i can chrrot to the ubuntu image, but i do know how to continue booting.

The stumbling block remains mounting dev/mmcblk to media, from the initrd file.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
You can try http://www.mediafire.com/?7r16qb3ox8nvg1x . I changed mountpoint, media > test. You don't change anything and only you try it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
I was going through the original initrd, and I could not find a reference to /media at all.

Would you need to create it first specificially?

---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------

this is not working as well, same problem.

Refer to previous post. I have to find a way of altering initrd, since it is appearign as read-only on my ubuntu machine
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Don't you flash my zip package? Do you make own package?

Folder media (or test in 2. package) is added to initrd.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
yes i have used both.

My mistake in claiming /media was not set, I was looking in the original initrd, as I could not get to yours. Still both packages are not working on my TF

there is also a FATAL error. could not load /lib/modules/2.6.36/4/modules.dep
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
I have too: FATAL error. could not load /lib/modules/2.6.36/4/modules.dep

I don't understand that to you it doesn't work but to me yes.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
where are you placing the actual mkdir /test line?

is it early in the initrd, or just before mounting? Maybe that is the cause...

I am trying to get a kernelblob with my modifications, but each time i find that it is loading yours.
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
No, folder "test" is packed in initrd.

# ls '/home/jozka1/initrd'
bin conf etc init lib sbin scripts test

http://www.youtube.com/watch?v=CzTimTGXkWU
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
Could you try removing the test directory, then actually making the test or media directory in init?

---------- Post added at 01:30 AM ---------- Previous post was at 01:22 AM ----------

for my reference and peace of mind, can you let me know how you compile to zip file?

I have managed to alter the init file, and manage to use abootimg and blobpack. I rename boot.img to kernelblob, and then exhange it for that in the Ubuntu.zip.

However, when flashed with CWM, it keeps loading the previous one that i would have used

stephen
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
http://www.mediafire.com/?ftqtqwtghoxg84u

This is pack which folder make. Tested and work for me. > http://www.youtube.com/watch?v=Dl33nMklX58

E: http://www.thegeekstuff.com/2009/07/how-to-view-modify-and-recreate-initrd-img/
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
again not working.................

"Making a directory

Mounting to a directory

mount: mounting /dev/mmc .... on /test/ failed: No such file or directory"

once in busybox, ls shows test, which is of course empty.

does:

mount /dev/mmcblk0p7 /test/

need any more arguments? eg -t or -o?

EDIT: scratch that - of course no need for arguments.... Am at loss at how it will not mount mmcblk... to any directory
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Have you realy ubuntu.img in right place? And using you ubuntu.img by lilsteve?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
well, it's not working for me either, but for different reasons i got kernel panics all the time. Did you use the image of 2.0 GB?
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
yes, ubuntu.img is the one by lilstevie, and i can find it in the right place after falling back to busybox.

It is simply not mounting /media or /test during the bootup before falling to busybox.

On another note, how can i make a zip file from a kernelblob, what tools do u use?
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
I have no idea, i just open (not extract) the zip file with a program (ark in my case), delete kernelblob and add a new file
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
I do just that, but my kernelblob do not get updated, instead my tf boots with the previous kernel
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
Your kernel is very big. Max size is 8MB +-.

When you make ls in busybox what do you see?
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
you are right it is about 8.4mb before placing it in the zip file.

will boot again into ubuntu.zip to check what busybox reports, but if it is not being used , the it will report your filesystem.

And I had used the one provided in the original post, used abotimg, and blobpack to get to this. I only changd initrd

EDIT: your kernelblob when extracted is 8.4mb, just the size as mine.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
That it's imposible, if you use abootimg and the result is bigger than 8 mb it will give an error

see boot.cfg, the size has to be limited to 8 mb
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
well it seems it was not blobpacking properly for some reason. Now am able to flash my own update.zip.

Still, I cannot mount mmcblk0p7 no matter what I do.

ls in busybox lists /media and it is empty.

I have even added an extra line in init to ls all directories before mounting, and media is there. Still mounting failed.

I have also used mount -t auto - am not sure what ext the partition uses.

This is part of the init that I did:

[ -d /dev ] || mkdir -m 0755 /dev

[ -d /root ] || mkdir -m 0700 /root

[ -d /sys ] || mkdir /sys

[ -d /proc ] || mkdir /proc

[ -d /tmp ] || mkdir /tmp

mkdir -p /var/lock

mkdir /media

mount -t sysfs -o nodev,noexec,nosuid none /sys

mount -t proc -o nodev,noexec,nosuid none /proc

# Some things don't work properly without /etc/mtab.

ln -sf /proc/mounts /etc/mtab

grep -q '\<quiet\>' /proc/cmdline || echo "Loading, please wait..."

# Note that this only becomes /dev on the real filesystem if udev's scripts

# are used; which they will be, but it's worth pointing out

if ! mount -t devtmpfs -o mode=0755 none /dev; then

echo "W: devtmpfs not available, falling back to tmpfs for /dev"

mount -t tmpfs -o mode=0755 udev /dev

[ -e /dev/console ] || mknod -m 0600 /dev/console c 5 1

[ -e /dev/null ] || mknod /dev/null c 1 3

fi

mkdir /dev/pts

mount -t devpts -o noexec,nosuid,gid=5,mode=0620 none /dev/pts || true

> /dev/.initramfs-tools

mkdir /dev/.initramfs

ls

# Mount ubuntu image

echo "Mounting mmcblk0p7"

mount -t auto /dev/mmcblk0p7 /media/

losetup /dev/loop0 /media/media/ubuntu.img

BTW, in the original post, boot.conf listed root=/dev/mmcblk1p1 , I changed that to 0p7, since I was not using the sd any more. still no success in mounting

---------- Post added at 03:05 PM ---------- Previous post was at 02:47 PM ----------

making some progress...

i discovered that "no such file or directory" might not refer to /media, and in fact, I have added a line to my init:

ls /dev/mmc*

and it claims that there is no such file. If I do only ls /dev a number of listings appear, but i cannot see any mmcblk

once in busybox, i can see all mmcblk, and can mount

Could it be that dev is not being populated before I try to mount? should I include some form of time out?

I have also removed the root= option from boot.cfg, as it would not allow me to mount from busybox
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
I have finally manage to get atround mounting the mmc. I dont know how, but adding ls /dev/mmc* somehow gave some time for dev to be populated.

It is now complaining that /etc/fstab is not being found. I suspect rootfs has not been mounted. The loop device with ubuntu.img is being found now, but how do i check if it becomes the rootfs?
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
and here would be my update files.

For anyone interested, also my android.zip for use with ICS, specifically the Revolver Rom

The kernel used is the one by lilstevie, from the olife scripts.

Many thanks to all, shoala, lilstevie, rdnetto, jhinta, jozka.1 for all the help. Now need to sort out increasing the image file for a more complete system.

stephen
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
Well, that works for me, although there are some minor errors we could fix, could you pass me your initrd and boot.cfg you used?
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
I don't understand your changes but when work for you :)

Resize: (bs=1G is 1GB)

dd if=/dev/zero bs=1G count=1 >> ubuntu.img
e2fsck -f ubuntu.img
resize2fs ubuntu.img
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
here they are

boot.cfg

bootsize = 0x800000

pagesize = 0x800

kerneladdr = 0x10008000

ramdiskaddr = 0x11000000

secondaddr = 0x10f00000

tagsaddr = 0x10000100

name =

cmdline = nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 ro quiet splash

EDIT Sorry, did not realise you cannot upload a cfg file
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
hmmmmmm, where? :p
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
may i ask which errors?

had to resize on PC, and transfer tthrough wifi, as of course, the img file cannot be bigger than 4G with vfat on MicroSD
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
missing modules.dep, and something about home partition, i didn't take a deep look cause i am a bit busy right now

EDIT: Be careful resizing the image file, you would probably need to update your fstab because is set by UUID
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
ok, will check how it goes. That would mean downloading another 5.5g...

On another note, how far is the kernel with respect to all the features? Do i need to inject any firmware. Wifi was working nicely. not sure about bluetooth and sound. I understand webcam is also a no-go at present.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
for the bluetooth yes, you will need to inject firmware, the sound is working with the latest kernel from git, i have it compiled and i'll upload and update everything as soon as i have time.

I don't know about everything else
[Eee Pad Transformer Q&A, Help & Troubleshooting] jozka.1:
I thought it so that when edit the boot.cfg > bootsize = 0x8d6000 and compile (abootimg) with new initrd + kernel (2.6.38) and flash, so it doesn't flashed and there stay old kernel.
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
because the LNX partition is just 8MB sized and you can't change that withouth nvflash
[Eee Pad Transformer Q&A, Help & Troubleshooting] shaola:
I have updated the first post, sorry i don't have time rigth now to go deeper in this configurations, and i don't use them because i have a sbk1 device.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssciberras:
thanks.

are these new files, or the previous files as per original post? So is it the latest kernel etc?

What are the chances of using CrOS kernel, i believe it uses tegra modules and hardware acceleration. But is it too big for 8mb partition?

Have resized img, now modifying fstab to use labels rather than uuid, so that any future modifications are easier.