[00:09] <bryceh> bjsnider, why is there doubt?
[00:09] <bjsnider> it's been a few days. i think he missed it. i certainly did
[00:09] <bjsnider> they released it very quietly
[00:09] <bjsnider> but it fixes a bug that is very relevant to maverick
[00:10] <bryceh> I'd guess it's just a matter of release stuff taking priority for his time
[00:11] <bryceh> bjsnider, if you're interested in helping move things forward, you could volunteer to help get it packaged up and tested
[00:11] <bjsnider> just give me the upload rights and i'll put it in there myself
[00:12] <bryceh> lemme check if I'm an admin...
[00:12] <bryceh> nope
[00:13] <bryceh> but, just click the button to join this team, and sarvatt or tormod will hook you up:  https://edge.launchpad.net/~xorg-edgers/
[00:13] <bryceh> bjsnider, thanks ahead of time
[00:13] <bjsnider> done
[00:16] <Sarvatt> x-updates is ubuntu-x-swat
[00:16] <Sarvatt> didn't know they released a driver
[00:16] <bjsnider> they released it middle of last week
[00:16] <bjsnider> i completely missed it. phoronix didn't have it
[00:17] <bjsnider> http://www.nvnews.net/vbulletin/showthread.php?t=155137
[00:17] <bjsnider> ftp://download.nvidia.com/XFree86/nvidia-settings/nvidia-settings-260.19.06.tar.bz2
[00:17] <Sarvatt> i'm not an admin of ubuntu-x-swat to accept ya :D
[00:18] <bjsnider> ok but can you get it in there?
[00:18] <bjsnider> this bug is highly annoying
[00:18] <bryceh> oh x-updates, for some reason I read that as xorg-edgers
[00:19] <bryceh> bjsnider, sorry, click to join https://edge.launchpad.net/~ubuntu-x-swat
[00:20] <bryceh> bjsnider, actually I can add you directly
[00:33] <Sarvatt> its uploading now
[00:37] <bjsnider> coolio
[00:42] <Sarvatt> could ya get nvidia-settings? or i'll get it tomorrow, house is about to start :)
[00:55] <bjsnider> yeah i'll do it
[00:56] <bjsnider> Sarvatt, are there any differences between the maverick and lucid nvidia-settings build scripts?
[00:56] <Sarvatt> nope
[00:57] <bjsnider> that makes it easy
[01:48] <ScottK> RAOF or Sarvatt: Are you planning on doing the mesa revert after RC?
=== JanC_ is now known as JanC
[09:25] <popey> Is someone able to tell what part of the xorg-edgers intel driver fixes bug 619663 ? at the moment the intel driver is broken for dual screen side-by-side on 10.10. 
[09:25] <ubot4> Launchpad bug 619663 in xserver-xorg-video-intel (Ubuntu) "[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor (affects: 5) (dups: 1) (heat: 28)" [Undecided,Confirmed] https://launchpad.net/bugs/619663
[09:25] <popey> and thus if it's possible to get that patch into 10.10
=== bigjools is now known as bigjools-afk
[13:45] <bjsnider> mvo, the latest build of xserver-xorg-dev in maverick does not contain the important file /usr/share/xserver-xorg/serverminver
[13:45] <jcristau> what still uses that?
[13:45] <bjsnider> nvidia-current
[13:45] <jcristau> boo.
[13:46] <bjsnider> probably the other proprietary drivers also
[13:47] <tseliot> bjsnider: no, it doesn't
[13:48] <tseliot> nvidia-current doesn't use that any more
[13:49] <bjsnider> oh, because i was just looking at the rules file and it does here. have you got newer build scripts?
[13:52] <bjsnider> ah yes i see
[13:52] <tseliot> bjsnider: the one in maverick doesn't use it
[13:54] <bjsnider> tseliot, what do you think about getting rid of the nvidia-current-dev package now that there are no more headers to install? the only file left in that package is libXvMCNVIDIA.a
=== bigjools-afk is now known as bigjools
[13:55] <tseliot> bjsnider: that's not a change that I will make in Maverick. In Natty we'll have separate packages and hopefully nvidia-current-dev can either be dropped or become an empty package that depends on opencl, etc.
[13:57] <bjsnider> that would be a good idea
[13:58] <mvo> bjsnider: thanks, I just touched the package to fix some upgrade issues, I don't know that much about the internals myself (but it looks you found the right people already :)
[15:13] <Sarvatt> mvo: would you be willing to sponsor a new compiz upload? we've got a problem where I added the sandybridge bridge devices to the previous upload and it's preventing machines not using the intel GPU from using compiz too. darn preproduction machines with no info on them outside of the source :( https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/644372
[15:13] <ubot4> Launchpad bug 644372 in compiz (Ubuntu) "Compiz Sandybridge blacklisting preventing discreet GPU machines from using it (affects: 1) (heat: 6)" [Undecided,In progress]
[15:14] <mvo> Sarvatt: sure, I can sponsor one, let me look
[15:17] <Sarvatt> mvo: thanks a ton for taking a look at it! I have verified it doesn't regress any of my sandybridge machines with 0100 bridge 0102 GPU pci ids, the id's were obtained from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=53767cc0d0a58d36cd445da3a31c65b349eebbba
[15:23]  * ScottK mumbles to Sarvatt about mesa uploads too.
[15:24] <Sarvatt> ScottK: want me to prepare a mesa with the revert? I thought RAOF had it under control but haven't spoken to him in a while, we keep duplicating work on mesa and screwing each other up in git
[15:25] <ScottK> Sarvatt: I'm not qualified to say for sure, but I'd think it's better in now than after RC.
[15:25] <mvo> Sarvatt: thanks, what about 0x126? it seems to got removed from the intel_driver.h but its still in the blacklist. is that pre-production or something?
[15:26] <mvo> Sarvatt: just curious, it seems to be a graphics controller, so not really relevant for the bug in question
[15:26] <Sarvatt> mvo: 0126 is a valid device, its just not lined up so looks like its gone on first glance, they had that added previously
[15:26] <Sarvatt> +#define PCI_CHIP_SANDYBRIDGE_M_GT2_PLUS	0x0126
[15:26] <mvo> aha, ok
[15:27] <mvo> sorry, see it now as well (what a little indent can do ;)
[15:27] <Sarvatt> yeah when you said that I didn't see it either at first :D
[15:28] <mvo> Sarvatt: thanks, diff looks fine, commited to bzr and uploaded
[15:29] <Sarvatt> thanks mvo!
[15:30] <bjsnider> Sarvatt, the nvidia-current build for mav failed last night because of the serverminver thing. that's going to be another difference between the lucid and mav build scripts, but i think it's ok to use that aspect of the mav scripts on lucid
[15:30] <Sarvatt> bjsnider: yeah I tried to upload the fix when I woke up but you already got it :)
[15:30] <Sarvatt> was my silly mistake forgetting to fix it, was rushing to upload it before house started :)
[15:30] <bjsnider> it looks like it's going to take several days to finish building at this rate
[15:31] <mvo> yw Sarvatt
[15:32] <Sarvatt> mesa is so bad off on sandybridge :(
[15:33] <Sarvatt> bjsnider: btw what did you change? here's the full list of changes needed - http://sarvatt.com/downloads/nvidia-maverick.patch
[15:35] <bjsnider> i matched the rues file with the upstream version
[15:36] <bjsnider> yep, it matches that patch
[15:36] <bjsnider> i did it the old fashioned copy and paste way
[15:37] <bjsnider> but i think those changes would work on lucid because the file being tested exists
[15:37] <Sarvatt> normally I just start with the maverick and apply http://sarvatt.com/downloads/patches/nvidia-graphics-drivers-lucid-backport.patch but I was a bonehead last night :)
[15:37] <Sarvatt> and reused the previous lucid packaging
[15:38] <Sarvatt> hmm
[15:38] <Sarvatt> mesa (7.9~git20100909-0ubuntu3) maverick; urgency=low
[15:38] <Sarvatt>   * Drop the changes from previous upload.  The Unity white screen problem
[15:38] <Sarvatt>     is clutter bug #632352, fixed in clutter-1.0 1.2.12-0ubuntu12.
[15:38] <Sarvatt>  -- Christopher James Halse Rogers <raof@ubuntu.com>  Thu, 16 Sep 2010 16:04:28 +0200
[15:38] <ubot4> Launchpad bug 632352 in clutter-1.0 (Ubuntu) "Clutter fails to update with Mesa 7.9 (affects: 1) (heat: 8)" [Critical,Fix released] https://launchpad.net/bugs/632352
[15:39] <Sarvatt> ScottK: yeah looks like RAOF already packaged and test built everything but hasn't gotten them sponsored yet - http://cooperteam.net/Packages/
[15:39] <ScottK> What are the odds of him appearing and saying "Yes, I want that in for the RC"?
[15:43] <Sarvatt> pretty much 100% he'll say that around 7PM EST when he wakes up, he should be back from the conference now :)
[15:50] <ScottK> It'll be too late by then.
[15:50] <ScottK> I'll take it.
[16:06] <ScottK> Sarvatt and RAOF: Mesa uploaded.  I guess I get to do the odd numbered ones.
[16:07] <Sarvatt> hah! thanks ScottK, sorry we dropped the ball on that one, it should have gone in a week ago
[20:40] <Sarvatt> fun, another cyclic dependency added to mesa besides X, wine-dev for the d3d1x state tracker now :)
[20:44] <bjsnider> to install that state tracker, you need wine-dev?
[20:44] <bjsnider> is that because they built it with wine's directx code?
[22:41] <patrickdickey> Hello there.  I'm curious about whether my ATI Graphics Card is supported under the fglrx package. It's an ATI Radeon Express 200M (RC410).
[22:42] <patrickdickey> Here's the exact description from lspci -v "GA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]"
[22:45] <bryceh> patrickdickey, no ATI dropped support for your hw from fglrx
[22:45] <bryceh> patrickdickey, uninstall fglrx and use -ati instead, it should work fine
[22:45] <patrickdickey> I don't think I have fgrlx installed.  I've got the default drivers that come with xorg (Kubuntu 10.04).
[22:46] <patrickdickey> xserver-xorg-video-ati <- This is the driver I should use?
[22:53] <patrickdickey> Thanks. I'm going to try that one out. Hopefully everything works out.  Have a great day:)
[23:05] <JanC> "try that one out" ?