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

Sarvatti dont know what to do about the gallium stuff though, Replaces: wouldn't work because someone removing libgl1-mesa-dri-gallium wouldn't have the files replaced over libgl1-mesa-dri restored. for now I was just shipping nouveau in libgl1-mesa-dri00:05
RAOFSo, options include: fixing the DDXs to load from the appropriate search paths & names, using the alternatives system, or conflicts/replaces/provides.00:07
Sarvattugh, alternatives just might be the best option there :(01:10
RAOFIf intel had a non-sucky gallium driver I'd plump for conflicts/replaces/provides.01:12
RAOFActually, that could still work - just duplicate i*_dri.so into both packages.  What fun!01:14
Sarvattduplicate every other non-gallium driver too? :D01:15
Sarvattit's just swrast and r300, could just divert those two?01:16
Sarvattllvmpipe swrast seems pretty important if we're going to package r300g, swtnl cards can use it for a huge speedup01:17
Sarvattin 7.9 that is01:17
Sarvatti hate diversions but i think that might be a better option since its just the 2, all the rest of the gallium stuff can just go in /usr/lib/dri and we dont need the dri-searchpath hack if we did that01:20
Sarvatti915g isn't bad at all btw, its just i965g that sucks01:21
Sarvatti915g and i965g have the same names as the classic ones so if you --enable-gallium-intel in the confflags-dri section you get gallium instead of classic btw01:23
rippsDo I need to install libkms in xorg-edgers? what's if for exactly?01:26
Sarvattif you have libdrm-dev installed yeah01:26
Sarvattotherwise nope01:26
Sarvattit'll probably be used for plymouth in MM01:27
RAOFSarvatt: Only if you take files from the installed directory.  If I remember correctly, they get put under gallium/ in the build directory, which is where I take them from.01:28
rippsI was just wondering, because It wasn't pulled with the other libdrm updates and it sounded kinda important01:28
SarvattRAOF: they dont here, they go in debian/tmp/usr/lib/dri when i build01:30
RAOFThat's after running make install.  I take them from build/dri/glx/gallium01:30
Sarvattif i build without --with-dri-driverdir=/usr/lib/dri in the confflags-dri target they do go in gallium/ though01:30
Sarvattah gotcha01:31
Sarvattripps: nah not important now, not used for anything01:31
Sarvattit's only used for the xorg gallium state tracker now, and plymouth is planning on switching to it01:32
RAOFZ01:32
RAOFI think that the vmwgfx dri also wants it.01:32
Sarvattthat needs the xorg state tracker01:32
RAOFFair 'nuff.01:33
RAOFGiven that we've got the relevant kernel module I was thinking of enabling that.01:33
Sarvattyeah planning on doing it in xorg-edgers once all this stuff is worked out for sure, thats why i was messing with enabling libkms before01:35
Sarvattmesa is going to take 2 hours to build in a few weeks at this rate :D01:36
RAOFFeel like running that by the Debian dudes?  I don't think they'd have a problem with enabling vmwgfx in experimental.01:38
Sarvattwould like to see if it even works first01:38
Sarvatti think it's picky about mesa and kernel versions01:38
RAOFFair enough.01:39
RAOFWoot!  I've got Chase's xorg log from 2.6.34+lucid.  Nouveau dies as expected, but fbdev picks up the slack.01:40
RAOFThat's pretty much the best possible outcome.  Hurray!01:40
Sarvattwow, nice!01:41
Sarvatt*that* i didn't expect, thats perfect01:41
Sarvattand makes sense, why didnt that work before?01:41
Sarvatti mean you have the framebuffer fine01:41
Sarvattohhh i know01:41
RAOFDid you test it after VESA stopped trying to claim the device?  I'm not sure if I did.01:41
Sarvattit was because we had vesa loading for kms01:42
RAOFHah :)01:42
Sarvattsweetness :)01:42
RAOFHm.  Is xorg-server 1.8.1+x-x-v-intel 2.11 actually faster at moving windows with all the bling, or is it just vsync working?03:28
RAOFAhem.  Note to self: actually install the new -evdev before loading the new xserver.03:31
RAOFGah.  -synaptics is a much better synaptics driver than evdev :)04:09
bjsniderthat's why they call it synaptics?04:10
RAOFYup.04:12
SarvattRAOF: did you build it locally and install with dpkg or in a ppa? i'm curious if you are getting nvidia-current and radeonhd force installed if you did ppa04:20
RAOFBuilt locally, installed with dpkg.04:20
Sarvatti did it in a PPA on top of xorg-edgers and was getting nvidia-current and radeonhd installed after an apt-get upgrade for some reason04:21
RAOFIf you installed from a PPA I presume you also updated xorg-server?04:22
RAOFInstalling nouveau_dri into /usr/lib/dri-gallium seems to work fine, too.04:24
Sarvattit's not in /usr/lib/dri/ also?04:26
RAOFNope.04:26
RAOFWell, AIGLX does complain trying to load it, but compiz swims along happily04:26
Sarvatthmm, and it loaded from /usr/lib/dri-gallium in Xorg.0.log?04:26
Sarvattah04:26
Sarvatthow many GLX fbconfigs/visuals do you have?04:26
Sarvatthttp://pastebin.com/JsWNk1rs04:27
RAOFMany fewer04:28
RAOF24 and 40 respectively.04:28
Sarvattthere's something really screwed up with that combination on ATI at least04:29
Sarvattcompiz flips out and crashes all over the place unless the gallium one is in /usr/lib/dri/04:29
RAOFWell, I don't have an old enough card to test that, sadly.04:30
Sarvatttrying to dig through phoronix forums to find the people that had the problem and  see if i can get morei nfo04:31
Sarvattoh yeah, ripps has the problem too04:31
Sarvatthttp://pastebin.com/gh6uAmfh (in /usr/lib/dri-gallium) vs http://pastebin.com/csr5BUZi (in /usr/lib/dri) with i915g04:36
RAOFYup, it definitely changes things.04:39
RAOFHm.  virt-manager doesn't like Maverick one little bit.04:47
Sarvatthmm all these people having problems are using gpu's with no hardware TNL that are sketchy anyway04:53
Sarvattripps: what gpu did you have again?04:53
rippsSarvatt: me? radeon 9600 pro - r30004:54
rippsI stopped using gallium a while ago, because it had would create a huge lag when rendering subtitles with gl output in mplayer04:55
bjsniderSarvatt, some of the people you're looking for might be in the #phoronix channel04:55
Sarvatthttps://bugs.freedesktop.org/attachment.cgi?id=35434 -- i pity the foo trying to run piglet on that04:57
Sarvatt192 visuals sheesh04:57
RAOFMan, my intel only has 3405:05
Sarvattyeah intel cut back on the worthless ones just for piglet cus they use it for QA testing every day, it takes a year to run through all those visuals for every test..05:20
Sarvattadded a 2.6.34 compatibility patch to x-updates fglrx-installer, just in time for xserver 1.8 to land soon and break it again :)05:22
Sarvattbryceh: did you get that xserver update into -proposed?06:19
Sarvattcould have sworn you did but i dont see it06:21
asacRAOF: hey master ... how are things going?06:22
Sarvattasac: just curious, you guys know you will need to package up the proprietary libgles/egl/etc for each arm platform to even do anything once you get things building right?06:24
asacSarvatt: yeah ... but we dont need to build against the proprietary drivers06:25
Sarvattasac: he's doing the work in debian-experimental it looks like and its almost done - http://git.debian.org/?p=pkg-xorg/lib/mesa.git;a=shortlog;h=refs/heads/debian-experimental06:25
asacjust drop in the drivers and stuff built against that mesa gles stuff should work 06:25
asaccooool06:25
Sarvatthave you seen how mameo is doing it?06:25
asacnope06:26
asacwhat are they doing?06:26
Sarvattthey have a libgles-qemu package with the headers and its even debianized06:26
asacah ... yeah06:26
Sarvattmeego sorry06:26
asacthats a qemu gles emulation06:26
RAOFNot quite as useful for us, at least as far as I'm aware.06:26
asacwe want to do that too06:26
asacbut its a bit of a pain to package afaiui06:26
* RAOF wonders if vmwgfx does egl too.06:27
RAOFHm, yes it does.06:27
RAOFSo, if that *works* then we'd get gles under vmware (and I'm pretty sure that qemu is at least partially supported).06:28
asachmm. no clue about vmware ...06:28
asacdo they support arm?06:28
asac(/me has doubts about that)06:29
Sarvatthttp://meego.gitorious.org/qemu-maemo/gles-libs and http://repo.meego.com/MeeGo/releases/1.0/core/repos/source/libgles2-qemu-1.3.0-1.1.src.rpm are interesting06:29
asachmm. so we font have the gles-libs?06:30
asacdont06:30
Sarvattdepends on what you want from gles libs, the mesa stuff isn't going to work on any arm systems06:30
asacah ok ... now i see its a gl to gles wrapper (actually the other way around)06:30
RAOFqemu supports arm, and I know that airlied at least has played at passthrough 3d support.06:31
asacyes qemu supports arm06:31
brycehSarvatt, haven't done any xserver updates since before uds so probably wasn't me06:31
asacSarvatt: mesa doesnt support arm? e.g. not even software rendering?06:31
asacanyway, as long as we can build stuff and then drop in the proprietary drivers that would be a big win06:32
RAOFThat should work, assuming sanity.  The proprietary drivers should be providing their own libGLES*, right?06:33
SarvattI have no idea, gallium has a hard requirement of DRI2/KMS, dont think the gallium swrast it's using will work on anything outside of maybe omap06:33
asacRAOF: i guess so ... i talked to vendors here and they said it should be binary compatible (plus some vendor specific extensions)06:34
asacRAOF: does mesa provide a libGLES.so with software implementation?06:34
asacor dont we have a libGLES.so at all?06:34
RAOFIn debian-experimental it provides libGLES{v1,v2}, with swrast.06:35
asacsounds like that should work06:35
RAOFWith swrast, radeon and nouveau drivers.06:35
RAOFFor both x11 and raw kms framebuffers.06:35
asacyeah ... swrast should work unless i am mistaken06:35
asacRAOF: so we the package is ready for synching and then pushing to lucid ppa?06:36
RAOFIt still needs some cleanup, but mostly in non-egl parts.06:37
RAOFIt takes forever to build mesa :(06:37
asacheh06:37
asacRAOF: you mean it takes forever on arm?06:38
asacor even on intelA06:38
asac?06:38
* RAOF shudders.06:38
Sarvatti'm scared how long it'll take on arm06:38
RAOFIt takes ~30minutes or so on my box.06:38
asachow long is "foregver">06:38
asacheh06:38
RAOFMore if I'm not building on a tmpfs.06:38
asacRAOF: thats decent. your CPU is idle most of the times anyway :)06:38
RAOFHeh.06:39
asacso finally there is somethign to do06:39
RAOFYou'd probably be happy with something that does egl in a pretty-much final state now, and then get the final package later, I guess?06:39
asacRAOF: all i want is someth9ing i can get clutter build against :)06:40
asacso yeah ... i dont care if its clean or anything06:40
asacas long as its build and exports all the headers etc. in the -dev i am more than happy06:40
RAOFCool.  I'll do that now, then.06:40
RAOFThe egl bits are pretty much ok.06:41
asacyou will do what? building clutter:) ?06:41
asacj.k.06:41
RAOF:)06:41
asaclet me know when its in mverick... i will push that to some arm ppa then06:41
RAOFBuild mesa in a PPA for you to copy from.06:41
asacwaste some build cycles most likely :)06:41
asacRAOF: oh ... if you do that i would be3 eve happpier06:42
asace.g. already do the backport06:42
SarvattRAOF: oh yeah need to hold off upgrading xserver and friends until pkg-config works on maverick also..07:00
RAOFI haven't seen any of that breakage.07:00
Sarvattpkg-config --cflags xorg-server07:01
RAOFRight, yes.07:01
RAOFI just haven't seen it break any of the packages I've been building.07:01
RAOFPresumably because they haven't been pkg-configing xorg-server07:01
Sarvattati nv radeonhd07:02
RAOFI'm pretty sure there are some patches we can drop from xorg-server, too.07:02
Sarvattxorg-edgers only has 6 patches07:03
Sarvattnot suggesting dropping a lot but a bunch dont make sense there like the arm one07:04
RAOFSo… why does 1.8.1-1ubuntu1 in pkg-xorg git have so many?07:04
Sarvattbecause none of them were submitted with attribution to push them upstream :D07:05
RAOFSo most of them are now upstream?07:06
SarvattI wish! I've emailed 6 of the original authors of them asking for a git formatted patch that I could push upstream but haven't had any responses and stopped, a lot of them are really old07:10
Sarvattok finally got a chroot set up to play around with this debian-experimental build since it doesn't build against newer libdrm. lets see if i can stay awake long enough to see the results :)07:17
RAOFSarvatt: You don't have a Maverick chroot already?07:26
Sarvattlooks like sis, nouveau, nv, dove, and savage are broken by pkg-config 0.2407:27
Sarvatt(still grepping though)07:27
Sarvattvideo-vmware07:28
Sarvattradeonhd07:28
Sarvatti have *many* but none were in a position to build it07:29
Sarvattnot exactly going to to build it on this atom for instance :D07:29
RAOFWhyever not?07:31
RAOFHm…07:31
Sarvatttakes around 1.5 hours07:32
Sarvattand i'm on battery07:32
RAOFOnly 1.5 hours?  I'm surprised.07:32
Sarvattawwh heck i have the HDD space on my 16 core xeon vps for mesa!07:32
RAOFWhere do you have a 16 core xeon vps?07:36
Sarvattthenynoc.com07:37
Sarvatti just dont have much hdd space on it, hard to build kernels with 10gb07:37
Sarvattwhoa baby, 7 second git clone of mesa from git.debian.org07:39
RAOFThat be hella fast.07:40
asacRAOF: looking at the gles-libs readme it says:07:43
asacFirstly, download and extract Mesa-7.6 and build it after applying a patch to07:43
asacenable OpenGL ES 2.0 shader features.07:43
asacdo we apply that patch?07:43
RAOFWe do not.07:43
asacis that a bad idea?07:43
asacor could ew just do that so i can play with gles-libs?07:43
RAOFLet me check if that's already enabled in mesa 7.8.07:44
asacyeah thats what i was thinking ... at best it would already have made its way upstream07:44
RAOFThat'll also be enabling support in a diffrent codepath; I'm pretty sure the packages wending their merry way into a PPA will have GLES 2.0 shader features enabled via a different codepath.07:45
Sarvattthat gles-libs meego uses doesn't actually build everything there, check out the .spec in the srpm07:46
asaci am looking at the git clone of gles-libs atm ... not the rpm07:46
asacRAOF: not sure what that means:)07:47
asacif it means we dont need to apply that patch i am happy ... if i end up having issues i can come back07:47
RAOFasac: That, while we might not have that specific patch, the egl packages in mesa 7.8.1-2 should have that feature anyway.07:47
asacah ok. then lets try without it07:48
asacRAOF: what ppa will you push this to?07:48
asac(mesa that is)07:48
RAOFppa:raof/mesa-egl07:48
asacalf__: ^^07:48
asacRAOF: cool. i am going to bed soon. if the package arrives today pleas ping alf__ who might want to ry building clutter on that07:49
asacRAOF: what timezon are you in btw?07:49
RAOFUTC+1007:50
RAOFI'm approaching EOD Friday :)07:50
asacah :)07:50
asacheh ok.07:50
asacso i guess the package wont be there till monday07:50
asacunless you are one of those crazy guys that work on sat :)07:50
asacthanks again. talk to you soon07:51
alf__RAOF: Great! Thanks a 10^6!07:52
asac:)07:52
SarvattRAOF: dh_install -s --list-missing08:14
Sarvattcp: cannot stat `debian/tmp/usr/lib/libGLESv1_CM.so': No such file or directory08:14
Sarvattdh_install: cp -a debian/tmp/usr/lib/libGLESv1_CM.so debian/libgles1-mesa-dev/usr/lib/ returned exit code 108:14
RAOFSarvatt: Sorry.  Try again now.08:15
Sarvattoh sweet ya merged it to origin/ubuntu too, thanks08:16
RAOFBah!  No pkg-config files in 7.8.108:19
Sarvatt7.8-gles branch... :D08:21
RAOFOr just steal them from master08:22
Sarvattlets see if master builds with origin/ubuntu debian/08:26
RAOFProbably not.08:26
RAOFWe'll need at least to switch to --enable-gles-overlay08:26
SarvattDEB_BUILD_OPTIONS="parallel=16" is insane08:27
RAOFYou're running out of parallelism at that point.08:27
RAOFSweet.  There's all the mesa demos built.08:28
Sarvatt4 minutes and its almost done with dri08:28
Sarvattinsane, building the debs now08:29
Sarvattsymbols are screwed up08:30
RAOFReally?08:32
RAOFI only have x86-64 and i386 to test build on, but I thought I'd captured all the relevant processor-specific symbols, and the internal symbols.08:33
Sarvatthttp://sarvatt.com/downloads/patches/7.8-gles.patch08:33
Sarvattone sec i'll give you the build log when its done, still creating the debs08:33
Sarvattthat patch is a git diff origin/7.8 origin/7.8-gles08:34
RAOFAh, right.08:34
Sarvatt09:13.02elapsed08:34
RAOFI was wondering :)08:34
Sarvattthats setting up the pbuilder and installing all the deps too, sheesh08:35
RAOFBAH.08:35
* RAOF wants08:35
RAOFWell, gles v1 & v2 & openvg work.08:36
Sarvatthttp://paste.ubuntu.com/440744/08:37
Sarvattsymbols08:37
Sarvattwant to use my vps RAOF?08:37
RAOFOh, yeah.  Those symbols.08:37
RAOFWait.  That's an i386, 16 core xeon builder?08:38
Sarvattresultant packages are here - http://sarvatt.com/downloads/mesa-gles/08:43
Sarvattdoesnt look like clutter needs the .pc's anyway08:46
Sarvatthttp://git.clutter-project.org/cgit.cgi?url=clutter/tree/configure.ac08:47
apwRAOF, yo...08:53
RAOFWell, they can get some pc files anyway.  mesa-demos need them, and I like having something to test.08:54
RAOFapw: Yo!08:54
apware you aware of reports that ati graphics using the kms drivers makes laptops hot and bothered, presume its doing poor power management08:54
RAOFYes.08:54
RAOFIt's not so much doing poor power management as having power management totally unimplemented.08:54
RAOFFixed in 2.6.3508:54
apwRAOF, hrm, thats going to be annoying for lucid, at least maverick may fix it then08:55
RAOFAt least, I think that got pulled in with the rest of the drm-next stuff.08:55
RAOFUsers can turn off kms to get power management, at least.08:55
RAOFThey'll loose dri2 by doing that, so it's not an unqualified win.08:56
apwjust turning off KMS gets them power management ?08:56
RAOFYup.08:56
RAOFThe UMS code has power management.08:56
apwpeople are reporting goodness from switching over to prop. drivers08:56
apwahh ok ... will ask them to test that then and confirm awsome08:56
RAOFThe prop drivers also have power management, surprisingly enough :)08:57
RAOFapw: Aaah, Sarvatt reminded me: are we going to be building the agp modules into the maverick kernel?08:58
apwRAOF, do we need to be, i forget already, so many discussions at UDS08:59
jcristauthere doesn't seem to be another way to ensure agp init happens before drm init aiui09:00
RAOFapw: It eliminates a class of bugs where the drm module gets loaded before the agp platform driver and breaks.09:00
RAOFThere's at least one launchpad bug, let me find it.09:00
Sarvattapw: it's only a problem on laptops supported by fglrx at least09:01
apwi did think that at least the intel driver had a link to the AGP driver to make it load first as a dependancy09:01
jcristauapw: intel is easy, there's only 1 chipset09:02
jcristauso you can just load intel-agp and be happy09:02
jcristaufor non-igp, not so much09:02
Sarvattnouveau has it worse off by far regarding laptops getting hot09:03
apwyeah i see i915 depends on intel-agp directly09:03
apwSarvatt, and nouveau is kms only i assume09:04
RAOFRight.  If you're lucky the card gets initialised to the lowest power state by the bios; that's what happens on my laptop.09:04
apwoh dear, what a disaster kms is in .32 ... "but its pretty"09:06
RAOFWell, nouveau has never had power management.  I don't think nv does, either.09:08
tseliotI *think* I read that nouveau it's starting to get power management09:08
RAOFMan, my bandwidth up to launchpad sucks.09:09
RAOFThere haven't been any power-management related commits for nouveau yet, and I haven't seen a branch implementing it.09:10
RAOFHeh.  Ben Skeggs commits from the future.09:10
* tseliot has suddenly become a fortune teller :-P09:12
RAOFalf__: https://edge.launchpad.net/~raof/+archive/mesa-egl/+packages ← they haven't built yet, but I see no reason why they shouldn't.09:28
Sarvattpulled 7.8-gles into origin/ubuntu and installed the gles and egl pc's, lets see if this builds :)09:34
Sarvatti want to play with the demos too09:36
alf__RAOF: Thanks!09:37
SarvattRAOF: you  uploaded to lucid?09:38
SarvattRequested 'libdrm_intel >= 2.4.19' but version of libdrm is 2.4.1809:39
Sarvatt7.8-gles branch doesn't even build09:49
RAOFBalls.  Oh, well.  One lucid libdrm backport coming right up.10:00
Sarvatthas rendercheck been debianized?11:43
RAOFOh, curses.  I should really have bumped the dpkg build-depends for mesa.  Oh, well.  That's now Monday.12:25
Sarvattmight be better to just --enable-egl --enable-gles1 --enable-gles2 to get the headers and libEGL and drop gallium for now12:34
RAOFAs long as you're not building from 7.8.1, yeah.  Those options don't exist in mainline.12:35
Sarvatthuh?12:35
Sarvattoh I see12:36
RAOFThey're probably in the 7.8-gles branch, and they're in master.12:36
RAOFAnyway, *this* build will probably work :)12:36
RAOFAnd with that, I disappear.  Like a phantom, into the night.12:37
Sarvatt7.8-gles doesn't build, and the openvg lib isn't there in master12:38
Sarvattdone like 30 builds now trying to get things working12:38
Sarvattwell your original one is working, I just want .pc's for mesa/demos :D12:41
Sarvattsee ya RAOF!12:55
Sarvattwell, packaged up rendercheck for the heck of it, i'm not sure about the license though (probably why it isn't in debian yet)12:56
Sarvatt2 files are MIT/X11, the rest are - http://pastebin.com/DBkfk3TR12:58
Sarvattis it acceptable to say make get-orig-source targets for some packages that are basically always going to be vcs snapshots because of infrequent releases? packaging up rendercheck and it looks like it hardly ever has releases even though it's been around since 2004, intel-gpu-tools is the same way14:30
Sarvattwas thinking about something like this - http://paste.ubuntu.com/440869/14:34
Sarvattnot sure if there's more files I should exclude from the newly packed orig.tar.gz though14:35
Sarvattautom4te.cache?14:35
Sarvattoops minus the rm snapshot-date at the end there14:36
Sarvattopenchrome could really use a get-orig-source target14:38
C10uDhello, i have two similar issues in two different systems17:55
C10uD1) low end machine running 10.04 with vesa driver (s3 card). once X is started i can't switch to VTs or shutdown/reboot because the screen corrupts17:56
C10uD2) high end machine with nvidia-current closed driver, VTs aren't working. the rest is all fine17:56
C10uDany clue on this?17:56
Sarvattwell debianized that for the heck of it - http://sarvatt.com/git/cgit.cgi/rendercheck/18:25
SarvattC10uD: how long have you waited for a VT switch to happen with nvidia-current?18:25
Sarvattit's taken me close to a minute before..18:25
SarvattC10uD: for both cases I'd try doing a echo "blacklist vga16fb" | sudo tee /etc/modprobe.d/blacklist-local.conf && sudo update-initramfs -u to see if its any better18:27
C10uDi think almost a minute, i'll try again.. i'm asking because i wanted to see if with the new beta driver i could get any improvement18:27
C10uDthanks Sarvatt i'll try18:27
SarvattC10uD: did you install the new beta driver from nvidia.com?18:27
C10uDnot yet18:27
Sarvattthats a recipe for disaster and it doesn't work on anything newer than karmic18:27
Sarvattuse this PPA instead - https://launchpad.net/~ubuntu-x-swat/+archive/x-updates18:28
C10uDoh, thanks for the info then, btw i was more interested in the problem 1) :p18:28
C10uDi'll wait for a new nvidia18:28
Sarvattthe new nvidia is in the PPA, drivers from nvidia.com aren't compatible with lucid or newer and probably wont be for a long time18:28
Sarvattto downgrade back to the lucid ones when you have x-updates activated if you don't like the newer beta drivers, just sudo apt-get install ppa-purge && sudo ppa-purge -p x-updates ubuntu-x-swat18:29
C10uDbad nvidia :) thanks for the link though, i watched the good ol' nvidia-vdpau repo for updates but no luck for lucid..18:29
Sarvattany reason why you are using vesa with s3?18:30
bjsniderthat's because the driver is in the x-updates ppa18:30
Sarvattthe guy working on nvidia-vdpau is helping us do the x-updates :)18:30
* Sarvatt points at bjsnider18:30
bjsniderjerk, not guy. i prefer jerk18:31
C10uDSarvatt, in this system i don't really need a graphics card, so i just moved the xorg failsafe conf18:31
Sarvattwell if vesa is causing problems which is does it might be worth using xserver-xorg-video-s3 instead :D18:31
C10uDbut, is the x driver capable of corrupting the screen after x is killed? (x noob here)18:32
C10uDanyway, now i'll try moving back to auto-recognizing of video card18:32
Sarvattpretty sure vesa is capable of that, yeah. vga16fb/plymouth might be adding an additional layer of screwed up on top of that too :)18:33
C10uDi'll try asap then18:34
Sarvattjust remove /etc/modprobe.d/blacklist-local.conf and sudo update-initramfs -u again after if blacklisting vga16fb doesn't help18:34
Sarvattwhat GPU do you have thats screwing up with the nvidia driver?18:34
C10uDnvidia 940018:35
Sarvattbest bet would be to boot the nvidia machine up and run ubuntu-bug xorg and paste the link after you submit it here so we can see the logs18:35
Sarvattis it a mobile one? one of the hybrid gpu's?18:35
C10uDnope, plain 40$ desktop18:36
Sarvattah18:36
bjsnider9400 was onboard18:36
C10uDi am doing some potentially bad stuff in grub though, such as telling acpi_enforce_resources=lax and setting GRUB_GFXMODE=1280x72018:36
Sarvatti've seen people with 9400M in macbooks unable to vt switch is why i asked18:36
C10uDbjsnider, thanks for your ppa though, it helped a lot when i wasn't running lucid :P (even if vdpau was (IS) a little screwed though, seems(ed) like it's not vsync'd)18:37
C10uD NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)18:38
SarvattC10uD: its also possible you have some cruft left behind interfering with things, would be able to see that right away if you did a ubuntu-bug xorg and filed one18:38
Sarvattwell ubuntu-bug nvidia-graphics-drivers would be more appropriate18:38
C10uDmind if i update the drivers first?18:39
Sarvatthopefully it wont reject the bug because of unverified packages if you do :)18:39
Sarvattif it does just do it via ubuntu-bug xorg18:39
coz_Amaranth,  do you have a link to the one report on compiz + intel you had reported on a week or so ago?18:40
C10uDanyway, i put the GRUB_GFXMODE thing in grub because plymouth broke up (i think i was still in ubuntu beta) and 1080p didn't seem to work18:40
SarvattC10uD: yeah you arent gonna get a pretty splash with the nvidia binary drivers, i wouldn't even bother18:41
C10uD720p was almost nice :p18:41
Sarvatti think the text mode splash when you blacklist vga16fb looks better personally18:41
Sarvatt720p 16 color splash...18:42
bjsniderC10uD, the ppa is stil relevant even with lucid's packages but i spend more time on the cutting-edge multimedia ppa now18:42
Sarvatttheres a way to use uvesafb with the plymouth framebuffer renderer but its a pain in the butt to set up just for a 5 second splash18:43
C10uDyes, in fact i was tempted to remove all plymouth plugins18:44
bjsnideris somebody here using kde?18:45
Sarvattjust blacklist vga16fb and remove splash from the boot stanza, removing all the plugins will probably break things :)18:45
Sarvattthe text renderer once you blacklist vga16fb aint bad at all though, just a black screen with ubuntu 10.04 in text on it and 4 dots :)18:48
C10uDpackages installing... thanks for the tip, i'll try it18:49
Sarvatti need to try the blob with acpi=off, odd nouveau 3D works fine but both karmic and lucid are screwed up and i know karmic's nvidia-185 wasn't screwed up before18:57
C10uDSarvatt, the trick worked great here (nvidia), thank you very much :) i'll try the other system asap19:04
C10uDSarvatt, the vga16fb trick worked also in the other system! many thanks!19:24
Sarvattno worries, vga16fb is evil :)19:24
C10uDindeed :(19:27
knomehey, any ideas how to restrict my wacom tablet to other monitor in lucid? i'm totally stuck...20:24
=== schmidtm_ is now known as schmidtm
Sarvattknome: Option "ScreenNo" "n" ?21:50
Sarvatthmm, what is this.. Create a new source package recipe on code.edge.launchpad.net21:50
brycehyeah I noticed that myself21:51
brycehrecipe21:51
brycehsounds yummy, I wonder what it is21:51
Sarvattmmm bzr help builder21:53
Sarvatti'm warming up to bzr so friggin much, if only it wasn't so darn slow21:53
Sarvattnice being able to handle git repos in bzr natively, and just bzr pull to git pull and bzr push to push it21:54
Sarvattoh wow, my mesa packaging branch +  lp:~vcs-imports/mesa/master....21:55
brycehyep21:57
Sarvattniiice, you can just use upstream git + merge only packaging from ubuntu in one recipe21:58
Sarvattthought you'd need a packaging only branch but nope21:58
Sarvatthmm guess i would nest a packaging branch inside the other instead of merge packaging since its only packaging21:59
Sarvattneed to figure out the recipe to get the version names decent22:00
Sarvattfound a good guide, woot https://wiki.kubuntu.org/DailyBuilds/BzrBuilder22:00
Sarvattdoesn't look like you can use git sha's in the version, just bzr revno's :(22:01
brycehsweet22:04
Sarvattwoot you can use git, i had a year old version installed and not the bzr-builder in the archives22:05
Sarvattgit revision numbers i mean22:05
Sarvattoh jeeze you have to basically replace debian/rules in the recipe?22:14
Sarvattgiving it a shot - https://code.edge.launchpad.net/~sarvatt/+recipe/mesadailytest22:38
Sarvattmesa over bzr = pain..22:41
Sarvattcould be worse, gcc or the kernel..22:42
Sarvattneed to dig into the code to see how to use git revisions in the version, its undocumented in man22:43
Kangarooohello https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test theres step 1 1.  Add the apt sources.list lines shown below to your /etc/apt/sources.list, but command deb http://ppa.launchpad.net/ubuntu-x-swat/x-freeze-test/ubuntu jaunty main   doesnt add that22:57
Kangaroooanybody alive?23:06
Kangaroooso maybe step 1 needs to be removed or added comment that its needed for step 2 or that with ver. 10.04 that package is already in universe23:07
Kangaroooalso this doesnt work..   4.  `sudo INTEL_DEBUG=batch /etc/init.d/gdm restart` it gave some erro http://pastebin.com/G4UCuFpS23:08
SarvattKangarooo: that PPA isn't meant to be used any more, nothing in that would even be installed in anything newer than jaunty23:15
Sarvattdisabling it now23:15
Kangarooobut since to that page links page with is linked in page about newest bugs and i filled one bug and wanted to do this test also.23:16
Kangarooothen some steps could be modified?23:16
Kangarooothat package intel-gpu-something is also in universe so step 1 can be removed and step 4 changed to "sudo service gdm restart"23:17
Kangarooofrom https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes i used first link Xfreezes that goes to https://wiki.ubuntu.com/X/Troubleshooting/Freeze and and end theres info about this page https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test23:18

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