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

Search This thread

lilstevie

Senior Recognized Developer
Apr 17, 2009
1,339
1,040
any fix for the flashing/blinking cursor?
can I change the keyboard layout to configure f1-12 like in android?

I am trying gnome shell but I get like 1 frame every 5 seconds. Glxgears shows 300fps, the hw acceleration should be fine...I also get 1/5fps at the login screen, in unity 2d it is fine, and hw is working because glxgears runs fine and dragging windows is smooth and not laggish...

the changes are made at a kernel level, so my suggestion would be to modify the keyboard layout that you use in ubuntu for it. there are far more reasons to have it this way than the android way.

I haven't run my tf101 with acceleration for a really long time, but the login screen slow down issue I have seen on my trimslice (also tegra2) although not seen it on my tf201. I don't use gnome-shell so I cannot comment on that
 
  • Like
Reactions: JoinTheRealms

JoinTheRealms

Senior Member
Apr 7, 2012
1,931
1,297
the changes are made at a kernel level, so my suggestion would be to modify the keyboard layout that you use in ubuntu for it. there are far more reasons to have it this way than the android way.

I haven't run my tf101 with acceleration for a really long time, but the login screen slow down issue I have seen on my trimslice (also tegra2) although not seen it on my tf201. I don't use gnome-shell so I cannot comment on that

A bit off topic but im interested to know if the tegra 3 runs Ubuntu any better then then the tegra 2, im tempted to upgrade to a tf300t when it gains Ubuntu but whether it will run Ubuntu any better the tf101 is really the deciding factor.

Cheers
 

cunctator

New member
Sep 1, 2012
4
0
Hello World

Hello world! I'm new here.

i got the lilstevie's precise pangolin running on my B60, energized by the 3.1.10 jintha kernel, using/hacking the OLiFE scripts suit to flash them on my device.
thank u guys for having done a so wonderful job! while the procedure is pretty easy to follow, i still dont understand how the partitions works, and more specific: what's the relation between the nvflash config file and what u get at runtime in /dev?
any help on this would be great!
 
Last edited:

akulik1990

New member
Aug 31, 2010
2
0
SBKv2

Sorry, just a bit confused, does this work on SBKv2 or no?((
I can not get the script to work after pressing enter in APX mode stage. nothing happens afterwards.
Also Adb can detect the device in recovery every now and then but in APX not((Don't know is this ok or no)

Sorry))found out it doesn't((
 
Last edited:

s.zamani

Senior Member
Jan 22, 2008
53
1
Berlin
it's not to be found I have searched so many times

thanks =)

the command is "cat /dev/zero > /dev/mmcblk0p3" but I have this message :
"cat: write error: No space left on device"
do you know what to do?

EDIT : despite the error message, it's running on android so thanks thanks thanks =D


is this command to be typed in to the terminal under osx?
sorry I have no idea how ADB works on a mac I allways used onclick installers under windows now I have no windows pc anymore it got stolen and I am stuck with a mac... can someone please help me! :rolleyes:
 
Last edited:

seshmaru

Senior Member
Aug 22, 2009
1,294
374
I'm kind of confused why no one has asked this yet but what is the default user info or root password? After successfully booting I never got asked to set up an account or anything, I booted into the log in screen.

AKA I can only access a guest session.
 
Last edited:

dvhh

Member
Mar 1, 2011
40
9
Osaka
with the default OLife ubuntu image ? it is suppose to start the graphical ubuntu installer.
Try restarting it one more time.
If the error persist it might mean that your image/partition is corrupted
 

2light

New member
Dec 27, 2010
1
0
Hello Guy,

I used the Tubuntu - One Click installer : http://xdaforums.com/showthread.php?t=1995157

with this Guide:http://xdaforums.com/showthread.php?t=2041030

In the tubuntu Install tool i select only install "ubunut only", all work up to the point where the tool flash the ubuntu.img.
There it says my Partition is to small..

I tryed to finde a fix, but i didn't get it :/

So may you can help me ..

The Error:
.\images\ubuntu.img is too large for partition
command failure: create failed


2light ♥
 

x3maniac

Inactive Recognized Developer
Sep 2, 2008
361
453
New York
www.novaspirit.com
If you read back towards my tread more towards the end. The solution is there. You have to modify a config file /config/ and add a zero at the end of the ubt partition size

Sent from my SGH-T999 using xda app-developers app
 

Jazztrmpter

Senior Member
Jan 18, 2012
115
23
Las Vegas
Hey all, quick question.

Is this screen from the eMMC installation? If so, can I get rid of it? I have CWM installed, so I don't know why this is still here every time I reboot.
I'm asking because I just tried to flash the custom JB 4.1.1 ROM by RaymanFX and I can't get past this screen.

20130108_213409.jpg


When I restart my tablet, I have to hold the volume down button. If I don't, it will go straight to CWM. When I hold volume down, that screen comes up, and then I must hit volume down again in order to initiate the ROM boot sequence. I just got rid of Prime in hopes of getting JB up and running tonight but I guess that's not going to happen tonight.

I had Ubuntu installed a while ago but have no use for it anymore, and was hoping to get back to more of a "stock" feel. Any help or tips are much appreciated.



This is for future search/reference purposes...like keywords/tags. Since I wasn't able to find anything in this thread about the text in the image, now others will be able to.
Press <vol_up> to execute or <vol_down> to cancel wiping data. Skip wiping user data and cold-booting Linux.
 
Last edited:

stibbons

New member
Jul 28, 2010
3
2
links are dead or down. I started to collect all the items today and all of lilstevies links are not working.

They've moved. I was able to get OLiFE from http://lilstevie.geek.nz/ports/ , though, and the rest of lilstevie's stuff should be there as well.

I've tried updating the links on http://xdaforums.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu/Ubuntu_Install a couple of times but it keeps failing with a loss of session data error. Maybe just because I'm a fairly new user?
 
  • Like
Reactions: Sharpe351 and dvhh

Jc61990

Senior Member
Oct 7, 2007
118
1
New York
jc61990.com
Tried installing ubuntu on my SBK1 Transformer. Using OLiFE on ArchLinux x64 everything has been smooth sailing until flashing the device (using asus boot linux only)

it looks to be an error after the boot.img is sent and the device wants to go back into Phone update mode. It errors out with a USB error

Code:
[HTML][/HTML]
sending file: ./images/bootloader.bin
| 976013/976013 bytes sent
./images/bootloader.bin sent successfully
sending file: ./images/recovery.img
- 4499456/4499456 bytes sent
./images/recovery.img sent successfully
sending file: ./images/boot.img
/ 3618816/3618816 bytes sent
./images/boot.img sent successfully
Device needs to be put back into APX mode
Putting device into Nv3P Phone Update mode
Nvflash started
nvos: dcc0 open failed: 2
usb read error (71): Protocol error
uid read failed
Nvflash started
[resume mode]
failed executing command 14 NvError 0x8
command failure: partition download failed

i thought it may have had something to do with the udev rules. so i got the hw and vendor id for the device while it was in APX mode showing up as
Code:
jc61990@jclinux ~ % lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 2109:0810  
Bus 004 Device 003: ID 2109:0810  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ad:07d0 Y.C. Cable U.S.A., Inc. 
Bus 001 Device 004: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
Bus 001 Device 005: ID 1532:0024 Razer USA, Ltd Razer Mamba
Bus 001 Device 006: ID 046d:c22d Logitech, Inc. G510 Gaming Keyboard
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 003: ID 2109:3431  
Bus 003 Device 004: ID 2109:3431  
[b]Bus 003 Device 039: ID 0955:7820 NVidia Corp. [/b]
Bus 003 Device 005: ID 045e:070f Microsoft Corp.

and when the device is booted into Android, lsusb shows the device as
Code:
Bus 003 Device 039: ID 0b05:4e1f ASUSTek Computer Corp.

i have the following rules
Code:
jc61990@jclinux /etc/udev/rules.d % cat 51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="0b05",ATTR{idProduct}=="4e1f",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="0b05",ATTR{idProduct}=="4e1f",SYMLINK+="android_fastboot"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", ATTR{idProduct}=="7820", MODE="0600", OWNER="jc61990"

anyone got any idea why it keeps failing?
 

Barracuda96

Senior Member
Oct 4, 2012
62
7
Skåne
Tried to flash CWM on my TF101 by running as instructed but the script just stops like below, anyone knows why and how I can flash CWM on my TF101?

Update using ClockWorkRecoveryMod

This option will temp flash CWR, then
restore the device back after, to allow
you to use CWR to update your rom

Press any key to continue...
Put your device in APX mode then press any key
Device detected in APX mode
Putting device into Nv3P Phone Update mode
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c62024040a457
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0

sending file: ./images/transformer.bct
- 4080/4080 bytes sent
./images/transformer.bct sent successfully

After this its just stops, have been trying several times and nothing happens, have waited a long time and it just doesn't happen anything else, anyone know why?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 66
    This 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.
    25
    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
    8
    Multiboot 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 : 40c9f82c30e0fd8230c712e23f2e3597
    7
    Downloads:

    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"
    6
    Simple 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