[01:17] I'm typing up a tutorial for installing ubuntu on a tablet, can anyone recall what the file name format is for a rootstock image? [01:21] Define "rootstock" [01:34] twb, the program on ubuntu that creates an image for ARM [01:35] Oh, right, that's the arm-specific equivalent of debootstrap; that rings a bell [01:35] Dunno the answer to your question, though. [01:35] Yup. [01:35] and kk [02:08] Netham46: rootstock is deprecated, we don't generally encourage its use. [02:09] infinity: what's the recommended solution? [02:09] Netham46: We tend to prefer people start with ubuntu-core and tailor it to their needs, or if you really need to build images from the ground up, use live-build. [02:09] Cool [02:09] infinity: if you have write access to help.ubuntu.com or wherever the rootstock page was, please add a deprecation notice to it [02:10] https://wiki.ubuntu.com/ARM/RootStock [02:10] twb: Yeah, we have a lot of docs to fix, afaik. [02:10] I might add a notice to that page now, though. [02:11] I'd do it myself but ICBF going through the account creation bollocks [02:13] twb: Does that look reasonable for now (until we have time to tidy more)? [02:13] infinity: yeah fine [02:36] infinity, hmm, okay [02:36] I didn't realize that it was antiquated [02:39] Not your fault [04:51] oh hello again [08:15] is ubuntu-arm ready for Nvidia "Tegra 3"? or should i wait? [08:31] Hanmac1: it will be [08:31] "ready [08:31] " [08:31] you will need to work the kernel side [08:32] but the userland part will work just fine, well providing they don't have any nasty bugs like the Tegra2 and the cp15 bug [08:43] i mean exist an image that i can use to install it or should i build one on my own? [08:54] Hanmac1: No images, since we have no kernels (and no specific devices we're targetting) [09:02] hm what is needed to build the kernels? i wanted to use "Asus Eee Pad Transformer Prime" with ubuntu [09:06] infinity, well, he could start from ubuntu-core, make a kernel and hack the bootloader and be done [09:08] 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 ... [09:09] 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 [09:09] if you dont understand any of the above i said above. you should better not do it though [09:10] Hanmac1: not enough is known about the prime yet [09:10] Hanmac1: biggest issue I forsee is the SBK === popey_ is now known as popey [09:13] 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? [09:13] ogra_: well given my exp with the tf101 I would say, if you have nvflash access, not bootloader, cause asus bootloaders are non interactive [09:14] and also, installing a bootsector to MBR is not the same thing [09:14] * ogra_ would see nvflash and full bootloader access as the same thing ... [09:15] if you can replace it you have full access ;) [09:15] heh I wouldn't [09:15] you could argue razorclaw gives you "full access" to the bootloader [09:15] because you can write to the staging partition [09:16] and that will flash pretty much everything [09:16] except BCT [09:16] and it really is full access, just risk of brickage increases exponantially as you flash more === Quintasan_ is now known as Quintasan [14:40] hi [14:44] 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? [14:44] thanks in advance [14:44] doko, ping [15:34] S0NiC, sounds like you're missing either a path to the qt includes or they aren't installed [15:46] tgall_foo, pong [15:56] hi doko, just wanted to catch up with you on the libjpeg8 / libjpeg-turbo project we had talked about at the last UDS [15:57] 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 [15:58] and by majority I mean majority in the main archive, universe is another matter [15:58] if I hadn't run out of space in my PPA main would be complete ? sigh [15: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 [16:00] doko, make sense ? [16:10] tgall_foo, can we move this discussion to #ubuntu-devel? [16:11] doko, sure === ericm|ubuntu is now known as ericm-Zzz [16:56] still working on a kernel that will boot on a Stingray board [16:56] good luck :) [16:56] ty [16:56] bug 888569 [16:56] 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 [16:57] GrueMaster: ^^ [16:57] i think i can utilize the ac100 kernel config as a base then add the stingray stuff [16:57] GrueMaster: wrt the failed tests, is there a way i can rerun these tests? [16:57] GrueMaster: actually it should just a matter of flipping some configs, but you never know... [16:57] An-iSociaL, note that the ac100 kernel is based on chromeos [16:59] 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 [17:00] sure, but there are ac100 specific bits you will likely need to clean up [17:00] like the nvec controller [17:02] 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? [17:02] as long as the things which do are enabled [17:02] no idea, might make your buold fall over [17:03] *build [17:03] lol quite likely, ive tried so many things already it couldnt be any worse [17:03] what kernel version is this for anyway? [17:03] i havent seen that part yet [17:03] ac100 ? [17:03] oh nvm [17:03] thats 2.6.38 [17:03] lol duh, config-2.6.38 [17:04] sorry [17:04] speedway in my head had a pile up, traffic's been diverted and the wreck has been cleared [18:49] 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. [18:49] I'm remote this week, but it should still be possible for me to post these. [19:15] ok comparisons are done [19:16] not nearly as bad as i thought [19:16] 10-15 unused which includes aroud 10 which are android [19:17] 13 which are unset in ac100 but tagged as yes in stingray [19:17] 7 of which are debug flags [19:17] ill write up a report when i get a moment [19:17] see how this goes first [19:19] several marked for modules in ac100 were marked as yes in stingray so i just marked them yes in ac100 [19:19] likely could go back to modules but i wanted to make sure they were available in case something went wrong with accessing the modules [19:45] GrueMaster: i'll pull from bzr, thanks [19:46] ppisati: Ok. On the test-kernel-security.py, the only test that "should" fail is /dev/mem. Still looking at it. [19:48] 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) [19:49] GrueMaster: ok, and in case one of the option there is not implemented, to whom shall i report it? [19:49] GrueMaster: i.e. SECCOMP was not supported on arm back then [19:50] Yes, it was. The test passes on earlier arm kernels. [19:50] iMX5/Dove. [19:50] Also, I think the config just has it disabled in the omap4 kernel. [19:51] GrueMaster: not for omap4, perhaps had some stuff backported as part of the marvell BSP [19:51] *perhaps mvl-dove [19:53] It should be in the 2.6.35 kernels. There was a CVE filed for the x86 kernel that added it. [19:53] I think. Will have to check my remote system (if possible - I'm away from home this week). [20:13] ppisati: I have remote access to my panda with Maverick installed. Will look it over again for SECCOMP. === gary_ is now known as Guest71968 [20:31] hm [20:31] no go on compiling [20:31] the sources is all kinds of outdated [20:31] patches were released for most of my problems [20:34] would it be possible to import the mach-tegra to another kernel? [20:34] with the stingray sources* [21:04] An-iSociaL: possible, yes, but it would be a lot of work [21:04] hm [21:05] clear your calendar if you plan to :) [21:05] yea thats not going to happen then [21:05] perhaps i can get the newer kernel from android 4.0 [21:05] for the moment though, i do have it compiled, about to test [21:05] i think i was able to keep support for ac100 [21:15] impressive it actually booted [21:16] now to actually put this on an sdcard [21:16] let me revice, the kernel booted, as in didnt freak out or freeze up [21:16] revise* [21:40] Well, that is always a good sign. [21:41] well i setup the sdcard... now all im getting is checksum file missing [21:41] never seen that one before [21:42] oh great and google doesnt have anything on it :| [21:43] uhm need a little help with this one [21:44] "Error: Checksum file missing" [21:44] "Spawning a shell within the initramfs" [21:45] No results found for "Error: Checksum file missing". [21:46] Is this on our image? [21:46] from the kernel i compiled using the ac100 kernel config and using the ac100 prebuilt filesystem [21:47] infinity: Do you know how to create this checksum? [21:47] I think it is done at image creation time and added to the initrd in some weird fashion [21:47] hm [21:48] i created the initrd from chroot inside the prebuilt rootfs [21:48] I think the md5sum is added after that step. Not sure how. [21:48] well im right there with you [21:49] But it shouldbe an md5sum of the rootfs tarball (iirc) [21:49] well thats gonna be a problem as i extracted it onto an sdcard to boot it [21:50] So you are trying to dual boot in essence? [21:51] 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 [21:51] never had a problem with that before [21:51] 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. [21:52] ok i found it [21:52] -> /usr/share/initramfs-tools/scripts/installer [21:52] regenerating [21:55] er [21:55] i guess i didnt read something i should have [21:55] i did the install myself [21:57] this could get interesting [21:58] ok proper way to remove: dpkg --purge ac100-tarball-installer [21:59] * GrueMaster crosses fingers/toes in anticipation. [22:00] * An-iSociaL does too while he fights with his microsd reader [22:06] and here we go [22:07] starting services [22:07] waiting for network configuration [22:07] err [22:07] no desktop [22:08] localhost.localdomain login: [22:08] which i cant do [22:08] no keyboard [22:08] ok let me get adbd onto it [22:15] uhm [22:15] whats going on in this filesystem? [22:15] no desktop started up [22:15] but i dont even see one to be started [22:16] oh [22:16] lightdm [22:17] Probably more magic that the install script handles. [22:18] yea [22:18] kinda hard to install from my sdcard to my sdcard though [22:18] i guess if its what i have to do i can work out how to put it on internal storage [22:18] just partitions after all [22:19] 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" [22:19] ok lightdm enabled and booting again [22:21] still no [22:26] whoa [22:26] its freaking out [22:26] keeps switching ttys, guessing trying to start lightdm and failing [22:27] trying to get adbd up and running so i can actually do something [22:27] welp lets check the logs [22:28] [ 89.326] (EE) open /dev/fb0: Device or resource busy [22:28] negative :( [22:30] ok time to try the nvidia drivers [22:39] its a bust === Gary_ is now known as Guest96366 [22:43] welp ill try some more stuff later [22:43] pretty much concrete the nvidia drivers do not work