yep vid fully working audi -> my tv was showing audio disabled , think a simpel switch and it should work , didnt test it yet..
Getting XBMC fully working is my own prio. then i will build a live roofs for it.
Jhinta Kernel for Lilstevie Ubuntu
- Thread starter Jhinta
- Start date
yep vid fully working audi -> my tv was showing audio disabled , think a simpel switch and it should work , didnt test it yet..
Getting XBMC fully working is my own prio. then i will build a live roofs for it.
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.
E: I don't understand why kernel (http://gitweb.lilstevie.geek.nz) with config from 2.6.36 or doesn't boot.
Last edited:
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
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
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
@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!
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
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
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.
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.
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
# 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
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.
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
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. 
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
9Dont have this tap anymore so cant support it anymore !!!
I do things manual as i want to know what has be done !
So every thing below is hardcore installation. This will give you the why and know how of things !!!
About bootimg.cfg
This file is need for creating boot.img
You can find it by unpacking a boot.img,but one is provided already.
The important part of this file is the first and last option.
The first one will say how big the image wil be, and the last is kernel cmdline.
This is also wehre you say loop= for a loop file
Pack or unpack blob files
Code:cd /tmp git clone git://github.com/AndroidRoot/BlobTools.git cd BlobTools make -j2 sudo cp blobpack /usr/bin/ sudo cp blobunpack /usr/bin/ cd ~
Unpack a boot.img
We create a folder and place a boot.img in it.
Code:mkdir ~/test cd ~/test abootimg -x boot.img
Unpacking a initrd image
Now you will have a directory with the ramdisk source files in ~/test/ramdiskCode:cd ~/test mkdir ramdisk cd ramdisk gzip -dc ../initrd.img | cpio -i
to repack it, run
for gzipCode:cd ~/test/ramdisk find . | cpio -o -H newc | gzip > ../new-initrd.img
for lzmaCode:find . | cpio -H newc -o | lzma -c > ../initram.lzm
This will give you a new-initrd.img file in ~/test/ for you to use............versions<
Go to the folder and select ALL file or folder BUT source and build !!!!
And compres it file wel be made in home.
modules are install in ubuntu in /lib/modules/
About kernel and initrd and boot.img and blob
Kernel = basic hardware installations and setup
initrd = like a ramdisk
boot.img = kernel + initrd
blob = boot.img + TF special header
Blob file you find in cwm.zip like a kernel update for android
boot.img you will find when using nvflash
kernel gets compiled from a git or source
initrd you can make your own or reuse
i will create cwm.zip to do the flashing
To do this i do.
This will give me a ubuntu.img ready for nvflash but i want cwm.Code:mkdir ~/test cd ~/test cp ~/TF101-GNU-kernel/arch/arm/boot/zImage ~/test/zImage abootimg --create ./ubuntu.img -f ./bootimg.cfg -k ./zImage -r ./initrd.img
so i do
(LNX is boot partition dont change this unless you know what your doing)Code:./blobpack kernelblob LNX ubuntu.img
Now i got a new file kernelblob that i can add to a cmw.zip file
To do this , open !!!! the cmw.zip below and remove and add the file kernelblob.
Thats it, and ready for flashing.
Rootfs
You sould be able to use any rootfs that is for arm.
you can also build a rootfs with rootstock
keep in mind a rootfs kan have diffrent types of names like ( rootfs.img.ext234 or ubuntu,dabian,linux.img.ext234 or evrey name you want it to be its just a name+ext)
If you want to relock it for oem-config ( nice first setup like name location keyboard setup) do
Code:touch /var/lib/oem-config/run
Ubuntu
Kbuntu
XBMX
So how do we even flash ?
I use nvflash directly or cwm
The easy why is just using Olife.
Keep in mind that i will never use uboot , only original bootloader of android.
So dualboot is what you need.
if you have dualboot flashed, do this.
Replaced (backup!) initrd-2.6.38.img and 2638-zImage in the kernel folder with my files,
and in Olife update your chromium kernel.
For those that want to use a loop file
Just flash this zip file
And copy the rootfs to sdcard (nand) /sdcard/linux/ubuntu.img (more will come, thats why linux/ubuntu.img)
Wifi setup
Wifi simply needs 2 files and you can get them from android space -> then copy them to Ubuntu space to /lib/firmware/
/data/misc/wifi/nvram.txt -> /lib/firmware
/data/misc/wifi/wpa_supplicant.conf -> /etc/wpa_supplicant.conf #optional
just use a root exploror to copy them to sdcard or usb ( this can alo be done when your in Ubuntu space (/system = mmcblk0p1, /data = mmcblk0p7))
and put them on the right place for Ubuntu.
Bluetooth setup
There are 3 file needed from android space, to get this,
Enable bluetooth
Rename you bluetooth name to what ever you want ( once in Ubuntu you cant change this !!!! )
Leave it on !! and boot to Ubuntu
/data/misc/bluetooth/{bcm4329.hcd,mac.txt} -> /lib/firmware
brcm_patchram_plus (lives on the net) -> /usr/sbin/brcm_patchram_plus (already in)
As last edit /etc/init.d/bsp-tf101 and correct your mac adress --bd_addr ***** (replac *** with mac !!!, mac is located in mac.txt)
.
and reboot and your done.Code:#! /bin/sh do_stop(){ #look if Board Support Package is already running PS=$(ps -A | grep " brcm_patchram_plus\>") if [ -n "$PS" ]; then echo "* Stoping Bluetooth Support Package..." killall brcm_patchram_plus fi } do_start(){ #if already started then stop first do_stop #now start all board support binaries echo "* Starting Bluetooth Support Deamon..." rfkill unblock 0 modprobe bcm4329 /usr/sbin/brcm_patchram_plus --enable_hci --baudrate 921600 --bd_addr ***** --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2& # making sure the nvtegra dev nodes have the correct permissions echo "* Setting correct permissions on nvtegra device nodes..." chmod 0666 /dev/nv* /dev/tegra_* } case $1 in start | restart) do_start ;; stop) do_stop ;; esac
Installing Tegra HEADER files ( needed when building things like XBMC )
Copy as root all folder to /usr/include/
Installing Opengl-ES
Download the Tegra drivers from Nvidia
Once downloaded unpack it and open a cmdline and go to that direction Where those files are and type,
-r = your root directeroy whey you want to install thisCode:sudo ./app*.sh --help
--abi = witch version of abi your running, to get you version run in ubuntu on TF
So when running this directy on the TF in Ubuntu you wil get thisCode:aptitude show xserver-xorg-core | grep abi
Code:sudo ./app*.sh --abi 10 -r /
Get audio working
Then open alsamixer and enableCode:sudo usermod -a -G audio sudo chmod -R 777 /dev/snd/*
playback
Left And Right speaker mixer DACL/R
Set DC input to DMIC
And sound sould work right away.
Install zram
Code:sudo wget -O /etc/init/zramswap.conf 'https://wiki.ubuntu.com/ARM/TEGRA/AC100?action=AttachFile&do=get&target=zramswap.conf'
Installing XBMC
sudo apt-get install (try installing all dependencies you can in the readme.ubuntu in xbmc folder , some will fail so just remove them) )
Code:cd ~ git clone git clone git://github.com/xbmc/xbmc.git cd xbmc ./bootstrap ./configure --enable-tegra --enable-gles --disable-openmax --disable-vdpau --disable-hal --disable-joystick --disable-debug --disable-dvdcss make -j2 sudo make install sudo apt-get install libgl1-mesa-swrast
Loop or native parition
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=/xxx/xxx
Default Kernel
files
Support
hdmi ( audio ? )
USB ( full working )
jack ( mic ? )
Opengl-ES
zram ( needs script also a most have beacuse of low ram space )
-more to come
Sources
kernel
Khronos header package
Tegra Opengl-ES drivers
Blobtools
THANKS TO:4
If you look in the wiki, there's a link to a post by me which contains a pretty detailed guide on how to compile a kernel and flash it. When you reach the stage involving abootimg, you'll need to update the config file passed to it with the -f option, and change "root=mmcblk0p8" to "root=mmcblk1p1" (or whatever partition it's installed on - you can check this by mounting it under Android/Linux then using the 'mount' command to check which device it corresponds to)
BTW, you can have a dual boot while retaining CWM - you keep CWM in the recovery partition, and modify some zip files to flash the packaged kernels for Android and Linux. (This is also the easiest way to try new kernels.) More instructions on this are in the kernel compilation guide.
-------------------------------------------------------------------------
In case anyone was wondering where I was, my TF was subject to a warranty claim (took them a month just to reconnect the LVDS cable). I'm currently in the process of repartitioning it and installing Debian armhf. Once I've got the new kernel working, I'll post a newbie friendly guide.4Kernel update
If someone is still interesting, I've merged kernel with lastest l4t nvidia souces (r16r3-rc)
Changes:
- framebuffer now fully works, switching between X and fb works.
- usb hotplug bugs fixed
- wifi disconnects fixed (used bcmdhd from cyanogenmod sources)
- I've remapped upper keys for F1-F12 scrollock, pause, ins, del.
Sources at github.com mozggg TF101-GNU-kernel
(sorry, external links blocked)
gnu.zip - for CWM flash. Includes kernel and modules. Installs on mmcblk0p8
bcm4329.tar.gz - firmwares for current bcmdhd driver and .hcd for bluetooth. Must be extracted to /lib/firmware
