**** BEGIN LOGGING AT Mon Nov 21 02:59:58 2011 Nov 21 04:53:25 oh hello again Nov 21 08:17:21 is ubuntu-arm ready for Nvidia "Tegra 3"? or should i wait? Nov 21 08:33:12 Hanmac1: it will be Nov 21 08:33:16 "ready Nov 21 08:33:17 " Nov 21 08:33:25 you will need to work the kernel side Nov 21 08:34:04 but the userland part will work just fine, well providing they don't have any nasty bugs like the Tegra2 and the cp15 bug Nov 21 08:45:13 i mean exist an image that i can use to install it or should i build one on my own? Nov 21 08:56:46 Hanmac1: No images, since we have no kernels (and no specific devices we're targetting) Nov 21 09:05:02 hm what is needed to build the kernels? i wanted to use "Asus Eee Pad Transformer Prime" with ubuntu Nov 21 09:13:49 infinity, well, he could start from ubuntu-core, make a kernel and hack the bootloader and be done Nov 21 09:13:49 Hanmac1: not enough is known about the prime yet Nov 21 09:13:49 Hanmac1: biggest issue I forsee is the SBK Nov 21 09:13:49 Hanmac1, find the kernel source for your device ... take the linux-ac100 kernel config as a base and adjust your config for the tegra3 to match everything but the HW bits needed for tegra3 ... build it ... Nov 21 09:13:50 then make sure you have full access to the bootloader, flash your kernel and boot into a modified ubuntu-core rootfs on MMC or SD Nov 21 09:13:51 if you dont understand any of the above i said above. you should better not do it though Nov 21 09:15:19 hm i does not know if i will have full access to the bootloader (i have not buy the pad jet), i have played enough with bootloaders (i know how to install it to the MBR), but what did you mean with SBK? Nov 21 09:15:39 ogra_: well given my exp with the tf101 I would say, if you have nvflash access, not bootloader, cause asus bootloaders are non interactive Nov 21 09:16:06 and also, installing a bootsector to MBR is not the same thing Nov 21 09:16:59 * ogra_ would see nvflash and full bootloader access as the same thing ... Nov 21 09:17:14 heh I wouldn't Nov 21 09:17:14 if you can replace it you have full access ;) Nov 21 09:17:44 you could argue razorclaw gives you "full access" to the bootloader Nov 21 09:17:54 because you can write to the staging partition Nov 21 09:18:05 and that will flash pretty much everything Nov 21 09:18:23 except BCT Nov 21 09:19:00 and it really is full access, just risk of brickage increases exponantially as you flash more Nov 21 14:42:47 hi Nov 21 14:46:15 i try to crosscompile a litte c++-programm for my pandaboard which is running ubuntu 10.10. my hostsystem runs also ubuntu 10.10 and i tried "arm -linux-gnueabi-cpp main.cpp" and the error was "fatal error: QTGui/QWidget: no such file or directory"... has anyone an idea? Nov 21 14:46:20 thanks in advance Nov 21 14:46:45 doko, ping Nov 21 15:36:06 S0NiC, sounds like you're missing either a path to the qt includes or they aren't installed Nov 21 15:48:39 tgall_foo, pong Nov 21 15:58:47 hi doko, just wanted to catch up with you on the libjpeg8 / libjpeg-turbo project we had talked about at the last UDS Nov 21 16:00:05 doko, as of this morning I've got the majority of pkgs with deps on libjpeg-dev built in my PPAs against the libjpeg-turbo's version of the libjpeg-dev for precise Nov 21 16:00:24 and by majority I mean majority in the main archive, universe is another matter Nov 21 16:00:45 if I hadn't run out of space in my PPA main would be complete ? sigh Nov 21 16:01:59 doko, for the sake of trivia https://wiki.linaro.org/TomGall/LibjpegUse lists the debs in universe and main for libjpeg62, libjpeg8, libjpeg-dev etc Nov 21 16:02:38 doko, make sense ? Nov 21 16:12:55 tgall_foo, can we move this discussion to #ubuntu-devel? Nov 21 16:13:18 doko, sure Nov 21 16:58:11 still working on a kernel that will boot on a Stingray board Nov 21 16:58:35 good luck :) Nov 21 16:58:45 ty Nov 21 16:59:02 bug 888569 Nov 21 16:59:04 Launchpad bug 888569 in kernel-sru-workflow/verification-testing "linux-ti-omap4: 2.6.35-903.27 -proposed tracker" [Undecided,Fix released] https://launchpad.net/bugs/888569 Nov 21 16:59:11 GrueMaster: ^^ Nov 21 16:59:26 i think i can utilize the ac100 kernel config as a base then add the stingray stuff Nov 21 16:59:31 GrueMaster: wrt the failed tests, is there a way i can rerun these tests? Nov 21 16:59:51 GrueMaster: actually it should just a matter of flipping some configs, but you never know... Nov 21 16:59:55 An-iSociaL, note that the ac100 kernel is based on chromeos Nov 21 17:01:29 noted, i suspect that just compiling the stingray kernel with the right things enabled will work, using the ac100 as a template for what needs to be enabled could do the trick Nov 21 17:02:12 sure, but there are ac100 specific bits you will likely need to clean up Nov 21 17:02:29 like the nvec controller Nov 21 17:04:32 ill need some time to do the research but tell me if im wrong, having things enabled which do not actually exist wont hinder anything will it? Nov 21 17:04:48 as long as the things which do are enabled Nov 21 17:05:00 no idea, might make your buold fall over Nov 21 17:05:07 *build Nov 21 17:05:21 lol quite likely, ive tried so many things already it couldnt be any worse Nov 21 17:05:32 what kernel version is this for anyway? Nov 21 17:05:37 i havent seen that part yet Nov 21 17:05:40 ac100 ? Nov 21 17:05:43 oh nvm Nov 21 17:05:44 thats 2.6.38 Nov 21 17:05:58 lol duh, config-2.6.38 Nov 21 17:06:07 sorry Nov 21 17:06:45 speedway in my head had a pile up, traffic's been diverted and the wreck has been cleared Nov 21 18:51:13 ppisati: Sorry, didn't see your ping earlier. Yes, you can run the failing tests. Either pull the entire bzr tree for qrt (bzr branch lp:qa-regression-testing), or I can post tarballs of just the failing tests somewhere. Nov 21 18:51:37 I'm remote this week, but it should still be possible for me to post these. Nov 21 19:18:06 ok comparisons are done Nov 21 19:18:12 not nearly as bad as i thought Nov 21 19:18:30 10-15 unused which includes aroud 10 which are android Nov 21 19:19:13 13 which are unset in ac100 but tagged as yes in stingray Nov 21 19:19:35 7 of which are debug flags Nov 21 19:19:57 ill write up a report when i get a moment Nov 21 19:20:02 see how this goes first Nov 21 19:21:12 several marked for modules in ac100 were marked as yes in stingray so i just marked them yes in ac100 Nov 21 19:21:34 likely could go back to modules but i wanted to make sure they were available in case something went wrong with accessing the modules Nov 21 19:47:44 GrueMaster: i'll pull from bzr, thanks Nov 21 19:48:52 ppisati: Ok. On the test-kernel-security.py, the only test that "should" fail is /dev/mem. Still looking at it. Nov 21 19:50:30 Also, test-kernel-[aslr-collisions|root-ops] both fail and are being worked on. I don't think they are kernel issues, rather kernel differences (vs x86) Nov 21 19:51:25 GrueMaster: ok, and in case one of the option there is not implemented, to whom shall i report it? Nov 21 19:51:46 GrueMaster: i.e. SECCOMP was not supported on arm back then Nov 21 19:52:13 Yes, it was. The test passes on earlier arm kernels. Nov 21 19:52:25 iMX5/Dove. Nov 21 19:52:46 Also, I think the config just has it disabled in the omap4 kernel. Nov 21 19:53:45 GrueMaster: not for omap4, perhaps had some stuff backported as part of the marvell BSP Nov 21 19:54:00 *perhaps mvl-dove Nov 21 19:55:22 It should be in the 2.6.35 kernels. There was a CVE filed for the x86 kernel that added it. Nov 21 19:55:48 I think. Will have to check my remote system (if possible - I'm away from home this week). Nov 21 20:15:08 ppisati: I have remote access to my panda with Maverick installed. Will look it over again for SECCOMP. Nov 21 20:33:23 hm Nov 21 20:33:27 no go on compiling Nov 21 20:33:32 the sources is all kinds of outdated Nov 21 20:33:46 patches were released for most of my problems Nov 21 20:36:20 would it be possible to import the mach-tegra to another kernel? Nov 21 20:36:35 with the stingray sources* Nov 21 21:06:32 An-iSociaL: possible, yes, but it would be a lot of work Nov 21 21:06:59 hm Nov 21 21:07:13 clear your calendar if you plan to :) Nov 21 21:07:13 yea thats not going to happen then Nov 21 21:07:31 perhaps i can get the newer kernel from android 4.0 Nov 21 21:07:43 for the moment though, i do have it compiled, about to test Nov 21 21:08:08 i think i was able to keep support for ac100 Nov 21 21:17:46 impressive it actually booted Nov 21 21:18:10 now to actually put this on an sdcard Nov 21 21:18:28 let me revice, the kernel booted, as in didnt freak out or freeze up Nov 21 21:18:33 revise* Nov 21 21:42:19 Well, that is always a good sign. Nov 21 21:43:33 well i setup the sdcard... now all im getting is checksum file missing Nov 21 21:43:41 never seen that one before Nov 21 21:44:24 oh great and google doesnt have anything on it :| Nov 21 21:46:00 uhm need a little help with this one Nov 21 21:46:52 "Error: Checksum file missing" Nov 21 21:47:00 "Spawning a shell within the initramfs" Nov 21 21:47:38 No results found for "Error: Checksum file missing". Nov 21 21:48:11 Is this on our image? Nov 21 21:48:42 from the kernel i compiled using the ac100 kernel config and using the ac100 prebuilt filesystem Nov 21 21:49:12 infinity: Do you know how to create this checksum? Nov 21 21:49:39 I think it is done at image creation time and added to the initrd in some weird fashion Nov 21 21:49:54 hm Nov 21 21:50:16 i created the initrd from chroot inside the prebuilt rootfs Nov 21 21:50:45 I think the md5sum is added after that step. Not sure how. Nov 21 21:51:08 well im right there with you Nov 21 21:51:14 But it shouldbe an md5sum of the rootfs tarball (iirc) Nov 21 21:51:56 well thats gonna be a problem as i extracted it onto an sdcard to boot it Nov 21 21:52:47 So you are trying to dual boot in essence? Nov 21 21:53:35 kind of, im working with a motorola xoom, the kernel+initrd were put into a img file then flashed to the recovery partition from fastboot Nov 21 21:53:51 never had a problem with that before Nov 21 21:53:52 there is probably a script in the initrd that can either be deleted or modified. But I'm remote from my test bench this week, otherwise I could look. Nov 21 21:54:14 ok i found it Nov 21 21:54:32 -> /usr/share/initramfs-tools/scripts/installer Nov 21 21:54:44 regenerating Nov 21 21:57:41 er Nov 21 21:57:48 i guess i didnt read something i should have Nov 21 21:58:00 i did the install myself Nov 21 21:59:37 this could get interesting Nov 21 22:00:58 ok proper way to remove: dpkg --purge ac100-tarball-installer Nov 21 22:01:44 * GrueMaster crosses fingers/toes in anticipation. Nov 21 22:02:37 * An-iSociaL does too while he fights with his microsd reader Nov 21 22:08:15 and here we go Nov 21 22:09:13 starting services Nov 21 22:09:33 waiting for network configuration Nov 21 22:09:59 err Nov 21 22:10:06 no desktop Nov 21 22:10:35 localhost.localdomain login: Nov 21 22:10:39 which i cant do Nov 21 22:10:47 no keyboard Nov 21 22:10:57 ok let me get adbd onto it Nov 21 22:17:28 uhm Nov 21 22:17:37 whats going on in this filesystem? Nov 21 22:17:43 no desktop started up Nov 21 22:17:51 but i dont even see one to be started Nov 21 22:18:29 oh Nov 21 22:18:32 lightdm Nov 21 22:19:59 Probably more magic that the install script handles. Nov 21 22:20:17 yea Nov 21 22:20:34 kinda hard to install from my sdcard to my sdcard though Nov 21 22:20:51 i guess if its what i have to do i can work out how to put it on internal storage Nov 21 22:21:04 just partitions after all Nov 21 22:21:38 I think the image is supposed to launch oem-config on startup. I think you can have it autostart with "sudo touch /var/lib/oem-config/run" Nov 21 22:21:39 ok lightdm enabled and booting again Nov 21 22:23:49 still no Nov 21 22:28:25 whoa Nov 21 22:28:28 its freaking out Nov 21 22:29:01 keeps switching ttys, guessing trying to start lightdm and failing Nov 21 22:29:14 trying to get adbd up and running so i can actually do something Nov 21 22:30:08 welp lets check the logs Nov 21 22:30:51 [ 89.326] (EE) open /dev/fb0: Device or resource busy Nov 21 22:30:58 negative :( Nov 21 22:32:28 ok time to try the nvidia drivers Nov 21 22:41:32 its a bust Nov 21 22:45:38 welp ill try some more stuff later Nov 21 22:45:49 pretty much concrete the nvidia drivers do not work Nov 22 00:25:37 Hello Everyone, I recently got a donate board from TI. It's the LogicPD OmapL138EVM board. Would anyone happen to know if this board supports ubuntu11arm? Nov 22 00:37:54 what processor is it? Arm11? Nov 22 00:39:04 We only support Armv7 (Cortex A8 & Cortex A9). Nov 22 00:39:17 howdy how GrueMaster Nov 22 00:39:51 An-iSociaL: Hey. Get your kernel up? Nov 22 00:40:07 GrueMaster: internet says ARM926 core Nov 22 00:40:08 negative :( Nov 22 00:40:30 not down yet though, still trudging Nov 22 00:40:49 Aww, sad face. Good luck. Nov 22 00:41:10 I'm EOD. Time for Skyrim. Nov 22 00:41:18 laters Nov 22 00:42:21 I think OmapL138--> A8, i believe Nov 22 00:44:04 Oh whoops it has an ARM926EJ-S + C6748 VLIW DSP Nov 22 00:44:25 any chance of seeing ubuntu on this system? i miss aptitude :( Nov 22 00:44:40 bge0: debian armel then Nov 22 00:45:24 ty! ill look into it Nov 22 00:45:40 and howdy to you too twb, sorry i didnt see you there Nov 22 00:45:46 An-iSociaL: whatever Nov 22 00:45:53 lol Nov 22 00:45:59 hmph Nov 22 00:49:53 whatre you upto? Nov 22 01:15:28 twb: I'm looking up debian armtel, but there seems to only be support for iop32x, ixp4xx, kirkwood and orion5x Nov 22 01:17:14 http://wiki.debian.org/ArmEabiPort Nov 22 01:18:19 You're not going to get turnkey installation, but it certainly seems to support OMAP1/2/3 boards Nov 22 01:18:37 yea I figured it wouldn't be quite that easy Nov 22 01:20:20 But if you aren't attached to the board I would suggest getting something armv7 flavoured, since everybody is switching to those Nov 22 01:22:28 Well it's a pretty nice board though. i would feel bad scrapping it. It has a good onboard dsp too Nov 22 01:24:54 Shrug Nov 22 01:29:04 Well, I guess I might just stick with the linux port that the board came with Nov 22 01:29:07 ty though Nov 22 01:36:21 An-iSociaL: that unable to open /dev/fb0 is indicating that the fb patch from the chromeos code review didn't take Nov 22 01:37:28 aha Nov 22 01:39:20 well im not ready to give in just yet Nov 22 01:42:02 An-iSociaL: http://www.cactuar.net/uploads/Xoom_Debian/xoomkernel-gnu.patch over https://github.com/Tiamat%E2%80%93AOSP/Tiamat-Xoom Nov 22 01:42:56 ah Nov 22 01:43:06 ill have to manually patch that in Nov 22 01:43:16 the AOSP tiamat is old Nov 22 01:43:24 but im using his latest version Nov 22 01:43:33 the only kernel i could get to ocmpile properly Nov 22 01:43:36 compile* Nov 22 01:48:05 right now i cant seem to generate another working initrd Nov 22 01:53:25 :/ Nov 22 01:53:32 i keep ending up with the installer Nov 22 01:58:51 there.. Nov 22 01:59:42 An-iSociaL: you want that installer "oem-config" so you can set up a user and shit Nov 22 02:01:25 yea i got it, i think i was doing something ignorant by trying to use relative path for initrd output from mkinitramfs Nov 22 02:02:09 did the initrd installer steps manually, format, extract, write fstab, touch oem-config so itll run Nov 22 02:03:01 got a nice bootup, only kernel module to fail was btfrs with unknown symbol _global_offset_table_ which is caused by my cross compiler Nov 22 02:03:30 video failed, as if im shocked, it flashed a couple times trying to switch but never did Nov 22 02:03:39 so, on to the patch Nov 22 02:17:09 did you already update this patch lilstevie ? Nov 22 02:27:22 not my patch Nov 22 02:29:13 Sorry for interrupting but are there any team that works with Nokia N900? apachelogger, mpoirier, rbelem, someone else? Nov 22 02:56:37 ok all patched up Nov 22 02:56:40 booting Nov 22 02:59:02 whatup! ubuntu is booted with xdesktop on my Motorola Xoom! Nov 22 02:59:20 tyvm lilstevie **** ENDING LOGGING AT Tue Nov 22 02:59:58 2011