yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] jrohwer:
Latest kernel config is pared down so your zImage is significantly smaller. It is now again possible to build a standard android bootimage with separate initrd and flash it, also for sbkv2 method. No need to compile into kernel. In this post

http://xdaforums.com/showpost.php?p=26789220&postcount=377

I posted a working initrd. Note that this mounts your android data partition under /mnt/androiddata. You have to make sure this path exists in your rootfs else you'll get kernel panic. Otherwise edit init script in initrd,img to your liking.
[Eee Pad Transformer Android Development] Jhinta:
Can you please test initrd in OP

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] Jhinta:
if iḿ correct my initrd has loop support by deafult but nobody's testing it , no editing needed ever just kernelcmdline correction , so test please so that i know its working
[Eee Pad Transformer Android Development] ssciberras:
did not boot on mine - mmcblk0p8 does not exist. I believe it should be mmcblk0p7

Tried my previous initrd - but somehow it still tries to mount p8

and the op initr still has lib/modules/2.6.34 not 3.1
[Eee Pad Transformer Android Development] Jhinta:
What is your kernel cmdline. About modules i know

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] ssciberras:
cmdline = nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/mmcblk0p8 ro quiet splash

ok saw the prob just now....

EDIT:

trying to boot with my initrd just now - failed again - device resource busy

trying to boot with op initrd - hoping.... hoping.... unfortunately kernel panic - not syncing: attempting to kill init! just before that, /bin/sh cannot open splash

so still no luck

EDIT AGAIN:

removed root and splash from the boot.cfg - no success
[Eee Pad Transformer Android Development] Jhinta:
like this !!!!!

nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/mmcblk0p7 rw loop=/xxxxxxxxxxxx ( and maby init=/bin/bash)

Loop or native parition

Just use my initrd but , in your config (dualboot.cfg)

You kernel cmdline would be

( if you have native root=/dev/mmblk0p8 rw.........)

( for loop support you add loop= ( location of file !!! + root= (the partition where the file is located !!)

root=/dev/mmcblk0p7 rw loop=/media/linux/ubuntu.img <- any one test this please

Default Kernel
[Eee Pad Transformer Android Development] ssciberras:
ok will do so tomorrow morning firt thing
[Eee Pad Transformer Android Development] shaola:
Hi, can someone please attache the Xorg log? i've compiled and installed this kernel into my debian instalation and i cannot get working the touch screen, even an usb mouse is not working properly, the left button is not working, in my xorg log all the devices are detected but ignored so i wanted to compare to ubuntu's one.

Thanks
[Eee Pad Transformer Android Development] jozka.1:
I tested your kernel + your initrd, but it doesn't boot.

Where is your dualboot.cfg? I used my cfg...
[Eee Pad Transformer Android Development] jrohwer:
Success! :)

But unfortunately not with your initrd. I'm getting the same initrd uncompression error we've seen earlier so I suppose it is too big (yours is 2.4 Mb) for SBKv2 devices without repartitioning the boot partition.

However I did get it to work with my own initrd which is somewhat smaller (1.9 Mb). I edited the init scripts and removed all the manual edit of setting up the loop mount. So it is now again the "default" init as shipped by ubuntu. When I now specify the loop on the cmdline it boots fine.

Note also that the initrd I use has the setup for mounting tmpfs at /run and /run/lock (which is default for Ubuntu 12.04, maybe also 11.10, not sure). Yours still has the "old" setup of /var/run and /var/lock. I can't tell whether this is important or not as I cant boot with your initrd.

Please test if it also works for your setup. If so, then we have an initrd that works for all setups (loopmount or not) and just specify in the command line!!! :D

Initrd attached. the cmdline I used is:

nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty1 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/mmcblk0p7 loop=/media/ubuntu.img ro quiet text
[Eee Pad Transformer Android Development] jrohwer:
Here you go.
[Eee Pad Transformer Android Development] Jhinta:
Nice will add if all oké to OP , tonight

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] nuovodna:
any blob ready to flash with a script?

Hi, i'm a total newbie in driver/kernel compilation and i'm scared to brick my tablet. Anyone as a prepared version of Ubuntu with Jhinta kernel integrated in Olife archive?

I'm asking for a simple procedure (like OLife wiki, a bunch of scripts) that take me in an Ubuntu 12.04 + Jhinta kernel environment.

Thanks in advance
[Eee Pad Transformer Android Development] Muchoaliento:
+1
[Eee Pad Transformer Android Development] ssciberras:
because the command line states tty1, x did not start. had to explicitly start it from commoand line, but otherwise booted. need to set lib/modules as kernel name was different.

this being done, i still had problems with wifi trackpad etc.

usb hotplug not working

Last usable package was from jozka, but keyboard not patched for all keys.
[Eee Pad Transformer Android Development] Jhinta:
for touchad you need a mt driver ubuntu 12 has mtrack

sudo apt-get install xserver-xorg-input-mtrack

and xorg.conf setting for that (OP)

what kind of problem do you have with wifi ?
[Eee Pad Transformer Android Development] ssciberras:
well, the trackpad worked with jozka.1 cwm zip file, but not with the a kernel compiled with myself and modules in place. Ditto for wifi - it is a no go.

I think i have a problem with my modules though, depmod says invalid argument each i try to load them. Tried renaming previous 3.1.10 directory, stll no success.
[Eee Pad Transformer Android Development] kenshin1388:
+2
[Eee Pad Transformer Android Development] jrohwer:
Did you put the modules from your kernel compile onto your rootfs? You won't be able to use jozka's models with your self compiled kernel. It certainly looks like a module related problem. Also make sure that the modules are in the right place:

/lib/modules/$(uname -r)

In my case uname -r for the self compile is not simply 3.1.10 but it has appended something to the effect of 3.1.10-g3748d62-dirty (most probably because modules from the staging directory have been compiled in).
[Eee Pad Transformer Android Development] rdnetto:
If you're compiling you're own kernel, I suggest you set the LOCAL_VERSION field under General Setup in 'make menuconfig' - that way you don't accidentally load the wrong set of modules (doing so will make the system very unstable).
[Eee Pad Transformer Android Development] ssciberras:
just finished all today - was a bit busy last few days.

Everything working, sort of. Modules installed - recompiled everything and made sure they were loaded properly.

Now the issues:

kb works including \ | etc

but x windows environment does not start, rather I get tty1, where I can log in and start x

if i change to tty0 as per previous jhinta post, it stops at the booting screen.

any ideas?
[Eee Pad Transformer Android Development] stonerhino28:
Ok, i have the Ubuntu.img in the /sdcard/ It boots to Ubuntu just fine. I installed the 3.1.10 kernel, and updated Ubuntu to 12.04. Everything still works but know it is saying I have less than 50 MB left on the drive. I know this is because the Ubuntu.img file is a fixed size. Is there a way to resize it from 2 GB to 5-8 GB? Also last time i tried this install on /sdcard/, i was unable to get the Tegra drivers to work. However the tegra drivers did do one thing, they disabled my wireless. Any ideas?
[Eee Pad Transformer Android Development] jrohwer:
In the command line I posted, at the end change "ro quiet text" to "ro quiet splash" and then re-make the boot image.

---------- Post added at 07:01 PM ---------- Previous post was at 06:28 PM ----------

I'm not aware of a method to do this inplace while running ubuntu, so reboot into android and copy the image file to a linux computer (either using adb or copy via wifi).

Then on the linux computer:

e2fsck -f -v ubuntu.img
resize2fs ubuntu.img 6G
e2fsck -f -v ubuntu.img

(Change 6G to the size you want).

Then copy your image file back to the TF.
[Eee Pad Transformer Android Development] ssciberras:
Remember that if u use a usb drive or otherwise, vfat partitions have a limit of 4g. I have one in ext for this reason, to backup image file occasionnally.
[Eee Pad Transformer Android Development] stonerhino28:
Ok. I got the file resized and it boots just fine. Now I need to get the Linux for Tegra drivers to work. When I run the install for the Tegra drivers everything goes smoothly until I reboot. After the reboot my wireless does not work. I also found out that the tegra drivers do not load/work. I then reloaded the 3.1.10 files in /lib/modules/ and rebooted. When it gets fully loaded the wireless works. Something else I noticed is that on every boot using Ubuntu31-patch.zip it gives a bunche of modprobe errors saying that it cant load /lib/modules/3.1.10/modules.dep. It does this on every boot regardless of Tegra drivers being loaded or the first boot after putting the ubuntu.img on /sdcard and rebooting into linux.

If some on could post their ubuntu.img with all drivers and kernel files already applied and compiled it would be a great help in trying to figure out if it is me or my machine or just the ghost in the machine that makes this not work.
[Eee Pad Transformer Android Development] kenshin1388:
I installed the kernelblob from android terminal and tried to boot Ubuntu but its not loading because I didn't add the modules before installing the kernel or something. Is there any way to fix that without having to renvflash a fresh copy of Ubuntu?
[Eee Pad Transformer Android Development] rdnetto:
Actually, the kernel supports live resizing, or at least the older ones did. You should be able to just run resize2fs from within Linux (as root). I'd suggest doing it from the console though, just to be safe.

If not, you can still run resize2fs from within Android (though I'd suggest doing it from within a chroot so you can use the version that comes with Ubuntu).

Restore the previous kernel - either from a kernelblob or via nvflash. (kernelblob is safer)
[Eee Pad Transformer Android Development] kenshin1388:
Where would I get a stock kernel blob?
[Eee Pad Transformer Android Development] jrohwer:
Would the Android kernel (I use stock ICS) also support live resizing from within Android in a chroot environment? Alternatively, do you perhaps have a statically compiled resize2fs that I could use from within Android? (Ubuntu ships with a statically compiled e2fsck.static package and I've copied the binary over to the Android partition and use it periodically to check the ubuntu image when under android).

I haven't been able to find such a statically compiled resize2fs, tried to compile my own but don't really know how to compile it static.

---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------

Regarding the problems people have been having with the tegra drivers, Ubuntu 12.04 actually ships with a package. I've just done

sudo apt-get install nvidia-tegra

and all seems to work for me, wasn't necessary to install from the L4T repository (that seems to install a whole bunch of other stuff to your rootfs which I wanted to avoid).
[Eee Pad Transformer Android Development] eng.stk:
I tried jozka.1 3.1.10 kernel+modules on lilstevie ubuntu 11.10 img and all works well.

I made a fresh Lubuntu 12.04 img with rootstock (It's very light and has a nice netbook desktop mode), chrooted to add some stuff like onboard screen keyboard and it boots using the same 3.1.10 pack. Installed modules, nvidia drivers, sound mod, zram, the works. But wireless doesn't work at all, I copied the files from Android but no luck. lsmod show no loaded modules (but they are there on /lib/modules, with folder 3.1.10 which worked on ubuntu 11.10.

I think 11.10 had ADB support, any way to get it working on 12.04, is just to painfull to get back to Android to get logs for troubleshooting.
[Eee Pad Transformer Android Development] ssciberras:
I did not tru the nvidia-tegra packages, or maybe I did but did not work for me.

Do check the version - i belive the package in the repositroes is still the old version 12. The newer 15beta would support more features - including i believe hdmi out.
[Eee Pad Transformer Android Development] ssciberras:
I am finding some differences between jhinta and jozka.1 kernels, even in their config.

Jhinta works nicely, but touchpad needs driver and xorg.conf modification. No usb hotplug

Jozka.1 kb is not patched, but touchpad and usb hotplug work.

Attached are the two configs used in compiling. Also differences as per diff

Am compiling a kernel with Jhinta's sources, with jozka.1 with modifications. will let you know if it works.

Initrd would remain the same as for jhinta's method, unless kernel becomes too big.

EDIT: Booted, kb works, touchpad works as well.

hotplug usb does not work.

during compilation of the kernel, i was asked two more questions, will check again if it makes any difference.

EDIT 2: could it be the initrd that is casuing the difference? /proc/kernel/hotplug lists nothing, should be /sbin/hotplug

ad there is no /sbin/hotplug

could jozka.1 provide his initrd? he mght have used an old jhinta version, as listed in his config
[Eee Pad Transformer Android Development] Jhinta:
Pritty intresting , jozka could you please upload your source as zip so i can look ad it .
[Eee Pad Transformer Android Development] rdnetto:
Apparently 2.6 kernels only support live resizing of ext3. You might be able to resize it and then use e2fsck to fix it, though.

Alternatively, use rootstock to create a minimal image and store it on a USB / the Android partition. You should be able to fit into ~500 MB, from memory, and it might come in handy for recovery purposes.

I assume you're referring to this package, which is outdated. It might not be a bad idea for someone to package the new one, though.

If you want to only install some of it, you're better off manually editing the installation script anyway.
[Eee Pad Transformer Android Development] jrohwer:
Yes, I was, but binary packages are shipped as nvidia-tegra:

https://launchpad.net/ubuntu/precise/armel/nvidia-tegra

Unfortunately I have no experience whatsoever in packaging Ubuntu packages, so won't be of any help here. But I will try manual installation and see how it goes. I haven't had any problems with the ubuntu-packaged version, hw accel works fine, but I haven't tried hdmi out.
[Eee Pad Transformer Android Development] kenshin1388:
Been trying to get the 3.1.10 kernel working but no matter what I do it won't find the modules. I had it setup so I could boot between the stock kernel and this. I tried to chmod them to 777, even retyped the name of the folder many times to double check. Something I'm doing wrong?

EDIT: Reflashed a fresh copy of Ubuntu and just thought about maybe the onscreen keyboard might have put in spaces. Gonna re-try getting it setup.
[Eee Pad Transformer Android Development] jrohwer:
After booting into the 3.1.10 kernel, do a "uname -r" on the command line. The modules should go into /lib/modules/xxxxx where xxxxx is the output from uname -r. The kernel may have a minor version or other string attached to the 3.1.10 base version. After modules are in the right place, do "sudo depmod -a".
[Eee Pad Transformer Android Development] kenshin1388:
I don't have a dock :(

Edit: I forgot to mention the 3.1.10 kernel freezes while booting up.
[Eee Pad Transformer Android Development] rdnetto:
Paths for the files:

/data/misc/wifi/wpa_supplicant.conf -> /etc/wpa_supplicant.conf #optional

/data/misc/wifi/nvram.txt -> /lib/firmware

/data/misc/bluetooth/{bcm4329.hcd,mac.txt} -> /lib/firmware

/system/vendor/firmware/fw_bcm4329.bin -> /lib/firmware

/system/bin/brcm_patchram_plus -> /usr/sbin/

(/system = mmcblk0p1, /data = mmcblk0p7)

wpa_supplicant.conf isn't necessary, but it's useful if you're setting it up from the terminal.

If you get "No such file or directory" when running brcm_patchram_plus, check dmesg to see if the module loaded successfully.
[Eee Pad Transformer Android Development] kenshin1388:
So is there no easy way to install this without a dock?
[Eee Pad Transformer Android Development] jrohwer:
Ubuntu has a soft keyboard (onscreen), I believe you can activate it from the login manager (lightdm) but I've never used it since I have a dock :-)
[Eee Pad Transformer Android Development] Jhinta:
if his touchpad works by default he is using asusec based one ps2 mouse and thats a rewrighten asusec driver , so does this fix usb? :confused:
[Eee Pad Transformer Android Development] ssciberras:
I could comile again, if you tell me which option to fix

EDIT

These are present in jozka.1 kernel, not in jhinta:

CONFIG_INPUT_MOUSE=y

CONFIG_MOUSE_PS2=y

CONFIG_MOUSE_PS2_ALPS=y

CONFIG_MOUSE_PS2_LOGIPS2PP=y

CONFIG_MOUSE_PS2_SYNAPTICS=y

CONFIG_MOUSE_PS2_TRACKPOINT=y

I had enabled these in my new kernel, but there is no usb hotplug. Could it be a probelm with udev from initrd? had jhinta changed his original initrd after you patched the asusec?
[Eee Pad Transformer Android Development] Jhinta:
Fore sure this is not the original asusec, its the asusec used in cromium thats Wu he has keyboard problems if that asusec fixes USB we can use that.

Curently i'm working on some other projects but will look into it

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] Character Zero:
I am wanting to update to 12.04 and load the new tegra drivers and 3.1.10 kernel. I understand everything up to flashing the kernel. Where can I get the zImage and initrd img file to load with OLiFE? The wiki link to the Unbuntu31.zip file has a kernelblob in it an I am confused on what that is. BTW, I have Ubunutu loaded on a SBKV1 Transformer. Any help would be great I have searched over all these threads and couldn't find a clear answer.
[Eee Pad Transformer Android Development] arti121:
I have the same problem with flashing a new kernel. Followed

http://xdaforums.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu/Ubuntu_Install and http://xdaforums.com/wiki/ASUS_Eee_Pad_Transformer/How_to_install_Ubuntu/Ubuntu_Kernels

but it doesn't seem to be working.
[Eee Pad Transformer Android Development] kenshin1388:
The problem is I (as I am told) need to type a command at boot, that might actually help me get this installed. I get everything where its supposed to be and have the same problem many others are getting. The modules cannot be loaded from '/lib/modules/3.1.10/modules.deb' recurring and then freezing shortly after.
[Eee Pad Transformer Android Development] Jhinta:
I cant compile nou but you simply need the modules for the kernel your using , if it failes you simply dont have the correct modules or location for that kernel

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] kenshin1388:
I followed the directions and unpacked the modules inside a new folder (3.1.10) inside of '/lib/modules/' but it throws that error still. Even chmoded the filed to 777.
[Eee Pad Transformer Android Development] kennyMC:
kenshin1388 try the file I added to this post. I had the same problems, it was a problem with the initrd.img. but now it works.
[Eee Pad Transformer Android Development] Character Zero:
How do you flash that? Is it sbk1 compatible?
[Eee Pad Transformer Android Development] Jhinta:
:crying::crying::crying::crying:

I'm selling my tab -> to get me a tegra3 tab.

So if some one can take over that would be nice
[Eee Pad Transformer Android Development] Jhinta:
how to you can read in OP you can do it by cwm file or Olife
[Eee Pad Transformer Android Development] Character Zero:
So this where I get confused. I have an sbk1 TF and I am using the dualboot method via OLiFE. What I understand is that for the dualboot method the unbuntu kernel is placed in the recovery partition. I can get CWM temporarily with OLiFE to update the Android ROM, but it saves off the ubuntu kernel, flashes CWM, and then replaces the kernel. So I am not sure I can use that method to flash a new ubuntu kernel (but I could be wrong). So it seems my options are using a zimage and initrd file but I couldn't find a clear answer on which files to use (the newest build and a initrd file that works). All the zips I can find have kernelblob files in them. I tried to flash a kernelblob but something went wrong.

I followed these instructions from the wiki:

1. Install Tegra Opengl-ES driver. Use the latest Ventana beta.

2. Install Khronos API Registry and copy folders to /usr/include/

3. Install 3.1.10 modules. Download the modulesand unzip them to /lib/modules/.

4. Download the kernel (A newer version my exist so check the Q/A thread) and flash it.

I had loaded 12.04 and then did each set in that order. For the Tegra drives i used the command line switch of -xabi 11. When I got to flashing the kernel I grabbed a zip, ripped out the kernel blob and ran this command:

sudo dd if=kernelblob of=/dev/mmcblk0p4

When I rebooted I got an error about reconfiguring the graphics drivers and then a blinking cursor. Also I couldn't get into my Android system. I was able to reload using OLiFE. So now I want to do this one step at a time. I have upgraded to 12.04, now I want to load the 3.1.10 kernel and get comfortable with that, but I have no idea what to do.
[Eee Pad Transformer Android Development] Jhinta:
Post your dmesg please

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] Character Zero:
Well I don't really have that. I reloaded and am sitting at 12.04. Just trying to understand the best way to load the kernel.
[Eee Pad Transformer Android Development] Jhinta:
Get a zImage and initrd read my OP to add it in Olive and your done, zImage and initrd you can find here ( currently working so dont realy have the files with me also OP sould have them) and install ssh and wifi before installing nvidia so can connect to it .

OP sould have cwm.zip also , just get recovery back and flash the zip file
[Eee Pad Transformer Android Development] Character Zero:
Ok I do have wifi and ssh currently working under 12.04. I will try the zimage and initrd from the OP. You have mentioned in previous posts to set "console=tty1", where do I set this?

Still the issue I expect with using CWM is where is it trying to flash the kernel? In the dualboot configuration the ubuntu kernel is in the recovery partition so CWM can't flash over itself, right?
[Eee Pad Transformer Android Development] Jhinta:
For cwm its already there , its when you create a boot.img also in OP

Verstuurd van mijn HTC One X met Tapatalk
[Eee Pad Transformer Android Development] Character Zero:
Ok thanks for your help.
[Eee Pad Transformer Android Development] zenith1111:
I'm a newbie at this and the tutorials in the wiki (and yours too) are great, but some steps may be a bit vague like this step in the install wiki: "Install Tegra Opengl-ES driver. Use the latest Ventana beta."

Probably someone already asked and I couldn't find it, but wouldn't it be possible to just save a working 12.04 *.img file with this kernel already loaded? This way the non-developers would just flash the new image instead of flashing the older image and then having to apply all the updates.
[Eee Pad Transformer Android Development] rdnetto:
It's possible, but it hasn't been done yet - that's why the OP clearly states 'not ready'. Right now it's still very much in the experimental stage.
[Eee Pad Transformer Android Development] rdnetto:
The X server crashes whenever I open Firefox/Chromium/Pidgin/Midori. Has anyone else experienced this?

I'm running Debian wheezy armhf with the R15 beta hardFP drivers.
[Eee Pad Transformer Android Development] Jhinta:
requested

files