**** BEGIN LOGGING AT Tue Jan 24 02:59:57 2012 Jan 24 04:08:36 lilstevie: do you know if TF has a "multi-channel sound card" ? Jan 24 04:10:21 I'm afraid the answer is no, which makes me sad Jan 24 04:10:54 I tried using two mpg123 processes at the same time, the second one gave up Jan 24 04:52:03 twb: Try running mpg123 under padsp so it passes through a software mixer? Jan 24 04:56:52 infinity: pulseaudio? Jan 24 04:57:34 I don't allow pulse on my systems :P Jan 24 04:57:52 I was asking because I'm trying to get emacspeak up and running again Jan 24 05:02:28 twb: Heh. Jan 24 05:06:53 I can't actually get emacspeak to work at all yet Jan 24 12:22:29 hello - anyone around who can help me with this armel/armhf build failure - bug 920871 Jan 24 12:22:30 Launchpad bug 920871 in zookeeper "zookeeper 3.3.4+dfsg1-2ubuntu2 FTBFS on armel and armhf" [High,Confirmed] https://launchpad.net/bugs/920871 Jan 24 12:22:52 not quite sure where to start :-) Jan 24 12:23:00 (have reproduced locally) Jan 24 12:29:58 jamespage, does this help https://wiki.ubuntu.com/ARM/Thumb2 ? Jan 24 12:36:58 ogra_, yes thanks Jan 24 13:37:20 I'm having bus powered USB disk issues on the pandaboard. Should I just give up? Does this work for anyone else? Jan 24 13:37:58 rbasak: I have an usb disk but it wants external power with the pand Jan 24 13:38:01 *panda Jan 24 13:38:43 so doesn't work without? Jan 24 13:38:51 even though it in theory should? Jan 24 13:39:18 not sure why, that is just my experience Jan 24 13:39:29 I'm giving the panda a beefy enough PSU I think. But perhaps a varying load is causing issues. I get combinations of kernel panics and disk spindowns Jan 24 13:40:49 rbasak, the PSU TI shipped with my first panda is 5V 4A, what do you use ? i wouldnt go below 3A for hub powered USb disks Jan 24 13:41:21 5V 4A, and I also have been trying a 200W AT PSU Jan 24 13:41:56 well, that should work, whats the issue you see ? Jan 24 13:42:08 kernel panics Jan 24 13:42:23 actually USB related ones ? Jan 24 13:42:35 and sometimes the disk keeps spinning on and off in a fast (maybe 0.8s) cycle Jan 24 13:42:42 I don't think the panics are USB specific Jan 24 13:42:54 well why blame the disk then ? :) Jan 24 13:43:08 I suspect maybe the disk is causing the board voltage to drop, though I've metered it I won't be able to see short interval drops Jan 24 13:43:29 only this disk does it. my sata/usb docking station which is externally powered does not have the same issue Jan 24 13:43:56 hmm, well, might even be a driver issue Jan 24 13:44:25 i think there are plenty people running host powered usb disks on their pandas ... not that i have empirical data though Jan 24 13:44:35 OK I'm pretty sure it's a power issue. taruti gave me an idea - I connected the second bus power connector to a usb hub powered by my AT PSU instead of into the panda. And powered the panda from the power brick I have. Now it seems to be going OK Jan 24 13:46:21 Perhaps I need to make a "USB power boost" harness which supplies 5V to those secondary connectors outside the panda Jan 24 13:47:40 perhaps this particular drive model causes more noise on the usb power affecting the panda? Jan 24 13:47:44 I just bought the cheapest one Jan 24 13:48:03 it's an intenso 320GB Jan 24 15:50:23 Hey folks. I was curious if someone could build the HUD feature for ARM and check to see if it's responsive. Jan 24 15:50:46 It's very much so on my computer, so I haven't spent much time optimizing, but I'd like to ensure that's across platforms. Jan 24 15:51:05 I'm not super worried, but I want to make sure :-) Jan 24 15:51:20 if it is as responsive as the dash it will take 10-15sec to come up Jan 24 15:52:02 ogra_, On Unity or UnityQt? Jan 24 15:55:35 can it run in unity-2d too ? Jan 24 15:55:35 (GLES support for 3D unity isnt merged yet, so we can only run under -2d) Jan 24 15:56:06 -2d == Qt Jan 24 15:56:08 :) Jan 24 15:56:34 ogra_, 2d is Qt only until Qt5 is out, then they're all 3d :-) Jan 24 15:56:42 we only have the Qt version on arm atm until the GLES patches from linaro get merged into unity Jan 24 15:56:56 ogra_, I thought Unity could run on the Pandaboards? no? Jan 24 15:57:10 ogra_, Is that with the ES patches? Jan 24 15:57:51 right, they are a) not merged (waiting since the dublin sprint) and b) still have a few bugs Jan 24 15:58:17 so all we can currently run proper is unity-2d (Qt) Jan 24 15:58:54 rbasak: Most USB powered drives require two USB connectors to get enough power, but unfortunately even then the panda doesn't deliver enough power from the usb ports. All of my USB<>SATA drives have separate power source, which isn't easy to find on 2.5" enclosures. Jan 24 15:59:00 ogra_, Hmm, okay. Is that plan updated? I thought there was a plan to merge those branches discussed in Budapest. Have you talked to the Unity guys about that since then? Jan 24 15:59:31 GrueMaster: aha, that'll be my problem then. I've tried connecting the second connector to an external source but that only seem to work some of the time. Thanks! Jan 24 15:59:32 tedg, once a week, yep. its in the process and hopefully ready by feature freeze Jan 24 15:59:52 ogra_, Cool, I'll leave you to it then! :-) Jan 24 16:00:09 tedg, btw, the HUD is public stuff now ? Jan 24 16:00:17 * rbasak wonders what to do with this drive that's going spare now Jan 24 16:00:20 * ogra_ didnt see any blogpost yet Jan 24 16:00:30 ogra_, Yup: http://www.markshuttleworth.com/archives/939 Jan 24 16:00:44 ah, k, had no time to follow planet since budapest Jan 24 16:01:29 ogra_, But you're a voracious reader of OMG! Ubuntu!, right? ;-) Jan 24 16:01:44 heh, rather planet than OMG :) Jan 24 16:16:59 k1l: didn't know you also hang out here ;) Jan 24 16:17:08 ;) Jan 24 16:24:57 ppisati: Any chance of getting the omap4 kernel fixed or at least removed from the pool today? Jan 24 16:31:57 GrueMaster, AIUI ppisati sent a fix to the list today Jan 24 16:33:57 GrueMaster: yep, sent, waiting for the upload Jan 24 16:34:12 Ok. Jan 24 16:34:23 btw, do anyone know why the arguments for the kernel cmdline changed? Jan 24 16:34:38 dpkg -S /boot/boot.script says it doesn't belong to any package Jan 24 16:34:59 so it must some hand-crafted stuff coming from the installer Jan 24 16:35:20 *it must be Jan 24 16:35:29 The boot script is generated during install, not by any packages. For preinstalled, it is created by jasper. Jan 24 16:35:46 For netinstall, it is generated by f-k-i (I think). Jan 24 16:44:04 ok Jan 24 16:44:28 and do we have a changelog of it? why an arg was added/deleted? Jan 24 16:45:17 What arg was added/deleted? Jan 24 16:46:24 GrueMaster: mem=456M@0x80000000 mem=512M@0xA0000000 Jan 24 16:46:54 GrueMaster: these two are not of boot.script anymore and one of the feature of our kernel (CMA) craps out without it Jan 24 16:47:05 s/it/them/ Jan 24 16:47:10 That arg is only necessary when using the closed source video decoder. Shouldn't have any affect when running server/headless. Jan 24 16:47:24 it has with CMA Jan 24 16:47:51 without these args it doens't initialize the pool at boot, and when the usb ask for some DMA buffers, kaboom Jan 24 16:47:57 that's what you get yesterday Jan 24 16:48:02 i sent a revert of this CMA Jan 24 16:48:11 since it's not mandatory and it's not even in mainline Jan 24 16:48:18 but the camera driver needs it Jan 24 16:48:18 so Jan 24 16:48:31 we either drop the camera driver, or we revert these args Jan 24 16:48:37 Then that is a new change, as I have been running w/o those settings on all headless images since Maverick. Jan 24 16:48:46 yep Jan 24 16:48:56 it was bropught in with the last TI bits Jan 24 16:49:07 btw i had these args since i started working here Jan 24 16:49:19 that's why i didn't notice CMA panicng at boot Jan 24 16:49:40 As to the netinstall cmdline parameters, they were never added when netinstall was created. I'd have to look, but I'm not sure they are even in the server preinstalled images. Jan 24 16:49:53 uhm ok Jan 24 16:49:58 anyway the revert is on its way Jan 24 16:50:00 so... Jan 24 16:51:17 Those parameters create a hw memory hole so that a specific hw device can use that address range. Not sure why it can't be a bit more intelligent and request it on module load. Jan 24 16:52:33 perhaps because if you don't explicitely say so at boot time, the entire memory would be mapped (and couldn't be reclaimed later) i guess Jan 24 16:52:58 Ok, those parameters are on the server preinstalled (which makes sense as they are hardcoded in jasper). Jan 24 16:53:34 I'll bug NCommander to add them to the netinstaller when he comes online. Jan 24 16:53:54 no no Jan 24 16:54:01 But as I said, we were told they were only needed for the closed source decoder bits. Jan 24 16:54:04 i already asked for the revert Jan 24 16:54:25 these won't be necessary anymore after nex upload Jan 24 16:54:44 But is that what TI wants going forward? Jan 24 16:55:06 well, CMA is not even mainline Jan 24 16:55:14 so when it will hit mainline, we'll see Jan 24 16:55:23 If their patches are now enabling it, then we should make sure all images are consistent. Jan 24 16:55:43 (we should make sure netinstall is consistent anyways). Jan 24 16:56:22 i was wondering why linaro has no such problems Jan 24 16:57:37 They may have that parameter as default on their images. Jan 24 16:58:31 could be Jan 24 16:58:53 i tried to ask it to agreen Jan 24 16:59:01 but he didn't answer yet Jan 24 16:59:01 For now, if that is all that is required for netinstall to work, that is easy to fix (w/o reverting the patch). Netinstall can be preseeded to include those parameters during install and the netinstall image can be fixed to have them on boot. Jan 24 16:59:30 yes, that would fix it Jan 24 17:00:05 My concern now is that by reverting it, are we causing issues to TI's development work down the road? Jan 24 17:00:19 revert the patches? Jan 24 17:00:26 this is just for 3.2 Jan 24 17:00:37 and since TI won't support it/as, we stay as it is Jan 24 17:00:56 for 3.3 we will get it, and bunch of new drivers exploiting it (i guess) Jan 24 17:01:37 Then we are better off leaving the kernel as is and fixing netinstall. Less pain in the long run. Jan 24 17:03:24 GrueMaster: when you say the binary driver, do you mean the pvr-omap4 dkms? Jan 24 17:03:59 Not sure if it is that one or the gstreamer code (think it was gstreamer though). Jan 24 17:04:27 ogra_ would know. Jan 24 17:04:32 Or ndec. Jan 24 17:04:45 k Jan 24 17:04:58 * ogra_ looks up Jan 24 17:05:40 ah Jan 24 17:05:50 * ndec too Jan 24 17:06:04 the cmdline is created at buildtime, only the root= parameter is added by jasper Jan 24 17:06:30 the memory hole is needed for ducati (the multimedia framework) Jan 24 17:07:07 ppisati: GrueMaster: i saw the email on kernel list, i am not sure i understand what the proposed fix is Jan 24 17:07:31 ndec: the problem is in the new memocry allocator (CMA) Jan 24 17:07:47 does it require the memory hole in bootargs? Jan 24 17:07:47 this CMA has never been in mailine, but we got it via tilt Jan 24 17:07:53 GrueMaster, the netinst images should have that cmdline params too, if not, NCommander should add them at build time Jan 24 17:07:59 because the camera driver needs it Jan 24 17:08:09 yes, it's in tilt because we use it for v4l2 camera driver. Jan 24 17:08:14 ogra_: Ok. I'll file a bug and assign to him. Jan 24 17:08:16 and later for MM with syslink3.0 Jan 24 17:08:30 since the usb crap was due to this memory allocator, i reverted it and now everything works Jan 24 17:08:39 GrueMaster, great, if he doesnt have the time, infinity or i can do it as well Jan 24 17:08:46 dunno why it doesn't init the pool at boot time if we don't pass the args stuff Jan 24 17:08:47 the camera driver should not need it. or there is something else missing. Jan 24 17:08:56 that's what agreen told me Jan 24 17:09:14 but i handed a couple of kernels without this cma to rbasak today, he testd it Jan 24 17:09:23 and all the panicing on boot&c are gone Jan 24 17:09:34 so i pushed the revert since we are close to kernel freeze Jan 24 17:09:44 i think the memory hole is just helping to hide another issue ;-) Jan 24 17:09:51 ogra_: iirc, we (NCommander and I ) had this discussion last cycle. Iirc, there was a problem getting others to accept the change. Jan 24 17:10:06 I will look into this, i would prefer we make the real fix instead. Jan 24 17:10:12 ndec: that's why i don't want it in (i mean the CMA) Jan 24 17:10:24 and our MM stuff with syslink3 will no longer require the memory hole anyways. Jan 24 17:10:39 but that's 3.3+ and we talking about a P kernel Jan 24 17:10:45 ppisati: no, i think we should keep it, but you might be missing another config somewhere. Jan 24 17:11:26 if you revert this one, you might want to revert the v4l2 camera driver as well, to ensure that nobody will attempt to use it. Jan 24 17:11:44 let me check one thing Jan 24 17:12:02 on the other hand if you keep it, and if we fix it properly, then all the boards that have a camera (blaze have, and some panda do) will get support for camera out of the box with 12.04... Jan 24 17:12:24 ndec: does our kernel boot on that boards? Jan 24 17:12:32 yep Jan 24 17:12:48 sebjan maintains blaze support in tilt tree Jan 24 17:13:41 ppisati: let me reply on the mail and let's try to sort it out. you can use the mem hole as a temp workaround. since it's really no longer needed moving forward, i would prefer to get rid of it... Jan 24 17:15:02 * ogra_ wouldnt be opposed Jan 24 17:15:14 its one hack less we have in the image builds Jan 24 17:16:11 ok, but then remember to get the memory hole back in place Jan 24 17:16:30 ppisati, i thought ndec just proposed to get rid of it Jan 24 17:16:56 ogra_: actually the opposite Jan 24 17:17:00 ;-) Jan 24 17:17:15 ogra_: he wants to reintroduce it to workaround this problem Jan 24 17:17:27 ppisati, anyways, we didnt change anything wrt kernel cmdline in precise yet Jan 24 17:17:37 ogra_: yep Jan 24 17:17:40 its still there, hasnt gone anywhjere Jan 24 17:17:49 ogra_: it's just that this cma came via last kernel update Jan 24 17:17:49 unless you used a netinstall Jan 24 17:18:07 ogra_: and my default boot.scr has those mem args in it Jan 24 17:18:15 right Jan 24 17:18:17 that's whty i didn't notice the panic on boot Jan 24 17:18:57 you will only see it on netinst since apprently NCommander didnt take them into account when building the image *or* in f-k-i Jan 24 17:19:14 not sure where they are missing there exactly Jan 24 17:19:54 So, what is going to be the goal here? a) fix netinstall to include the hole, or b) fix the kernel cma to not need the parameter on the cmdline? Jan 24 17:20:54 sounds like b) as the final goal and a) as the interim Jan 24 17:20:59 right Jan 24 17:21:36 not sure how long b) will take Jan 24 17:21:55 if its only a few days, changing netinst might be wasted time Jan 24 17:22:35 GrueMaster, so the answer is "depends ... " Jan 24 17:23:21 Well, we can work around the netinstall issue for now, but I wouldn't recommend it long term. Jan 24 17:23:57 If the kernel can be fixed before freeze, then netinstall workaround is the way to go. Jan 24 17:24:14 right Jan 24 17:24:17 If not, a more permanent netinstall fix is required. Jan 24 17:28:11 Ugh. Now I remember why it wasn't in the netinstall (or at least on my testing). u-boot cmdline is limited to ~256 characters. I'm getting ready to verify it now, but if that is still the case, it screws up automation in a huge way. Jan 24 17:35:22 Grrr. And netinstall doesn't seem to care about debian-installer/add-kernel-opts in the preseed. grumble. Jan 24 17:41:51 GrueMaster: does latest 12.04 image boot on panda and es? Jan 24 17:42:01 i was told (didn't try) it wouldn't boot Jan 24 17:42:03 on es Jan 24 17:42:36 I just booted today's daily-preinstalled desktop image ok. Jan 24 17:42:56 And I have a couple of systems running netinstall now. Jan 24 17:43:12 on panda ES? Jan 24 17:43:18 The desktop is running on my 4460 ES. Haven't seen any issues. Jan 24 17:45:37 ok. thx Jan 24 17:45:41 I haven't done a "full" test, but desktop is installed and running. I'm currently sitting in unity2D with an open terminal. Couple of kernel warnings in dmesg (early during boot), but nothing serious. Jan 24 18:23:51 bug 920618 Jan 24 18:23:51 Launchpad bug 920618 in debian-installer "Setting "d-i base-installer/kernel/image none" fails to ignore installation w/o kernel" [Undecided,New] https://launchpad.net/bugs/920618 **** ENDING LOGGING AT Wed Jan 25 02:59:56 2012