[00:08] superm1: hmm your nvidia 190 drivers dont pull in libvdpau for me [00:09] ah maybe because Depends: nvidia-190-kernel-source (>= 190.42), libvdpau, x11-common (>= 1:7.0.0), ${shlibs:Depends} when the package is libvdpau1 [00:09] Sarvatt, it's possible i didn't add that depends (because mythtv has it inheritently when it build-depends against something with vdpau support) [00:10] might have been libvdpau in your 0.2 version and changed to libvdpau1 in this 0.3 i'm guessing [00:16] its libvdpau1 in the 0.2 in all your PPAs too incase you want to change that in the nvidia-glx-190 depends next time you upload to one without mythtv [00:17] ....not that there is one without mythtv now that i look :D [00:20] thanks for all of the help, it's working great now [00:29] hmm, updating the nvidia-glx-190 package to Depend on libvdpau1 didn't pull in libvdpau on the update either [00:45] debian/control.in was missing the libvdpau depends completely was the problem [00:48] The following NEW packages will be installed: libvdpau1 The following packages will be upgraded: nvidia-190-kernel-source nvidia-glx-190 [00:48] phew thats more like it [00:52] now i notice no modalias getting installed :D [01:56] nvidia-common dependencies need to be adjusted for that [03:04] i just made it provide nvidia-185-modaliases for now === freeflyi1g is now known as freeflying [06:46] nvidia-settings 190.42 needed a patch to compile against the x11proto-xf86vidmode-dev headers instead of the libxxf86vm-dev ones, errors trying to build against the lib's after the xorg 7.5 split. http://bugs.gentoo.org/attachment.cgi?id=208926 [08:57] Sarvatt, is there a fix specific to our problem in this new libdrm? ([drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged) [16:27] Duke`: nope, pretty sure its a kernel problem. check out the "enable memory self refresh" patch threads on the intel-gfx mailing list. the new libdrm is just overwriting the headers in linux-libc-dev and its the same as the one before it otherwise [16:28] Duke`: what kernel are you using? I haven't had it happen on the ubuntu 2.6.32 kernel yet [16:28] of course suspend/resume is broken on this and not on the drm-next kernels, flickering and eventually freezing on a solid color after resume [16:42] memory self refresh? [16:42] what's that do? [16:47] Sarvatt, i use the 2.6.32 [16:48] my intel seems to make X eat the cpu (stock lucid) [16:55] anything special about it or is it just a stock install? [16:55] gonna check if mine does too [16:56] haven't tried the stock environment in a few weeks [16:56] KMS doesn't work unless I blacklist vga16fb though on 2.6.32-7 [17:00] nothing special, 965GM. booting fails ~every second time, evdev crashes for some reason and falls back to vesa (which doesn't work at all due to KMS) [17:00] I'll merge new evdev & xserver tomorrow [17:00] and mesa (includes r600_dri.so) [17:02] does it happen with compiz disabled too? [17:03] haven't tried [17:06] sounds like a problem hyperair (i think?) had with 965 back when edgers had mesa 7.6/libdrm 2.4.14 is why i was asking [17:07] I've had this before iirc [17:07] happens after the first resume I guess [17:08] /proc/dri/0/gem_objects was growing huge and and x was using 100% cpu i think [17:10] size is 0 [17:11] now thats odd.. [17:13] reverting back to stock lucid now but i doubt it'll be the same on my 945 [17:14] hmm The following packages are BROKEN: xserver-xorg-core [17:15] oh because i have a newer wacom in edgers and theres no installable wacom in the archive [17:16] sounds like yer using vesa though if theres nothing in gem_objects? [17:17] ah joystick is broken in lucid too [17:18] oops i have some newer bits in a local package archive, no wonder ppa-purge didnt work right [17:19] compiz works, so doubt it's vesa :) [17:20] do you have a /proc/dri/1 ? [17:21] Sarvatt: which issue? [17:21] X using alot of CPU like 6 months ago [17:21] Sarvatt: i had two issues: one was the crazy memory leak that drove me nuts, and the other was the weird re-drawing issue. [17:21] X using a lot of CPU... [17:21] no i don't think i had that [17:22] i just had increased swapping activity [17:22] until it took up all my resources [17:22] if X got oom killed in the fray, then well and good, otherwise i restart [17:22] rebooting to stock lucid to see how things are here [17:22] or i preemtively log out and kill X before it can kill the rest of my computer [17:23] anyway the issue was a kernel thing [17:23] if lucid uses .32, it shouldn't see such an issue [17:23] no wait, there was a patch involved in mesa i think.. [17:23] I won't worry too much about it, yet [17:24] no wait, it was definitely the kernel. i remember sarvatt giving me a custom compiled kernel and that solved all my issues [17:30] thats strange, 4 reboots, X only started twice [17:30] the other 2 I got failsafe with vesa all garbled [17:30] ouch [17:31] * hyperair makes note not to upgrade to lucid until all's clear [17:31] Sarvatt: sounds like my problem. check the gdm log [17:33] cant find any gdm logs from the failed boots hmm [17:34] its only got the 2 successful ones then edgers ones, failsafe doesnt have anything in it [17:35] when it failed x tried to start on vt2, dont know if thats normal for failsafe [17:39] wonder why it fails like that with the lucid packages and not edgers though [17:42] do you have plymouth installed tjaalton? [17:42] yep [17:42] me too [17:43] theres some video trickery in there, gonna try removing it [17:52] what the heck, 4 boots again, 2 failures again [17:56] got an orphaned /etc/init/usplash.conf for some reason [18:13] 164_trap-aspect-ratios.patch is the only patch we're dropping in edgers vs lucids xserver [18:15] * Sarvatt wonders how this edid caching works in the ubuntu kernel [18:17] its happening every other boot reliably though for some reason [18:18] going to try a stock 2.6.32 just to rule out any kind of patches [18:19] * hyperair uses 2.6.32-zen0 [18:42] 10 reboots on a stock 2.6.32 kernel from the mainline thing and no errors, pretty darn safe to say its a ubuntu kernel patch messing it up [18:49] only thing ubuntu specific that stands sticks out is http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=c5155725948be57010c4a558a1b9c5ddefb864c3 [18:55] hrm, my trackpad isn't showing up in "xinput list" in lucid [18:57] that commit isnt even in 2.6.32-7 thats having problems so definitely not that then