**** BEGIN LOGGING AT Fri Oct 25 02:59:58 2013 Oct 25 06:55:32 What can be done to speed up booting in Precise? Point is, we have an embedded product running on OMAP3, w/display, and running non-X Qt graphics (QWS). Booting takes around 30-40 seconds, which is far too long. So we need to reduce it. So in general we can either optimize precise boot or we have to change distro to something more lean. Oct 25 06:56:33 Much of the boot is scripts and initramfs and all those generic checks made during boot. And the boot is mostly io bound, because the machine is running off an SD-card which isn't too fast Oct 25 07:37:23 sveinse, make sure your kernel supports ureadahead ... use bootchart to identify slow processes on boot Oct 25 07:57:35 ogra_: I have used bootchart to ploy, and there is something like 100 processes/scripts before our apps start loading. Oct 25 07:58:27 ogra_: for the ureadahead, I've been told (here) that ARMv7 does not support ureadahead. At least I get a failure for it while booting Oct 25 07:58:41 you need a kernel patch Oct 25 07:59:03 it works fine on all arm arches and helüps quite a lot Oct 25 07:59:23 ogra_: Where can I find this patch? Oct 25 08:00:14 * ogra_ isnt sure if bug 1194127 has a direct link Oct 25 08:00:16 Launchpad bug 1194127 in linux-manta (Ubuntu Saucy) "ureadahead does not work in current linux-maguro/linux-mako/linux-manta" [High,Fix released] https://launchpad.net/bugs/1194127 Oct 25 08:01:19 try to find this one on kernel.ubuntu.com iirc the changelog entry comes from git Oct 25 08:02:01 https://lists.ubuntu.com/archives/kernel-team/2009-October/007712.html Oct 25 08:03:24 ogra_: We running on precise because this is LTS. Would there be any advantages speedwise to change to a newer distro version? Oct 25 08:03:59 I mean, I supporse the ARM support has matured since precise Oct 25 08:05:01 we had a big performance review of arm stuff in quantal ... so yes, you might see some speedups ... but OTOH the support for non LTS is only 9 months nowadays Oct 25 08:06:48 Will 14.04 will be LTS? Oct 25 08:09:29 yep Oct 25 08:26:36 _ogra: Thanks Oct 25 08:50:10 ppisati: Hi Oct 25 08:50:48 ppisati: I was looking for you and want to ask something related to page https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile Oct 25 08:52:18 ppisati: I have downloaded the Ubuntu-quantal source code and later I did git checkout -b temp Ubuntu-3.4.0-1.1 to move to branch 3.4 Oct 25 08:52:50 I want to build the Ubuntu for the APQ8064 Oct 25 08:54:11 there is a support for the ti-omap4, but I wan to build for the qualcomm APQ8064 ..... Oct 25 08:54:30 ppisati: Can you please help me how should I proceed Oct 25 08:55:23 ppisati: to get omap4 ...I did git checkout -b ti-omap4 origin/ti-omap4 Oct 25 08:55:55 ppisati: But, how should I get a support for the qc-apq8064 ......or how can I create the same\ Oct 25 08:58:08 ppisati: Please help me sir .....I will not take much of your time Oct 25 09:14:35 too quick Oct 25 09:14:43 or maybe i was too late... :) Oct 25 09:15:12 abhishek_: two things: Oct 25 09:15:27 ppisati: I lost the connection to this Oct 25 09:15:46 1) first check that the kernel version you checked out support your chip Oct 25 09:15:49 ppisati: I might have missed your earlier messges Oct 25 09:16:09 ppisati: ok Oct 25 09:16:11 2) then copy the debian.omap4 branch and make all the modifications related to your chip Oct 25 09:17:14 ppisati: How to find that that the kernel downloaded by me is supporting the chip ?? Oct 25 09:17:50 ppisati: In arch/arm/configs Oct 25 09:17:54 abhishek_: since it's a normale kernel after all, check in arch/arm/* Oct 25 09:17:57 and so on Oct 25 09:18:42 ppisati: ok Oct 25 09:19:12 ppisati: in arch/arm/mach-apq8064 is not present .....but mach-msm is present Oct 25 09:19:35 abhishek_: if you try a make ARCH=arm menuconfig Oct 25 09:19:46 check than your soc is there Oct 25 09:19:49 *that Oct 25 09:21:08 Qualcomm MSM is present ...but not Qualcomm APQ8064 Oct 25 09:21:28 than you first should try to compile a kernel the normal way Oct 25 09:21:34 adding stuff for your chip Oct 25 09:21:42 and when you have a stable config, come back Oct 25 09:22:18 So, I will compile the kernel for the qualcomm MSM ...... Oct 25 09:22:33 abhishek_: and you need to boot it too Oct 25 09:22:42 If I want to add stuff for my chip ....what needs to be changed Oct 25 09:23:06 the config Oct 25 09:23:11 ppisati: How the kernel compiled for the different SOC will boot up ? Oct 25 09:23:35 dude, first get familiar with compiling and booting a new kernel on your board Oct 25 09:23:37 the config in arch/arm/config/apq8064_defconfig Oct 25 09:23:58 I have already done this activity Oct 25 09:24:32 I have compiled the kernel for x86 also .....and changed by desktop kernel also Oct 25 09:24:48 *my Oct 25 09:26:20 ppisati: What else needs to be changed Oct 25 09:28:31 Hi Lee Oct 25 09:29:24 lag: I want some help for the kernel configuration for SoC Qualcomm apq8064 Oct 25 09:30:47 I have downloaded ubuntu-quantal ....but this kernel has no support for my SoC ....what I need to change to support my SoC Oct 25 09:43:33 Please help me Oct 25 12:57:33 If I try to build debian packages in an ubuntu chroot, what sort of things tend to go wrong? Oct 25 12:57:43 I need to nobble dpkg-vendor Oct 25 12:57:47 what eles? Oct 25 12:58:18 dch does the wrong thing Oct 25 13:01:53 wookey, edit base-files Oct 25 13:03:10 lsb_release -a should work Oct 25 15:17:48 wookey: base-files and dpkg should be the only two things required to turn Debian into Ubuntu and vice versa. Oct 25 15:58:11 dpkg? because it encodes teh dpkg-vendor answer in the build? Oct 25 15:58:29 I'd naively assumed I could change that in a config file somewere Oct 25 16:07:14 wookey: Mangling /etc/dpkg/origins should be enough to switch dpkg. Oct 25 16:07:41 wookey: And then /etc/lsb-release and /etc/os-release for base-files. Oct 25 16:07:58 wookey: I can't think of anywhere else that people query to determine what sort of system they're on. Oct 25 16:08:43 wookey: Of course, toolchain defaults will differ unless you rebuild those. So, if the goal is to bootstrap Debian from Ubuntu, or Ubuntu from Debian, as soon as you mangle dpkg and base-files, the first order of business is to build your toolchain. Oct 25 16:09:30 (Can you tell I've done this before...) Oct 25 16:33:14 that's good. I was oping to find someone who'd done this before to stop me wasting a lot of very slow model time Oct 25 16:34:11 wookey: Well, I did it in the other direction with armhf, since Debian started that before us. So, I'd do arm64 in exactly the other direction and it should work well. Oct 25 16:34:32 (Well, as well as anything can work on a model...) Oct 25 16:34:37 wookey: I assume you'll be in Santa Cruz? Oct 25 16:34:40 Err. Oct 25 16:34:41 Clara. Oct 25 16:34:44 yes Oct 25 16:34:44 Santa something. Oct 25 16:35:02 next question. presumably it's unwise to adulterate my working ubuntu build chroot by jamming just-build debian packages in Oct 25 16:35:09 and I should make another one for that purpose Oct 25 16:35:15 so I can go back when it breaks Oct 25 16:35:20 Going back is for wimps. Oct 25 16:35:25 And you can always debootstrap a new one. :) Oct 25 16:35:38 But the goal is to evolve into Debian, so you *want* to be installing your just-built packages. Oct 25 16:36:06 Once everything in your chroot as become Debian versions, then you get to rebuild them all AGAIN, and be fairly confident that you're no longer building against Ubuntu. Oct 25 16:36:11 yes, i realise that :-) but I was expecting something bad to break Oct 25 16:36:11 s/as/has/ Oct 25 16:36:25 I wouldn't expect much world breakage in taking that approach. Oct 25 16:36:48 I guess I should just save the base chroot for emergencies Oct 25 16:37:21 debootstrap is easy but the settign up of keys and dupload configs and nobbled dpkg etc is a faff I don;t want to repeat to many times Oct 25 16:37:32 Luckily, since the autosync, trusty and sid are pretty dangerously similar, so it shouldn't be too, too bad. Oct 25 16:37:34 easpicially as it's all so gloriously slow Oct 25 16:37:58 ah, and actualy the keys and stuff is in my $home so that's OK Oct 25 16:38:30 did you use a snapshot to avoid undue churn, or just stick with 'latest' in both? Oct 25 16:38:56 No snapshotting, though we did start when saucy was mostly frozen, which helped a bit. **** ENDING LOGGING AT Sat Oct 26 02:59:59 2013