[00:00] huh, this is interesting [00:00] on my chomebook, the status bar seems to know about my battery [00:00] but acpitool is clueless [00:06] janimo: i can take a look at the kernel tomorrow AM === jsol is now known as jsolano [00:39] mjrosenb, have a look at the output from "upower -d" [00:40] mjrosenb, that is where the power applet gets the data from [00:42] lilstevie: most excellent. [00:42] lilstevie: has this replaced acpi? [00:43] mjrosenb, arm doesn't have acpi [00:44] Well, it is possible those Windows RT tablets do, but current ARM hardware does not [00:44] well [00:44] that makes sense [02:44] Here is hoping that acpi doesn't come to arm in any form. :S === Ursinha is now known as Ursinha-afk === vibhav is now known as Guest5822 === Guest5822 is now known as vibhav === vibhav is now known as Guest21128 === Guest21128 is now known as vibhav [07:49] good morning [08:24] anyone know if the raspberry pi has vfp on it? [08:28] morning all [08:34] feasty: morning. === doko_ is now known as doko === chrisccoulson_ is now known as chrisccoulson === Quintasan_ is now known as Quintasan === yofel_ is now known as yofel [13:03] hello [13:03] yo === Ursinha-afk is now known as Ursinha [13:25] I'm trying to run Ubuntu on my pandaboard, but the 12.10 release only had an installer image, not a preinstalled image. I want to run the rootfs off of my SD card, not a USB stick/disk, is there any way to achieve this? [13:48] sspiff: have you tried building a linaro image? [13:48] sspiff: Unofficially, you can use the netboot image, and when d-i/partman asks where to install, tell it to use the "largest contiguous free space". [13:49] sspiff: Officially, we don't support installing to SD, as the user experience is awful. [13:49] has anyone tried upgrading the nexus7 from 12.04 -> 13.04 recently? [13:49] via dist-upgrade [13:52] sfeole, dholbach did and found a bug, should be fixed by now [13:52] ogra_: with bluez ? [13:53] the bluetooth fix wasnt uploaded yet [13:53] and wemdont have brcm-patchram in raring yet [13:54] *we don't [13:54] how to recover a EEE Pad TF101 with battery issues? gets into APX mode but error -71 [13:54] battery or cable, not sure [13:54] there were a couple of problems 1) onboard needs an upload to raring (I'm in touch with upstream), 2) bluez did not start/stop correctly, 3) nexus7-firmware wasn't pulled in (fixed by infinity), 4) do-release-upgrade did not work (seems fixed in my last try), 5) unrelated to upgrades, but during an installation I couldn't enter anything into oem-config's text-boxes, neither with onboard, nor attached keyboard [13:54] sfeole, ogra: ^ that's all I noticed [13:55] yeah, the last one is really bad [13:55] did the unity stack land in standard raring already? or should we advise to use the daily-build still? [13:55] landed yesterday [13:55] yes baby! [13:56] in 1.5h there should be images with it [13:56] (and wit the new serial console by default) [13:57] no more wlan needed for debugging ;) [13:57] asiekierka, this probably isn't the place to get support with that, but usually you are looking at an issue with the usb cable [13:58] lilstevie: there's no place to get a support with that and this looks like the best bet seeing as you're here often [13:58] #asus-transformer looks kinda more suited [13:58] oh [13:59] asked. [14:01] * lilstevie heads to bed [14:02] for everyone else watching i meant 12.10 -> 13.04 , I just noticed that [14:03] heh [14:07] does this: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1045741 affect ubuntu on nexus7? [14:07] Launchpad bug 1045741 in firefox (Ubuntu) "since the switch to unity 3D and the GLES driver by default firefox on the pandaboard reders extremely slow" [Undecided,New] [14:09] my firefox works fine here [14:09] * ogra_ is currently typing from his nexus [14:10] i think firefox is a bit slow, but that could be due to the arm isn't as fast as a desktop...:P [14:17] I think that ogra_ is spoiled by ac100 speed [14:18] lol === albert is now known as Guest91253 === Guest91253 is now known as Phryq [15:04] arg still hangs for me when replacing bluez [15:04] sfeole, I had to kill the process, twice - once for stopping and another time for starting the service [15:07] dholbach: yea, that did it for me, what I will do is document this for now, I know we are recommended a fresh install to raring but you know there will be some people trying the upgrade path ;P [15:08] upgrade path == dist-upgrade [15:08] yeah, I did it too, as the installation from the image did not work for me [15:08] upgrades should definitely be functional [15:09] so thats a high prio bug [15:09] ogra_: agreed, my installation is now continuing .. I'm already filing the bug now [15:09] great, thx [15:12] sadly the touchscreen still dies after a while :( [15:24] hmm the nexus7-firmware0.2 package looks like it was pulled down and made me confirm it, but it failed to install [15:25] looking into why [15:34] infinity, ogra_ I am just curious, is armhf going to switch from ports.ubuntu.com ? [15:35] i dont think so, but ask infinity he might know more ans part of the release team :) [15:35] *as [15:36] janimo: Probably not for a long while, if ever. It has nothing to do with official or unofficial support, it has to do with amount of traffic. [15:36] and mirrors [15:36] janimo: Mirrors don't want to mirror a whole port just for the sake of 1% of users. [15:37] ogra_: Yes, mirror traffic was what I meant. [15:37] yup [15:38] sounds reasonable [15:51] sfeole, "screen /dev/ttyACM0 115200" could you run that on your PC with the nexus attached via USB ? hitting enter should get you a login (needs the latest kernel nad the latest default settings) [15:52] it works for me, just want to make sure it works for everyone [15:52] ogra_: http://www.elinux.org/PandaBoard-NC [15:52] ogra_: think there would be any market interested in that? [15:53] ogra_: i will try after I get upped to Raring [15:53] yeah,, needs raring indeed [15:53] ogra_: will let you know [15:54] prpplague, microsd and no ethernet ? [15:55] might be intresting for beagle guys that want to go up one level [15:55] ogra_: ethernet is there, just no connector for it, you have to wire it up yourself [15:55] yeah [15:55] ogra_: more for doing hardware dev [15:55] likewise for the USB hub [15:55] ogra_: yea [15:55] ogra_: you can use the standard usb panel connectors [15:56] well, surely intresting for getting a panda into a slim case [15:56] ogra_: yea [15:56] but i wouldnt expect massive sales from it i think [15:56] seems pretty special cased ... will it be the same priice as a "normal" panda ? [15:57] cheaper [15:59] that might be a sales argument then ... i personally would prefer a normal panda if i dont plan to put it into any case or so [16:00] having the little feet, and all sockets on board makes it easier to use for me ... if i would want to build a server with 10 pandas in a 4u case i would pick the NC [16:00] or when putting a panda into an ac100 shell :) [16:01] ogra_: yea that is the thought process [16:01] brb, need a reboot [16:28] janimo, ogra_: so is usb-serial turned on in today's image? I'd like to give it a try today if possible [16:29] plars, see above :) [16:29] ogra_: do you have the linux-firmware pkg installed on your Raring image? version 1.98? [16:29] plars, as long aas you have the latest kernel and latest ubuntu-default-settings-nexus7 [16:29] ogra_: awesome, thanks! [16:30] sfeole, indeed i do, else i wouldnt have wlan [16:30] and linux-image-nexus7 [16:31] ogra_: i'm trying to find out what each pkg does, linux-firmware-nexus7_0.2 and linux-image-nexus7 [16:31] linux-image-nexus7 is a metapackage that depends on the latest kernel [16:32] linux-firmware-nexus7 carries the closed binary firmware bits used on the nexus [16:32] ok [16:32] both need to always be installed [16:33] plars, crap, i think we're missing a securetty entry, i get a prompt but cant log in [16:44] * sfeole cheers as he upgrades to raring from Q, [16:44] ogra_: i just filed a 2nd bug.. #1087335 [16:45] bug #1087335 [16:45] Launchpad bug 1087335 in ubuntu-nexus7 "linux-firmware-nexus7_0.2 fails to install while dist-upgrading from Q -> R" [Critical,Confirmed] https://launchpad.net/bugs/1087335 [16:45] janimo, ^^^ [16:46] thats why i was asking about those packages [16:46] ogra_, are we still supposed to support Q->R upgrades? I thought 12.10 were play only demo images and we should recommend fresh install on R [16:46] it would save us a lot of trouble [16:47] janimo, well, we said upgrades should work, even though we dont encourage them [16:47] ogra_, would we need conflicts markers in the package just because we used linux-firmware in the PPA? [16:48] I thought the whole point of 12.10 was here, you get to keep both pieces and we do not spend time on anything related besides initial UDS bringup [16:49] ogra@nexus7:~$ dpkg -l |grep firmware [16:49] ii linux-firmware 1.98 all Firmware for Linux kernel drivers [16:49] ii linux-firmware-nexus7 0.2 all Firmware for the Nexus 7 tablet. [16:49] janimo, conflicts wouldnt help [16:49] since you want both installed [16:50] oh, wait, conflicts ony [16:50] *only [16:50] yeah, that should work [16:50] or rarther replaces in that case [16:50] well whatever marker says some files moved to another package [16:51] what if we apt-get install linux-firmware [16:51] this will remove the nexus binaries [16:51] and then apt-get install linux-firmware-nexus7 [16:51] so make sure we do not let order be determined by apt [16:51] yes, that way would work, but isnt how apt does it [16:51] or even more hackily backport linux-firmware-nexus7 to Q PPA [16:52] just a replaces should do [16:52] ogra well would apt do anything else beyond installing the single specified package? [16:52] ogra_: "screen /dev/ttyACM0 115200" drops me into a login prompt ;) [16:52] Replaces for a PPA package - so carrying some cruft in a baely opened series feels ugly to me :( [16:53] sfeole, but can you get in ? i seem to have issues with that here [16:53] I think people insatlling 12.10 images are really knowledgable anyway and I would rather they sort the upgrade out by themselves or guided by a wiki [16:53] janimo, well, its a minor change that will save us lots of silly support questions [16:57] ogra_: yes i'm in, I had to hit "enter" initially to display the password prompt === help is now known as balloons1 [16:57] yeah, thats normal [16:58] ok, i'll blame my chromebook (client side) then === balloons1 is now known as balloons [16:59] http://pastebin.ubuntu.com/1415103/ [16:59] ogra_: ^^ [16:59] perfect, thanks for checking ! [16:59] plars, see above [17:02] bad chromebook! [17:02] heh, yeah, i blame hrw [17:02] he does all the chromebook stuff, so it must be his fault :P [17:49] ;D === Ursinha is now known as Ursinha-afk [18:50] fwiw, i blame him for everything. if it weren't for him talking about how awesome the chromebook is, my checking account wouldn't be so light === Ursinha-afk is now known as Ursinha [19:12] ogra_: so I have the usb serial stuff working fine (Thanks!) but I'm having a bit of trouble getting preseeding to work. I've tried adding my preseed file to the initrd that I'm pushing to it, but I'm guessing that by the time it gets there, it's already remounted userdata as root so I'm not finding it. Any suggestions? [20:32] \o/ usb serial ftw [20:32] * vanhoof just flashed todays image [20:44] vanhoof: yes, it's working pretty nicely I think, but any ideas on how to preseed the remainder of the install? [20:45] vanhoof: I've tried sticking a preseed in the initrd, as well as in the rootfs, no luck so far, but tbh I don't have much experience with preseeding just the oem-config portion so I'm not confident that I'm doing it right [20:46] plars: i've never done a oem-config preseed myself :\ [20:46] * vanhoof takes a look === You're now known as ubuntulog === ssweeny is now known as AndroUser [22:33] hey, anyone know if the raspberry pi has vfp? [22:33] yes it does [22:48] sweet. [22:54] mjrosenb: It's v6, however. [22:54] that indeed [22:55] mjrosenb: Which means that neither Ubuntu nor Debian armhf will run on it (but there's an unofficial Debian v6+hardfloat port called "raspian" just for the Pi) [22:57] infinity: yup. I need an armv6/vfp machine to test on. [22:57] infinity: and it certainly sounds like the raspberry pi fits the bill. [22:57] What an odd requirement. :) [22:57] well, I already have like 10 armv7 devices [22:58] As long as you like testing in slooooow motion, you'll have fun with the Pi. [22:58] It's cute, at least. [22:58] what is it clocked at? [22:58] I thought it was like 600 mhz [22:59] ok, 700 mhz [22:59] Yeah, 700. [23:00] so like half the clock rate of the upper end of my armv7's [23:00] Still, a 700MHz ARM11 isn't anywhere near 7/10 of Cortex-A8. [23:00] true. [23:00] And nowhere close to 7/10 of a 1G A9. [23:00] mjrosenb, why would you want to test on an armv6+vfp [23:00] The newer model with 512M of RAM might prevent urges to shoot yourself, though. [23:01] I'm getting my fix for that with a roku 2 :p [23:01] at least that is optimised for arm11 [23:01] and the one good thing I have heard about the pi, or really the bcm soc is that it is good at media [23:01] lilstevie: because firefox is going to attempt to support armv6, and I would like to make sure that we can do that. [23:02] oh I see [23:02] but we are requiring armv6 + vfp [23:02] because javascript uses doubles *EVERYWHERE* [23:03] Raspbian on a Pi may well be just the right testbed, then. [23:03] It ain't fast, but it should do the trick. [23:03] (For the love of god, though, don't compile on the thing) [23:03] haha [23:04] compiling on dual and quad core a9s is painful enough [23:04] I've come to terms with A9 performance. [23:04] Then again, I came from 68k porting, so I'm a bit weird. [23:05] infinity: I can't remember the last time I built on an a9 [23:05] Sadly, software is like goldfish, and it seems to bloat to fit your computer. [23:05] I cross compile basically everything [23:05] except on my a15 [23:06] Cause I swear today's (very fast, in comparison) ARM cores don't really do anything any faster than a 68k 10 years ago performing similar tasks. [23:06] 126 minutes to build firefox! [23:07] I did get a refresher course in just how many crazy drivers we build in distro kernels the other day. [23:07] Was doing some benchmarking with an upstream defconfig (cause building the package is just plain no fun as a benchmark)... Turns out that a defconfig on a Panda is about 10 minutes. [23:08] Whereas our distro kernels take hours. [23:08] infinity: most distro kernels just enable everything possible as a module [23:08] Zero_Chaos: Yes, and I know that. I just didn't realise how many modules that IS these days. [23:08] Zero_Chaos: Apparently, the answer is "a lot". [23:08] infinity: yeah, make -j64 is nice [23:08] Not on a Panda, it's not. :P [23:09] infinity: I would imagine not ;-) [23:10] Still, a defconfig in 10m isn't bad. It wasn't that long ago I used to build my own barebones monolithic kernels on x86 kit, and that was around 30m. [23:10] (Might have been around P200ish days?) [23:11] Okay, maybe I'm getting old, when I imply that the P200 wasn't that long ago. [23:12] -j5 is about as far as I can take the prime before more jobs make things slower [23:12] (tegra3) [23:12] http://paste.ubuntu.com/1413025/ <-- My unscientific quick tests on a PandaES. [23:12] and also agreed, computers may have gotten faster, but the software has gotten bigger [23:13] infinity, heh [23:13] building a kernel deb with pbuilder takes about an hour and a half on my trimslice [23:13] -j64 would probably make it weep. [23:15] lilstevie: Do you talk to the Trimslice guys much? [23:15] lilstevie: I'm kinda curious if they plan to rev the hardware with newer and shinier SoCs, or if it was a one-shot deal. [23:15] infinity, not really, the only times I have had questions for them I get "why would you want that" [23:16] Cause I like the idea and the form-factor, but it's obsolete by now. [23:16] yeah, someone has asked that question, and they said no comment [23:16] infinity: -j64 brings most systems to their knees pretty quick. -j brings nearly all systems to their knees [23:17] Zero_Chaos: The build machine we use for internal kernel test builds seems to have a sweet spot around -j256... Ish. [23:17] infinity, http://emea.kontron.com/products/boards+and+mezzanines/embedded+motherboards/miniitx+motherboards/ktt30mitx.html has my attention, except I am getting to the point where I would rather avoid tegra [23:17] (It's a 32-core i7-base Xeon with stupid amounts of RAM and a shamelessly fast stripe) [23:18] infinity, although most of the crippling in tegra systems is slow eMMC [23:18] infinity: yeah on that I'm guessing you could just rock "-j" and let it fork as much as it likes. even on kernel builds like that I can't keep it >200 jobs for very long so if you have that many procs give up and use -j [23:18] lilstevie: Curious that that's only clocked at 900MHz. [23:18] infinity: I have 32 amd cores and build in RAM [23:18] that board would be an interesting test cause it does have SATA [23:19] infinity, yeah, I noticed that too [23:19] infinity: so about 1/2 the intel system you describe [23:19] infinity, I wonder if it is for cooling [23:19] infinity, throw a heatsink on it and go nuts [23:20] on the tf201 they have managed to bring it out to 1.8GHz with all 4 cores active [23:20] but it does make the metal case nice and toasty [23:20] lilstevie: Maybe. I'm probably not going to buy any more A9s out of pocket. I suspect I'll pick up one A15 at some point with my own money, and then wait for someone to bless me with aardvarch64 silicon. [23:20] lilstevie: (Not counting useful items I actually need, like phones, of course. I just mean I'm not going to keep collecting toys) [23:21] infinity, yeah, I am getting a surface (waiting for it to arrive right now) but after that I am not paying for any more arm systems until aarch64 [23:22] infinity, the only exception to that may be a quad core S4, cause krait is crazy fast compared to A9 [23:24] but yeah, I am going to live with my current arm machines for as long as possible === AndroUser is now known as ssweeny