Hi everyones...I think it's time for a new thread, previous ones were good enough to setup ubuntu on the folio but with natty, support for arm and tegra should be much improved...
Sadly, I tried to get a booting system with previous method with --dist natty but it did not worked ! I tried
Code:
sudo rootstock --fqdn nvidia-tegra --login ubuntu --password ubuntu --imagesize 16G --dist natty --serial ttyS0
from here : elinux.org/Installation_Detail
inspired from ; wiki.ubuntu.com/ARM/RootfsFromScratch
no boot, got nearly frozen soon after boot with repeated error cpu sleeping for more than 120s !
anyone ?
I haven't already tried to get natty on the folio, but I guess it would not work because of the kernel version..
Natty usually comes with 2.6.38..
But the folio comes with 2.6.32...
So I think it wouldn't be as easy as installing it on a x86/64 system...
Can you post a picture of your screen after freezing?
Or type down what's on the screen?
Hi, here's a shot done with my cam...
I used armel file for ubuntu found overthere :
elinux.org/BeagleBoardUbuntu#Natty_11.04_2
but it stucked same way...here's a snapshot !
!edit!
Code:
tar xvz ubuntu-10.10-r7-minimal-armel.tar.xz
echo "dev /dev tmpfs rw 0 0" >> ./etc/fstab
from here
lguegan.free.fr/article.php3?id_article=29
then it goes a bit further...i though i had kinda login input...naaah then every 5s it prints this :
"init: tty02 main process (xxxx) terminated with status 1"
arrg !
like I said in my post above..
I guess the problem is the kernel version which is too small for natty...
You can try to port the mach-tegra tree and some other driver parts to the newest kernel version and run natty again..
Maybe this will work...
Unfortunately I'm not owning a folio.. I just lent it from somebody, but I gave it back to him a few days ago, so I'm not able to test porting it..
why do you say kernel is not good ?
I don't understand
with correct options, rootstock should build a correct kernel, when I use armel natty image, it's natty's kernel ?
Could you briefly explain the booting process of folio and kernel issues ?
I'm downloading from github this
github.com/mblaster/linux_2.6.32_folio100
should just copy paste the arch/ tree in my / ?
see ya
No its much more complicated..
You have to be able to cross-compile your kernel..
I already explained it here http://forum.xda-developers.com/showpost.php?p=13628768&postcount=4
You have to download the source you posted above and then clone the actual source from kernel.org
For example:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.6.tar.bz2
After that you have to move the folder
Folio_source/arch/arm/mach-tegra
to
kernel.org_source/arch/arm/
And much more things..
After that you have to cross-compile it and fix some errors which may occur...
So you have to got knowledge in compiling a kernel source and in C++ programming!
Hi,
I have built natty for ubuntu but i have problems with X11 not running as expected.
No time right now to debug but will try ASAP.
Akta
Anyone tried to port this to Toshiba Folio?
I see some work here with Vega and Gtablet
http://wiki.meego.com/ARM/TEGRA2
Some video of MeeGo tablet UI.
http://www.youtube.com/watch?v=GB-nnFhGKbk&feature=player_embedded#!
Looks nice. Seems to run on our oldish 2.3.32.9 kernel. Might be worth a try to get this working.
I copy MeeGo to sdcard with dd command and from fastboot ONLY BOOTED(NOT FLASH) 2.6.32 kernel for booting from sdcard(DerArtem's) with this command(like it said in readme file):
fastboot -c "boardtype=PR root=/dev/mmcblk1p1 init=/sbin/init usb-storage.delay_use=0 rootdelay=10 tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 [email protected] [email protected] vmalloc=192M video=tegrafb usbcore.old_scheme_first=1 debug" boot boot.img
BUT
during boot I saw that sdcard is recognized,(and) first cpu stopped.(and) I'm not sure for init, it said that init isn't fond(that's ok, I unpacked boot.img and there're nothing in ramdisk folder and there're something else under init not found. Some words and numbers that I don't understand. Init is in /sbin folder, I checked. I set init position in fastboot command(init=/sbin/init) and I forgot, it said that it's try to pass "init=" and after that some strange words and numbers.
Is it problem in booting kernel but I think that isn't, I this thread ==> http://forum.xda-developers.com/showthread.php?t=899976 (post 6, wolfx) he only boots kernel.
What's the problem???
Thank's in advice!!!
Xperia Boot Menu v1.0
Disclaimer:
- Me (munjeni) is not responsible for anything related to the our project, you using our project on your own risk! If you no want to risk than don't play with Boot Menu! You can play with Boot Menu but on your own risk!
Feature:
- multiboot based on kexec
- posibility for defining: menu title, path to the kernel, path to the ramdisk, kernel cmdline
- posibility for defining max 10 menus
- autoreboot to the first kernel if menu is not moved (stop timer on menu move)
- graphic timer
Instructions:
- create folder "bootmenu", add settings.ini to these folder, modify settings.ini for your needs
- flash bootmenu using fastboot command (fastboot flash boot recovery.img)
- since internal sdcard is only supported by now, you can define only kernel and ramdisk from internal sdcard path! Make sure you define right path and make sure create folders in bootmenu on your internal sdcard
- make sure settings.ini is in internal sdcard in folder bootmenu!!!
- kexec can boot only kexec patched kernels, so your kernel need to have kexec patch!!! Complete kexec patch you can find on my git!
Simple settings.ini (example):
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-2]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-3]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-4]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-5]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-6]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-7]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-8]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-9]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
# [rom-10]
# menutitle=recovery touch black
# kernel=/sdcard/bootmenu/zImage
# ramdisk=/sdcard/bootmenu/initrd.gz
# cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Click to expand...
Click to collapse
Download:
- http://d-h.st/UXm
Kernel source code:
- https://github.com/munjeni/android_kernel_xperiago/tree/jb-dev
You're simply the best :beer: :beer: :beer:
Inviato dal mio Xperia U usando Tapatalk 4
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and my new CWM Touch Recovery v6.0.3.6 ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
00000000-05ffffff : System RAM
0005e000-008fa4c7 : Kernel text
008fc000-00f2e797 : Kernel data
06000000-06efffff : db8500-trace-area
08000000-09ffffff : System RAM
0e800000-1fdfffff : System RAM
1fe00000-1fefffff : kexec_hardboot
1ffe0000-1fffffff : ram_console
40010000-400107ff : lcpa
40010000-400107ff : dma40 I/O lcpa
Click to expand...
Click to collapse
So I am not sure about X-U
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and recovery ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
Xperia u have 512mb ram
Sent from my Xperia U using xda app-developers app
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and recovery ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
Here's the output..
And no XU has only 512 mb of ram
Boot menu download link ready, please let me know if booting!
First of all create bootmenu folder inside your internal sdcard, create settings.ini file in bootmenu folder:
Code:
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Since cmdline settings is from Xperia Go please edit these line and add cmdline for Xperia U !!!
Than create "examplerom" folder in your bootmenu folder, put initrd.gz and zImage from attachment to the example rom folder, reboot to the fastboot and flash bootmenu:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Reboot and let me know if working!
AD9295 said:
Here's the output..
And no XU has only 512 mb of ram
Click to expand...
Click to collapse
Thanks, so kexec will working I am sure Enjoy guys!
For example if you want to boot your android rom, simple extract ramdisk from boot image, create new folder in bootmenu folder for example my_stock_rom, add [rom-2 settings lines for your new rom, modify path to "my_stock_rom", use zImage from cwm.rar, use modules from cwm.rar and put into your android /system/lib/modules folder... new menu will apear in boot menu... etc Note: autoreboot is automatically set to the [rom-1] (first menu) so if you want to automatically boot "my_stock_rom" simple move them to the top of the settings.ini ... Enjoy!!!
munjeni said:
Boot menu download link ready, please let me know if booting!
First of all create bootmenu folder inside your internal sdcard, create settings.ini file in bootmenu folder:
Code:
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Since cmdline settings is from Xperia Go please edit these line and add cmdline for Xperia U !!!
Than create "examplerom" folder in your bootmenu folder, put initrd.gz and zImage from attachment to the example rom folder, reboot to the fastboot and flash bootmenu:
Reboot and let me know if working! If not working please give me output of the command "adb shell cat /proc/iomem"
Click to expand...
Click to collapse
I would like to help but I dont know hot add and modify settings.ini..
Edit: I learnt how to do that.. will post results when I get back from college.. Sorry but i have to attend today..
Another example:
Since I not sucesfully booted android from sdcard, we need to prepare ramdisk of the future sdcard rom boot, modify them to use partitions from sdcard instead of using partitions from emmc!!! Need help for them!!!
So example is:
kexec cwm which have modified partitions table (sdcard partitions) -> load them into bootmenu -> boot them -> since these cwm will load sdcard partitions we can install an rom.zip regulary to these partitions using these cwm (cwm will install android to these sdcard partition) -> rom.zip updater-script need allso modification because we need to edit for example all lines which contain for example /dev/block/mmcblk0p** and change for example to the /dev/block/loop**
Ramdisk cwm or rom need allso reparation -> /dev/block/mmcblk0p** need changes to the /dev/block/loop** since for sdcard boot we need to mount system,data,cache partitions to the /dev/loop devices.
ETC...BLABLA Thats all we need for multiboot!!!
AD9295 said:
I would like to help but I dont know hot add and modify settings.ini..
Edit: I learnt how to do that.. will post results when I get back from college.. Sorry but i have to attend today..
Click to expand...
Click to collapse
No problem mate, I am sure most experienced users will help and get them working, and post the results Good thing is we have boot menu and kexec working, so all other things will come soon, I am sure
Waiting your creations and modifications. Want to see message "sucesfully booted rom from sdcard" :laugh: First of all waiting confirmation about working Boot Menu v1.0 in Xperia U !
munjeni said:
No problem mate, I am sure most experienced users will help and get them working, and post the results Good thing is we have boot menu and kexec working, so all other things will come soon, I am sure
Waiting your creations and modifications. Want to see message "sucesfully booted rom from sdcard" :laugh: First of all waiting confirmation about working Boot Menu v1.0 in Xperia U !
Click to expand...
Click to collapse
How can I modify sdcard since its emmc,I dont understand.
How to create partitions on it for system,data,cache or this supports kernels only?
XperianPro said:
How can I modify sdcard since its emmc,I dont understand.
How to create partitions on it?
Click to expand...
Click to collapse
You no need to modify emmc! Simple create file based ext4 partition and mount them on boot time to the loop device For get these to work you need to modify ramdisk, fstab...etc of the rom
munjeni said:
Not sure if kexec working on Xperia U, I will post kernel, kernel modules, boot menu and my new CWM Touch Recovery v6.0.3.6 ramdisk for test.
Need your help, need output of the command:
adb shell cat /proc/iomem
Xperia U have 1gb ram???
Xperia Go by now have:
So I am not sure about X-U
Click to expand...
Click to collapse
i know this is too noob but does xperia go have 1 gb ram?isnt it 512m?
can i flash the attached recovery.img in an unlocked xperia u running ics??
bibhu059 said:
can i flash the attached recovery.img in an unlocked xperia u running ics??
Click to expand...
Click to collapse
No, only JB !
chessmanyaki said:
i know this is too noob but does xperia go have 1 gb ram?isnt it 512m?
Click to expand...
Click to collapse
have 512 !
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
munjeni said:
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
Click to expand...
Click to collapse
I've got to say I'm really impressed anytimes you release/post something, many thanks for your progress
I guess that, at first look, it is not working for locked bootloader, but it seems your recovery handles the boot menu and kexec thing : would it be possible to port your recovery to our locked bootloader "a la" atis' patch ? I guess we won't be able to straight boot your recovery because of its' kernel, but would it be portable to ICS kernel&codes to, lets say => load your recovery by loading ramdisk like atis', then kexec to an unsigned kernel ?
edit: partially answered myself: we need to enable kexec support therefore I guess "official kernels" don't =/
Sympnotic said:
I've got to say I'm really impressed anytimes you release/post something, many thanks for your progress
I guess that, at first look, it is not working for locked bootloader, but it seems your recovery handles the boot menu and kexec thing : would it be possible to port your recovery to our locked bootloader "a la" atis' patch ? I guess we won't be able to straight boot your recovery because of its' kernel, but would it be portable to ICS kernel&codes to, lets say => load your recovery by loading ramdisk like atis', then kexec to an unsigned kernel ?
edit: partially answered myself: we need to enable kexec support therefore I guess "official kernels" don't =/
Click to expand...
Click to collapse
Stock kernel doesn't support it. He has said it earlier himself
Yup, I read too fast, was excited about this post and I've used to read "kexec could be our way out of locked bootloader" (@Xperianpro, some of his posts)
Anyone knows if an official kernel had kexec support in the past ? Even if it's GB *not really hoping*
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16
Answer
GGgamer16 said:
So i saw this video of a guy having ubuntu 12.04(pc version) on his phone,he was running the linux server on his phone and at the same time accessing it, using androidVNC . BTW i have a samsung galaxy S 4 (sprint Version ,without knox) Running cyanogenmod 11.0 , android version 4.4.2, the kernel version is [email protected] #1 Thu Jan 9 21:12:16 PST 2014 .
I checked if my phone is loop compatible using, the following in terminal emulator : zcat /proc/config.gz | grep CONFIG_BLK_DEV_LOOP , i found it on a webpage , and i got y, that means it is a loop device, but when i ran CompleteLinuxInstaller i got into the following problem
Checking loop device ... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed : Invalid Argument
ERROR: Unable to mount the loop device
but when i did modprobe loop
it didn't find anything
so if you can help, me i am not a genius, just tell me the simplest way to fix this.
btw i want to install unbuntu 13.10 i have everything downloaded(Terminal emulator, Complete linux installer, AndroidVNC, and the 3.72gb image file)
Thank's in advance,
GGgamer16
Click to expand...
Click to collapse
I don't own that phone. And so I cannot say much about it.
But my personal advice is to take backup of everything before you proceed with any changes to your phone.
I found the following links give you an idea:
http://android.stackexchange.com/questions/25396/how-to-find-out-if-my-devices-kernel-has-loop-device-support
http://ubuntuforums.org/showthread.php?t=2189642
http://ubuntuforums.org/showthread.php?t=2193699
Keep searching Google.