yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] shanegru:
i dont think this works on my nvflash version of the tablet.. ive tryed.. i even went back to stock..they say katkriss and this works..but i like the rayman roms..

guess im giving up...hard to beleive that a nvflash tablet.. this wont work on...someone let me know.. also if you say a certain rom works.. can you do a benchmark? i mean i seen alot of roms score half the score that raymans roms score..even though they appeared to be fast and fliud...
[Eee Pad Transformer Android Development] vietchinh:
Uh.. Wromg place?

Well benchmark arent good.

If you feel fast and fluid choose that rom. If not choose other.
[Eee Pad Transformer Android Development] TravellingGuy:
Debian unstable and hardware acceleration

Thanks to shaola's thread about building your own image (http://xdaforums.com/showthread.php?t=1476835) and jrohwer rootbind method of installing Linux, I've successfully built Debian sid (unstable) and have it running on my TF101.

One thing that confounds me, however, is hardware acceleration. For the life of me I can't get it working.

I DO have the Nvidia Tegra drivers installed and working (confirmed by the Xorg.0.log), using the download from the Nvidia site (https://developer.nvidia.com/linux-tegra).

Does anyone have hardware acceleration working? What mesa packages are required? If you have it working and are using one of the Ubuntu images around, can you provide me with your mesa packages you have installed? I'm confused about whether GLES is required, whether we need to use software rendering (swrast package, as this wiki page seems to suggest, but maybe it's old...http://xdaforums.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu/Ubuntu_Install), and what other packages or configuration is necessary. There's not a lot of concrete info on that bit of the process.

And, what's the best way to test that hardware acceleration is working? es2_info? When I run es2_info, I get:

libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: GLX: failed to load GLX
Error: eglInitialize() failed

What confuses me is, the tegra drivers explicitly disable GLX and DRI and DRI2 modules in the xorg.conf. Color me confused. :)

On another note, I'm documenting in detail my progress and steps and also documenting all my issues/questions. With shaola's Debian image no longer available from his post, would anyone find it useful if I started a thread with my Debian image available for anyone?
[Eee Pad Transformer Android Development] zachf714:
Does anybody have an xfce/xubuntu image they are willing to share
[Eee Pad Transformer Android Development] steveeJ:
the Linux 4 tegra drivers come without opengl support. look at the libraries they provide, and notice that they don't include libglx. they come with libegl and libgles1/2, so that is what you will get hardware acceleration for. I'm building a rootfs myself, but based on gentoo. i have fiddled around with this for a while now. right now, the support for egl accelerated desktop environment is being in development by gnome using clutter with egl acceleration, and kde with egl acceleration in kwin. but nothing seems to be ready for production use.

we could start a new thread for hardware acceleration on native Linux. i would share more detailed information on this!
[Eee Pad Transformer Android Development] zachf714:
It seems on 4.3 the chmod needs to be different because when booting the image I chose it was in RO mode and is every time I boot it in that image or any other linux image on 4.3
[Eee Pad Transformer Android Development] vietchinh:
Mine boot in RW with modified blob in kernel zip. It easy to do. Just open the blob and change the rw to RO done. Or u mean something else then tell me :D
[Eee Pad Transformer Android Development] TravellingGuy:
A new thread would be a good idea. I'm sure we're not the only ones working this out. :) I'll go and create one right now.
[Eee Pad Transformer Android Development] szigeza:
Hi TravellingGuy!

Could you share your debian image?
[Eee Pad Transformer Android Development] TravellingGuy:
http://xdaforums.com/showthread.php?p=44977299

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

Hey szigeza.

I'll start a new thread with my steps and a download of my Debian image. I need to create a new one for public consumption.
[Eee Pad Transformer Android Development] shark11:
Hi guys,

When I run busybox mount -o loop /sdcard/ubuntu.img /mnt/ubuntu it fails and I got an error which says mount: mounting /sdcard/ubuntu.img on /mnt/ubuntu failed: Block device required. I have no idea why it fails because as I know -o loop should handle this problem.

Rooted: yes

ubuntu.img: Lubuntu 12.04

Android: 4.0.3

Kernel: 2.6.39.4

Tomorrow I'm gonna try with rootfs ubuntu, but this error is quite annoying,
[Eee Pad Transformer Android Development] mpcjanssen:
Sounds like a corrupted ubuntu image file.
[Eee Pad Transformer Android Development] shark11:
Same error with different image file. I think I ruined something.
[Eee Pad Transformer Android Development] jrohwer:
Which busybox are you using? Have you maybe tried a different busybox, or maybe a different version?
[Eee Pad Transformer Android Development] jrohwer:
I will answer you in detail in the new thread you created. Short version: I have hw accelleration working but you don't seem to have (according to your logs there). More detail in that reply.
[Eee Pad Transformer Android Development] jrohwer:
KDE has for a few releases already shipped with a window manager compiled with GLES. You just have to instruct your system to run kwin_gles instead of the normal kwin (e.g. by setting the env variable KDEWM=kwin_gles). This works perfectly on my Ubuntu 13.04 and I can get desktop effects (e.g. cube, etc) all working.
[Eee Pad Transformer Android Development] jrohwer:
This can't have anything to do with 4.2 vs 4.3. The Linux kernel mounts the partition mmcblk0p7 and then bind-mounts the /linuxroot directory on that partition. It does not even *see* the android kernel.

Are you running Ubuntu or Arch? Ubuntu re-mounts the partition rw during the boot process but I have had reports that this does not happen in Arch (don't run Arch myself). So you might want to unpack the boot image, change command line to rw and then repack as suggested by vietchinh a few posts back.
[Eee Pad Transformer Android Development] zachf714:
An older raring image, do you have an updated one
[Eee Pad Transformer Android Development] jrohwer:
Unfortunately not, I created my own with the debootstrap method of shaola but now there is tons of other stuff installed and set up already, so I no longer have a "clean" one :(
[Eee Pad Transformer Android Development] zachf714:
Oh OK :) I can do my own

---------- Post added at 09:17 PM ---------- Previous post was at 08:17 PM ----------

How do I unpack the kernel and make it boot RW
[Eee Pad Transformer Android Development] zachf714:
Got RW working .. how do I get trackpad working
[Eee Pad Transformer Android Development] jrohwer:
Install xserver-xorg-input-mtrack or something to that effect. You need the mtrack driver. Put the attached file into /etc/X11/xorg.conf.d (rename to elantech-mtrack.conf). Restart X.
[Eee Pad Transformer Android Development] zachf714:
I dont have an xorg.conf or an xorg.conf.d

Edit - I got it fixed thanks :)
[Eee Pad Transformer Android Development] El Quedro:
I have tried the Net install and the Lubuntu 12.04 image and both are working fine.

However, at the startup I get an 'unrecoverable fsck error' error. Linux suggests that I should repair my filesystem. I don't think that is a good idea, because the filesystem is shared with Android.

Is there an easy way to skip this error? Maybe we should mount it as an ext4 filesystem instead of ext2?
[Eee Pad Transformer Android Development] jrohwer:
The filesystem should be mounted ext4. Is yours mounted ext2? Where?
[Eee Pad Transformer Android Development] mpcjanssen:
I have got tubuntu working with this. I think the bind solution is very elegant. However I am having stability issues. It seems to be especially while using Chrome where the system just hangs. I have tried to set max cpu to 1.2 ghz but that doesn't seem to help. Anyone having similar experience? Fwiw with android I can easily over clock to 1.4 ghz.
[Eee Pad Transformer Android Development] jrohwer:
Was it working previously with the "normal" tubuntu install (loopmount)? Have you installed the Nvidia tegra drivers/firmware for hardware acceleration? I don't think it's the overclock. I have overclocked mine to 1.5 ghz and never had stability issues.
[Eee Pad Transformer Android Development] mpcjanssen:
I didn't notice any problems with the normal install (which was on a separate partition which is not loopmount AFAIK) although I didn't give that a big test. I have investigated a bit further and it seems that no matter what I try, max CPU is always set to 1.6GHz, cpufreq-set (from cpufrequtils doesn't do anything)

How can I limit the CPU to 1.5GHz or lower?
[Eee Pad Transformer Android Development] El Quedro:
The message is like this:

After that i press I(gnore) and everything just works..

Or did I forget something to run?
[Eee Pad Transformer Android Development] mpcjanssen:
The fact that it refers to the ext2 superblock doesn't mean it's mounted as ext2. Ext2 and Ext3 are very similar (ext3 having journalling). The fact that the system is using fsck.ext3 suggests it's correctly identifying it as an ext3 partition. If you boot into linux (or into an Android shell) a mount command should confirm it is mounted as ext3.

It seems that your partition is actually damaged so the fact that it's working fine is more luck than anything else and it might not keep working. You could try the manual fsck with the alternate superblock as suggested.

If that doesn't work you could make a nandroid backup (which will take a while as it includes the linux install as well) and then restore the nandroid backup. This should reformat your partitions fixing the problem.

How do you switch off your tablet or switch to linux, do you properly reboot or shutdown or do you just long press power? The second way can lead to partition corruption although on ext3 it's been ages since I have seen anything that needed a manual fsck to fix.
[Eee Pad Transformer Android Development] jrohwer:
Place the following lines in /etc/default/cpufrequtils (under linux):

# Defaults for cpufrequtils init script

# Set ENABLE to "true" to let the script run at boot time.
#
# eg: ENABLE="true"
# GOVERNOR="ondemand"
# MAX_SPEED=1000
# MIN_SPEED=500

ENABLE="true"
GOVERNOR="interactive"
MAX_SPEED="1504000"
MIN_SPEED="0"

Change the MAX_SPEED to whatever you want. Reboot and it should be good to go. you can test current values with cpufreq-info.
[Eee Pad Transformer Android Development] mpcjanssen:
That should have been something I could have found by RTFM-ing, but thanks for the quick answer. I have put max_cpu back to the stock 1.2 GHz just to judge stability.

Thanks
[Eee Pad Transformer Android Development] El Quedro:
I am using KatKiss 4.2.2 and by default FSync is not included. So, I believe something went wrong there. I do always reboot my tablet normally to 'recovery'. But I did had to hard reboot when a linux install failed. So, maybe something went wrong there..

I am installing FSync now and I will try to repair my filesystem (I do not know how just yet.).

Thanks for your reply
[Eee Pad Transformer Android Development] mpcjanssen:
With max CPU set to stock (1.2GHz) and interactive governor, stability seems fine. I will slowly increase the overclocking from there. It might be an idea to add a kernel version with stock overclocking in OP because I almost gave up on this version because initially it was so unstable.
[Eee Pad Transformer Android Development] jrohwer:
Running KatKiss 4.2.2 as well but have always run fsync_on. The added protection against data loss is just worth it for me, compared to the slight gain in performance with fsync off. I've had the occasional random reboot on my KatKiss ROM and it rebooted just fine where I've heard reports of filesystem corruption when fsync was off.

To repair your filesystem you could do a nandroid backup and restore as suggested by mpcjanssen.

Alternatively, if you don't want to format /data you can try and repair it. I have statically compiled e2fsck. I'm attaching it here. First download gunzip the file. Reboot your TF into recovery. I'm assuming you have adb working and a PC to connect to your tab. Then in recovery you can push e2fsck.static to /tmp on your TF. Then do "adb shell" and then

cd /tmp
chmod +x e2fsck.static
./e2fsck.static

This should allow you to check and possibly fix the /data partition (/dev/block/mmcblk0p7).

N.B. Make sure that /data is not mounted in recovery when you are doing this!!! Running e2fsck on a mounted file system will lead to corruption!!!

Of course this assumes you are somewhat familiar with adb and with the Linux command line, but if you aren't I would not attempt to fix/recover the file system in this way... Good luck :) Anyway do a nandroid in recovery first, before attempting any of this.
[Eee Pad Transformer Android Development] El Quedro:
Thanks for multiple solutions :)

I had made a nandroid backup before I started installing linux, so I will recover that first. After that I will install FSync. And then, install Linux again.
[Eee Pad Transformer Android Development] El Quedro:
Thanks jrohwer, the nandroid backup worked perfecty! My system will now boot without any filesystem warnings.

Now I have to figure out why my dock stops working after a couple of minutes.. very annoying..

[edit]

Does anyone know a solution for the dock problem? It does not matter if I boot linux without the dock..
[Eee Pad Transformer Android Development] vietchinh:
Im kinda curious. Is there any ground breaking things discoverd over past months?
[Eee Pad Transformer Android Development] jrohwer:
No - still have not been able to patch the overclock code into Sni's kernel (he fixed the USB and framebuffer). So I'm still running the kernel in the OP as it is faster and I'm not too bothered about the USB hotplug not working (it works when present from boot). I haven't had much time but will try and look at the OC code again in the coming weeks :fingers-crossed:
[Eee Pad Transformer Android Development] vietchinh:
Im currently fiddiling with the open gl :\. As my linux expierence is well amateur. Let say kinda bad, but im looking into on getting 720 p smooth and working. Currently: Sound lag!. urgh.

Good luck :)

edit What sheduler does this kernel use? And how do change them. I found some sourced that BFQ works better on ubuntu.
[Eee Pad Transformer Android Development] jrohwer:
The kernel has noop and cfq schedulers compiled in, with default to cfq. If you want any other schedulers, you would have to recompile the kernel yourself from source.

You can see the current scheduler by typing in a terminal (as root):

cat /sys/block/mmcblk0/queue/scheduler

To change the scheduler (e.g. to noop) you type (again as root):

echo noop > /sys/block/mmcblk0/queue/scheduler

etc. etc.

This is the scheduler for your internal EMMC (mmcblk0). To change the scheduler for your microsd, replace mmcblk0 with mmcblk1.
[Eee Pad Transformer Android Development] jrohwer:
New kernel

New kernel for rootbind with USB hotplug fixed and framebuffer fixed ! :)

See post #3 here: http://xdaforums.com/showpost.php?p=43177640&postcount=3
[Eee Pad Transformer Android Development] Kingzak34:
Nice ! Thank you !

I'm just begining of using Ubuntu again on my tab so excellent ! :D
[Eee Pad Transformer Android Development] shanegru:
ok i got lubuntu to work.. can only seem to login as gues.. but i dont know the password to get su.. can you guys post all passwords for these images posted under the transform link in the post plz..
[Eee Pad Transformer Android Development] Kingzak34:
Please, post in right thread next time ( I mean ubuntu one there's nothing related with the kernel )

Anyway, the username is user and password is family ( Be aware of QWERTY layout )

Envoyé depuis mon Transformer TF101 avec Tapatalk 4
[Eee Pad Transformer Android Development] shanegru:
ok i got lubuntu on there kind of.. still tons of boot errors..i have to watch the load screen and press i for ignore all these dumb errors..it loads.. most of the time.. . yes i can login to guest..sometimes the desktop is blank.. like only a background screen and nothing else..but heres the problem..the dock keyboard.. like 99% of time wont work..i am very new to linux...on my lubuntu install.. the root password is ubuntu not root or family..seing the keyboard wont work.. and i cant install the modules without my dock keyboard working...if i had a onscreen keyboard..i guess most of problems would be fixed..but it does seem to crash alot...so in lubuntu how i use or turn on onscreen keyboard? btw i use stock rom.. and lubuntu.. and the rootbind 9.
[Eee Pad Transformer Android Development] prog19:
I think the better is to download the ubuntu 13.04 core image and then follow the tutorial called "installing gnome core " from here in xda. You can chose any DE you like
[Eee Pad Transformer Android Development] TravellingGuy:
Awesome, thanks jrohwer. I'm going to give my Debian unstable install another try.

Your supplied modules packages seem to be missing some of the modules that were in your original modules package (from post #1), specifically the bcm4329.ko.
[Eee Pad Transformer Android Development] jrohwer:
The new kernel has the wifi module compiled in so no need to load it separately. Also, it now uses the bcmdhd driver from cyanogenmod (no longer the bcm4329 driver) as this is more stable. You can get the firmware from Sni's post (linked in my post) if you haven't got it. The modules I supplied are all the modules you'll need - the rest is compiled into the kernel.
[Eee Pad Transformer Android Development] JoinTheRealms:
How can i convince you guys to move to the tf700 when/ if you upgrade your tablets? :) Our port is very good, we just need more of you guys to join in the fun!
[Eee Pad Transformer Android Development] Kingzak34:
1GB Ram isnt it a bit small for performance ratio ? That's the only thing I find bad for the TF700 ? ( Sorry for off topic BTW )
[Eee Pad Transformer Android Development] Kingzak34:
[MENTION=3753391]jrohwer[/MENTION] I finally switched to your rootbind method. Should say that's really a good kernel !

It may take some try to boot ( sometimes backscreen directly after ASUS logo, maybe i should try 1.0Ghz one.

But it's really amazing ! :)

BTW, do you know if we can use the core rootf here http://cdimage.ubuntu.com/ubuntu-core/releases/13.10/release/

directly in rootbind ? Cause I tried but it didnt boot ( Nothing more than usual kernel boot messages )
[Eee Pad Transformer Android Development] zachf714:
You have to make it tf compatible :)
[Eee Pad Transformer Android Development] jrohwer:
The increased boot time is due to the fact that the kernel is LZMA compressed which takes longer to decompress than GZIP but compresses better, so you can fit more into the boot image.

I've also had the black screen sometimes directly after ASUS logo, but then long-pressing the power button and waiting for reboot usually fixes it. It only happens about 1 in every 10 boots for me. It is still better for me to run this OC'ed kernel than 1.0 because it is faster :) And once it is up and running I've found it to be really stable.

BTW as soon as I try to OC any higher I get this black screen after the ASUS logo all the time. This also happens if I use *EXACTLY* the same frequencies and voltages as for Jhinta's kernel which OC'ed fine to 1.6 GHz! I am really puzzled by this but have given up after literally hours and hours of work. Glad I could get it to 1.2 at all...

I haven't looked at 13.10, not gotten around to upgrading my system, still running 13.04 here. Guess I've spend too much time trying to hack the kernel :)
[Eee Pad Transformer Android Development] TravellingGuy:
Thanks, it wasn't working because the interface was coming up as wlan1, not wlan0, so I assumed it was a module problem. :)

Having another issue, "cfg80211-error wl_cfg80211_hang : In : fw crash eventing" when it's trying to bring up the interface, but I see there's lots of hits on that error in Google, so will debug. I may have extra firmwares beyond what Sni provided.
[Eee Pad Transformer Android Development] Kingzak34:
I'm maybe dumb, but I cant get wifi working on last one.

What I did :

Extracting modules winthin android with adb shell ( modules are in /data/linuxroot/lib/modules/3.1.10-12-gf6ea477 )

Booting my raring core img then logging and type sudo depmod -a

Then reboot.

Now I typed wpa_supplicant -B -c /etc/wpa_supplicant.conf -iwlan0

and got this : http://cjoint.com/13nv/CKltcTmykAm_img_20131111_184759.jpg
[Eee Pad Transformer Android Development] TravellingGuy:
I was getting the same error. The problem is, it's trying to load nvram_4329.txt, but in Sni's bcm4329.tar.gz package, it's nvram.txt. Discovered this by looking at dmesg. Make a copy of nvram.txt, name the copy nvram_4329.txt and that fixed it for me.

As well, for some reason, it was bringing up my interface as wlan1, not wlan0, so theck that as well.
[Eee Pad Transformer Android Development] Kingzak34:
Thanks for answer, I'll take a look :)
[Eee Pad Transformer Android Development] jrohwer:
You can fix this by editing /etc/udev/rules.d/70-persistent-net.rules and removing the entry for wlan0 and wlan1. The updated driver causes the kernel to see a different address and thus assign a new interface name. When you reboot and the address/interface combo is not present in the file, it gets automatically recreated/appended/incremented.

I have never seen this and get no such wifi error in my syslog. You aren't by any chance still loading the bcm4329.ko module from the old kernel which may be conflicing?
[Eee Pad Transformer Android Development] jrohwer:
Sorry only read this post now. Ignore my other message re teh bcm4329.ko module. For wlan0 vs wlan1 see above :)
[Eee Pad Transformer Android Development] Kingzak34:
Not solving anything for me, still says that wlan0 doesnt exist.

And it's not wlan1 cause in /etc/udev/rules.d/70-persistent-net.rules the wifi mac adress correspond to wlan0.

Nevermind, just saw jrohwer message
[Eee Pad Transformer Android Development] kenshin1388:
I cant seem to get the tubuntu image that i have to boot. it eventually just hangs up but always at the same point in the boot process. Can someone post a link to an image that will work?
[Eee Pad Transformer Android Development] Kingzak34:
File was recreated successfully, with mac adress present in nvram.txt ( and in nvram_4329.txt so ) ( That doesnt corresponding to the one in android 4.3 BTW ) And still got same errors.

Here's a picture

http://cjoint.com/13nv/CKlxr7eiH3k_img_20131111_231121.jpg
[Eee Pad Transformer Android Development] jrohwer:
The 70-persistent-net.rules lists wlan0 but you are trying to run wpa_supplicant with "-iwlan1". Retry with -iwlan0 :)

There is a curiosity that the mac address picked up by the udev file (00904c112233) is not the same as the one that is actually assigned to the wifi interface and listed with "ifconfig" (mine starts with 04:46:65:...). The latter corresponds also to android 4.3. It appears that the mac address as set in nvram_4329.txt is not applied and nvram_override does not work, so it always comes up with the "burnt in" mac address on the chip.

Anyway, deleting all wlan* entries from 70-persistent-net.rules will work, rebooting then will set the wlan interface to wlan0.
[Eee Pad Transformer Android Development] Kingzak34:
The first command with lot of errors ( Invalid argument and "cfg80211-error wl_cfg80211_hang : In : fw crash eventing") is with wlan0, I just tried wlan1 for curiosity :P

And that's what I done, I deleted all lines then rebooted then tried with wlan0 without success. ( My mac adress begin with 04:46 but with 00:90 in nvram.txt and so in udev file )

Anyway, I would say to you, thanks for your support :)