From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209345] [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80)
Date: Tue, 22 Sep 2020 00:00:43 +0000 [thread overview]
Message-ID: <bug-209345-2300-6MPI0Cj2oc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209345-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209345
--- Comment #1 from Alexander von Gluck (kallisti5@unixzen.com) ---
lspci -vvn
08:00.0 0302: 10de:102d (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: nouveau
Kernel modules: nouveau
09:00.0 0302: 10de:102d (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel modules: nouveau
08:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev ff)
09:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev ff)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-09-22 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 23:55 [Bug 209345] New: [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80) bugzilla-daemon
2020-09-22 0:00 ` bugzilla-daemon [this message]
2020-09-22 0:01 ` [Bug 209345] " bugzilla-daemon
2020-09-22 1:14 ` bugzilla-daemon
2020-09-22 1:54 ` bugzilla-daemon
2020-09-22 4:05 ` bugzilla-daemon
2020-09-22 4:07 ` bugzilla-daemon
2020-09-22 13:59 ` bugzilla-daemon
2020-09-22 14:14 ` bugzilla-daemon
2020-09-22 14:15 ` bugzilla-daemon
2020-09-22 14:18 ` bugzilla-daemon
2020-09-22 14:23 ` bugzilla-daemon
2021-04-14 15:00 ` bugzilla-daemon
2021-04-14 15:08 ` bugzilla-daemon
2021-04-14 15:10 ` bugzilla-daemon
2021-04-14 15:35 ` bugzilla-daemon
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-209345-2300-6MPI0Cj2oc@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox