/srv/irclogs.ubuntu.com/2009/06/15/#ubuntu-x.txt

Sarvattsheesh, device detection in drivers is such a mess02:47
Sarvattapw: new nouveau kernel isnt working for me :(03:01
Sarvatt[   79.549480] nouveau 0000:05:00.0: display fifo hung :(03:02
Sarvatt[   79.565710] nouveau 0000:05:00.0: nouveau_fifo_free: freeing fifo 203:02
Sarvatt[   82.565011] [TTM] GPU lockup dectected on engine 2 fence type 0x0000000103:02
Sarvatt[   82.566471] nouveau 0000:05:00.0: PFIFO_CACHE_ERROR - Ch 2/7 Mthd 0x1ffc Data 0xffffffff03:02
Sarvattthen a few thousand lines repeating :D03:02
Sarvattoh i see, want calling nouveau.modeset=1 for that kernel. guess you cant use it any other what than in KMS with the kernel option :D03:09
hyperairhmm i wonder how well geforce4 mx support is in nouveau at the moment O_O03:24
Sarvattlooks like it supports every mx :D03:58
Sarvattugh, wasn't thinking, apw's kms kernel is versioned higher than 9.10 so alot of ati people on karmic probably just got a rude awakening to a non working setup since we dont have the drm for it03:59
hyperairSarvatt: no 3d =(04:41
Sarvatttheres 3d!04:41
hyperairthere is?04:41
hyperairbut not for the lower models, right?04:41
Sarvattas long as you dont mind glxinfo being the only thing you can run lol04:41
hyperairat least the nouveau status matrix didn't show any 3d support at all O_o04:42
Sarvattahh not sure04:42
hyperairbah!04:42
hyperairi'll be staying with my old outdated blob for the time being then04:42
hyperairno KMS for my desktop =(04:42
=== crevette__ is now known as crevette
crevettesuperm1, hey, I seen bluez has udev manager now http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=03971a2d726bc9a8630b2419508235a2920eb19f16:20
crevettethanks for pushing this uptream16:21
superm1crevette, yeah, as soon as the udev rules show up to match it, we should be in the clear16:23
crevette"in the clear"?16:24
superm1ready to disable the init script and switch to ondemand16:35
crevettesuperm1, I don't see any code that hook on udev, so I think the udev rules to start blutoothd is still necessary, but for stopping bluetoothd will stop by itw own16:44
superm1crevette, right i'm saying the init script would go away from rc.d16:46
crevettesuperm1, ah you would be extremist ? :)16:48
crevetteyou're true, karmic is for testing so let's test :)16:48
brycemorning17:13
jbarnesbryce: hi17:25
Ngbryce: when's the switch to kms on by default? :D17:40
bryceNg: the kernel team is working on it; iirc they need to implement a whitelist/blacklist before switching it on.  apw may have more info17:41
NgI say switch it on now and start collecting machines for the blacklist ;)17:42
Ngbut I can say that because a) nobody will whine at me, b) it works for me ;)17:42
Ngmy laptop has been up for a week now and apart from a couple of userspace things, I'm having a great time17:44
Ngat least two suspend/resume cycles a day, no X borkage or kernel borkage that I've noticed17:44
* hyperair has black screens caused by gnome-screensaver17:45
tjaaltonit was pain to use 2.6.28 on karmic, because 3g is broken on .30 :)17:45
bryceyeah it's quite solid on -intel for me as well.  we've had a few kms bugs in launchpad, but they're either solved now or nothing earth shattering17:45
tjaaltonit doesn't work too well with the intel snapshot17:45
brycebut the blacklist/whitelist stuff is more for catching ! -intel cases17:45
Nghyperair: where it suddenly switches the display off with dpms until you poke a key? I was wondering if that was g-p-m, but either way I'm seeing that17:46
bryceso we don't try to do kms on e.g. -nvidia, until it supports it17:46
hyperairNg: that's another bug.17:46
hyperairNg: the one i'm talking about is if close the lid, wait some time, then open it again, the screen won't come back on17:46
Nghyperair: it is, but upstream think it's fixed in gpm 2.27.217:47
hyperairno matter what you do17:47
Nghyperair: ah17:47
bryce(xkeyboard-config 1.6 merge uploaded)17:47
hyperair+you17:47
hyperairNg: it also happens if i close the lid faster than my notebook can suspend17:47
apwbryce, i wanted to check with you that my memory was correct, that the requied X bits to cope with and without KMS are enabled in karmic by default17:48
Nghyperair: ouch. are you sure that's gnome-screensaver's fault? it shouldn't be doing screen on/off stuff, should it?17:48
hyperairNg: i'm really really not sure, but someone on #intel-gfx said so17:48
Nghyperair: I won't pretend to know more than them ;)17:48
hyperairNg: he had slightly different symptoms.. i think just locking the screen for some time would trigger it17:49
hyperairNg: and i'm not willing to try just yet =p17:49
Ngheh17:49
hyperairssh works17:49
hyperairbut you can't chvt or anything17:49
james_w<-- one more satisfied KMS user17:53
bryceapw: yes should be good to go.  Only -intel will do kms so far, so if you have a whitelist, that's the only one to be whitelisted.  17:54
apwno lists right now, just want to make sure that making the default kernel turn it on, and all my combo kernels the same, that userspace will work17:55
apwat least for intel17:55
bryceyes, there's no other changes on the X side we need for -intel for kms17:56
bryceerf, horrible grammar.  hope that made sense.17:56
Ngso it should be on for intel for alpha3?17:56
bryceNg: yes17:56
Ng\o/17:56
NgI'll test 855GM shortly after that is published :)17:57
hyperairbryce: speaking of KMS stuff, are you noticing KMS spitting flames with usplash?18:19
hyperairi find it especially fun to stare at a blank screen for 20 odd minutes while waiting for my fsck to complete18:20
hyperairstarting from when i915 is loaded, ending when X is started18:20
brycehyperair: no I hadn't noticed that18:34
hyperairhmm18:35
hyperairhow strange =\18:35
=== ripps_ is now known as ripps
macohola. there was a wiki page for UXA testing where the graphics chips were laid out in a table and comments could be added. any intention of doing that again but for KMS?20:23
brycemaco -> https://wiki.ubuntu.com/X/KernelModeSetting20:29
macobryce, ahead of me as usual....thanks20:30
Sarvatthyperair: got a dmesg handy?20:45
hyperairSarvatt: for the black screen thing?20:45
Sarvattyep20:45
hyperairi don't remember seeing anything in dmesg20:45
hyperairlemme go poke my syslog20:45
hyperairhmm nothing20:46
hyperairlemme try reproduce the bug20:46
Sarvattcan I see it anyway even if theres no error? :D20:51
Sarvattwant to see the order of things and whats getting loaded in your case20:51
hyperairSarvatt: strange, i can't reproduce it any more O_o20:53
Sarvatti'll build you a new gnome-power-manager in a few minutes if you want, it wasnt updated for a long time there so ya got me to look and see it needed to be updated :) i dont see anything since karmic's that would fix your lid problem though20:53
hyperairSarvatt: wait, are we talking about the gnome screensaver one or the usplash one20:53
Sarvattusplash20:53
hyperairaah20:53
Sarvatti've been having to build that myself since i need hal enabled in it for things to work right on all my machines20:55
Sarvatt(g-p-m)20:55
hyperairi see20:56
hyperairSarvatt: anyway i'm not very concerned about the lid problem, since it's mostly intermittent and doesn't occur most of the time20:57
hyperairSarvatt: the usplash bit.. i'm pasting by dmesg, but looks like pastebinit's taking some time O_o20:57
hyperairhttp://pastebin.com/f4639d2c520:58
hyperairthere we go20:58
hyperairdon't mind the whole bunch of iptables stuff at the bottom. i was debugging my router's dhcp server20:59
hyperairand then i forgot to turn it off20:59
hyperair....okay suddenly my screen blanked out on me for no apparent reason21:02
hyperairand it won't come back on21:02
hyperairwtf?21:02
hyperairwell off i go to restart then21:04
* hyperair sighs21:04
Sarvattlooks like it might be picking your TV to output to until X starts hyperair21:06
hyperairthat's very strange21:08
hyperairoh and hell, i can't seem to get my comp to reboot now =.=21:08
hyperairreisub time i guess21:08
Sarvattnevermind [   17.703535] allocated 1280x800 fb: 0x007df000, bo ffff88007d5ed0c021:12
Sarvattyour drm isnt getting initialized until after i915, mine loads before and looks like this21:14
Sarvattoh he isnt here, wish i could turn part messages on on a channel by channel basis :D21:15
hyperairi'm back!21:16
Sarvatthyperair: edit your /etc/initramfs-tools/modules and add these on 3 seperate lines in this order21:16
Sarvattintel_agp21:16
Sarvattdrm21:16
Sarvatti91521:16
hyperairsudo vim /etc/initramfs-tools/modules21:16
hyperairoh shit21:17
Sarvattcould do i915 modeset=1 instead too21:17
* hyperair facepalms21:17
jbarnesSarvatt: has the xorg edgers kernel landed in the ppa yet?21:17
Sarvatt:D21:17
hyperairmodeset=1 is in /etc/modprobe.d21:17
Sarvattyeah it is in there, there is no metapackage for it yet though so its an opt-in thing to install it21:17
jbarnesSarvatt: great21:17
Sarvatti saw that bug report from the guy not having fbcon loaded, told him to install the kernel in edgers since it has KMS enabled in the kernel config so fbcon gets linked right21:18
Sarvatthyperair: after you're done you need to update-initramfs too21:20
hyperairSarvatt: yeah i'm running that21:20
hyperairSarvatt: by the way, doesn't i915 automatically pull in drm and intel_agp when loaded?21:21
cwilluoh where, oh where did my working suspend go?21:21
Sarvattits so much nicer having i915 built in because you get a high res KMS console like 2 seconds after the boot starts :D21:27
Sarvattbut usplash doesnt show the throbber/progress bar that way21:27
superm1is it still going to be possible to turn off modesetting if it turns out to be unstable on some of your hardware with i915.modeset=0 once it's fully built in?21:28
bryceanother question is if we build-in i915, would we have to do that for nouveau and radeon as well?21:29
tjaaltonI don't think keybuk wants those built in21:29
bryceand if so, then how do we handle if say -fglrx or -nvidia needs to unload those modules in order for them to do their thing21:29
bryceheya tjaalton21:30
tjaaltonhi21:30
brycecan the module loading be made to occur sooner so we can get the benefit without having to build them in?21:31
tjaaltonthey are not going to be included in the initramfs, because it would slow down booting up21:31
Sarvattsuperm1: about turning it off, you boot with "nomodeset"21:32
superm1Sarvatt, okay good21:32
Sarvattand no we wouldnt have to do it for radeon, thats a seperate option in the staging area on the kernel config and only applies to those21:33
Sarvatti dont think theres any chance in heck nouveau KMS is going to be in karmic, been testing it out the past few days and have it all working but its incompatable with radeon KMS right now and doesnt work at all with KMS disabled21:34
tjaaltonwhat happens if you remove the module from the console? :)21:34
tjaaltonwhile running kms21:34
SarvattDuke`: have you tried the updated xserver on xorg-edgers with no xorg.conf to see if it works right?21:39
Duke`Sarvatt: not yet, but I have to leave, sorry... I'll try tomorrow if I have time23:08
Sarvattno worries, was just letting you know i updated it and it should be fixed now23:08

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