Post Reply

[DEV] ubuntu on the transformer

OP lilstevie

28th September 2011, 03:24 PM   |  #1  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
This is my kit for running ubuntu 11.04 on the ASUS Transformer.

THIS IS NOT A NEWBIE SUPPORT THREAD, NON DEV QUESTIONS AND HELP ME HELP ME KIND OF POSTS ARE NOT WELCOME IN THIS THREAD, THIS THREAD IS FOR DEVELOPMENT RELATED POSTS ONLY

This thread is to replace old thread for dev information here. Use that thread for newbie support and non development related discussion in relation to ubuntu on the transformer.

This is running natively and from the eMMC so no µSD card required, at the moment only linux is supported, but a windows of the kit is coming soon.

This video shows ubuntu running on the transformer, it is slower than what is installed with this flash pack. The video is a class2 µSD card and speeds are not an example of speeds from this kit.

Updates will be available in .deb form at some point.

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.


Ubuntu flash pack for the ASUS transformer
------------------------------------------------------------------

(c) 2011 Steven Barker <lilstevie@lilstevie.geek.nz>

This package should have only been linked to from
http://rootzwiki.com/showthread.php?...he-transformer
or http://forum.xda-developers.com/show...p?p=16097869if you
got the links to this package from anywhere but that forumpost
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
------------------------------------------------------------------

Before using this pack back up any data that you may have on your
device, this method is destructive to data, and will wipe
everything. If you plan on dual-booting with android you will need
to download a full system like prime and put the images (system.img
boot.img recovery.img) in images/

This package does not include the ubuntu rootfs. You should have
already downloaded this from the link located on this forum post
located http://rootzwiki.com/showthread.php?...he-transformer
or http://forum.xda-developers.com/show...p?p=16097869if you
haven't downloaded it yet it is 950MB so start it downloading
and grab a coffee. Decompress the gzipped tar to images/

With that taken care of, here are the instructions for use:

1) select whether you want to dual boot, and which OS you want as
your default.

2) make absolutely sure that you have backed up your data, everything
past this point is going to destroy your data.

3) run the appropriate sh for the choice you have made in step 1

flash-purelinux.sh for a pure ubuntu setup, this is no android
recovery is ubuntu single user mode.

flash-linux-android.sh for installing android and linux dual boot
with android as the default OS. To boot into linux hold power+vol-down
until prompted on screen to press vol-up.

flash-linux.sh for installing android and linux in dual boot with
android and linux, linux is the default OS, to boot into android
hold power+vol-down until prompted on screen to press vol-up.

flash-android.sh for installing android only, no linux, use this to restore
back to a android only state, this will retain the blobs-be-gone enhancement.

restore-default.sh for reverting to a factory state, this restores the emmc
layout back to how it was before running any of the scripts in this pack.

4) Boot into linux, oem-config will run giving you initial setup. For this
you will need either the keyoard dock, or to use adb.

5) To use the onscreen keyboard you need to attach the usb cable to your
computer and wait for it to boot to the language selection screen.
Make sure not to disconnect the cable from your transformer while you are
using the keyboard during initial setup.

Connect to the device with adb shell. once connected execute "DISPLAY=:0 onboard"

The onscreen keyboard will appear.

6) Enjoy the new life you have with ubuntu on your transformer.

7) Once on the internet you may like to add the tegra ppa
Last edited by oka1; 3rd November 2011 at 05:26 PM. Reason: grammer
The Following 14 Users Say Thank You to lilstevie For This Useful Post: [ View ]
28th September 2011, 03:25 PM   |  #2  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Reserved 1
The Following User Says Thank You to lilstevie For This Useful Post: [ View ]
28th September 2011, 03:26 PM   |  #3  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Reserved 2
The Following User Says Thank You to lilstevie For This Useful Post: [ View ]
28th September 2011, 03:26 PM   |  #4  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Reserved 3
The Following User Says Thank You to lilstevie For This Useful Post: [ View ]
28th September 2011, 03:27 PM   |  #5  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Reserved 4
The Following User Says Thank You to lilstevie For This Useful Post: [ View ]
28th September 2011, 03:51 PM   |  #6  
jerdog's Avatar
Developer Committee / OEM Relations / XDA Portal Team - Harbinger of Doom
Flag Gallifrey
Thanks Meter: 4,275
 
6,007 posts
Join Date:Joined: May 2007
More
Quote:
Originally Posted by yalkowni

Why can't we look to other tablets to get the wifi and hardware execl

Sent from my SGH-T959 using XDA App

This is a development thread - and the OP has requested that development happen in it - not Mobile Phone User Support Services For Ungrateful Nerds.

Anything not development, or useful to development, will be removed.
The Following 5 Users Say Thank You to jerdog For This Useful Post: [ View ]
28th September 2011, 05:07 PM   |  #7  
Member
Thanks Meter: 16
 
81 posts
Join Date:Joined: Jul 2011
There is some rather good information about wireless and bluetooth in bcm4329 using the original kernel on the following two pages:

http://htc-linux.org/wiki/index.php?title=LeoWifi
http://htc-linux.org/wiki/index.php?.../Leo/Bluetooth

With this information I was able to connect to wireless networks through Network Manager and I was also able to use BT. Still did not test Dial Up Network through Bluetooth in Network Manager.

I've forked lilstevie's github kernel and applied the patch to make Network Manager work. You can find it in branch wireless/bcm4329 of the following repository:

git://github.com/vhda/linux_kernel_TF101.git

I understand that you are working in a 2.6.38 kernel where this no longer applies. Could someone share the repository link?
The Following User Says Thank You to vhda For This Useful Post: [ View ]
28th September 2011, 06:10 PM   |  #8  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Quote:
Originally Posted by vhda

There is some rather good information about wireless and bluetooth in bcm4329 using the original kernel on the following two pages:

http://htc-linux.org/wiki/index.php?title=LeoWifi
http://htc-linux.org/wiki/index.php?.../Leo/Bluetooth

With this information I was able to connect to wireless networks through Network Manager and I was also able to use BT. Still did not test Dial Up Network through Bluetooth in Network Manager.

The bluetooth stuff is what I have been testing out, and is included as part of the BSP for the next revision of the rootfs.

As for the NM patch, did wifi work through the network manager, because AFAIK if WICD does not work, NM won't.

Quote:
Originally Posted by vhda

I've forked lilstevie's github kernel and applied the patch to make Network Manager work. You can find it in branch wireless/bcm4329 of the following repository:

git://github.com/vhda/linux_kernel_TF101.git

I understand that you are working in a 2.6.38 kernel where this no longer applies. Could someone share the repository link?

sure https://github.com/lilstevie/uboot-tegra and https://github.com/lilstevie/CrOS-Hybrid-Kernel

I am not going to post any further instructions other than
Code:
 [device]
type=hsmmc
instance=3

[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=./images/u-boot.bin

[partition]
name=MBR
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=ENV
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=uim
id=7
type=data
allocation_policy=sequential
filesystem_type=ext2
size=41943040
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=./images/u-boot.img

[partition]
name=UBT
id=8
type=data
allocation_policy=sequential
filesystem_type=basic
size=-1
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0

[partition]
name=MPT
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
partition_attribute=0
allocation_attribute=8
percent_reserved=0
being the required flash config, I am specifically being vague because as stated in the other thread, I WILL NOT SUPPORT THIS CONFIGURATION at this point in time
28th September 2011, 11:23 PM   |  #9  
Member
Thanks Meter: 16
 
81 posts
Join Date:Joined: Jul 2011
Quote:
Originally Posted by lilstevie

The bluetooth stuff is what I have been testing out, and is included as part of the BSP for the next revision of the rootfs.

Following the steps in the page I copied above I was able to make BT connections. NM is not able to automatically detect the DUN configuration of my mobile phone, but I don't think that is related with the driver.
Don't know if this still applies in 2.6.38.

Quote:
Originally Posted by lilstevie

As for the NM patch, did wifi work through the network manager, because AFAIK if WICD does not work, NM won't.

Yep. I'm answering from Linux in TF connected through NM. I can see other networks and my personal is hidden and it still connects automatically.
But I do have to run everything as root. If I don't, this happens:

Code:
$ host www.google
net.c:142: socket() failed: Permission denied
net.c:142: socket() failed: Permission denied
host: can't find either v4 or v6 networking
Tried the obvious solution and added myself to netdev group, but doesn't seem to work. Still did no analysed this part too much. It can also be related with selinux, apparmor or anything else...

Quote:
Originally Posted by lilstevie

sure https://github.com/lilstevie/uboot-tegra and https://github.com/lilstevie/CrOS-Hybrid-Kernel

I am not going to post any further instructions other than
[...]
being the required flash config, I am specifically being vague because as stated in the other thread, I WILL NOT SUPPORT THIS CONFIGURATION at this point in time

Don't worry. I'm already seeing that this is probably too much sand for my truck (is this expression valid in english?). I do not intend to use uboot at this time and will wait for you guys to finish that development to learn from the end result. I'm hoping there is not special patch applied to the kernel for uboot support so that I can use it as I am using the current one.
Thanks for the clues anyway. I may try to play around with uboot if I give up on the kernel stuff
29th September 2011, 01:29 AM   |  #10  
lilstevie's Avatar
OP Senior Recognized Developer
Thanks Meter: 1,032
 
1,332 posts
Join Date:Joined: Apr 2009
Donate to Me
More
Quote:
Originally Posted by vhda

Following the steps in the page I copied above I was able to make BT connections. NM is not able to automatically detect the DUN configuration of my mobile phone, but I don't think that is related with the driver.
Don't know if this still applies in 2.6.38.

Ah, I think this is related to which firmware you use, some are worse than others. On both 2.6.38 and 2.6.36 I can get bluetooth PAN working (that is how my BT devices share their networking) AFAIK PAN and DUN share the same general idea


Quote:
Originally Posted by vhda

Yep. I'm answering from Linux in TF connected through NM. I can see other networks and my personal is hidden and it still connects automatically.
But I do have to run everything as root. If I don't, this happens:

Code:
$ host www.google
net.c:142: socket() failed: Permission denied
net.c:142: socket() failed: Permission denied
host: can't find either v4 or v6 networking
Tried the obvious solution and added myself to netdev group, but doesn't seem to work. Still did no analysed this part too much. It can also be related with selinux, apparmor or anything else...

ok, if the patch is actually working this time, do a pull request and I will merge it, I believe we talked about this in the past but you weren't sure about it working. As for needing to run everything as root, check your kernel config for android paranoid networking, you will probably find that it is set.

Quote:
Originally Posted by vhda

Don't worry. I'm already seeing that this is probably too much sand for my truck (is this expression valid in english?). I do not intend to use uboot at this time and will wait for you guys to finish that development to learn from the end result. I'm hoping there is not special patch applied to the kernel for uboot support so that I can use it as I am using the current one.
Thanks for the clues anyway. I may try to play around with uboot if I give up on the kernel stuff

At present the 2 kernels are not compatible with each others bootloader, I am working on trying to figure this problem out, and hopefully when it is they will both work on u-boot and vice versa

The Following User Says Thank You to lilstevie For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes