**** BEGIN LOGGING AT Tue Jul 17 02:59:58 2012 Jul 17 03:07:12 robclark: Patches welcome. ;) Jul 17 03:07:33 robclark: The whole QT/GLES thing is a royal pain to mangle. Jul 17 03:24:06 infinity, ok.. I was just chasing up a bug reported on pandaboard list from someone who had somehow enabled desktop fx... so was wondering if I had missed installing something.. Jul 17 03:26:34 robclark: To be fair, I have no idea what does and doesn't work, I try out KDE so very infrequently. Jul 17 03:27:14 robclark: All I know is that the GL/GLES abuse between ARM and $everything_else makes all things QT and KDE a porting nightmare. ;) Jul 17 05:54:06 ogra_, I tried the ac100 installer with a local kernel that has the NLS pieces built in. It goes on but it does not write the config boot image and boots into the initial one. There are errors saying init: abootimg not found Jul 17 06:18:35 janimo: Which sounds a whole lot like abootimg isn't installed. :P Jul 17 06:44:52 why arn't you guys running precise kernels on your buildds? Jul 17 06:46:21 infinity, right, but I am not sure anything should have changed in the initrd generation, hence calling ogra :) Jul 17 06:46:40 scientes: Because they're not all precise. Did a build blow up due to kernel version? Point me at it, and I can fix it. Jul 17 06:48:20 scientes: The plan is to upgrade them all to precise/armhf over the next week or two, but it's a reinstall (since they were previously natty/armel), so a bit irksome. Jul 17 06:49:33 infinity, well actually i did my research, and my package would need 3.4 to build with its current settings, i downgraded a try-execute test to a link-test, and never realized that gcc-4.7 has support for 8-byte atomics on arm Jul 17 06:49:48 infinity, ABI bump needed for kernel modules/built-in changes or just strictly for actual changes in the signatures, data structs? Jul 17 06:49:57 scientes: 3.4? Eh? Jul 17 06:50:00 so the setting is incorrect, and next upload will hard code turning it off on armel Jul 17 06:50:05 scientes: The atomic helpers in the kernel are in 3.1 Jul 17 06:50:11 I see skipabicheck and skipmodulecheck as different toggles, so I think that may be the case Jul 17 06:50:15 scientes: Trust me. Which package is this? Jul 17 06:50:23 oh really Jul 17 06:50:26 scientes: No, really. Trust me. :P Jul 17 06:50:28 i just used git describe Jul 17 06:50:34 scientes: It'll build on sigbin. Jul 17 06:50:38 ok kyotocabinet Jul 17 06:51:20 Yeahp, that will build fine on sigbin. I'll toss it there now. Jul 17 06:53:06 janimo: Hrm? abicheck is all about exported interfaces. If a module is built-in, it wrong trigger it. Jul 17 06:53:35 janimo: Of course, modulecheck will blow up if you're moving modules around from built-in to not (was that the question?), and yes, that should be an ABI bump. Jul 17 06:54:12 janimo: Enabling something that wasn't previously on at all, however, would not be an ABI bump. Jul 17 06:54:22 janimo: (unless it changes something else) Jul 17 06:54:25 infinity, ok. Just did not know whether ABI change is a superset of drivers moving drom built-in to modules or vice-versa change Jul 17 06:54:46 this is actually from modules to built-in Jul 17 06:54:55 NLS modules for the installer to be happy Jul 17 06:55:20 janimo: Strictly speaking, "ABI" was originally meant to just represent the module ABI, so ignored the modules themselves, but we now use it as a superset to also deliver guarantees of availability. Jul 17 06:55:31 So, if a module disappears (or moves between image and modular), that's a break. Jul 17 06:55:43 If one's added, that's perfectly fine. Jul 17 06:56:01 And I think I'm being repetitive now, so I'll shut up. ;) Jul 17 06:56:19 janimo: If in doubt, rev ABI. It doesn't really hurt anything to be wrong in that direction. Jul 17 07:24:21 infinity, the only thing it hurts is new binaries and meta needed Jul 17 07:41:25 janimo: pci-e is not used on ac100, I think I activated it sometime to shut down something (clock or pinmux), but I haven't measured power consumption yet Jul 17 07:41:46 lilstevie: I mean kernel oops with plymouth (not no splash) Jul 17 07:47:30 Hi all Jul 17 07:47:44 I just tried to install 12.04 on a pandaboard, did a dist-upgrade Jul 17 07:47:53 then tried to install the pvr driver via jockey Jul 17 07:48:24 it fails... it did a while back when I tried too Jul 17 07:48:30 any known workaround? Jul 17 08:35:51 janimo, ah, yeah, thats just a missing chroot call, abootimg isnt in the initrd, i changed the bootconfig handling to match with flash-kernel 3.0 but forgot that i need to call abootimg chrooted from the target partition Jul 17 08:36:38 i'm just preparing ext2 media here to do a test install Jul 17 08:52:13 janimo, fix uploaded Jul 17 09:12:43 * ogra_ has oem-config :) Jul 17 09:14:54 hi guys. have you all come across this: Couldn't open /sys/bus/nvhost/devices/host1x/syncpt/22/max ? is there a set of patch(es) which adds this interface in? Jul 17 11:08:37 grmbl Jul 17 11:09:12 flash-kernel always exits "1" on the ac100, no wonder it doesnt work Jul 17 11:20:48 marvin24: the plymouth oops that locks up the whole system affects us too Jul 17 11:23:31 yay, fixed Jul 17 11:24:09 janimo, the next ac100 image shold be fully installable now (from ext2/3/4 media though) Jul 17 11:24:33 silly bug in flash-kernel Jul 17 11:25:10 ogra_, great Jul 17 12:05:54 lilstevie: are you able to dump the oops? Jul 17 12:07:14 if not, does it look like this one http://paste.ubuntu.com/1095134/ ? Jul 17 12:11:33 marvin24, bug 1018907 Jul 17 12:11:34 Launchpad bug 1018907 in plymouth "plymouth in quantal on arm does only boot with black screen" [High,Confirmed] https://launchpad.net/bugs/1018907 Jul 17 12:11:45 try the rm /lib/plymouth/renderers/drm.so workaround Jul 17 12:12:06 ogra_: that's different I think Jul 17 12:12:23 well, it makes plymouth by default talk to the kernel sdrm interface Jul 17 12:12:31 *kernels drm Jul 17 12:12:40 you mean this could cause an oops? Jul 17 12:12:54 well, it would be a kernel bug, but yeah Jul 17 12:13:48 I'll test it later on but i doubt that's the reason Jul 17 12:13:54 i.e. on omap4 we have a drm device thats not connected to anything, there the plyouth output just gets /dev/null'ed Jul 17 12:14:17 who knows whats there on nvidia ... very likely no drm device :) Jul 17 12:14:40 tegra2 has no drm compiled into the kernel I think Jul 17 12:20:01 ogra_, is that issue fixed in ac100 by blacklisting something? Jul 17 12:34:31 marvin24, it does not look like that it just blacks out Jul 17 12:40:29 janimo, nope Jul 17 12:40:52 lilstevie, you should too try the workarouond from the bug above Jul 17 12:49:23 ogra_, ok I will get to it eventually Jul 17 12:50:58 hmm, having the desktop defaulting to suspend on lid close but having the kernel break on suspend isnt really a great combo Jul 17 12:53:13 * ogra_ tries the nvidia driver from the archive with todays image Jul 17 12:56:14 haha Jul 17 12:56:27 I wish my lid close sensor was working correctly Jul 17 12:58:56 BAH ! Jul 17 12:59:31 "module ABI major version (11) doesn't match the server's version" Jul 17 12:59:35 GRMBL Jul 17 12:59:54 there are days where i hate progress Jul 17 13:02:05 * LetoThe2nd hands ogra_ some i286 box. Jul 17 13:02:32 heh Jul 17 13:02:39 *g* Jul 17 13:02:50 k, fixed Jul 17 15:33:11 infinity, when adding a new package to a released series, what source does one file the SRU bug against? Jul 17 15:33:23 trying to get in new packages into 12.04 Jul 17 15:35:12 * ogra_ would just file against the ubuntu product Jul 17 15:35:34 after all the ubuntu-sru team works by subscription. so the package name shouldnt matter a lot Jul 17 15:39:37 ogra_, ok thanks Jul 17 16:25:08 sigh, forgot to touch modules.ignore (or was it ignore.modules) now ac100 kernel FTBFS :( Jul 17 16:25:16 I . HATE. PACKAGING Jul 17 16:25:28 double hate kernel packaging Jul 17 16:26:47 janimo, it wouldn't be such a pain if it didn't take so long to build Jul 17 16:27:16 I actually mind the time it takes of my life not of the build machines :) Jul 17 16:27:56 that is why I am sloppier about it than I would if we had some big timesharing server where we'd get limited cycles Jul 17 16:28:26 but if feedback of mistakes was faster you would learn better Jul 17 16:28:57 a conceptually simple change described in English as 'make NLS codepage 437 built in instead of module' which could be even terser in a special purpose language is a long series of error prone steps Jul 17 16:29:33 scientes, it is not about learning. It is stuff I more or less know but practice not frequently enough to have it on autopilot :) Jul 17 16:38:29 scientes, and it does not take that much when cross-building btw. On my fr from top of the line machine it is at most 20 min Jul 17 16:38:38 s/fr/far/ Jul 17 16:38:57 janimo, except that when compiling on buildds you ARNT cross-compiling Jul 17 16:39:15 not long enough to be prohibitive, but long enough for my attention-span to go out the window a few times in that interval Jul 17 16:39:32 wow, i though a gcc compile was going to take forever, but not on a octo-core xeon ;) Jul 17 16:39:37 scientes, most bugs I can catch cross-building I just did not cross-build the 3rd time today Jul 17 16:39:46 forgot that crappy modules thing Jul 17 17:02:55 janimo: Err, a new source that isn't in quantal? Jul 17 17:03:06 /wg 10 Jul 17 17:03:44 infinity, good point, completely forgot that requirement, as this was OEM/HWE driver for 12.04.1 images Jul 17 17:04:06 I could upload to quantal now, with only a changelog bump right? Jul 17 17:05:07 janimo: You could do, yes. We'd definitely prefer to see the source NEWed to quantal first, then backported to precise. Jul 17 17:07:02 infinity, shall I add a new changelog entry making it ubuntu2 - quantal and upload or something different? Not sure what a backport to precise should look changelog wise Jul 17 17:08:46 janimo: Would make more sense for ubuntu1 to go to quantal, and ubuntu0.12.04 (or similar) to precise. Jul 17 17:09:19 ah. ok. Please discard the 3 cedarview packages in NEW then Jul 17 17:09:36 Done. Jul 17 17:13:27 infinity, actually these depend on kernel patches too which intel only provided for 3.2.0. tseliot reminded me, I completely forgot about before Jul 17 17:15:10 janimo: Oh, you mean it literally can't be in quantal? Fun. Jul 17 17:15:42 infinity, yes, but I overlooked that. Jul 17 17:15:51 maybe with a forward ported kernel patch but not at the moment Jul 17 17:15:58 janimo: I'd still upload to precise as if it were a backport (so, with a "backporty" version number), but yeah, guess we'll have to NEW it into precise at some point. Jul 17 17:16:54 is there any way of undoing the purge or do we need a new upload :D ? These need upgrade path from existing PPA version numbers so 12.04 may not work. Could you join #hwe ? Jul 17 17:17:20 otherwise I keep proxying between you and the other cedarview packagers and I may add noise :) Jul 17 17:18:27 infinity, so since I got confirmation that these won't work in quantal could you remove the vaapi upload to quantal of 5 min ago? thanks :) Jul 17 17:20:05 janimo: Rejected from quantal. Jul 17 19:03:19 marvin24, do nvidia take patches to their 3.1 tree? looks like quite a few of your paz00 patches could live there, the mach is in their tree already Jul 17 19:04:52 I just out of curiosity rebased our current ac100 tree on nvidia's l4t/15. seems there are about 120 patches over it in your tree if I count correctly, and about 60 more Ubuntu packaging commits Jul 17 19:36:53 janimo: sure, I already forward some to them Jul 17 19:37:07 what patches do you refer to? Jul 17 19:37:46 ah, you mean to add full paz00 support to it? Jul 17 19:38:17 not a good idea ... Jul 17 19:38:41 the tree is only short living and who wants to take care of it? Jul 17 19:38:59 on the other hand, bugfixes are welcome I guess Jul 17 19:39:38 I already have enough stress to keep mainline up to date Jul 17 20:24:51 marvin24, well yes full paz00 that you carry now which does not affect other machs and some of it is already in nvidia's tree. But you know better :) Jul 17 20:26:10 janimo: yes, not worth the effort IMHO Jul 17 20:27:18 btw, removing the plymouth drm.o think didn't fixed the console problem Jul 17 23:08:09 the armhf SGX Ti binaries are available now? Jul 17 23:10:22 for omap3 Jul 17 23:17:58 cvanvliet_, only the kernel is differn't between devices Jul 17 23:26:51 scientes, the omap3 Ti SGX armhf binaries have not been available, and I just saw someone using them, and I was just following this up Jul 18 00:22:59 cvanvliet_: Using them from where? **** ENDING LOGGING AT Wed Jul 18 02:59:58 2012