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