**** BEGIN LOGGING AT Wed Feb 23 02:59:56 2011 Feb 23 12:29:39 Hi, while testing the Natty Alpha2 image on panda, I need to run a 'sudo dhclient -4 usb0' to get an IPv4 allocated (else, I seem to have an IPv6 only). Is this expected / known behavior? Feb 23 12:41:56 not expected and i dont see it on my panda Feb 23 12:42:14 NM just does what it's supposed to Feb 23 12:55:17 ogra: I don't see the nm-applet in the bar, and ifconfig does not provide a IPv4. after the above trick, I can get a network connection through usb0, but still do not see the nm-applet (I'd like to configure my wlan connection with in in fact) Feb 23 13:06:43 sebjan: check if you have nm-applet running, if so then check if the network manager daemon is running Feb 23 13:06:52 otherwise it's not going to show itself at the bar Feb 23 13:07:33 rsalveti: nm-applet is running actually, but not hint on network-manager (it shall be called like this?) Feb 23 13:07:58 sebjan: NetworkManager Feb 23 13:09:50 rsalveti: ok, not running either Feb 23 13:10:29 I suspect that it fails to run properly since I activated the wlan: I need to make some tricks to be able to use the wlan, and this may upset network manager... Feb 23 13:10:38 sebjan: try service network-manager start Feb 23 13:10:47 could be Feb 23 13:11:17 sebjan: run NetworkManager --no-daemon --log-level=DEBUG Feb 23 13:11:23 then you can check why it's failing Feb 23 13:12:06 rsalveti: ok, thanks, I'll do that Feb 23 13:24:56 sebjan, and make soure you didnt touch /etc/network/interfaces ;) Feb 23 13:25:06 else NM will ignore your interface Feb 23 13:36:33 damn, network manager segfaults... Feb 23 13:38:54 sebjan: are you using maverick? Feb 23 13:39:15 rsalveti: no, Natty alpha2 Feb 23 13:42:01 sebjan: hm, if you didn't update than this maybe fixed already with latest upload Feb 23 13:42:19 sebjan: we had some issues and instabilities with NM during the alpha2 time Feb 23 13:43:09 right, I will make an upgrade: I just see that during gdm start, network manager is started/dies/re-started/dies/... Feb 23 17:39:43 rsalveti: hi there! we're looking at the question of building qt4-x11 with gles2 enabled on armel instead of opengl; if we did this in the official package in natty, do you know if that would cause regressions? Feb 23 17:40:17 i.e.: I don't think there are any accelerated full-opengl drivers available in Ubuntu, but I know we have gles2 for panda, so it's a win there... but what about unaccelerated systems? Feb 23 17:40:20 slangasek: would affect some kde packages, and some others from universe Feb 23 17:40:33 affect them adversely? Feb 23 17:40:49 is that because it would introduce ABI changes, or for other reasons? Feb 23 17:40:50 bug 707794 Feb 23 17:40:50 Launchpad bug 707794 in qt4-x11 "libqt4-opengl on armel should be compiled with OpenGL ES 2.x support" [Undecided,Confirmed] https://launchpad.net/bugs/707794 Feb 23 17:41:17 slangasek: the main problems is a conflict that happens when you have an application that needs GL and uses libqt4-opengl Feb 23 17:41:41 once we build qt with the gles backend, the symbols will conflict Feb 23 17:42:01 symbol collision> oh, interesting Feb 23 17:42:17 because Qt lets the user to use GL directly, together with Qt Feb 23 17:42:21 yes Feb 23 17:42:49 so those libraries should really have symbol versions applied, but I guess that may technically be a violation of the standard ABI Feb 23 17:43:21 thanks for the bug reference. Do you know of any issues besides what's mentioned in that bug? Feb 23 17:43:57 worst case, we will probably provide a gles2 build in our ppa for this cycle Feb 23 17:44:29 but I would like to dig deeper to see if we can resolve the symbol problem for the short term, without compromising future development work on the proxy library Feb 23 17:45:31 slangasek: for the moment I believe having it on a ppa should be enough Feb 23 17:45:47 the problem of sharing many symbols Feb 23 17:46:07 and also, if you link with libqt4-opengl it'll bring EGL and GLES2 Feb 23 17:46:27 headers collision and more Feb 23 17:49:21 * ogra would really like to see the core libs to be GLES on arm ... ignoring the few packages that will break until they are fixed properly Feb 23 17:49:29 it's "enough", but ppas are only 2GB and if we put qt4 in our linaro overlay ppa, that's a good chunk gone :) Feb 23 17:49:49 imho its a failure of the apps to be programmed in a broken way Feb 23 17:51:13 well, Qt gives you the liberty to use GL together with Qt Feb 23 17:51:20 and also support different backends Feb 23 17:51:37 how about having a libqt4-gles ? Feb 23 17:51:39 so it's not something like clutter, that you only use the clutter API Feb 23 17:52:08 (arm only indeed) Feb 23 17:52:10 ogra: and in what that will help us? Feb 23 17:52:47 then we would need to change all the packages we want to link with the new libqt4-gles package Feb 23 17:53:18 yes, it would need some buildd sided magic i guess Feb 23 17:53:21 and probably need some work in qt to generate both libs without many issues Feb 23 17:53:35 without having 2 different qts in the archive Feb 23 17:53:43 yes Feb 23 17:54:08 no, building libqt4-gles is not a good solution Feb 23 17:54:09 its surely a lot of work (and surely nothing for natty) Feb 23 17:54:17 that's why having it on a ppa would be easier for the moment Feb 23 17:54:32 while we don't have the proxy lib and the gles support for glew Feb 23 17:54:33 I'm going to have a look at symbol versioning on the gles2 side Feb 23 17:54:35 i would still prefer to rather ignore the handfull of apps Feb 23 17:55:12 as a fallback, we might disable the opengl-needing packages in discussion with the Kubuntu team Feb 23 17:55:23 yup Feb 23 17:55:42 ++ Feb 23 17:55:48 software rendering with opengl on arm is basically having nothing Feb 23 17:55:53 very very slow Feb 23 17:55:55 so, no use Feb 23 17:55:59 * slangasek nods Feb 23 17:56:18 * ogra disagrees :) Feb 23 17:56:31 you should see composite on framebuffer here on the ac100 Feb 23 17:56:51 no noticeable difference to non-composite metacity Feb 23 17:56:58 * hrw confirms Feb 23 17:57:13 hm, cool, good to know :-) Feb 23 17:57:13 seems to depend on the HW :) Feb 23 17:58:16 ogra: how fast is membus on ac100? Feb 23 17:58:26 400MHz ? Feb 23 17:58:31 not sure Feb 23 17:58:39 ok Feb 23 18:42:49 So, the image doesn't have initrd.img in /boot on the second partition. Why? Feb 23 19:13:12 Hello, I am trying to get cross-compiling environment (including autotools) for Arm on Ubuntu 10.04. What is the best way to proceed? Feb 23 19:44:21 GrueMaster: probably something is broken at the update-initramfs part Feb 23 19:44:28 or the hook while installing the kernel Feb 23 19:56:02 The uImage is on the boot partition, and there is a link in /boot, but no actual file. Feb 23 20:06:14 so it could be a problem at the update-initramfs Feb 23 20:06:37 try mounting and installing with qemu Feb 23 20:06:53 to see if the the update-initramfs is called at the postinst Feb 23 20:52:46 rsalveti: It is something with the image generation. uImage wouldn't exist if update-initramfs failed. Feb 23 20:52:57 And it works fine on an installed image. **** BEGIN LOGGING AT Wed Feb 23 22:23:30 2011 **** ENDING LOGGING AT Thu Feb 24 02:59:57 2011