Launchpad has imported 19 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=35457.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-03-20T06:24:50+00:00 Brian Visel wrote: This is a severe issue, that prevents me (and a decent number of others) from using accelerated graphics. This bug has the following behaviors: * Corrupts the displayed graphics of every running program (as far as I can tell). * Often corrupts the pointer graphics * Corrupts fonts * Corrupts the terminal display with noise from X, if you switch to a terminal * Exists in accelerated and unaccelerated modes, but is marginal when not accelerated. * Is made worse by KMS * Is made worse by Compositing. * Affects a rather large number of users (many with the rs690/x1200/x1250 cards, which are common in netbooks) The previous workaround has been to disable KMS, which I believe somehow caused the radonhd driver to be used (uncertain about this). Either way, it brought the garbage to a usable level, and still allowed acceleration. However, that is not the case now. Using nomodeset results in a non-accelerated desktop. Please let me know what pieces of information I should supply, and how I can be of assistance regarding this. Note that glxinfo currently (with kms disabled) reports me to be using SGI and Mesa. Direct Rendering is "Yes", but it's actually using software, yes?. Even with this totally different driver set, I still sometimes get the corruptions (particularly after a long time running). Is it possible that some fundamental thing (like a base memory address, or how much shared memory is to be used, or something) is being misreported and causing all these issues? This seems to be a very difficult bug to sort out, as it has been around a while. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/56 ------------------------------------------------------------------------ On 2011-03-20T06:30:11+00:00 Brian Visel wrote: Created attachment 44628 A screenshot that clearly displays corruption between program visuals Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/57 ------------------------------------------------------------------------ On 2011-03-20T06:40:35+00:00 Airlied-freedesktop wrote: /var/log/Xorg.0.log and dmesg with KMS enabled. Does your bios have an option for sideport RAM, do you know if you have sideport? Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/58 ------------------------------------------------------------------------ On 2011-03-20T15:05:49+00:00 Brian Visel wrote: Yes, I believe I do have sideport ram. In discussion in bug #25469, (A duplicate of bug #27529, which got marked 'resolved--fixed'), someone stated they have the same issue, and that they have the same model of laptop as myself, and that the sideport ram can't be disabled in the bios (which is true in my case as well). I am currently running xorg 1.10.0, with ati drivers from the git repo (xf86-video-ati), pulled yesterday. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/59 ------------------------------------------------------------------------ On 2011-03-20T15:07:25+00:00 Brian Visel wrote: Created attachment 44638 dmesg with KMS enabled Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/60 ------------------------------------------------------------------------ On 2011-03-20T15:08:21+00:00 Brian Visel wrote: Created attachment 44639 Xorg.0.log, KMS enabled Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/61 ------------------------------------------------------------------------ On 2011-03-20T15:51:36+00:00 agd5f wrote: Does: Option "ColorTiling" "False" in the device section of your xorg.conf fix the issue? This might be a duplicate of bug 33929. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/62 ------------------------------------------------------------------------ On 2011-03-20T18:11:05+00:00 Brian Visel wrote: No, that appears to have no effect. (thanks for taking time to troubleshoot this with me) Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/63 ------------------------------------------------------------------------ On 2011-03-21T16:38:40+00:00 Brian Visel wrote: read the 'severity' description in 'help', and updated this to a blocker. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/65 ------------------------------------------------------------------------ On 2011-03-21T16:53:31+00:00 agd5f wrote: The gart table buffer needs to be aligned to size (table address needs to be 512k aligned for 512 MB GART). I'm not sure if the Linux DMA API provides any mechanism to request that. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/66 ------------------------------------------------------------------------ On 2011-03-21T17:16:24+00:00 agd5f wrote: Created attachment 44674 check gart table align Can you try this patch and see if it prints an error when you load the driver? Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/67 ------------------------------------------------------------------------ On 2011-03-21T21:43:07+00:00 Brian Visel wrote: Unfamiliar with working with compiling the kernel, so it took me a while. The module loads without complaint, either to the terminal or to dmesg. I checked the strings in radeon.ko to make sure I had installed the right .ko file, and it's the right one. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/68 ------------------------------------------------------------------------ On 2011-03-26T23:22:20+00:00 Brian Visel wrote: Just to clarify, since there's been no activity on the bug, in case there was a misunderstanding: by "The module loads without complaint," I didn't mean that it was working properly, just that the module loaded. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/69 ------------------------------------------------------------------------ On 2011-04-16T04:43:52+00:00 krmolot wrote: It's a same problem? https://bugs.archlinux.org/task/23215?string=x1250&project=1&type%5B0%5D=&sev%5B0%5D=&pri%5B0%5D=&due%5B0%5D=&reported%5B0%5D=&cat%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto= https://bugzilla.novell.com/show_bug.cgi?id=678264 p.s. My computer is crash whis screen cooruption when GDM is start when KMS is enable (kernel 2.6.37). Together with kernel 2.6.38 in gxgears i see black screen. When KMS is disable it's switch to the software 3d rendering. Tested distros: Ubuntu 11.04, Arch notebook: eMachines D620, video: x1250 Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/72 ------------------------------------------------------------------------ On 2011-04-22T09:22:31+00:00 axel wrote: Hi Guys, do not know if you are aware but this issue affects a lot of netbooks built by the same company Gateway,Acer,Packard Bell. Its been plaguing me for over 2 years, like most people I disabled KMS to get it working in the interim or just did not use compiz. Problem is now Ubuntu is launching 11.4 next week ....with as you are aware Unity. Unity and any desktop affects will no no longer work because of this bug, as will all compix desktop effects!! We are about to get a "lot" of bad Ubuntu user experience with Unity next week. Is this going to be another argument for Wayland and justifies MS's controversial move? Can I assist in any way ? Lets prove him wrong. I have pulled in the latest main git repo and compiled the latest driver. Its an holiday in the UK I can dedicate a few days of my time to this if it helps? I can compile and add patches at your disposal. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/74 ------------------------------------------------------------------------ On 2011-05-08T15:30:54+00:00 André Oliva wrote: I also have this problem. In my case, the corruption is not in the form of horizontal lines; simply the area inside any window that requires 3d graphics is black or frozen. I use Ubuntu 11.04. Compiz simply doesn't start, and the same behavior for programs like Stellarium or the visual module in Python (that I use very often). This behavior was **not present** a year ago in Ubuntu < 10.04. 2D acceleration works well (as a workaround, I can use `export LIBGL_ALWAYS_SOFTWARE=1`, but of course that is not a solution because graphics are extremelly slow). The issue does not occur always. "Sometimes" I have an slow 3d acceleration (that I suspect it's really software rendering), and "sometimes" I have normal 3d acceleration (fast, smooth, as expected). I really don't understand when it works and when it doesn't work. If you give me instructions, I can help to clarify this. /var/log/Xorg.0.log has nothing strange. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/84 ------------------------------------------------------------------------ On 2011-05-28T12:20:28+00:00 André Oliva wrote: The bug that I reported in Launchpad was incorrectly marked as a duplicate of this bug. I filed bug 37679 here in Freedesktop about this issue. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/96 ------------------------------------------------------------------------ On 2011-06-02T20:07:01+00:00 Brian Visel wrote: >From Launchpad: Setting VBLANK_MODE=0 seems to delay the appearance of corruption. Example: Starting a regular, non-accelerated gnome-session, and then running: VBLANK_MODE=0 glxgears ..it takes a while (and some dragging of glxgears around the screen) before the corruption appears, whereas normally it would appear rather quickly. As noted before, the corruption isn't limited to the accelerated areas, and can happen when running a non-composited desktop under normal usage. Running openGL programs or compositing makes it appear very readily, though. I believe it was mentioned in the Launchpad bug, but not here -- Once corruption begins, changes in an X-Session can affect other virtual consoles (e.g., once corruption begins, start a slow-loading program, switch to a virtual console, and as the program maps its graphical components, the console graphics get corrupted). Hope this helps.. Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/101 ------------------------------------------------------------------------ On 2012-02-25T09:20:16+00:00 Stillcompiling wrote: I am a long-time sufferer of this problem. I have the Gateway LT3103u, which is I have not yet applied Alex's patch, but I recently tried playing with the gartsize and vramlimit options. gartsize seems to have no effect. However, setting the vramlimit to 64 seems (2 reboots later) to clear up the corruption. vramlimit of 128, 256, and 0 (0 is ignored) each result in corruption The card normally reports 384 MB of vram and 512 MB of gtt memory. Is it possible this computer is misreporting the amount of sideport ram? I read someplace that th x1270 can only have up to 128, but that there is some "Hypermemory" mumbo jumbo going on that adds some of your system ram to the mix. Unfortunately, the Gateway LT3103u has a terrible bios config. you can't change anything, and you can't see much of anything either. So, for the record: adding "radeon.vramlimit=64" to the kernel parameters in grub seems to alleviate the problem. I'm running gentoo amd64, kernel 3.2.6-gentoo and git mesa Reply at: https://bugs.launchpad.net/linux/+bug/556782/comments/121 ** Bug watch added: Novell/SUSE Bugzilla #678264 https://bugzilla.novell.com/show_bug.cgi?id=678264 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/556782 Title: [rs690m] Graphics corruption with ati x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/556782/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
