/srv/irclogs.ubuntu.com/2012/08/21/#ubuntu-x.txt

barryyep.  waiting for login screen to come back up00:00
barryhmm, black screen00:00
Prf_Jakobtry to VT switch to a console.00:01
Prf_Jakobctrl+alt+f100:01
Prf_JakobIf you are on linux, ctrl+alt+space ctrl+alt+f100:01
barryi think it's ctrl-fn-command on os x, but nope, it's not switching00:02
barryi'm still ssh'd in though00:02
barry*ctrl-fn-command-f100:02
barryhowever:00:03
barry% lsmod | grep vmwgfx00:03
barryvmwgfx                121226  2 00:03
barryttm                    83595  1 vmwgfx00:03
barrydrm                   275528  3 vmwgfx,ttm00:03
barry 00:03
Prf_Jakobsudo service lightdm start00:04
Prf_Jakobincase doing it from X killed it.00:04
barryyep, just did that again.  i hear bongos, so i do think it's restarting00:04
Prf_JakobHmm00:04
Prf_JakobAnything interesting in Xorg.0.log?00:08
barrynot too much, perhaps this:00:09
barry[  1104.435] (WW) Warning, couldn't open module modesetting00:09
barry 00:09
Prf_JakobDon't think so00:09
Prf_JakobIs 3D enabled?00:10
Prf_Jakobon the host?00:10
Prf_JakobDoes it say it has 3d in Xorg.0.log00:10
barrygrep -i 3d /var/log/Xorg.0.log00:10
barry[  1104.440] (WW) vmware(0): Failed to initialize Gallium3D Xa. No render acceleration available.00:10
barry[  1104.440] (--) vmware(0): Direct rendering (3D) is disabled.00:10
barry[  1104.440] (II) vmware(0): No 3D acceleration. Not setting up textured video.00:10
barryi definitely have Accelerate 3D Graphics turned on in settings00:11
Prf_JakobOk, thats normal if you don't have 3D turned on.00:11
Prf_JakobOh... hmm.00:11
Prf_JakobWhat does it say drm?00:11
barry% grep -i drm /var/log/Xorg.0.log00:12
barry[  1104.412] (II) config/udev: Adding drm device (/dev/dri/card0)00:12
barry[  1104.436] (--) vmware(0): DRM driver version is 2.4.000:12
barry[  1104.746] (II) config/udev: Adding drm device (/dev/dri/card0)00:12
barry 00:12
Prf_Jakoblooks okay00:12
barrywhat do you think about adding vmwgfx to /etc/modules and rebooting?00:13
Prf_JakobThat might work00:14
barryworth a try i guess ;)00:14
Prf_Jakobsudo service lightdm stop00:14
Prf_Jakobsudo killall Xorg -900:14
Prf_Jakobmight work as well00:14
Prf_Jakoband then starting it again.00:14
barryinteresting, no Xorg process found00:15
barrylet's try a reboot00:15
barry% grep -i 3d /var/log/Xorg.0.log00:17
barry[     8.737] (II) vmware(0): Gallium3D XA version: 1.0.0.00:17
barry[     8.737] (--) vmware(0): Direct rendering (3D) is enabled.00:17
barry 00:17
barryand yep, the llvm-based corruption seems to be gone, as is the tiny fonts on lightdm00:18
barryPrf_Jakob: i have to go eod now.  i've updated bug 1039157 with what i know so far.  if you have any other debugging suggestions, please comment on the bug and we can chat tomorrow.  thanks!00:22
ubottuLaunchpad bug 1039157 in xserver-xorg-video-vmware (Ubuntu) "X problems in Fusion guest" [Critical,New] https://launchpad.net/bugs/103915700:22
Prf_Jakobbarry: ok, thanks00:25
Sarvatti'll try to figure out why its not auto loading tomorrow, from the looks of it with my old logs x-x-v-vmware actually did the modprobing before though and its not now under xserver 1.1300:25
Prf_JakobYeah, I was thinking about that.00:25
Sarvattwould be nice to have it modprobed earlier in the boot though so theres a splash, adding it to /lib/udev/rules.d/78-graphics-card.rules might make that happen00:27
Sarvattoh vmwgfx doesn't have any modaliases00:28
Sarvattthats why its not auto loaded by udev?00:28
Prf_JakobHeh, I don't even know what a modalias is :)00:29
Sarvattmodinfo i915 lists the devices it auto loads from udev for, nothing on vmwgfx even though theres 1 pci id00:30
Prf_JakobAh00:30
Prf_JakobWhat does the splash use btw?00:31
Prf_Jakoblibkms, OpenGL?00:32
Sarvattif theres /dev/fb0 it uses that, theres specific backends written for each kms driver, although i think that changed in 12.10 and it uses the newer dumb ioctls. there is a libkms backend for the drm renderer that would work though thats also in 12.04 though00:35
* Sarvatt passes the heck out, sorry to disappear suddenly :)00:35
tjaaltonRAOF: busy with the baby?-)06:08
RAOFtjaalton: Yeah; Sam's gone out for an appointment, so I'm holding the baby :)06:09
tjaaltonalrighty06:09
mlankhorstRAOF: ping06:12
RAOFPong06:12
mlankhorstRAOF: you dropped the core patch and are encouraging -core to be passed, how do you pass that by default?06:12
RAOFmlankhorst: In lightdm06:13
RAOFmlankhorst: I should see if that's been uploaded, actually.06:13
tjaaltonRAOF: wondering if the libgallium patch should actually be modified to add the gallium stuff in libdricore, if what you said that's what upstream might take06:13
mlankhorstRAOF: yeah but could that be sru'd for precise somehow for next lts stack?06:14
tjaaltonalso, probably no reason to move libdricore out of libdir to libdir/dri06:14
tjaaltonhmm need to add that to debian06:14
RAOFmlankhorst: Hm, possibly06:23
RAOFdvorak is poorly optimised for 1 handed typing!06:24
mlankhorstuse a smartphone :D06:24
mlankhorstor a dumbphone with t906:25
tjaaltonor get a carrying sling :)06:25
mlankhorstor use text to speeds06:26
mlankhorstit shoot laugh your ascend!06:26
RAOFNo irc on my phone :)06:28
RAOFI can't find the baby sling, either :(06:29
tjaaltonnasty name for that thing btw :)06:29
RAOFNot for launching babies at all!06:30
mlankhorstwe never said that06:31
tjaalton:)06:31
mlankhorstit looks like the stress of parenting is getting to you if you would think we would think about such cruel things06:31
mlankhorstdo you manage to sleep at nights, even?06:45
RAOFYeah; plenty.06:48
RAOFZoƫ's pretty good that way.06:48
RAOF...and xserver uploaded.06:49
jcristauupload with one hand?07:17
tjaaltongit push with the other07:17
jcristauwhere's the baby then? :)07:18
tjaaltondamn ;)07:18
RAOFUp in the air.07:18
RAOFYou throw her up, type something, and then catch her.07:18
mlankhorstRAOF: lucky you, I have to face the wraith of ttm maintainers :)07:24
mlankhorstwhich I guess in a way wouldn't be too unsimilar from a crying baby at night07:27
* mlankhorst ducks07:27
RAOFHeh07:33
tjaaltonhum, trying to build mesa with --with-llvm-shared-libs, but fails07:45
tjaaltong++  -L/usr/lib/llvm-3.1/lib  -lpthread -lffi -ldl -lm  lp_test_blend.o lp_test_main.o -o lp_test_blend -Wl,--start-group  -L../../auxiliary/ -lgallium libllvmpipe.a -lLLVM-3.1 -lXext -lXdamage -lXfixes -lX11-xcb -lX11 -lxcb-glx -lxcb -lXxf86vm   -ldrm   -lm -lpthread -ldl -Wl,--end-group07:45
tjaalton/usr/bin/ld: ../../auxiliary//libgallium.a(u_dl.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5'07:45
oyvindbjsnider: Latest nvidia-settings 304.37 for amd64 has failed to build in X updates PPA. Looks like the archive was distributed in a slightly unclean state. Removing objects under src/libXNVCtrl/ in advance should fix the build..07:45
tjaalton/usr/bin/ld: note: 'dlclose@@GLIBC_2.2.5' is defined in DSO /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libdl.so so try adding it to the linker command line07:45
tjaalton/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../x86_64-linux-gnu/libdl.so: could not read symbols: Invalid operation07:45
tjaaltonoh, and bumping build-deps like llvm isn't nice for backports, I guess07:46
mlankhorstyour libdl is screwed?08:49
mlankhorsteither that or you forgot -ldl :)08:50
jcristauhe has -ldl there twice08:51
mlankhorstah08:51
jcristauand ld even says it found dlclose there08:51
tjaaltondunno, fedora has a recent snapshot and they use --with-llvm-shared-libs, so wonder why it fails to build here09:14
mlankhorsttjaalton: well what if you remove one of those 2 and build it manually?09:16
tjaaltonmlankhorst: still the same09:16
mlankhorstdid you remove the first one or the second one?09:17
tjaaltontried both09:17
tjaaltondoesn't the error suggest that something is wrong with libgallium.a?09:17
mlankhorststatic libraries are weird09:17
mlankhorstI think you might need to remove the -Wl,--start-group and -Wl,--end-group and keep the last libdl09:18
tjaaltonbroke even harder :)09:20
mlankhorstsigh09:21
mlankhorstcan you send me what you have?09:21
tjaaltongit pull09:22
tjaaltonno wait09:22
tjaaltonmerged master and bumped the version to 9.0~git..09:22
tjaaltonthere09:23
tjaaltonit was the same error with the previous snapshot09:24
mlankhorstblegh needs quantal to build, give me a sec09:25
tjaaltonyup09:26
mlankhorstupdating chroot09:26
mlankhorstok i seem to get the same error :)09:29
tjaaltongood :)09:29
mlankhorst g++  -L/usr/lib/llvm-3.1/lib  -lpthread -lffi -ldl -lm  lp_test_blend.o lp_test_main.o -o lp_test_blend -Wl,--start-group  -L../../auxiliary/ -lgallium libllvmpipe.a -lLLVM-3.1 -Wl,--end-group -lXext -lXdamage -lXfixes -lX11-xcb -lX11 -lxcb-glx -lxcb -lXxf86vm   -ldrm   -lm -lpthread -ldl09:30
mlankhorstseems to work09:30
mlankhorstbut I have no idea where the start-group and end-group are inserted..09:33
tjaaltonsrc/gallium/Makefile.template09:33
mlankhorstit should be just protecting llvmpipe and lgallium, not the rest09:34
jcristauisn't that a ld bug?09:34
mlankhorstpossibly09:35
mlankhorstseems Sarvatt had already reported it as https://bugassistant.libreoffice.org/show_bug.cgi?id=4950409:37
ubottubugs.freedesktop.org bug 49504 in Mesa core "[Bisected] Mesa master compilation broke when built with --with-llvm-shared-libs" [Normal,Resolved: duplicate]09:37
mlankhorstand duplicate bug had this attached https://bugassistant.libreoffice.org/attachment.cgi?id=6510309:38
mlankhorstso maybe just cherry pick that?09:38
tjaaltonit's not in master09:39
tjaaltonbut if you mean cherry-pick from bugzilla then yes09:39
mlankhorstyeah :)09:39
mlankhorstsigh, why do I know such things are a problem even before finding the bugzilla entry :s09:40
tjaaltonok I'll add that to the debian branch09:43
tjaaltonand do yet-another merge..09:43
mlankhorst:>09:43
mlankhorstwish I had something to push to mesa so you'd immediately rebuild again :p09:45
mlankhorstI can push to most of X now09:47
tjaaltonme too, never abused it though09:47
tjaaltononce had plans to break -sis, but meh09:48
mlankhorstthe trick is you don't want to see it as 'abuse' :)09:48
tjaaltontouch something and you're the defacto maintainer09:48
mlankhorsthm lets see about virtualbox then09:49
mlankhorstyay10:00
mlankhorstvirtualbox won't even netboot despite advertising it? o.O10:00
om26ermy screen' dpi is 138 but its always hardcoded to 96 in ubuntu. is there a way I could change that?10:28
om26erxrandr --dpi 138/eDP1 seems to have no effect10:28
mlankhorsttjaalton: surprisingly, works here..10:28
tjaaltonmlankhorst: huh, ok10:29
mlankhorstvirtualbox seems to start fine10:29
mlankhorstalthough compiz is corrupted if i try10:29
tjaaltonyeah that's the bug then10:29
tjaaltonbut is it general llvmpipe-borkedness or something else..10:30
mlankhorstno idea10:30
tjaaltoncheck the log :)10:31
mlankhorstit's using llvmpipe at least..10:32
tjaaltonthere you go10:32
tjaaltonso it's fallout from dropping unity2d10:32
mlankhorstso.. nothing to worry about then?10:32
tjaaltonright10:32
tjaaltonsry :)10:32
tjaaltonbut hey, now you have time to fix the libgallium.so build?-)10:32
mlankhorstprobably10:33
mlankhorstwhat needs fixing?10:33
tjaaltondon't know what good --with-llvm-shared-libs brought10:33
tjaaltonmake the patch apply and build the .so10:33
mlankhorstoh that10:33
mlankhorstyou know that would mean the whole llvmpipe patch could be dropped, too10:33
tjaaltonbut it might be easier(?) to merge it in libdricore10:33
tjaaltonprobably so yeah10:33
tjaaltonwanted to see what it did10:34
tjaaltonand don't see much10:34
mlankhorstwill virtualbox be sru'd to precise for .2?10:35
mlankhorstsince the dkms module will no longer build and the xorg one needs an update10:35
tjaaltonnah10:36
tjaaltonvbox users can stay on .110:36
tjaaltoni mean the stack on .110:36
mlankhorst:/10:36
tjaaltonwhy not?10:36
tjaaltonit's not like the "hw" needs enabling10:37
mlankhorststill leaves the kernel build failure, though10:37
tjaaltonwait, what?10:37
mlankhorstif you enable the 3.5 kernel on precise10:37
tjaaltonmake it conflict10:38
tjaaltonit's possible today..10:38
tjaaltonbreaking the setup that is10:38
mlankhorstyeah, I'll ask leann10:38
tjaaltonnah, make vbox conflict with the kernels that it doesn't support10:39
tjaaltoneasier10:39
jcristauconflicting with kernels is teh suck10:39
tjaaltonwell :)10:39
mlankhorstbut right i don't care enough today, I'll add a point to backports to think about it later10:39
tjaaltonor sth10:40
mlankhorstyeah10:42
mlankhorstok enough caring for now, I'll look at the gallium patch10:43
tjaaltongreat10:43
tjaaltonwould take more time if I tried :/10:44
mlankhorstI kind of want to ask raof about it first, i sort of understand the patch but not the reasoning behind it11:00
tjaaltonsure11:00
tjaaltonseems to be having some network issues11:01
mlankhorst seems sort of like since it's using libgallium everywhere anyhow, it could just change libgallium.a to libgallium.so and be done with it11:03
mlankhorsttjaalton: seems a variant of it was already merged though11:15
tjaaltonoh?11:15
mlankhorstthe patch adds --enable-shared-dricore11:16
tjaaltonthere's the libdricore support upstream yes11:17
mlankhorstoh nm it was just from my first partial apply11:18
tjaalton:)11:19
mlankhorstcan the entirety of libgallium.a be built shared?11:28
tjaaltonno idea :)11:30
* mlankhorst tries a automake hack11:41
mlankhorstwell looks a bit harder to make it shared than I thought12:27
mlankhorstit's part autotools and part custom makefiles..12:27
tjaaltonyeah :/12:33
mlankhorstok next attempt12:40
mlankhorstmore luck now13:46
tjaaltonhow much more? :)13:46
mlankhorstoh as in 'almost feeling confident it links libgallium.so correctly'13:46
tjaaltoncool13:47
seb128mlankhorst, hey13:48
seb128+ [ubuntu-x-swat] Detect gfx hardware changes (maybe by checking the modaliases?) and inform users about the change: TODO13:48
seb128mlankhorst, please try to find somebody rather than a team for workitems, team assignments tend to not work, everybody waits on somebody else to pick the stuff up which often never happens :p13:49
mlankhorstseb128: yeah unfortunately half of my team went to sleep or didn't wake up yet :)13:50
seb128fair enough ;-)13:51
mlankhorsttjaalton: I think libtool leads to aggression in a natural way14:09
mlankhorstyay.. builds static and shared :)14:20
debfxmlankhorst: virtualbox upstream requires contributions to be licensed under the MIT license. if you can agree to that posting the patch and a license statement to vbox-dev@virtualbox.org would be great.14:33
mlankhorstdebfx: you send it then, copyright belongs to canonical ;)14:35
debfxmlankhorst: huh?14:37
mlankhorstI mean unless I'm mistaken since I did it as part of my work for canonical, the copyright belongs to canonical, not me personally :)14:38
mlankhorstbut shrug it should be fine, I'll send it14:40
mlankhorsttjaalton: blegh is it really worth it building libgallium shared?14:51
tjaaltonmlankhorst: ask the ones who try to keep the cd image under 700M :)14:55
jcristauthose people still exist?14:55
tjaaltonthat said, i'm not sure if we have more to use for quantal14:55
tjaaltonnot sure14:55
mlankhorstshrug I think I'm close14:55
tjaaltonseb128: do you know? ^14:56
mlankhorstsome linking error in llvmpipe :s14:56
seb128tjaalton, mlankhorst: what's the issue?14:57
tjaaltonis the installer image size still 700M14:58
mlankhorstlets see if it's just llvmpipe breaking..15:02
mlankhorstwoops, probably made all symbols invisible :)15:04
mlankhorst*amused* even on his homepage ulrich drepper manages to be ulrich drepper15:14
mlankhorst"If you have problems with this page it probably means you are using a junk browser. Especially the one from the monopolist. Get something better. Use Firefox or Mozilla."15:14
tjaaltonmlankhorst: ok, we have enough space for mesa, so don't worry about the patch anymore. we can fix it later15:20
tjaaltonstash your changes somewhere :)15:20
tjaaltonmlankhorst: i promised to upload it later today, mind giving it a go on some machine if you have some to spare? since I don't know what the llvm-shared-libs actually did, testing some gallium based driver would be great15:23
tjaaltonI have some radeon card to test with15:23
tjaaltonbut can't get to the machine until maybe 3h from now15:24
Prf_Jakobbarry: ping15:32
barryPrf_Jakob: pong15:32
Prf_JakobAh you are here.15:33
barryyep, how's it going?15:33
Prf_Jakobfine, haven't done anything more on the bug.15:33
Prf_JakobHAve a interface change for mesa that needs to be done before the stable branch is created.15:34
barryPrf_Jakob: np, the workaround is getting me thru.  i was thinking about changing the bug title to "vmwgfx kernel module not getting loaded by default".  would that be helpful?  (if not, i'll leave it as is)15:35
mlankhorsttjaalton: ok15:35
mlankhorsttjaalton: I can stash it, but it seems to be a pain to get it really working15:36
jcristaubah, speaking of mesa my fix still hasn't made it in.15:37
Prf_Jakobbarry: that is the real issue.15:37
barryPrf_Jakob: done15:38
Prf_Jakobthanks15:38
mlankhorsttjaalton: I can build libgallium.so just fine, it's the linking that's proving to be a pita :)15:38
mlankhorsttjaalton: but what do you want me to do, test if it works on a radeon card?15:40
barryPrf_Jakob: thanks for looking into this and helping me out!15:40
Prf_Jakobnp15:41
mlankhorsttjaalton: hm, seems to be just swrast failing15:43
mlankhorstbut I'll put the changes together into something almost coherent15:45
mlankhorstok lets see if those binaries work on quantal :)15:50
tjaaltonmlankhorst: yeah test the non-libgalliuminized (!) version to see it works, i believe intel is mostly fine16:24
mlankhorstinte's easiest to test for me right now :p16:33
mlankhorsttjaalton: not getting a desktop, weird16:49
mlankhorstoh, old kernel16:51
mlankhorstjust some kernel panics on 3.5.0-11 I suppose, nothing really wrong :p16:56
mlankhorsttjaalton: I have no idea what's wrong with the drivers but glxgears spins fine, so dno..17:01
mlankhorstit was broken before too, though17:01
tjaaltonhmm, quantal works on snb for me17:04
tjaaltonthough the machine has 3.5.0-817:05
mlankhorsttjaalton: yeah but it was broken before too, guessing the ddx was screwy instead18:01
tjaaltonok18:02
tjaaltonuploaded xorg that adds -modesetting to video-all18:10
mlankhorstyay \o/18:12
tjaaltonhad it in git for some time..18:12
mlankhorstblegh, updating lts-quantal can wait18:24
Sarvatttjaalton: modesetting's in universe :(18:34
tjaaltonSarvatt: yes, informed -release that it needs to be moved to main18:35
tjaaltonogra_: is it armhf you care about for llvmpipe?18:40
tjaaltonhaha19:03
tjaaltonmesa *.install.in totally messed up19:04
tjaaltonhrm, if we're not going to get swx11 back, maybe it would be best to drop the separate 'dri' build target and have sane paths in *.install.in19:07
mlankhorsttjaalton: we don't know that yet19:09
tjaaltonit's useful on s39019:10
tjaaltonfedora builds it only on that arch19:10
tjaaltonand nothing else, since it has no gfx hw19:10
mlankhorstand for all we know there is some insane reason to keep it19:10
mlankhorstif it has no graphics hardware why would you need it? o.o19:11
tjaaltonfine, I'll mess with the .install files then19:11
tjaaltonrunning apps remotely?19:11
tjaaltonno idea19:11
mlankhorstafter quantal is released there'll be no objection from me to drop it :)19:12
tjaaltonit's dropped already19:12
tjaaltonin git19:12
mlankhorstmeant the separate dri stuff19:13
tjaaltonok19:13
mlankhorstbut shrug i suppose in worst case you do it now and it turns out we would have to revert that common19:13
tjaaltonok correction, fedora builds swrast on s390, no swx11 at all19:15
mlankhorstI retract all my objections :)19:15
tjaaltonright19:16
tjaaltonI'll take the heat to revert the packaging, it isn't that hard19:16
tjaaltonif it should happen19:16
tjaaltonor maybe I'm just a coward and fix the install files instead19:19
mlankhorsthey for stable releases it's good to be a coward :)19:20
tjaaltonargh19:22
jcristautjaalton: i'd prefer to keep swx11.19:22
jcristauit's still useful if you don't have glx19:23
jcristauthat's for debian, you can do what you like in U :)19:23
mlankhorstin that case no point in changing the directory off19:23
tjaaltonyeah I kept it there, it should build again soon19:23
tjaaltoneither I change the directory, or edit all install.in to copy the stuff from dri/.. to ..19:24
tjaaltondunno which makes more sens19:26
tjaaltone19:26
mlankhorstwhatever gives the smallest delta with debian19:26
tjaaltonok it's easier to revert the install.in19:27
tjaaltonthan to retest big changes to rules19:28
mlankhorst:-)19:36
* mlankhorst always favors the lazy approach19:37
tjaaltonjcristau: what about the libosmesa build? I ripped those targets, but the downside is that the static libs are gone19:37
jcristaudunno19:39
mlankhorsttjaalton: libosmesa is still built right?19:42
tjaaltonmlankhorst: yes, but during the dri target build19:42
mlankhorstah good :)19:42
tjaaltonand since you can only build either static or dynamic libs, the static ones are now "lost"19:43
tjaaltonsame thing with libglut19:44
tjaaltonlibglu, whatever19:44
mlankhorstyeah, just have no idea what libosmesa does, just know wine can use it :p19:44
tjaaltonE: libgl1-mesa-dri: binary-or-shlib-defines-rpath usr/lib/x86_64-linux-gnu/dri/i915_dri.so /mnt/src/git.d.o/lib/mesa/build/dri/src/mesa/libdricore/.libs19:47
tjaaltonwth19:47
mlankhorstshared dricore probably19:48
tjaaltonoh well, needs fixing then19:48
tjaaltonless lintian errors anyway19:48
mlankhorstyeah usually the autotools relink before install19:48
tjaaltongetting there19:48
mlankhorstbut those specific ones don't autotool19:49
tjaaltonneed a break.. ->19:49
ogra_tjaalton, yeah, dont bother with armel20:27
tjaaltonmesa-8.0-llvmpipe-shmget.patch on fedora. probably worth checking out at some point21:31
=== jibel_ is now known as jibel
=== RAOF_ is now known as RAOF

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