=== chihchun_afk is now known as chihchun === balloons is now known as Guest62641 === chihchun is now known as chihchun_afk [05:42] hello [12:15] bjf, i updated the rpi doc to point to the correct commands and versions ... [14:01] Woot! RPi images, thanks ogra_ ! [14:02] :) [16:28] i'm a bit confused. i just built ubuntu-device-flash (on fedora, with sources taken from launchpad), but it doesn't seem to have the options described on the "porting" wiki page [16:28] i mean, yeah... i took the source from the goget-ubuntu-touch package, but i didn't find anything else [16:47] maybe outdated documentation, certainly wouldnt' be the first time with snappy [16:59] but would they really remove the oem image and file output options? [17:44] basically what i'm trying to do is build custom core images with preinstalled software to flash onto some devices we have at work [17:51] ogra@styx:~/Devel/branches/wget$ apt-cache show ubuntu-device-flash|grep Depends [17:51] Depends: android-tools-adb, android-tools-fastboot, debsig-verify, click-ubuntu-policy, dosfstools, fakeroot, kpartx, parted, qemu-user-static, ubuntu-snappy-cli, libc6 (>= 2.6) [17:52] peacememories, you would have to make sure that all runtime deps used for building core images are there too ... (and if anything is in different locations you would need to bend the paths in the source i guess) [17:53] click-ubuntu-policy, dosfstools, fakeroot, kpartx, parted and ubuntu-snappy-cli in any case ... if you want to build for non x86 arches also qemu-user-static [17:54] * ogra_ would simply use a VM or some kind of emulation to run a minimal ubuntu instead ... [17:59] using a vm (a container in my case) would work for me, but my problem isn't that the software doesn't work, it just doesn't recognize the options [18:00] peacememories: which one? [18:01] --oem for example [18:01] which, according to the wiki could be used to supply an oem snap specifying preinstalled software ect. [18:02] *etc [18:02] --oem is only allowed in developer mode [18:02] (well, a local oem snap that is) [18:03] otherwise if you specify ..oem it needs to be a valid package from the store ... [18:03] btw, is there a way to _search_ oem snap? [18:03] (RaspberryPi2)ubuntu@localhost:~$ snappy search oem|wc -l [18:03] 9 [18:04] finds 8 (plus a header line) [18:05] how about on a host? [18:05] sabdfl, are you booting your RPi with a screen attached ? (where do you see these dots, i have never seen them, but i also only watch the boot via serial console) [18:05] ogra_, yes, screen andkeyboard [18:06] how long did you wait ? [18:06] cloud-init on arm can take up to 2-3min on first boot [18:06] an hour or so [18:06] hmm [18:06] yashi_, https://uappexplorer.com/apps?q=oem&sort=relevance&type=snappy [18:06] ;) [18:07] sabdfl, i'll try here, just need to find a free monitor that will take a bit [18:07] ogra_: that's what i did and found out that your rpi isn't there [18:07] thanks ogra_ [18:08] also, is there a preferred ppa to get the new 4.2 rpi2 kernel from? [18:09] sabdfl, the wily archive ;) [18:09] my favourite ppa :p [18:09] the kernel team uploaded it last week [18:10] yashi_, indeed, thats weird ... i definitely see it in webdm on all my snappy installs ... probably a bug in uappexplorer (which is mainly made for phones, snaps are just a freebie based on luck :) ) [18:11] ogra_: ;) [18:16] ogra_, i think i should specify that i'm trying to create images for intel NUCs, not to flash smartphones [18:17] so i'd need --oem and -o. how would i get into developer mode? [18:17] by using --developer-mode [18:17] and yes, it was relatively clear to me that if you ask in #snappy you want to build snappy images ;) [18:17] sorry^^ [18:17] thanks for your help [18:18] heh, np [18:20] sabdfl, hmm, so i get a proper login prompt and also the normal kernel boot noise on boot ... i wonder if there is something wrong with the image [18:21] * ogra_ pulls http://people.canonical.com/~platform/snappy/raspberrypi2/ubuntu-15.04-snappy-armhf-rpi2.img.xz to make sure he sees the right boot :) [18:35] * yashi_ struggling to setup $GOPATH when I hack on goget-ubuntu-touch [18:37] u-d-f dpends on snappy, so I setup GOPATH=somehere then I also have goget-ubuntu-touch under $GOPATH [18:41] * ogra_ twiddles thumbs while watching dd ... [18:44] sabdfl, ok, i verified there is everything ok with the image itself even a fresh download boots properly ... lets find out what went wrong for you ... a) did you download from http://people.canonical.com/~platform/snappy/raspberrypi2/ubuntu-15.04-snappy-armhf-rpi2.img.xz b) did you verify the md5 (or sha256/sha512) sum against the download [18:45] sabdfl, also, how did you write the image to the SD ... it needs to be uncompressed first and you need to write to the whole device, not a partition ... my common command is: xzcat ubuntu-15.04-snappy-armhf-rpi2.img.xz | sudo dd of=/dev/sdc bs=4M [18:46] (where /dev/sdc is my USB SD controller ... native SD controllers would show up as /dev/mmcblk0) [20:37] ogra_, sorry to bother you again but ubuntu-device-flash doesn't seem to know the developer-mode flag O.o [20:38] well, it definitely does for me [20:38] whats the error you see [20:39] maybe i'm misunderstanding where to get the newest version... i'm on 0.23 right now (the newest version i could find on launchpad) [20:39] oh [20:39] we're somewhere around 0.31 [20:40] ah yes, i clicked on the wrong dropdown it seems [20:40] my bad [20:40] https://launchpad.net/ubuntu/+source/goget-ubuntu-touch [20:40] but --developer-mode is supported since "core" is supported iirc [20:41] or at least shortly after it was introduced [20:41] 0.31 doesn't know the flag either [20:42] whats the error ? [20:43] like i said above: "unknown flag `developer-mode'" [20:43] how does your command look like ? [20:44] oh...OOOH, i need to specify those flags _after_ the core argument... well... [20:44] yeah [20:44] *facepalms* [20:44] dont facepalm ... i think it took me 3 months to not mess that up all the time :) [20:45] thanks again =) [20:45] np [20:48] hm, creating images needs root permissions? note sure how i feel about that [20:53] it needs to partiton and loop mount the img [20:53] and uses kpartx for that [20:54] there is perhaps a fuse way to get around this ... not sure [20:54] (but that would need implementation indeed)