[00:13] what's the best way to tell if I'm running r600 vs. r600g? [00:13] ah, glxinfo: OpenGL renderer string: Gallium 0.4 on AMD RV770 [00:20] bryceh: The g in r600g stands for Gallium [00:23] soreau, yes I'm aware ;-) [00:24] bryceh: I misread your statement there [00:24] humber:~$ grep r600 /var/log/Xorg.0.log [00:24] [ 236.995] (II) RADEON(0): [DRI2] DRI driver: r600 [00:24] [ 237.000] (II) AIGLX: Trying DRI driver /usr/lib/dri/r600_dri.so [00:24] [ 237.002] (II) AIGLX: Loaded and initialized r600 [00:25] was surprised I don't have the 'g' on those. But "r600" == "r600g" here === yofel_ is now known as yofel [18:17] Hey guys, Im looking in driconf and there are a lot of options missing [18:18] even in expert mode [18:18] Is there some package missing? [18:33] bryceh, i'm about to buy a laptop with a 6770m. will i be able to patch fglrx whenever the xserver abi changes or will be stuck with radeon except for april and october? [18:37] no you cant patch fglrx for abi changes, we might not do 1.11 for 11.10, and it'll work fine with radeon since its a rebranded 5xxx series [18:39] Sarvatt: Any idea about driconf? [18:39] Im pretty stumped on this one [18:39] soreau: what about it? [18:39] sorry, missed those messages umm [18:39] what GPU is it? [18:40] Sarvatt: It used to have a near plethora of options, now its next to nothing. rv350/r300g [18:40] sarvatt, oneiric will be 1.10.x? [18:40] i'm guessing you're talking about the options that were exposed with r300c instead of r300g [18:41] Sarvatt: hmm.. maybe so but it doesnt make sense for gallium to expose less I would think [18:41] the options were only there for the classic driver, its not based on the gpu it's based on what the dri driver exposes [18:41] ok [18:42] LLStarks: its possible, we're going to talk about it at UDS [18:43] * soreau ppa-purges xorg-edgers to see [18:44] soreau: LIBGL_DRIVER_PATH=/usr/lib/dri-alternates/ driconf should show the r300c ones to be sure [18:44] Oh interesting [18:45] r300c is in there so it gets loaded when KMS isn't used automatically [18:45] Sarvatt: Is that to say, you can run any app with the classic drivers by setting this path? [18:45] yep [18:45] and these are updated classic drivers from xorg-edgers, not stock ubuntu [18:45] its the same in the archive [18:46] Sarvatt: ok thanks for that information [18:46] libgl1-mesa-dri installs both in both the ppa and natty [18:47] the only major changes between the ppa and natty are that i have libtxc_dxtn in there, texture-float is enabled and the tls patches in edgers [18:48] oh and the whole libglapi-mesa package split [18:49] err tls patches are disabled in edgers which breaks some obscure apps [18:50] Sarvatt: s3tc?? [18:50] yeah [18:50] How does that work to enable/disable it? [18:50] the lib should be pulled in automatically so its enabled [18:50] But it causes problems for many apps that do not use this compression format.. [18:51] many being a few proprietary apps yeah [18:51] huh [18:51] oh ya mean having it installed causes problems in some apps? [18:52] Yes [18:52] is that a radeon specific thing? what does the driconf option to enable it default to? [18:52] There is no driconf option in gallium exposed apparently [18:53] This was actually the problem I was referring to in the first place [18:53] sarvatt, what makes 1.11+ so prohibitive? i though randr and the rest of xinput2 were safe for later this year. [18:53] are you sure the problems were just with the screwed up release? I put the latest 1.0.0 in there [18:55] libtxc_dxtn070518 had some nasty bugs in it [18:56] * Sarvatt has to run, sorry [19:00] soreau: oh you're on maverick? I haven't updated that in months in xorg-edgers, I've been talking about natty all this time sorry [19:00] Sarvatt: Well the fact remains.. classic exposes many more options than gallium [23:41] Sarvatt or RAOF: Are you aware of this: http://bugs.kde.org/show_bug.cgi?id=270942 [23:41] KDE bug 270942 in compositing "Direct Rendering is wrongfully disabled on Intel graphics since mesa 7 10 1" [Normal,Unconfirmed]