From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91319] New: Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree
Date: Mon, 13 Jul 2015 00:34:05 +0000 [thread overview]
Message-ID: <bug-91319-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2151 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91319
Bug ID: 91319
Summary: Nouveau driver cannot extract FCODE ROM / DCB Block
from OpenFirmware Device tree
Product: xorg
Version: unspecified
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: psaisanas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 117079
--> https://bugs.freedesktop.org/attachment.cgi?id=117079&action=edit
kernel dmesg log & NVDA,BMP FCODE ROM
Hi,
When running a Powermac 11.2, (G5 Quad - powerpc64) with a Quadro FX4500
(NV47), previous kernels had no issue extracting the FCODE ROM / DCB block via
the OpenFirmware device tree.
Last vanilla kernel that i have compiled that seemed to work fine was kernel
3.18.16.
Normally, it will find the "BIT SIGNATURE" via OpenFirmware method.
However, when compiling a newer vanilla kernel 4.1.2, nouveau seems to have an
issue reading the FCODE ROM / DCB block / from the OpenFirmware device tree.
Also, interestingly, this time around it attempts to use the PROM method and
attempts to find the "BIT SIGNATURE" via this method.
Apparently it found a signature, but looks like garbage and seems like it cant
extract the DCB BLOCK.
As instructed, i have attached a dmesg.log along with a dump of the NVDA,BMP
image out of the following folder:
/sys/firmware/devicetree/base/pci@0,f0000000/NVDA,Parent@0/.
Not sure if this is correct, but i have passed the following nouveau module
options as i understood:
options nouveau config="NvMSI=0,debug=debug,VBIOS=trace"
I have placed the kernel dmesg log along with the NVDA,BMP dump in the attached
nouveau_powerpc64_pmac11.2.tar.xz archive.
Please let me know if there is any more info required.
Thanks for your help!
Best Regards,
Peter
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3595 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-07-13 0:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 0:34 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-91319-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-13 0:41 ` [Bug 91319] Nouveau driver cannot extract FCODE ROM / DCB Block from OpenFirmware Device tree bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-13 9:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-13 14:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-21 1:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-02 7:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 0:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 3:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-05 5:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-06 10:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-07 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 6:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-01 4:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-01 13:21 ` 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-91319-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.