<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PowerPC e5500, kernel crash, GT520, GT610" href="https://bugs.freedesktop.org/show_bug.cgi?id=88868#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PowerPC e5500, kernel crash, GT520, GT610" href="https://bugs.freedesktop.org/show_bug.cgi?id=88868">bug 88868</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Dmitriy from <a href="show_bug.cgi?id=88868#c16">comment #16</a>) > Created <a href="attachment.cgi?id=113026" name="attach_113026" title="incorrect image">attachment 113026</a> <a href="attachment.cgi?id=113026&action=edit" title="incorrect image">[details]</a> > incorrect image > > Dear Ben and Ilia. Thank you for your answers. > > There is no BIOS on our device. We have u-boot instead of it. But that patch > from Ben is necessary even in kernel of the version 3.18.5. Yeah, that's expected. The write needs to be posted to the card (not related to BIOS POST), and the extra read forces that to happen. > > The result of the monitor connection is in attach picture. The image is > incorrect. I tested both video cards GT520 and GT610, the result is the same. Welcome to the 1960's :) Neat picture... > > There are some errors in the initialisation log. > nouveau E[ PFIFO][0000:01:00.0] PBDMA0: (unknown bits 0x00004000) > nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 1 [DRM] subc 0 mthd 0x0000 data > 0x00000000 > ....... > nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device > nouveau 0000:01:00.0: registered panic notifier The full errors would be useful, esp after userspace starts up. > > Could the wrong work of video card be the reason of these errors? Or what > else is to be tested to find out the cause of wrong function. I suspect there are a few issues here. I'd start with turning acceleration off, that may magically "fix" things (but obviously also lose any sort of accel). You can use Option "NoAccel" "true" in xorg.conf or boot with nouveau.noaccel=1. I guess we may have to tell the card to byteswap stuff and/or use the proper reversed formats (e.g. A2BGR10 vs RGB10A2) when reading from "GART" space... and/or when uploading textures... that'd be annoying. Oh also I'd advise against using mesa's 3d acceleration, at least initially -- there are some well-known byteswap issues there (which may or may not have been fixed, the number of people using BE machines is vanishingly small).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>