From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 107016] Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02)
Date: Thu, 06 Sep 2018 08:54:54 +0000 [thread overview]
Message-ID: <bug-107016-8800-JHoWBbyQLn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107016-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107016
--- Comment #21 from atirage21 <tothsoft-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Karol Herbst:
Hi,
do you still have your GK107 Nvidia GPU? I just recently found out,
that there is a strange thing to control the GPU voltage there which
I never saw on any other board and I would like to know if you are up
for doing some testing.
Greetings
Karol
Attila:
Hi,
yes, i am. So , i tried todya oibaf witk last mesa 18.3 devel, but is same.
4.496952] nouveau 0000:01:00.0: bios: version 80.07.40.00.02
[ 4.497677] nouveau 0000:01:00.0: mxm: BIOS version 3.0
[ 4.501493] nouveau 0000:01:00.0: volt: Type mismatch between the voltage
table type and the GPIO table. Fallback to GPIO mode.
[ 4.502201] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1758 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2018-09-06 8:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 19:18 [Bug 107016] New: Gpio error only from kernel higher as 4.x (k2000m; 0x0e73b0a2; version 80.07.40.00.02) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-107016-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-06-24 19:18 ` [Bug 107016] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 20:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-24 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 3:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 3:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 10:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 12:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 12:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 14:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 14:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 14:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 15:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 16:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 16:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 17:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-25 17:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-01 8:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-06 8:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-12-04 18:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-04 18:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-10 13:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-16 8:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:43 ` 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-107016-8800-JHoWBbyQLn@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.