yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Android Development] Geometry:
Wow, that is indeed amazing! I remember having tried an external monitor just once or twice a long time ago with horrible graphics corruption as an immediate consequence. But I guess that was not with the latest verison of the graphics drivers...

Good new indeed.

Just one question: Did you tweak anything, like xorg.conf for example? Or did you just work with the plain rootfs without any relevant modifications?
[Transformer TF300T Android Development] JoinTheRealms:
Nope no modifications, worked out of the box. By the way, do you have any idea why Gnome refuses to load? From previous tests i've noticed Gnome with compiz doesn't suffer from window corruption like xfce does. I've noticed plasma-desktop can suspend fine, but with gles-kwin window manager waking from suspend will break.

In Fact the corruption doesn't seem to be related to suspend, but to changes to the monitor. Changing monitor configuration for example causes it.
[Transformer TF300T Android Development] shenk:
dbus helper error

hi all,

able to boot the rootfs but had this error and my networking is not working.

failed to apply network settings

"failed to execute program /usr/lib/dbus-daemon-launch-helper"

anyone had this issue?

thanks

Sorry i've solved this by :

sudo chmod 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper

sudo chown root:messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper
[Transformer TF300T Android Development] SmallR2002:
I believe you only hit half the solution. Can I take a wild guess that you extracted this tarball on a non Ubuntu system?

By default tar stores group/user names and group/user numbers. When tar extracts (as root) it tries to set the group/user by finding a user of the same name.

In my case I use Gentoo (don't look at me like that) and the messagebus user is not the same numeric ID as it is within Ubuntu. The result is that tar takes root/0:messagebus:1234 and converts it to root:0/messagebus456. Of course this is a good thing in many cases but completely terrible in this case.

I re-extracted and everything runs fine. I would expect a lot of things to eventually break otherwise.

---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------

Goodness me my profile is old on here.

I should add that I have Android, XUbuntu 13.04 (from earlier in the thread, rabbit kernel) and XUbuntu 14.04 running using the new kexec kernel. A triple boot tablet. This is pretty awesome, I feel the need to go round showing it off. Amazing work guys, thank you!
[Transformer TF300T Android Development] alb-o:
you guys are the bomb.

i dont know **** about kexecboot but if i were to grab the old cb22 arch rootfs and kernel could i boot that using kexec? it requires an old bootloader, but id like to mess with the arch rootfs on my tablet without having to constantly upgrade/downgrade to use the latest ubuntu from this thread, since it works near flawlessly and is quite useful. thanks in advance.
[Transformer TF300T Android Development] SmallR2002:
OK, you may be able to do that as long as you copy the kernel in to one of the slots. If Arch boots from the kernel in this thread (menu based rabbit from a while back) then you should be OK. Just remember to unpack the blob as described.

I have 13.04 running with the old kernel I'm this thread booted via the new kexec one so it's certainly possible.
[Transformer TF300T Android Development] ch3mn3y:
Any chance for 5.1.0 katkernel with dualboot support?
[Transformer TF300T Android Development] Valantur:
Good job guys in moving this project forward. I hadn't checked the post in a while and it makes me happy to know there are people trying to make Linux work as seamlessly as possible on our TF300T!
[Transformer TF300T Android Development] Feazzu:
Hi

Can i use a 5.x ROM with "kexec-boot-menu.blob" method?

Thanks.
[Transformer TF300T Android Development] Dabba87:
Hey guys,

I realize this is a development thread but are there any updated resources or guides to getting this on my tf300t? I've flashed my own custom roms but reading through this thread it's very hard yo understand. I've seen things like franks tools and tubuntu but further reading revealed these were used for the tf201. Any help or guidance would be appreciated. I wish it was as easy as flashing through twrp.

Also at the very least, how does the tablet run as far as smoothness/laggyness compared to something like katkis/combikk? I've formatted my tablet a few times and after a week it slows down. Its okd so I'm willing to try more.
[Transformer TF300T Android Development] tux-friend:
Hi Geometry, supend is generally working in my case but the graphics corruption after wakeup and even after reboot causes some inconveniences. Therefore I tried to extract your "001video-tegra-xfce" file under the path "/etc/pm/sleep.d/". Does this script also solve graphics corruption issues after booting? And futhermore, I would like to change my general theme to "Numix". In this case, do I have simply to change the line

xfwm4_alt_theme="Greybird"

to

xfwm4_alt_theme="Numix"

Actually, I tried this already but the graphics corruption remains.

And is there anybody who found another, more elegant solution for the problem in between?

--

Many thanks

---------- Post added at 01:41 PM ---------- Previous post was at 01:29 PM ----------

Basically, yes, it should be possible. I am running 5.x ROM and xubuntu in parallel on my tablet.

I recommend that you read all the information of this post from Geometry.
[Transformer TF300T Android Development] Geometry:
I have just updated my post about the corruption issue. The way it works now you can call the script as a stand-alone via "xfwm_restore". You can associate this to a key combination to invoke it whenever necessary. But no, there is no automatic invocation after reboot. About the theme: You do not need to change the script at all. What it does is that it detects your theme then it swicthes to "Greybird" or "Bluebird" and then back to your theme. The reason for two possibilities (either "Greybird" or "Bluebird") is that it is necessary to swith to a theme that is different from the actual theme. So if the actual theme is "Bluebird" then it switches to "Greybird" before switching back. Otherwise it switches to "Geybird" and then back to the original theme.

On a related note: On the TF701T which is somwehat similar to the TF300T it turns out that the KDE windows manager KWIN works without this corruption problem. I have not tested this on the TF300T, but if you want to give it a try, it is easy to test and the instructions are here. (If "kwin_gles" gives problems you might also try "kwin", but you probably will not have hardware acceleration working in the window manager)

UPDATE: I have now tested KWIN (actually kwin_gles) in Xubuntu 14.04 on the TF300T exactly as described in the post and it seems to work perfectly, exactly as on the TF701T.
[Transformer TF300T Android Development] tux-friend:
Graphic corruption solved

Thank you very much for the response! Your stand-alone script is a very cool workaround and it works perfectly. I have assigned a button combination of my keyboard to start the script.

Thank you for this hint, too! However, I am quite sure that I won't install KDE on my tablet because it takes much more ressources and every little bit of free ram memory seems precious to me.

But maybe for other users this advice could be valuable.

--

Many thanks
[Transformer TF300T Android Development] Geometry:
Have a look at the post I linked to. It is not about installing KDE, but only about replacing xfwm4 (the xfce window manager) with kwin_gles (the GL ES version of the KDE window manager) within Xubuntu. The rest of Xubuntu remains untouched. I think the additional memory footprint is quite small. Sorry, if this was not clear from what I wrote.
[Transformer TF300T Android Development] tux-friend:
Sounds interesting! Maybe I should give it a try. But before I need to succeed with kernel compilation because I need kernel headers to get some drivers and modules ready for use.

--

Many thanks
[Transformer TF300T Android Development] tux-friend:
Finally, I succeeded to compile the kernel from source directly on my tablet. And I was also able to compile kernel headers so that I can build modules now. That's great! But it was also an adventure due to some troubles and bugs.

My recommendation to anyone who tries to compile a kernel from source according to Geometry's description

You need to get the official ASUS kernel source for Android 4.2 JB OS (version 10.6.1.27.5)

Then you can apply all the patches. With another version it won't probably work (or just partly and you maybe have to look for other workarounds).

Does anyone know if it's possible to use virtualization mode with the TF300T and create or use KVM module? I am currently trying to emulate x86 architecture to get some binaries running under the tablet. I succeeded in general by using qemu. But it's too slow for productive use. I have read that KVM could change this by enhancing the performance. Then it might be possible to use Wine or other applications which are not available for armhf yet.

I don't want to make some advertisement but is there anybody who has knowledge with the commercial product Exagear Desktop and could confirm that this software is running under xubuntu 14.04 on the TF300T?

--

Best regards

tux-friend

---------- Post added at 11:58 AM ---------- Previous post was at 11:40 AM ----------

Until now, I am still using the xfce window manager and I could also recognized some visual distortions when I use abiword or firefox browser. The distortions are characterized by missing or wrongly displayed letters which reappear if I scroll up or down.

Have anyone experienced the same issues and can the kwin_gles workaround also solve this problem?

P.S.: Despite the described trouble, I am impressed how well xubuntu is already running on my tablet. Many thanks to Geometry for the great work!
[Transformer TF300T Android Development] Geometry:
Yes, I also experience these graphics issues. Unfortunately, this seems to be a bug of the nvidia tegra driver. (It is much worse with ABI version 14, which is why i am not using that.) And, no they do not go away with using kwin_gles. I have not found any satisfactory way to avoid them. There is a suggestion here which I have tried and it seems to work, but at the price of breaking many applications, including xfce components.
[Transformer TF300T Android Development] tux-friend:
tegra video driver and graphical distortions

If it's a bug of the nvidia tegra driver then the chance is probably very low that NVIDIA will provide another update to fix this issue. Then there is only some hope that the OpenTegra driver would work on the tablet one day in the future and help to overcome this problem.

Or is there anybody who is already using the OpenTegra driver successfully?
[Transformer TF300T Android Development] JoinTheRealms:
[MENTION=6136418]Geometry[/MENTION]

Have you seen the latest update to the linux-for-tegra driver? 16.5 as of Jan 2015, shows support for X11 ABI 14 which iirc was the issue we had with 16.4?
[Transformer TF300T Android Development] tux-friend:
swap working?

Thanks to the xubuntu rootfs provided by Geometry my tablet is turning more and more into a productive machine :laugh:

However, one basic thing which is obviously not working at the moment is swap.

I checked the swap status via following commands

swapon -s

Output:

Filename	Type	Size	Used	Priority

free -h

Output:

total used free shared buffers cached

Mem: 976M 932M 43M 205M 1.3M 367M

-/+ buffers/cache: 564M 412M

Swap: 0B 0B 0B

I also tried

grep swap /etc/fstab
grep zram /etc/fstab

giving no output.

However, on the one hand I have recognized that Geometry has included zram in the kernel configuration. And on the other hand I have recognized that command "Deactivate swap" is performed during shut down sequence. Strange!

Furthermore, in my panel I have added an indicator for cpu, ram and swap usage. Untill now, the indicator for swap has never shown any activity, even there were at least two situations when I was running out of memory.

I think most people would agree, that a swap partition on SD card would be slow and will therefore not make a lot of sense (furthermore it would probably be the best way to quickly wear out the card). However zram concept seems interesting and it would allow to use memory even more effective.

Has anybody an idea how to set zram correctly so that it will be used for swap?

---------- Post added at 04:07 PM ---------- Previous post was at 03:17 PM ----------

Thanks for the great news that a new l4t driver update from nvidia is available! A little miracle come true. Never thought that this will still happen.

Hopefully, nvidia has also fixed the problem concerning visial corruptions.
[Transformer TF300T Android Development] Geometry:
[MENTION=4582979]JoinTheRealms[/MENTION]

I have also seen this update recently, but I have not yet had time to test it. (I now mostly work with my newer TF701T instead of my TF300T, which has very similar problems by the way.)

About the ABI versions: The 16.4 release (used in my Xubuntu rootfs) also had support for ABI 14, but it is too broken to be useable (see more explanation in previous posts), that is why ABI 13 is used. It remains to be seen if NVIDIA fixed this in the 16.5 release. I am somewhat sceptical given that releases previous to 16.4 also already had buggy ABI 14 support, and the bugs were not fixed in 16.4. In any case the default for Ubuntu 14.04 is ABI 15, so we would still need an outdated xserver (but from Ubuntu 13.10 rather than 13.04 as currently used).

If anybody has time to check this out, let me know!
[Transformer TF300T Android Development] fedee13:
Following this guide I could flash the kexec-boot-menu, expand the rootfs into a sdcard (with only one ext4 partition) and start both android and linux systems. But when I start xubuntu, it seems to load some thing, then some others with an [OK] at the right side but then it just does nothing, I have a black screen with a blinking cursor at the upper left corner....Any ideas?

When you say "rename "/boot/vmliuz-3.1.10" to "zImage-1" and "/boot/initrd.img-3.1.10" to "initrd-1.img" and place them there", what I did was make a copy of both files, rename them and cut-paste them in "/storage/emuldated/0/boot/", leaving the originals on the micro sd card as they were:"/boot/vmliuz-3.1.10" and "/boot/initrd.img-3.1.10". Is that right or should I delete the original ones?

Thanks!
[Transformer TF300T Android Development] tux-friend:
troubleshooting - booting process

This procedure should be fine and just leave the original files on your external sdcard under /boot exactly as they are. Actually, I am not sure if these files are still needed but I left them there and they didn't interfere with the booting process. Furthermore, if you flash your internal eMMC card and the boot folder under /storage/emuldated/0/ gets lost, then you still have the original files to start again.

According to your description the first initialization process seems to be successful. Otherwise, you wouldn't see the screen with the OKs.

However, in order to give you any more support it would be helpful to get some more details at which stage the booting process was exactly interrupted. Could you check on your external sdcard for this log file: /var/log/boot.log ? If you can find this file then just post it as attachment.
[Transformer TF300T Android Development] fedee13:
Ok, here is the boot.log attached.
[Transformer TF300T Android Development] tux-friend:
Thanks for the boot.log. I compared it with my own boot.log. There were some differences and the order of the initialization processes were not always the same. Hmmm ... but I am not sure if this is really a problem.

Here are the results about the differences:

1. Messages which were included just in your boot.log

* Starting Populate and link to /run filesystem[154G[ OK ]
* Stopping Populate and link to /run filesystem[154G[ OK ]

* Stopping flush early job output to logs[154G[ OK ]

* Starting set console font[154G[ OK ]
* Stopping set console font[154G[ OK ]

* speech-dispatcher disabled; edit /etc/default/speech-dispatcher
saned disabled; edit /etc/default/saned

* Starting Initialize Tegra Sound Card State[154G[ OK ]

* Starting Initialize Tegra Sound Card State[154G[ OK ]

* Stopping System V runlevel compatibility[154G[ OK ]

2. Messages which were included just in my own boot.log

* Starting Enabling additional executable binary formats[154G[ OK ]

* Starting crash report submission daemon[154G[ OK ]

The rest was basically the same but order was sometimes different as I said.

To be sure, I want to ask you following questions:

A) Are you using a TF300t tablet?

B) You have extracted the rootfs in an external sdcard with only one ext4 partition, correct?

C) Which command have you exactly used for extraction? And which system have you used at that time (Linux or Android)?

A long time ago, when I have installed xubuntu on my tablet, I have also experienced some troubles while booting. And as far as I can remember it was related to the system which I have used to extract the rootfs.

Anyway, your boot.log is an evidence that you are on the right way in general to get xubuntu working. So don't give up!
[Transformer TF300T Android Development] fedee13:
A) Yes, I'm using a TF300t tablet.

B) Yes, I did.

C) I used this (from Lubuntu running on my tablet):

sudo tar -zxvf xubuntu.tar.gz -C /path/sdcard

I did it on my tablet running a Lubuntu 12.04 LTS .img from internal storage from here with this kexec menu and KatKiss 4.4.4. I also did the same procedure with a gentoo distro and I could boot it up with no problem.

I also tried to boot up xubuntu using Geometry's kexec menu with the same result (black screen with blinking underscore).
[Transformer TF300T Android Development] tux-friend:
Ok, you have used a Linux system. That should be fine. While using terminal emulator in Android I have experienced troubles, even though I have used the same command for the extraction. That's why I have asked.

Concerning your problem, there are two things I can suggest:

1. If you don't mind, reformat your sdcard with ext4 filesystem again and extract the rootfs with following command:

sudo tar -zxpvf xubuntu.tar.gz -C /path/sdcard

As you can see I have added the p parameter which preserve permissions during the extraction. process.

2. Before you try no 1, make sure that the downloaded rootfs is not corrupt. If possible please check the md5sum for this purpose.

Good luck!
[Transformer TF300T Android Development] fedee13:
I just checked the md5 and it's the same, now I'm going to extract the rootfs as you instructed.
[Transformer TF300T Android Development] fedee13:
I just did that but I have the same problem as before, I end up in a black screen with a blinking underscore. :(

EDIT: added boot.log just in case.
[Transformer TF300T Android Development] tux-friend:
I am not really sure what's going wrong in your case. Maybe the more advanced users could be a better help.

But you still have some few options:

1. Use another sd card to extract the rootfs. Maybe there is something wrong with your sd card which you are currently using.

2. After extracting the attached zip file copy zImage and initrd to /storage/emulated/0/boot/ (aka "/data/media/0/boot/") on your internal eMMC. Then restart your tablet and insert the external sd card with the extracted xubuntu system in the micro sd card slot of your tablet. Hit "2" in the kexec menu during booting and see what happens (both files are working for me in order to boot xubuntu from external sd on an ext4 partition)

3. Create and update your own initrd in a chroot environment by following command:

update-initramfs -c -k 3.1.10

Before you do that you should also check that there is following file /etc/initramfs-tools/conf.d/specify_root_device with correct settings so that the root partition is indicated properly (your external sd card). Below you find two links for more information:

#8

#62

.

Actually, point 3 shouldn't be necessary if you have exactly followed the instructions of Geometry. But if nothing else is working I would even try this option as well.
[Transformer TF300T Android Development] tux-friend:
updated linux-for-tegra driver 16.5

Today, I have installed the driver update and it was successful. However, I decided to stay with the X11 ABI 13 version because I don't see any advantages to change to ABI 14. Again, nvidia missed to add support for ABI 15 which is somehow disappointing :( So, I was too enthusiastic when I have heard about the news of the updated version.

On the other hand, the new version seems to work fine. And I have the impression that the graphic system is a little bit more stable. However, graphical distortions haven't disappeared completely but it seems that there is some little improvement.

I need more time for testing and if there is some interest I can share my experience here.

---------- Post added at 11:51 PM ---------- Previous post was at 11:15 PM ----------

I have another question concerning the GL ES version of the KDE window manager: Are there further advantages of kwin_gles over xfwm4 or other features worthwhile to mention apart from the fact that it solves the graphical distortions in the window system?

I found that the package including the dependencies will consume over 150MB of disk space if you haven't installed other KDE apps or components, yet. But if you use different KDE apps anyway, required additional disk space will be much less, of course.

Furthermore, memory requirement will be a little bit higher (around 10-20 MB) compared to xfwm4 which isn't really that much. But I am curious if there are further arguments for kwin_gles.
[Transformer TF300T Android Development] J0SH1X:
do i need 4.1 jellybean for this or can i use 4.2 ?

with 4.2 i stuck at Linux mount failed. Fallback to Android
[Transformer TF300T Android Development] tux-friend:
Basically you could use any Android version as you want if you use the kexec boot option. Probably just stock ROM with locked bootloader wouldn't work. But you must extract the kernel and initrd of the Android system which you want to use and for booting xubuntu you must add an adequat Linux kernel and Linux initrd as well.

You will find everything you need to know in the earlier postings of this thread. So please check them for more information. Especially these links will be useful:

#581

#589

And if the whole topic is new for you, I recommend to start on page 56 with posting 555.

I know it seems like a lot of information but it will help you to avoid mistakes and to get a better understanding of the topic.
[Transformer TF300T Android Development] gs-crash-24-7:
Would it be possible to install it as the only os on my tablet, just on my internal flash memory?
[Transformer TF300T Android Development] ch3mn3y:
You would need to edit kernel script to look for xubuntu files on internal memory not just one folder (sprry dont remember its name). But its doable.

Sent using R800i - DiXperia 3 'Enormous'/LuPuS_GB
[Transformer TF300T Android Development] gs-crash-24-7:
Yeah I've tried to edit the kernel and it compiled than flashed it and copied the xubuntu fs to my fresh formatted data partition and tried to boot but it seems that it's impossible to boot from data. At least my tablet hang on the bootloader splash screen for more than 15 minutes, them rebooted to recovery.
[Transformer TF300T Android Development] ch3mn3y:
Xubuntu bootable from /data needs to be in specific folder. And u dont need to compile kernel as there is dualboot one for KK and Kexec for other OSes.

Sent using C6833 - AICP/GreatDevs
[Transformer TF300T Android Development] lambolighting:
First of all, has this project been abandoned? And second will it work with a TF300T or with the TF300TG only?
[Transformer TF300T Android Development] gs-crash-24-7:
The project is abandoned by the original developer as far as i know but there are still a few developers working on it.
[Transformer TF300T Android Development] ch3mn3y:
Can kexec kernel be used to boot katkiss 6.0 kernel? Won't it be a problem?