[10:57] <Duke`> Hi
[10:58] <Duke`> I'm trying to build deb packages with xorg-edgers's xorg-pkg-tools
[10:59] <Duke`> I run "auto-xorg-git -t "~" -g -H hooks -d origin/ubuntu -p mesa", it creates the .orig.tar.gz, the diff.gz, the .dsc, the .build and the .changes
[10:59] <Duke`> but I have no .deb file at the end. Is it expected?
[11:00] <Duke`> do I have to make the .deb manually?
[11:00] <Duke`> what's next?
[11:21] <tormod> Duke`, yes these files are the source package. to build binary packages you can run debuild -b -us -uc
[11:22] <tormod> usually we upload the source package to a PPA
[11:23] <Duke`> ok, thanks, I'll look at this command
[11:24] <tormod> don't forget apt-get build-dep mesa before building binaries
[11:57] <Unggnu> hi all
[11:57] <Unggnu> I just wanted to ask if the patch from this report could make it into Karmic: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/435241
[11:57] <Unggnu> http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=blobdiff;f=drivers/gpu/drm/drm_edid.c;h=bbcb2e22675b127ce64454e69ba7a9abe55b6cc9;hp=80cc6d06d61b6ba53ae316a8de5112c8cf434a09;hb=5c61259e6c7290082108e93815f7f72f27da14f4;hpb=26bbdadad356ec02d33657858d91675f3e9aca94
[11:58] <Unggnu> * http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=5c61259e6c7290082108e93815f7f72f27da14f4
[12:02] <Duke`> hum, is there a way to make the building use more than one CPU core?
[12:03] <Unggnu> Duke`: sure -j CORENUMBER
[12:03] <Duke`> can I pass it to debuild?
[12:03] <Unggnu> some say you should use 1,5xCores
[12:04] <Unggnu> I don't know, but it works with dpkg-buildpackage
[12:04] <Unggnu> afaik
[12:04] <Duke`> I know the option for make, but I'm generating deb package
[12:04] <Duke`> ok
[12:04] <Duke`> I'll try next time I build one :)
[12:04] <Unggnu> Imho the Debian-Script should recognize the core number on its own and pass it
[12:05] <Duke`> currently it's using one core of two, and it's slow :(
[12:05] <Unggnu> It has a huge impact if you have a quad core and compile the kernel or wine or similar big things
[12:05] <Unggnu> +especially
[12:07] <Duke`> yeah, I already experienced these benefits with only a dual core :)
[12:09] <Unggnu> that's why the build script should recognize its on their own, I mean the difference is even more severe with an i7
[12:35] <Duke`> ok, I have all my deb packages \o/ It was a bit long.
[12:35] <Duke`> thank you for your help tormod
[12:35] <tormod> Duke`, np. you know you can just d/l debs from xorg-edgers also right?
[12:36] <Duke`> yes, I've done that for months, but I need to track some performance regression
[12:36] <Duke`> so I'll try to do some bisecting myself...
[12:36] <tormod> I see, recompiling the whole mesa is quite long
[12:38] <tormod> yes, you know the tricks with mesa env vars so you can just test the libs without reinstalling?
[12:38] <Duke`> aahhhh, I've heard about them once but I forgot their existence...
[12:39] <Duke`> I should look at it, yeah
[12:39] <tormod> to save you the whole debuild > install debs, rerun cycle
[12:40] <tormod> maybe you can even git-bisect a built tree and only rerun make (or debian/rules build)
[12:40] <Duke`> without cleaning up? possible
[12:42] <tormod> for env vars, see http://dri.freedesktop.org/wiki/TestingAndDebugging
[12:47] <tormod> http://dri.freedesktop.org/wiki/Building also mentions LD_PRELOAD
[13:08] <lv_> hi folks - i'm having a hard time getting my extended desktop to work with ubuntu jaunty jackolope using an intel 945GM --- if I am to go through the process of enabling UXA - should i solve this problem
[13:08] <lv_> ?
[13:09] <lv_> as of now an output of lshw is showing my graphics controller to be 'unconfirmed'
[18:13] <ScottK> Urgh.  No compositing today all of a sudden on my mini 10v.  Bug report soon.
[18:50] <ScottK> Meh, of course as soon as I want to replicate the problem, it goes away
[19:04] <Duke`__> hehe
[21:06] <mdeslaur> hmm...I've updates karmic, and now Xorg uses 100% of the CPU all the time.
[21:06] <mdeslaur> s/updates/updated/
[21:08] <mdeslaur> the only thing that looks related in dpkg.log is mesa
[21:11] <pwnguin> hmm
[21:11] <pwnguin> is compiz running?
[21:13] <mdeslaur> pwnguin: no, I turn off desktop effects.
[21:14] <mdeslaur> although I tried turning compiz back on, same thing
[21:14] <pwnguin> my guess was compiz was somehow running in software mode
[21:15] <mdeslaur> not even touching the keyboard and Xorg is using 100% cpu
[21:16] <pwnguin> have you browsed /var/log/Xorg.0.log?
[21:16] <mdeslaur> yeah, but the only thing that looks odd is: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[21:17] <mdeslaur> hold on, I'll try logging out and loggin back in
[21:20] <mdeslaur> hmm...logging out and logging back in, the problem is solved and I have "(II) Open ACPI successful (/var/run/acpid.socket)"
[21:20] <mdeslaur> looks like X is starting before the acpid socket is there for some reason
[21:20] <mdeslaur> when I fresh boot
[21:20] <jcristau> shouldn't make a hugh difference though
[21:20] <jcristau> huge, even
[21:22] <mdeslaur> hmm...I was on vt 9 after a fresh boot, and now I'm on vt 7
[21:22] <mdeslaur> sorry, opposite
[21:22] <mdeslaur> 7 after a fresh boot, 9 now
[21:24] <pwnguin> you might see if there are other xorg logs of recent origin
[21:25] <mdeslaur> I found one from a week ago, no difference except for the acpi failure
[21:32] <mdeslaur> bug 441706
[21:37] <pwnguin> mdeslaur: how attached are you to 3d?
[21:40] <jcristau> oh, nvidia.  fun.