[00:02] <bryceh> having a new checkout could only help, I should think?
[00:06] <RAOF> bryceh: Maybe give jockey & nvidia-common a bit of time to percolate out first.
[00:07] <bryceh> RAOF, *nod*
[01:57] <bryceh> hey, a few weeks ago I mentioned the idea of providing mesa updates (for Intel graphics) through the x-updates PPA.  At the time there were some concerns raised.  Sarvatt I think you demurred about having mesa and libdrm updates in there for proprietary driver users that might not need it.
[01:58] <bryceh> I'd like to open discussion on this again.  We have driver updates for Intel (needed by certain games) which include mesa, i915 (via dkms), cairo, wayland, and the ddx.
[02:00] <bryceh> currently we're staging them in dedicated ppas but I'm thinking that being able to point to a single ppa for updates would be simpler to communicate to folks.
[02:00] <bryceh> would love to hear feedback.  Dinner calls, so will be back later tonight.
[02:32] <Sarvatt> bryceh: i915 via dkms is a lofty goal but wont happen, they end up touching intel_agp every kernel version and thats built in so can't be a module you can just dkms to get the updates.. back when I had an objection it was because blobs ended up needing the newer libdrm but thats not the case for the last few releases, no problems with it anymore :P cairo is kind of sketchy because it broke all EXA drivers for a long time in 1.12 even though intel wa
[02:32] <Sarvatt> s fine, but there is more in the world than just intel.. if it's reenabling accelerated gradients they want in there thats fine, everything should be ok now but it wasn't until after feature freeze so we're stuck with that in 12.10's cairo
[02:40] <Sarvatt> if they want cairo 1.12 in precise for there it's going to break nouveau and ati at the very least and need updates of those too, not that thats a big of a deal
[02:40] <Sarvatt> lts backports might be more appropriate though
[02:48] <bryceh> https://launchpad.net/~ubuntu-x-swat/+archive/intel-graphics-updates/+packages is one of the ppas.  mesa9's the other.
[02:49] <bryceh> Sarvatt, the i915 dkms package is included there if you want to tease it apart and see what they're touching
[02:50] <RAOF> Sarvatt: The idea here is the x-updates PPA, right? If they want the new cairo, we can just include the new nouveau & ati, right?
[02:50] <Sarvatt> yeah will be interesting to see how it works considering intel_agp wont bind to any of our haswell systems so i915 won't work and that part can't be modular
[02:51] <RAOF> Yeah, that's moderately annoying :)
[02:52] <bryceh> I figure it'd be pointless for nouveau and ati folks to install x-updates if we didn't put the new bits there...  ;-)
[02:53] <Sarvatt> RAOF: yeah updating those is no big deal, just something that wouldn't be considered we'd have to watch out for :P
[03:56] <tjaalton> bryceh: thanks!
[06:11] <tjaalton> marked desktop-q-hybrid-graphics as implemented
[06:11] <tjaalton> xrandr snapshot got in earlier
[06:18] <tjaalton> mesa snapshot? ok then
[06:19] <tjaalton> oh this time the 9.0 branch has actually changed
[06:20] <tjaalton> 63 commits, not bad
[06:23] <RAOF> tjaalton: Thinking of hybrid graphics - do they work for you with the recent unity?
[06:23] <tjaalton> RAOF: work in which way?
[06:23] <RAOF> Get rendering
[06:24] <tjaalton> the radeon fixing patch actually broke it here, nouveau throws in the towel
[06:24] <tjaalton> but it's a good tradeoff I think :)
[06:24] <tjaalton> mentioned it to airlied back then, but haven't had time to look closer
[06:25] <tjaalton> but I'll give it a go to see where it's at
[06:29] <RAOF> Civ V no longer does any rendering with DRI_PRIME set, but only under Unity.
[06:30] <tjaalton> ah
[06:31] <tjaalton> I've only tested it so far that glxgears hangs the machine after a few seconds :)
[06:31] <tjaalton> told that it's to be expected
[06:35] <RAOF> Awesome.
[06:35] <RAOF> Civ V works under metacity.
[06:35] <RAOF> ...I *think* I verified that it's actually using r600 there.
[06:35] <RAOF> But there's something odd happening, 'cause glxgears -fullscreen works just fine.
[06:51] <mlankhorst> hey
[06:52] <mlankhorst> RAOF: well if rendering takes too long intel will show the frame before it finished drawing
[06:55] <mlankhorst> what if you turn off vsync?
[08:04] <Hanmac> my radeon driver keeps crashing with  "irq 18: nobody cared (try booting with the "irqpoll" option)" ... someone an idea to fix that?
[08:06] <mlankhorst> whats on irq 18 in /proc/interrupts?
[08:06] <Hanmac>  18:          0          1        197      70917   IO-APIC-fasteoi   ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, radeon
[08:08] <Hanmac> before i get the irq error i also get this:
[08:08] <Hanmac> [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8500)=0xCAFEDEAD)
[08:08] <Hanmac> [drm:r600_resume] *ERROR* r600 startup failed on resume
[08:12] <Hanmac> mlankhorst is this an software problem or iam the problem? :( .... or have you an idea to fix that?
[08:13] <mlankhorst> oh so it crashes during resume?
[08:15] <Hanmac> not that i knew ... i am working on something, and than the output goes gray or stripes sometimes i still see a square where the mouse was sometimes i see it not, if i see the square i can move it but its damm slow, and if i click it chanes nothing on the output ... and tty1-tty6 has the same stripes too
[08:16] <Hanmac> it may even happen before i could login oO
[08:17] <Hanmac> the only known solution is to goto tty1 and try to reboot with typing blind
[08:17] <mlankhorst> is that really the only thing in the log?
[08:17] <mlankhorst> and precise or quantal?
[08:20] <Hanmac> quantal http://pastebin.com/E8491jBM << part of the log, http://pastebin.com/Cf9Mpch1 << installed packages
[08:22] <xclaesse> outch, cannot set more than 1024x768 on my external screen since latest ubuntu upgrade :/
[08:22] <xclaesse>  xrandr does not list any higher resolution
[08:23] <xclaesse> in logs I see this: [    17.229] (II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync
[08:23] <tjaalton> "latest upgrade"=
[08:23] <xclaesse> but nothing higher
[08:23] <tjaalton> ?
[08:23] <xclaesse> did apt-get dist-upgrade this morning, rebooted, and tadaaaamm :)
[08:23] <tjaalton> so what changed?
[08:24] <xclaesse> dunno what packages it upgraded exactly, but there were some x stsuff
[08:24] <tjaalton> running edgers?
[08:24] <mlankhorst> kernel update?
[08:24] <xclaesse> yeah kernel as well, IIRC
[08:24] <xclaesse> running Quantal
[08:25] <xclaesse> Linux X230 3.5.0-16-generic #25-Ubuntu SMP Fri Sep 28 22:31:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[08:25] <mlankhorst> Hanmac: is it like https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328  ?
[08:25] <tjaalton> xclaesse: does it work with -15?
[08:25] <tjaalton> if yes, file a bug against the kernel
[08:25] <xclaesse> tjaalton, let me reboot to try :)
[08:27] <tjaalton> xclaesse: pastebin /var/log/dpkg.log if the older kernel doesn't work
[08:27] <Hanmac> mlankhorst the curruption on my pc looks a bit different but similar enough ... thanks for pointing it
[08:29] <mlankhorst> interesting tiling corruption :p
[08:29] <xclaesse> tjaalton, actually I've got no other kernel installed
[08:30] <mlankhorst> .. :/
[08:30] <xclaesse> does ubuntu *finally* remove older kernels when upgrading instead of waiting for /boot to be full? 
[08:30] <mlankhorst> it should keep at least the previous one though
[08:31] <xclaesse> ok so maybe there just were no kernel updates since I installed
[08:31] <xclaesse> made a clean install last weekend
[08:33] <tjaalton> xclaesse: ls /boot
[08:34] <tjaalton> ah
[08:34] <tjaalton> install pastebinit and run 'pastebinit /var/log/dpkg.log' then
[08:36] <mlankhorst> I'm going to see if I can get https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1044680 fixed at least
[08:37] <xclaesse> tjaalton, /boot contains only -16 ;)
[08:38] <xclaesse> tjaalton, http://paste.ubuntu.com/1257505/
[08:38] <mlankhorst> tjaalton: pah, /lib/modules is a lot better indication anyway
[08:48] <tjaalton> xclaesse: file a bug anyway, ubuntu-bug xorg
[08:49] <mlankhorst> tjaalton: I'm fairly sure there might already be a bug about it :/
[08:50] <mlankhorst> then again maybe not
[08:51] <mlankhorst> oh my 570 is now partying too
[08:51] <mlankhorst> 6570*
[08:51] <tjaalton> I'm not going to ask the logfiles one at a time
[08:51] <tjaalton> better to have them somewhere
[08:51] <tjaalton> nothing suspicious on the upgrade log
[08:52] <xclaesse> tjaalton, I never remember how to fill a bug in mp
[08:52] <xclaesse> lp
[08:52] <tjaalton> unless it's your valgrind fix that btoke it :P
[08:52] <mlankhorst> I was testing my 6570, it seems to have done weird things
[08:52] <tjaalton> xclaesse: I just told you
[08:52]  * Hanmac is back from yetanother reboot
[08:53] <xclaesse> ah, ubuntu-bug is a command...
[08:53] <tjaalton> yep
[08:53] <xclaesse> the "report a bug" link in lp is a trap
[08:53] <mlankhorst> normally it's ok but for xorg we collect a whole bunch of logs so we don't have to ask for them
[08:55] <xclaesse> tjaalton, I hope it included all you need: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1060808
[08:56] <xclaesse> tjaalton, in the meantime, is it possible to "force" the screen resolution?
[08:57] <tjaalton> xclaesse: maybe, not sure how
[08:57] <tjaalton> xclaesse: is the external screen connected all the times?
[08:58] <xclaesse> when I'm at office, yes :p
[08:58] <tjaalton> try booting without it attached
[08:58] <xclaesse> but it's a laptop on dock station
[09:00] <tjaalton> there is bug 1049534 but you said it worked after the fresh install
[09:01] <tjaalton> xclaesse: which installation image did you use?
[09:03] <xclaesse> tjaalton, quantal daily live, last weekend
[09:03] <xclaesse> was working perfectly yesterday
[09:04] <Hanmac> mlankhorst: there is my curruption scene: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1043328/comments/5 ... looks similar right?
[09:05] <tjaalton> xclaesse: check the monitor configuration capplet
[09:05] <xclaesse> tjaalton, aahh,  reboot without docking, then dock once logged worked!
[09:05] <tjaalton> ok
[09:06] <tjaalton> good to hear then
[09:06] <xclaesse> but I'm 200% sure that booting while docked was working previously
[09:09] <mlankhorst> http://pastebin.com/KPFAVvzr I think this might be that SIGABRT ati bug..
[09:09] <Hanmac> ... hm i need to get the bug an higher Importance ... imo that the system crash multible times per day sounds like very critical ...
[09:09] <mlankhorst> oh nm its a closescreen thing
[09:10] <xclaesse> tjaalton, thanks for the help!
[09:10] <xclaesse> commented on the bug that docking after being logged fixed it
[09:11] <tjaalton> xclaesse: it's probably a dupe of the other bug, a race in the kernel dri driver
[09:11] <mlankhorst> tjaalton: I'm going to update xxv-ati, might fix a bug
[09:11] <tjaalton> mlankhorst: ok
[09:13] <tjaalton> hmm, no vga capable monitors in the house anymore :/
[09:13] <tjaalton> oh, forgot about the tv..
[09:16] <mlankhorst> tjaalton: pushed
[09:17] <tjaalton> oh, a new snapshot
[09:17] <mlankhorst> yeah seemed to have a bunch of relevant fixes :)
[09:18] <mlankhorst> oh nm
[09:18] <mlankhorst> can skip it, it just removes mibstore.h
[09:19] <tjaalton> right :)
[09:19] <mlankhorst> you didn't update debian-experimental when you updated the snapshot :P
[09:20] <tjaalton> meaning RAOF?
[09:21] <mlankhorst> you as in whole ubuntu-x, but yeah raof it seems :)
[09:22] <mlankhorst> could still upload it for the libdrm dependency fix but I don't think it is that important
[09:22] <Hanmac> mlankhorst did you push the xxv-ati package changes? i very looking forward to it
[09:23] <mlankhorst> I'll see if I can fix the crash in closescreen first
[09:39] <tjaalton> xclaesse: is the display cloned when you boot docked?
[09:39] <tjaalton> what happens here is that the displays are cloned when booting up with the external one attached
[09:40] <tjaalton> and it'll use extended mode when plugging it in post-login
[09:40] <tjaalton> not a driver bug
[09:41] <tjaalton> hmm, guess it isn't cloned for you, if the laptop is using the native resolution
[09:43] <xclaesse> tjaalton, it is cloned in boot splash and gdm, but not once logged
[09:47] <tjaalton> xclaesse: ok
[09:58] <Hanmac> mlankhorst sorry if i anoy you, but where do you publish the xxv-ati package? i want to look when its finish
[09:59] <mlankhorst> Hanmac: no point, no real fix in it
[09:59] <Hanmac> that makes me sad :'(
[10:04] <tjaalton> you can try a newer mainline kernel
[10:04] <Hanmac> tjaalton do you mean me?
[10:05] <tjaalton> yes
[10:06] <Hanmac> my linux image is 3.5.0.16.* ... is this new enough?
[10:06] <tjaalton> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[10:07] <tjaalton> try 3.5.5
[10:07] <tjaalton> need to install both -image and -image-extra
[10:09] <Hanmac> yeah i know ... but where are the lowlatency packages? ... 
[10:12] <tjaalton> nowhere
[10:12] <tjaalton> it's mainline..
[10:13] <tjaalton> you don't need fancy options for testing if your gfx work
[10:17] <Hanmac> ok download them for testing ... the problem is that i cant provoke the bug ... (and someday i need the lowlatency features back ...)
[10:45] <Hanmac1> tjaalton why do you think an new kernel could help with my problem?
[10:46] <tjaalton> Hanmac: because that's where most of the magic is
[10:48] <Hanmac> hm from my kern.log it looks that drm & radeon & r600  are the evil guys: https://launchpadlibrarian.net/118212480/kernlogpart.txt
[10:55] <Hanmac> i downloaded an 3.5.5 and one 3.6.0 ... so i could test if some of them is working longer ...
[10:55] <ricotz> Hanmac, the kernel contains the actual drivers -- and yes test those two
[10:55] <tjaalton> 3.5.5 has "drm/radeon: make 64bit fences more robust v3"
[10:56] <tjaalton> mlankhorst: is that what you're backporting?
[10:56] <tjaalton> re #radeon
[10:56] <ricotz> tjaalton, irc quantal master-next already contains 3.5.5 so i guess it will be out soon
[10:57] <tjaalton> yep
[10:57] <tjaalton> went through the drm changes in 3.5.5
[10:57] <tjaalton> earlier today, it's a long list :)
[10:57] <mlankhorst> tjaalton: yeah trying to see if v3.6 works
[10:58] <ricotz> yeah
[10:58] <mlankhorst> if that works I'll try to see if I can get it working on the 3.4 kernel
[10:58] <mlankhorst> i think it should be similar to get working
[10:58] <tjaalton> why 3.4?
[10:58] <tjaalton> quantal has 3.5 :)
[10:58] <mlankhorst> erm quantal kernel at least
[10:59] <mlankhorst> oh right, my panda is on 3.4 :P
[10:59] <Hanmac> i would not have this problem if fglrx did not drop my graphic card from the supported :(
[10:59] <tjaalton> you should feel blessed
[11:01] <mlankhorst> at least you're not seriously considering rewriting ttm
[11:01] <mlankhorst> or at least rip the memory management out too
[11:02] <Hanmac> my pc only need to suvive this month ... i will do an rebuild of the hard&soft-ware when the new CPU's are out ...
[11:02] <mlankhorst> no idea what it's doing now, sigh!
[11:02] <mlankhorst> oh right the depmod on first new kernel
[11:11] <Hanmac> hm i get still "[drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !" with the 3.5.5 but it seems not SO bad ... (i mean not so bad than output-curruption)
[11:13] <mlankhorst> yeah it recovers from whatever causes it to hang up for me :/
[11:14] <mlankhorst> but it's still hanging up
[11:22] <Hanmac> hm if the 3.5.5 does not crash for me, when do i get the packages as ppa or in the default ubuntu repo? (ps and i would likeit if i get lowlatency packages too)
[11:25] <tjaalton> -17 will have 3.5.5
[11:25] <tjaalton> *will be based on 3.5.5
[11:26] <Hanmac> what do you mean with "-17"? i dont get it ...
[11:27] <tjaalton> 3.5.0-17, the official package
[11:27] <tjaalton> meaning you'll get the usual flavours with it
[11:28] <Hanmac> OH ok ... i dont care much about versionsnumbers ... i only wonder why its called "3.5.0-17" when its an "3.5.5" inside ... 
[11:30] <tjaalton> dunno
[11:59] <mlankhorst> wee bugs bugs bugs
[12:04] <Hanmac1> 3.5.5 was no help for me :/
[12:05] <mlankhorst> Hanmac1: Yeah I tested drm-next too, and filed a bug upstream
[12:06] <Hanmac> can you give me a link to the upstream bug? so i can monitor it?
[12:07] <tjaalton> mlankhorst: link it to the lp bug
[12:07] <mlankhorst> I already did, both ways
[12:07] <tjaalton> ah
[12:13] <Hanmac> currently i am running 3.6 daily ... but i dont think this solv something
[12:14] <mlankhorst> I tested drm-next, still broken there, so you will be out of luck by trying that..
[12:15] <Hanmac> mlankhorst: about " shows SMALL pieces of horizontal corruption on plymouth and Xorg" i have some image made by mobile phone that could show LARGE pieces of corruption 
[12:15] <Hanmac> https://launchpadlibrarian.net/118210933/IMG_20121003_102910.jpg << as you can see, you see nothing good :P
[12:16] <mlankhorst> same thing
[12:18] <Hanmac> hm I notice that the temperature. showing by sensors  is going higher in the moment is crashing ... 
[12:23] <mlankhorst> no surprise there
[12:23] <mlankhorst> that's usually the case with HCF commands
[12:24] <mlankhorst> https://en.wikipedia.org/wiki/Halt_and_Catch_Fire
[12:25] <Hanmac> "the CPU does not usually catch fire" ... until something is VERY wrong :D
[12:38] <Hanmac> mlankhorst my graphic "card" is "ATI Radeon HD 3300 Graphics" so the error does not happen on "RadeonHD 6570" alone ..
[12:38] <mlankhorst> weird, maybe different issue? my 5450 works fine
[12:41] <Hanmac> sorry i dont know :/ maybe it picks the wrong radeon driver? is r600 for an "RadeonHD 3300" currect?
[12:44] <mlankhorst> it's a rs780d if I may believe wikipedia
[12:44] <mlankhorst> does precise work?
[12:44] <Hanmac> precise had work because i used fglrx ... 
[12:47] <mlankhorst> might be a different bug then
[12:48]  * mlankhorst retries 5450 just to be sure
[12:49] <mlankhorst> ugh erm 5450? i meant 5570, evil numbers :p
[12:49] <Hanmac> hm i need to find the manual because google dont find anything when i type the mainboard name
[12:57] <Hanmac> okay i dont know what grapic chip it is only "ATI Radeon HD 3300 Graphics" ... ps its onboard ... i found the mainboard name: dfi lp jr790gxm3h5
[14:06] <mlankhorst> don't worry about that
[14:07] <mlankhorst> try apport-bug xorg and file a new bug
[14:15] <Hanmac> hm ps if you ask i should make a fresh install? yeah its planed for this month
[14:16] <mlankhorst> its not windows, fresh install wont solve this problem
[14:30] <Hanmac> mlankhorst there are other funny thinks wich confuses me ... like the panel calendar shows the wrong month-panel after clicking, and the automatic smart checking is for some reason not loaded (that means the disks gui says: smart is not enabled, but i could run smart manualy) ... the problems does or appear on the ubuntu live cd so i think it may be some config problem ... ¿
[14:40] <Hanmac> my system is upgraded since lnyx ... i think sometime an fresh install is useful 
[14:40] <Hanmac> PS: @ mlankhorst there is my bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1060987
[14:41] <mlankhorst> thanks
[14:50] <Hanmac> should I add my kern.log to the bug?
[14:52] <mlankhorst> it's already attached that by opening the bug :)
[14:53] <tjaalton> dmesg is, but it's not interesting from this boot
[14:55] <mlankhorst> tjaalton: well yeah it needs to be from the corrupted one
[14:56] <Hanmac> PS: you may be wonder but lightdm & wayland are installed but not used currenty ... 
[14:56] <Hanmac> what may be more wonderable: for some reason gdm is still a bit broken, so currently i use kdm but still with gnome-classic
[15:15] <bryceh> mesa 9 scheduled for next wed
[15:16] <tjaalton> yeah and there's autotools stuff still pending
[15:17] <tjaalton> started the merge but patch 118 needs an update
[15:19] <mlankhorst> I'll get it working then
[15:23] <tjaalton> pushed what I had
[15:24] <Hanmac> ok 3.6.0daily is not save too but it was an different "bug" hm
[15:35] <mlankhorst> well since 118 was supposed to fix build errors I'll try without first
[15:35] <tjaalton> it won't work
[15:35] <tjaalton> well, it'll have linking issues
[15:36] <tjaalton> mattst88 posted a set of patches to fix various issues, but that was last week
[15:36] <tjaalton> not merged there yet but apparently targeted for 9.0 too
[15:36] <mlankhorst> ok I'll pick those, then
[15:37] <tjaalton> patch 13/16 should be enough
[15:37] <tjaalton> "automake patches for 9.0"
[15:41] <bryceh> given that oct 11th is past final freeze, think we can still get the tagged 9.0 included in the release?  I'm thinking maybe this puts us into SRU territory
[15:41] <tjaalton> yeah
[15:42] <tjaalton> it's already a month late :)
[15:45] <mlankhorst> sigh stupid mail archives
[15:45] <mlankhorst> I'm fairly spammers are smart enough already to defeat @ substitution
[15:49] <bryceh> mlankhorst, if they even care
[15:49] <mlankhorst> yet we still all mangle email addresses
[15:49] <mlankhorst> :/
[15:49] <bryceh> we're not exactly their target audience ;-)
[15:54] <mlankhorst> tjaalton: pushed, untested, doing build test now
[15:54] <Hanmac> mlankhorst: about my bug, what do you mean with "no hardware lockup " in my bug?
[15:55] <mlankhorst> Hanmac: the other one has some kind of hardware lockup in dmesg, yours didn't
[15:56] <Hanmac> you mean stuff like [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8500)=0xCAFEDEAD) ? its in the kernlog
[15:57] <mlankhorst> oh ok attach it then
[15:58] <Hanmac> i attached my entire kernlog
[16:02] <mlankhorst> probably a dupe then :)
[16:04] <Hanmac> hm probably not ... i get IRQ problems, he gets none (but its because my radeon shares the irq with others)
[16:07] <mlankhorst> tjaalton: seems to build
[16:07] <tjaalton> cool
[16:08] <ehoover> Sarvatt: Is there something else that needs to be done to get Bug #1059276 fixed in Precise as well?
[16:18] <mlankhorst> ehoover: looks good to me
[16:18] <ehoover> mlankhorst: well, a package was built for quantal but not for precise (https://launchpad.net/ubuntu/+source/libxcb)
[16:19] <mlankhorst> Sarvatt: are you sru'ing it?
[16:21] <Sarvatt> the regression potential part needs to be filled out first, was giving it a few days of using it to see if there were any obvious regressions but its been ok
[16:21] <Hanmac> mlankhorst i notic that debian has fglrx-legacy packages ... who should i ask for ubuntu ones?
[16:22] <Sarvatt> Hanmac: file a bug, assign tseliot (~albertomilone on launchpad), he already had plans to do it afaik
[16:23] <mlankhorst> I prefer to have radeon fixed though
[16:23] <ehoover> ah, i thought a package would still get built and it just wouldn't get pushed as part of the stable repo.
[16:24] <ehoover> (my bad, sorry to be a troublemaker)
[16:24] <tseliot> Sarvatt: yes, well, the main problem is that the legacy driver doesn't support the new X abi
[16:24] <bryceh> tseliot, ha of course
[16:24] <Sarvatt> doh!
[16:25] <tseliot> :(
[16:26] <Hanmac> tseliot shit you are right :'(
[16:27] <tseliot> I might introduce it in Quantal but we'll see
[16:27] <tseliot> I have yet to introduce Nvidia's new legacy driver
[16:48] <mlankhorst> I believe best way forward is to make radeon better than fglrx, not a high bar I know :p
[16:51] <Hanmac> i dont think you can make radeon as fast as fglrx was ... fglrx had 10times more fps than radeon ...
[16:55] <mlankhorst> that means that somewhere there is probably a simple speedup that could be done to at least double the fps in radeon, would just need to find it :p
[17:01] <Hanmac> sorry that i cant help with that ... i dont even understand ogre 100%
[17:09] <mlankhorst> just need to know command line stuff really
[17:09] <mlankhorst> and some C
[17:10] <Hanmac> i did some C stuff with glfw, but writeing graphic-driver is too freaky for me :/
[17:11] <mlankhorst> Why?
[17:12] <Hanmac> i dont know ... i prefer my code more object orientented than pure C is ...
[17:13] <mlankhorst> can't get more object oriented than raw drivers!
[20:36] <Hanmac> hm it may be interesting but 3.6daily crashs a bit more worse than 3.5.5 ...
[21:04] <dj_ryan> well i tried to make xinerama, nvidia + intel work
[21:04] <dj_ryan> but ubuntu is excessively crashy
[21:04] <dj_ryan> so i have to give up on triple monitor
[21:04] <dj_ryan> X11 is so so far behind the times it's sad
[21:37]  * mlankhorst wonders why he has nvidia-common on armhf :x
[21:45] <Sarvatt> mlankhorst: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/977245
[21:45] <Sarvatt> its renamed ubuntu-drivers-common now because it hasn't been nvidia specific in a long time :)