Jump to content

  1. 0
  2. 0
  3. 0/5

Rate this Topic

- - - - -

ubuntu on the transformer

  • Please log in to reply

OP lilstevie

lilstevie

Developer

Posted 02 July 2011 - 10:32 PM #1

The video is an earlier version running off a class2 and is damn slow.

The flash-pack included in the second post installs ubuntu to the internal memory of your Transformer.
links to the files are included in the second post :)

This nvflash also comes with what I am calling "blobs-be-gone" which maps boot and recovery into userspace addressable locations, blobs-be-gone is from a discovery I made, and improvements made by RaYmAn.

Updates to the rootfs will not be delivered as a full download, but rather via update-manager, information will be available from here

Here is the video still for your viewing pleasure:

http://www.youtube.com/watch?v=3cFcjB3_RsI



OLiFE for the ASUS transformer
------------------------------------------------------------------

© 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.gee...s/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.

Edited by lilstevie, 06 November 2011 - 04:52 AM.

  • 2 Likes

OP lilstevie

lilstevie

Developer

Posted 02 July 2011 - 10:32 PM #2

Changelog
------------------------------------------------------------------

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 Release


Downloads:

RootFS md5sum(1a9fa8a698e4a96245a3c08511841eb4)
OLiFE md5sum(c30263fd8271a23bb211fd9fdd69fa45)

Sources:
http://gitweb.lilstevie.geek.nz
To clone the repos "git clone git://lilstevie.geek.nz/$(name of repo).git"

Edited by lilstevie, 06 November 2011 - 04:54 AM.

  • 0 Likes

trsohmers

trsohmers

1337 h4x0r / Developer

  • 56 posts

Posted 03 July 2011 - 09:26 AM #3

Awesome man. Now that linux4tegra has been released, it should be really easy to run Ubuntu or virtually any other *nix OS on any of the Tegra devices. I've been working on a native boot since mid March, and even though I wasn't able to get it working on the Xoom first, it's great that we can use the full power of these devices.
  • 0 Likes
Hacker, inventor, and developer
Currently working on ways to dualboot other OSes easily on bootloader unlocked Android devices.
http://trsohmers.com
trsohmers@mit.edu

ChiefzReloaded

ChiefzReloaded

Developer

Posted 05 July 2011 - 07:27 PM #4

That's F'n WIN!! +1... million...
  • 0 Likes

r2doesinc

r2doesinc

Just here for teh bewbs

Posted 07 July 2011 - 02:38 AM #5

are you working with jhinta or are they parallel projects?
  • 0 Likes

OP lilstevie

lilstevie

Developer

Posted 07 July 2011 - 06:02 PM #6

are you working with jhinta or are they parallel projects?


parallel projects, reasons why I will discuss in private only :) I don't feel that my reasons should be in the public eye as it is bad for the community :)
  • 0 Likes

parkjam

parkjam

Android Apprentice

  • 22 posts

Posted 08 July 2011 - 07:37 PM #7

You, sir, are a god
  • 0 Likes

nfusion77

nfusion77

Android Apprentice

  • 26 posts

Posted 09 July 2011 - 10:43 AM #8

Are you still working on getting wifi going ? Ive tried making a few rootfs but havnt had much luck :S I tried the hd2 one that jhinta suggested but cursor is stuck in corner of screen.
  • 0 Likes

OP lilstevie

lilstevie

Developer

Posted 09 July 2011 - 05:17 PM #9

Are you still working on getting wifi going ? Ive tried making a few rootfs but havnt had much luck :S I tried the hd2 one that jhinta suggested but cursor is stuck in corner of screen.


That is expected, evdev in natty is the first to use multitouch improvements, without a small patch to the touchscreen driver it will not work with any earlier version. The next kernel I release will include the TSP patch so people can use different flavours of linux :)

as for the wifi, that has been a major pain in my ass, for some reason it will not scan and I cannot figure out why, on the odd occasion that I manage to get a scan, wpa_supplicant will not connect, once I have a few ideas on what may help, so fingers crossed I will get that working.

on a side note this is Jhintas wifi fix, if any of you have ubuntu up and running give it an attempt, it does not work on my device, and I am trying to get an idea of just how strict the conditions for this are.

i have wifi working by,

sudo iwconfig eth0 mode managed
sudo iwconfig eth0 essid xxx (open dint test secure )

then with wcid, just press connect (setting show wired connections).

  • 0 Likes

nfusion77

nfusion77

Android Apprentice

  • 26 posts

Posted 09 July 2011 - 05:35 PM #10

I would love to help you test this but without a working rootfs i can't do much, how did you compile yours? with rootstock? what command did you use ?
  • 0 Likes