=== yofel_ is now known as yofel | ||
=== Amaranth_ is now known as Amaranth | ||
brobostigon | good afternoon everyone. | 16:28 |
---|---|---|
brobostigon | https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/720468/comments/10 | 16:28 |
ubot4` | Launchpad bug 720468 in xserver-xorg-video-intel (Ubuntu) "[i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7f9c002d) (affects: 25) (dups: 21) (heat: 206)" [High,Fix released] | 16:29 |
brobostigon | the published fix seems to hve not worked. | 16:29 |
brobostigon | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/715096/comments/9 | 17:12 |
ubot4` | Launchpad bug 715096 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "[i945gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011) (affects: 18) (dups: 15) (heat: 216)" [High,Incomplete] | 17:12 |
brobostigon | its getting confusing now, as where put reports for gpu lockup's on intel, as there seems to be quite a few. | 17:13 |
brobostigon | can someone advise please. | 17:15 |
brobostigon | https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/720468/comments/10 | 19:17 |
ubot4` | Launchpad bug 720468 in xserver-xorg-video-intel (Ubuntu) "[i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7f9c002d) (affects: 25) (dups: 21) (heat: 206)" [High,Fix released] | 19:17 |
brobostigon | i amstill getting gpu lock up, even after the fix, but there are a few gpu lockup bugs revolving around intel. | 19:18 |
brobostigon | any advice. | 19:18 |
jcristau | http://intellinuxgraphics.org/how_to_report_bug.html | 19:19 |
brobostigon | jcristau: i followed all of that a few weeks ago, and then the bug i reported was reported as a duplicate of that main gpu lockup bug. | 19:22 |
jcristau | well then it's probably not the same | 19:22 |
brobostigon | 730099 was my original bug, | 19:24 |
brobostigon | howeevrm i see no point in reporting to that, if its considered a duplicate, and will be ignored. | 19:25 |
brobostigon | jcristau: so for it to be different can the bug i originally reported be un-duplicated. please. | 19:28 |
tjaalton | brobostigon: bug 715096 is still open | 19:40 |
ubot4` | Launchpad bug 715096 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "[i945gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011) (affects: 18) (dups: 15) (heat: 216)" [High,Incomplete] https://launchpad.net/bugs/715096 | 19:40 |
tjaalton | and your bug is a dupe of that | 19:40 |
brobostigon | tjaalton: so what do i do? | 19:41 |
brobostigon | tjaalton: and i have proved info onto that bug. aswell. | 19:42 |
tjaalton | brobostigon: is it the same with current natty? | 19:42 |
brobostigon | provided* | 19:43 |
brobostigon | tjaalton: with updates untill 10am this morning, yes, | 19:43 |
tjaalton | I don't see you mentioning that there | 19:43 |
brobostigon | https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/715096/comments/9 | 19:44 |
ubot4` | Launchpad bug 715096 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "[i945gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011) (affects: 18) (dups: 15) (heat: 216)" [High,Incomplete] | 19:44 |
tjaalton | yes, a link to another bug | 19:44 |
brobostigon | tjaalton: but that has the details of the dmesg dump etc | 19:44 |
tjaalton | better to post it on the bug yours is marked as a duplicate of | 19:45 |
brobostigon | so ie 715096 ? | 19:46 |
tjaalton | no | 19:46 |
tjaalton | oh, yes | 19:46 |
tjaalton | getting confused | 19:46 |
tjaalton | or report it upstream | 19:46 |
brobostigon | ok, let me copy that dmesg dump, showing the bug into that. | 19:47 |
tjaalton | attach it, don'αΊ— paste it inline | 19:47 |
brobostigon | attach a text file containing. | 19:48 |
brobostigon | that dump. | 19:48 |
tjaalton | yep | 19:49 |
brobostigon | ok. | 19:49 |
brobostigon | done https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/715096/comments/10 | 19:53 |
ubot4` | Launchpad bug 715096 in xserver-xorg-video-intel (Ubuntu) (and 1 other project) "[i945gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x02000011) (affects: 19) (dups: 15) (heat: 140)" [High,Incomplete] | 19:53 |
tjaalton | good | 19:53 |
brobostigon | so thats the one, i should file stuff to, if it happens again, and or reoccurs? | 19:54 |
tjaalton | yep | 19:55 |
tjaalton | and I think you should be able to undupe your own bugs if needed | 19:55 |
tjaalton | just open the bug and see the panel where it says it's a dupe | 19:55 |
tjaalton | and change that | 19:55 |
brobostigon | is there any need and or ppoint in doing that, as you said, i shouldreport to a different bug.? | 19:57 |
tjaalton | no, just saying | 19:57 |
brobostigon | ah, ok. thank you. i will note that down. | 19:57 |
tjaalton | you can check it out now, to see if I'm wrong.. | 19:58 |
tjaalton | don't need to commit the change, just check that you can delete the dupe info | 19:58 |
brobostigon | let me try and see if i can. | 19:58 |
tjaalton | it's possible that only members of the respective package team and members of ubuntu-bugs can do that, but.. | 19:59 |
brobostigon | yep, i cansee where, | 19:59 |
brobostigon | dont know if it will let me or not. | 20:00 |
tjaalton | is there a yellow "ball" in front of the "duplicate of bug..." line? | 20:01 |
brobostigon | yes. | 20:01 |
tjaalton | click it | 20:01 |
tjaalton | it opens a dialog where you can clear the bug field | 20:02 |
tjaalton | so that's how you do it | 20:02 |
brobostigon | got it, i have made notes. | 20:03 |
brobostigon | :) | 20:03 |
tjaalton | niice | 20:03 |
brobostigon | tomboy to the rescue. | 20:03 |
Eren | I've installed binary ATI drivers, 11.2. However, all the files are gone into /usr/lib/fglrx (including libraries, x modules, etc.) | 20:04 |
Eren | I've set module path to /usr/lib/fglrx on X, however, these modules in fglrx directory searches for libraries in /usr/lib/fglrx/ | 20:04 |
Eren | there are similar problems on the net with workarounds, but these workarounds do not work as well, any ideas? | 20:04 |
tjaalton | haven't used fglrx in years. besides, if you use the ati installer, all bets are off | 20:05 |
tjaalton | don't think we even try to support it | 20:06 |
Eren | I see from Xorg.0.log that "dlopen: libatiuki.so.1: cannot open shared object file: No such file or directory" | 20:06 |
Eren | whereas, this file is present in /usr/lib/fglrx directory | 20:07 |
Eren | I, at least, want to give a try :) | 20:07 |
Eren | tjaalton: what would you suggest for new-brand AMD E-350, with APU ? | 20:07 |
tjaalton | windows :) | 20:07 |
Eren | I just deleted it :) | 20:07 |
tjaalton | never heard of that one before | 20:08 |
tjaalton | i mean the chip | 20:08 |
Eren | http://www.phoronix.com/scan.php?page=article&item=amd_fusion_e350&num=1 | 20:08 |
Eren | some guys in ubuntu forums managed to get VAAPI work | 20:09 |
Eren | I cannot even start X server though :) | 20:09 |
tjaalton | well, natty should work according to that article | 20:10 |
tjaalton | no idea about vaapi | 20:10 |
Eren | "dlopen: libatiuki.so.1: cannot open shared object file: No such file or directory" | 20:10 |
Eren | that's the problem right now, I tried setting LD_LIBRARY_PATH, but no luck | 20:10 |
Eren | any way to set prefix for dlopen in x? | 20:10 |
tjaalton | sure, I just don't remember how / have never needed that | 20:12 |
Eren | huh, I'm stuck :) | 20:18 |
bjsnider | don't we have the latest fglrx in x-updates? | 20:36 |
bjsnider | it was sent in on dec 17. not sure if that's the latest or not | 20:38 |
tjaalton | probably not, 11.2 is from last month | 20:43 |
bjsnider | not sure why it wasn't updated | 20:44 |
Eren | I am still digging it, tbw | 20:48 |
Eren | if you are interested in updating the binary driver, I would like to test it | 20:49 |
Eren | https://help.ubuntu.com/community/BinaryDriverHowto/ATI needs updating as well | 20:49 |
tjaalton | it's a wiki ;) | 20:50 |
Eren | :) | 20:51 |
Eren | need to sleep.. | 20:53 |
Eren | good night all | 20:53 |
brobostigon | nos da everyone, sleep well. | 22:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!