[02:22] <bryceh> RAOF, wow, Intel's getting flamed hard for 8xx on phoronix
[02:22] <bryceh> (at least, in the comments)
[02:25] <ScottK> Does Phoronix ever say anything nice about anyone in the comments?
[02:26] <ScottK> Last thread I heard about it was Intel was wonderful and Kwin was just asking too much.
[02:27] <bryceh> tis true, every comment there is a rant against something or other
[02:39] <nigelb> someone ranting about intel 8xx? I should join in
[02:54] <bjsnider> ranting about it isn't going to solve anything
[04:34] <RAOF> Who wants to sponsor an xserver upload!  Fun for one and all!
[04:36] <RAOF> Gah.  I don't think Intel are particularly culpable for i8xx.  Those cards are a decade old, don't work properly in Windows Vista (IIRC), etc.  We have *better* i8xx support than recent windows!
[04:37] <ajmitch_> RAOF: I'd be more impressied if you supported my old i740 card properly, with nice shiny 3d :)
[04:37] <RAOF> ajmitch_: We do!
[04:37] <ajmitch_> with some 3d support?
[04:37] <RAOF> It's just that your *hardware* doesn't support shiny 3D :P
[04:37] <ScottK> My 865 box is only less than 5 years old.
[04:37] <ajmitch_> RAOF: oh it supported some 3D, I think
[04:37] <ajmitch_> I just don't have a motherboard to put it in
[04:38] <RAOF> ajmitch_: Yeah, but you'd be better of with a software rasteriser in any modern system.
[04:38] <ajmitch_> undoubtably
[04:38] <ScottK> ajmitch_ should sponsor it since he needs a break from the last task I gave him.
[04:38] <RAOF> ScottK: Oh, I didn't know you could get 865 cards that recently.
[04:38] <ajmitch_> I look forward to the day when I can replace fglrx with a free driver & get the same features & performance
[04:39] <ScottK> RAOF: Actually I think it's a little over 5 years now that I think about it again.
[04:39] <RAOF> ajmitch_: That'll take a while, although Natty might get you the same features.
[04:39] <ScottK> IIRC it was early 2005.
[04:40] <RAOF> The 855 and 845 are older, though probably not by _that_ much.  I stand corrected.
[04:40] <ajmitch_> RAOF: it's a relatively modern ati chipset in the laptop, the other one has i915
[04:41] <RAOF> We'll almost certainly be switching to r300g for Natty, supporting all the GLL
[04:41] <ScottK> Win2K works with it very nicely.
[04:41] <ajmitch_> RAOF: which ati chips would that support?
[04:41] <RAOF> GLSL, GL 2.x, and suchlike fun.
[04:41] <ScottK> RAOF: How goes the Mesa FFe?  I didn't see much in the way of additional test results recently.
[04:41] <RAOF> r300-r500.  I think that's up to Radeon 2xxx.
[04:42] <ajmitch_> ah
[04:42]  * ajmitch_ has a mobility radeon hd 4650, I think that's r600?
[04:42] <ajmitch_> hard to keep track of them these days :)
[04:42] <RAOF> That's likely to be r700, I thinke.
[04:43] <ajmitch_> looks lik you're right
[04:44] <RAOF> I don't think anyone's waiting on me for more testing on the mesa FFe?  The next activity I expected was “go ahead”, followed by an upload.
[04:44] <ScottK> Oh.
[04:46] <RAOF> I was also expecting to have a 7.9 release branch open up upstream, but that hasn't happened yet.
[04:47] <ScottK> RAOF: You said "I'll test swrast on my nouveau system" in the bug, but didn't report results yet.
[04:47] <RAOF> Ah.
[04:47] <RAOF> Ok.
[04:49] <RAOF> Done.
[05:25]  * ScottK notes to RAOF that he's approved and goes to bed.
[05:41] <Sarvatt> oh sorry about that, I thought I replied on the FFe saying nouveau with and without swrast is what I've been testing mostly with no problems. my wife's been using it and she's good at complaining about broken things :)
[05:42] <Sarvatt> RAOF: release branch tomorrow morning PST
[05:43] <Sarvatt> idr said "I will do this on the morning (US pacific time) of 9/14", there's a release bug tracker at https://bugs.freedesktop.org/show_bug.cgi?id=30124
[05:43] <ubot4> Freedesktop bug 30124 in Mesa core "Mesa 7.9 release tracker" [Normal,New]
[05:45] <Sarvatt> only one relevant bug on there - https://bugs.freedesktop.org/show_bug.cgi?id=27831
[05:45] <ubot4> Freedesktop bug 27831 in Drivers/DRI/i965 "[regression] DynamicBranching3 does not render correctly" [Normal,Assigned]
[05:49] <Sarvatt> better off getting it in now and updating later though if there's a sponsor around, I can try to find one in the morning and/or pull in the release branch if not
[05:51] <RAOF> So, before I board this plane, the two sponsorship opportunities are: http://cooperteam.net/Packages/xorg-server_1.9.0-0ubuntu6.dsc & http://cooperteam.net/Packages/xserver-xorg-input-synaptics_1.2.2-2ubuntu4.dsc
[05:51] <Sarvatt> ohh, XDS already?
[05:51] <RAOF> Sarvatt: Would you like to shepherd the mesa upload now that the FFe has been granted?
[05:52] <RAOF> Yup.
[05:52] <RAOF> Australia is a long way from *everywhere*, so….
[13:51] <ScottK> Sarvatt: Do you have anything ready for upload for mesa?
[14:03] <Sarvatt> ScottK: just woke up, building it now because RAOF made some changelog changes vs the one I had prepared
[14:04] <Sarvatt> http://sarvatt.com/downloads/merges/mesa/
[14:09] <ScottK> Looking.
[14:09] <Sarvatt> have it building on that server atm and will put the build log in that directory when its done
[14:14] <ScottK> Sarvatt: Why are you renaming libegl1-mesa-drivers-x11 to libegl1-mesa-drivers?  That means it will have to go through binary New?
[14:15] <Sarvatt> let me find where RAOF did that for the rationale, I'm not sure exactly
[14:15] <ScottK> Also did anyone check if the dropped symbols are used by anything?
[14:21] <tball> Hi
[14:22] <tball> Anyone know if mesa 7.9 make it into the final version of maverick?
[14:22] <tball> makes*
[14:23] <Sarvatt> the only users of openvg and egl were experimental arm packages, the dropped symbols in libopenvg1 don't exist in the proprietary drivers for all of those arm platforms because they split it off into a separate libOpenVGU lib there
[14:23] <Sarvatt> i'm not sure if symbols were dropped in EGL since RAOF updated that, need to go over the history and look
[14:30] <Sarvatt> yes, all of the removed symbols were ones that should have been hidden in the first place, checked libgles1 libgles2 and libopenvg1that had changes. the EGL split was because they used to ship two different drivers for x11 or kms EGL backends but they are now all shipped as a single one
[14:31] <Sarvatt> http://git.debian.org/?p=pkg-xorg/lib/mesa.git;a=commit;h=598176dc22273ef4d3270580338d3eb414d2db27
[14:43] <Sarvatt> alf__: do you know anything about the rdepends on libegl1-mesa-drivers-x11 in linaro? afaik asac knows about the new mesa 7.9 packages, I'm not sure if RAOF discussed it with you guys?
[14:48] <alf__> Sarvatt: at the moment, we just really need libegl1-mesa and the swrast driver. We don't have a direct dependency to libegl1-mesa-drivers-x11.
[14:48] <Sarvatt> yeah thats what I thought but wasn't positive, thanks
[14:49] <Sarvatt> alf__: were you aware of the mesa 7.9 FFe? egl/gles/vg has changed quite a bit in it
[14:50] <alf__> Sarvatt: You mean the on the packaging guide or in general?
[14:50] <alf__> Sarvatt: s/guide/side/
[14:51] <Sarvatt> I was wondering if you guys had tested it at all and had any problems
[14:53] <ScottK> Sarvatt: The binary package renames isn't mentioned in debian/changelog (that I saw).  Also there is some redunancy between your entries and RAOF's that should be cleaned up.
[14:53] <ScottK> Sarvatt: I'm wondering if we really need to do the package rename or if than can wait until Natty.
[14:56] <alf__> Sarvatt: I haven't tested it yet, I don't think asac has tested it either
[14:56] <alf__> Sarvatt: I am not sure about asac, though
[14:57] <Sarvatt> the package rename looks necessary from what I can see, it only builds a single driver that has both the x11 and KMS backends built into it, not sure shipping that in libegl1-mesa-dri-x11 makes sense? we could stuff it in both but the x11 backend will be the default in both
[14:58] <ScottK> OK.  Please clarify in debian/changelog what's going on.
[14:58] <Sarvatt> ScottK: thanks, you're right that this changelog is silly, cleaning things up now
[14:59] <ScottK> Thanks.
[15:11] <Sarvatt> http://sarvatt.com/downloads/merges/mesa/ - anything missing from that changelog?
[15:14] <Sarvatt> RAOF did the egl change so I added it to his section
[15:17] <Sarvatt> went through the git history for debian/ and there isn't really anything else user visible that makes sense in the changelog except maybe mentioning the changes in libgl1-mesa-dri-experimental, but we dont really want people installing that package anyway because its unsupported :)
[15:19] <Sarvatt> ack, speaking of which, that needs to be in universe
[15:20] <Sarvatt> it's completely unsupported by upstream
[15:40] <Sarvatt> filed https://bugs.edge.launchpad.net/ubuntu/+source/mesa/+bug/638097 for the demotion request
[15:40] <ubot4> Launchpad bug 638097 in mesa (Ubuntu) "Universe binary demotion request for libgl1-mesa-dri-experimental (affects: 1) (heat: 8)" [Undecided,New]
[15:40]  * Sarvatt waits for bryceh's script to mark it incomplete because there's no lspci attached
[15:41] <jcristau> heh
[16:14] <ScottK> Sarvatt: Looks much better.  Thanks.
[17:19] <ScottK> Sarvatt and RAOF: Mesa uploaded.  Thank you for your contribution to Ubuntu.
[17:19] <Sarvatt> thank you so much for all of the help with it ScottK!
[17:19] <ScottK> Sarvatt: LP closing bugs in changelog is broken, so you'll still need to mark all those bugs fixed by hand.
[17:20]  * Sarvatt nods
[18:18] <Sarvatt> In conjunction with the release of the E620 (600 MHz. processing speed) / E640 (1.0 GHz.) / E660 (1.3 GHz.) / E680 (1.6 GHz.) devices and their enhanced temperature (-40° to +85° C) counterparts (E620T, E640T, E660T, E680T), Intel has also concurrently announced the release of a new embedded graphics driver called Intel® EMGD which stand for Intel® Embedded Media and Graphics Driver.
[18:18] <Sarvatt> woohoo? wonder if it supposed > xserver 1.6 now
[18:18] <Sarvatt> supports rather
[18:19] <Sarvatt> or psb in general for that matter
[18:20] <Sarvatt>  Intel® EMGD is NOT a follow-on/next generation driver to IEGD since both drivers support different chipsets
[18:20] <Sarvatt> oh that answers that
[18:41] <Sarvatt> time to close out all these mesa bugs
[18:53] <bryceh> ugh, another intel driver?  is it open or closed?
[18:54] <Sarvatt> closed!
[18:55] <bryceh> :-(
[19:02] <Sarvatt> The Intel® Embedded Media and Graphics Driver and Video BIOS support the following Linux operating systems and APIs:
[19:02] <Sarvatt> Fedora* 11 (Timesys kernel 2.6.29, X.server 1.6 DRI2)
[19:02] <Sarvatt> MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0)
[19:03] <Sarvatt> skipped lucid/squeeze xserver video abi completely, yay
[19:05] <Sarvatt> oh wait
[19:05] <Sarvatt> EMGD does work with PSB
[19:06] <Sarvatt> they just dropped all the other intel chipsets noone used IEGD for anyway
[19:06] <Sarvatt> Intel® EMGD 1.0 supports these Intel® Atom™ processor- based platforms:
[19:06] <Sarvatt> Intel® Tunnel Creek system-on-a-chip (SoC). Tunnel Creek integrates an Intel® Atom™ processor core + GPU + other i/o functions.
[19:06] <Sarvatt> Intel® Atom™ processor Z5xx series (with Intel® System Controller Hub US15W/US15WP/WPT Chipset)
[19:06] <Sarvatt> so lucid + xorg-edgers + EMGD will work on PSB
[19:56] <Sarvatt> nautilus sure picked a good time to go belly up - (nautilus:30209): Unique-DBus-WARNING **: Error while sending message: No such interface `org.gtk.UniqueApp' on object at path /Factory
[20:07] <seb128> Sarvatt, restart your session or nautilus
[20:07] <seb128> it's just that the running instance has issue with the installed one
[20:07] <seb128> it's a maverick to maverick issue
[20:07] <seb128> ie will not happen to users running lucid and upgrading
[20:44] <vish> Sarvatt:  seems the new mesa does the same for all ATI in Unity.. its a white screen for me as well :(
[20:46] <Sarvatt> what did you get before?
[20:46] <Sarvatt> also, :(
[20:48] <Sarvatt> multiple people said it was fixed for them during testing, what GPU are you on again?
[20:48] <vish> Sarvatt: well , earlier , it was unity doing a repeated reload , but with mesa 7.9 its just a constant white page
[20:49] <Sarvatt> it's certainly working fine now on r600+ when it wasn't before
[20:49] <vish> and mutter needs to be run with  VBLANK , else even mutter wont work..
[20:50] <vish> i mean CLUTTER_VBLANK=none
[20:50] <Sarvatt> CLUTTER_VBLANK=none?
[20:50] <vish> :)
[20:50] <Sarvatt> i need that on intel to use unity too :)
[20:51] <Sarvatt> (otherwise its a white screen)
[20:51] <Sarvatt> vish: did I ask you to try changing driconf options?
[20:51] <vish> on ATI?
[20:51] <Sarvatt> yeah
[20:52] <vish> havent tried it.. will try now..
[20:52] <Sarvatt> one sec, cant actually change the option i'm gonna ask via driconf
[20:52] <vish> yeah.! 
[20:52] <vish> you made me do this the last time too ;p
[20:52] <Sarvatt> oh, put something in ~/.drirc?
[20:53] <Sarvatt> http://pastebin.com/t8nND0bV
[20:53] <vish> no , i think i downloaded the driconf and tried some option you wanted me to change , but it turned out to be for intel..
[20:53] <Sarvatt> try that as ~/.drirc
[20:54] <Sarvatt> ohhh man that was a *long* time ago!
[20:54] <vish> :)
[20:54] <Sarvatt> surprised you remember that :)
[20:54] <Sarvatt> that was texture tiling when they turned it on by default on intel in mesa 7.7 I think
[20:56] <Sarvatt> anyway gotta put that in ~/.drirc manually because you cant edit the dri2 driver options in driconf, they are listed for the actual driver and vblank_mode doesn't do anything there
[20:57] <vish> ok.. in a few ,  making a new daily live...
[21:19] <vish>  http://pastebin.com/t8nND0bV
[21:28] <vish_> was mesa 7.9 released or is it still in sarvatt's ppa?
[21:32] <vish_> oh if its still building in other architectures it wont be available as an update?
[21:49] <vish_> Sarvatt: nope.. that .drirc dint help :(  mutter doesnt work..  but if i start mutter with $CLUTTER_VBLANK=none mutter --replace        mutter works
[21:50] <vish_> this is on an RV515 
[21:51] <Sarvatt> white screen with mutter too?
[21:51] <Sarvatt> anything in ~/.xsession-errors?
[21:52] <vish_> mutter is not white , its just a background with a few missing windows
[21:56] <vish_> Sarvatt: nope , nothing in .xsession-errors  after i launch mutter --replace
[21:57] <vish_> http://paste.ubuntu.com/493840/  after mutter --replace
[21:58] <vish_> http://paste.ubuntu.com/493839/  before
[22:05] <Sarvatt> darnit, vish_ do you have your bug # handy about this?
[22:05] <Sarvatt> <Sarvatt> darnit, vish_ do you have your bug # handy about this?
[22:07] <vish> Sarvatt: bug 616997 :)
[22:07] <ubot4> Launchpad bug 616997 in unity (Ubuntu) (and 3 other projects) "[RV515] Unity keeps reloading with a white background (affects: 7) (dups: 2) (heat: 155)" [Low,Triaged] https://launchpad.net/bugs/616997
[22:07] <vish> Sarvatt: btw, i logged in twice ;)
[22:07] <vish_> o/
[22:23] <Sarvatt> vish: so you still get this? (unity:9610): Clutk-WARNING **: [CheckGLError] GL_INVALID_VALUE error in File ./ctk-render-target.c at line: 286
[22:23] <Sarvatt> (unity:9610): Clutk-WARNING **: [CheckGLError] OpenGL Error 1281 in File ./ctk-render-target.c at line: 286 
[22:24] <vish> oh.. i need to log in again into unity and check! :D
[22:25] <Sarvatt> sorry :( I'm pretty sure you do, you said you did with the PPA one
[22:25] <vish> yeah , got it with the ppa too.. 
[22:26] <Sarvatt> MESA_EXTENSION_OVERRIDE=-GL_ARB_texture_non_power_of_two unity doesn't crash with that same error for me anymore on intel, weird
[22:26] <Sarvatt> its all grey though
[22:28] <Sarvatt> second try using MESA_EXTENSION_OVERRIDE=-GL_ARB_texture_non_power_of_two unity -p did it
[22:28] <vish_> :D
[22:29] <Sarvatt> are you using -p when you check it?
[22:30] <Sarvatt> just curious cus without -p its different
[22:31] <vish_> oh no.. for unity i just login into a unity session and its a white screen..
[22:31] <vish_> thso i havent tried with -p 
[22:32] <vish_> so*
[22:32] <Sarvatt> i really am clueless about all of this clutk stuff, but it seems like things should be checking for NPOT support before using it at least..
[22:34] <vish> the other reporter for the ATI HD also mentioned the same issue..
[22:34] <vish> white screen.
[22:36] <vish> bugs 599741
[22:36] <ubot4> Launchpad bug 599741 in unity (Ubuntu) (and 2 other projects) "Major rendering issues using ATI Mobility Radeon HD 3450 (affects: 8) (dups: 1) (heat: 50)" [Undecided,New] https://launchpad.net/bugs/599741
[22:37] <vish> the mesa task was closed due to new 7.9 upload but the reporter mentions same white screen..
[22:38] <Sarvatt> he isn't the original reporter
[22:38] <vish> oh! then maybe he is having my issue then :p
[22:38] <Sarvatt> he's got a hd3200, not positive but i think that has a r500 based 3d engine?
[22:40] <Sarvatt> nope looks like its really an r600+
[22:49] <Sarvatt> vish: you've really got me stumped here
[22:49] <vish> :s
[22:51] <vish> odd was that the .drirc dint work?  but had to use CLUTTER_BLANK while launching mutter..
[23:47] <Dink> Hello I just posted, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/638496 I am not sure if its X or kernel related.
[23:47] <ubot4> Launchpad bug 638496 in xserver-xorg-video-intel (Ubuntu) "[i945GME] invalid framebuffer id; AOD250 netbook (affects: 1) (heat: 6)" [Undecided,New]
[23:48] <Sarvatt> gnome-terminal is causing that?
[23:49] <Dink> That has been the only way for me to actually freeze everything
[23:50] <Dink> without things are slower and windows are locked, as in I can't click the other application.
[23:51] <Dink> sometimes works if I alt-tab to the other windows/apps when the window/app is locked.
[23:51] <Sarvatt> that error is pretty harmless and happens when someone shuts down or X restarts because of the plymouth junk, maybe X is actually crashing
[23:51] <Sarvatt> oh boy, our friend 101_copy-fb.patch again in x-x-v-intel?
[23:52] <Sarvatt> [116756.332] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e83bb]
[23:52] <Sarvatt> [116756.333] 1: /usr/bin/X (0x8048000+0x5da8d) [0x80a5a8d]
[23:52] <Sarvatt> [116756.333] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x12140c]
[23:52] <Sarvatt> [116756.333] 3: /usr/bin/X (FreeClientResources+0xed) [0x808f04d]
[23:52] <Sarvatt> [116756.333] 4: /usr/bin/X (FreeAllResources+0x60) [0x808f120]
[23:52] <Sarvatt> [116756.333] 5: /usr/bin/X (0x8048000+0x1a5e6) [0x80625e6]
[23:52] <Sarvatt> [116756.333] 6: /lib/libc.so.6 (__libc_start_main+0xe7) [0x93cce7]
[23:52] <Sarvatt> [116756.333] 7: /usr/bin/X (0x8048000+0x1a191) [0x8062191]
[23:52] <Sarvatt> [116756.334] Segmentation fault at address 0x4
[23:52] <Dink> so I guess that is when I do the kill -hup mutter it creates that message
[23:53] <Sarvatt> yeah and that backtrace is from the copy-fb patch, probably not related to the actual problem either
[23:54] <Dink> hmm so what can I run when it freezes to grab logs etc ?
[23:54] <Dink> I am sure I can reproduce it.. the windows are "locking" now
[23:55] <Dink> I will have to do it in vt1 since my screen completely locks up
[23:56] <Dink> I think it started happening during the beta updates phase
[23:56] <Dink> or maybe right after that
[23:58] <Sarvatt> Dink: does it only happen with compiz enabled?
[23:59] <Dink> umm not sure how to enable/disable that.. running this on a netbook right now
[23:59] <Sarvatt> system - preferences - appearance - desktop effects, set to none to disable