Related
Hi
I've installed the prime 1.5 rom onto my transformer. However I need serial devices support for my electronics stuff. How would I go about compiling the kernel module using the chrooted ubuntu.
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 <[email protected]>
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 <[email protected]> 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.
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)
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"
lilstevie said:
This is running natively and from the eMMC so no µSD card required,
The video is a class2 µSD card and speeds are not an example of speeds from this kit.
Click to expand...
Click to collapse
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Finally, is this a final release, or for testing purpose only ?
If final, a step by step guide would be very welcome
Edit : Just saw there is the tag [DEV] so forget about my last question (guide)
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Nice to see the post in XDA Good work !
bud77 said:
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Click to expand...
Click to collapse
The video was taken before I was stable enough to even think about using internal memory, where as this kit is not using the µSD
and yeah you lose recovery after selecting dual boot, not much we can do about that for the time being.
poltak11 said:
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Click to expand...
Click to collapse
I started back at uni this week myself, and have been using my transformer as a netbook replacement with ubuntu. The video is using my stuff but before I had it running on the internal memory.
speed diference is massive between the class2 and internal. It was so great of a difference that I forget that it is arm now that it is on internal
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
ErGo_404 said:
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
Click to expand...
Click to collapse
yes, that is the plan anyway
lilstevie said:
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
Click to expand...
Click to collapse
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
poltak11 said:
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
Click to expand...
Click to collapse
The second battery does work, unless you get one of those dodged ones that just randomly stops charging which happened to me, with the dock connected and the battery in it refusing to charge my battery lasted 6 hours.
the layout is different to standard, UDA(User DAta partition) is 4.2GB smaller than what it was, so you have 9.99gb for android and 4.2 for ubuntu, the kernel and recovery kernels are moved up to the end of the flash as well so that they are accessible through /dev
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing. Good job!
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
aligatro2010 said:
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing.
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
Click to expand...
Click to collapse
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
lilstevie said:
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
Click to expand...
Click to collapse
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
So basically we will be able to dual boot Windows 7 and Android?
liorry said:
So basically we will be able to dual boot Windows 7 and Android?
Click to expand...
Click to collapse
No, Windows 7 doesn't have arm version. Windows 8 maybe in future, long future ....
aligatro2010 said:
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
Click to expand...
Click to collapse
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
lilstevie said:
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
Click to expand...
Click to collapse
"bcm4329_sta.bin" was already there before I even copied 2 modules and it was also loaded as module when I did modprobe. (not 100% sure about the second)That's why I thought it was conflicting with android's modules.
Wow, great work! Can't wait to try it.
Sent from my Transformer TF101 using XDA Premium App
I've probably missed something obvious.. But I get this.
file not found: linux.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
rm: cannot remove `linux.img': No such file or directory
Click to expand...
Click to collapse
After like 5 minutes of NvFlash installing stuff.
[Win32/64][Dual Boot][Mount-Loop] Tubuntu - 1 click installer SBK1 & SBK2! *2/1/2013*
* ADDED Ubuntu Raring(13.04) *
* ADDED ARCH Linux *
Tubuntu - One Click Installer for Windows
Hi, i recently been seeing myself flashing my tf101 a lot using OLiFE2. yes my main os is linux but i also use windows and came across a lot of people asking about windows verison SBK2 for ubuntu installer. I found modified version of Frankc123 tools http://forum.xda-developers.com/showthread.php?t=1760513 but it's down. so i created a new one from scratch.
thanks
lilstevie for his OLiFE scripts
wheelie app
Frankc123
kenshin1388
and a few more. (i will find there names and edit this post again)
*Name is still Pending. couldn't think of a good name when i was making this tool. suggestions are welcomed!
Disclaimer:
you know the usual stuff. use are your own risk blah blah might brick.. will not help your become rocket scientest... yea that stuff.
Note:
this was made using VS2010. package needed to run will be dot net 4.0. google is your friend
this is very alpha not all the features are implemented yet
Code:
v0.4.7:
fixed sbk1 device flashing.
v0.4.6beta:
reworked the code for loading into sync mode for sbk1 devices
basically wasted my time with version 0.4.4b & 0.4.5b due to this new update =P
v0.4.5beta:
removed --setbct parameter for sbk1 devices
v0.4.4beta:
fixed bct loader for sbk1 devices
v0.4.3beta:
fix bootloader injection for sbk1 devices
v0.4.2beta:
fixed more bugs not initiating wheelie when needed to for sbk2 devices
v0.4.1beta:
fixed syntax error for flashing kernels
v0.4beta:
added sbk1 support(not tested nor confirmed yet)
re coded flashing method
fixed kernel flashing
fixed only ubuntu boot
fixed only ubuntu/android boot
v0.3alpha:
added RootFS install only option to selected partition
added 2.6x x3maniac kernel to the mix
removed uboot kernel image.( i will not be developing on uboot yet)
reduces zip from 80mb to 50mb. quicker download for faster hacking =)
v0.2.2alpha:
fixed ubuntu/android flash.(ubuntu as default was not booting)
fixed timing issue caused with apx mode detection.
v0.2.1alpha:
added APX mode detection.(now this app will let you know if you are really in apx mode, using drivers i provided)
v0.2alpha:
added logo
added ability to for different flashes and restore back to stock
added different recovery CWM and TWRP
added kernel flashing for chromium or jhanti
fix textbox not updating with console
few bug fixes in program
v0.1a:
initial release
Known bugs:
Code:
[strike]when flashing with Ubuntu Only. kernel panic and keeps rebooting. i am working on a fix.[/strike]
program appears to not be doing anything while flashing device. if it's not frozen and window can be dragged
around it's working. wait for device to reboot. usually 15 - 20 mins to upload 1gb
Not my program bug. but should be mentioned. After you flash your device the 1st time. let Prime run until welcome
screen. then you can flash twrp to flash custom rom. Failure to do so and flashing custom rom without letting prime
run will cause boot loop in newly flashed custom rom. i havn't looked into the logcat but i'm pretty sure that the data
partion don't match or something.
if you run into any problems and you feel it might be bricked.( haven't happen to be at all using this tool) you can use http://forum.xda-developers.com/showthread.php?t=1688012 easy flasher to fix.
Instructions:
MOUNT-LOOP now possible! * 2/1/2013 *
I have now made my new kernel which supports Mount-Loop!! thanks to transformador for the suggestion.
http://goo.im/devs/x3maniac
what does this mean?
this means that you can now just place the ubuntu.img in your internal sdcard and boot the image.
How it works?
i have turned this into a blob file(can be flash with cwm or twrp). which mean you can boot into your recovery flash ubuntu-mountloop.zip. To go back to your android you would need the kernel blob that goes along with the rom your are using. http://www.mediafire.com/?labcx60jowrdx which can be found here. (this is not my link)
Need more information?
http://forum.xda-developers.com/showthread.php?t=1537566
**Useful posts**information regards to partition size
Thanks again to TomTcom for putting together instruction to get BLUETOOTH working!!!! http://forum.xda-developers.com/showthread.php?t=2128080
**FOR SBK1 devices**Follow this guide TomTcom has created! don't forget to thank him!
http://forum.xda-developers.com/showthread.php?t=2041030
**FOR SBK2 devices**
FOLLOW THIS UPDATED GUIDE [GUIDE][Win32/64][Dual Boot] For SBK2 Install of TFUbuntu for x3Maniac Thread by Kingzak34 & don't forget to thank him!!
download the prime image and have it named system.img(if not so already) and place it in the /images folder
download the ubuntu image of your choice and name it ubuntu.img and plce it in the images folder.
go into APX mode. (press volumn up & power at the same time until screen goes black) for windows try to listen for a usb connected sound( for linux type lsusb and look for nvidia(not asus))
Dual Boot A/U:
use flash from dual boot a/u option and wait for device to reboot.
Flash Recovery for Custom rom:
to flash custom rom. goto advanced option and use "flash TWRP recovery" and click "flash". the button will now say "reflash" to reflash the kernel back into the recovery partition.
Drivers:
this option is to install the drivers for APX mode.
(¯`'•.¸//( Using Custom ROM(cm, aosp, etc......))\\¸.•'´¯)this app will re-partition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the CustomRom.ZIP in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your CustomRom.ZIP. when done flashing custom rom. go back into tubuntu app and click "ReFlash" in (advanced/flash TWRP recovery) to flash the recovery back to booting ubuntu.
Screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
lilstevies Prime
http://forum.xda-developers.com/showthread.php?t=1191141
Tubuntu Image - lightweight ubuntu
Tubuntu In Action! video submitted by hugantic
Ubuntu Raring Ringtail (13.04) is up on goo.im
This is a ubuntu-core image.(this mean it has nothing)
for a quick and dirty howto check post #652
password: family
added Nano
added WPA_SUPPLICANT
added kernel supplicants(2.6.36-12.10+)
added wifi modules on boot
Image is 200M
this is a nightly development from http://cdimage.ubuntu.com/ubuntu-core/daily/20130201/
i have this up cause when 13.04 does launch i know what i'm dealing with =)
ARCH Linux for ARM (alarm)
Arch Linux - http://goo.im/devs/x3maniac 151M
More Details for How To
this is a build it yourself system.
It Boots
root password: family
Ubuntu(ubuntu.img)
Lubuntu v1.2 (12.10) - http://goo.im/devs/x3maniac 496.01 MB
only added support for 2.6.36 kernel.(if you want to use newer kernels must installed kernel and supplements)
please review all change log from previous version to see what and how much i have done
zram is broken with kernel 2.6.36 (I am working on patching this up to new zram variation)
added multi-touch support
minimize - three finger down swipe
scroll - two finger up or down
maximize - three finger up swipe
move window - 3 finger drag
right click - two finger tap
fixed boot loop when using "reboot to recovery" from android space
fixed typos on applations not starting
updated a few program forked from "raring" 13.04
removed unnecessary boot up bloat
fixed conky from dissappearing when clicking on desktop
sound works (must use alsamixer and enable DACL & DACR)
Hot plugging works!
DO NOT INSTALL NVIDIA DRIVERS!!(2.6.36.4 does not have hw acceleration)
Lubuntu V1.1-rc1 (12.10)- [download] -382mb 1.4G unrar (wip)(i don't have dock yet so some stuff can't be tested. but it's stable @ 1.2ghz)
Don't forget to download and flash the new kernel below
lots of fixes read post #236 remember to thank Serkenar!!
changed swappiness to 10
now will start on performance mode on boot(had to recompile the kernel for that)
added script in rc.local to fix sound on boot up(you will now hear a slight click noise on boot, means sound should be working)
added scripts to brighten and darken screen(can't test yet but should would with function keys on keyboard)
using newest 3.1.10 kernel forked from jhinta(i just overclocked it)
added script to turn off backlight completely when xscreensaver "blanks" screen
added initial firstboot script to re-partition file system broken: run "sudo resize2fs /dev/mmcblk0p8" (in terminal for now until i get it working again)
sound is working
added cpufreq goverenor controller(located in menu/preferences/cpu-goverenor)
added conky (auto starts with session)
changed XF86poweroff button to disable screen(instead of logoff-selection)
added adb support(jhinta kernel break it, do doesn't work. i'm looking for a fix)
removed programs that our tablet can't use(example: xbacklight)
added zram support
added cifs support(to mount window shares install cifs-utils)
fixed nvidia tegra headers(now can be installed via "software sources" and disabled if needed)
added support for ntfs read and write support
chromium fixed
added some what of a patching system. to upgrade my builds without having to reflash.
added default user "user" (password family)
fixed "waiting for network". no more waiting
removed option with onbaord on boot in favor or default user
added gnome-system-manager (much better i think)
removed extra /lib/modules/ not needed
fixed apparmor complaining issues on boot.
added kernel boot to show everything(easier to debug for me, will be removed in future release when i know it's stable)
some more stuff i can't seem to think of( just bug fixes).
kernel issue: usb stuff gotta be plugged in before you turn on device
kernel issue: touch pad not working(look at post #154 & #206 for fix)
Discussion starts from page 13: http://forum.xda-developers.com/showthread.php?t=1995157&page=13
Lubuntu (12.10)- download - 448mb zip 1.5gb unzipped -now its working, but still don't have my dock =(
version 1.0
removed ubiquity
removed oem-config-firstinstall
removed wpa-supplicant on boot in flavor of network manager(much easier)
pre-installed all packages needed to startup and run
added support for kernel 2.6x and 3.1x
hardware accereration fully working
(not working :cryingadded onboard support for login(people without dock)
added resize2fs on boot (first time) to resize ubuntu image to fill partition (6gb)
pre-installed openssh
more stuff like bug fixes.
what's not working yet:
**do not use android os to reboot to recovery - you will be stuck in recovery boot loop!**
if you happen to be stuck in recovery loop type this in terminal
Code:
sudo echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
sound
zram
aircrack
webcam(don't think this will ever work)
chromium-browser (use firefox instead for now)
this is a LXDE destop version of ubuntu http://lubuntu.net/ light weight and works pretty fast with our devices. i have not been able to fully test if this linux image is stable. currently still waiting for my keyboard to arrive. i will be making this lubuntu image better as i go.
(root password is family i changed it due to hurricane Sandy, yes i'm from NYC)
i'm in the works for my own Lubuntu Image and Arch linux. (waiting for my keyboard dock to arrive but i do have both os booted)
I use netinstaller v0.5 (smaller file size) v0.6(more bug fixes and better support for no dock)
http://forum.xda-developers.com/showthread.php?t=1852702
lilstevies ubuntu.img
http://forum.xda-developers.com/showthread.php?t=1191141
shaola Debian image
http://forum.xda-developers.com/showthread.php?t=1476835
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
[good]
2.6.36 - [cpu 1.4 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 36
glxgear - 59 fps
[stock]
2.6.36 - [cpu 1.2 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 40
glxgear - 50 fps
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/ then use tubuntu tool to flash new kernel
[whats up with 2.6.x]
clocked at 1.2ghz (for now)
hot plugging works
sound works
chrome works (enable CONFIG_SYSVIPC & CONFIG_SHMEM)
STABLE. does not have freezing issues
lid patch
hardware acceleration (not working)
** experimental NOT Stable! **
compiled with gcc 4.7
3.1.10 - xlinux.img
source - http://github.com/novaspirit
*kernel Instructions*
download kernel unzip and place in \tubuntu\images folder
copy the xlinux.img over linux.img(temp fix to load new kernel until i get the program fixed)
flash using "x3maniac 2.6 kernel" (even tho it says 2.6, your acutally uploading the new xlinux.img, which is 3.1.10)
*updated kernel 12/10/2012*
kernel image - 3.1.10-g6e2783c
kernel supplement - kernel_sup.tar.gz
download the kernel supplement file and place it on the root of the drive.
you can also wget the file
Code:
sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
unzip using root
Code:
sudo tar zxvf /kernel_sup.tar.gz
this will extract the new firmware and modules to the correct location(/lib/modules, lib/firmware)
now use my tubuntu tool copy the linux3.img to the \images\ folder and rename to xlinux.img
now flash using "x3maniac kernel" option in the advanced section.
** I will be making a tutorial when i get around to it **
*linux version*
as per a few request in this thread about a linux version. i will not be creating a linux version for there is one that works perfect!
OLiFE by lilstevie
someone then has modified the version and made it compatible with SBK2 devices using wheelie. due to OLiFE sbk2 is hard to find on this forum i have uploaded the version to my own server
OLiFE sbk2
I did not create this program so support for it will be limited.
*i don't remember where i found the thread nor who modified it. if someone knows the orginal creator please pm me and i will update to apply credit to the dev. the orginal creator contacted me josteink. thanks for his amazing work on updating oLiFe to support sbk2
Source Codes - http://www.github.com/novaspirit/
Downloads - http://goo.im/devs/x3maniac
I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.
LeoBloom. said:
I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.
Click to expand...
Click to collapse
give me a few more days and i'll come up with a good summary for you(waiting for my dock). but as for a brief one. it works really well on minimal install like lxde or gnome classic. everything does work except webcam. it's pretty stable but i've been flashing my device so much i havn't stayed on one os that long(1 day max). hardware acceleration does work on certain kernel (will be updating my programs to inject new kernels later). my goal for this program in general is to keep my transformer as a fully functional 2nd laptop and being able to swap between / backup my ubuntu as i go along trying to find the perfect build.
Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now
LeoBloom. said:
Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now
Click to expand...
Click to collapse
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see
x3maniac said:
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see
Click to expand...
Click to collapse
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.
LeoBloom. said:
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.
Click to expand...
Click to collapse
look in post #3 of lilstevies thread. OLiFE with prime. pull the system.img from there. it's going to be a bit before i get mine up on my website. 500mb
Hi!
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....
Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk
billouetaudrey said:
Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk
Click to expand...
Click to collapse
well "prime" is the ROM stock from asus.
x3maniac said:
well "prime" is the ROM stock from asus.
Click to expand...
Click to collapse
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?
billouetaudrey said:
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?
Click to expand...
Click to collapse
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps
thxxxxxx
x3maniac said:
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps
Click to expand...
Click to collapse
OK Thx I will try tommorow Thx !
Envoyé depuis mon Galaxy Nexus avec Tapatalk
i9apps said:
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....
Click to expand...
Click to collapse
follow the instructions on screen to finish the installtion process. head over to http://forum.xda-developers.com/showthread.php?t=1852702 post #1
Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk
billouetaudrey said:
Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229
x3maniac said:
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229
Click to expand...
Click to collapse
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk
billouetaudrey said:
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.
x3maniac said:
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.
Click to expand...
Click to collapse
OK so I wait because I'm not expert and don't all understand... And I'm french and it's not easy...
Envoyé depuis mon Galaxy Nexus avec Tapatalk
I recently got an ASIX AX88179 USB 3.0 to Gigabit Ethernet adapter for my Android device running CyanogenMod based on Android 5.1.1 and the 3.4.* kernel.
The drivers for the device are provided as source code and are available:
http://www.asix.com.tw/FrootAttach/driver/AX88179_178A_LINUX_DRIVER_v1.14.2_SOURCE.tar.gz
ASIX represents that the drivers are "For Android 1.x/2.x/3.x/4.x/5.x, Linux kernel 2.6.25 and later".
I attempted to compile the drivers using the CyanogenMod-included Terminal emulator App, but could not get anything to compile. It seemed that the "make" command or tool is not recognized.
I found a note in the drivers source readme file:
Code:
Prepare to build the driver, you need the Linux kernel sources installed on the
build machine, and make sure that the version of the running kernel must match
the installed kernel sources.
I found kernel sources on https://www.kernel.org/ . How do I make use of the kernel sources?
The version 3.4.* kernel is frequently updated. Should I be recompiling the driver with new, updated kernel sources every time a new kernel version is installed?
Must the drivers be compiled on the system they are to be used on?
Is there a better way to handle driver preparations or acquisitions?
This thread is for native Linux development on Galaxy A8/A8+. This means no Halium here. It's also aimed at people who know how to compile their stuff, ect., so don't complain to me about no fancy zip installer.
I have made some fixes in our DECON framebuffer driver, ect that makes TTY, and Xorg, and anything that uses the framebuffer work! (Based on @prashantp01's Quantum Quack kernel because that's what I had at the time and it's a good kernel).
I have tested this using Arch Linux ARM (ALARM), and it boots just fine!
A postmarketOS tree for the regular A8 is in the way of being merged, and I need someone to try the A8+ version.
Please provide a photo of the phone running PostmarketOS with weston on A8+!
Prebuilt zip for A8+ and A8 with postmarketOS weston (not really useful, but good for screenshot) here:
A8: https://drive.google.com/file/d/1cVamhYGmBrDVrzzcIVyCmhLHJIQ3u3Xq/view?usp=sharing
A8+: https://drive.google.com/file/d/1xe9rFu4TRzxmM9yV4lINOHOHsEQ2TD0O/view?usp=sharing
This may also be useful for other 7885 and 7885 based (7884 variants, 7904) devices as well!
What currently works on Arch (and probably on any other native linux distro):
Booting (Arch Linux sometimes hangs on "Triggering uevents" for a few minutes, sometimes boots instantly)
Screen (inc. brightness and turning on/off (due to a hacky workaround in kernel, the screen may show a corrupted screen for a split second when turning on)
Framebuffer console (TTY)
Xorg (unaccelerated)
Touchscreen
Hardware buttons
Battery indicator (detects some other stuff as batteries/charging ports too ATM)
USB OTG (Mouse, keyboard, ect)
(After adding some configs)USB SSH, and web access from PC using USB
Basically anything using Xorg (LightDM, Xfce, GNOME, KDE Plasma, Firefox, Chromium, GIMP, VLC, ect ect ect)
Anything that can use framebuffer (weston's framebuffer backend)
NOTE: This is a guide assumes you know how to do some stuff. For some help you can also reference this
Rough instructions for Arch Linux (Using prebuilt boot.img):
Partition your SD card (using PC or something) so that your second partition will contain your rootfs (the boot.imgs provided use the 2nd SD card partition as root! Change in defconfig if you are building your kernel.)
Install the generic version of ARMv8 Arch Linux ARM to the second partition of your SD card.
Install additional packages by chrooting from Android, or using USB networking
(For dual-boot) back up boot.img
Install the correct boot.img.
To boot back into Android, restore your boot.img
Prebuilt Arch Linux boot.imgs
Source code
VDavid003 said:
This thread is for native Linux development on Galaxy A8/A8+. This means no Halium here. It's also aimed at people who know how to compile their stuff, ect., so don't complain to me about no fancy zip installer.
I have made some fixes in our DECON framebuffer driver, ect that makes TTY, and Xorg, and anything that uses the framebuffer work! (Based on @prashantp01's Quantum Quack kernel because that's what I had at the time and it's a good kernel).
I have tested this using Arch Linux ARM (ALARM), and it boots just fine! A postmarketOS port will follow soon!
This may also be useful for other 7885 and 7885 based (7884 variants, 7904) devices as well!
What currently works on Arch (and probably on any other native linux distro):
Booting (Arch Linux sometimes hangs on "Triggering uevents" for a few minutes, sometimes boots instantly)
Screen (inc. brightness and turning on/off (due to a hacky workaround in kernel, the screen may show a corrupted screen for a split second when turning on)
Framebuffer console (TTY)
Xorg (unaccelerated)
Touchscreen
Hardware buttons
Battery indicator (detects some other stuff as batteries/charging ports too ATM)
USB OTG (Mouse, keyboard, ect)
(After adding some configs)USB SSH, and web access from PC using USB
Basically anything using Xorg (LightDM, Xfce, GNOME, KDE Plasma, Firefox, Chromium, GIMP, VLC, ect ect ect)
Anything that can use framebuffer (weston's framebuffer backend)
NOTE: This is a guide assumes you know how to do some stuff. For some help you can also reference this
Rough instructions for Arch Linux (Using prebuilt boot.img):
Partition your SD card (using PC or something) so that your second partition will contain your rootfs (the boot.imgs provided use the 2nd SD card partition as root! Change in defconfig if you are building your kernel.)
Install the generic version of ARMv8 Arch Linux ARM to the second partition of your SD card.
Install additional packages by chrooting from Android, or using USB networking
(For dual-boot) back up boot.img
Install the correct boot.img.
To boot back into Android, restore your boot.img
Prebuilt Arch Linux boot.imgs
Source code
Click to expand...
Click to collapse
Thanks david
VDavid003 said:
This thread is for native Linux development on Galaxy A8/A8+. This means no Halium here. It's also aimed at people who know how to compile their stuff, ect., so don't complain to me about no fancy zip installer.
I have made some fixes in our DECON framebuffer driver, ect that makes TTY, and Xorg, and anything that uses the framebuffer work! (Based on @prashantp01's Quantum Quack kernel because that's what I had at the time and it's a good kernel).
I have tested this using Arch Linux ARM (ALARM), and it boots just fine! A postmarketOS port will follow soon!
This may also be useful for other 7885 and 7885 based (7884 variants, 7904) devices as well!
What currently works on Arch (and probably on any other native linux distro):
Booting (Arch Linux sometimes hangs on "Triggering uevents" for a few minutes, sometimes boots instantly)
Screen (inc. brightness and turning on/off (due to a hacky workaround in kernel, the screen may show a corrupted screen for a split second when turning on)
Framebuffer console (TTY)
Xorg (unaccelerated)
Touchscreen
Hardware buttons
Battery indicator (detects some other stuff as batteries/charging ports too ATM)
USB OTG (Mouse, keyboard, ect)
(After adding some configs)USB SSH, and web access from PC using USB
Basically anything using Xorg (LightDM, Xfce, GNOME, KDE Plasma, Firefox, Chromium, GIMP, VLC, ect ect ect)
Anything that can use framebuffer (weston's framebuffer backend)
NOTE: This is a guide assumes you know how to do some stuff. For some help you can also reference this
Rough instructions for Arch Linux (Using prebuilt boot.img):
Partition your SD card (using PC or something) so that your second partition will contain your rootfs (the boot.imgs provided use the 2nd SD card partition as root! Change in defconfig if you are building your kernel.)
Install the generic version of ARMv8 Arch Linux ARM to the second partition of your SD card.
Install additional packages by chrooting from Android, or using USB networking
(For dual-boot) back up boot.img
Install the correct boot.img.
To boot back into Android, restore your boot.img
Prebuilt Arch Linux boot.imgs
Source code
Click to expand...
Click to collapse
So one can boot Armbian on A8+ as we do with Android box? Where is dtb for this?
p5uresh said:
So one can boot Armbian on A8+ as we do with Android box? Where is dtb for this?
Click to expand...
Click to collapse
Yes you could probably boot it. The dtb is inside the boot.img
Try installing it to an sd card, chrooting into it from android, generating an initramfs, then replacing the initramfs in the boot.img with the one you generated. (Maybe it could even work without that, wiht arch's initramfs?)
VDavid003 said:
Yes you could probably boot it. The dtb is inside the boot.img
Try installing it to an sd card, chrooting into it from android, generating an initramfs, then replacing the initramfs in the boot.img with the one you generated. (Maybe it could even work without that, wiht arch's initramfs?)
Click to expand...
Click to collapse
OK
Thanks.
postmarketOS tree on the way! Please someone send photo of A8+ running it! Info in first post!
this is absolutely amazing, thank you for the work
im very happy with gentoo linux on my phone haha
saraphiem said:
this is absolutely amazing, thank you for the work
im very happy with gentoo linux on my phone haha
Click to expand...
Click to collapse
You got gentoo to boot? How did the drivers and compatability work out? I am asking this quite seriously as I do want to port it to my own device in the future.
Please update download links
Fandroid Tech said:
You got gentoo to boot? How did the drivers and compatability work out? I am asking this quite seriously as I do want to port it to my own device in the future.
Click to expand...
Click to collapse
well, it boots, tty works as expected with a phsyical keyboard lmao
the power button interestingly triggers a reboot, openrc & sysvinit goes through the "proper" shutdown process
i wasn't able to get much more than that working, unfortunately :c
saraphiem said:
well, it boots, tty works as expected with a phsyical keyboard lmao
the power button interestingly triggers a reboot, openrc & sysvinit goes through the "proper" shutdown process
i wasn't able to get much more than that working, unfortunately :c
Click to expand...
Click to collapse
I tried running it in a chroot, running gentoo on an 10 year old armhf cpu was hell in itself. The bigger problem was trying to update an old system. The closest anybody has gotten to gentoo mobile is sharkbait os, but that was just a chroot I think.
Fandroid Tech said:
I tried running it in a chroot, running gentoo on an 10 year old armhf cpu was hell in itself. The bigger problem was trying to update an old system. The closest anybody has gotten to gentoo mobile is sharkbait os, but that was just a chroot I think.
Click to expand...
Click to collapse
haha sure does take a while to compile things