[00:01] OK, that's a good pile. 'fun' might be a bit strong :-) === mythos_ is now known as mythos [00:34] doko_: is three a reason why networking doesn't work inside the trusty schroot in your image? [00:34] wookey: Wants a valid resolv.conf? [00:35] which I expect schroot to sort out for me on chroot entry [00:35] looks like that clever stuff may be turned off [00:36] right. It's got the same static one the extrernal chroot has [00:38] OK. that's better === TheMuso` is now known as TheMuso === ping__ is now known as kiss [08:53] I have development board with Android preloaded on it. I want to run the Ubuntu desktop version on it. What steps I need to perform? [08:53] Please suggest me [09:00] I have development board with Android preloaded on it. I want to run the Ubuntu desktop version on it. What steps I need to perform? [09:00] Please suggest me [09:36] I have development board with Android preloaded on it. I want to run the Ubuntu desktop version on it. What steps I need to perform? [09:36] Please suggest me [09:48] abhishek___: what board? [09:48] IFC6410 [09:49] shadeslayer: I have IFC6410 board with Android pre-loaded on it [09:49] shadeslayer: I have source code of Android ......downloaded from codeaurora [09:50] shadeslayer: I want to run Ubuntu desktop on it? [09:50] shadeslayer: can you please suggest me what steps to follow? [09:52] abhishek___: start with compiling the kernel that comes with it, pack a ubuntu ARM initramfs, combine the two together to create a flashable image, create a standard ubuntu image ( just the ubuntu-standard package) and then flash all of that and try to boot it? [09:54] shadeslayer: I have compiled the kernel .....(Also, I can pic the zImage from Android images available to me) [09:54] not quite [09:54] you'll probably have to enable various other kernel options [09:54] shadeslayer: from where to get the Ubuntu ARM initramfs ? [09:55] abhishek___: you'll have to make one, I usually run mkinitramfs in a ubuntu arm chroot [09:55] shadeslayer: Ok ....I will compile the kernel all by myself and will create the zImage === doko_ is now known as doko [09:56] shadeslayer: can you please explain [09:57] explain what [09:57] shadeslayer, update-initramfs ... never use mkinitramfs directly [09:57] I usually run mkinitramfs in a ubuntu arm chroot [09:58] ogra_: oh, does mkinitramfs eat kittens? [09:58] it misses a lot [09:58] ah I see [09:58] its only one step in building an ubuntu initrd (update-initramfs calls it in the end) [09:58] abhishek___: just debootstrap a ubuntu arm chroot [09:58] and then chroot into it [09:58] call update-initramfs [09:59] or crab an ubuntu-core tarball [09:59] *grab [09:59] or that ^ [09:59] ( must be something new, I haven't followed ARM stuff in the last 6 months :) [09:59] what is new ? ubuntu-core ? [09:59] its 3 years old or so [09:59] Ubuntu core tarball can be picked from https://wiki.ubuntu.com/Core [10:00] oh okay, first time I'm hearing of it :S [10:00] well, you need to fiddle with qemu-user/static if you want to chroot into it [10:00] ogra_ : from where to pic the tarball [10:00] so qemu-debootstrap is probably the better choice since that does everything for you [10:01] abhishek___, there should be links on the wikipage [10:02] ogra_ : can you please link the traces [10:02] ? [10:02] ogra_ : I have kernel image ...compiled for my board [10:02] http://cdimage.ubuntu.com/ubuntu-core/releases/13.10/release/ ? [10:02] now from where to get the initramfs [10:02] you will likely need to rebuild it woith many android options dropped [10:02] ^^ [10:03] you need to create a chroot or use a core tarball, chroot into it (with /sys, /dev and /proc bindmounted ... and then call update-initramfs [10:03] Ok.....I have kernel image compiled for my board [10:03] no you don't [10:04] you will likely need to rebuild it woith many android options dropped [10:04] yes, recompile it with android dropped [10:04] ok ....I will recompile with android dropped [10:04] * shadeslayer has to go, cya [10:05] ogra_: I also require the bootloader ? [10:05] indeed, that is what loads your kernel and initrd [10:06] ogra_ : Android images uses fastboot\ [10:06] thats fine [10:06] ogra_ : can I use that to load the Ubuntu [10:06] yes, you need to use abootimg to create a boot.img file from your kernel and initrd [10:07] that one you can feed to fastboot [10:08] ogra_ : So, I have kernel image (fresly compiled for my board) and Ubuntu core tarball .....I will pack those to create boot.img image [10:08] no [10:08] you need to create an initrd first [10:08] ogra_ : How to create initrd ? [10:08] a) compile the kernel with a config that works under ubuntu [10:08] b) create an initrd.img [10:08] ok [10:08] c) create a boot.img using abootimg [10:09] how to create initrd.img [10:09] d) flash the boot.img to the right place so fastboot will find it [10:09] e) put the ubuntu-core tarball in place so the initrd can find it and boot into it [10:10] abhishek___, that was explained to you a few times now [10:10] (how to create an initrd) [10:10] for more details please look at documentation of the different tools [10:11] initrd.img using update-initramfs ??? [10:12] If I flash the boot.img in the boot sector (using: fastboot flash boot boot.img) ..... [10:12] ogra_: ubuntu used cavium model for arm64 work? [10:13] hrw, no idea [10:13] hrw, ask infinity [10:13] ogra_ : I also require the recovery.img, system.img images ... [10:13] ogra_: mkey, thanks [10:15] ogra_ : will I am able to boot the board into ubuntu desktop using the steps explained by you? ....I think I also require the recovery.img and system.img image .....is it not required? [10:16] ogra_ : you gave me step "e) put the ubuntu-core tarball in place so the initrd can find it and boot into it" [10:17] ogra_ : Please tell me .....I am new to this activity ? [10:23] abhishek___, why do you care for e) before even having done a) ? [10:23] (which might take you days anyway) [10:24] expect that you need to read a lot of documentation and dont expect to be dont within a week or two if you havent done this before ... this is not a beginner task and will require you a lot of time and learning [10:25] ogra_ : I have read on the web that if Android boot.img is wrong ...then it will boot from the recovery image ....... [10:25] yes, thats what the bootloader might do ... depends on how the vendor created it [10:26] but recovery or system or all the other android stuff is unrelated [10:26] ogra_ : so, if i flash the ubuntu boot.img in the boot sector and boot the board ...then Android will boot from the recovery image ....and then again i will be in Android [10:26] so make sure to have a working boot.img [10:27] try to find out whats wrong using the right android debugging tools and fix that [10:27] ogra_ : My problem is ...I don't have uboot (standard bootloader) ... [10:27] you dont need uboot [10:27] just create a proper boot.img [10:27] ogra_ : So, I don't require bootloader (u-boot) [10:27] you have a bootloader already [10:28] If I am able to create the correct boot.img ....then I am able to boot the uBuntu on it ? [10:28] ok .....what abt the GUI ? [10:29] stop juping that far ahead, lets talk in one or two weeks about GUIs ... get it booting first [10:29] ogra_ : can you please give me your email-id ?? .......I will try to follow the steps as mentioned by you .....and will ask you for further suggestions ..... [10:29] ok ...... [10:30] if you have questions it is better to use th eubuntu-devel mailing list, i'll answer there [10:30] ok ... [10:31] ogra_ : thanks for your help ..... === calculu5 is now known as calculus