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 76475] [NVE7] fails to load due to unknown opcode 0x80 (incorrect vbios)
Date: Sat, 22 Mar 2014 21:40:55 +0000	[thread overview]
Message-ID: <bug-76475-8800-7Av2l7wCku@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76475-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1491 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=76475

--- Comment #7 from patrick.clara-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
> Unfortunately the VBIOS from the PCIROM is often the wrong one. The data
> here is the x86 opcodes instead of the vbios opocdes. And as you observed,
> we now consider unknown opcodes an error. (The init tables need to be run on
> e.g. resume, and if it's a secondary card, on load as well.)

I have read many times on the internet about PCIROM providing wrong bios. I
have tried various methods of getting one but all failed or provided the
exactly same bios as PCIROM. Vbtracetool freezes. Also nvclock fails.

> An mmiotrace of the blob loading would potentially be helpful, you can send
> one (compressed... xz -9 works well) to mmio.dumps-Re5JQEeQqe9fmgfxC/sS/w@public.gmane.org

I have sent one. I used blob version 331.49. During the trace I have loaded the
nvidia module and started X. I did it with a ubuntu live cd with kernel 3.13
since on my debian installation I m not able to launch X anymore. Hopefully I
did it right.

> Can you provide a bit more info about this system? Is it an optimus setup?
> Could you provide an acpidump?

The macine is an ASUS ZENBOOK UX51VZH, the version with the 2880x1620 display.
It appears to have only the nvidia gpu, or at least the intel one in the
i7-3632QM is permanently disabled.

I have attached lspci dmidecode and an acpidump.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2383 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-03-22 21:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22  9:19 [Bug 76475] New: Nouveau fails to load due to unknown opcode 0x80 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-76475-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-22  9:20   ` [Bug 76475] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22  9:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 13:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 13:29   ` [Bug 76475] [NVE7] fails to load due to unknown opcode 0x80 (incorrect vbios) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 19:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-22 21:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-03-23 17:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-26 22:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-26 23:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-27 11:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-28  3:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-28 11:25   ` 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-76475-8800-7Av2l7wCku@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.