/srv/irclogs.ubuntu.com/2008/09/02/#ubuntu-x.txt

tjaaltonpwnguin: if you have input-hotplug, evdev steals the input devices (if they have mouse/kbd capabilities) unless other drivers have fdi files for them, so yes, input devices in xorg.conf is generally not working anymore05:39
tjaaltondexconf might need an update05:39
tjaaltonum, should05:39
wgrantShouldn't dexconf go away?05:39
tjaaltonthere are some quirks left05:40
tjaaltonkvm/ps3 stuff05:40
wgrantAh.05:40
wgrantIs there currently a way to make input-device properties persistent besides hacking support into g-s-d?05:41
tjaaltonbryce: ajax said that the server shouldn't poke acpid at all anymore :)05:41
tjaaltonwgrant: not that I know of05:41
wgrantUnfortunate.05:49
brycetjaalton: then how is it that the server is issuing warnings when acpid isn't present?05:49
wgrantBut I guess it should all be exposed in capplets eventually.05:49
tjaaltonbryce: I mean that the code should be removed altogether.. "shouldn't poke acpid in the future" :)05:51
brycetjaalton: ahh.  Is there an easy way to disable it without requiring major surgery, or should we leave it 'til intrepid+1?05:52
tjaaltonwgrant: well, xrandr isn't persistent either05:52
wgranttjaalton: True.05:52
wgrantg-s-d handles that now, doesn't it?05:52
tjaaltonbryce: I haven't had a look.. upstream would like patches, so if it makes in 1.6..05:52
tjaaltonwgrant: yep05:52
brycetjaalton: ah ok.  well let's go with my patch in the meantime.05:54
tjaaltonyep, sure05:54
bryceI forgot I had today off05:55
tjaaltonhow unfortunate :)05:55
bryceso all that git fussing wasn't needed until tomorrow ;-)05:56
brycebut on the plus side I got all my alpha-5 stuff in (well, xorg still needs uploaded)05:56
bryceand I implemented a quirk system for -ati for AGPMode quirking05:57
tjaaltonreally? how?05:57
bryceI used the same approach as -intel, but made it also account for the hostbridge's PCI ID.  airlied and alex said it depends on both05:58
tjaaltonah, right05:59
brycethere's other factors that play into it though, so maybe more should be accounted for, but it's a start05:59
bryceprobably should be ok for laptops that don't have involved BIOS options05:59
brycewhich I'm guessing is going to be like 95% of the cases ;-)06:00
tjaaltonyeah06:00
tjaaltonbryce: what about applying xserver commit 5e847c1d4fc30a0d263a?06:58
tjaaltonit would at least fix bug 26197706:59
ubottuLaunchpad bug 261977 in xorg-server "nv is chosen even if it doesn't support the card" [Undecided,Confirmed] https://launchpad.net/bugs/26197706:59
tjaaltonand make the failsafe-stuff simpler06:59
tjaaltonthen we could also add patches to first try nvidia/fglrx if they are installed (but maybe this needs TB ack?)07:01
* bryce looks07:17
tjaaltonthe last fallback would be vesa for x86 etc07:19
brycehmm07:24
bryceyeah I can see how this'll help when patched for nvidia/fglrx.  I am not sure I see how this helps in general though... but upstream obviously accepted it, so...07:25
tjaaltonif the "optimal" driver fails, it'll try the next one, and finally the fallback07:26
brycewill it?  I don't see the failure handler07:27
tjaaltonit has been there AFAIK, but not working07:27
brycewell in any case I can see that better fallback handling is the direction this goes07:28
bryceit looks like something else is needed in addition to this to do that07:28
bryceanyway, +1 for including this patch.07:28
tjaaltonok, I'll add it and test how it goes07:29
tjaaltonthe fallback thing07:29
bryceI don't think we need a TB ack to add something to load nvidia/fglrx if they're installed - I think it's a general principle that if the user installs something, then it's safe to assume that they want it, and to go ahead and "just work" from there07:29
brycehowever obviously we should get working fglrx and nvidia before that ;-)07:30
tjaaltonI'm just thinking about if it has negative PR implications07:31
tjaaltonbasically it would claim that we support the drivers, while we can't07:31
tjaaltonor maybe we can draw the line somewhere between "we'll allow it to autoconfigure" and "you should report your crashers upstream" :)07:32
brycewould we accept that patch if fglrx and nvidia* were demoted to universe because the foss drivers were good enough?07:33
tjaaltondunno.. it's problematic since the free driver is always installed07:35
tjaaltonso if you want to use the nonfree one, it should be on top of the driver stack to try07:35
wgrants/universe/multiverse/, I hope.07:37
tjaaltonyes07:37
tjaaltonthey could be demoted, because they're no longer part of lrm07:37
pwnguinplus, it doesn't mean anything special anymore like it used to07:40
pwnguinyou previously had to enable universe repos07:40
tjaaltonyep07:40
wgrantYou still have to enable multiverse, don't you?07:41
wgrantI hope...07:41
tjaaltonalso, tseliot would be able to upload directly :)07:41
pwnguinit does mean that any joe motu can upload07:41
tjaaltonthat rarely happens07:41
pwnguinsomething that's basically in use everywhere and affects everything07:41
wgranttseliot it's a MOTU.07:42
wgrant*isn't07:42
tjaaltonoh, duh07:42
wgrantHow'd I manage that, I wonder.07:42
tjaaltonwell, not yet anywya07:42
tjaalton-way07:42
tjaaltonevery motu should know to stay away from nvidia* :)07:42
pwnguini can imagine one of two scenarios07:43
wgrantIf we have MOTU who touch it inappropriately, they shouldn't be MOTU.07:43
tjaaltonright07:43
pwnguini guess theres already a few kernels in universe07:44
wgrantThis is proving to be unfortunately common, but that's another story.07:44
pwnguinbut nvidia is more popular than say -rt07:44
wgrantI don't think main exists just to keep some packages out of our reach.07:45
pwnguinwell, it's supposed to denote some level of canonical annointing07:45
pwnguinannointedness?07:45
bryceessentially, we say we provide ongoing security fixes for stuff in main, but not universe07:46
wgrantThat's all it means, right.07:46
wgrantCan Canonical guarantee updates for blobs? No.07:46
bryceright07:46
pwnguinwould canonical refuse to update a blob found to be insecure and fixed?07:47
tjaaltonso, I'd say that by not hardcoding the driver in xorg.conf would be better in the end, since then the fallback has a chance of working, which is more useful for the blobs anyway07:47
brycetjaalton: sounds good07:48
brycepwnguin: generally what I've been told is that doing SRU's of fglrx/nvidia is hardly ever going to be acceptable since we can't verify the source changes07:49
pwnguinhow about07:49
pwnguinwe put nouveau on the top of the stack07:49
tjaaltonthe only setting the nvidia's have in xorg.conf is NoLogo.. (71/96 has some AIGLX-stuff too)07:49
pwnguinthen nvidia07:49
pwnguinthen nv07:49
pwnguinPR solved07:49
tjaaltonpwnguin: there is no usable nouveau07:49
brycea security fix *might* be ok, but generally the blogs are released with a bunch of fixes, not just one cherry picked thing07:49
tjaaltonrelease07:49
tjaaltonif there were, I'd be all for it07:49
pwnguinbryce: oh right, you werent around for the last time nvidia had a remote exploit07:50
tjaaltonpwnguin: it was fixed07:50
pwnguintjaalton: yes it was07:50
tjaaltonafter edgy I think07:50
tjaaltonor was it breezy07:51
brycesounds nasty07:51
pwnguinjavascript crafted to exploit a video driver?07:51
pwnguinnasty doesn't begin to describe the horror07:51
tjaaltonheh07:51
pwnguinin such a situation, if canonical can't provide a fix, i'd almost say upload a new package that just removes it07:52
pwnguintjaalton: there's no usable nouveau, or no usable nouveau in Ubuntu proper?07:55
tjaaltonpwnguin: both. debian-experimental has, but they also have a libdrm snapshot07:55
pwnguinmy laptop power cable is inthe mail07:56
pwnguintjaalton: rihgt07:56
pwnguinRAOF has a ppa07:56
tjaaltonyes, he's co-maintaining the d-e stuff07:56
pwnguini havent tested it it recently, but it seems like it'd at least be a statement of support and cooperation07:56
tjaaltonI don't think we have the manpower to support it.. upstream wont, that's known :)07:57
tjaaltonthey don't want users yet, developers are fine07:57
pwnguinnouveau, or d-e?07:57
tjaaltonnouveau07:57
tjaaltonwhen they can use stable drm interfaces and put out a release, the situation changes07:58
pwnguinof course07:58
tjaaltonnow that the drm release management has been reshaped, there's hope that nouveau will catch up too07:59
tjaaltonmy words07:59
tjaaltonthe GEM/TTM mess didn't really help either08:00
tjaaltonbut that's mostly done now I guess08:00
pwnguindoes something bad happen if nouveau driver isn't found? i thought it'd fall back to the next available driver08:00
tjaaltonright, it should08:01
tjaaltonnote that I haven't tried it yet08:01
pwnguinheh08:01
pwnguinit just seems like a token nod to their efforts that costs nothing, gets them a little, and gives you something to say when people ask why nvidia is picked over nv08:02
tjaaltonyes, but when nouveau is better than nv, it'll be installed in favour of nv, and we are facing the same problem08:03
pwnguinoh. hrm08:03
tjaaltonyou install nvidia by yourself so you'd expect it to work08:03
tjaaltonby the next LTS we'll hopefully have good FOSS drivers so we can kick nvidia/fglrx out of the door completely :)08:04
pwnguinthe only reasonable option is order of quality, but nobody wants to hear that08:04
tjaaltonintrepid+1 could have 3D support for all the latest ATI chips08:05
pwnguinim not so hopeful about 3D on nvidia. there's a plan and like one dude last i looked08:05
tjaaltonyes it's more problematic08:06
* bryce squints and wishes real hard for nVidia to disappear08:07
pwnguinfrom my interactions with fedora users, apparently Canonical just needs to spend money to make it disappear, like Red Hat does08:09
brycehaha08:09
pwnguini wish i was joking08:09
tjaaltonthey should just open up08:10
pwnguindamn 7.0B market cap08:10
pwnguin51 percent will be hard to buy08:11
jcristaupwnguin: well, RH does a lot of work on X upstream. can't say that's true of canonical.08:11
pwnguinwhat?08:14
pwnguinwell,08:14
pwnguindave left, seemingly on not great terms08:14
pwnguinerr08:14
pwnguindaniel08:14
tjaaltonand about to leave nokia for...08:14
pwnguinoh?08:15
tjaaltonlater this fall08:15
tjaaltongoing back down under, don't know what to work on08:15
pwnguinhmm. tough one to guess. intel, or RH08:15
pwnguinmaybe he can finish his degree ;)08:16
tjaaltonanother PhD on XI?08:16
tjaalton:)08:16
pwnguinbachelors08:16
tjaaltonah :)08:17
pwnguinhis resume lists like a year of college08:18
tjaaltonyou know him personally?08:20
pwnguinnope08:20
pwnguinbut i can read his website08:20
tjaaltonheh08:20
tjaaltonI know one australian chick that was at our school as an exchange student in -94/95, do you happen to know her?-)08:21
pwnguinlook08:21
pwnguinim awake during the aussie time zone08:22
pwnguinbut thats a personal failing, not an indication of where i live08:22
tjaaltonoh damn, sorry :)08:22
brycehehe08:22
pwnguinlast i checked, kansas wasnt an australian province08:22
* wgrant annexes pwnguin.08:22
pwnguinwgrant: from what i hear, it wouldn't be much different08:23
pwnguinits gotta be a hell of a move, from australia to finland08:25
tjaaltonhmm so when alice fell through the hole, she ended up in brisbane?08:25
brycekangaroos and wallabies for instance08:25
tjaaltonwell we have polar bears running wild08:25
tjaalton(not)08:25
brycetjaalton: I think you mean dorothy and a tornado08:25
pwnguinheh08:26
pwnguinhis mastery of american culture is still better than my mastery of finnish08:26
pwnguinbut thank you for the translation08:26
brycejust put on a steel helmet with horns, you'll fit in fine08:26
pwnguinwell, parts of my family came from denmark and russia08:27
tjaaltonman, I thought alice was the one who said "I think we are not in Kansas anymore" :)08:27
pwnguinalice was british08:27
tjaaltonduh08:28
pwnguinor at least european08:28
bryceand she had a rabbit fetish08:28
pwnguini dont think "kansas" existed when it was written08:28
tjaaltonthat's what you get for not seeing old classics08:28
pwnguinyou've missed nothing08:28
tjaaltonthat line is so familiar to me because of Rainbow'08:29
tjaalton's Finyl Vinyl08:29
tjaaltonnot because I saw the movie :)08:29
brycekansas existed - had just finished sparking off the civil war or some such08:29
bryceok I'll shut up now08:29
tjaaltonoh and climate wise it's getting better here, local warming and such08:30
tjaaltonor was it global08:30
pwnguinheh08:30
pwnguinwell, john brown did raid a union armory08:30
tjaaltontoo bad that the winters are just wet08:30
pwnguinto attack the south08:30
pwnguinhe's memorialized in our capital building08:33
pwnguinbible in one hand, rifle in the other08:33
tjaaltonthat's so modern08:33
pwnguinhttp://images.google.com/images?q=john%20brown%20mural08:34
tjaaltonmoses!08:34
pwnguinheh, it beats the time they put an indian on the top of the dome, and used a noose to hoist it08:34
tjaaltonheh08:36
tjaaltonuploaded xorg-server to my ppa to test the autoconf stuff09:43
Hobbseehey there - have people reported regressions with compiz and the intel driver, with locking the screen making the computer freeze, and never bringing up a password dialogue?09:53
tjaaltonHobbsee: that's a kernel problem09:54
tjaaltonand yes, I've seen that myself09:54
* wgrant solved it by using metacity.09:54
Hobbseetjaalton: ahhh, thanks.09:54
Hobbseetjaalton: do you know if people are looking into it, or?09:54
tjaaltonbut with .27-2-generic, it seems to work09:54
Hobbseethat was what i had, and it definetly wasn't working for me.09:55
tjaaltonwhat chip do you have?09:55
tjaaltonbryce: your acpi patch is broken :) http://launchpadlibrarian.net/17229928/buildlog_ubuntu-intrepid-amd64.xorg-server_2%3A1.4.99.906-2ubuntu3.1_FAILEDTOBUILD.txt.gz09:56
tjaaltonmaybe it's easier to just not log anything09:57
Hobbseetjaalton: Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)09:58
tjaaltonHobbsee: ok, mine is 965 and it works fine now, even after a suspend cycle09:58
bryceoh, s/acpi_warning_msg_time/acpi_warning_msg_timer/.  guess I should have compiled that one ;-)10:00
Hobbseetjaalton: ah, it's https://bugs.edge.launchpad.net/bugs/262605 apparently.10:00
ubottuLaunchpad bug 262605 in xserver-xorg-video-intel "[intrepid] X locks up or crashes when screensaver activates" [Undecided,New] 10:00
tjaaltonbryce: ok, will do10:02
tjaaltonHobbsee: yes, I'll reassign it to kernel10:02
Hobbseetjaalton: thanks.  didn't want to fiddle with it myself, and get the wrath of the kernel guys in my direction.10:03
tjaaltonI'll point ogra to that bug10:03
tjaaltonprobably some drm funkiness10:05
wgrantIsn't DRM implicitly funky? Isn't that why it's being killed?10:08
tjaaltondepends what DRM you mean :)10:11
bryceX11, the land of overloaded acronyms  :-P10:12
wgrantThe kernelly Xy thing.10:12
tjaaltondirect rendering manager, yes10:12
tjaaltondidn't know it was being killed though :)10:12
tjaaltonreworked maybe, but it'll always be too complex for me to grog10:13
wgrantWhere do TTM and co come into the equation?10:13
bryceTTM -> GEM10:13
tjaaltonthe memory manager is a part of drm10:14
wgrantAh.10:14
brycewe *might* have GEM for intrepid.  I was helping benc with it earlier but don't know the current state of things10:14
Ngtjaalton: interesting that the new kernel fixes it for you10:53
NgHobbsee: do you see that too?10:53
NgI can't test for a while, my laptop just left for a trip to Scotland to be repaired :(10:53
* wgrant tests.10:54
wgrant(i915 here)10:54
HobbseeNg: where new kernel == -2?10:54
NgHobbsee: yeah10:54
HobbseeNg: that's the first place i see it, but i went straight from .25 to .2710:54
Ngoh10:54
Ngfail ;(10:54
Hobbsee(so i don't know if -1 had the problem)10:55
tjaaltonI'll try to reproduce with -110:55
tjaaltonalso, usplash works with .2710:56
Hobbseeyes, surprisingly!10:56
Hobbseeit's nice to see it agai10:56
Hobbseen10:56
tjaaltonmaybe they added v86d to the initrd10:57
NgI manually install v86d and it updated the initrd and all that changed was that X refused to start10:57
Ngsaying that it couldn't operate in framebuffer mode10:58
wgrantWell, that failed.10:58
wgrant-2 from 12 hours ago doesn't even suspend on i915 when compiz is running.10:58
tjaaltonwell, can't reproduce with -1 either10:59
tjaaltoncompiz was updated recently..11:00
tjaaltonnope, not the compiz update. it only un-blacklisted mobile ati11:16
tjaaltonwow, now it blanked again13:12
tjaaltonwith -213:13
tjaaltonNg: do you think bug 258923 is fixed now with .27?13:23
ubottuLaunchpad bug 258923 in xserver-xorg-video-intel "Black VGA output on Intel G45 (aka x4500hd)" [Undecided,New] https://launchpad.net/bugs/25892313:24
Ngtjaalton: I've never plugged anything into the VGA output on mine. I could dig around for a VGA cable and try, I'm pretty sure my TV has such an input13:25
Ng(I literally own zero monitors at this point ;)13:25
Nglaptops and digital TVs for the win :)13:26
* tjaalton <3's the 24" benq :)13:26
tjaaltonNg: oh and thanks for trying it out13:30
tjaaltonNg: what about bug 258925?-)13:31
ubottuLaunchpad bug 258925 in xserver-xorg-video-intel "Horizontal lines on Intel G45 (aka x4500hd) output" [Undecided,Incomplete] https://launchpad.net/bugs/25892513:31
* Ng looks13:33
NgI think I know what that is13:33
Ngok the mouse jumping thing mentioned in that is not related, I see that on everything, and it happens to a lesser extent on login on hardy afair13:34
Ngbut the black lines thing I think is kernel dependent13:35
Ngif I booted my X300 on hardy's kernel with intrepid userspace, I got loads of inch-long horizontal black lines on the screen13:35
tjaaltonthe mouse-jumping is soon fixed, with the same patch that should fix flickering13:45
Ngnice13:49
wgrantIs this mouse jumping the thing where the cursor freezes and jumps to the bottom right by a few cursor-heights, then recovers?13:58
tjaaltonrecovers when you touch the mouse, yes13:58
tjaaltonannoying as hell13:58
wgrantHmm.13:59
wgrantMaybe not identical to what I see, then.13:59
wgrantMine will continously jump.13:59
wgrantUntil it has finished logging in.13:59
tjaaltonjcristau: looks like the autoconfig patch didn't work right, no fallback-mechanism or something missing: bug 26197713:59
ubottuLaunchpad bug 261977 in xorg-server "nv is chosen even if it doesn't support the card" [Medium,Incomplete] https://launchpad.net/bugs/26197713:59
wgrantIt used to just do it once while gdm was starting.13:59
tjaaltonit does it every time a gtk app starts13:59
wgrantRight.14:00
wgrantThat sounds plausible.14:00
tjaaltonso you can demonstrate it yourself by running xrandr -q14:00
tjaaltonand then touch the mouse14:00
wgrantThat doesn't affect my mouse.14:00
wgrantIt just shows some apparently uninitialized textures for a frame or two.14:01
tjaaltonah14:01
tedgIt is a known bug to have X start up and not have a keyboard/mouse?  Then if I restart X it's all happy.18:56
tedgI'm guessing that it's not finding HAL on first start.18:57
tjaaltonright18:57
tjaaltonknown18:57
tedgOkay, then I'll be quiet :)18:57
tjaaltonhal should be started earlier..18:57
tedgWell, yes, but X should detect when HAL starts also.  That's easy to do with DBus.18:58
tjaaltonI've never seen that though, but there are bugs about that18:58
tedgIt happens to me on every clean boot.  I'm not sure if there's anymore debugging I could provide, but if so, I'm all for it :)18:59
jcristaupretty sure patches to detect when hal starts would be accepted19:01
* tedg has fear of X, he always makes sure there's at least 2 levels of abstraction between him and X at all times :)19:05
jcristaui just do that for xkb19:06
brycetedg, chicken!19:58
brycetedg: actually X code is just plain C and fairly well documented.  Easier than Inkscape ;-)19:59
brycewell, "fairly well" might be a stretch.  But more documented than Inkscape's code ;-)20:00
tedgbryce: I think it comes down to: "What happens when I mess up?" -- "Can't draw" vs. "at a terminal prompt"20:14
brycebawk bawk bawk20:15
tedgbryce: Why don't you just go do the patch I want and show me up :)20:15
bryceah, but then we miss the valuable learning experience for you20:16
tedgHow much work have you done with DBus?  I'd really like you to learn more about "the future" (tm).20:16

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