All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 17571] New: Nouveau and PPC64 issues
Date: Sun, 14 Sep 2008 09:39:43 -0700 (PDT)	[thread overview]
Message-ID: <bug-17571-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=17571

           Summary: Nouveau and PPC64 issues
           Product: xorg
           Version: unspecified
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: r.goyet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Running nouveau on PPC64 is a whole experience :-)

 - Running from git/master crashes X : "(EE) NOUVEAU(0): No known BIOS
signature found"

 - Removing nvidiafb and using only offb was suggested, done, but didn't change
a lot of things

 - Commenting { "PROM", load_vbios_prom }," in nv_bios.c fixed the first issue.

 - I was then back to the same state I was at a few weeks ago : the screen is
full of weird vertical multicolored lines.

 - Taking a screenshot with ImageMagick's 'import' shows a perfectly good image

 - Trying to go back to the console (killing X) would show a black screen

 - Adding "return;" at the start of the run_tmds_table function in nv_bios.c
mostly fixes the issu : the screen is now totally readable, even though some
artefact appear throughout the screen

 - Adding `Option "Randr12" "Off"' in your xorg.conf device section eventually
totally fixed the issue, letting me use nouveau on a PPC64 machine !!


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-09-14 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 16:39 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-17571-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-09-14 17:29   ` [Bug 17571] Nouveau and PPC64 issues bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-10 17:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-10 17:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-10 17:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-10 17:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-14  2:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 17:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17571-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.