From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209345] New: [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80)
Date: Mon, 21 Sep 2020 23:55:14 +0000 [thread overview]
Message-ID: <bug-209345-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209345
Bug ID: 209345
Summary: [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla
K80)
Product: Drivers
Version: 2.5
Kernel Version: 5.8.9
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: kallisti5@unixzen.com
Regression: No
Attaching an nVidia Tesla K80 compute card to a Fedora 32 machine.
Getting:
nouveau 0000:08:00.0: unknown chipset (0f22d0a1)
--
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 reply other threads:[~2020-09-21 23:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 23:55 bugzilla-daemon [this message]
2020-09-22 0:00 ` [Bug 209345] [nouveau] unknown chipset (0f22d0a1) (nVidia Tesla K80) bugzilla-daemon
2020-09-22 0:01 ` 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@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 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.