yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] jozka.1:
I will build kernel 3.1. Do I have add any special for mount loop? Can I use .config from 2.6.36?

E: I don't understand why kernel (http://gitweb.lilstevie.geek.nz) with config from 2.6.36 or doesn't boot.
[Eee Pad Transformer Android Development] Jhinta:
i thing initrd gets bypassed , you can easly test this by echo in schript

if you see it on disply its working if not initrd get bypassed
[Eee Pad Transformer Android Development] jozka.1:
I've echo commnad in init script, but wth 2.6.38 kernel I freeze on Asus Eee Pad logo.
[Eee Pad Transformer Android Development] Jhinta:
thats not mine kernel mine is 2.6.39 or higher , that one is cros kernel and with default bootloader only sdcard will work

---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------

start reading from post 1
[Eee Pad Transformer Android Development] ssciberras:
do u have any step - by step instructions on how to compile and which patches? I was going to use kernel 3.1.1 from kernel.org, and nvidia linux fior tegra drivers, but am not sure which config to use.

and i feel that most prob you did something different
[Eee Pad Transformer Android Development] Jhinta:
iḿ sending you some stuf , iḿ of a day or two realy bizy.
[Eee Pad Transformer Android Development] rmaniac:
@ssciberras did you receive anything helpful?

@Jhinta, sorry you are so slammed. Once life is not in the way, could you let me know if your current 3.1 setup is known to work on sbkv2 devices and maybe shoot me over any info or links I might need to get it going.

Thanks!
[Eee Pad Transformer Android Development] ssciberras:
i received the kernel - attached

I have an sbkv2, so i can only use a loop mounted image, but for me it is not working...

you have to change also console in boot.cfg to ttyS0

am still struggling to see why my init is not loading, it is saying uncompression error.

regards
[Eee Pad Transformer Android Development] rmaniac:
Thanks for that. There is some good stuff in there. I am also getting the same error. I am sbkv2, but I use a partition on my SD card for my linux setup. I am going to try to patch and compile the kernel myself to see if I can find some magic. Otherwise I'll go back to playing with the initrd image.
[Eee Pad Transformer Android Development] rmaniac:
In case anyone cares. I compiled my own copy of the kernel with the patches provided. It boots, I get as far as j did, but I am also having the same issue with the dock and touchscreen not working. This of course makes it pretty useless, also sound is a bit off. All of these things seem to configure at bootup, but the X11, pulse, etc don't seem to register them so they don't do much good. I may do a dist upgrade to 12.04 and see if I can blow anything up, but I have homework to do so I may have to sit back till someone with better coding skills has the time.
[Eee Pad Transformer Android Development] ssciberras:
CONFIG_MACH_HARMONY=y

# CONFIG_MACH_VENTANA is not set

CONFIG_MACH_TF101=y

is the TF 101 not a ventana board?

am adding a rootde;lay to cmdline in boot.cfg, maybe that helps
[Eee Pad Transformer Android Development] Jhinta:
Did you compile if so , did asusec build correctly, and if so can you see it in dmesg?

Verstuurd van mijn Transformer TF101 met Tapatalk
[Eee Pad Transformer Android Development] rmaniac:
Compiled fine. There is nothing about in the dmesg, that I can see.
[Eee Pad Transformer Android Development] Jhinta:
Look into asusec folder i think it doesnt compile there sould be a dmesg about it

Verstuurd van mijn Transformer TF101 met Tapatalk
[Eee Pad Transformer Android Development] lilstevie:
no the tf101 is not a ventana, just like the tf201 is not a cardhu. however they are based off them. The problem has been that asus were too lazy to change it to their own machine type and just left it as ventana.
[Eee Pad Transformer Android Development] rmaniac:
Well sir, I have a working keyboard. Nothing for the mouse or screen yet. I just slopped it together as quick as a could by adding old function back in or hard coding values. I'll see if I can get the trackpad, maybe followed by the screen going. If I do it before a decent coder does the same, then I'll post a patch. Just don't throw anything at me because it will be terrible. I can't code my way to my own ass honestly.

[ 3.361275] asusec: [asusec_init] cdev_alloc

[ 3.541408] asusec: [asusec_irq_dock_in] Dock detected

[ 3.541932] asusec: [asusec_dock_init_work_function] EP101 dock-init

[ 3.541978] asusec: [asusec_dock_init_work_function] Dock detected

[ 3.542421] i2c-core: driver [asusec] using legacy suspend method

[ 3.542461] i2c-core: driver [asusec] using legacy resume method

[ 3.985548] asusec: [asusec_reset_dock] send EC_Request

[ 4.279234] asusec: [asusec_chip_init] Model Name: ASUS-EP101-DOCK

[ 4.285479] asusec: [asusec_chip_init] EC-FW Version: EP101-0213

[ 4.296876] input: asusec as /devices/platform/tegra-i2c.1/i2c-2/2-0019/input/input1

[ 7.342610] asusec: [asusec_chip_init] touchpad and keyboard init
[Eee Pad Transformer Android Development] rmaniac:
FYI. Nobody wait on me. As amusing as it is trying to beat kernel drivers into submission; it is taking up far too much time. I must cut myself off and work on my studies. Hopefully, Jhinta or lilstevie can find time to amuse themselves with this. If I get all my exams aced, I'll come back to it. Besides, all I have to show for a few hours is working keyboard and only only because Jhinta pointed me in the right direction. :)
[Eee Pad Transformer Android Development] Jhinta:
Touchpad sould work once multitouch is gone also for touchscreen i think
[Eee Pad Transformer Android Development] ssciberras:
tried your kernel, jhinta.

it booted, this time to show two linux penguins, and then stopped.

I had changed tty yo s0, and added rootdelay to my config.
[Eee Pad Transformer Android Development] Jhinta:
stopt? like in reboot/hang/exit to terminal

also if running the first display will be black for some time 3+ min
[Eee Pad Transformer Android Development] rmaniac:
Also, if you can boot with the previous kernel, make sure you networking is setup and turn on ssh. That way you can at least see if it pings or login and check dmesg or Xorg.0.conf to see what's up, assuming it's booting but the screen is just staying dark.

Also, Jhinta's kernel is lacking dock and touch support so unless you are going to use a usb mouse/keyboard it will only do so much for you.

@Jhinta: I see where (I am assuming) you tore out all of the ASUSGetProjectID requests (since that function is not around in the current sources) and hard coded everything to match the TF101.

The easiest way to get asusec to compile is to change the CALLBACK_READY to 0 in asusec.h which seems to only remove a reference to docking_callback() which is only in drivers/power/bq20z45_battery.c. From what I can tell, that would, at most, mean that we could not get battery info from the dock, but honestly mouse and touchscreen are much higher on my list than dock battery level.

Also to get it to be compiled at all, there needs to be some consistency in the Asusec.patch. It adds INPUT_ASUSEC to the configure, uses CONFIG_INPUT_ASUSEC to decide if it will look in the asusec directory and then CONFIG_ASUSEC to decide what gets compiled in the asusec directory.

I just set it to CONFIG_INPUT_ASUSEC for all of them.

So, changing the CALLBACK_READY to 0 and the CONFIG_*ASUSEC vars to match will make it compile. At that point, we have keyboard and accel, but no trackpad or touchscreen. X11 just does not care for them. Not sure if you have any bright ideas, but getting those working would make the kernel quite usable and with 12.04 getting released this week, I could build a new base image based on it with the tegra drivers and we would have a nice little setup.

I'm just not sure where to go on the trackpad or touchscreen at this point and having an sbk2 make testing a little annoying when it blows up.
[Eee Pad Transformer Android Development] lilstevie:
tty0 or ttyS0 because ttyS0 will not output to the fbconsole, ttyS0 is serial port 0
[Eee Pad Transformer Android Development] Jhinta:
System didnt git in user space other wise , or maby this is already fixed didnt test after. also on nv-dev othere user had the same , so thats why ttyS0
[Eee Pad Transformer Android Development] rmaniac:
I found that by using tty1 I could see the boot and X would load with accel. It's weird but works on my compile anyway. It uses the same config.
[Eee Pad Transformer Android Development] Jhinta:
good to know , btw asusec working , will lookup touchpad to night ( enabled touchpad debug and its fully working as i can see in log)
[Eee Pad Transformer Android Development] rmaniac:
Yeah, not sure if you saw my earlier post. I had it compiling, keyboard worked I just could not get the touchscreen or pad going. By asusec are you meaning the screen or just the doc? I know it's somewhat tied to both. Also I hosed my C10 with a bad flash, which should be SBKv2 by all accounts, but I was able NVFlash it. Not sure how that worked, but posted about it in Q&A.
[Eee Pad Transformer Android Development] Jhinta:
Touchpad fixed

touchscreen and hdmi audio to go
[Eee Pad Transformer Android Development] ssciberras:
actually i had added rootwait, so i thin that is the reason why it is not booting at all. am changign to rootdelay

---------- Post added at 11:23 PM ---------- Previous post was at 10:51 PM ----------

still did not work.

ttyS0 keeps two pengiuns and nothing more.
[Eee Pad Transformer Android Development] Jhinta:
Change to tty1 so you that you have output en see whats going on . Also i think initrd gets bypast

Verstuurd van mijn Desire HD met Tapatalk
[Eee Pad Transformer Android Development] ssciberras:
then if initrd gets bypassed, it is useless for me. as you might remember i have an sbkv2 tf, so the only way for me to boot ubuntu is to loop mount an image file, hence the need for a custom initrd.

that explains wy both me and jozka.1 keep having the initrd uncompression error.
[Eee Pad Transformer Android Development] jozka.1:
http://xdaforums.com/showpost.php?p=25003979&postcount=1897

Work for me, but only by 2.6.36 other kernel doesn't work.

I tried edit kernels config, but without result.

Can someone please explain to me, how it works? Why I see only two penguins :D Any modules - drivers for mmc memory?
[Eee Pad Transformer Android Development] ssciberras:
why do we need to have initrd in the kernel? I suspect that the problem in our case is that there needs to be a delay before the kernel loads up the dev/mmc blocks, and is able to find the image file.
[Eee Pad Transformer Android Development] jozka.1:
I don't know why, but it works and it is enough for me :)
[Eee Pad Transformer Android Development] davewang:
is there anyway this can be done in MicroSD/SD card of 32GB? My model is only 16GB, and doing dual boot of both OS basically left me with about 8GB internal memory for each OS. I used to install alot of apps on uBuntu, so I don't think it can fulfill my usage. Any idea guys?
[Eee Pad Transformer Android Development] conizius:
Well actually was the first approach based on sd card because the internal memory was not usable. But it was way too slow to feel good (compared to the performance now).

Therefore I would not recommend that... Better use app2sd of some sort. To use the full 8gb you have to install a lot of games with extra downloaded content, right? Then you should look for a thread in this forum where a script mounts the actual sd card as /sdcard and therefore only the actual app data needs to be on the internal memory.

Edit: I should read the whole sentence... For Ubuntu the case is pretty easy:

Create a new partition on you sd and mount it as whatever you like (say /usr for example).

But don't forget to copy all the old stuff and mount it on boot with /etc/fstab

Ubuntu gives a damn shi* about where the actual applications are as long as they are mounted on the right place
[Eee Pad Transformer Android Development] ssciberras:
can you let me know how you did it?
[Eee Pad Transformer Android Development] jozka.1:
Ehm...

The method - tutorial is in the link above. ^^^
[Eee Pad Transformer Android Development] ssciberras:
can you post kernel.zip file?

thanks
[Eee Pad Transformer Android Development] jozka.1:
I have to recompile, because I have my kernel in notebook at the college - moment.

Here is it ˇˇˇ

boot.cfg

bootsize = 0x800000
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/loop0 ro quiet splash

But other kernel doesn't work, only 2.6.36.
[Eee Pad Transformer Android Development] rdnetto:
A few things I want to add to this:

This is the best approach, since keeping the most important stuff on the emmc will be much faster than moving everything to the microSD.

8 GB is plenty for an installation of Ubuntu. If you're going over this, chances are the culprit lies in your home folder, so it's just a matter saving your files somewhere else. The biggest individual set of packages I've come across is for Lyx (~260 MB), so I'd be interested to know what you're installing that's larger than that.

The folders you'll be most interested in mounting elsewhere will be /usr, /opt and /home, though you'll probably want to look at their actual sizes to get a better idea of which to move. You may want to just mount a single partition to /media/sdcard, then symlink them to folders inside it - that way you don't have to worry about dividing the space up. (Keep in mind that you'll need to use a Linux filesystem for the sdcard partition(s).)

Do *not* try to move /boot or /bin, because those contain files needed before the other partitions are mounted.
[Eee Pad Transformer Android Development] Jhinta:
What is your console= commandline

Verstuurd van mijn Desire HD met Tapatalk
[Eee Pad Transformer Android Development] conizius:
I think installing texlive-full for latex will require around 1gb :D

But yeah 8gb is pretty much. On my workhorse-laptop I got 9gb by now and I have a lot of crap installed, tons of developer libraries and some databases. Altogether /usr is taking up 6.6gb and /var is at 1.4gb where texlive is taking a huge amount of /usr and my database resides in /var.

a pretty easy way to find out what's taking up your memory is

du -hs * | sort -h

executed in whateever directory where you want to free some space (say / for the beginning ;) )
[Eee Pad Transformer Android Development] jozka.1:
The kernel 2.6.39 works!

Very thanks jhinta for your help :)

Unfortunately I have dock at the college and stuck on initramfs. Output is working, but no from init script (tested with echo, ls commnad), why?

to ssciberras:

fb.c replace to drivers/video/tegra/ and compile with TF101-linux_defconfig and CONFIG_INITRAMFS_SOURCE:=/path/to/directory/with extraht initrd.img
[Eee Pad Transformer Android Development] Jhinta:
update

Whats working-> ALL but sound:D oke how did i do the sound part :confused:
[Eee Pad Transformer Android Development] jozka.1:
Update? Source please :)
[Eee Pad Transformer Android Development] ssciberras:
again, did not work...

this time booted init, but fell back to terminal

attached pics of screen
[Eee Pad Transformer Android Development] Jhinta:
Let me know if it works

#!/bin/sh

/bin/sleep 5
mkdir -m 0755 /proc
mount -t proc proc /proc
mkdir -m 0755 /sys
mount -t sysfs sys /sys
mount -t devtmpfs devtmpfs /dev

fail() {
echo "Failed"
echo "$1"d
exec /bin/sh
}

while [ ! -e /sys/block/mmcblk0 ] ; do
echo "Waiting for MMC"
sleep 1
done

partition1=mmcblk0p8 # MMC
partition2=mmcblk1p1 # SDCARD

# Try MMC
if	[ ! -e /sys/block/mmcblk1/$partition1 ] ; then
# Mount MMC
mkdir -m 0777 /MMC
mount -t auto /dev/$partition1 /MMC
[ $? -eq 0 ] || fail "Failed to mount MMC."
fi

# Try SD
if	[ ! -e /sys/block/mmcblk1/$partition2 ] ; then
# Mount sdcard
mkdir -m 0777 /sdcard
echo "Checking SD card for errors"
dosfsck -y /dev/$partition2
mount -t vfat -o fmask=0000,dmask=0000,rw,flush,noatime,nodiratime /dev/$partition2 /sdcard
[ $? -eq 0 ] || fail "Failed to mount the SD card."
fi

#Try MMC rootfs
if [ -e /MMC/ubuntu/rootfs.ext2 ] ; then # <- rootfs file location .
mkdir -m 0755 /rfs
mount -t auto -o loop,rw /MMC/ubuntu/rootfs.ext2 /rfs
[ $? -eq 0 ] || fail "Failed to mount /rootfs"
umount -l /proc
umount -l /sys
echo "Switching to rootfs..."
exec switch_root /rfs /sbin/init
fi

#Try SD rootfs
if [ -e /sdcard/ubuntu/rootfs.ext2 ] ; then # <- rootfs file location .
mkdir -m 0755 /rfs
mount -t auto -o loop,rw /sdcard/ubuntu/rootfs.ext2 /rfs
[ $? -eq 0 ] || fail "Failed to mount /rootfs"
umount -l /proc
umount -l /sys
echo "Switching to rootfs..."
exec switch_root /rfs /sbin/init
fi
[Eee Pad Transformer Android Development] rmaniac:
Well, last I saw you made a bunch of changes to fm34_voice_processor.c and .h. I never really saw that working properly. ALSA claimed to see it, and I might have been able to use aplay with it, but pulse audio did not seem to see it and I think it was lacking a mixer.
[Eee Pad Transformer Android Development] conizius:
Uhhh please post the source and the kernel... I'm just too excited! ;)
[Eee Pad Transformer Android Development] Jhinta:
lol , when i'm home :p
[Eee Pad Transformer Android Development] conizius:
Ahhrr! Can't await it... Germany got a holiday today, therefore I have long hours to wait for it and have to fill it with bringing some devices to 12.04 :)
[Eee Pad Transformer Android Development] Jhinta:
So you have sbk2 going ???

Verstuurd van mijn HTC Desire HD met Tapatalk
[Eee Pad Transformer Android Development] jozka.1:
Yeah!

E: I'm waiting for update, I need touchpad works.

E2: I tried build rootfs with 12.04, but there wifi doesn't work and audio - 2.6.36 kernel.

Does someone have rootfs with 12.04? :)
[Eee Pad Transformer Android Development] Jhinta:
add the modules for wifi , 11.04 -> 12.04 is the same for wifi, or just update your system to 12 . also how did you fix sbk2 ?
[Eee Pad Transformer Android Development] jozka.1:
I added all modules and they are load, but don't work.

Fix? Nothing :D

I added to init script:

for:

mount /dev/mmcblk0p7 /media/

losetup /dev/loop0 /media/media/ubuntu.img

and it works.
[Eee Pad Transformer Android Development] Jhinta:
if your using the original android kernel , wifi has to be patched but doesnt mater kernel will be up to night ( no sound yet )
[Eee Pad Transformer Android Development] ssciberras:
there was a thread about this, shoala, jozka.1 and myself had managed to get sbkv2 working by mounting a loop image. theoritcally, we could have different images, and boot different flavours of linux.

http://xdaforums.com/showthread.php?t=1537566

but my machine and that of jozka behave differently, i needed to add a delay to my initrd to get it working.

---------- Post added at 05:18 PM ---------- Previous post was at 04:38 PM ----------

this works nicely on my machine. thanks a lot: can u detail the steps you had to do to get it?

and what should be working? keys on dock work, touchpad no. HDMI? Sound?

and i assume you need tegra drivers, but how can i check that they are loaded? lsmod only shows bluetooth, and wait_for_scsi
[Eee Pad Transformer Android Development] jozka.1:
Replace fb.c, compile with "TF101-linux_defconfig" and with initrd(by jhinta with added mount loop) directly in the kernel.

boot.cfg

bootsize = 0x800000
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = nvmem=128M@384M mem=1024M@0M vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 lp0_vec=8192@0x1fbed000 root=/dev/loop0 ro quiet splash
[Eee Pad Transformer Android Development] Jhinta:
mic recoding and playing working upload within 30 min

---------- Post added at 11:11 PM ---------- Previous post was at 10:18 PM ----------

Kernel <- change console=xxx to console=tty1 !!!!!!

Initrd <- This one sbk1 ONLY

Modules

Config File

Source

boot.zip - main boot

recovery.zip - recovery boot

To get sound working do this first.

After installation and up and running do

sudo usermod -a -G audio <your username here>
sudo chmod -R 777 /dev/snd/*

Then open alsamixer and enable

playback

Left And Right speaker mixer DACL/R

Set ADC input to DMIC

And sound sould work right away.

Download Khronos API Registry and copy foldersssss to /usr/include/

Make sure you have Tegra Opengl-ES driver installed

Install libgl1-mesa-swrast to get soft Open-GL ( This is not Open-GLES !!! ) needed for xbmc.

sudo apt-get install libgl1-mesa-swrast

Install zram

sudo wget -O /etc/init/zramswap.conf 'https://wiki.ubuntu.com/ARM/TEGRA/AC100?action=AttachFile&do=get&target=zramswap.conf'

Install flash ( NOT FULLY WORKING !!! also link dead !!!! )

sudo wget -O /usr/lib/mozilla/plugins/libflashplayer.so http://kotelett.no/ac100/phh/Android2.2/libflashplayer.so

Chromium browser run from command line and add to enable gles support (webgl demos)

Last time i looked ad it, it was unstable.

--use-gl=egl --ignore-gpu-blacklist

Supports

OpenGL-ES
Touchscreen
Touchpad
zram
Wifi
Bluetooth
FB-console (console=tty1)
HDMI fully supported ( sound not test )
Mic
Kexec enabled , dont know if its even working

Thanks to:

XDA & Tweakers

Google

HTC

lilstevie

Paul Burton

And Asus of course.
[Eee Pad Transformer Android Development] jozka.1:
Nice!

I'm going test it.
[Eee Pad Transformer Android Development] lilstevie:
This is pointless to add to a kernel that you are not using to kexec from, there are a few things needed for kexec to work, that have no place in a normal kernel, like disabling SMP
[Eee Pad Transformer Android Development] Jhinta:
I know , anyway tegra sould support hotplug with smp enabled did a reading about it, ill will look into that if thats even posible.

Me still learning from scrap :D
[Eee Pad Transformer Android Development] ssciberras:
if it works for you, can you upload kernel or zip file? am way from main computer, so cannot compile, but have some time to test in evening
[Eee Pad Transformer Android Development] jozka.1:
It works for me.

Sound only works with headphones or with speakers? - yes, speakers works!
[Eee Pad Transformer Android Development] MrMuffin:
Hey jozka.1 will the kernel you posted work on an sbkv2?

Edit: Ignore this post, I'm an idiot.
[Eee Pad Transformer Android Development] stonerhino28:
How do apply the new kernel?
[Eee Pad Transformer Android Development] ssciberras:
sound not working. maybe alsa conf problem, did left and right speaker mixer enable, but they remain at 0. no sound comes out.

do you have an alsa file that i can try?

otherwise touchpad, keyboard work, cannot say about accel, need to check hdmi - which for me is the most import part, as now i would be abe to use libreoffice for presentations

thanks again, wonderful job
[Eee Pad Transformer Android Development] Jhinta:
enable playback and int spk

---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------

You alrady have a minimal ubuntu? upload please
[Eee Pad Transformer Android Development] conizius:
Well trying to try jhintas 3.1 kernel. But I am still stuck at flashing (or well booting afterwards).

How do I create an working initrd for 3.1? Can anybody give me a hint?

Working with dualboot on skb1 and olife - if that's important.
[Eee Pad Transformer Android Development] Jhinta:
just download my kernel and add it to qlife kernel folder as 2638-zImage and in q flash cromium kernel under advange

if original init does not work ill post a init
[Eee Pad Transformer Android Development] conizius:
That does not work because of some silly size abootimg is complaining about.

reading config file ./boot/dualboot.cfg
reading kernel from ./kernels/zImage-jhinta-3.1
reading ramdisk from ./kernels/initrd-2.6.38.img
./tmp/linux.img: updated is too big for the Boot Image (10633216 vs 9265152 bytes)

Well only found something about this message in the source itself (abootimg.c)

562: abort_printf("%s: updated is too big for the Boot Image (%u vs %u bytes)\n", img->fname, total_size, img->size);

Oh well and the resulting linux.img is 0kb :)