From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91523] [NVE7] driver cannot initialize gpu(failed to parse ramcfg data)
Date: Sat, 01 Aug 2015 17:16:56 +0000 [thread overview]
Message-ID: <bug-91523-8800-RRo1sFOdod@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91523-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 951 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91523
--- Comment #1 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Relevant bits:
[ 3.766892] nouveau D[ PFB][0000:01:00.0] 0x100800: 0x00000002
[ 3.766892] nouveau D[ PFB][0000:01:00.0] parts 0x00000002 mask
0x00000000
[ 3.766900] nouveau D[ PFB][0000:01:00.0] 0: mem_amount 0x00000400
[ 3.766902] nouveau D[ PFB][0000:01:00.0] 1: mem_amount 0x00000400
[ 3.766913] nouveau E[ PFB][0000:01:00.0] failed to parse ramcfg data
[ 3.766914] nouveau E[ PFB][0000:01:00.0] failed to create 0x00000000,
-22
[ 3.766915] nouveau ![ PFB][0000:01:00.0] error detecting memory
configuration!!
[ 3.766916] nouveau E[ DEVICE][0000:01:00.0] failed to create 0x1000e00b,
-22
Could you attach your vbios.rom from a successful boot
(/sys/kernel/debug/dri/1/vbios.rom)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1719 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-08-01 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 17:04 [Bug 91523] New: [NVE7] driver cannot initialize gpu(failed to parse ramcfg data) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-91523-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-08-01 17:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-08-01 20:55 ` [Bug 91523] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-17 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-18 17:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-22 20:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-22 22:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:02 ` 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-91523-8800-RRo1sFOdod@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.