From: James <bjlockie-ozXLQgHQwDP3fQ9qLvQP4Q@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: new GP107
Date: Sun, 9 Dec 2018 14:16:40 -0500 [thread overview]
Message-ID: <pujpim$q19$1@blaine.gmane.org> (raw)
In-Reply-To: <CAKb7Uvg83nMOd9_4xTuGGggY=AH_P=Mi7O2iVLLLaddBTUsNZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 2018-12-09 12:41 a.m., Ilia Mirkin wrote:
> On Sun, Dec 9, 2018 at 12:24 AM James <bjlockie@lockie.ca> wrote:
>
>> # dmesg | grep -i nouveau
>>> [ 2.171473] fb: switching to nouveaufb from VESA VGA
>>> [ 2.171595] nouveau 0000:01:00.0: NVIDIA GP107 (137000a1)
>>> [ 2.286501] nouveau 0000:01:00.0: bios: version 86.07.39.80.5e
>>> [ 2.287672] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
>>> [ 3.573113] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
>>> [ 3.573114] nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
>>> [ 3.573116] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
>>> [ 3.573117] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
>>> [ 3.573119] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
>>> [ 3.573120] nouveau 0000:01:00.0: DRM: DCB version 4.1
>>> [ 3.573121] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f42 04620030
>>> [ 3.573123] nouveau 0000:01:00.0: DRM: DCB outp 01: 02011f62 04620010
>>> [ 3.573124] nouveau 0000:01:00.0: DRM: DCB outp 02: 02822f76 04600020
>>> [ 3.573125] nouveau 0000:01:00.0: DRM: DCB outp 03: 02022f72 04620020
>>> [ 3.573126] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001031
>>> [ 3.573127] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010161
>>> [ 3.573128] nouveau 0000:01:00.0: DRM: DCB conn 02: 00020246
>>> [ 3.844431] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
>>> [ 3.983733] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 122124 [ IBUS ]
>>> [ 4.091733] nouveau 0000:01:00.0: DRM: allocated 1920x1200 fb: 0x200000, bo (____ptrval____)
>>> [ 4.160682] fbcon: nouveaufb (fb0) is primary device
>>> [ 4.160758] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
>>> [ 4.192044] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
>>
>> # tail /var/log/Xorg.0.log
>>> [ 2798.820] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
>>> [ 2798.820] (WW) glamor: Failed to allocate 11x8 FBO due to GL_OUT_OF_MEMORY.
>>> [ 2798.820] (WW) glamor: Expect reduced performance.
>>
>> Is this a bug?
>
> Something's failing bigtime - GL can't allocate a texture or other
> buffer. Not really enough info here, but perhaps something interesting
> in dmesg after this happens. I'd recommend using xf86-video-nouveau
> though, instead of modesetting, since it doesn't involve trying to use
> GL all the time.
>
> -ilia
What has lubuntu done?
# apt install xf86-video-nouveau
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package xf86-video-nouveau
# apt-cache search xf86-video-nouveau
xserver-xorg-video-nouveau - X.Org X server -- Nouveau display driver
# apt install xserver-xorg-video-nouveau
Reading package lists... Done
Building dependency tree
Reading state information... Done
xserver-xorg-video-nouveau is already the newest version (1:1.0.15-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
https://nouveau.freedesktop.org/wiki/
> Little hope of reclocking becoming available for GM20x and newer GPUs as firmware now needs to be signed by NVIDIA to have the necessary access.
Is that why I get this:
# cat /sys/kernel/debug/dri/0/pstate cat:
/sys/kernel/debug/dri/0/pstate: No such device
Can I see the current clocking with nouveau?
Everything should at least be readable.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2018-12-09 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 5:09 new GP107 James
2018-12-09 5:41 ` Ilia Mirkin
[not found] ` <CAKb7Uvg83nMOd9_4xTuGGggY=AH_P=Mi7O2iVLLLaddBTUsNZw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-09 19:16 ` James [this message]
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='pujpim$q19$1@blaine.gmane.org' \
--to=bjlockie-ozxlqghqwdp3fq9qlvqp4q@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox