similar to: NVAC "No Signal"

https://bugs.freedesktop.org/show_bug.cgi?id=98405 poma <pomidorabelisima at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|No signal on HDMI output |[NVAC] No signal on HDMI |after upgrade to kernel |output after upgrade to

https://bugs.freedesktop.org/show_bug.cgi?id=98405 poma <pomidorabelisima at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from poma <pomidorabelisima at

On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: > For example, my laptop (which also has an NVAC) has been triggering the > no-signal message on external monitors way before Ben???s patch landed, > but only for some adapters. I haven???t tried Ben???s patch yet, nor > yours, but I will certainly do it, and see what effect each of them has. The external DP port on your

On Thu, Oct 20, 2016 at 10:08:28AM +0200, Lukas Wunner wrote: > On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: > > For example, my laptop (which also has an NVAC) has been triggering the > > no-signal message on external monitors way before Ben???s patch landed, > > but only for some adapters. I haven???t tried Ben???s patch yet, nor > > yours, but I will

On 21.10.2016 10:56, Pierre Moreau wrote: > On 01:15 am - Oct 21 2016, Lukas Wunner wrote: >> On Thu, Oct 20, 2016 at 10:08:28AM +0200, Lukas Wunner wrote: >>> On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: >>>> For example, my laptop (which also has an NVAC) has been triggering the >>>> no-signal message on external monitors way before

how sure are you, that this is needed for _every_ nvac? 2016-10-18 5:55 GMT+02:00 poma <pomidorabelisima at gmail.com>: > Fixes "No Signal" via HDMI from NVIDIA Corporation ION VGA (rev b1) > > Ref. > "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a >

well, I just don't want that this fix breaks the same thing for other users, that's why I am asking. 2016-10-18 13:56 GMT+02:00 poma <pomidorabelisima at gmail.com>: > On 18.10.2016 09:35, Karol Herbst wrote: >> how sure are you, that this is needed for _every_ nvac? >> > > Thank you for asking. > > If you consider, as relevant, > referring to the

Hello, On 07:37 pm - Oct 19 2016, poma wrote: > On 19.10.2016 17:03, Karol Herbst wrote: > > > You don't get why I try to say. We have to actually find out when to > > apply this workaround, not to create some silly whitelist/blacklist. > > It's the last option, we never want to actually use. > > > > Well if you do not say, who can understand!? :)

On 12/24/2016 07:48 PM, Roy Spliet wrote: > I've observed this regression on my NVAC board; a 1920x1080 TV on HDMI > (single monitor set-up) gets no signal with Fedora kernels from 4.8. > Trace sent to the mmio dumps mailbox. A brief scan already revealed that > register 0xe840 is never touched, so it appears that NVIDIA does > something different. > VBIOS for this board is

On 18.10.2016 09:35, Karol Herbst wrote: > how sure are you, that this is needed for _every_ nvac? > Thank you for asking. If you consider, as relevant, referring to the original commit: "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a <quote> Fixes the second DVI output

On 01:15 am - Oct 21 2016, Lukas Wunner wrote: > On Thu, Oct 20, 2016 at 10:08:28AM +0200, Lukas Wunner wrote: > > On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: > > > For example, my laptop (which also has an NVAC) has been triggering the > > > no-signal message on external monitors way before Ben???s patch landed, > > > but only for some

2016-10-19 16:47 GMT+02:00 poma <pomidorabelisima at gmail.com>: > On 18.10.2016 16:02, Karol Herbst wrote: >> well, I just don't want that this fix breaks the same thing for other >> users, that's why I am asking. >> > > Affected device ID: > https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nvkm/engine/device/pci.c#L1229 > can it be

http://goo.gl/Gm4ffO mmiotrace-nouveau/

On 20.10.2016 00:46, Ben Skeggs wrote: [...] > I'd like to see a mmiotrace of the NVIDIA binary driver on a system > where this WAR breaks things. I applied it to all the GPUs that NVIDIA > told me required it. > > Ben. > Still broken, more than four months, tested with mainline 4.9-rc6. According to Ben Skeggs, since this is "told" by NVIDIA i.e. by you, or

Op 09-01-17 om 00:24 schreef Ben Skeggs: > On 12/24/2016 07:48 PM, Roy Spliet wrote: >> I've observed this regression on my NVAC board; a 1920x1080 TV on HDMI >> (single monitor set-up) gets no signal with Fedora kernels from 4.8. >> Trace sent to the mmio dumps mailbox. A brief scan already revealed that >> register 0xe840 is never touched, so it appears that NVIDIA

On 18.10.2016 16:02, Karol Herbst wrote: > well, I just don't want that this fix breaks the same thing for other > users, that's why I am asking. > Affected device ID: https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nvkm/engine/device/pci.c#L1229 can it be excluded from device->chipset case 0xac ? Care to create a patch? I'll test it.

On 10/20/2016 03:58 AM, Pierre Moreau wrote: > Hello, > > On 07:37 pm - Oct 19 2016, poma wrote: >> On 19.10.2016 17:03, Karol Herbst wrote: >> >>> You don't get why I try to say. We have to actually find out when to >>> apply this workaround, not to create some silly whitelist/blacklist. >>> It's the last option, we never want to actually

I've observed this regression on my NVAC board; a 1920x1080 TV on HDMI (single monitor set-up) gets no signal with Fedora kernels from 4.8. Trace sent to the mmio dumps mailbox. A brief scan already revealed that register 0xe840 is never touched, so it appears that NVIDIA does something different. VBIOS for this board is in the usual place. Commenting out 0xac from the workaround seems to

On 19.10.2016 17:03, Karol Herbst wrote: > You don't get why I try to say. We have to actually find out when to > apply this workaround, not to create some silly whitelist/blacklist. > It's the last option, we never want to actually use. > Well if you do not say, who can understand!? :) Besides, you can mock with "silly" whitelist/blacklist", however there is

Fixes "No Signal" via HDMI from NVIDIA Corporation ION VGA (rev b1) Ref. "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a The last working Fedora kernel 4.8.0-0.rc0.git3.1.fc25 Patched and tested with: $ modinfo -n nouveau