/srv/irclogs.ubuntu.com/2012/06/14/#ubuntu-x.txt

mlankhorstmorning06:02
RAOFYo yo!06:03
mlankhorstno luck yet, did manage to scan for all storage modes yesterday and rediscovered some missing in the enumeration :P06:03
mlankhorstneed something else to do for today, any suggestions?06:04
tjaaltonnouveau bugs? :)06:04
mlankhorstI mean, something not nouveau so I can focus my mind on something else then try with fresh view in a few days06:05
tjaaltonserver bugs then06:05
RAOFYeah, server bugs are often good.06:06
mlankhorsthm, do we have that evdev and synaptics memory corruption sru'd yet?06:06
tjaaltonit's not in quantal even06:07
tjaaltoni think06:07
mlankhorstyikes06:07
tjaaltonno wait06:07
tjaaltondifferent thing maybe06:07
RAOFWhat was the synaptics memory corruption?06:14
RAOFDear mesa: kindly build, love, Chris.\06:14
tjaaltonRAOF: 8.0.3? builds here06:15
tjaaltonor built06:15
RAOF8.106:15
tjaaltonahh06:15
tjaaltonno comments06:15
mlankhorstRAOF: the one where X dies a slow death, or sudden death on unplug :)06:15
RAOFI think the -evdev one which was that got accepted, didn't it?06:16
tjaaltonwas it the silent abi change?06:16
mlankhorstyeah might, but basically all patches from xf86-input-synaptics 1.6.206:16
tjaaltonor where it looked like one06:16
RAOFI *think* it ended up being miscompiled code on i386 under certain circumstances?06:17
tjaaltonyeah that06:17
RAOFtjaalton: Incidentally, do you have any idea what 101_mesa_hidden_glname.patch is *for* ?06:18
mlankhorstRAOF: do we have plans to sru synaptics 1.6.3 yet? haven't seen any reports of regressions in quantal with it06:20
RAOFIt's not on my TODO list; this is something that you could usefully do today, if you wanted :)06:21
mlankhorsti want to move synaptics to 1.6.2 first, since it basically is. Only thing lacking is the 2 version changing commits.06:24
tjaaltonRAOF: looks like we've lost all the history before 8.0-rc2..06:25
tjaaltonoh it goes way back06:26
RAOFtjaalton: The earliest reference I can find to it is in your changelog from 7.1~rc106:26
RAOFAlthough you don't seem to have known what it did then :)06:27
tjaaltonneither did kyle mcmartin five years ago06:27
tjaaltonin 6.5.3-1u106:27
tjaaltonso, DEP-3 has a true purpose :P06:29
mlankhorstdrop it for quantal ? :>06:29
RAOFAs far as I can tell that would break ABI by hiding a symbol that was previously unhidden.06:30
RAOFOn the other hand, I have absolutely no idea what anyone would *do* with that symbol.06:31
tjaaltonhttp://old-releases.ubuntu.com/ubuntu/pool/main/m/mesa/mesa_6.5.1~20060817-0ubuntu3.diff.gz06:36
tjaaltonback in the golden days there was no patch-system..06:36
tjaaltonbeing used06:36
tjaaltonah, not true. but that change was done directly to the source it seems..06:37
mlankhorstlater than in dapper?06:37
tjaaltonlooks like I put that in a patch Feb 21st '0706:40
tjaaltonand no comment about why it was there06:41
tjaaltonmlankhorst: right, it was introduced in edgy06:42
tjaaltonbut reading between the changelog lines..06:42
tjaaltonmight just as well been a temporary hack that remained in the package06:42
RAOFIt doesn't do anything to x86-64. I think we can probably drop it in quantal and see if anything explodes. I don't think it will.06:47
tjaaltonyeah06:48
mlankhorstwell, i ran dapper fine without it ;)07:02
RAOFYou know what would be *totally awesome*? If make wasn't saying “no target to make depend”.07:19
mlankhorstdidn't it use 'makedepend' ? :P07:28
RAOFAh, no.07:34
RAOFIt turns out that if makedepend doesn't work, it says “No rule to make target depend”07:35
RAOFBecause it's GODDAMNED RIDICULOUS, that's why.07:35
mlankhorstRAOF: btw I'm still RE'ing even if to the casual observer it may look like I'm preparing synaptics 1.6.2 (just a version bump, we already have all the patches)07:39
RAOFIf we've already got all the patches why are we getting the version bump?07:39
mlankhorstRAOF: shrug, there will probably be a new release at one point, i need to get my mind off reverse engineering for a bit so I can subconsciously process information and think of things you cant when staring too long :)07:41
RAOFFair enough :)07:41
mlankhorstplus it was just merging debian and dropping the patches-that-were-commits series07:43
RAOFFair enough.07:49
RAOFMmm. Hardlinks.07:52
RAOFJUST TO MAKE IT MORE DIFFICULT.07:52
mlankhorst'thou shalt not built from tmpfs with package on a real fs'?07:54
RAOFNo, in this case “be careful when editing files in ./build/dri, because they're hardlinks to files in ., and different editors will break those hardlinks.07:55
RAOFGrrrrAAAAARCGH!08:00
mlankhorstI build intree with git anyhow :)08:01
mlankhorstmesa make clean is broken enough to justify using git clean instead08:02
RAOFWell, you're *required* to build mesa in-tree; out of tree builds are broken.08:02
RAOF...that's retarded.08:09
mlankhorstthere's another build system you can use too08:09
mlankhorstscons iirc08:09
RAOFYeah, but we don't use that. And I'd be surprised if it isn't a bit broken.08:10
RAOFSo, make can't seem to determine that a rule for main/api_exec_es1.c can be used to make ../../src/mesa/main/api_exec_es1.c08:11
mlankhorstI'm pretty sure out of tree shouldn't even be attempted atm unless you want to fix things08:12
RAOFThat's what I'm doing now; attempting to fix things.08:13
RAOFBecause we'll probably want 8.1, and that means we'll want out-of-tree to work.08:13
mlankhorsthm, where can I see the stable queue for 3.2.21?08:16
mlankhorststable-queue.git doesn't list it08:17
jcristauprobably not started yet08:19
RAOFOh, man. Out-of-tree builds are so utterly broken.08:34
tjaaltonmlankhorst: git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-3.2.y-queue.git08:55
tjaaltonbut nothing there yet08:55
tjaaltonI'll add some commits though08:55
mlankhorstmulti arch is funny, took a bit to figure out how to install libdrm2 amd6409:10
SarvattRAOF: that problem is because of galliumcore09:18
SarvattRAOF: dget -u -x http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/pool/main/m/mesa/mesa_8.1~git20120529.f92b2e5e-0ubuntu0sarvatt.dsc , that was the last time mesa built09:19
Sarvattllvmcore was broken because of https://bugs.freedesktop.org/show_bug.cgi?id=49504 , now it fails with https://bugs.freedesktop.org/show_bug.cgi?id=5060409:21
ubottuFreedesktop bug 49504 in Mesa core "[Bisected] Mesa master compilation broke when built with --with-llvm-shared-libs" [Normal,New: ]09:21
ubottuFreedesktop bug 50604 in Mesa core "[compile error] ../../../../../src/mesa/libdricore/../main/api_arrayelt.c:45:27: fatal error: main/dispatch.h: No such file or directory" [Critical,New: ]09:21
aissenSarvatt: is there a reason your cedarview ppa is private ?10:07
Sarvattaissen: i got asked to delete it, the packages are going straight into precise in the next few days though10:08
aissenSarvatt: alright !10:09
aissenSarvatt: I tried it on two different hardware (D2500 and N2600), and I only have a black screen on X startup.11:56
aissenSarvatt: will there be an updated version from the latest code drops ?11:56
Sarvattaissen: if you're using ubuntu you need to remove vt.handoff=7 from the kernel command line to get around that, can do GRUB_GFXPAYLOAD_LINUX=text in /etc/default/grub and update-grub to do it12:05
Sarvattsysrq-v works too, or vt switch and stop/start the dm12:07
aissenSarvatt: thanks12:24
aissenSarvatt: the screen is filled with garbage. Even the "kms" side doesn't work, it doesn't seem to find the right refresh rate.12:26
aissenSarvatt: yes, I'm on ubuntu, running precise12:26
Sarvattaissen: unity 2d or gnome fallback session instead of unity or gnome-shell12:39
Sarvattaissen: arent these drivers fun? :P12:40
aissenSarvatt: yeah I love that :-)12:40
Sarvatt2d deceleration, broken GL support, but video acceleration works ok12:41
aissenSarvatt: how can I enable unity 2d ? Isn't the problem at the modesetting level, since the display is already scrambled before X starts ?12:42
Sarvattits scrambled on the lightdm login screen?12:42
aissenyes12:43
Sarvatterr, thats a new one12:43
aissenI could "find" unity 2d choice in lightdm, but I'm guessing this won't help much12:43
aissenlet me try on the other hardware (D2500) the grub options, I'll tell you if it helps.12:44
Sarvattaissen: are you using your own kernel? you dont have psb_gfx loaded right?12:45
aissenSarvatt: nope, clean precise install.12:46
aissenSarvatt: let me check.12:46
Sarvattdid you dkms the kernel patch or something?12:46
aissenhum, I installed the dkms package from your ppa - wrong move ?12:47
aissencedarview-drm12:47
Sarvattoh yeah12:47
Sarvattthat wont work12:47
aissenoh, ok.12:47
rohanhello.. anyone here from the x-swat x-updates ppa team?14:03
mlankhorstyes?14:05
rohanmlankhorst: I was wondering about the 295.59 nvidia driver -- has it been deliberately kept to the 259.3x version due to some issue? 14:07
mlankhorst259?14:08
rohansorry, 295.3x14:08
mlankhorstthink there were some regressions indeed :)14:08
rohanah.. looks that way, because even the page here http://www.nvidia.com/object/unix.html lists 295.53 as the latest14:09
rohani hope it's resolved soon because the .53 version doesn't support my card14:10
tjaaltonwhich is.. ?14:10
rohanPCI ID 0fd3 14:11
rohanGT 640M LE14:11
tjaaltonit's up to nvidia to provide that14:11
rohanyes, I realise :) I know it's not something x-swat / x-updates can fix :) 14:12
rohanIt looks like 295.59 was supposed to be a "long-lived branch release".. i can't imagine how they could release it with regressions!14:15
tjaaltonthere was a security fix that broke stuff14:16
rohanI see, thank you, tjaalton , mlankhorst 14:17
rohanI will wait for the next iteration 14:17
tjaaltonnvidia-current is at 295.40, nvidia-current-updates at 295.4914:17
mlankhorstplus it didn't fix the gaping hole :(14:18
tjaaltonah that14:18
rohanmlankhorst: which gaping hole? [just curious]14:19
tjaaltonoh now there should be 295.5914:19
mlankhorstrohan: from what i read from the patch, it seems whole io space is open to user14:19
tjaaltonwith support for 640m le14:19
mlankhorstnow whole io space minus 100kb is14:19
tjaaltonhttp://www.nvidia.com/object/linux-display-amd64-295.59-driver.html?ClickID=d2mtm2tsoxksbkobmcnznsx20bn22ytbcymy14:20
rohan[10:17] <tjaalton> nvidia-current is at 295.40, nvidia-current-updates at 295.49 ==> are we looking at different repos? I am looking at the x-updates PPA and the version of nvidia-graphics-drivers is 295.5314:20
tjaaltonah14:21
mlankhorstftp://download.nvidia.com/XFree86/patches/security/CVE-2012-0946/nvidia-blacklist-register-mapping-290-295.diff14:21
ubottuThe NVIDIA UNIX driver before 295.40 allows local users to access arbitrary memory locations by leveraging GPU device-node read/write privileges. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0946)14:21
rohanyes, but isn't 295.59 the one with the security hole?14:21
tjaaltonit's the latest of the series..14:21
mlankhorstlook at that patch.. there is no reason for userspace to map ANY register from the device in that range..14:21
mlankhorst     if (IS_REG_OFFSET(nv, NV_VMA_OFFSET(vma), NV_VMA_SIZE(vma)))14:22
tjaaltonso if they all are affected then yes14:22
mlankhorstthat whole branch needs to be removed if nvidia cared about security14:22
tjaaltonis it fixed in 302?-)14:22
mlankhorstnope14:22
tjaaltonheh14:22
rohan[10:19] <mlankhorst> now whole io space minus 100kb is ... ?14:23
rohanoh you were referring to the patch you linked? 14:23
mlankhorstyeah that was their 'fix' turns out userspace needed it so it broke on a few14:23
rohanoh this 'fix' is what's holding 295.59 up? 14:25
rohanI guess that's also why they removed it from the main download page14:25
tjaaltonno14:25
tjaaltonthe hole is old14:25
rohanyes, but the fix is breaking userspace, like mlankhorst said, right? or am I just not following? 14:25
mlankhorstit's in all nvidia drivers ever released up to 295.40, and even there still open. :S14:25
rohanso does 295.59 fix it, and by fixing it, cause issues? or were the regressions you mentioned separate?14:40
mlankhorsti cant say since i dont look into nvidia drivers14:54
tjaaltonthey tried to fix it in .40, which caused issues, and at least some got fixed later14:54
tjaaltonaiui14:54
rohanah i see14:55
rohanguess my best option atm is just wait, then :) 14:55
mlankhorstthere's no point in just updating for the sake of updating14:55
tjaaltonright, but .59 adds support for 640mle..14:57
tjaaltonand a bunch of other cards14:57
mlankhorstthat's a valid point :)14:59
rohanso should i file a request or just wait?15:18
tjaaltontseliot probably has it on his todo-list already15:19
tseliotyep15:20
tjaalton:)15:20
rohangreat, thank you :)15:35
=== yofel_ is now known as yofel

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