[01:15] <Sarvatt> nice!
[01:19] <Sarvatt> I guess it was the XvMC stuff that was the problematic one in the end looking at it not just play Xv overlay
[01:22] <RAOF> Fortunately, no one cares about XvMC.
[01:26] <Sarvatt> lots of people care if its disabled even if it's basically useless, you'd be surprised how much email I get about noting I disable it in xorg-edgers in the changelog on karmic because of the old libxcb :)
[01:29] <RAOF> I'm surprised people care about MPEG2 decoding hand-off so much.  I remember watching the gallium XvMC development having trouble with the setup & teardown overhead being more than what it'd take for the cpu to actually just decode the streatm :)
[01:31] <bryceh> they probably don't know, they probably just think it'll make their pr0n look better
[01:32] <Sarvatt> were they testing with the right source for it to matter? it makes the most difference with huge interlaced mpg2 videos and the deinterlacing quality is better which is pretty important on a HTPC
[01:32] <Sarvatt> but for like a progressive source it makes almost no difference
[01:34] <RAOF> ...The other problem they were running into is that nouveau didn't have a memory manager then, so huge mpeg2 videos would ENOMEM :)
[01:36]  * bryceh documents quirking in KMS-land - https://wiki.ubuntu.com/X/Quirks
[01:39] <bryceh> RAOF, for blacklisting nouveau so it uses -nv, do we just put 'blacklist nouveau' in /etc/modprobe.d/blacklist.conf ?
[01:42] <Sarvatt> does nouveau require blacklisting to use -nv? I still haven't tested that, wifes laptop HDD now says failure imminent  so shes back on my nvidia one :(
[01:44] <Sarvatt> anyone familiar with libpciaccess know if pci_device_has_kernel_driver checks if KMS is in use or just if there is a kernel module loaded for the device?
[01:47] <RAOF> bryceh: For some reason in my testing -vesa claimed the display rather than -nv unless I manually listed nv in xorg.conf.
[01:48] <RAOF> That's certainly a fine way to blacklist nouveau, though.
[01:48] <bryceh> ok stuck docs here https://wiki.ubuntu.com/X/KernelModeSetting
[02:01] <bryceh> tjaalton, ok looks like http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/PkgList/versions_current.html is automatically updating once again
[02:02] <bryceh> weird cron issues
[02:02] <bryceh> tjaalton, let me know if you spot any troubles, I suspect I won't be watching it too closely henceforth
[02:14] <Sarvatt> wow, death to vga16fb
[02:14] <Sarvatt> turns on the suspend/resume problems I'm having now with the blob go away when I blacklist it again :D
[02:14] <bryceh> huh
[02:15] <bryceh> did you see the patch on kernel-team@ about it?
[02:15] <Sarvatt> 11 suspends in a row with it blacklisted, second resume hung after removing the blacklist
[02:15] <Sarvatt> nope not yet
[02:15] <bryceh> heya rafiyr
[02:16] <rafiyr> hi
[02:16] <rafiyr> how are you
[02:16] <bryceh> good, just finishing up a few bits before heading up to seattle for the weekend
[02:16] <bryceh> (my sister's in a play)
[02:17] <rafiyr> going for fun?
[02:17] <Sarvatt> that fix on the mailing list wont affect the blob
[02:17] <rafiyr> take that as a yes
[02:17] <bryceh> Sarvatt, ok
[02:17] <bryceh> rafiyr, :-)
[02:18] <rafiyr> I'm heading up to see some family too.
[02:18] <Sarvatt> so its basically, do you want suspend support or do you want a text splash up for 1 second at this point with the blob..
[02:18] <rafiyr> Wish I was better at reading code in the car.
[02:50] <RAOF> Sarvatt: Oh, sweet.  More reasons to hate on vga16fb :)
[03:32] <RAOF> bryceh: About the Intel lid quirks - I'm pretty sure I've seen an upstream commit that's basically “Stop using the lid status for lvds, it breaks too often”
[03:33] <RAOF> So that particular class of quirks might be easily solved.
[03:36] <Sarvatt> RAOF: http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=6e6c822868f113dabe3c33bdd91e883cc28fa11b
[03:37] <RAOF> Sarvatt: :)
[03:38] <RAOF> FWIW, nouveau also has a variant of that approach.
[03:41] <Sarvatt> i was gonna change that part on the wiki but it was actually talking about other bugs that i think might still need quirks
[05:57] <tjaalton> bryceh: ok, thanks!
[05:57] <tjaalton> btw, looks like the autoconfig patch was not guilty for the crash-on-exit bug.. :)
[05:58] <tjaalton> only happens with MALLOC_PERTURB_ set, and with vanilla xserver
[06:49] <tjaalton> hmm, trying syncpackage with -sis
[06:52] <tjaalton> basically it just downloads the source and runs debsign on it, the it's jut a dput away of being "synced"
[06:53] <tjaalton> *just
[06:56] <bryceh> tjaalton, heh
[06:57] <bryceh> so that's all it's been all this time?
[06:59] <ara> bryceh, thanks for the feedback on MT :-)
[07:00] <bryceh> ara, sure; hope it helps
[07:01] <tjaalton> bryceh: yeah, so it's nothing to worry about imo
[07:01] <tjaalton> if you meant the crasher
[07:04] <bryceh> tjaalton, no I meant, that's all we've had to do to sync a package?
[07:04] <bryceh> I always assumed it involved more dials and levers
[07:04] <tjaalton> bryceh: yeah, quite simple :)
[07:05] <tjaalton> you still need to feed the url to it, and answer 'n' when it asks to use the original signature
[07:05] <tjaalton> so there are some quirks left
[07:05] <tjaalton> but I guess those are known and worked on
[07:05] <tjaalton> +being
[07:16] <bryceh> mm
[07:21] <tjaalton> new synaptics (1.2.2)
[09:40] <tjaalton> ok, vmmouse and joystick inputclass configs added and uploaded to my ppa, only evtouch to do
[09:45] <tjaalton> hmm, the tag matching is not properly documented in the xorg.conf manpage, nothing mentioned that the backend needs to set ID_INPUT.tags for MatchTag to work
[10:14] <tseliot> tjaalton: is the new mesa release a bug fix release?
[10:14] <tjaalton> tseliot: yes
[10:14] <tjaalton> we have a snapshot of that branch already
[10:15] <tseliot> tjaalton: ok, so we should just wait for upstream to release it, right?
[10:17] <tjaalton> tseliot: yep, I'll ping debian-x to upload it, or we can dput it as -0u1 if they're busy
[10:19] <tseliot> tjaalton: ok, good
[10:19] <tjaalton> tseliot: bug 546933
[10:19] <tjaalton> https://edge.launchpad.net/~tjaalton/+archive/test/+packages
[10:20]  * tseliot has a look
[10:21] <tjaalton> the build queue is hopelessly long though
[10:22] <tjaalton> but synaptics and evdev works with the previous set of packages
[10:26] <tjaalton> lunch ->
[14:14] <Consul_Falx> hello
[14:14] <Consul_Falx> I'm affected with the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/545289
[14:15] <Consul_Falx> what does the "pll quirk" stand for, and how is it done?
[14:23] <solarion> is everything on the screen being upside-down and backwards a known bug?
[14:23] <solarion> (lucid)
[14:25] <solarion> (eee 901)
[14:25] <tjaalton> yes
[14:25] <tjaalton> wrong libGL
[14:25] <solarion> excellent
[14:26] <solarion> how do I get the right libGL, and which libGL do I have?
[14:26] <tjaalton> dunno
[14:26] <tjaalton> probably a poulsbo in it?
[14:26] <solarion> no
[14:26] <solarion> hell no
[14:26] <solarion> :)
[14:26] <solarion> 945GME
[14:27] <tjaalton> check Xorg.0.log
[14:27] <tjaalton> or pastebin it
[14:27] <solarion> I can't atm, maybe when I get to work
[14:27] <solarion> what am I looking for in xorg.0.log?
[14:28] <tjaalton> what it says after loading libglx
[14:28] <tjaalton> likely nvidia
[14:29] <tseliot> solarion: "ldconfig -p | grep GL" and "update-alternatives --display gl_conf" should show what's wrong
[14:29] <solarion> xorg foundation
[14:29] <solarion> indeed
[14:29] <tseliot> maybe you switched between drivers by simply changing your xorg.conf. This is not the right way to do it
[14:29] <solarion> glcore is nvidia
[14:29] <solarion> effing nvidia
[14:30] <solarion> no
[14:30] <solarion> I have no xorg.conf
[14:30] <solarion> the entirety of what I did was update yesterday
[14:31] <solarion> how do I set back to mesa?
[14:31] <tseliot> please follow this paragraph "Problem: Need to manually review/tweak alternatives settings" here: https://wiki.ubuntu.com/X/Troubleshooting/NvidiaDriverSwitching
[14:31] <solarion> why did it switch on my from just doing an update, though?
[14:32] <tjaalton> good question
[14:32] <solarion> I'd done *nothing* manually, and I've not selected *any* proprietary drivers
[14:32] <solarion> this is also a pretty fresh install from beta 1
[14:32] <tjaalton> check dpkg.log
[14:34] <solarion> what specifically am I looking for?
[14:35] <solarion> oh, 03-23 had update-alternatives --force with GL
[14:35] <tjaalton> see what it installed
[14:35] <solarion> yes
[14:35] <solarion> nvidia-current seemed to force GL 
[14:35] <tjaalton> nice :)
[14:35] <solarion> 195.36.15
[14:35] <solarion> -0ubuntu1
[14:35] <tjaalton> what pulled it in?
[14:36] <solarion> what pulled in nvidia-current?
[14:36] <tjaalton> yes
[14:36] <solarion> I've no idea
[14:36] <tjaalton> as a dependency
[14:36] <solarion> I'm guessing that's an apt thing that I always forget. :)
[14:37] <tjaalton> apt-cache rdepends
[14:37] <tjaalton> or use aptitude
[14:38] <solarion> nvidia-glx-185
[14:38] <tjaalton> had that installed?
[14:38] <solarion> eh, I'm not sure where this is getting pulled in
[14:39] <bigon> are you aware of that bug?
[14:39] <bigon> http://bugs.freedesktop.org/show_bug.cgi?id=26394 
[14:39] <tjaalton> no
[14:40] <solarion> modealiases seems to have pulled in nvidia (first reference in dpkg.log)
[14:40] <solarion> nvidia-173-modealiases
[14:40] <tjaalton> those are installed by default
[14:40] <tjaalton> the don't depend on nvidia-current
[14:40] <tjaalton> they
[14:40] <solarion> oooh
[14:40] <solarion> I think I know what happened.
[14:40] <solarion> hahahahah
[14:41] <solarion> It's when I pulled the packages from my workstation (which has nvidia)
[14:41] <solarion> I'm such an idiot
[14:41] <tjaalton> proven ;)
[14:41] <solarion> verily
[14:41] <tjaalton> use pkgsync if you need to do that
[14:41] <tjaalton> and list nvidia in mayhave
[14:42] <solarion> not heard of pkgsync
[14:42] <solarion> I was using the default tools (synaptic)
[14:42] <tjaalton> install and see
[14:42] <solarion> lemme kill this effing nvidia driver
[14:42] <tjaalton> it's a tool to keep a predefined set of packages installed
[14:42] <tjaalton> nothing more, nothing less
[14:42] <solarion> hmmm
[14:43] <tjaalton> so if you want to keep the same set of packages, copy the config around
[14:43] <tjaalton> but keep hw related stuff in mayhave
[14:43] <solarion> too bad that's not more automatic
[14:44] <tjaalton> what do you mean?
[14:44] <solarion> I mean, hw drivers are clearly hardware-dependent and a separate category from libs, which are separate category of package from apps
[14:45] <tjaalton> well there aren't too many of them anyway
[14:45] <solarion> too many of which?
[14:45] <tjaalton> might as well handle them by hand
[14:45] <tjaalton> hw drivers
[14:46] <tjaalton> that you need to install
[14:46] <solarion> sure, but it sucks more than it needs to. :)
[14:46] <tjaalton> wfm
[14:46] <superm1> tseliot, well while you are sorting out that fglrx handler in jockey, there's a few commits that need cherry picking from trunk of jockey to fix some other bugs too
[14:46] <superm1> pitti should be able to point them out if you aren't sure
[14:46] <solarion> until you forget something one day and have to put the pieces back together
[14:47] <solarion> "wfm" isn't an answer to "it sucks more than it has to"
[14:47] <tjaalton> it was just a suggestion
[14:48] <solarion> I am a big fan of automatic things doing tedious things for me
[14:48] <solarion> like this one. :)
[14:48] <tseliot> superm1: maybe we should discuss this with pitti in, say, #ubuntu-desktop?
[14:48] <solarion> Anyhow, thanks a lot for the pointer. I'll check out pkgsync
[14:49]  * solarion heads to work
[14:50] <superm1> tseliot, sure
[17:02] <Sarvatt> gonna start doing something crazy on edgers - http://sarvatt.com/downloads/patches/exa_backport_to_1.7.6.patch
[17:06] <Sarvatt> buh Applying patches...Patch 111_armel-drv-fallbacks.patch does not exist
[20:08] <Sarvatt> ton of new tools in intel-gpu-tools now, just uploaded a new one to edgers. intel_error_decode looks nice :)
[20:09] <Sarvatt> wow intel_reg_dumper doesn't hang the system anymore! \o/
[20:53] <Sarvatt> http://lists.freedesktop.org/archives/xorg/2010-March/049749.html
[21:04] <Duke`> hum nvidia announced deprecation of xf86-video-nv
[21:06] <tjaalton> wow
[21:12] <mdeslaur> wow, so no more 2d source code for newer nvidia chips
[21:20] <bjsnider> they said that it would be better to use the vesa driver, which is true and beyond question
[21:20] <tjaalton> didn't say a word about nouveau ;)
[21:21] <bjsnider> nouveau has a different purpose than nv did
[21:21] <bjsnider> nv was just for an initial x screen so users could install the blob
[21:21] <tjaalton> yep
[21:21] <bjsnider> nouveau is a replacement for the blob
[21:22] <bjsnider> vesa does better that nv was supposed to be for
[21:50] <jcristau> bjsnider: nv supported dual head.  vesa not so much.
[21:51] <bjsnider> did you need dual-head to install the blob?
[21:52] <jcristau> who said i cared about the blob
[21:53] <bjsnider> nv's purpose is to provide an initial x screen to facilitate installation of das blob
[21:53] <jcristau> well that's what nvidia wants it to be, yes
[21:53] <BUGabundo> evening
[21:54] <bjsnider> anyway, we figured out a patch to the gnome-shell that fixes all nvidia issues