/srv/irclogs.ubuntu.com/2010/03/04/#ubuntu-x.txt

tjaaltonbryceh: there are some "can be synced" tags on the versions_current list, do you think that sync requests should be filed for those?05:10
tjaaltonhttps://wiki.ubuntu.com/X/PackageNotes05:10
tjaaltonhmm, slightly outdated though, there are more05:11
tjaaltonlibxi for instance is very much needed, there are some bugs filed against libxcb that this should fix05:12
tjaaltonhttp://bugs.debian.org/40044205:12
tjaaltonsuperm1: libvdpau can be synced too, it won't break anything?05:13
tjaaltonoh and lifeless should merge libx11 ;)05:14
tjaaltonok, list updated05:15
superm1tjaalton, although it's unlikely to break, it would be better to test it first05:25
tjaaltonsuperm1: ok, sure05:37
tjaaltonleft it out from the list05:37
superm1tjaalton, when trying to build even: The following packages have unmet dependencies:05:39
superm1  pbuilder-satisfydepends-dummy: Depends: x11proto-dri2-dev (>= 2.2) but it is not installable05:39
superm1is that not in lucid yet?05:39
tjaaltonsuperm1: hah, no. but on the list of syncs05:39
superm1tjaalton, okay well after all that's in place i'll try a build and look at it again05:40
tjaaltonthere was a sync request for the proto, confirmed it now so hope that it'll get synced soon05:44
* RAOF prepares to hang his system by trying to suspend.06:32
tjaaltonRAOF: nouveau suspend works fine for me07:10
tjaaltonit's nice how the user-switch is instant07:10
tjaalton+also07:10
RAOFtjaalton: Yeah; my laptop's just a bit of a problem-child.07:10
tjaaltonok, mine is a desktop07:10
RAOFIt *has* worked with nouveau suspend in the past, but it now goes through the motions and then fails to actually power down in any way.07:11
RAOFI think that no_console_suspend is the next step in debugging.07:11
mvocan we get ctrl-alt-f2 and friends back when in X-is-in-trouble mode please? the menus are all nice but much less efficient than just going to the terminal07:56
tjaaltondoesn't change the vt for you?07:57
mvoit didn't 07:58
mvobut maybe something else was wrong too - is it mean't to work?07:58
tjaaltonwhat hw? works for me on intel and nouveau07:58
tjaaltonof course :)07:58
mvonvidia (very new one)07:58
mvoaha .) I though it was removed for "safety" (just like ctrl-alt-backspace)07:58
mvoglad that its not :)07:58
tjaaltonheh, no. looks like it's missing ctrl for some reason?07:59
mvoyeah, it looks like my keyboard map is wrong too08:00
mvoso that may explain it, I look into it08:00
mvothanks08:00
tjaaltonnp08:00
* mvo was also missing nouveau-firmware for some reason08:03
tjaaltonnothing depends on it08:04
tjaaltonbut aiui it won't be needed for long08:05
RAOFIndeed; the .33 drm backport kernel also has the voodoo generator backported to it, too.08:06
mvoRAOF: nouveau is not working for me, gives me a "module nouveau not found" error - do I just need to wait for a new kernel with the .33 bits backported?08:35
tjaaltondo you have a -pae kernel?08:37
RAOFmvo: You could wait for the kernel, or add-apt-repository ppa:apw/red to get it now, or check that you've got the right linux-backports-modules-nouveau-lucid-FLAVOUR installed.08:45
mvoRAOF: odd, modprobe lbm_nouveau gives me the module and X starts but for some reasons its not loading it itself (linux-backports-modules-nouveau-lucid-FLAVOUR)08:48
RAOFHm.  Feel free to throw up your dmesg.08:50
mvo[drm] failed to load kernel module "nouveau" in Xorg.0.log - but I can wait for the new kernel to hit the archive, if -backports-nouveau is temporarely anyway its probably not worth spend (too) much time debugging08:51
mvonothing in dmesg releated to nouveau, just [lbm-drm] initialized 1.1.008:52
mvo(amd64)08:52
RAOFYeah.  If you feel like it, check out the apw/red PPA; if that doesn't work, we've got an issue.08:52
* mvo tries that now08:53
mvothe prospect of having free driver finally is just too tempting :)08:54
mvoRAOF: I'm much impressed, works like a charm now with the apw/red kernel09:02
RAOFGood to hear.09:02
apwmvo is that amd64 or i38609:04
mvoamd6409:04
mvoI can not switch to a vt anymore, but I had a similar problem earlier so it may be unreleated09:04
mvoand no compiz for me (G86 I think) - but that is probalby know, the 2d bits are fine though (so far)09:04
RAOFmvo: Can you post your dmesg; that sounds annoyingly like a bug I was sure the backport kernel would fix.09:04
mvohttp://paste.ubuntu.com/388159/09:05
tseliotyes, compiz shouldn't work09:05
mvo(uname -a http://paste.ubuntu.com/388160/)09:06
RAOFYeah, we don't have the 3D components in the main archive.  You can try the xorg-edgers PPA; lots of people have had compiz-level success with it.09:06
tseliotRAOF: my late congratulations on joining Canonical :-)09:06
RAOFtseliot: Thanks :)09:06
RAOFmvo: Can I have the rest of dmesg?  I think the error in there is plymouth, and unrelated.09:07
mvoRAOF: sure, sorry, give me a second09:07
RAOFtseliot: Oh, I was looking at some of the nvidia bugs, and bug 530481 sprang up as something you'd know about.09:07
ubottuLaunchpad bug 530481 in nvidia-graphics-drivers "nvidia-graphics-drivers break libgl horribly if hardware isn't nvidia" [Undecided,Confirmed] https://launchpad.net/bugs/53048109:07
RAOFI guess that's the new alternatives system making nvidia no longer *totally* break every other driver.09:08
mvoRAOF: mailed09:09
RAOFBut leaving libgl just broken enough that compiz thinks everything's ok, but is actually horribly broken.09:10
tseliotRAOF: yes, right. It looks like mplayer's build-dep should be fixed and there is very little I can do if people install the wrong driver09:19
tseliotI could make mesa's libraries have the highest priority (with alternatives) so that this doesn't happen though09:20
tseliotand users will get the nvidia libraries only if they switch to them manually (or through jockey)09:20
tseliotsuperm1: thoughts? ^^09:21
tseliotnote: this may break dist-upgrades09:22
tjaaltontseliot: but wasn't it meant to be able to install these side-by-side?09:23
tjaaltonhmm though in this case nvidia was probably enabled as well09:23
tseliottjaalton: yes but unless you choose the correct alternative automatic mode kicks in09:24
tselioti.e. the alternative with the highest priority wins09:25
tjaaltonshouldn't the free one have that?09:26
tjaaltonbecause there's no way to decide the highest priority among the blobs09:26
tjaaltonso even if you install the blog, you need to enable it09:27
tjaaltonthat way it doesn't break any setups09:27
tseliottjaalton: that's what I was suggesting but there's a use case we wouldn't cover09:28
tseliotthink of dist-upgrades09:28
tseliotusers with nvidia would be left with mesa's libraries09:28
tseliotinstead of nvidia's09:28
tseliotand even if we fixed this in update manager, things would still be broken for dist-upgrades from the command line09:29
tjaaltonand the hw manager would then suggest to enable the nvidia libs09:30
tjaaltonisn't that what happens?09:30
tseliotyes, if X doesn't crash09:31
tseliotnvidia would still be in xorg.conf09:31
tseliotbut we would have no kernel module or gl libraries for that driver09:31
tjaaltonthe kernel module would be loaded, no? or does the alternatives touch that too?09:32
tjaaltonthe ddx driver loads it09:32
tjaaltonthen X wouldn't crash, just that GL is broken09:34
tseliottjaalton: no, it wouldn't be loaded because of nouveau09:34
tseliotthe KMS moduel09:34
tseliotmodule09:34
tjaaltonuh, so how does nvidia make it not load nouveau?09:34
tseliotalternatives put a blacklist file in /etc/modprobe.d/09:35
tseliotthen we update the initramfs09:35
tjaaltonok then09:35
tjaaltonI give up :)09:35
RAOFBut there wouldn't be any other alternative for the blacklist file, right?09:36
tseliottjaalton: heh :-)09:37
tseliotRAOF: no, when you switch to mesa the blacklist file goes away and you (meaning jockey) will have to update the initramfs09:37
RAOFmvo: Have you done anything strange to your initramfs hooks?  It takes 26 seconds for nouveau to start to come up, which seems strange as it should be in the initramfs.10:26
mvoRAOF: nothing 10:26
RAOFWhat does your computer *do* in the 23 seconds before it starts udev?!10:29
mvoRAOF: I don't know, I was making tea - I can start it again and see if its reproducable10:30
RAOFI'm not entirely sure how to read that dmesg; could you just make sure that nouveau.ko appears in /lib/modules/2.6.32-16-whatever/modules.order, before vga16fb?10:31
RAOFmvo: Ah, well, if you were making tea!10:31
mvoRAOF: sure, I can do that10:33
mvoRAOF: I just checked, nouveau is way before vga1610:34
RAOFmvo: Finally... can you check that the output of “sudo update-initramfs -u -v” contains /lib/modules/2.6.32-16-generic/kernel/drivers/gpu/drm/nouveau/nouveau.ko10:49
mvoRAOF: running that now - it says its running the nouveau_kms hook, but that is it. the module is not mentioned in the output (i can provide the full output if you want)10:55
RAOFYes, please.10:56
jcristau'zcat /boot/initrd.img-$(uname -r)|cpio -t |grep nouveau' maybe10:58
jcristauif you want to know whether it's in the initramfs10:58
RAOFYeah, or that. :)10:59
RAOFIs -t really a synonym for --list?10:59
RAOFYes it is.  How strange.10:59
mvoRAOF: here it is http://pastebin.com/VjqCNVTA11:02
mvoRAOF: I need to leave for lunch now, but I will read scrollback11:02
araI am getting a lot of X crashers in a dell mini 9 (with an i945), is it known¿11:03
ara(lucid, of course)11:04
jcristauhard to say with 0 details11:05
RAOFmvo: Ok.  Now I ask you whether /usr/share/initramfs-tools/hooks/framebuffer exists, is executable, and if it's both of those, to pastebin its contents.11:11
RAOFmvo: I will be off to the more extended version of lunch in which I lie in a bed and sleep for 8-odd hours.  I shall also read scrollback  :)11:11
mvoRAOF: exists, executable, http://pastebin.com/UrGTFc9b is the content - is that outdated?11:12
mvoRAOF: heh :) 11:12
apwRAOF, yay i beat the docbook failure11:51
alkisgHow can I debug 100% xorg usage problems? (lucid, ancient ati)12:44
apwstrace perhaps?12:44
alkisgstrace xorg? ugh, any specific functions to look for?12:45
tjaaltoncheck with gdb where it's spinning12:46
tjaaltonor some profiler12:47
alkisgI think strace or gdb would be too much for my abilities - could you propose some profiler?12:47
tjaaltonnot really, google around12:51
alkisgThanks12:51
alkisgHeh, an update solved my 100% xorg usage problem with ati :)13:26
apwbryceh, ok, we have some thumbs up from RAOF for the new kernel, i am getting a whole set together in my red ppa, to make sure the interactions on upgrade work correctly ... so don't test with it till i tell you its all there ... need to get kernel lbm and meta sorted as a group, to make it a proper test13:51
Sarvattapw: * (pre-stable) drm/i915: blacklist lid status: Sony VGN-BX196VP, Dell    Inspiron 700m14:35
Sarvattthat's pointless isnt it?14:35
Sarvatttheres already a commit in .33 blacklisting all 8xx machines lid status14:35
Sarvatt...if i'm not mistaken, checking14:36
Sarvatthttp://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=commit;h=7b9c5abee98c54f85bcc04bd4d7ec8d5094c73f414:38
tjaaltonbryceh: expect a yet-another merge clash with xorg, since you didn't push the changes :)14:40
tjaaltonjust the changelog though, as usual14:41
Sarvattso yeah that commit is only in drm-intel-next only, wont make it back to stable until its merged I guess anyway14:50
superm1tseliot1, mplayer just needs to be fixed15:06
superm1dont worry about adding hacks for the fact that mplayer is doing it wrong15:06
tseliot1superm1: that's for sure15:06
Sarvattit wasnt even a PPA version of mplayer that was causing it but one in the archive??15:06
tseliot1superm1: right, at this point I would rather not make too many changes. I will only re-enable the nvidia installer15:07
superm1i think the problem is it's not just s/nvidia blah dev/libvdpau-dev/ because mplayer FTBFS right now15:08
superm1so siretart really needs to fix the FTBFS 15:08
tseliot1ah15:08
Sarvattwhat mplayer package is pulling in nvidia-current? i dont see anything on 2:1.0~rc3+svn20090426-1ubuntu1315:09
superm1it's the build-deps that pull it in15:09
Sarvattahh15:10
bjsniderhe has to refresh ffmpeg first15:11
bjsniderand x264, theora, vorbis, et al.15:12
bjsniderand then finally mplayer15:13
bjsniderand as far as i know none of this has been started15:13
bjsniderevery time i ask him about it he gets snippy15:13
=== ara_ is now known as ara
superm1bjsnider, yeah it's an annoying problem :(15:17
superm1i would think since he tries to maintain them in debian and ubuntu it would be stable in debian and more syncable though15:18
bjsniderthe debian version is in no sense upstream. it's horribly outdated15:19
bjsniderthe commands listed in his upstream-upgrade file for ffmpeg no longer work because there is no ffmpeg-debian to git pull from15:20
bjsniderso i don't know what is going on there15:20
bjsniderthe ffmpeg 5.1 release happened yesterday i think. i went in to their irc room and asked about it. they said debian/ubuntu wanted them to release it15:20
bjsnidereven though it's outdated code15:21
bjsniderdebian/ubuntu i assume refers specifically to siretart i would assume15:21
bjsnidersaid assume twice there15:21
superm1well there's more to the debian multimedia team than just him i thought15:22
bjsniderthat's older code than what is currently in karmic15:22
bjsniderwell, debian/ubuntu and specifically ffmpeg? who else is there?15:23
bjsniderthe 5.1 release notes specifically mentioned the linker bug that he fixed15:24
bjsniderit's also awfully late in the lucid cycle for a multimedia refresh15:29
superm1well if nothing else then, perhaps patching mplayer to not FTBFS15:31
bjsniderwhy not just delete it until it's fixed15:33
superm1that sounds like a waste of archive administration resources to me15:35
=== ara_ is now known as ara
tjaaltonhm, need to merge xorg since xorg-dev is uninstallable15:46
bjsniderdoes nvidia-current have a provides: nvidia-libvdpau or something like that?16:34
tseliotnope16:38
bjsniderare there provides at all?16:39
bjsniderdpkg must somehow think nvidia-current is related to nvidia-glx-xxx16:40
bjsniderotherwise i don't see why mplayer would pull it in16:40
tseliotwe have transitional packages for that16:40
superm1it pulls in the 185 stuff16:40
superm1which is transitional16:40
bjsnideroh, right hahahaa16:41
bjsnideri forgot about the transitional packages16:41
bjsniderthose darned things16:41
bjsniderwhat would happen if those didn't exist and someone tried to install mplayer?16:41
superm1probably wouldn't work16:42
bjsniderit would error out if the dependent packages weren't there i assume16:42
superm1but remember they're build-deps and suggests right now16:43
superm1not recommends or depends16:43
bjsnideri wonder what would happen during upgrades if the transitional packages weren't there16:43
bjsniderdoes nvidia-current have a conflicts: nvidia-glx-xxx?16:44
bjsniderwithout that i guess dpkg would fail due to duplicate files16:46
tseliotno, its doesn't conflict with that16:47
bjsnidertseliot, if someone manually installs nvidia-current, and does nvidia-xconfig to take care of xorg.conf, (bypassing jockey) are they missing anything?16:58
bjsniderit seems to me they're missing the glx part16:58
tseliotbjsnider: they will have to update the initramfs16:58
bjsnidertseliot, nvidia-current doesn't do that though dkms?16:59
tseliotbjsnider: ah, right it does that in the postinst16:59
superm1s/dkms/postinst/16:59
bjsniderbut are they using mesa or are they using nvidia-s glx?17:00
brycehmorning17:00
tseliotmorning bryceh17:01
tseliotbjsnider: the alternative provided by nvidia-current already has the highest priority so it should use Nvidia's gl libraries17:01
bjsniderah, so you do not in fact need to use jockey to install the driver17:02
superm1nvidia-xconfig is probably writing out a lot of unnecessary content to xorg.conf though17:03
bjsnideryes, i agree17:04
bjsniderat one point it was writing data that was incompatible with xorg and it was causing the driver to fail to load17:04
bjsniderit still writes the mouse/keyboard info to it17:04
superm1i almost think it would be better to provide a shim that uses xkit in place of nvidia-xconfig to avoid that17:05
tseliotyou can use jockey from the command line. That will give you a very minimal xorg.conf17:05
superm1that or ship an xorg.conf in nvidia-current as a conffile17:05
bjsniderbut nvidia-settings will still write that parochial data to it as well17:05
superm1i thought it was patched?17:06
bjsnideroh, i don't know what's happening in lucid, but all other versions do17:06
tseliotI patched nvidia-settings to use policykit, I'm not aware of any other work on it17:10
bjsnideryeah, so nvidia-settings will be writing gobbledygook data to xorg.conf17:10
tseliotsuperm1: shipping a conffile can make things ugly17:10
bjsniderbut it's nvidia's fault17:10
Sarvatthmm, just had an idea.. maybe we could add a pci id check in the nvidia-current postinst that checks for a 10de vendor id before it sets the nvidia alternatives17:27
=== radoe_ is now known as radoe
superm1Sarvatt, that doesnt help if you need to master an image with nvidia in it already 17:40
Sarvatthmm, if you did that though it wouldnt use nvidia GL by default in that case and activating it in jockey would end up running the postinst wouldnt it?17:43
Sarvattwe should be able to add the fglrx/nvidia to the autoconfiguration list at this point in xserver I imagine also17:46
Sarvattthat way we dont need an xorg.conf for nvidia anymore17:47
superm1bryceh had some patches for that, but they needed work17:48
brycehhmm?17:48
brycehyeah, tseliot was going to look into improving that but ran out of time17:49
Sarvattyeah I added those :) we can add nvidia to the nouveau patch easily, our problem at the time was that we were shipping a stock xorg.conf with no explicit driver specified so it only used the first device from the autodetection list17:49
brycehit gets complicated though.  for nvidia there are also some xorg.conf settings aside from specifying the driver, like the depth, and autoconfiguring the driver would not set those up automatically17:49
Sarvattonly the nologo option, dont really need that17:50
jcristauwasn't fglrx the one needing to have Depth set?17:50
brycehmaybe it was fglrx17:50
jcristau(which is incredibly stupid, but hey)17:50
Sarvattah nvidia has depth and Load    "glx" in it too but i didnt think they were required17:50
Sarvatti'll test it out in a bit17:51
brycehI seem to remember that at least many cards won't boot if depth is not specified17:52
brycehanyway, I believe with some work it could be hacked around server-side, but makes the size of the effort just beyond what seems easy to do quick17:52
Sarvattbuilding xserver now with nv swapped to nvidia in the nouveau default patch to test it out real quick, will be a few hours though because I'm out of the house with a spotty connection17:55
Sarvattthere seems to be an x client leak with chromium/flash/nvidia blob :(17:55
Sarvattrebooting to the new xserver without an xorg.conf now18:05
* Sarvatt crosses fingers.18:05
Sarvattit worked18:06
superm1i thought the problem was if you had an xorg.conf though, it doesn't use the proper fallback logic18:07
Sarvattor not! :D18:07
Sarvattload glx is required18:07
Sarvatthttp://pastebin.com/0nGXwtDX18:07
Sarvattthat was only during the jaunty and early karmic devel stage superm1 where there was a default xorg.conf with no specific driver specified but that was dropped a long time ago18:08
Sarvattso glx is not loading with no xorg.conf but 2D works fine18:09
Sarvattthat seems like a win to me, jockey installs the xorg.conf still and it'll still work without 3D if theres no xorg.conf for some reason18:11
superm1is there a way to get it to conditionally load glx if it's using nvidia18:11
Sarvattneed to dig into that more when I have some time, but this would make things basically work for people who install via a terminal instead of jockey (like me)18:12
jcristauthe server loads glx unconditionally18:13
superm1Sarvatt, you can install via a terminal using jockey, jockey-text -e xorg:nvidia-current18:13
Sarvattnice!18:14
Sarvattis that new?18:14
superm1i added it a release or two ago to jockey18:14
Sarvattsweet, thank you for that because I use that machine headless 99% of the time18:15
Sarvatthmm mesa is kind of screwed up now on intel, 4 glx visuals 6 glxfbconfigs and some 3D apps arent working18:19
Sarvatt(in edgers not lucid's packages)18:19
Sarvatthmmm18:36
Sarvatt  * Add 11_nvidia_suspend.patch: Re-enable chvt quirk for nvidia driver, to repair suspend with the current driver versions. (LP: #488720)18:36
SarvattI swear I tested that when I was looking into it and it didnt work on my machine18:36
Sarvattyay for a mesa upload at 3KB/second18:37
Sarvatttime to test out this drm backport kernel, the -14 drm backport kernel had all kinds of problems on my intel that a .33 kernel didn't have for some reason18:41
superm1bjsnider, https://lists.ubuntu.com/archives/lucid-changes/2010-March/007277.html18:45
Sarvattapw: might still want to enable the powersave=0 i915 module parameter default patch on -16, still have the hangs here after resume18:48
bjsniderwell, siretart has decided to go with a very conservative release19:43
superm1mplayer doesn't build-dep on ffmpeg though does it?19:44
bjsnideroh yes it does19:44
bjsniderit uses dynamic ffmpeg like everything else19:44
bjsnideri tried building the 5.1 release yesterday and it still had the vhook stuff in it19:45
bjsnidernot part of current svn code and hasn't been for a long time19:45
bjsniderbut whatever. he's the expert19:45
apwbryceh, RAOF, finally have gotten what i think is the upgrade packages for drm33.  all in my red PPA21:32
brycehapw, great thanks21:33
bdrungwill xserver-xorg-video-ati updated to version 6.12.191? this will fix the tearing bug #51484521:56
ubottuLaunchpad bug 514845 in xserver-xorg-video-ati "videos and window movements tear" [Undecided,Triaged] https://launchpad.net/bugs/51484521:56
brycehbdrung_, 6.13 just came out iirc; probably we'll move to that22:04
bdrung_bryceh: great22:04
brycehwe'll probably need a ffe though22:04
bdrung_bryceh: you can use my bug report for getting it accepted ;)22:06
bdrung_bryceh: the current version in the archives hurts my eyes (found no translation for augenkrebs)22:06
brycehbdrung_, no, there's not evidence that you tested the newer version and found it solved the issue, so it won't work as a base for a ffe22:07
brycehI don't know what augenkrebs is22:08
bdrung_maybe going cross-eyed (direct translation would be eye cancer, but this is meant metaphorically)22:09
bdrung_bryceh: i tested a snapshot from 2010-02-24, but i will explicitly test 6.12.191 or 6.13.22:11
bdrung_bryceh: according to http://www.x.org/wiki/radeon 6.13 is not yet released22:11
Trinity33hi anyone here?22:40
Trinity33knock knock........22:41
BUGabundono22:42
Trinity33i just found info somewhere that is i want to help i should come over :) so i got lucid alpha 3 q9000 quadcore ati hd4850 ddr2 4gb so where is that driver i have to test:) the last one i tested from open source included in lucid doesnt work so is there anything a=else i could do?22:43
Trinity33any other driver to check ?22:43
Trinity33catalyst 10.2 doesnt work in 2.6.3222:43
SarvattTrinity33: there is no catalyst for lucid to test yet unfortunately22:52
SarvattI'm kind of doubting there even will be one at this point..22:54
Trinity33why doesnt soemone make one? for me? nvidia is working in lucid22:54
Sarvattbecause its a closed source driver and only ATI can do it22:55
Trinity33the driver included in lucid doesnt work with hd4850 too it use to much cpu22:56
Sarvattit stinks because we really need time to work out the packaging issues like we did with the nvidia binary driver22:56
SarvattTrinity33: try booting with radeon.modeset=0 added to the kernel command line22:56
Sarvattthe 2.6.32-16 kernel should hopefully help with that a bit22:56
Sarvatti'm guessing you're complaining about how slow flash is with the radeon drivers? radeon.modeset=0 should help with that alot22:57
Trinity33im not that good with drivers and generally linux im beginner :) so if i have to change something u need to speak english or russian i tried open source driver in karmic 2.6.31.14 and it use lot of cpu too the same like in lucid in karmic i have installed catalyst and the cpu usage is between 0 and 2% with open source driver between 30 and 50% cpu22:59
brycehSarvatt, yes there will be an -fglrx22:59
brycehSarvatt, they always deliver it in time, but only just.22:59
johanbrDoes anyone know if it's possible with nouveau to detect a GPU lockup and do a reset (similar to what Intel does) ?23:10
brycehjohanbr, not afaik23:13
brycehat least not currently23:13
johanbralright, thank you23:14
Sarvattonly 965+ intel you should say :) it doesn't now but i imagine some of the newer hardware will be able to do it at some point because I'm pretty sure I remember the windows drivers doing it. nouveau is reverse engineered though so i wouldnt hold my breath for it to happen anytime soon if the blob doesn't already do it23:15
RAOFjohanbr: It would actually be pretty easy to implement that.23:32
johanbroh, alright :)23:32
johanbrso the nouveau people know how to "hot-reset" the gpu?23:32
RAOFIn some cases.23:32
RAOFOh, I was thinking more of “when you have detected a GPU lock up, tell someone so you can get a good bug report”.23:33
RAOFI'm not sure that being able to recover from arbitrary GPU lockups is easy.23:33
RAOFBut GPU lockups are currently detected, various errors are detected, and a subset of them can be resloved.23:34
johanbrI get them every few days, but I'm not sure how to get the debug information...23:34
johanbrI could ssh in from my phone, I guess23:34
RAOF#nouveau is likely to be a better resource for actual debugging.23:35
johanbralright, thanks23:37

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