[00:01] chrisccoulson: Ping. [00:02] after setting up gimp for the wife i can really understand why that person wanted multiple stylus support back [00:03] heyo RAOF! nouveau needs your loving if you get around to it, 2.6.34 is in maverick, libdrm is updated without the abi reverts too [00:04] Sarvatt: Yeah, I saw that. Thanks! [00:05] Sarvatt: I also see that you're working on xserver master? We'll want to follow that moderately closely for Maverick - we should start shipping pre-releases in the archive once 1.9 branches off, I think. [00:06] don't know what you want to do with nouveau so I didn't touch it, could just sync it with debian since they fixed it up to build like the rest of the X packages but it's a big change [00:07] Oh, libdrm-nouveau broke ABI, didn't it (without bumping SONAME, bad dogs!). That's why x-x-v-nouveau's broken. [00:07] ? [00:08] 1.8.1 is merged and builds in git, running into a few dependency problems with it though (it dragged in nvidia-common and x-x-v-radeonhd for some reason..?) [00:08] yeah, we had it broken anyway since there was a 2.6.34 kernel in maverick that didn't work with the lucid userspace anyway [00:09] it's like the new dependency system pulls in anything providing xserver-xorg-video-7 or something, I dunno [00:10] That seems odd. [00:13] gradually hitting more and more roadblocks building packages against debian git since they are using the ${xviddriver:Depends} stuff :( [00:15] error: xserver-xorg-dev >= 1.7.6.901 needs to be installed [00:15] make: *** [serverabi] Error 1 [00:15] (xserver-xorg-dev 1.8.1 is installed there..) [00:16] :( [00:26] ugh, need to be sure to cc: stable@kernel.org next time I submit a patch obviously meant for stable, trying to figure out how to submit http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8d06a1e1e9c69244f08beb7d17146483f9dcd120 [00:43] btw RAOF - http://pastebin.com/7vjm2Stt [00:43] (just saw you updated the non root X blueprint) [00:44] non root vesa patch from meego [00:46] matches[i++]. I love statements with side-effects. [00:47] sheesh meego has a rediculious amount of dri2/glx backports to server 1.8 branch too, everyones just bypassing upstream [00:48] Well, wasn't dri2 moderately broken on the 1.8 branch?_ [00:48] Still... [00:49] + } else if ((dev->device_id == 0x8108) || (dev->device_id == 0x8109) || (dev->device_id == 0x4102)) { [00:49] + driverList[0] = "psb"; [00:49] + driverList[1] = "pvr"; [00:49] i guess 4102 = moorestown and the driver name is pvr.. [00:52] Fun! More crazy! [01:05] anyone mind if I delete this patch? it's pointless unless i'm missing something - http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=blob;f=debian/patches/184_virtual_devices_autodetect.patch;h=2b03e929dfc85329eec0be851800fb5ccd32c166;hb=refs/heads/ubuntu [01:06] probably made sense when we had pci.id files and cirrus matched 1234 [01:06] it's not doing anything though, it's not a cirrus pci id anyway and already defaults to vesa [01:09] 1234 looks like it's the QEMU stdvga device and not cirrus, the cirrus emulated device actually has a cirrus pci id (0x1013) [01:10] if you boot with a 1234 pci id device without that patch you get vesa and fbdev, if you boot it with that patch you get vesa vesa and fbdev right? [01:12] Sarvatt: From that context, yes. This seems like something that would be trivial to test to make sure, though. [01:12] :) [01:13] yeah looking into how to set up qemu to test it [01:14] about to extract all patches from meego's and put them on my server since they dont have any kind of VCS.. [01:16] they have a vesa patch to remove DGA usage that i'm not sure if its needed for non root as well [01:18] It clearly isn't - the first patch you posted was “don't fall back to VESA if we're not root”. [01:18] they renamed -cirrus to -kvm too :D [01:19] I don't think we'll actually need that one - the plan was to start X as root, check whether we actually need it, and drop privs if we don't. Which means we'll only be dropping privs in the presence of KMS, which means vesa's already stuffed. [01:35] haven't seen this before either, xf86-input-mrstouch for moorestown. says its a combination of plpevtch and evtouch 0.8.8 [01:36] been around for 3 years...? [01:37] i've never even heard of plpevtch before, it's a fork of evdev [01:49] Doesn't evdev basically just forward kernel events up? [01:49] * RAOF hasn't looked at it in any depth. [01:59] RAOF: were you at the X on ARM session? [02:00] there were two, he was at one, I was at the other [02:02] did you catch what the plans are regarding gles/EGL and different clutter backends and such? [02:03] i know we need to start packaging up libEGL for the wayland stuff anyway which I can do in the next few days [02:20] http://www.imgtec.com/powervr/insider/powervr-vframe.asp - woohoo [02:23] Sarvatt: Yeah, we need to start packaging libegl. [02:25] hmmmmm, EGL_NOKIA_texture_from_pixmap, haven't seen that before [02:25] That makes it the second EGL_*_texture_from_pixmap I've seen. [02:27] and EGL_OES_image_pixmap [02:29] oh is libegl required for wayland? that might be the last piece I'm missing [02:30] don't recall that being discussed in the meeting I attended, tho it could have gotten lost amongst all the hand waving [02:30] That was the point of krh's mesa branch, wasn't it? [02:31] * RAOF is pretty jet-lagged, so DISCLAIMER: Sense-making is not guaranteed. [02:32] I was working from the dx team sprint notes [02:32] * bryceh doublechecks [02:32] well got a list of what my phone supports on android, http://paste.ubuntu.com/435264/ [02:33] https://wiki.canonical.com/DesktopExperienceTeam/Wayland [02:33] weird, no mention of libegl, but I'm definitely getting errors about it [02:35] Sarvatt, ok if you don't get to packaging libegl, I'll take care of it when some of my launchpad work's done [02:36] yuck, looks like clutter's egl backend is limited to one application at a time, and only works with tslib for input [02:36] bryceh: how old a snapshot are you using? [02:37] he's been doing EGL stuff in mesa like mad for the past 2-3 months [02:37] the mesa snapshot is pretty recent [02:38] the wayland snapshot is from March; seems he's not been doing much there [02:38] I'd guess that you could try master; there's a lot of egl commits happening in there. [02:40] bryceh: packaging names are the only things that have stopped me from doing it for months, i dont want to pick something that isn't going to be used later when debian picks it up :D [02:41] Sarvatt: This sounds like a job for Debain Experimental™. [02:41] except debian experimental seems to be the new unstable now until squeeze is released :D [02:42] But with even less of an implicit support guarantee. [02:43] libegl1-mesa? [02:43] Sarvatt, maybe you could pop a Q on debian-x@, or ask jcristau for a quick recommendation? [02:43] Yeah. That's what I was going to suggest. [02:46] I'd also like to ensure that we don't duplicate work on xserver & mesa; we're going to be pretty aggressive on the version front, and I'm going to ask whether working in the debian-experimental branch + syncing would make the XSF happy. [02:46] well I still need to wrap my head around everything that builds, i'm not sure what the arm people are planning on doing too, like are they going to make libgles-omap libgles-sgx and such with all of the proprietary blob crap and headers for those in -dev packages? [02:47] Frankly I'm not totally clear on the ARM driver stack; it seems like a den of madness. [02:47] for sure [02:49] libegl is no big deal to add, its the libgles stuff i'm trying to figure out [02:50] RAOF, btw in the past a couple times following UDS I'd post to debian-x@ briefly outlining the blueprints that got decided at uds, to solicit debian's feedback on them and make them aware in case they wanted to collaborate [02:52] usually I'd do it after I'd finished drafting the blueprints, but in hindsight it's probably better to do it before the blueprints have been written, else it might require extra work rewriting stuff. [02:52] one package with the libs and egl_dri2.so, one package with the dev stuff (just 4 headers and a libEGL.so), another package with the demos [02:53] dont know if we need to put libEGL in /usr/lib/mesa though, if the proprietary arm drivers use a different libEGL? [02:53] Sarvatt, did the egl_dri2.so, etc. bits use to live in mesa? that could explain the discrepancy [02:54] bryceh: That's a good idea. I'll prioritise getting that mail out a bit. [02:54] RAOF, starting to see why I got into using gtg so much? ;-) [02:55] bryceh: they still do [02:56] Sarvatt, oh... what does libegl provide then? [02:56] oh they moved to mesa after you packaged it a long time ago [02:56] bryceh: :) [02:57] * Sarvatt looks at the ppa to see whats n there [02:57] digging up your old ppa [02:58] libeagle [02:59] that was dropped and everything moved to mesa [03:00] no, I'm referring to this: [03:00] Sarvatt: Yeah, we need to start packaging libegl. [03:00] we never shipped any egl stuff in mesa [03:02] if we need to ship libegl in /usr/lib/mesa its not really applicable to debian [03:04] argh [03:06] the proprietary sdk's do ship egl headers with the same names as the mesa ones and they are different [03:07] oh nope the same reference ones, phew === verbalshadow_ is now known as verbalshadow [03:11] they do have their own libEGL though :( [03:26] almost done with libEGL, i'll finish it by tomorrow probably [03:38] http://sarvatt.com/downloads/patches/egl.patch [03:38] what i got so far [03:38] oh thats missing some stuff [03:39] there we go [03:41] chromiumos is using gentoo now instead of ubuntu? tried it out earlier and was a sad panda [03:44] * RAOF heads out for a walk to lunch. [04:07] interesting.. looking through the moblin psb kernel source - http://paste.ubuntu.com/435292/ [04:16] xf86-video-psb-5.1.0.0112-1.3.moblin2.i586.rpm too [04:24] Ah, so they're actually using gallium for their proprietary driver now? I understand that was one of the goals. [04:28] this moblin psb isn't using a special libdrm, and uses http://cgit.freedesktop.org/mesa/libwsbm/ that i never heard of before, it's just basic 2D without the gallium component that never made it and they support IGED out of the box [04:29] also the mrst patches from meego that apply to 2.6.34 will work for it [04:29] interesting [04:30] this is all open source 2D thats not vesa though, wonder why they never pushed this anywhere [04:33] doesnt look like it even needs any kind of firmware [04:38] xpsb-glx will work with it too [04:38] for 3D [04:40] as long as you dont pass --enable-dri2 when building the ddx [07:32] Hi, i have got some trouble with fpit touchscreen driver. [07:33] looking at the source there seems to be a typo in the code [07:34] concerning initialization of the driver. changed it, recompiled & works for me [07:35] please take a look at:http://pastebin.com/pZC3c16Q [07:35] line 60, the changed code. [07:35] oc13: Have you filed a bug? [07:35] no corrected it [07:43] Could you produce a patch? It's not obvious what is wrong. Also, file a bug so that we know that there's something wrong, and attach the patch so that we know we can easily fix it :) [07:45] It's also not obvious what the symptoms of the problem you're fixing is :) [07:50] submitted a bug report: Bug #582123 [07:50] Launchpad bug 582123 in launchpad "xorg-input-fpit gets wrongly initialized" [Undecided,New] https://launchpad.net/bugs/582123 [07:50] Thanks. [08:01] oc13: Hm. Where are you getting that driver from? That code doesn't match what we've got in the xserver-xorg-input-fpit package. [08:11] i checked out from git [08:14] Ah. You probably want to post a patch to the appropriate driver mailing list, then. [08:14] Whatever bug you're running into doesn't (yet!) affect Ubuntu. [08:16] xorg-devel@ is probably the best match [08:16] If you're not familiar with the process of submitting a patch, we can probably help you. [08:17] i will try it. [08:21] I can send the patch and add a reported-by: [08:33] ok, submitted a patch to xorg [08:33] heh, ok [08:34] argh, is it me or do lucid livecd's totally not boot with -vga std? [08:34] in qemu [08:35] maybe its just being completely silent and not actually dead, took 30 minutes to boot with cirrus :D [08:35] * Sarvatt kicks his atom cpu [08:35] git status: changes to be committed... no unchanged files. git commit: “It is not possible to commit because you have unmerged files”. [08:35] I hate you, git. [08:36] git diff show anything? [08:36] aahh 10 minutes later I see the splash, phew [08:36] Hah. It does. Changes in .gitignore, which git has erroneously decided has been moved to debian/clean [08:38] Ah. And now .gitignore has an empty diff, but still counts as changed. Superb! [08:38] oc13: probably stuck in the queue [08:38] git reset --hard [08:40] this is neat, i didnt know qemu had a vmware graphics option now, goodbye cirrus [08:42] if i can get this working it'll give me a good excuse to get the gallium vmwgfx stuff going [08:42] Which means you'll want libkms? [08:43] yeah which still needs libdrm to compile, yay [08:43] already packaged up libkms [08:44] It's not in 2.4.20-2ubuntu1, though, is it? I didn't notice it at least. [08:44] nah did it on xorg-edgers but backed it out since it needed libdrm to compile [08:45] But it's in the same source tree as libdrm? How can it need libdrm to compile? [08:45] yeah, crazy aint it? [08:45] Like a frikkin cut snake. [08:48] you had a patch for libkms to compile against the source instead of the system libdrm at one point didn't you? [08:48] I certainly patched *something* - it may well have been libkms. [08:49] I don't think it would have been for that, though. [08:49] it was back when libkms first started being enabled by default [08:49] have you guys been getting reports of the nvidia current driver breaking peoples x server ? [08:50] I certainly filed that upstream; I don't know if it got applied. [08:52] eagles0513875: I haven't seen such, but UDS didn't leave me with a lot of bug browsing time. [08:52] RAOF: i have no x or i can start it but with rather cruddy looking graphics [08:52] and also having problems with apt and package dependencies but thats a different issue [08:52] guess i saw it on the lists somewhere [08:53] RAOF: i think the mailing list has somethign floating around if i saw right but then again i didnt bother to read as it wasnt affecting me [08:53] hah RAOF! [08:53] http://bugs.freedesktop.org/show_bug.cgi?id=26852 [08:53] Freedesktop bug 26852 in libdrm "Build libkms against in-tree xf86drm.h" [Normal,New] [08:53] you really did forget :) [08:53] J'accuse jetlag! [08:54] RAOF: or Sarvatt eitherone of you can help [08:54] i dont know what you did to get into the broken state [08:55] but on reboot i get this error mess saying im running in low graphics mode drm failed to open device and failed ot initialize glx extension compatible nvidia x driver not found [08:55] whats not making sense [08:55] i can get on to kde in low graphics mode [08:55] i check jockey and it is saying its activate [08:55] guessing you either installed from nvidia.com or a screwed up PPA package at some point and messed up the package manager [08:55] runnign apt-cache policy nvidia-current shows [08:55] Sarvatt: i didnt use a ppa and didnt install from the nvidia website [08:55] And without the relevant logs (dmesg + /var/log/Xorg.0.log) we can't really say anything useful. [08:55] everythign from ubuntu repos [08:56] let me try paste it hold on [08:56] do you have a bug? [08:56] with the logs we can look at? [08:56] no i dont [08:56] as this only happened this morning after a reboot [08:56] it was working up until that point [08:56] pastebin your /var/log/jockey.log please [08:56] gonna try if i can get into a console [08:58] this is even better :9 [08:58] :( [09:00] !paste [09:00] For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://tinyurl.com/imagebin | !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [09:00] if it's saying drm failed to open device that means you dont have nvidia-current installed though [09:01] http://paste.ubuntu.com/435381 <--dmesg [09:02] http://paste.ubuntu.com/435383 <---Xorg.0.log [09:02] eagles0513875: whats your /etc/X11/xorg.conf? [09:03] ah that works, looking [09:03] you dont have an xorg.conf [09:03] eagles0513875: just run sudo nvidia-xconfig [09:04] why all of a sudden wouldnt i have one [09:05] ok Sarvattshould i reboot [09:05] i have no idea, something wonky with jockey, might be able to tell from your /var/log/jockey.log [09:05] yeah [09:05] give me sec [09:05] http://paste.ubuntu.com/435387 <-----jockey log [09:05] gonna reboot [09:05] did you install nvidia-current with a package manager instead of jockey? that doesnt create the xorg.conf if so [09:06] no i havent [09:06] and atm apt is messed up :( [09:06] well that fixed it [09:06] O_o [09:07] ...madwifi? [09:07] ? [09:07] did you upgrade from hardy maybe? [09:07] is this the official ubuntu x channel [09:07] Sarvatt: no [09:07] clean install of lucid [09:07] had to use ubuntu server though [09:07] as i need gpt to be able to use my 2tb hdd [09:08] how did you say you installed nvidia-current again? [09:08] jockey [09:08] i dont see that in that log :( [09:09] rereading the scrollback.. [09:09] O_O [09:12] so you activated nvidia-current in jockey, rebooted, then this started? [09:12] my install has been working for about 2 weeks or so [09:12] the installation in jockey failed [09:12] i just rebooted to day and it happened [09:13] tseliot: ? [09:13] nvidia-current was working and just stopped with no intervention this morning? [09:13] DEBUG: nvidia_173 is not the alternative in use [09:13] tseliot: im using the latest one [09:13] the one that jockey recommended [09:14] yes, but somehow it failed to set the correct alternative [09:15] tseliot: should i uninstall nvidia current and reinstall it [09:15] the alternatives were fine going by his xorg.0.log because it wouldn't have loaded the nvidia libglx [09:15] eagles0513875: what's the output of "update-alternatives --display gl_conf" ? [09:15] brb really fast [09:17] nouveau was properly blacklisted too, it only loaded drm while trying to load nouveau and that failed so it fell back to vesa [09:17] then maybe the jockey log file shows the uninstallation process of nvidia [09:17] as I can see: [09:17] got handler xorg:nvidia_current([NvidiaDriverCurrent, nonfree, enabled] NVIDIA accelerated graphics driver) [09:18] what could have deleted his xorg.conf? [09:18] and then a few lins below [09:18] got handler xorg:nvidia_173([NvidiaDriver173, nonfree, disabled] NVIDIA accelerated graphics driver) [09:18] so an uninstallation would explain it [09:18] uninstalling the driver means removing xorg.conf if none was available before the installation from jockey [09:19] uninstallation of what? [09:19] of the nvidia driver [09:19] hey wait a sec [09:19] because he had the nvidia-current kernel module loading and the alternatives had to be right because it loaded the nvidia libglx [09:20] NvidiaDriverCurrent and NvidiaDriver173 are not the same... [09:20] replacing coffee with tea is not working well for me :-/ [09:20] so that's correct [09:22] Hi, I'm trying out the xorg-edgers ppa, but it seems to fail on boot. According to the Xorg.0.log, it's failing to load the fbdev module [09:22] Sarvatt: maybe just uninstalling and reinstalling nvidia from jockey will do it [09:23] ripps: xorg-edgers not xorg-testing right? [09:23] ripps: sudo apt-get install xserver-xorg-video-all if so, you must have let it get removed at some point [09:24] tseliot: what was that command you want me to run [09:25] eagles0513875: as I said, maybe just uninstalling and reinstalling nvidia from jockey will do it. Please try [09:25] ok [09:25] xserver-xorg-video-fbdev - 1:0.4.2+git20100422.7ec9d466-0ubuntu0sarvatt is in xorg-edgers and compiled against xserver 1.8 [09:25] its running fine since i added an xorg.conf file [09:25] Sarvatt: okay, I installed that, but just so you know, it failed to load fbdev_drv.so because of a requirement mismatch [09:26] whats the version on your xserver-xorg-video-fbdev? [09:26] tseliot: its uninstalling atm [09:26] Sarvatt: huh... it's using the main lucid one, not xorg-edgers. [09:27] eagles0513875: delete your /etc/X11/xorg.conf too before you reinstall [09:27] ok sar [09:27] Sarvatt: [09:27] eagles0513875: and after you install, please post your xorg.conf [09:28] ok tseliot [09:28] it should make the right one when you do it that time, it's still a mystery as to what deleted it randomly :( [09:28] Sarvatt: I think I figured it out, I needed to run a full-update, it wasn't pulling in all the video drivers [09:28] eagles0513875: and the output of "update-alternatives --display gl_conf" [09:28] well hell this isnt good [09:28] ripps: yea sudo apt-get dist-upgrade [09:29] jockey isnt starting and my apt is messed up atm :( [09:29] should i just do a clean install [09:29] and go from there [09:29] be back in a reboot [09:29] eagles0513875: did you already remove nvidia-current? [09:29] Sarvatt: [09:29] ya [09:30] wait there it goes [09:30] open a terminal and sudo jockey-text -e xorg:nvidia_current [09:30] ah ok [09:30] im getting an error when trying to remove the driver [09:30] systemError: installArchives() failed [09:30] i think i managed to screw up my install royally [09:32] * eagles0513875 is gonna reinstall [09:34] eagles0513875: do you have a package manager running? [09:34] synaptic? [09:34] cant have that open at the same time as jockey [09:35] Sarvatt: no i went to instal tex live and it has unmet dependencies and its kinda got me locked outa installing anything [09:35] thats usually what that error means [09:35] hummm [09:35] sudo apt-get -f install? [09:35] yeah its stuck waiting for you to resolve that problem first [09:35] Sarvatt: tried that still nothing [09:35] how can i resolve it sudo apt-get -f install doesnt work neither does dpkg --configure -a [09:36] whats it say when you do a sudo apt-get dist-upgrade? [09:36] packages on hold? [09:36] try installing each one individually to see where the problem is [09:37] says that this dependency is missing but it wont be installed [09:37] and even individually says the same thing about unmet dependencies [09:37] do you have -proposed enabled? [09:37] ya === wgrant_ is now known as wgrant [09:38] yah looks like a problem with packages in proposed right now, hmm [09:38] can you just purge all of the ones waiting? [09:38] Sarvatt: Awesome everythings working great, XV performance in mplayer is outstanding [09:39] Sarvatt: tried purging it just mentioned there are unmet dependencies [09:39] its not recommended to enable proposed globally for that exact reason btw [09:39] ya i know actually this reinstall i wont [09:40] especially since i need to do work on this desktop [09:41] just gotta find what you have installed that is depending on those things that it cant fulfill [09:41] Sarvatt: whats even more annoying is it took me bout 2 weeks of swearing and headaches to find out that gpt partition table isnt compiled into main stream ubuntu kernel [09:41] sudo apt-get purge texlive-binaries libkpathsea5 libkpathsea-dev ? [09:41] err wait [09:41] Sarvatt: im gonna do a clean install [09:43] ty for reminding me i need to get some stuff i downloaded off u tube off of there hehe [09:43] Sarvatt: gave me an idea ctually [09:44] can you paste the output after you sudo apt-get dist-upgrade? [09:44] really its not something you have to reinstall over, knowing how to recover from that is extremely handy and once you do it once you wont forget :) [09:44] Sarvatt: i might have solved it [09:45] sudo apt-get purge texlive* [09:45] all of texlive gone for now a [09:45] and im gonna disable proposed [09:45] that works too :) [09:46] if you needed it you could disable proposed, sudo apt-get upgrade and then sudo apt-get install package1/lucid package2/lucid..etc to downgrade back to the lucid versions [09:46] and also strangly enough it started up just fine [09:47] yeah it definitely sounds like something decided to delete your xorg.conf out of the blue, maybe it even got corrupted and it was gone after a fsck at boot [09:47] tseliot: iand Sarvatt start up just fine with out an xorg.conf and without the driver [09:48] Sarvatt: i removed it as well as the driver and it starts up just fine without the xorg.conf [09:48] ah you're using nouveau then [09:48] its supposed to work that way [09:48] ahhh ok [09:48] now to install the driver [09:48] should i do it form jockey or commandline [09:48] right [09:48] its just screwed up if you have the binary driver installed with no xorg.conf [09:49] let me try with binary [09:49] driver now [09:49] jockey, yeah [09:50] restarting now [09:51] hmmm... weird, mplayer using opengl video output renders ass subs incorrectly... perhaps it's because of the mesa/xserver version. Let me try a mplayer rebuild using xorg-edgers as a ppa dependency. [09:51] it booted up just fine wiht the driver [09:52] woohoo :) [09:53] \o/ [09:57] i'm putting money on it just having been corrupted and removed during a fsck it since it happened at boot [09:57] ripps: define incorrectly? :D [09:58] timed wrong? wrong fonts? graphics glitches? [09:58] ripps: some letters have a weird graphic glitches and artifacts in over or in place of a few letters [09:58] Sarvatt: ^ [09:59] Don't see the glitches with XV though. [09:59] work any better if you sudo apt-get install libgl1-mesa-dri-gallium? :) [10:00] are you using mutter? [10:00] no [10:01] * ripps is d/l gallium dri now... [10:02] you had a x1400 mobility or something close to that didnt you? [10:03] Sarvatt: older, 9600 pro [10:03] rv350 chipset [10:04] oh dont think that works with whats in libgl1-mesa-dri-gallium :( [10:04] only r300g in there [10:04] Sarvatt: rv350 is r300 [10:04] well you'll know if you install it and glxinfo :) [10:04] *essentially* [10:05] * ripps is restarting X now [10:05] oh i was thinking it was an r200 [10:05] darn rv's [10:06] was off a generation [10:06] RV250 = r100 [10:06] OpenGL renderer string: Gallium 0.4 on RV350 [10:06] :) [10:07] err RS250=R100, argh :) [10:07] tseliot: and Sarvatt ty for your help [10:07] RS350=R200 too ahh [10:08] np [10:08] no worries eagles0513875, hope it doesn't happen again since we dont know what caused it :) [10:08] Sarvatt: ya i hope so too [10:09] if i can digup the mention of nvidia issues on the mailing list i can pastebin for you guys to take a look at [10:09] ah yeah it was RS350=R200 that I was thinking of, I have an RS350 [10:09] Sarvatt: okay, much better now. However, it seems that GL video playback has taken a performance hit [10:11] oop, compiz suddenly crashed [10:11] restarted okay though [10:12] okay, there are still a few ass rendering issues. Some slight graphical hiccups with punctuation (,'.) and the dot in i's. [10:13] (performance wasn't hit that much, my awn was making a signal that was soaking a few cpu cycles) [10:13] and it works fine with the normal lucid packages? [10:13] yes [10:14] I'm not using a normal mplayer btw, I'm using the mplayer-build git repo to build ffmpeg-mt mplayer packages [10:15] I rebuilt it with xorg-edgers -dev files though [10:15]