https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #30 from Anonymous Helper ---
As the days went by. I'm wondering what I should do. Or what's the case with
this report.
Is it kind of a problem, that I need to take care myself? E.g. it cannot be
patched/removed/altered, because this
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #31 from Emil Velikov ---
(In reply to comment #30)
> As the days went by. I'm wondering what I should do. Or what's the case with
> this report.
> Is it kind of a problem, that I need to take care myself? E.g. it cannot be
> patched/
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #32 from Martin Peres ---
(In reply to comment #31)
> (In reply to comment #30)
> > As the days went by. I'm wondering what I should do. Or what's the case with
> > this report.
> > Is it kind of a problem, that I need to take care my
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #33 from Emil Velikov ---
Created attachment 84479
--> https://bugs.freedesktop.org/attachment.cgi?id=84479&action=edit
nv50 quirk
Confirmed that only nv50 are affected. The blob's dac handling does differ
between nv50 and later c
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #34 from Emil Velikov ---
Here is a bit more information as to the blob's handing on the case
nv50
Simple register bashing
write(loadval | 0x010)
udelay(140s)
read()
write(0)
nv94/96
HWSQ
: 5f 01 00 ewait #
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #35 from Anonymous Helper ---
(In reply to comment #33)
> Created attachment 84479 [details] [review]
> nv50 quirk
>
> Confirmed that only nv50 are affected. The blob's dac handling does differ
> between nv50 and later cards, so thi
https://bugs.freedesktop.org/show_bug.cgi?id=67382
Emil Velikov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #37 from Emil Velikov ---
P.S. feel free to close bug ticket at kernel.org, as the fix lands.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #38 from Anonymous Helper ---
(In reply to comment #37)
> P.S. feel free to close bug ticket at kernel.org, as the fix lands.
Will do, but how long does it usually takes until a patch is accepted?
Checked the source of 3.10.10 and 3.
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #39 from Ilia Mirkin ---
This is now in Linus's tree as 5087f51da805f53cba7366f70d596e7bde2a5486.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mail
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #40 from Anonymous Helper ---
Ah, that's nice. So landing with 3.12
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #1 from Anonymous Helper ---
Created attachment 83073
--> https://bugs.freedesktop.org/attachment.cgi?id=83073&action=edit
nouveau specific entries from journalctl using 3.9.6
Journalctl log from the working 3.9.6 kernel
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #2 from Anonymous Helper ---
Created attachment 83074
--> https://bugs.freedesktop.org/attachment.cgi?id=83074&action=edit
nouveau specific entries from journalctl using 3.10.3
Log from a non working kernel (3.10.3, the latest kern
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #3 from Emil Velikov ---
(In reply to comment #0)
> After looking at #66129 and testing linux 3.10.3 (includes the patches from
> 66129) and still having problems, I decided to open a bugreport, as the
> problem appears to be somethin
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #4 from Ilia Mirkin ---
You probably also want this patch to make NV50 work properly:
http://lists.freedesktop.org/archives/nouveau/2013-July/013051.html
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #5 from Anonymous Helper ---
(In reply to comment #3)
> A brief explanation what happens here:
> Nouveau detects a phantom/ghost monitor hooked up to DVI-I-2, which on it's
> own causes the DISPLAY engine to hang. Leading to the kern
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #6 from Anonymous Helper ---
Result linux-3.9.7 without the
drm-nv50-disp-force-dac-power-state-during-load-detect.patch[0]: Stuff is
working like it should
No ghost monitor anymore:
Current Operating System: Linux Hekate 3.9.7-1-ARC
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #7 from Emil Velikov ---
Great stuff :)
I'll attach a few patches in the next few days for you two try
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #8 from Emil Velikov ---
Created attachment 83155
--> https://bugs.freedesktop.org/attachment.cgi?id=83155&action=edit
some debug printfs
Give this patch a try and attach the output of dmesg. Thanks
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #9 from Anonymous Helper ---
Created attachment 83228
--> https://bugs.freedesktop.org/attachment.cgi?id=83228&action=edit
dmesg from 3.9.7 with the debug patch
There you go :)
I hope the information you need is there.
Also I wasn
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #10 from Anonymous Helper ---
Created attachment 83231
--> https://bugs.freedesktop.org/attachment.cgi?id=83231&action=edit
dmesg from 3.10.3 with the debug patch
Like stated in the comment before. Here the dmesg log using 3.10.3 a
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #11 from Emil Velikov ---
Created attachment 83240
--> https://bugs.freedesktop.org/attachment.cgi?id=83240&action=edit
another debug patch
Another patch, it will printout a bit more information (that the first one
missed) and it w
https://bugs.freedesktop.org/show_bug.cgi?id=67382
Emil Velikov changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #13 from Anonymous Helper ---
Created attachment 83307
--> https://bugs.freedesktop.org/attachment.cgi?id=83307&action=edit
dmesg from 3.9 with the faulty commit and debug2 (aka 3.9.7+debug2)
There you go. dmesg output with debug2
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #14 from Emil Velikov ---
(In reply to comment #13)
> Created attachment 83307 [details]
> dmesg from 3.9 with the faulty commit and debug2 (aka 3.9.7+debug2)
>
> There you go. dmesg output with debug2 kernel.
>
Thanks, there is som
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #15 from Emil Velikov ---
Created attachment 83320
--> https://bugs.freedesktop.org/attachment.cgi?id=83320&action=edit
debug-3
Grab the 3.9 branch _without_ the offending patch and apply debug-3 one on top.
Attach dmesg as usual.
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #16 from Anonymous Helper ---
Created attachment 83335
--> https://bugs.freedesktop.org/attachment.cgi?id=83335&action=edit
dmesg from 3.9.7 without the bad patch + debug3
And the next log.
>Thanks, there is something really funky
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #17 from Emil Velikov ---
A fair bit of fairy stuff in here.
Without the bad patch, nouveau does not call the appropriate sense() function,
thus your system never looks for any other outputs and does not see the fathom
monitor connec
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #18 from Anonymous Helper ---
Created attachment 83378
--> https://bugs.freedesktop.org/attachment.cgi?id=83378&action=edit
BIOS dump from my graphic card
The card type is Nvidia Geforce 8800 GTS manufactured from Leadtek (IIRC
Lea
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #19 from Emil Velikov ---
According to your vbios
> dvi-1 --> dvi-to-vga adaptor going to a vga monitor
The above uses OR 2/1 for analogue/digital output
> dvi-2 --> normally not used. But working
OR 1/1 respectively here
> tv-out -
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #20 from Anonymous Helper ---
(In reply to comment #19)
Interim report
> According to your vbios
> > dvi-1 --> dvi-to-vga adaptor going to a vga monitor
> The above uses OR 2/1 for analogue/digital output
>
> > dvi-2 --> normally n
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #21 from Emil Velikov ---
(In reply to comment #20)
> It was working. Xorg.log wrote, that DVI-I-1 is disconnected and DVI-I-2
> connected.
Let me see if I'm not day dreaming in here. If you startup with your monitor
connected to the
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #22 from Anonymous Helper ---
Created attachment 83466
--> https://bugs.freedesktop.org/attachment.cgi?id=83466&action=edit
dmesg from 3.9.7 without offendind patch+debug3. Monitor connected to the
second dvi
>> It was working. Xor
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #23 from Anonymous Helper ---
Created attachment 83477
--> https://bugs.freedesktop.org/attachment.cgi?id=83477&action=edit
dmesg from kernel available through * git checkout
7ebb38b556485449bfaa506a196439f6a6fd6ebd~1
Nothing parti
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #24 from Anonymous Helper ---
Created attachment 83478
--> https://bugs.freedesktop.org/attachment.cgi?id=83478&action=edit
dmesg from kernel available through * git checkout
7ebb38b556485449bfaa506a196439f6a6fd6ebd~2
Worked too, s
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #25 from Emil Velikov ---
Created attachment 83549
--> https://bugs.freedesktop.org/attachment.cgi?id=83549&action=edit
possible fix
Still not too sure how come your system senses a monitor connected to your
second dvi port.
This
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #26 from Anonymous Helper ---
Created attachment 83558
--> https://bugs.freedesktop.org/attachment.cgi?id=83558&action=edit
dmesg from 3.9 with offending commit + fix
(In reply to comment #25)
> Created attachment 83549 [details] [
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #27 from Emil Velikov ---
(In reply to comment #26)
> Yes, this is working. It seems no ghost monitor was detected and X works
> like it should :)
Great, can you track down which hunk(one or a combination) is needed ?
* set DAC_CLK_
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #28 from Anonymous Helper ---
Yes, I can do that and will post the results, when I'm finished.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #29 from Anonymous Helper ---
I can confirm, that applying
>* remove the stabilisation
>+/*
> nv_wr32(priv, 0x61a00c + doff, 0x8000);
>+*/
solves my issue.
The other two hunks weren't successful.
I suppose, testing the
40 matches
Mail list logo
