tar is pointless in this situation, tar is compressionless and all piping the dd output though tar would do is put the image in a tarball, running it though gzip would probably be the better option
[Q&A] Ubuntu on the Transformer (eMMC install)
- Thread starter lilstevie
- Start date
tar is pointless in this situation, tar is compressionless and all piping the dd output though tar would do is put the image in a tarball, running it though gzip would probably be the better option
I tried compiling the kernel last night again and ran into more issues. I followed the guide made by rdnetto but only used "make" instead of "make -j2". I ran it twice to make sure the it wasnt a one time glitch. Also when I ran "make tf101_gnulinux_defconfig" I got some weird error but I dont remember what it is. When the kernel failed to compile the it showed the error below. I have tried google for solutions but have been unable to find anything concrete. I can see that its an error with the wireless drivers but I am not sure why I am getting these. I thought I inject the drivers after the kernel is built. Is there a config option to disable treating warnings as errors?
cc1: all warnings being treated as errors
make[4]: *** [drivers/net/wireless/bcm4329/dhd_linux.o] Error 1
make[3]: *** [drivers/net/wireless/bcm4329] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
cc1: all warnings being treated as errors
make[4]: *** [drivers/net/wireless/bcm4329/dhd_linux.o] Error 1
make[3]: *** [drivers/net/wireless/bcm4329] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
You can edit file drivers/net/wireless/bcm4329/Makefile and remove -Werror from DHDCFLAGS and kernel will compile without errors.
Search this thread for "cat /dev/zero " you will find the whole command to type in a terminal to fix this
But, it most probably seems like you blew up your android partition
Thanks, your fix did the trick. If I want to compile the CROS kernel do I follow the same steps?
If you have that same error message probably yes.
Ok that fix boot of android but is it possible to update android os without removing ubuntu ? Or how to remove update from android os because it's all the time showing me that is an update from asus.
Last edited:
anyone know if how to get hdmi working? with the ac100, they have used the nvidia-tegra drivers, but they clash with the kernel provided by lilstevie. I cannot try Cros kernel, as i have sbkv2
Some recent update (must be in the last month) rendered my 12.04 completely useless 
It just keeps flickering on the login screen, alternating boot messages (console) and the login screen.
I don't know where to start searching the problem because I can't get any error message... Xorg.log is 0kb and Xorg.log.old looks fine as if Xserver has been shutdown normaly.
I even did a new install (well a fresh 11.10 and then an update). Right after the dist-upgrade the same result
Does anyone encounter a similar problem? Does even anyone know a fix?
It just keeps flickering on the login screen, alternating boot messages (console) and the login screen.
I don't know where to start searching the problem because I can't get any error message... Xorg.log is 0kb and Xorg.log.old looks fine as if Xserver has been shutdown normaly.
I even did a new install (well a fresh 11.10 and then an update). Right after the dist-upgrade the same result
Does anyone encounter a similar problem? Does even anyone know a fix?
I meant it in the sense of use tar as a frontend to gzip/etc. Admittedly an unneeded level of abstraction, but it does simplify things a bit IMO, particularly since most people are more familiar with using tar than gzip directly.
The defconfig line is important, because if it fails then all the settings in the configuration will be completely wrong. Try running 'export ARCH=arm' first.
Also note that the changes to bcm4329 (which result from changes in the latest version of gcc) are included in the sound patch I uploaded in the dev thread (which hasn't been uploaded to the git yet). Since you'll probably want your speakers to work, it'll be easier to just apply that. (I think it has a few other changes for the same reason as well.)
The CrOS kernel can be used under SBKv2, but uboot can't. CrOS currently needs uboot because it doesn't seem to parse the partition table properly. I'll be working on fixing this soon, atm my TF is being repaired (hardware problem - nothing related to Ubuntu).
Some recent update (must be in the last month) rendered my 12.04 completely useless
It just keeps flickering on the login screen, alternating boot messages (console) and the login screen.
I don't know where to start searching the problem because I can't get any error message... Xorg.log is 0kb and Xorg.log.old looks fine as if Xserver has been shutdown normaly.
I even did a new install (well a fresh 11.10 and then an update). Right after the dist-upgrade the same result
Does anyone encounter a similar problem? Does even anyone know a fix?
apt-get autoremove pulseaudio
I just compiled the CrOS kernel this morning and was going to flash it later today.Good thing you mentioned that it cant read the standard android partition table. What exactly is the problem?
I'm not sure - having my TF die kinda stopped all dev work in its tracks. CrOS actually has support for the Tegra-style partition tables, meaning it should be able to access the previously hidden partitions as well. I'll have to take a look at the source and figure it out - it could be as simple as changing one of the kernel parameters, but I can't really do anything until I've got a working TF again.
I'm going to try to flash the kernel cros today keeping the stock tegra bootloader. Is there something I need to pay attention to to figure out what's wrong? Is there a log file generated that I could post? I know that my question seems vague but I searched both tf threads and the iconia thread and couldn't find an explanation of the problem.
Just the standard kernel output that appears as the kernel loads. Most people who have been using the CrOS kernel have been using uboot, so few people have noticed it. Unless you're comfortable editing the kernel source, there probably isn't much you can do, so you might as well just wait until I can take a closer look at what's going on.
This is great but I am not sure what exactly you did. This is the android kernel, not the chromium one right? Is it a patched version of lilstevie's or is a new build, possibly based of ICS?
simply the latest Asus TF kernel.
til now i have patched and compiled it on my own .
Awesome. I dont mean to be critical and I think all progress is great but why the work on the android kernel and not on the chrome one? I dont really understand the differences and so I am not sure why work on getting the android kernel to work if most people porting ubuntu to android devices (iconia, ac100, etc.) have been using the cros kernel?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
66This thread is for help and support related to ubuntu on the eeepad transformer, all questions not related to development should be asked here, please be friendly and do not flame each other or I will request the thread be closed.
Download links are in the third post.
There is a wiki entry here that has a bit more detailed explanation. Please note though that as it is a wiki information
quoted in there may or may not be entirely accurite.
you will need to download an nvflashable rom, like prime.
Please read the README before attempting this. The readme is below as well as in the kit, YOU WILL LOSE DATA.
Download links are in the second post.
OLiFE for the ASUS transformer
------------------------------------------------------------------
(c) 2011 Steven Barker <lilstevie@lilstevie.geek.nz>
This package should have only been linked to from xda-developers
or rootzwiki if you got the links to this package from anywhere
but those sites please send an email to the above email
address with the subject: "unauthorised posts"
DISCLAIMER
------------------------------------------------------------------
Steven Barker (lilstevie) nor anybody will take any responsibility
for any damage, data loss, fire, death of a loved one, or loss of
data resulting from using this mod for your device. Using this mod
may void your warranty.
NVFLASH
------------------------------------------------------------------
nvflash is the intellectual property of nvidia, and remains the
property of nvidia. Any questions or queries regarding the usage
and licence of nvflash should be directed to nvidia.
abootimg
------------------------------------------------------------------
abootimg is by Gilles Grandou <gilles@grandou.net> and is
unmodified. The source is available from online at
http://gitorious.org/ac100/abootimg
usage
------------------------------------------------------------------
Usage has changed since the release of the last kit, please read
these instructions carefully, as the install method is a little
more complex, (but easier once you use it).
If you downloaded OLiFE.tar.gz you will need to inject the android
rom and ubuntu image. You can use any nvflashable rom with this.
I recommend that you use prime as that is the configuration that
I have tested myself, and the ROM that I support for use with this
device. You can download the ubuntu image from
http://lilstevie.geek.nz/ports/ubuntu.img.gz.
If you downloaded OLiFE-Prime-Edition.tar.gz you will not need to
download the ubuntu image or an nvflash rom as they are seeded into
the image.
Install instructions:
1) Download the specific flavour of OLiFE that you want to use, and
extract it with "tar xvf <filename>".
2) If needed inject android rom and ubuntu image.
3) From the directory that OLiFE was extracted in run the main script
with the command ./OLiFE.sh.
4) Read the text that comes up and answer the question it asks.
5) Follow the menu to the option you want (below is a breakdown of
what each menu item is) and follow the instructions prompted. (also below
is instructions on how to get into the modes requested).
Menu items:
1) Backup Menu:
1) Full Backup (stock)
- Full backup (stock) takes a full backup of a stock
android system. This gives you an option to also back
up your user data(this will take a while).
2) Full Backup (ubuntu)
- Full backup (ubuntu) takes a full backup of a system
that dualboots android and ubuntu, this backs up your
system, and the ubuntu image. This gives you an option
to also back up your user data(this will take a while).
3) User data only
- This backs up the user data partition on your device.
(This option takes a while)
4) Android ROM
- This option backs up the android system only. This
option generates all the files (minus bootloader, and BCT)
required to flash a rom via nvflash.
5) Ubuntu Install
- This option backs up the ubuntu install on your device.
2) Flash Device:
1) Dualboot:
- This option will install ubuntu to your device in a
dualbooting configuration with android. During the
installation process it asks you which OS you would like
to boot by default.
2) uboot (linux only):
- This option will install ubuntu with u-boot and the
ChromeOS kernel that supports acceleration. This option
is currently unavailable, but should be available soon.
3) asus boot (linux only):
- This option will install ubuntu with the asus bootloader
with this configuration you will use all the eMMC for ubuntu
and there will be no android system installed on your device.
4) stock:
- This option will partition the device in a stock way and
install the android system that is in ./images. Use this
option if you no longer want ubuntu on your device.
3) Update Device:
1) Android Kernel:
- This option will update the android kernel on your device
with the boot.img from ./images/. This allows you to install
your own kernel on the device for android rather than the one
that comes with your chosen rom.
2) Ubuntu/Linux Kernel:
- This will update the ubuntu kernel on your device to the version
included in this flashkit. This option is for updating just the
kernel with nvflash rather than using the blob method. This method
is also good for if you flash a bad ubuntu kernel to the device.
3) Android ROM:
- This option will update the android rom on the device with the
one from ./images/. This is good for if the ROM you use is updated
or you would like to change ROMs and there is an nvflash image for it.
This option does not destroy your data.
4) Ubuntu Rootfs:
- This will update your ubuntu image on the device. This is destructive
to data stored in the ubuntu image.
5) Advanced (Unsupported):
- Any option in this menu is not supported and should be considered
unstable. There may be bugs in these options and they are not maintained
at this point in time.
1) Flash ChromeOS Kernel (Primary Boot):
- This option will flash the ChromeOS kernel to the primary boot
partition. This option may not currently work in it's current
configuration.
2) Flash ChromeOS Kernel (Secondary Boot):
- This option will flash the ChromeOS kernel to the secondary boot
partition. This option may not currently work in it's current
configuration.
3) Update Uboot Partition:
- This option will update the u-boot boot partition that u-boot
reads the kernel and boot script from. This option does work if
you have installed u-boot by compiling it from source and installed
it yourself.
4) Flash ClockworkRecoveryMod:
- This option allows you to temperarily flash CWR to the device so
you can update the installed rom. It backs up the current kernel in
the recovery kernel position and then flashes CWR. When you have finished
using CWR you then push any key and put the device back in APX mode and
it will restore the kernel that was in that position. (This only works if
android is your primary boot option at this time).
4) Inject Firmware:
1) Bluetooth firmware (default install):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system.
2) Bluetooth firmware (CrOS Kernel):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system and flashes the proper u-boot kernel
if you no longer need adb support.
5) Onscreen Keyboard:
- This runs OnBoard so that you can run through oem-config properly
you only need to use this option if you do not have a keyboard dock
and on the first boot.
1) Standard Kernel:
- This will invoke oem-config on the standard kernel installed
on the device.
2) ChromeOS Kernel:
- This will invoke oem-config on the u-boot kernel that is
installed on the device and flashes the proper u-boot kernel
if you no longer need adb support.
Device Modes:
APX Mode:
-This mode is used by nvflash to write files to the eMMC device.
To boot in this mode you press Power and Vol-Up.
Recovery Mode:
- This mode is where CWR or Asus recovery normally lives, but is
replaced by the secondary OS in the dualboot configuration.
To boot in this mode you press Power and Vol-Down, then Vol-Up when prompted.
Normal Boot:
-This mode is where android normally lives.
To boot in this mode you press the Power button until the screen turns on.25Changelog
------------------------------------------------------------------
1.2a - Release name: Odyssey
* New name for kit: OLiFE
* New menu system
* Updated README
* Better handling of platform detection
* Bluetooth support in ubuntu.img
* Preliminary support for ChromeOS kernel
* Preliminary support for uboot
* Fixed touchpad
* Fixed network manager
* Updated to ubuntu oneiric
* More options for flashing and updating
* OTB Wireless support (No more injecting)
* Smaller ubuntu.img for faster upload to device
* Auto resizing of rootfs on first boot
* Larger partition size (6GB) for ubuntu
* Refactored to more easily between devices
* Maybe something else I have missed
1.1 - Release name: Daedalus
* Firmware injector for BT and wifi firmwares
1.0 and silent updates - Release name: Prometheus
* Support for x86_64 linux distributions
* Updated README for release on xda-developers
* Fixes to install scripts
* Initial Release8Multiboot by cmw.zips
This will restore cwm on recovery partition.
And multiboot by flashing Ubuntu.zip or Android.zip
Create flash-recovery.sh in flashkit dir !!
The code below wil not work unless you provide some info on witch flash mode you used !!!!!
Like me i have selected flash-linux-android.sh,
View it and find witch --config file it use as you can see below.
--->--configfile ./flash/android-linux.cfg <---
Code:#!/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
To Make this code above work replaced nflash with ./nvflash -> then sudo sh flash-recovery.sh
Android <-- Prime 1.7 kernel !! you can select any kernel you want !!
MD5 : 97cf64f6d5698276bde1d8657ec80cef
Ubuntu
MD5 : 40c9f82c30e0fd8230c712e23f2e35977Downloads:
RootFS md5sum(1a9fa8a698e4a96245a3c08511841eb4)
OLiFE md5sum(c30263fd8271a23bb211fd9fdd69fa45)
OLiFE Prime Edition md5sum(767779ccfa200e5e00b2f1e33a3d73a9)
Sources:
http://gitweb.lilstevie.geek.nz
To clone the repos "git clone git://lilstevie.geek.nz/$(name of repo).git"6Simple Version
Here's a simple nvflash package I put together to make things easy. It uses Jhinta's CWM files (incl.) and Prime 1.7. Just add ubuntu.img (from the OP) and run download-ubuntu.sh. (You'll still need to run the firmware injection script for drivers though.)
http://www.multiupload.com/6GZSLRBP8S
MD5: 843f964141ac96423c2fcdfc26092050
