[09:55] <tseliot> tjaalton: did nvidia -96 fail to build again (for the same reason)? I've reuploaded the source to my website again.
[09:58] <tseliot> tjaalton: please reupload it when you have the time
[10:21] <tjaalton> tseliot: i guess it doesn't try to rebuild it if the version didn't change
[10:22] <tjaalton> but I've requested a rebuild
[10:22] <tseliot> tjaalton: thanks
[10:23] <tjaalton> nope, didn't help
[10:23] <tjaalton> tseliot: you need to bump the version
[10:23] <tseliot> tjaalton: ok, let me do it and reupload the source
[10:26] <tseliot> tjaalton: ok, uploaded. http://albertomilone.com/ubuntu/karmic/to_upload.txt
[10:32] <tjaalton> tseliot: and uploaded
[10:33] <tseliot> tjaalton: thanks again
[16:48] <Q-FUNK> bryce: what is missing to get http://launchpadlibrarian.net/31292587/xserver_1.6.x_add_Geode_GX1_GX2_LX_to_xf86AutoConfig.patch merged into Karmic?
[17:12] <andresmh> Someone at ubuntu+1 told me this would be a good place to discuss some issues I have with Xorg Intel drivers for Karmic. 
[18:25] <bryce> good morning tseliot
[18:26] <tseliot> bryce: good morning to you (or good evening in Italy)
[18:34] <bryce> tseliot, I'll work on the libdrm update
[18:35] <tseliot> bryce: ok, I'll work on the other merges then (I haven't started yet)
[18:39] <bryce> yeah looks like a lot of stuff got done upstream recently, probably prepping for their next release
[18:43] <tseliot> good
[20:17] <apw> bryce, i am seeing some strange behaviour with pretty recent karmic bits on ati ... specificially it is showing me the shutdown screen very briefly on X start
[20:18] <bryce> hmm
[20:18] <bryce> apw, I've upped us to pretty recent git versions on -ati
[20:18] <apw> i can see he window i ran reboot in, for a couple of seconds
[20:18] <apw> and its not the best either in use
[20:18] <bryce> apw, is this with stock karmic kernel or one with backported ati drm bits?
[20:19] <apw> this is with a stock -9 kernel
[20:19] <apw> indeed all stock bits
[20:19] <bryce> ok, there's been some problems I've heard with -ati when using the stock kernel
[20:19] <bryce> bbiab (breakfast)
[20:20] <apw> bryce, it almost feels like every other refresh is not on the real screen, i get junk instead
[20:23] <apw> it is definatly not clearing out its video memory on init, which is potentially a security issue
[20:25] <Q-FUNK> has bryce moved to japan?
[20:26] <superm1> even if he did, 4:26 is a  little early for breakfast isn't it?
[20:27] <Q-FUNK> either that or he got up reaaaaaaaaaaaaaaaaally late in USA
[20:35] <apw> or he is soooo dedicated he only just got round to breaky
[20:38] <tjaalton> it's 12:38 in portland.. not that late for a hacker ;)
[20:38] <tjaalton> PM
[20:39] <Q-FUNK> ah, yes.  west coast
[20:45] <bryce> apw, hmm weird, it works okay on my ati system
[20:46] <apw> its utterly corrupting my display most of the time
[20:46] <bryce> yeah apw is right, I neglected too long to take a break.  blood sugar was getting pretty low ;-)
[20:47] <bryce> morning got kinda screwed up due to meetings and wife having dual flat tires
[20:47] <apw> dual!  what did she do, drive over a milk float?
[20:48] <bryce> she had a "bolt" in one, and nfi on the other
[20:48] <apw> (that metaphore probabally doesn't translate, they used to use glass bottles)
[20:48] <bryce> (a nail or screw I could understand, but a bolt?)
[20:49] <apw> yeah thats sooo very pointy, not
[20:49] <bryce> I suspect the one was due to a stuck valve from after I checked all her tires.  They've replaced the valve as they didn't see anything else wrong
[20:50] <bryce> 2 flat tires + wife 1-day from baby due date == trouble
[20:50] <apw> 10x trouble
[20:59] <rawler> does anyone here happen to know anything about Matrox Parhelia on Ubuntu?
[20:59] <rawler> is there some nice PPA to add, or at least a guide to get better than VESA-graphics?
[21:01] <Q-FUNK> yikes
[21:02] <rawler> *ahh* found https://help.ubuntu.com/community/BinaryDriverHowto/MatroxParhelia :)
[21:02] <rawler> of course :)
[21:02] <rawler> help.ubuntu.com should be my new google.. :)
[21:03] <bryce> h.u.c is waaay out of date on X stuff
[21:04] <bryce> but then, matrox is so ancient even out of date info is probably still of use ;-)
[21:04] <rawler> well.. perhaps.. except all changes in core X breaks all that good ol' stuff.. ;)
[21:04] <rawler> and, it's not exactly.. parhelia.. it's P650, but same driver I assume?
[21:06] <rawler> btw, out of curiosity, what are the odds of seeing old drivers, like matrox and friends up-ported to KMS-glory etc?
[21:06] <rawler> (from a guy that know ~0 about driver-creation)
[21:07] <bryce> ~0
[21:07] <rawler> allright.. :) I thought so..
[21:07] <bryce> requires someone to care enough about the driver to work on it
[21:07] <bryce> by definition old drivers are usually old because no such person exists
[21:07] <rawler> as with all software, of course.. :)
[21:08] <rawler> too bad for KMS though.. it's a bit flaky to rely on it unless also old and exotic hardware can support it.. :S
[21:08] <bryce> anyway, not something we'd put resources into for ubuntu, since we're sufficiently tied up dealing with bugs in the !old drivers
[21:09] <rawler> hehe.. yep.. :)
[21:09] <Q-FUNK> speaking of which, I haven't quite understood how hardware without KMS will work under the new scheme.
[21:09] <rawler> just my question.. :)
[21:09] <rawler> thinking about Nvidia in particular..
[21:09] <bryce> UMS still works
[21:10] <bryce> for now anyway
[21:10] <Q-FUNK> e.g. Geode is not likely to ever get KMS, now that OLPC switched to VIA 
[21:10] <bryce> I'm still waiting for xrandr on some drivers
[21:11] <Q-FUNK> then again, kernel 2.6.31 is still no go on Geode anyhow.  bug filed, camera snapshot added, LKML informed.  no action.
[21:13] <Q-FUNK> ogasawara has been trying to help me narrow down the exact commit that broke things. we sort-of spotted it, but LKML has not acted upon it.  instead Ingo went postal and called our bisect botched.
[21:13] <bryce> gotta love upstream
[21:13] <Q-FUNK> yup
[21:14] <rawler> :)
[21:14] <bryce> I suspect some hw corporations paying for X development that ends up breaking hw produced by corporations not paying for X development is not a stable configuration
[21:14] <Q-FUNK> but basically, older Geodes already broke around 2.6.23 and now recent Geodes broke with 2.6.31, which basically kills the whole LTSP hardware base.
[21:31] <jg> Q-FUNK: you can thank AMD for that..
[21:32] <Q-FUNK> jg: how so?
[21:32] <jg> though I wouldn't say it is "the whole LTSP hardware base"....
[21:32] <jg> Q-FUNK: they bought the Geode, and ended up laying off a very good guy who was maintaining the X (and other) drivers.
[21:33] <Q-FUNK> yup. I know him. I've been involved in xf86-video-geode.
[21:33] <Q-FUNK> OLPC could have just as easily hired him, but didn't.
[21:33] <jg> heh.
[21:34] <jg> I would have, if I could have...
[21:34] <Q-FUNK> jg: that you could not says a lot about the viability of the whole project, TBH.
[21:34] <jg> Q-FUNK: or priorities of certain people....
[21:35] <jg> I wouldn't draw that conclusion....
[21:35] <Q-FUNK> or lack of
[21:40] <Q-FUNK> Jordan had actually planned to get around implementing KMS and was looking forward to it.
[21:40] <Q-FUNK> now, the only one I can think of who might pull it off would be dilinger.
[21:42] <Q-FUNK> here, I'm mostly worried of how many nice surprises like the devPrivates breakage we're gonna encounter before -geode becomes hopelessly broken.
[21:46] <jg> yup.
[22:16] <Q-FUNK> or cjb, but he keeps on having less and less time for -geode.
[22:34] <jg> bryce: every so often, my screen goes off, and then back on again, when it is idle.  Seems Koala's screen saver or blanking is busted....
[22:34] <bryce> jg, yeah everyone is seeing that
[22:35] <bryce> jg, and everyone is claiming "not our fault"
[22:35] <jg> ok, fine...  I'll let you help throw rotten eggs....
[22:36] <Q-FUNK> heh
[22:37] <bryce> jg, let me retrieve the blog about it
[22:38] <bryce> http://blogs.gnome.org/hughsie/2009/08/17/
[22:39] <bryce> jg, I've pulled in the various patches and fixes described up through that blog post, but it seems people still have problems (as do I)
[22:40] <mac_v> bryce: wasnt the gpm side fixed? what is delaying the xorg fixes? upstream or hasnt landed for Ubuntu?
[22:40] <bryce> mac_v, afaik everything on the X side is there
[22:41]  * mac_v  constantly getting the icon in the panel , pointing to that blog :(
[22:42] <jg> yeah, I've seen the icon in the panel, but it wasn't kind enough to let me cut and paste the URL.
[22:43] <mac_v> that was what asac was complaining too ;)
[22:43] <bryce> yep, both patches mentioned there went into our xserver, on aug 14 and 19th
[22:43] <bryce> icon?
[22:43] <mac_v> last month! o.0
[22:43] <mac_v> notification area icon
[22:43] <bryce> not following
[22:43] <bryce> apport crash icon?
[22:44] <jg> bryce: you know who else has had to deal with this sort of stuff, who might have a valid opinion of what the "right thing" is, is cjb.... I'm not sure I believe hugsie'
[22:45] <jg> claims, though.
[22:45] <jg> I see the blanking problem even when I'm nowhere near the keyboard.
[22:45] <jg> (like just now while watching video).
[22:45] <mac_v> bryce: nope > http://launchpadlibrarian.net/30946483/Screenshot.png and Bug #423694
[22:46] <jg> now messing with DPMS shouldn't be resetting any notion the X server has of idleness, I don't thin....
[22:46] <jg> so there may be multiple interacting bugs....
[22:47] <bryce> yeah could be
[22:47] <bryce> hrmble
[22:48] <bryce> probably I should instrument all the dix screensaver stuff
[22:49] <bryce> maybe after all these freezes and crashes are solved ;-)
[22:52] <mac_v> bryce: the low fps with radeon and KMS ? can we expect a solution before karmic? :)
[22:52] <mac_v> from upstream
[22:56] <bryce> dunno
[22:56] <bryce> I'm about to go on leave for a month, though
[23:03] <mac_v> have a fun vacation , when you come back , we'll have loads of bugs waiting for you ;p
[23:08] <bryce> it's paternity leave, hardly a vacation ;-)
[23:21] <Q-FUNK> bryce: first one?
[23:23] <bryce> yea
[23:26] <Q-FUNK> neat :)
[23:37] <jbarnes> 904 ships with xf86-video-intel 2.5.x right?
[23:38] <bryce> 2.6.3 actually - http://packages.ubuntu.com/jaunty/xserver-xorg-video-intel
[23:38] <jbarnes> ah ok thanks
[23:39] <Q-FUNK> bryce: was there anything left to do to get that geode autoconfig patch merged into karmic?
[23:40] <bryce> Q-FUNK, what patch?
[23:40] <Q-FUNK> I noticed that you confirmed the bug after I added the 1.4 and 1.6 patches, but nothing since then.
[23:41] <Q-FUNK> http://launchpadlibrarian.net/31292587/xserver_1.6.x_add_Geode_GX1_GX2_LX_to_xf86AutoConfig.patch
[23:41] <bryce> oh I have scripts that do that
[23:42] <Q-FUNK> bug #423866
[23:45] <Q-FUNK> those patches
[23:45] <Q-FUNK> there's one for jaunty+karmic and one for hardy
[23:46] <Q-FUNK> submitted to debian as well
[23:48] <bryce> alright, I can do the karmic one.  For the other you'll need an sru
[23:48] <Q-FUNK> indeed
[23:49] <bryce> hmm, patch didn't apply
[23:49] <Q-FUNK> no?
[23:49] <bryce> Applying patch 186_autoconfig_geode.patch
[23:49] <bryce> patching file hw/xfree86/common/xf86AutoConfig.c
[23:49] <bryce> Hunk #1 FAILED at 144.
[23:49] <bryce> Hunk #2 succeeded at 152 (offset 1 line).
[23:49] <bryce> 1 out of 2 hunks FAILED -- rejects in file hw/xfree86/common/xf86AutoConfig.c
[23:49] <bryce> Restoring hw/xfree86/common/xf86AutoConfig.c
[23:49] <bryce> Patch 186_autoconfig_geode.patch does not apply (enforce with -f)
[23:49] <bryce> Restoring hw/xfree86/common/xf86AutoConfig.c
[23:49] <bryce> failed! (check stampdir/log/patch for details)
[23:49] <bryce> make: *** [stampdir/patch] Error 1
[23:49] <bryce> dpkg-buildpackage: error: debian/rules build gave error exit status 2
[23:49] <bryce> E: Failed autobuilding of package
[23:49] <Q-FUNK> hm
[23:50] <Q-FUNK> you picked the 1.6 patch?
[23:50] <Q-FUNK> here, it worked when I built test packages for my PPA
[23:50] <bryce> right, commit 842b7a47d583a77 from the last comment
[23:51] <Q-FUNK> that commit might not apply as is
[23:51] <Q-FUNK> besides, I made minor adjustments in upstream git (mainly additional comments)
[23:51] <Q-FUNK> however, the attached patch is diffed against whatever is in karmic and jaunty
[23:53] <Q-FUNK> IIRC upstream git has a somewhat noticable diff between 1.6.3 and... was it 1.6.99 now?
[23:54] <bryce> ah well thanks for uploading it
[23:55] <bryce> er upstreaming it
[23:55] <bryce> uploaded other patch, hope that'll work for you
[23:56] <Q-FUNK> it should
[23:56] <Q-FUNK> in karmic, at least, the fixed gx2 support is already there, so the only part missing is that autoconfig
[23:57] <Q-FUNK> https://bugs.launchpad.net/debian/+source/xorg-server/+bug/423866/comments/9
[23:57] <Q-FUNK> this particular comment explains the whole situation