=== Sarvatt_ is now known as Sarvatt
[06:33] <YoBoY> hi
[06:35] <YoBoY> My laptop on natty is making fun of me. The desktop freeze very too often, sometimes I can go to a tty and restart gdm, sometines I only can use the power button. Can you guys give me some advices or help me report or find help on this bug ?
[06:43] <tjaalton> YoBoY: install the kernel from -proposed
[06:44] <YoBoY> hum... normally I'm already on proposed, I check
[06:44] <tjaalton> should be abi version 9
[06:46] <YoBoY> I'm on 2.6.38-9-generic
[06:47] <tjaalton> ok then
[06:49] <YoBoY> (i'm on the 64bit edition btw)
[06:50] <tjaalton> doesn't matter
[06:54] <RAOF> tjaalton: You wanted to test llvm support on your r300-r500 chips?
[07:16] <tjaalton> RAOF: no, sis :P
[07:17] <tjaalton> i have some firegl card, but don't know which generation it is
[07:19] <RAOF> tjaalton: Oooh, the ultimate in software-fallbacks!
[07:20] <RAOF> Anyway, it's in git.  Or, if you prefer, I'm sure I've got some prebuilt packages I could throw at you :)
[07:20] <tjaalton> YoBoY: looks like that kernel doesn't have the fix I was after..
[07:20] <tjaalton> RAOF: yeah, 32bit ones would be nice
[07:21] <tjaalton> RAOF: you wrote the patch for i915 that fixes a sh*tload of these natty crashers?
[07:21] <RAOF> tjaalton: By “crashes” you meen freezes?  Yes, and I finally aligned all the knobs to get it into stable-queue.
[07:22] <tjaalton> RAOF: yeah that, cool
[07:24] <YoBoY> tjaalton: the fix will be available soon ?
[07:24] <tjaalton> YoBoY: well it's not even in -proposed yet
[07:24] <tjaalton> as it seems
[07:25] <RAOF> It's in the 2.6.39 kernel, but not yet in any natty kernel.
[07:25] <tjaalton> right
[07:35] <YoBoY> there is a bug I can subscribe to follow the progress ?
[07:36] <tjaalton> yes
[07:36] <tjaalton> but I don't have it handy :P
[07:37] <tjaalton> there's also a ppa with a test kernel
[07:37] <RAOF> bug #740126
[07:37] <ubot4`> Launchpad bug 740126 in unity (Ubuntu Natty) (and 6 other projects) "Disabling an output can cause vblank events to be missed (affects: 76) (dups: 10) (heat: 380)" [High,Triaged] https://launchpad.net/bugs/740126
[07:46] <soreau> I'm having trouble in natty where after coming out of a fullscreen window, compiz is completely b0rked. There are major issues flickering and it bounces between front and back buffers that are remnants of previous frames
[07:47] <soreau> on rv350 with xorg-edgers installed
[07:48] <soreau> restarting compiz or even X does not help, it's like the driver is stuck in b0rken mode
[07:49] <soreau> I'm thinking it's a kernel/radeon module bug or mesa but not sure which
[07:49] <RAOF> soreau: It's not inconceivable that it's an X bug, either.
[07:50] <RAOF> tjaalton: Hm.  It seems I don't have an i386 build handy; I'll build one now.
[07:50] <soreau> RAOF: Right but how do I know where to file a report?
[07:50] <tjaalton> RAOF: got beefy hw for it? I have a dualcore here, so could build it myself too
[07:51] <RAOF> tjaalton: No beefy hardware here; just a dualcore.
[07:51] <tjaalton> ok, so maybe I'll just pull from git and build it here
[07:51] <RAOF> soreau: I'm *pretty
[07:51] <RAOF> sure* it's reported on xorg-devel.
[07:51] <RAOF> Also, I'm pretty ;)
[07:52] <soreau> Alrighty then :)
[07:52] <soreau> RAOF: You mean it's a known issue?
[07:52] <soreau> I saw mareko say something on dri-devel that might be the issue
[07:52] <RAOF> I think it might be.
[07:53] <soreau> apparently it only affects r3xx and not r5xx
[07:53] <RAOF> tjaalton: I'll leave you to build it then.
[07:55] <soreau> RAOF: Possibly OT: Do you know if ubuntu will run X in wayland or even package wayland in the next cycle (or two)?
[07:55] <tjaalton> it's packaged
[07:56] <RAOF> Run X in wayland by default in the next two cycles?  That's a big N O.
[07:57] <RAOF> Wayland is, however, packaged, and should be runnable under X and on the console for O.  We'll get a new snapshot that doesn't require cairo-gl, so nvidia users won't be shafted.
[07:57] <soreau> RAOF: I'm kinda thinking that wayland would make it's debut in ubuntu by just running X inside it but perhaps next year, there will be enough stable toolkits that it will be able to run native stuffs
[07:57] <soreau> but I'm merely speculating
[07:57] <RAOF> Well, that's the plan.
[07:58] <RAOF> However, 12.04 is an LTS; we're not going to throw Wayland under X in the LTS :)
[07:58] <soreau> ah ok
[07:58] <soreau> Also I'm curious what nvidia is planning to do WRT wayland. AFAIK, they have no plans to provide support for it in their driver
[07:59] <soreau> Will they ever cough up hw specs you think?
[07:59] <RAOF> All this is discussed in one of the Wayland sessions at UDS; the notes are on the etherpad.
[07:59] <soreau> RAOF: Link me?
[07:59] <RAOF> (Well, not the nvidia discussion; that's a whole different kettle of awkward)
[08:00] <soreau> I'm more curious to know than anything
[08:00]  * soreau doesn't even use nvidia
[08:02] <RAOF> http://summit.ubuntu.com/uds-o/meeting/desktop-o-xorg-wayland-something-or-other/
[08:02] <soreau> heh, wayland-something-or-other
[08:02] <soreau> RAOF: thanks
[08:05] <soreau> cool
[08:06] <soreau> I'm surprised how quickly wayland is taking off and gaining a large amount of support by everyone (except nvidia)
[08:06] <soreau> I wonder how compiz will fare ;)
[08:06] <RAOF> Compiz is surprisingly X-agnostic.
[08:07] <soreau> Yea I know. And porting to gles is probably only a quarter of the work
[08:07] <soreau> Porting to EGL might require an entire rewrite
[08:32] <tjaalton> RAOF: hum, building this on natty is more work it seems, need to backport llvm and libdrm
[08:33] <RAOF> tjaalton: Yeah, of course :).  I thought you were oneiricing :)
[08:33] <tjaalton> not on the desktop, though I could build it on my laptop which is dualcore as well
[08:33] <tjaalton> booted it up
[08:37] <tjaalton> and I'll upgrade the other laptop too, no point in keeping it on natty
[11:29] <tjaalton> RAOF: ok, finally got it built, but I have a hook that tries to install them and that phase fails
[11:40] <tjaalton> RAOF: http://pastebin.com/7n1LDKez
[11:40] <tjaalton> probably nothing, just a symptom of how the hook installs stuff
[11:40] <tjaalton> it just runs 'dpkg -i $tmpdir/*.deb'
[11:44] <tjaalton> hmm right, since libgl1-mesa-swx11 conflicts with libgl1, which is provided by libgl1-mesa-glx
[11:45] <tjaalton> so nothing to worry about, I just need to disable the hook because the failure makes the pbuilder run fail, and so the debs are gone :)
[11:54] <RAOF> tjaalton: Oh, ouwch!
[12:14] <tjaalton> so the thinkpad fan control doesn't work, and the kernel is reporting near-critical temperature..
[12:14] <tjaalton> while building mesa
[12:16]  * RAOF fires off an i386 mesa build.
[12:16] <tjaalton> it should finish soon though :)
[12:16] <tjaalton> my build
[12:16] <RAOF> If your laptop doesn't melt first! :)
[12:17] <RAOF> llvm takes a surprising amount of time to build.
[12:18] <tjaalton> placed a frozen bottle of water under the machine :)
[12:18] <RAOF> Or, rather, there's an annoying delta between build_time(on launchpad buildd) and  build_time(on laptop)
[12:19] <soren> For the longest time, stuff was quicker to build locally than on the buildd's.
[12:22] <tjaalton> ooh, dpkg-shlibdeps.. soon finished
[12:22] <tjaalton> CPU temp down to 81
[12:23] <tjaalton> if i'm reading /proc/acpi/ibm/thermal right
[14:23] <tjaalton> ok, so how do I determine if llvmpipe is used or not?
[14:23] <tjaalton> swrast_dri.so is loaded
[14:23] <Prf_Jakob> glxinfo | grep render
[14:25] <tjaalton> http://paste.ubuntu.com/614934
[14:26] <Prf_Jakob> you are not running llvmpie.
[14:27] <tjaalton> right
[14:27] <Prf_Jakob> it should say "Gallium 0.4 on llvmpipe" or something like that
[14:27] <tjaalton> does it build a dri driver of its own?
[14:28] <tjaalton> maybe the packaging change wasn't complete
[14:32] <Prf_Jakob> dunno, upstream it was/is called swrastg_dri.so
[14:33] <tjaalton> yeah, probably just needs to be included in the package then :)
[17:45] <seb128> is #ubuntu-x tracking glew?
[17:45] <seb128> is there any plan to update to 1.6?
[17:46] <seb128> does anybody know if bug #711401 got investigated after the version revert to figure if the issue was a nux or glew one?
[17:46] <ubot4`> Launchpad bug 711401 in unity (Ubuntu) (and 3 other projects) "update to glew 1.5.7 broke unity (dup-of: 711396)" [Undecided,Confirmed] https://launchpad.net/bugs/711401
[17:46] <ubot4`> Launchpad bug 711396 in nux (Ubuntu Natty) (and 4 other projects) "segfault in nux::IOpenGLFrameBufferObject::Deactivate (affects: 42) (dups: 13) (heat: 178)" [Undecided,Fix released] https://launchpad.net/bugs/711396
=== yofel_ is now known as yofel
=== soren_ is now known as soren
=== maxb_ is now known as maxb