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

RAOFIs anyone else having compiz problems with nvidia-180?  Mine seems to corrupt all the GL transformed textures.01:31
RAOFWoah!  Wobbly is *trippy*.01:31
anderskRAOF: I'm not (but now I almost wish I did :-P). 01:32
RAOFI wonder if istanbul will capture it.  It's truly nifty.01:33
RAOFo/` Istanbul is Constantinople / now it's Istanbul not Constantinople / been a long time gone / Constantinople o/`01:35
RAOFWell, that's disappointing.  Istanbul captures nothing but noise.01:37
RAOFMmm, temporary craziness.  Gotta love it.01:39
RAOFOh, even better.  Combined with that 'large windows sometimes don't update' XDamage bug.  Sweet.01:39
bryce_tjaalton: what's your thoughts on UXA for jaunty?10:37
bryce_I'm leery of it being still too unstable10:37
tjaaltonyeah, and there's the alpha-channel corruption thing10:39
tjaaltonand it crashes my X on resume10:39
bryce_tjaalton: I'm wondering if we should revert -intel back to 2.4.x given how many people complain about the performance10:46
bryce_tjaalton: what are your thoughts?10:46
bryce_tjaalton: I'm wondering if we should revert -intel back to 2.4.x given how many people complain about the performance... your thoughts?14:38
tjaaltonbryce_: the ddx driver doens't have much to do about it14:39
bryce_tjaalton: mesa?14:44
tjaaltonbryce_: xserver 1.6 depends on 7.314:44
tjaaltonI think it would be silly to go back :)14:44
bryce_tjaalton: then how to fix the performance issues?14:45
tjaaltonre-enable patch 107..14:45
tjaaltonand give KDE users the finger ;)14:45
bryce_we were seeing performance issues before that was dropped14:45
bryce_^weren't14:46
jcristaugem is probably responsible for at least some of the performance problems14:47
desrtAlexia_Death: you wrote a program that reads the serial port and injects events into the kernel input layer, or...?14:53
Alexia_Deathdesrt: No. I made a dbus daemon that adds and removes wacom devices.14:53
Alexia_DeathWhy the question?14:54
desrtjust wondering why my tablet isn't working and what needs to be done to make it happen out of the box14:54
Alexia_Deathdesrt: Jaunty with all the latest updates?14:55
desrtdownloaded alpha214:55
Alexia_DeathAnd what tablet?14:55
desrtit's an x200 tablet14:55
desrt(lenovo)14:55
desrtthe tablet shows in hal.  complete with the 'input' and 'input.tablet' capabilities and "Wacom" appearing in the product string14:56
Alexia_DeathIts a serial TabletPC device?14:56
desrtand the wacom fdi file is installed...14:56
Alexia_Deathyou have stylus then.14:56
desrtya.  the serial.device points at /dev/ttyS014:56
desrti suppose so14:56
desrtwhen i hacked up xorg.conf to manually handle this i added stylus and eraser sections14:57
Alexia_DeathFor taplet pc X xonf is OK.14:57
desrtdid you just try to tab-complete irc?14:57
Alexia_DeathYour serial device is not going anywhere.14:57
Alexia_Deathdesrt: ?14:58
desrt'xonf'14:58
Alexia_Deathconf14:58
desrtah.  right.14:58
desrti was sort of thinking that it would be nice, though, to have it working for jaunty out of the box14:59
desrtlike, if i go edit my xorg.conf, then it works for me14:59
Alexia_Deathdesrt: as to making it work out of the box, HAL should take care of enabling the stylus14:59
desrtbut anyone else who installs on a thinkpad ends up thinking 'ubuntu sucks'14:59
Alexia_DeathSo it works there.14:59
Alexia_DeathMy daemon can be used for per user conf14:59
desrtso perhaps i need to know a little more about how X deals with hal15:00
Alexia_Deathdesrt: if you are aup for making a configuration utility for it then thats good enough15:00
Alexia_Deathdesrt: its really simple.15:00
tjaaltondesrt: didn't you say it works OOTB as a stylus?15:00
desrtno15:00
desrtnothing happens at all out of the box15:00
desrti mean.. i can make some nice drumming noises, i guess...15:00
tjaaltonthen why does lshal show it? pastebin pleas15:01
tjaalton+e15:01
desrtbut the cursor isn't moving :)15:01
desrterm15:01
desrtthat's going to take a little while.  hold on :)15:01
Alexia_Deathdesrt: HAL should be able to make the stylus move if it recognizes it.15:01
desrtright.15:01
desrtso that's what i found odd :)15:01
Alexia_Deaththat is a bug15:01
desrtgood!15:01
desrtnow we're getting somewhere :)15:02
Alexia_Deaththe limitation of HAL is that it can add just one device15:02
Alexia_DeathSo no eraser.15:02
desrtit seems sort of like X should work around that15:02
Alexia_Deathyou need the daemon for that.15:02
jcristauAlexia_Death: that's the part i don't understand15:02
Alexia_DeathX does. with allowing DBUS conf.15:02
desrtlike.. this "one physical device = one XInput device" is an incorrect assumption in X, clearly15:02
desrthmm15:03
Alexia_Deathdesrt: Its an incorrect assumotion in HAL not X15:03
jcristauAlexia_Death: if the driver gets loaded, then it can add the other devices as it pleases15:03
Alexia_DeathAnd hall people have said they wont fix it.15:03
desrtAlexia_Death: how is HAL to know?15:03
jcristauso no need for a daemon or dbus or anything?15:03
Alexia_Deathjcristau: Im not a driver developer15:03
Alexia_DeathI knw how I can do it now.15:04
desrti could buy a brand new pen15:04
jcristaumeh. nobody is.15:04
desrtand bring it near my laptop15:04
Alexia_DeathBesides, I think its smart to keep that out of the drver15:04
desrtare you saying HAL should create a new device node for it when that happens?15:04
Alexia_Deathdesrt: pen is not the device15:04
Alexia_Deathdevice is the surface15:04
desrtabsolutely agree15:04
Alexia_Deaththat supports pens and erasers15:04
desrtthere is only one surface15:04
Alexia_DeathHAL can only give you support for pen15:05
desrtsupposedly i can use airbrushes and all sorts of other fancy stuff with this...15:05
desrtany wacom device15:05
Alexia_DeathAnd like I said, Ive talked to HAL people about it.15:05
Alexia_Deathairbrush is a kind of pen15:05
Alexia_DeathIIRc.15:05
desrtbut i would expect it to show as a separate xinput device15:05
Alexia_Deathserials are used for that I think15:06
Alexia_DeathThat support is iffi.15:06
Alexia_DeathI have to go for now.15:06
desrtk.15:06
Alexia_DeathIll be back in a little later.15:06
tjaaltonthe product mapping could live inside the driver, and initialize the devices it supports15:06
desrti'll boot up the live cd again and get lshal15:06
tjaaltonso yes, no daemon needed15:06
desrttjaalton: that's sort of what i was thinking15:07
Alexia_Deathtjaalton: DAemon is still needed fpr per user configuration15:07
desrtseems like it should be sufficient for hal to say "there's a wacom serial device here"15:07
jcristauAlexia_Death: why?15:07
Alexia_DeathYou dont expect all users to live with default conf do you.15:07
desrtand for X to create as many Xinput devices as are required from it15:07
tjaaltonAlexia_Death: wacom should just support input properties, then the settings could live in .xsession or gconf or ..15:07
Alexia_Deathdesrt: thats in the domain of wacom development. Talk to ping about it.15:08
desrttjaalton: you'd need something to bridge the settings over, in that case15:08
Alexia_Deathtjaalton: tablet properties need a UI and easy way to change.15:08
jcristaudesrt: that's called a desktop environment15:08
desrtlike gnome-settings-daemon or whatever15:08
Alexia_Deathits not a set once thing.15:08
desrtjcristau: ya.  exactly.15:08
tjaaltonAlexia_Death: yes, but the gui should be provided by the DE (in the long run, we discussed this already :)15:09
Alexia_DeathNice dreams guys15:10
tjaaltonhehe15:10
Alexia_DeathBut its not happening dor jaunty 15:10
tjaaltonno15:10
Alexia_Deathwhat i do works now15:10
jcristauthe ui is completely unrelated to how you pass those properties to the driver..15:10
desrtthis seems to be sort of similar to how gnome configures the keyboard layout and stuff15:11
desrtsomeone just needs to teach it about tablets :)15:11
desrtAlexia_Death: do you have a link to the stuff you wrote?15:12
desrtlshal -> http://pastebin.com/m49dbb4ad15:12
tjaaltondesrt: ok, then Xorg.0.log15:12
desrttjaalton: no mention of the word "wacom" anywhere in there15:13
tjaaltonsure is15:13
desrtsure isn't15:13
tjaaltonlines 318-33315:13
desrtin the Xorg.log i mean15:13
tjaaltonah15:13
tjaaltonwas this on jaunty?15:13
desrtjaunty alpha 2 livecd15:13
tjaaltonancient! :)15:14
desrt:)15:14
tjaaltonstill, I'd like to see it15:14
desrtok15:14
desrtgimme a sec15:14
tjaaltonI'm surprised that hal picked that up15:14
desrthttp://pastebin.com/mf39b2d015:15
tjaalton(WW) config/hal: no driver or path specified for /org/freedesktop/Hal/devices/pnp_WACf00415:15
desrtahah15:15
desrtgood catch :)15:15
desrtthing about that is that i have this /usr/share/hal/fdi/policy/20thirdparty/10-wacom.fdi15:16
tjaaltonfrom the wacom driver15:16
desrtit says that if input.caps contains "input" and product contains "Wacom" then input.x11_driver is set to "wacom"15:17
desrtand indeed, in the lshal output:15:17
desrt  input.x11_driver = 'wacom'  (string)15:17
desrt  input.x11_options.Type = 'stylus'  (string)15:17
desrtfor udi = '/org/freedesktop/Hal/devices/pnp_WACf004'15:17
tjaaltonyes, but I think they should be for /org/freedesktop/Hal/devices/pnp_WACf004_serial_platform_015:18
tjaaltonalso the capabilities15:18
tjaaltonthat way the driver would be assigned for it15:18
desrtthe one that has the linux.device_file15:19
tjaaltoneither kernel or hal boog15:19
tjaaltondepends where info.capabilities is coming from..15:19
desrtcould also argue that it's an X bug for not querying subdevices to find ports15:20
desrtand, as these things go, i guess probably there -will- be an argument about that :)15:20
tjaaltonwell, if it would list the capabilities for the subdevice, it'd just work15:20
tjaaltonyou can do test that by not matching info.cap..15:21
tjaalton-do15:21
desrtya.  i believe that it would work.15:21
desrtit's also not quite right, though15:21
tjaaltonat least it should be confirmed, so that it's not something else15:21
desrtbecause then it will assign the x11 driver to both nodes15:21
tjaaltonthat's not a problem15:21
tjaaltonit'll fail to use it for the first one15:22
desrti know it's not a problem... X will just say "dur... dunno what to do, so i ignore"15:22
desrtbut that's not right15:22
desrtseb128: this is why i switched to fedora!15:22
seb128desrt: good for you!15:22
desrtdamn X hackers breaking my tablet :p15:22
desrt(or hal hackers...)15:22
tjaaltonwhot has done the same already, so you lose :)15:23
desrtya.  i noticed.15:23
LLStarksyo.15:23
LLStarkshttp://ubuntuforums.org/showthread.php?t=105891515:23
LLStarkshopefully i can get a nice tester pool for you guys15:23
desrtX guys need to have a talk with HAL guys, i think15:24
desrtand figure out what the correct thing to be doing here is15:24
desrtany workaround done at the vendor level in the meantime will be more or less at the "quick hack" level...15:24
tjaaltonhal is just the messenger I guess15:24
desrtwhich is like, half of making a distribution anyway :)15:24
jcristaudesrt: you know, you could send a mail to hal@ today, and get that fixed :)15:25
tjaaltonright, hal is full of quirks15:25
tjaaltonhal-info15:25
tjaaltondesrt: but you should try removing the other match rule to see if it would work then15:26
desrti'll just bug david on irc :p15:27
desrtit's actually really hard for me to check if adding that match rule would make it work15:27
desrtso i'm gonna hal-set-property instead15:28
desrtdid you guys add nozap?15:29
desrtdidn't fix it15:31
desrti think X doesn't even look at the subdevice at all15:31
desrti'm gonna try adding the linux device path to the parent node instead15:31
tjaaltonyou need to restart hal15:31
desrti used hal-set-property15:31
tjaaltonoh15:31
desrti can't really make changes and restart... i'm running off of a livecd :)15:32
tjaaltonsure you can15:32
tjaaltonthe console is right there15:32
tjaaltonif it works15:32
desrtstill no love15:33
* desrt wonders what xorg log will have to say now15:33
tjaaltondon't bother, just pastebin it ;)15:34
desrtstill "no driver or path" even when i specify the serial path15:34
tjaaltonthere should be two entries for them15:34
tjaalton?15:34
desrti think X doesn't bother visiting the second one15:35
desrtpossibly because it doesn't have the input capability on it15:35
desrtlemme try adding that15:35
jcristauX just looks for input.x11_driver15:35
jcristauafaik15:35
desrtwell, it has that15:35
desrti'll try adding the cap15:35
jcristauthen it's missing input.device15:36
tjaaltonoooh, right15:36
tjaaltonit's looking more and more like a hal bug :)15:37
tjaaltonit doesn't seem to handle serial devices too well15:37
desrtahh15:38
desrtX looks for input.device key?15:38
jcristauyes15:38
desrtcan that be a serial device instead of an evdev?15:38
jcristaumaybe not15:39
tjaaltontry :)15:39
desrti got X to notice the second device node by adding the input capability, btw15:39
desrtbut it still fails due to no input.device :)15:39
desrtwtf15:40
desrtwell15:40
desrtsomething happened?15:40
desrtafter so many X server restarts X decided that i was bored of looking at brown15:40
desrtand put a nice purple pattern on my screen15:40
desrtlovely as it is, i can't read anything anymore and my system appears to have crashed15:41
desrti guess this can't be blamed on HAL bug :)15:41
tjaaltonso no console anymore?15:41
desrtnah.  completely dead15:41
desrtmy caps lock was flashing.  that's usually a bad sign.15:42
tjaaltonok15:42
desrtprobably some weird race in the video driver or something15:42
desrtand after so many restarts i finally hit it15:42
tjaaltona feature in the drm driver15:42
tjaaltonor so15:42
desrtyes.  feature.15:42
desrt"you've seen too much brown.  how about some lovely purple?"15:42
tjaaltonhow did you kill the server?15:43
desrteither the ubuntu livecd boot has gotten one hell of a lot faster or my new laptop is cooler than i thought15:43
desrti logged out15:43
tjaaltonok15:43
desrti think you guys enabled nozap15:43
tjaaltonno, upstream15:43
desrtah15:43
desrtthat is my preferred way of restarting X :)15:43
desrts/is/was/ i guess15:44
tjaaltonstill there to be enabled if you wish15:44
tjaaltonjust not on by default15:44
desrterm15:45
desrtok.  this is odd.15:45
desrtit's doing it again15:45
desrtthis is the second time, now, that it has happened immediately after me adding input.device15:45
desrti'm starting to suspect causation15:45
desrti have no idea how that would work, though15:46
desrtbut no capslock flash this time15:46
desrtmaybe X has changed the video mode, but not put anything on the screen15:48
desrtthen it goes to open the device and crashes15:48
desrtso i see the uninitialised screen -- purple15:48
desrtwhereas had it gotten past opening the device, it would have gotten to the part where it puts non-purple stuff on the screen15:48
tjaaltondunno15:51
desrti'm gonna try starting X under gdb over ssh15:51
desrtfecking network manager.  nm-applet appears to tear down the wifi when you take down X15:53
desrtgrrr15:53
* desrt stops caring for now and tries to get some real work done instead15:54
desrtmaybe later :)15:54
tjaaltonsure :)15:54
Alexia_Deathdesrt: http://a.death.pri.ee/watahod-0.4.1.tar.gz bonuspointd for figuring out without handholding how to use it.16:03
LLStarks|Boredhi. quick question. is there a reason why restarting x has been made impossible for laptops without a dedicated sysrq key?16:03
bryce_LLStarks, because people accidentally hit the key combo and it kills their x.  sysrq has little to do with it16:05
tjaaltonLLStarks|Bored: try printscreen16:06
jcristau'impossible'. heh.16:06
jcristausudo killall Xorg still works :)16:06
Alexia_Deathbryce_: its intentional that I cant kill my X with ctrl alt backspace? Awww... its such a usefull combo16:11
tjaaltonAlexia_Death: sure you can, it's just not enabled by default16:12
Alexia_Deathno clue how to enable it:P16:13
jcristaureading docs is hard16:13
bryce_Alexia_Death: read http://wiki.ubuntu.com/X/Config/16:14
Alexia_Deathjcristau: figuring out if its a bioug ora feature that it does not work is hard:P16:15
jcristauAlexia_Death: fair enough16:16
Alexia_Death:)16:18
jcristaumaybe i should add that in NEWS.Debian so i at least can beat people with that stick :)16:19
tjaaltonheh16:20
_MMA_In Jaunty, what nvidia driver should one use for a GeForce 6 series card?16:45
superm1_MMA_, jockey isn't ready in jaunty yet, but you will probably need nvidia-glx-180 or nvidia-glx-17716:58
_MMA_superm1: Ok. I think I got -180 installed and I *still* (since Edgy) cant get my proper res back on the HTPC. So I'm thinking I need to use a legacy driver or something.17:00
superm1_MMA_, i would recommend holding off until jockey is ready.  it will be able to tell you what driver you are supposed to be using17:00
superm1resolutions are detected via the EDID of your television set generally17:01
tjaaltonhmm so -180 supports the 6-series.. which means -177 should probably be dropped17:01
_MMA_superm1: And that's when my problems started. ;) My modline no longer worked. :)17:02
superm1_MMA_, if you have a bad TV EDID there are methods to add modelines.  You'll have to read the NV readme on their website for the exact options to let you do it though17:03
_MMA_superm1: Hell with it. I'll just stick with windows on the box 'till I build a new one. I've really put out tons posts and read alot to try to solve this. Gonna be easier to just buy new stuff.17:05
superm1_MMA_, the problem is most likely your TV set if the EDID is bad.  I'd check for TV firmware updates before you scrap all this17:05
tjaaltonand not get nvidia this time?-)17:05
superm1tjaalton, TV's with bad EDID's don't handle so well with any of the drivers from what i've seen....17:06
_MMA_tjaalton: Well they still work better than ATI. :)17:07
_MMA_And I'm unsure if Intel can do 1080p. Still gotta look at that.17:07
superm1at least for the moment the hardware acceleration you get out of NVIDIA drivers for XvMC and libvdpau and what not makes them more attractive generally for HTPC's.17:08
superm1until Intel supports VA-API that will probably be the case17:08
tjaaltonoh well, I'm happy to not need the craphics card (pun intended) on my htpc at all17:08
_MMA_superm1: Any of the jaunty players using XvMC and libvdpau now?17:14
superm1_MMA_, mythtv trunk does.  we may or may not be uploading it to jaunty though.  it's living in a PPA until upstream blesses it17:20
superm1_MMA_, I dont think ffmpeg is getting uploaded with the support until jaunty+1, so the rest of the apps will follow that17:21
_MMA_superm1: Ok. Maybe one day, I'll get this all sorted out. I can't even find a soundcard that works with SPDIF right. I have one, but have only had it work correctly once.17:22
* _MMA_ shrugs.17:22
LLStarksnote to self. holding down printscreen for 1 second yields 100 prompts.18:48
LLStarksalt+printscreen as well.18:49
LLStarksi can't access sysreq from this inspiron.18:49
LLStarksand if i can't  restart x on a whim, i'll be sad18:49
LLStarksalso, i want to punch the google earth devs for having atmosphere on by default.18:52
LLStarksi know it sounds hypocritical with regard to my stance on uxa, but jeez.18:52
tjaaltondoes alt+prtscr+h work from the console?19:03
tjaaltonshould print out the hotkeys that work19:03
=== maxb_ is now known as maxb

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