https://bugs.freedesktop.org/show_bug.cgi?id=91738
Ilia Mirkin changed:
What|Removed |Added
Attachment #117904|text/plain |application/octet-stream
mime typ
On 18 August 2015 at 04:04, Hauke Mehrtens wrote:
> On 08/08/2015 07:01 PM, Hauke Mehrtens wrote:
>> These patches are adding support for outputting 2560x1440@56 over HDMI.
>> This needs a pixel clock of 225 MHz which was not supported before.
>>
>> This was tested in a dual monitor setup with a G
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #15 from ryanpcmcquen ---
Thank you, I was able to get it attached.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #14 from ryanpcmcquen ---
Created attachment 117904
--> https://bugs.freedesktop.org/attachment.cgi?id=117904&action=edit
/sys/kernel/debug/dri/0/vbios.rom
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #13 from Ilia Mirkin ---
Add nouveau.modeset=0 to your kernel cmdline, that should prevent nouveau from
loading. I believe that xcmddc is killing of CPU's one-by-one as nouveau is
mishandling something it's asking for.
--
You are re
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #12 from ryanpcmcquen ---
Sorry, trying to do this from my phone, since the computer will not stay on for
more than a few minutes.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #11 from Ilia Mirkin ---
Please attach files here.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://l
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #10 from ryanpcmcquen ---
Ah, I did not know that! Learning is fun. :-)
As requested, vbios.rom:
http://sprunge.us/fLiF
Also the system is still experiencing a hard lock up after a few minutes, so
this is definitely worth investig
https://bugs.freedesktop.org/show_bug.cgi?id=91738
Ilia Mirkin changed:
What|Removed |Added
Summary|[NV117] xf86-video-nouveau |[NV117] NULL deref in
|1
https://bugs.freedesktop.org/show_bug.cgi?id=91738
ryanpcmcquen changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=91738
--- Comment #7 from Ilia Mirkin ---
Looks like you still have the same failure from xcmddc. IMO it's worth
investigating/fixing. Will need your vbios though, as I mentioned before.
[8.700223] BUG: unable to handle kernel NULL pointer derefer
https://bugs.freedesktop.org/show_bug.cgi?id=91738
ryanpcmcquen changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 08/24/2015 10:02 PM, Ilia Mirkin wrote:
Edge flag stuff is annoying. Pretty sure only blender uses it. shade
model = flat should get fixed on nv50 before edge flags, since blender
uses that too, and it's produces much worse visual artifacts.
No rush for this one though.
I'm having secon
Edge flag stuff is annoying. Pretty sure only blender uses it. shade
model = flat should get fixed on nv50 before edge flags, since blender
uses that too, and it's produces much worse visual artifacts.
I'm having second thoughts about this patch. I think I'm going to go
back to my previous approac
Reviewed-by: Samuel Pitoiset
This fix is simpler than I was expected. What about the edge flag stuff
now? :)
On 08/24/2015 05:51 PM, Ilia Mirkin wrote:
The hardware only generates vertexid when vertices come from a VBO. This
fixes:
vertexid-drawelements
vertexid-drawarrays
Signed-off
Cc: nouveau@lists.freedesktop.org
Signed-off-by: Emil Velikov
---
nouveau/abi16.c | 13 ++---
nouveau/nouveau.c | 6 +++---
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/nouveau/abi16.c b/nouveau/abi16.c
index 4ca0bfb..59bc436 100644
--- a/nouveau/abi16.c
+++ b/nouvea
On Mon, Aug 24, 2015 at 11:57 AM, Tobias Klausmann
wrote:
>
>
> On 24.08.2015 17:51, Ilia Mirkin wrote:
>>
>> The hardware only generates vertexid when vertices come from a VBO. This
>> fixes:
>>
>>vertexid-drawelements
>>vertexid-drawarrays
>>
>> Signed-off-by: Ilia Mirkin
>> Cc: "11.0"
On 24.08.2015 17:51, Ilia Mirkin wrote:
The hardware only generates vertexid when vertices come from a VBO. This
fixes:
vertexid-drawelements
vertexid-drawarrays
Signed-off-by: Ilia Mirkin
Cc: "11.0"
---
src/gallium/drivers/nouveau/nv50/nv50_program.c| 1 +
src/gallium/driv
The hardware only generates vertexid when vertices come from a VBO. This
fixes:
vertexid-drawelements
vertexid-drawarrays
Signed-off-by: Ilia Mirkin
Cc: "11.0"
---
src/gallium/drivers/nouveau/nv50/nv50_program.c| 1 +
src/gallium/drivers/nouveau/nv50/nv50_program.h| 1 +
sr
https://bugs.freedesktop.org/show_bug.cgi?id=91632
--- Comment #3 from Ilia Mirkin ---
(In reply to Allan Sandfeld from comment #2)
> The original qtwebengine bug is at
> https://bugreports.qt.io/browse/QTBUG-41242
>
> One interesting thing I discovered was that using the EGL/GLES mode instead
>
https://bugs.freedesktop.org/show_bug.cgi?id=91632
--- Comment #2 from Allan Sandfeld ---
The original qtwebengine bug is at https://bugreports.qt.io/browse/QTBUG-41242
One interesting thing I discovered was that using the EGL/GLES mode instead of
GLX/GL solved the issue. I assume at your level
https://bugs.freedesktop.org/show_bug.cgi?id=91632
--- Comment #1 from Ilia Mirkin ---
I've seen that a few times... My analysis was that there's a fixed number of
GEM objects and we're running out of them. Which means that the GPU is either
locked up or way way WAY behind. However I haven't conf
22 matches
Mail list logo
