=== chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [07:00] hi all, is there a cpuburn tool that support cortex-a9 without neon? [09:00] cpuburn is using neon? === chihchun is now known as chihchun_afk === hrww is now known as hrw === doko_ is now known as doko [13:31] ogra: question, can we keep the image building stuff simple? like we did with the Nexus 10? where I just debootstrapped a base ubuntu rootfs, put that onto the data partition, compiled the kernel and packed that with the standard ubuntu initrd [13:31] ( for the Nexus 7 ) [13:31] only with the Nexus 7, I preseed the chroot with https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-tegra3 and the desktop kernel [13:34] ( the desktop kernel being this one : http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-nexus7.git;a=summary _ [13:34] ) [13:35] who is "we" ? [13:35] do you mean you create an image locally ? [13:39] i have a BeagleBoard Black that I want to throw Ubuntu on. I downloaded the ubuntu-13.04-console-armhf-2013-05-29.tar.xz, and the md5 comes out correct. When I try to use 7-Zip (Windows) to extract the .xz file, it says it is not an archive. Is the xz file actually image, and I should use that file when creating my SD card? [13:42] ogra: we = kubuntu team :) [13:42] ogra: yes [13:42] for now [13:42] this isnt an official ubuntu image, find the person who created it and ask him/her [13:43] which image are you talking about :S [13:44] thanks ogra [13:45] oh that was for pbcw [13:45] that beaglebone thingit [13:45] right [13:45] roger [13:45] well, for your kubuntu image, just create a tarball, make sure abootimg is in it as well as the graphics driver [13:45] i assume that should suffice [13:46] uhhhh I'm not going through the whole reflash kernel method :P [13:46] * ogra hasnt touched desktop images in ages ... have a look at the build scripts in livecd-rootfs [13:46] you have to [13:46] why? [13:46] you *need* to rebuild the initrd [13:47] right, but *why* [13:47] if you use a proper bootimg with tarball installer at least [13:47] because it will not boot [13:47] can't it work like we did with the Nexus 10? [13:48] i have no idea what you did with the N10 [13:48] compile kernel , pack it with a standard ubuntu initrd, set rootfs=/dev/mmcppblk [13:48] apart from hacking it to get X up [13:48] sure, you can do that as a hack [13:49] if I understand it correctly, the way it's done in the desktop image currently is to allow for kernel upgrades? [13:50] so when there's a new kernel in /boot the device flashes itself again? [13:50] no [13:50] oh, so why is it done like that? [13:50] anything that uses a trigger for initramfs will re-flash [13:50] has nothing to do with /boot [13:51] I see [13:51] but with dpkg triggers [13:51] roger [13:53] anyway, I'll take the hacky way for now ;) [13:53] ogra: FWIW I still don't have X on then N10, because I can't find the right X11 exynos 5250 drivers :( [13:54] I heard there's a simplefb driver in the kernel now, going to look at that once I'm through with the N7 [13:54] well, if your kernel works correct it should just start [13:54] using xfbdev [13:54] (which is the default on arm) === XorA is now known as XorA|gone === piscodig is now known as discopig [19:23] hey guys I'm trying to compile libavg for arm, I am getting some configure errors, the pkg-config script could not be found or is too old make sure it is in your PATH any ideas? [19:23] I am not sure how to set the flags [19:27] ValDuare: Did you try installing pkg-config? [19:28] doing that now heh [19:28] retesting [19:29] got a new error now [19:29] I'm sure you did. [19:29] Out of curiosity, what's wrong with the libavg in the archive? [19:30] pangoft2 [19:30] apt-cache search libavg shows nothing? [19:30] python-libavg [19:31] And it's in universe, do you have only main enabled in your sources.list? [19:31] checking [19:32] hah if that works I'm going to crack spent all morning fulfilling dependancies to compile libavg haha [19:32] On, wait. What release are you running? It was arch-restricted to x86-only in precise and quantal. :/ [19:33] Build on armhf in raring and saucy. [19:33] s/Build/Built/ [19:33] 12.10 picuntu on an mk808 [19:34] Ahh. Why 12.10? [19:34] If you upgrade to 13.04, you might be a bit happier. :) [19:34] I haven't tried updating yet [19:35] main restricted universe multiverse is enabled in sources [19:35] Yeah, but like I said, it's not built in quantal. [19:35] And this is why: [19:35] * Change architecture to any [19:35] * Make some x86 specific debug code conditional (replacing it with a [19:35] deliberate segfault) (patch accepted upstream) (Closes: #683105) [19:36] ^-- Before that change (which was made in raring), it wouldn't have worked on ARM. [19:36] k [19:36] ok [19:36] i'll work on updating tonight [19:36] are you familiar with mk808 and picuntu? [19:37] Nope. === Quintasan_ is now known as Quintasan [21:55] Hello all, I am trying to install Ubuntu Precise 12.04 on my PandaboardES. I have followed the instructions here: https://groups.google.com/forum/#!topic/pandaboard/vKunvhMNV8k Just wanted to know if there has been an update on this known issue: * Black screen issue on some HW - workaround: Ctrl+Alt+F1 then Ctrl+Alt+F7 or boot with screen un-plugged, plug it after 1 minute. Issue under investigation.