/srv/irclogs.ubuntu.com/2010/05/23/#ubuntu-x.txt

Sarvattjcristau: yeah I sent the disable FBC commit to .33 stable earlier this week but not .32 yet since it needs changing00:56
Sarvatti'm not sure if http://sarvatt.com/downloads/patches/disable_fbc.32.patch is correct and haven't had time to test it00:58
Sarvatt(for .32)00:58
SarvattGM45 has FBC problems on .32 and .33 too though, we're disabling it there as well soon :(01:02
Sarvattscreen flicker for GM45, getting stuck on a single color screen for 915-94501:02
jcristauoh thanks for doing this01:12
jcristaui'm not too bothered about .32 at this point01:12
bjsniderSarvatt, did you get the nvidia 256 driver into x-updates?01:12
jcristauhaven't had any issues on my gm45, but apparently some guy on bugs.debian.org/580601 does01:13
Sarvattbjsnider: nope needs adjustments to the .install.in's to install all of the headers right, if you want to do it everything but that is in my nouveau ppa i linked earlier01:14
bjsniderwha?01:14
bjsnideri didn't understand that01:14
bjsnideri just finished earlier packaging it for pre-lucid distros, and it was a pain01:15
Sarvattjcristau: yeah that guy is has the same problem as all of these - https://bugs.launchpad.net/bugs/53864801:15
Sarvattbjsnider: well the packaging tries to install things from the old locations, everything is in the root directory after you extract it now01:16
Sarvattall the headers in one place, need to manually put them in the right places in the install files01:16
jcristauSarvatt: is there a fdo or korg bug i can link to?01:16
Sarvattthere's one on that bug where I upstreamed it but they haven't said anything on there01:16
jcristausigh01:16
bjsniderSarvatt, how about i take care of it here and send you the updated packaging scripts?01:17
jcristauthanks01:17
Sarvattloading it up to link it01:17
Sarvatthttp://bugs.freedesktop.org/show_bug.cgi?id=2758901:17
Sarvattwe're dropping FBC on that pci id (which happens to be the only GM45 anyway) though to work around it, odd that you dont experience it01:18
jcristaua month old..01:18
Sarvattit took RAOF a few days to even see the flicker once on his01:18
Sarvattbut for some people its really bad, maybe dual channel/single channel memory configuration related I dunno01:19
Sarvattwould be nice of FBC was a module option that defaulted to off at this point :)01:20
Sarvattbjsnider: send me a link to the PPA or whatever, i'll copy it over :)01:21
Sarvattthanks a million if you do it btw01:21
bjsnideri thought i'd just build it in pbuilder here and then email the scripts to you as a tarball.01:22
Sarvattthat works if its easier for you, sarvatt@ubuntu.com01:23
bjsnidervery well01:24
bjsnideroh my god this is a nightmare02:38
bjsnidernvidia did this just to screw us over02:39
bjsniderthe whole directory structure of the -dev package has been lost. what should i do, just throw all of the cuda, cl, gl, and vdpau headers into one directory?02:42
bjsnideror recreate the existing structure in the install script?02:43
bjsniderthat's what i'll do. screw them, too02:44
Sarvattbjsnider: yeah I said screw it and stopped when I saw that too :D03:08
Sarvattits just like 10 headers though, just add each one to a seperate line in the -dev.install.in and have a second section after each pointing to usr/include/CL and stuff03:10
Sarvattnot sure, something like #DIRNAME#/cl.h                       #INCLUDEDIR#/#DRIVERNAME#/usr/include/CL/cl.h?03:12
Sarvatt(for each one)03:12
Sarvattoh it installed everything to /usr/include/nvidia-current/foo/bar.h before03:13
Sarvattso yep that should work? just gotta get the list of where everything goes from the current from the current nvidia-current-dev03:13
Sarvatti thought it installed stuff straight into /usr/include/ hmm..03:14
Sarvattanyway thats just 11 lines like i pasted in the nvidia-current-dev.install.in, i'll try that out03:15
Sarvattoops meant #DIRNAME#/cl.h                       #INCLUDEDIR#/#DRIVERNAME#/usr/include/CL03:16
Sarvatthttp://pastebin.com/Bv5fcMNb03:20
Sarvattlike that03:20
Sarvattgotta fakeroot debian/rules regen-from-templates after of course03:20
bjsnideri'm testing now03:25
bjsniderit worked hahaha03:28
bjsniderSarvatt, but the headers are only in that structure because that's how nvidia originally packaged them. if they think the headers don't need that kind of specific structure then i guess they don't03:38
bjsnidervga_arbiter_workaround.patch has to be disabled as it will not apply03:51
Sarvattthey do need that structure, nvidia-installer handles it now03:56
Sarvattthey just shoved everything in one directory :(03:57
bjsniderok, i have it your way now except a bit shorter with wildcards03:57
Sarvattguess XF86Config.sample is gone04:00
bjsnideryep04:04
bjsniderok, i just successfully installed the module04:04
bjsniderso i guess the scripts i've got are appropriate04:04
bjsnideri'll pack them and email them immediately04:04
bjsnideror maybe i should reboot first?04:05
bjsniderSarvatt, i have emailed the scripts to you04:07
Sarvattthink i've got it going too, checking the contents of every deb just incase and i'll compare to yours after04:13
Sarvattonly diff in our rules - http://paste.ubuntu.com/438134/04:21
Sarvattlooks like thats the only change lol04:22
Sarvattincludes are screwed up04:25
Sarvattneeds to go to /usr/include/nvidia-current/CL and stuff, got them in /usr/include/nvidia-current/usr/include/CL whoops04:26
Sarvatt#INCLUDEDIR#/#DRIVERNAME#/CL instead of #INCLUDEDIR#/#DRIVERNAME#/usr/include/CL04:28
bjsnideri changed the nv directory to kernel because of the change in nvidia's file obviously04:29
bjsnideri can't really think of any good reason for them to change the locations like they did04:29
Bernardogood morning04:30
BernardoSarvatt: can you point me where to find the meego psb drivers? Do I need to clone their whole git repo? I was looking through gitorious last night and couldn't find them04:31
Sarvattwhat meego psb drivers?04:33
Sarvattthey are internal only still04:33
Sarvattthere's the kernel driver in the meego kernel-source git repo though04:33
Sarvattthere are also moblin ones with the 5.1 versioning in the moblin repos04:34
Sarvattthe meego ones are 5.3 and work with moorestown, meego has 5.1 with the appropriate kernel source in the src rpm (it's called like 2.6.32-msrt-rollup.patch I think)04:35
Sarvattthe ones in the latest moblin release from january were the ones you probably caught me talking about that were 2D only (3D needs gallium)04:36
Bernardook, thanks. 04:37
BernardoSo those won't work with xpsb-glx?04:37
Bernardowe could live a little more without 3D, if at least xv works04:39
BernardoI'll look into moblin then, since I am making no progress with freedesktop bug 2807704:40
Sarvattbjsnider: tried the drivers out yet?04:52
Sarvatti just uploaded them to x-updates since the debs look correct, wont be able to try for a few hours until the wife passes out05:01
* Bernardo wonders why moblin devs had to hack the struct backlight_device05:26
=== Bernardo is now known as Bernardo|away
Bernardo|awayhi lucazade11:47
lucazadehi Bernardo11:48
=== Bernardo|away is now known as Bernardo
Bernardothe mobline guys decision of including the module on the kernel sources is giving me a lot of trouble... :)11:50
Bernardomoblin11:50
lucazadeare you trying moblin psb patches?11:52
lucazadeor meego?11:52
Bernardoyes, I got their src rpms, but the patches are huge11:52
Bernardomoblin for now11:52
Bernardomeego doesn't have yet the xorg driver11:52
lucazadeok11:53
Bernardoat least that I could find11:53
lucazadedidn't know11:53
Bernardomoblin guys decided to make a huge monolythic patch for psb11:53
Bernardoand change some drm files, and also redefine backlight_device in backlight.h11:54
BernardoSo I am trying to reduce the changes and build it as a dkms module,11:54
lucazadecould you point me to this patch? 11:54
BernardoI extracted it from the kernel source rpm, but let me pastebin it, just a sec11:55
lucazadeok when possible :)11:55
Bernardothis is the big one - http://pastebin.com/aCFwLe3z11:57
BernardoMRST-GFX-driver-consolidated.patch11:57
lucazadehuge11:57
lucazade:O11:58
Bernardothere is also some psb related stuff in linux-2.6.31-drm-mem-info.patch - http://pastebin.com/P2Vn6NSq11:58
BernardoI just got the 2.6.32 kernel from lucid, applied those two (correcting what wouldn't apply), then went to get it building out of tree, doing something like what is done in our current module11:59
lucazadeso all these patches are related to psb drivers and not to iegd.. instead the new code drop for meego is for iegd,... right?12:00
Bernardowhen I get it to build out of tree I'll have a go packaging it as a dkms module like the current one12:00
BernardoThere is also a big monster (though smaller) for IEGD12:00
lucazade*terrified*12:01
Bernardohttp://pastebin.com/4eWVi81E - linux-2.6.31-iegd.patch12:01
BernardoI left that one for you... ;)12:01
lucazadeheheeh12:01
lucazadethis stuff is known to work?12:02
BernardoI think so - at least 2D12:03
Bernardo[05:36:47] <Sarvatt> the ones in the latest moblin release from january were the ones you probably caught me talking about that were 2D only (3D needs gallium)12:03
lucazadeok now is a bit clearer12:03
BernardoI had to re-add a definition ubuntu had removed from drmP.h (DRM_PROC_PRINT)12:09
Bernardolater will see if I can remove that again and the calls to it12:09
lucazadetell me if i can help you12:09
BernardoI'm fighting the makefile now... It seems easier to put all stuff in a single dir like the old module12:14
bjsniderSarvatt, the build failed. your rules file is wrong in the 32-bit compat libs section. nvidia has removed some of the 32-bit compat libs.13:07
bjsniderthe rules file i sent works13:08
* Bernardo hates monolythic patches14:34
* Bernardo gives up on moblin drivers for today15:20
Sarvattstill can't find libXvMC.so.117:06
Sarvattdont tell me that got moved to an alternative somewhere too..17:06
tjaaltonlibxvmc1: /usr/lib/libXvMC.so.117:09
tjaaltonapt-file search is your friend17:09
Sarvattoh dangit I know the problem, I was adding the dep to the control not the control.in so it was getting removed17:13
bjsnideri already took care of this in my scripts17:13
bjsniderSarvatt, did you remove the .so.1 links too?17:14
Sarvattweird, glxinfo takes about 15 seconds to complete and I'm getting (WW) May 23 13:34:59 NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004758, 0x00004858) in xorg.0.log when it happens, everything stalls18:49
bjsniderit's fine here18:49
Sarvatti get it with 195 too apparently :(18:56
Sarvattbjsnider: are you on karmic still?19:00
bjsnidernegative19:09
bjsniderhave you got an old card?19:09
bjsniderwhat opengl version does glxinfo give you?19:10
bjsnidermine is 3.319:10
Sarvatt8400M GS, 3.3 here too19:14
Sarvattcan you pastebin your ~/.nvidia-settings-rc?19:15
bjsniderhttp://pastebin.com/YkT7Ax4E19:19
bjsnider'it's just defaults though19:19
Sarvatt4x anisotropy and 12x FSAA is default?19:20
Sarvattand texture sharpening enabled?19:20
bjsniderwell, i have those things on full blast19:24
bjsnidereverything else is default19:25
bjsniderbesides i doubt any of those settings make any difference19:25
bjsniderexcept on windows19:25
Sarvattenabled MSI and it's down to about 3 seconds for the freeze19:32
Sarvattno, it didn't take the module parameter so its just luck it was faster that boot19:33
Sarvattthis doesn't happen on a 32 bit livecd with nvidia-current installed, ugh19:34
bjsnideris it really an irq issue though?19:38
Sarvattits hanging polling the performance profile state looking at the strace19:45
bjsnideris it on a shared irq?19:46
Sarvattnope19:46
bjsniderhave you got a crap system there?19:46
bjsnidermaybe the hardware's broken19:47
Sarvattit worked fine for years with <=190 drivers19:48
bjsnidermaybe it's the x server19:49
bjsniderwhat happens in karmic?19:50
bjsniderhave you got any crazy stuff in the xorg.conf?19:50
Sarvattits fine, its fine on a 32 bit livecd too19:50
Sarvattnope stock19:50
Sarvattthats highly annoying :) i forgot i disabled compiz because of this problem when we moved to 195 series19:52
Sarvatt14 seconds to open the display 8 seconds to quit after it displays everything for glxinfo19:53
bjsnideris the cpu spiking at that point?19:57
bjsnideri don't see what the difference is in this context between a livecd and a hdd install19:59
coz_I know I have lucid on a 64 bit system with 32 bit install  ...also had 64  bit install with no issues with the 195.xx.xx drivers on either and no compiz issues..just thought I would comment :)20:03
bjsnideri think he has a hardware problem20:13
coz_I would guess the same20:14
coz_although the inability to install official nvidia drivers is a real  down side of lucid at this point  in terms of testing drivers for hardware configuration20:15
Sarvattthe livecd install is 32 bit my install is 6420:15
Sarvatti give up on those darn 256 drivers for now, gnome panel is corrupted horribly every single boot too20:15
Sarvattthe whole display blinks on and off real quick when glxinfo is done showing the info before it actually quits too (was testing things remotely and didnt notice)20:16
Sarvattah should try nvidia-173 out20:20
Sarvatthmm the panel corruption looks exactly like this guys - http://www.nvnews.net/vbulletin/showthread.php?t=14936120:22
Sarvattoh jeeze dont tell me https://bugs.edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/456637 is affecting me too20:25
Sarvatti might as well use nouveau if i have to use the highest perf state20:25
bjsniderSarvatt, did you change powermizer settings like recommended in that thread?20:57
Sarvattnot yet, had to give the laptop back :)20:58
Sarvatti'm just going to edit the video bios so the highest power state is the medium one if it does work20:59
bjsniderwell, on that train of thought, my card doesn't have power management options because of a chip on the board being locked in position or whatever. so my card is always on full blast20:59
bjsniderand that might explain why mine works20:59
* Sarvatt nods20:59
Sarvatti mean i see it hung polling the power state info when i strace glxinfo21:00
Sarvattjust didnt have time to test forcing it21:00
bjsniderof course forcing a laptop gpu to full throttle isn't helpful in terms of power usage21:04
bjsnidernouveau is always on fullthrottle too so i bet nouveau works fine21:04
Sarvattyeah, will try out 173 too incase that works21:04
Sarvattit a huge hit, over 1.5 hours less battery life at max speed21:08
Sarvattmaybe i'll see how low i can push the GPU voltage at max speed instead, this GPU overclocks like crazy so it might have the headroom to go a lot lower21:10
bjsniderthe changelog for the 256 blob doesn't explicitly say they fixed the powermizer issue21:11
Sarvatti had it stable at 640mhz core clock up from 400mhz at one point with default voltages21:13
Sarvattthe windows drivers always were horrible at powermizer crap21:13
Sarvatthad to use specific releases because it was broken for months at a time21:14
bjsniderif the windows drivers were bad at it then i wonder if the problem is the shared code instead of anything linux-specific21:18
bjsnideror perhaps it's a design flaw21:19
coz_could be the card itself ?21:30
coz_could be the power supply is diing also.... change power plugs on the card to see if that helps incase it is just a bad plug21:31
bjsnideryes but this is a laptop22:13

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!