/srv/irclogs.ubuntu.com/2009/03/20/#ubuntu-x.txt

superm1bryce, i'm starting to think it makes sense to include some type of patch that would force fglrx to be the active graphics driver when installed given bulletproofx is entirely shot and you can't use radeon/radeonhd when it's installed..07:49
tjaaltonradeon should work, just not with DRI07:52
superm1well the majority of people won't know to put NoDRI or what not in xorg.conf tho07:53
brycetjaalton: I couldn't get radeon to work at all as long as fglrx was installed07:53
brycealthough I didn't try NoDRI07:53
tjaaltonok07:53
tjaaltonweird07:53
bryceI've been spotting various bug reports (including one where the guy deleted libdri.o to get radeonhd working again)07:53
tjaaltonmaybe the kernel module is hostile07:54
brycemaybe07:54
superm1well radeon and fglrx's kernel modules can't be loaded simultaneously afaik07:54
tjaaltonso radeon doesn't work at all without it then07:55
superm1oh how about adding modprobe options to radeon to rmmod fglrx 07:57
superm1if its loaded 07:57
tjaaltonit should be unloaded before the server starts07:58
tjaaltonso where exactly?-)07:58
superm1gah, that's unfortunate08:01
bryceone user thinks we should ship two versions of xorg with each ubuntu release, so we can retain backwards compatibility for an older fglrx that supports their r3xx card08:08
superm1oh that would be fun08:10
brycetjaalton: what's the status of the vblank stuff?  I've been seeing some scattered error messages mentioning vblank, is that just a stray warning?08:10
brycesuperm1: I laughed.  They didn't appreciate it though.08:10
superm1bryce, yeah from their perspective i suppose it looks like "ubuntu is breaking fglrx" rather than "fglrx isn't supporting the latest releases"08:11
tjaaltonbryce: yes, it's disabled by default in the dri driver08:12
tjaaltonwe'll all be laughing a year from now ;)08:13
RAOFWhen nouveau is the default nvidia driver, and radeon{,hd} supports all cards with 3d?08:13
bryceRAOF: that'll be an enjoyable day08:14
bryceRAOF: of course by then everyone will be owning GMA500's and wanting -psb working08:14
tjaaltonRAOF: even I am not that optimistic, meant that r6xx-> should be supported by the dri driver by then ;)08:16
tjaaltonbryce: hehe08:16
brycetjaalton: noticed most recently on https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/xorg/+bug/345714/08:17
ubottuUbuntu bug 345714 in xorg "[Mobile 4 IGC] X exits when switching ttys on 2.6.3" [High,Incomplete]08:17
bryceMar 19 22:42:15 laptop kernel: [ 4495.802798] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 008:17
tjaaltonI don't think the message is related, but best ask upstream what they think08:19
tjaaltonrelated to the crash..08:20
* bryce nods08:20
bryceI'll shoot it upstream next week.  Just need a bit more info from robbie.08:21
bryceI hate upstreaming to Intel with incomplete info, they always nitpick08:21
tjaalton:)08:23
macoanything change in -intel lately to explain why i cant enable compositing in kwin?09:27
bryce2.6.309:32
macoer...string to go with those numbers?  "new upstream version" or some such?09:33
bryceyep09:33
macowas that in the last month?09:35
tjaaltonthis week09:35
macooh, im not that far behind then09:35
macoya know, on finding out a chunk of functionality just disappeared09:36
tjaaltonwhich chip?09:36
tjaaltontry with a new user first09:36
macoi96509:37
macoSubsystem: 1043:826509:37
macook09:38
tjaaltoncompiz works on mine09:38
tjaaltonso doubt it's the driver at fault09:38
macoi did try "reset to defaults" on the kwin settings09:38
macothe message that came up said to check the X config09:38
macoand the compositing type09:39
tjaaltonsure, "blame someone else" ;)09:40
tjaaltoncheck the x log if dri is enabled09:44
tjaaltonglxinfo should reveal it too09:45
macofails on a new user too09:46
macodirect rendering: Yes09:46
maco(i assume thats what you mean?)09:47
tjaaltonyes09:47
macoi dont have uxa explicitly enabled anymore, but the default is to not enable uxa, isnt it? so that should make no difference?09:47
tjaaltonshouldn't09:48
RAOFWon't the software renderer _also_ return 'direct rendering: Yes' in Jaunty?09:51
macowell my xorg.conf currently looks like what dexconf outputs, except that it has a commented out 'Option "AccelMethod" "uxa"' line09:52
RAOFI suppose that check can pick up partially working, but broken.09:52
brycelook at OpenGL renderer string to see if software rendering is going on 09:52
tjaaltonmaco: just try compiz next :)09:53
macodarn, people that know i still have gnome installed09:53
maco:P09:53
tjaaltonI didn't, but apt-get works :)09:55
maco"desktop effects could not be enabled"09:56
macolately all the whining ive done while testing has been of the "good for you gnome-only people, but that totally breaks for people using kde and gnome!" variety09:57
crdlbmy new general-purpose 3d checker is glxinfo | egrep 'direct|software' :)09:58
macocrdlb: no lines matched for software09:59
tjaaltontry a daily live-cd, if it doesn't work, then I'll believe there's something wrong in the driver :) 09:59
maconote that the last few days' live cds have been over 700mb...09:59
tjaaltontoo bad10:00
crdlbdid you look at the compiz output to see exactly what failed?10:00
macono i just tried the appearances window that i hate...will switch consoles10:00
macothough i should point out: vt switching is broken more weirdly now10:00
tjaaltoncompiz --replace in a terminal10:00
macofrom the kdm screen on which the other user was logged in, i cant ctrl+alt+f7 back to here. it just keeps refreshing kdm. cant get from there to a tty either. even when i do it twice in a row10:01
tjaaltonuh10:01
tjaaltonyou don't have dri in the second sessionä10:01
tjaalton10:02
tjaaltonso you need to try it in the primary session10:02
macosoftware rasterizer detected: abortingaborting, falling back to /usr/bin/metacity10:03
macoi thought it just couldnt be in use in two sessions at once10:04
tjaaltonright, what I said :)10:04
crdlboops, I forgot -i :)10:04
macooh ok well that works...compiz does run10:05
* maco glares at kwin for lying10:05
crdlbwhat happened to multi-master drm?10:05
macoah! who made the compiz window switcher so busy?!10:05
tjaaltoncrdlb: WIP10:06
macohrm well then i guess i should go ask in #kubuntu-devel10:06
tjaaltonprobably so10:07
crdlbtjaalton: heh, it just seems like it should have gotten in by now10:07
tjaaltonthere's a wikipage on wiki.x.org about it10:10
tjaaltoniirc10:10
macoctrl+c'ing compiz didnt bring kwin back. and plasma died. and my keyboard stopped working.  adding "use compiz inside kde" to the list of things i shouldnt do10:15
tjaaltonthere's a wikipage on wiki.x.org about it10:17
macowell i dont think the kbd was the window manager's fault10:19
macothat happens from time to time10:19
tjaaltonuh10:19
RAOFHeh.10:20
tjaaltonthe previous comment was an error10:20
tjaaltonput the phone in my pocket10:20
maco?10:20
macothe "uh" or the wiki.x.org comment?10:20
tjaaltonwiki10:21
RAOFOK.  There's a nouveau-kernel-source package that'll build a drm module that's compatible with the driver in Jaunty in bzr.  Tomorrow shall be FFe filing time :/.10:28
macowont work19:35
macobah wrong channel19:35
macomy mouse missed19:35
jcristautormod: thanks for filing the savage bug.  uploaded to stable-p-u now.21:15
tormodjcristau: great21:15
tormodjcristau: btw, why didn't you use debian/patches?21:16
jcristaugit cherry-pick -x is faster :)21:16
jcristaufor stuff that's upstream, i tend to just do that21:16
jcristauand use debian/patches/ for stuff that either is debian specific or we need to keep longer term21:17
tormod_oops, solid lock-up on RV410 (compiz+googleearth)21:25
tormod_jcristau: ok make sense. I wondered if it be helpful to post a debdiff, but figured you would use git anyway.21:26
jcristautormod_: yeah with a bug to point the RMs at, it was just a matter of cherry-picking your patch, writing a changelog entry, waiting for an ack, and building the package :)21:27
jcristau(and the ack came very fast, so.)21:27
tormod_jcristau: yes, I was impressed how fast that went! I thought SRU on Debian would take months :)21:28
jcristautormod_: actually including it in stable will take more time, since that only happens at the point release. but the next one is scheduled for april 4th, so pretty soon too.21:30
tormod_let's see how long it takes in Ubuntu, with beta freezes and all that ;)21:31
brycetormod_: which bug is this?22:13
brycetormod_: if it's the pci by default bug, it's already in22:14
tormod_bryce: no, it's another22:15
tormod_bryce: just assigned it to you tonight: bug 29489922:15
ubottuLaunchpad bug 294899 in xserver-xorg-video-savage "No signal with Samsung SyncMaster 570s and ProSavage8 [patch]" [Undecided,Confirmed] https://launchpad.net/bugs/29489922:15
brycetormod_: uploaded22:21
bryceok, I'm supposed to be off work today so am going to try to spend the day away from the computer ;-)22:24
tormod_bryce: cool, as fast as Debian :)22:24
brycetormod_: touch base with slangasek on beta freeze permission (I already mentioned it to him) but I think this one should sail through fine22:25
tormod_bryce: I see. go away from screen22:25
tormod_bryce: just want to congratulate you (and tjaalton and others) for getting such an up to date xorg stack in Jaunty! rocks22:26

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