Ok, after compiling once again kernel, I flashed it through CWM, and everything works fine I really thank you for your help, and I cannot believe to have the wireless scanning tooThat's odd, all CWM does is dd the blob to the partition (mmcblk0p4).
"ROM manager" doesn't support Transformer.
So I decided to write a dd script for swapping recovery partition.
I will use some command like:
dd if=/sdcard/linux.img of=/dev/block/mmcblk0p4 bs=409
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4 bs=409
but I am not sure which is the recovery partition. It seems it's not mmcblk0p4 anymore. Any ideas ?
how can I backup my current UBT partition to an img file ?
as I had to work on it for 3 nights, I'd like to keep it somewhere.
And if anyone requires to have a working Ubuntu 11.10 partition, I can share...
how can I backup my current UBT partition to an img file ?
as I had to work on it for 3 nights, I'd like to keep it somewhere.
And if anyone requires to have a working Ubuntu 11.10 partition, I can share...
Ok, after compiling once again kernel, I flashed it through CWM, and everything works fine I really thank you for your help, and I cannot believe to have the wireless scanning too
"ROM manager" doesn't support Transformer.
So I decided to write a dd script for swapping recovery partition.
I will use some command like:
dd if=/sdcard/linux.img of=/dev/block/mmcblk0p4 bs=409
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4 bs=409
but I am not sure which is the recovery partition. It seems it's not mmcblk0p4 anymore. Any ideas ?
You're welcome. But you shouldn't have scanning - at least, I don't.
I am interested in why you do not have scanning, the latest versions compiled from git should have scanning as that is what was merged in from VHDA
Use dd (it's mmcblk0p8) under Android. I suggest piping it through gzip or something similar.
You're welcome. But you shouldn't have scanning - at least, I don't.
p4 is where the blobs are loaded from for installation.
p9 and 910 are SOS and LNX, and are inaccessible while the OS is running. To flash both, you'll need to create a blob (use blobpack) and write it to p4.
dd alone is enough, but the image will be massive. Because it's mostly empty space, compressing it with gzip will result in a much smaller image. The alternative is to run resize2fs before and after, but generally you want to avoid modifying the partition when making a backup.I didn't understand that. Why do I need gzip ? Just dd wouldn't be enough ?
I'm guessing you're using Gnome as well?I have wifi scanning as well. I compiled the kernel with your instructions on page 103.
When you boot the transformer, the bootloader starts by checking if there's a blob in p4. If there is it executes it. The blob will then extract the images it contains to the relevant partitions.I don't understand. Shall I use p8 ?
if so, what do I need p4 , p9 and p10 for ?
I'm really confused...
This is a quick guide I've written for anyone who wants to use a different kernel, since the original one is now rather outdated and doesn't support the mouse.
sudo resize2fs -p /dev/mmcblk0p7 20G
resize2fs 1.41.14 (22-Dec-2010)
resize2fs: /dev/mmcblk0p7: The combination of flex_bg and
!resize_inode features is not supported by resize2fs.
I've searched the two main threads and haven't been able to find anything about setting up the webcam. I've been able to upgrade to Ubuntu 11.10 with touchpad and wifi working on a Transformer with only an Ubuntu. Any ideas on where to start to set it up?
Also: I'd like to try to the CrOS kernel - do I need the custom uboot for it to work, or can I just compile the custom kernel from the github and have it work on my pure ubuntu setup?
Thanks!
Thanks for the guide. I started building the kernel on the Transformer, but I ran out of space on my Ubuntu partition (mmcblk0p8 - 3.9G). I'd like to grab some space from the Android partition (mmcblk0p7 - 24G), but when I try and run:
...I get this output:Code:sudo resize2fs -p /dev/mmcblk0p7 20G
Code:resize2fs 1.41.14 (22-Dec-2010) resize2fs: /dev/mmcblk0p7: The combination of flex_bg and !resize_inode features is not supported by resize2fs.
Tips?
Webcams I am not too sure about, all of mine are built into devices, and even then, I don't use them.
As of the latest commit you can run the CrOS kernel without needing u-boot, but be warned, it is nowhere near as friendly on the asus bootloader, the gained stability is at the cost of artifacting on the graphics, I am still working on solving all the problems with it
Actually that's what I meant - the built-in webcam wasn't working on mine (couldn't get it to detect in empathy). Is something wrong with my installation, or how do you suggest setting it up?
As for the new kernel, thank you for the heads-up. I really like what you've done so far and am looking forward to the stable release.
Yes I understand that, thanks. I'm interested in trying to set it up, do you have any constructive advice?
p4 only holds blobs, and once the blob is used the partition is formatted. You can't backup partitions with it - if you want to create a backup you have to use nvflash.so, you say I can't access p9 and p10 from Android and I should access p4.
p4 seems to be a big partition. what else does it hold except the blobs ?
now, if I dd all p4 partition it will backup all partition. I just want to change the recovery partition to "clockwork" when I need that. and after I finish with recovery, I want to put the Ubuntu loader back.
how can I achieve this ?
You can't resize them like that. resize2fs only changes the size of the filesystem - it's still limited by the size of the actual partition, which can only be changed with nvflash (which formats the entire system in the process).Thanks for the guide. I started building the kernel on the Transformer, but I ran out of space on my Ubuntu partition (mmcblk0p8 - 3.9G). I'd like to grab some space from the Android partition (mmcblk0p7 - 24G), but when I try and run:
...I get this output:Code:sudo resize2fs -p /dev/mmcblk0p7 20G
Tips?Code:resize2fs 1.41.14 (22-Dec-2010) resize2fs: /dev/mmcblk0p7: The combination of flex_bg and !resize_inode features is not supported by resize2fs.
To add onto this I went ahead and built the kernel on the Android partition without any issue. Running the script "blobbed" it up and flashed it, and sure enough upon restart the blue meter filled up.
Then the Transformer rebooted and sat at the Asus screen. Eventually I rebooted into CWM Recovery, flashed the ZIP attached to the instruction post, and booted back into Ubuntu just like before. Two questions:
- Any ideas as to what I did wrong in the build process?
- I'm still running Android, and I didn't realize that the ZIP you posted would load Ubuntu as the default OS. I assumed it was the ZIP that let you boot Ubuntu from CWM. How can I restore Android as the default OS (I'm assuming I can bundle this kernel I've built into an Ubuntu-booting ZIP once I fix whatever's wrong with it.)
#!/bin/sh
nflash --bct ./images/transformer.bct --setbct --configfile ./flash/android-linux.cfg --bl ./images/bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
nflash -r --download 5 ./images/recovery.img