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 109952] New: nv106 nv108 confusion
Date: Sun, 10 Mar 2019 21:18:00 +0000	[thread overview]
Message-ID: <bug-109952-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109952
           Summary: nv106 nv108 confusion
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: moebius1-GANU6spQydw@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 143619
  --> https://bugs.freedesktop.org/attachment.cgi?id=143619&action=edit
hope it's the good one (the internal nvidia card is not in use, but...)

Bonjour,
I own a MSI GT 710
I'm running a debian buster
Here are the outputs of different commands :
lshw : GK208 [GeForce GT 710B]

dmesg : [    6.211259] nouveau 0000:02:00.0: NVIDIA GK208B (b060b0b1)

vainfo: Driver version: Mesa Gallium driver 18.3.4 for NV106

And just an example of syslog that shows that nouveau is looking for nv106
drivers  and fails to load them because I've renamed the firmware directory:
Direct firmware load for nouveau/nv106_fuc084 failed with error -2

In fact, I suppose that, for nouveau driver the card is a nv106 (GK208B, GT
720) but, in fact, it's a nv108 (GK208, GT 710B).

So I've rename /lib/firmware/nouveau/ directory in nouveau.ori to avoid
kaffeine to crash (and vlc too when selecting VDPAU output). But doing so, I
can't expect any hardware acceleration.

PS : I don't know how to find version number of nouveau driver but kernel is 
4.19.0-2-rt-amd64 SMP preempt

Thank's for your work

cordialement,

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2019-03-10 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 21:18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-109952-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-03-11 11:47   ` [Bug 109952] nv106 nv108 confusion bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-11 13:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-11 13:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-11 14:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-03-12  9:13   ` [Bug 109952] Possible " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-02 12:00   ` [Bug 109952] Possible nv106 nv108 confusion ; different bugs bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-02 12:00   ` [Bug 109952] Possible nv106 nv108 confusion ; different bugs too bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:48   ` 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-109952-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.