Hello everyone,
I would need testers to check that this patch doesn't break working
NVAA/NVAC configurations. It fixes an issue where some NVAC would hang on boot;
if similar issues exist on NVAA, it may fix them too.
You will find the patch below in two different versions: one will apply on Ben
S
https://bugs.freedesktop.org/show_bug.cgi?id=27501
Pierre Moreau changed:
What|Removed |Added
Attachment #110350|0 |1
is obsolete|
On 02.12.2014 14:59, poma wrote:
> On 02.12.2014 14:52, Ilia Mirkin wrote:
>> On Tue, Dec 2, 2014 at 8:50 AM, poma wrote:
>>> On 02.12.2014 14:40, Ilia Mirkin wrote:
On Tue, Dec 2, 2014 at 8:38 AM, poma wrote:
> Is this expected result for Chipset: G98 (NV98)?
Yep, 100% expecte
Reviewed-by: Andy Ritger
On Sun, Nov 30, 2014 at 12:56:18PM -0500, Ilia Mirkin wrote:
> Indications are that no GF116's actually have a copy engine there, but
> actually have the decompression engine. This engine can be made to do
> copies, but that should be done separately.
>
> Unclear why thi
The set of variable defs does not need to be ordered in any way, and
removing/adding elements is a fairly common operation in various
optimization passes.
This shortens runtime of piglit test fp-long-alu to ~11s from ~22s
No piglit regressions observed on nvc0!
Signed-off-by: Tobias Klausmann
--
https://bugs.freedesktop.org/show_bug.cgi?id=86935
--- Comment #6 from Ilia Mirkin ---
(In reply to Sven from comment #5)
> I will try to do the mmiotrace of the blob. Problem is, that the binary
> nvidia drivers gives me a kernel OOPS. Yay!
D'oh! Maybe try a newer driver? If it oopses "later" r
https://bugs.freedesktop.org/show_bug.cgi?id=86935
--- Comment #5 from Sven ---
I will try to do the mmiotrace of the blob. Problem is, that the binary nvidia
drivers gives me a kernel OOPS. Yay!
Also, while I can make the changes to the kernel source, I'm not really sure
what you're asking from
https://bugs.freedesktop.org/show_bug.cgi?id=86935
--- Comment #4 from Ilia Mirkin ---
(In reply to Sven from comment #2)
> Created attachment 110361 [details] [review]
> the patch proposed in the previous comment
>
> Adding 0x106 seems to have worked. I can now boot with nouveau framebuffer
> a
https://bugs.freedesktop.org/show_bug.cgi?id=86935
--- Comment #3 from Sven ---
Will this patch be included in 3.18 (a bit late I guess) or maybe 3.19?
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=86935
--- Comment #2 from Sven ---
Created attachment 110361
--> https://bugs.freedesktop.org/attachment.cgi?id=110361&action=edit
the patch proposed in the previous comment
Adding 0x106 seems to have worked. I can now boot with nouveau framebuffer
https://bugs.freedesktop.org/show_bug.cgi?id=86935
Ilia Mirkin changed:
What|Removed |Added
Summary|unknown kepler chipset |[NV106] unknown kepler
|
https://bugs.freedesktop.org/show_bug.cgi?id=86935
Bug ID: 86935
Summary: unknown kepler chipset
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority:
https://bugs.freedesktop.org/show_bug.cgi?id=27501
--- Comment #59 from l3iggs ---
(In reply to Pierre Moreau from comment #58)
> Created attachment 110350 [details] [review]
> [Patch] Fix acceleration on 9400M v4
>
> This should be the final verson of this patch, thanks to answers given by
> th
On 02.12.2014 14:52, Ilia Mirkin wrote:
> On Tue, Dec 2, 2014 at 8:50 AM, poma wrote:
>> On 02.12.2014 14:40, Ilia Mirkin wrote:
>>> On Tue, Dec 2, 2014 at 8:38 AM, poma wrote:
Is this expected result for Chipset: G98 (NV98)?
>>>
>>> Yep, 100% expected. [Perhaps you might glance at the wiki
On Tue, Dec 2, 2014 at 8:50 AM, poma wrote:
> On 02.12.2014 14:40, Ilia Mirkin wrote:
>> On Tue, Dec 2, 2014 at 8:38 AM, poma wrote:
>>> Is this expected result for Chipset: G98 (NV98)?
>>
>> Yep, 100% expected. [Perhaps you might glance at the wiki page you got
>> that from for clues as to why.]
On 02.12.2014 14:40, Ilia Mirkin wrote:
> On Tue, Dec 2, 2014 at 8:38 AM, poma wrote:
>> Is this expected result for Chipset: G98 (NV98)?
>
> Yep, 100% expected. [Perhaps you might glance at the wiki page you got
> that from for clues as to why.]
>
"You basically never need to do the mmiotrac
On Tue, Dec 2, 2014 at 8:38 AM, poma wrote:
> Is this expected result for Chipset: G98 (NV98)?
Yep, 100% expected. [Perhaps you might glance at the wiki page you got
that from for clues as to why.]
>
> $ modinfo nvidia -F version
> 304.123
>
> $ stat -c %s mmiotrace.log
> 134659197
>
> $ file mm
Is this expected result for Chipset: G98 (NV98)?
$ modinfo nvidia -F version
304.123
$ stat -c %s mmiotrace.log
134659197
$ file mmiotrace.log
mmiotrace.log: ASCII text
$ grep -i lost mmiotrace.log ; echo $?
1
$ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c");
op
https://bugs.freedesktop.org/show_bug.cgi?id=72180
--- Comment #40 from Matthias Nagel ---
@Cedric: Well this means, that the kernel could not find the firmware. There
are several ways how to do it and it depends on wether you have a initramfs or
not, if the kernel has access to /lib/fimware when
https://bugs.freedesktop.org/show_bug.cgi?id=72180
--- Comment #39 from Cedric Brandenbourger ---
I also have this random GPU lookups on my GT660.
I tried to get the proprietary PGRAPH working, but without success.
Im'getting an error at boot:
Failed to loader firmware with error -2
Fallback to
https://bugs.freedesktop.org/show_bug.cgi?id=27501
Pierre Moreau changed:
What|Removed |Added
Attachment #107262|0 |1
is obsolete|
21 matches
Mail list logo
