[02:24] <Sarvatt> hmm think i stripped too much out of the livecd that time, kept crashing back to gdm login :P got the iso down to 446MB ripping out printing/scanning stuff though
[07:16] <wesmo> hi all
[07:19] <wesmo> When trying to build the latest drm-modules source from https://launchpad.net/~xorg-edgers/+archive/ppa with "sudo module-assistant auto-install drm-modules"; the build fails
[07:21] <wesmo> the buildlog from /var/cache/modass/drm-modules-source.. is http://pastebin.com/m70a9e8bb
[07:22] <wesmo> any idea whats wrong?
[08:00] <crevette> heya
[08:03] <crevette> when I used KMS this week-end with intel, I had the screen that became black during the boot process and I ws not able to see anything else. I am using plain karmic. What information would you need? (I don't have my laptop here) 
[08:58] <jcristau> crevette: kernel log for a start
[09:30] <crevette> jcristau, okay
[09:30] <crevette> I'll try to test KMS in the coming days to see if it happens again
[09:31] <jcristau> this is using a stock kernel, not a self-compiled one, right?
[09:31] <crevette> yep, all stock
[09:31] <crevette> on https://wiki.ubuntu.com/X/KernelModeSetting you can look for bmillemathias
[09:31] <jcristau> so it could be misdetecting the connected outputs. and then turning off the lvds.
[09:32] <crevette> when I trying to switch vt, I was alble to seem some text on the vt5 IIRC
[10:13] <seb128> on what package do you suggest opening a bug about xorg crashing on jaunty intel when playing some videos?
[10:13] <seb128> the server or the intel driver rather?
[10:14] <tjaalton> intel I think. although there probably are dupes in the 300 open bugs ;)
[10:50] <Ng> the uds spec for karmic xorg plans gives the impression that apart from xserver 1.7, the merges are generally done at this point :o
[10:50] <Ng> assuming I'm reading that right, that rocks :)
[12:08] <tjaalton> Ng: we still need a newer mesa, and the nouveau version is obsolete
[12:08] <Ng> it all seems to be in pretty good shape to me :)
[12:09] <tjaalton> I'll try to remember that in late September ;)
[12:10] <jcristau> you're planning on mesa 7.6-ish?
[12:10] <tjaalton> something like that
[12:11] <tjaalton> I'd really like to see r6/7xx support in the dri driver, but it's the holiday season soon etc..
[12:12] <tjaalton> unless it's going to be released as a bug-free driver :)
[12:13] <Ng> tjaalton: when I start screaming at the last minute because of bugs? ;)
[12:14] <tjaalton> Ng: gotcha :)
[12:15] <Ng> hehe
[12:15] <Ng> I'm running the dev version *way* earlier than usual, so hopefully I'll spot anything sooner :)
[12:15] <Ng> I normally wait until a month before beta
[12:16] <jcristau> tjaalton: ah yeah good point.  hopefully r6/7xx will be usable by then.
[12:16] <jcristau> if it's not, then it'll be usable by squeeze ;)
[13:41] <tjaalton> jcristau: that's just my hopeful thinkin, fingers crossed
[13:41] <tjaalton> +g
[17:02] <XCP2> hi. there's a bug in xorg in the newer versions of ubuntu that has not been fixed. however, there is a PPA on launchpad that apparently fixes the problem (not in clean way, but it's okay for me). Now my question: if I apply this PPA patch and some time later there is an official ubuntu patch for this problem, or any other update to xorg, will and can this newer update still be applied, although I manually changed my xorg some time before?
[17:02] <jcristau> i guess it depends on the version number in the ppa
[17:03] <XCP2> jcristau: here's the link. (how would I find out the version number from it?) https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill ... it fixes a problem in xorg, which causes xorg to use up 6GB+ memory after a while and take it 3-4 seconds to maximize a single window, each time leaking memory.. 
[17:04] <XCP2> this bug has actually haunted me and other users for 2 months now, and I finally found this unofficial patch (because the official developers seem to see no reason to fix it)
[17:04] <jcristau> the description on that ppa doesn't sound like it has anything to do with a memory leak
[17:04] <XCP2> jcristau: yes, this is misleading, I know. it actually reverts a patch that causes this memory leak.
[17:05] <XCP2> jcristau: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/351186?comments=all
[17:05] <jcristau> no it doesn't.
[17:05] <XCP2> jcristau: according to the patch author, it does
[17:06] <jcristau> *shrug*
[17:06] <jcristau> anyway yeah, if there's an update in jaunty proper, it will take precedence over this package
[17:07] <XCP2> so the answer to my original question is 'yes'? I can install this PPA and still have my xorg be properly updated later by ubuntu?
[17:08] <jcristau> yes
[17:08] <XCP2> thank you, jcristau. :)
[17:09] <XCP2> I don't want to be importunately or something, but this bug is known for over 2 months now, it has 3 duplicates, and as you can see a lot of affected users. it really is a very annoying bug which seriously hinders usage of a system. how come this still isn't fixed? I cannot see any information on why it is taking so long.
[17:10] <Sarvatt> because there are even more people broken and just as annoying by disabling it most likely :) (aka all kubuntu users)
[17:10] <Sarvatt> just as annoyed*
[17:11] <XCP2> Sarvatt: please say again? what do you mean? 
[17:11] <Sarvatt> http://bugs.kde.org/show_bug.cgi?id=170462
[17:12] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/310228
[17:12] <XCP2> oh, I get what you mean... but then again, you can have the patch to the KDE problem AND patch the patch :) it's not like the only solution is to revert the patch.
[17:14] <jcristau> it's the one that's available today
[17:14] <jcristau> and since this isn't a high priority thing..
[17:15] <XCP2> jcristau: no offense, but if you had this problem yourself, you would certainly think otherwise. it is very annoying, my system crashes every so often because xorg becomes a memory hog, and whenever I maximize windows I have to wait for 3-4 seconds. I'd rather have video garbage than this.
[17:18] <jcristau> XCP2: the no-backfill patch doesn't change memory usage.
[17:23] <XCP2> jcristau: have you test it yourself? do you have an ATI card?
[17:23] <jcristau> no, and no
[17:24] <XCP2> then how do you know? :)
[17:24] <jcristau> because i've seen the patch?
[17:25] <XCP2> jcristau: maybe the change in memory usage & behavior is just a side effect, not visible in the code. 
[17:26] <XCP2> but, that's just a guess.
[17:27] <XCP2> jcristau: from what I understand, the backfill patch itself leaks memory and therefore applying the no-blackfill patch reverts that behavior.
[17:28] <jcristau> sounds like a driver bug to me...
[17:28] <XCP2> maybe, but I used the same official ATI driver on 8.04 & 9.04... on 8.04 it does not happen, on 9.04 it leaks.
[17:28] <XCP2> still, can be a driver issue, but I think it's rather unlikely.
[17:43] <lesshaste> any cuda users here?
[19:21] <jbarnes_PDX> bryce or apw: who should I harass about bluetooth stuff?
[19:26] <superm1> jbarnes_PDX, what about bluetooth stuff?
[19:27] <superm1> i happen to touch it a lot, but i dont pretend to know everything about it :)
[19:34] <jbarnes_PDX> superm1: oh cool
[19:34] <jbarnes_PDX> with karmic bluetooth bits (gnome-bluetooth & pulse stuff)
[19:34] <jbarnes_PDX> a2dp *almost* works automatically
[19:35] <superm1> jbarnes_PDX, that's great to hear!
[19:36] <superm1> what's the "almost" tho ;)
[19:36] <jbarnes_PDX> well sometimes it doesn't pair
[19:36] <jbarnes_PDX> and it also doesn't work with skype (with karmic bits skype no longer lists "pulse" as an option)
[19:37] <superm1> isn't default equivalent to pulse though?
[19:37] <jbarnes_PDX> also with the pulse dev chooser I'd expect my headset to show up as a new sink
[19:37] <jbarnes_PDX> probably should be, but doesn't work
[19:37] <jbarnes_PDX> and finally, when switching profiles, between a2dp and headset, I need to unpair and pair again, which seems wrong
[19:38] <jbarnes_PDX> it's cool to be able to listen to music, but I'd like for everything to "just work"
[19:38] <superm1> yeah i agree, yeah that does seem wrong
[19:38] <jbarnes_PDX> ideally, I turn on my headset and a dialog pops up "wanna use this?  as a headset or stereo headphones?"
[19:39] <jbarnes_PDX> and takes care of the rest (making it default in pulse, moving my streams over, etc)
[19:39] <jbarnes_PDX> I guess I'll chat with marcel about which bits I ought to use, then file bugs in launchpad
[19:40] <superm1> unfortunately marcel doesn't use an upstream tracker at all
[19:41] <superm1> he browses launchpad every so often, but doesn't commit to fixing bugs
[19:41] <jbarnes_PDX> right
[19:41] <jbarnes_PDX> brb
[19:41] <superm1> how do you switch profiles on your headset? is it a little switch?
[19:48] <jbarnes_PDX> superm1: no, pulse lets me choose
[19:49] <jbarnes_PDX> superm1: but my headset doesn't need to repair afaik
[19:49] <jbarnes_PDX> my phone can switch profiles pretty easily at least... it doesn't take long
[19:50] <superm1> ah that's surprising. i didn't realize that the pulse plugin was that feature filled
[19:51] <crevette> superm1: latest pulseaudio make audio over bluetooth quite easy
[19:51] <crevette> :)
[19:52] <superm1> oh hai crevette
[19:52] <crevette> hey hey superm1
[19:52] <superm1> do you follow linux-bluetooth@vger?
[19:52] <crevette> ubuntu-x became the lair for bluetooth discussion ?
[19:52] <jbarnes_PDX> crevette: yeah it's really close to being nice
[19:52] <superm1> haha
[19:52] <jbarnes_PDX> crevette: heh
[19:52] <crevette> superm1: unfortunately I lack time to
[19:52] <jbarnes_PDX> probably #ubuntu-desktop would be better?
[19:52] <crevette> :)
[19:53] <superm1> crevette, okay well i was gonna let you know, i talked to petr @ redhat, and that ondemand stuff is going upstream
[19:53] <superm1> so lets wait in ubuntu until it's ready upstream
[19:53] <crevette> superm1: ah I see you asked that on the IRC chan few days ago
[19:53] <crevette> ah wonderful
[19:53] <superm1> i did?  I spoke to him over email i thought..
[19:54] <crevette> I've opened a but in debian because I was thinking to merge our delta with debian package
[19:54] <crevette> superm1:you did :)
[19:54] <superm1> actually i think we can sync to debian
[19:54] <superm1> i reviewed the delta yesterday, and it looks like everything we have is useless right now delta wise
[19:54] <crevette> superm1: there is no change to keep on ubuntu side?
[19:54] <superm1> i just want to test their hid2hci changes
[19:55] <superm1> hid2hci is where i invested my blood in bluez, so if we sync and that breaks, i think i'll cry
[19:55] <crevette> my knowledge in blueooth is quite ... low, so as does it does, switching hid devices to another mode?
[19:56] <crevette> s/so as does it does/so what does it does.
[19:56] <jbarnes_PDX> I'm not sure
[19:56] <superm1> some bluetooth devices support a mode that doesn't expose a BT radio, but instead lets a pre-paired keyboard and mouse work 
[19:56] <jbarnes_PDX> I don't know if it has to renegotiate the link or just tell the dev to switch profiles
[19:56] <superm1> all "newish" dell devices start up in this mode. i wrote some patches to hid2hci to get them back
[19:57] <jbarnes_PDX> oh hid devices
[19:57] <superm1> how its done for different BT chips is proprietary on a vendor by vendor basis
[19:58] <superm1> generally if you are using a hid device in hid mode and then want to use the hid device in hci mode too, you will have to renegotiate the link
[20:01] <bryce> jbarnes, heya
[20:01] <jbarnes_PDX> bryce: howdy
[20:02] <bryce> btw, I sent a couple bugs upstream yesterday, but interestingly I found that pretty much all the UXA, KMS, 2.6.30, 2.6.99* bugs in our tracker seem to already be upstream near as I can tell
[20:02] <bryce> so... that's good news... sounds like most everything that's worth caring about at the moment is upstreamed
[20:02] <jbarnes_PDX> yeah that's great
[20:02] <bryce> however I still need to do my script thingee to ask everyone to re-test.  gonna work on that today
[20:03] <jbarnes_PDX> bryce: has a kernel landed in xorg edgers yet?
[20:04] <bryce> we've got a few kernels bouncing around in ppas, but not in xorg-edgers so far
[20:04] <bryce> apw has been working on one with nouveau and ati bits merged in
[20:04] <bryce> jbarnes, is there a particular kernel you think we should pull into xorg-edgers?
[20:04] <jbarnes_PDX> cool
[20:04] <Sarvatt> kernel for what?
[20:04] <bryce> heya Sarvatt
[20:04] <jbarnes_PDX> bryce: I was hoping for something with drm-intel-next merged into it
[20:04] <Sarvatt> heyo!
[20:05] <bryce> ahh
[20:05] <bryce> I'll try to remember to ask apw if he'd be able to produce one next time I see him
[20:06] <lesshaste> anyone here got cuda to work?
[20:06] <bryce> lesshaste: nope
[20:06]  * apw is just off, if you email me a reminder i'll have a peek tomorrow.  it may be hard to give you just one kernel for all of those on an on going basis if they collide, but i can try it out
[20:06] <apw> bryce, ^^
[20:07] <bryce> apw: cool, will send an email later today
[20:07] <lesshaste> bryce, :( did you try?
[20:07] <Sarvatt> drm-intel-next drm-radeon-merge and newttm for nouveau dont all merge right now :(
[20:08] <apw> cirtianly i had to work hard to get the latter two to merge last time
[20:08] <apw> those gem guys need to get their heads together!
[20:08] <bryce> lesshaste: no, I'm pretty sure no one on this channel has experimented with it, so this may not be the optimal place for discussion on it
[20:08] <lesshaste> bryce, ah
[20:08] <lesshaste> bryce, it's very hard to find anyone who has got it working to be honest
[20:08] <lesshaste> as in so far I have found exactly no one
[20:09] <bryce> lesshaste: maybe you'll become the definitive source if you write a good blog post on it ;-)
[20:09] <lesshaste> everything could be solved if there was a package for cuda in a repository
[20:09] <lesshaste> but I can't find one
[20:09] <lesshaste> bryce, :)
[20:09] <Sarvatt> i saw a PPA for cuda a few months ago
[20:09] <lesshaste> Sarvatt, ooh!!
[20:10] <lesshaste> I searched for the word cuda but didn't see it
[20:10] <lesshaste> any idea how to find this?
[20:10] <crevette> superm1: do you want to package 4.41? or do you prefer me to do it?
[20:10] <superm1> crevette, after i check debian's package w/ hid2hci on karmic, i think we can just ask debian to do it
[20:10] <superm1> and sync from them instead
[20:11] <superm1> did you see anything in the delta from debian that we needed to keep?
[20:11] <crevette> superm1: when you say "ask debian to do it" you mean slap filippo until he did it?
[20:11] <crevette> :)
[20:11] <superm1> exactly
[20:14] <crevette> let ask to sync on it once debian has it
[20:15] <lesshaste> Sarvatt, any ideas? I only see things like https://bugs.launchpad.net/ubuntu/+bug/203503
[20:15] <Sarvatt> lesshaste: http://forums.nvidia.com/index.php?showtopic=93535 ?
[20:16] <lesshaste> Sarvatt, thanks.. that's the painful route I have been trying
[20:16] <lesshaste> you just feel envyng should do this for you
[20:21] <lesshaste> hmm.. maybe it does secretly
[20:21] <lesshaste> will check tomorrow
[20:22] <bryce> Sarvatt: have you had a chance to test the kernel at https://edge.launchpad.net/~apw/+archive/daily ?
[20:22] <Sarvatt> are you just trying to run cuda apps? because the cuda libs should be installed by the driver, the guide is just for installing the SDK to develop against..
[20:23] <bryce> I'm thinking of pulling it into xorg-edgers.  I've tested it on several different video cards, and think it could be useful for further KMS work in X.org, but what do you think?
[20:25] <Sarvatt> i dont think its really compatable with putting in edgers right now because it has radeon KMS enabled by default and the drm/ddx parts arent compatable with the packages on there
[20:26] <bryce> ok
[20:27] <Sarvatt> i guess we could start shipping libdrm-radeon1 in libdrm though.. but the ati ddx is kind of a regression from master for non KMS stuff, i'm not sure if it'd require us to start merging radeon-rewrite with master on mesa on top of that too
[20:29] <Sarvatt> really though, not much point IMO because the KMS stuff has already been presented for proposal in 2.6.31 a few hours ago, hope they clean up the libdrm stuff soon
[20:29] <lesshaste> bryce, I see you are involved in envyng?
[20:29] <lesshaste> bryce, where is the #envy channel?
[20:30] <lesshaste> unless there is another bryce :)
[20:30] <lesshaste> tseliot, hi
[20:31] <tseliot> lesshaste: hi
[20:31] <lesshaste> tseliot, I wanted to ask an envyng question.. if you don't mind
[20:31] <tseliot> lesshaste: shoot
[20:32] <lesshaste> I am trying to get cuda to work and have been struggling all day
[20:32] <lesshaste> envyng installs 173.x I think  hardy
[20:32] <lesshaste> which doesn't seem compatible with the cuda sdk you can download from nvidia
[20:32] <lesshaste> but I may have this messed up
[20:32] <lesshaste> do you think that it's possible to get cuda working with the version of the nvidia driver envyng gives you?
[20:33] <Sarvatt> yeah thats not compatable, they didnt make the drivers cuda compatable until the 180's
[20:33] <lesshaste> but envyng does give you a cuda library file
[20:33] <lesshaste> so I am confused
[20:34] <tseliot> lesshaste: cuda in 173?
[20:34] <lesshaste> I went in so many circles today I may have this wrong
[20:34] <lesshaste> tseliot, so let's scrap my ignorance just ask the key question
[20:34] <lesshaste> could you please make an envyng version that also installs cuda :)
[20:34] <lesshaste> as it is killing me
[20:34] <lesshaste> I installed the later nvidia driver
[20:34] <lesshaste> but I really can't get cuda to work
[20:35] <Sarvatt> ahh sorry, i thought it was 180's only for some reason, maybe that was the case on windows or something because thats the only place i've messed with the cuda sdk
[20:36] <lesshaste> I see http://albertomilone.com/wordpress/?p=148 .. which seems to say to me that envy does provide cuda now
[20:36] <lesshaste> I am so confused :)
[20:37] <tseliot> lesshaste: the packages provide cuda. Maybe install the -dev package of the nvidia driver (the -envy flavour)?
[20:38] <bryce> heya tseliot
[20:38] <lesshaste> tseliot, ok so once I have installed should I be able to compile the cuda SDK?
[20:38] <lesshaste> tseliot, because I feel it failed today
[20:38] <tseliot> hi bryce
[20:39] <lesshaste> or can envy get  a version of the SDK that works too?
[20:39] <tseliot> lesshaste: I guess so. Make sure you uninstall the driver that you installed from the nvidia installer first or you'll end up with a mess
[20:39] <tseliot> lesshaste: Envy doesn't get the SDK
[20:40] <lesshaste> tseliot, ok.. what's the best way to uninstall the driver from nvidia?
[20:41] <lesshaste> ah.. maybe nvidia-installer --uninstall
[20:41] <tseliot> lesshaste: have a look at point B of the FAQ: http://albertomilone.com/envyngfaq.html#B
[20:42] <lesshaste> tseliot, thanks.. I don't have the computer here now but will try it all tomorrow.. especially compiling the sdk
[20:42] <lesshaste> tseliot, will you be about at all tomorrow?
[20:42] <lesshaste> so I can thank you :)
[20:43] <lesshaste> also, perhaps some words about cuda could be added to the FAQ?
[20:43] <lesshaste> for dumb people like me
[20:43] <tseliot> lesshaste: yes, even though it's 21:43 here now and I don't work at this time. But my computer is always on ;)
[20:43] <lesshaste> tseliot, mine too :)
[20:43] <lesshaste> it's 20:43 here
[20:44] <lesshaste> tseliot, the point is that the web is full of detailed instructions for how to get cuda to work in ubuntu and..
[20:44] <lesshaste> a) they don't work
[20:44] <lesshaste> and b) they don't mention envyng 
[20:44] <tseliot> lesshaste: I don't use it, therefore I wouldn't be comfortable with writing instructions for the things that I've never tried
[20:45] <tseliot> I made sure that the libcuda.so, etc. were provided by the packages
[20:45] <lesshaste> tseliot, ah ok.. I'll let you know what happens when I try it in that case
[20:45] <lesshaste> if you are interested
[20:45] <tseliot> ok
[20:52] <lesshaste> tseliot, oh yes.. is there really a #envy channel somewhere?
[20:54] <Sarvatt> http://lkml.org/lkml/2009/6/10/294
[20:54] <tseliot> lesshaste: no, I don't think there is one. I don't even have the time to maintain envy anymore
[20:56] <lesshaste> tseliot, ah ok.. there is an irc log https://wiki.ubuntu.com/EnvyNG
[20:56] <lesshaste> it must be faked :)
[20:56] <Sarvatt> why dont you just use the binary drivers from nvidia lesshaste? only issue with those is having to reinstall them every kernel upgrade, but how often do you get kernel upgrades still on hardy?
[20:56] <lesshaste> Sarvatt, well.. let me tell you :)
[20:57] <lesshaste> Sarvatt, I did exactly that and installed 185.18.08
[20:57] <lesshaste> I think compiled the SDK as per instructions
[20:57] <lesshaste> and when I run any cuda sample I get
[20:57] <Sarvatt> those had a library problem screwing up some mesa things that got fixed in .14 i think
[20:57] <lesshaste> cutilCheckMsg() CUTIL CUDA error: cudaMalloc failed in file
, line 49 : initialization error.
[20:57] <lesshaste> or equivalent
[20:58] <tseliot> lesshaste: what card are you using?
[20:58] <lesshaste> Sarvatt, http://www.nvidia.com/object/cuda_get.html offers only 185.18.08 as the latest version
[20:58] <lesshaste> tseliot, geforce 6200
[20:59] <Sarvatt> .....
[20:59] <Sarvatt> you know those dont  support cuda right
[20:59] <lesshaste> err..
[20:59] <Sarvatt> 8xxx and up..
[20:59] <lesshaste> no!!
[20:59] <lesshaste> I had no idea
[21:00] <lesshaste> I feel quite depressed now 
[21:00] <tseliot> Sarvatt: are you sure? He's talking about CUDA not VDPAU
[21:00] <Sarvatt> yeah positive, even the site he linked shows it requiring 8xxx and up
[21:00] <Sarvatt> http://www.nvidia.com/object/cuda_learn_products.html
[21:01] <tseliot> aah, you need the latest driver to use the latest version of CUDA
[21:01] <Sarvatt> http://en.wikipedia.org/wiki/CUDA
[21:02] <Sarvatt> The latest drivers all contain the necessary CUDA components. CUDA works with all NVIDIA GPUs from the G8X series onwards, including GeForce, Quadro and the Tesla line.
[21:02] <lesshaste> well.. what an idiot!!
[21:03] <tseliot> you're right. I thought it was just VDPAU that required newer cards
[21:03] <tseliot> problem solved then ;)
[21:03] <tseliot> well, kind of
[21:03]  * tseliot > away
[21:04] <lesshaste> sorry everyone for that
[21:04] <lesshaste> I wasted quite a lot of time :)
[21:04] <lesshaste> Sarvatt, thanks
[21:45] <bryce> Ng: hey, quick question on your 8xx system - does it have an S-Video (TV-out) port?  If so, would you mind testing at some point when it's convenient if it does not work on jaunty, and then test karmic alpha-2 as well?  I'm looking at bug 6270 (currently the lowest-numbered X bug report yay), and wondering if the problem is going to still be a problem with the new stack.
[21:57] <Ng> bryce: 'fraid not, just LCD and VGA
[21:57] <bryce> Ng: ok thanks
[22:30] <lesshaste> what's the easiest way to get a dual head setup in ubuntu?
[22:30] <lesshaste> basically, what card do I need to buy?
[23:02] <bryce> lesshaste: I have an ATI X1650 that is quite easy to configure
[23:02] <bryce> lesshaste: I'd recommend any ATI in the R5xx class
[23:03] <bryce> be aware that R600 and newer are not supported as well by the open source driver, but 6xx/7xx cards are the most common in stores these days, so it takes some hunting to find a suitable R5xx card
[23:03] <lesshaste> thanks
[23:03] <bryce> Intel 945 and 965 are also good choices, but only come on motherboards
[23:04] <bryce> with nvidia, I've heard good things about 8800 GTS, however pretty much with nvidia you're still limited to the proprietary driver only
[23:04] <bryce> I've heard 8800 works with -nouveau, and in fact I've put in an order for one in order to check that out.