similar to: [Bug 98405] [NVAC] No signal on HDMI output after upgrade to kernel 4.8.3-1

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 ---------------------------------------------------------------------------- CC| |ulr_bugs_freedesktop_org at mo | |ehrkevielfalt.de --- Comment #3

https://bugs.freedesktop.org/show_bug.cgi?id=98405 poma <pomidorabelisima at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |xorg-team at lists.x.org Component|DRM/other |Driver/nouveau Product|DRI

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 >

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

https://bugs.freedesktop.org/show_bug.cgi?id=99858 Bug ID: 99858 Summary: disp: ERROR 4 [INVALID_VALUE] 84 [] chid 0 mthd 0828 data 000099bb Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

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

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

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

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

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 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

Hi all, My apologies - I'm trying to reply to a thread and the web interface doesn't play well with Mutt. I tried to hack it. Hopefully I didn't goof it up too much! I am also getting a "No Signal" on the HDMI port when the resolution changes on boot. This is on an ION-based desktop. VGA is fine when the monitor is plugged in on boot, but is disabled if I plug it in

On 16.09.2014 01:21, Ilia Mirkin wrote: > On Mon, Sep 15, 2014 at 1:28 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 15.09.2014 15:36, Ilia Mirkin wrote: >>> On Mon, Sep 15, 2014 at 4:23 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> Chipset: G98 (NV98) >>>> Family : NV50 >>>> >>>> >>>> WORKING

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 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 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 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

On 13.07.2015 18:48, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 10:20 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 15:19, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> On 13.07.2015 14:53, Gene Cumm wrote: >>>>> On Mon, Jul 13, 2015 at 6:42 AM, poma

On 13.07.2015 15:19, Gene Cumm wrote: > On Mon, Jul 13, 2015 at 9:03 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.07.2015 14:53, Gene Cumm wrote: >>> On Mon, Jul 13, 2015 at 6:42 AM, poma <pomidorabelisima at gmail.com> wrote: >>> >>>> A patch like this? >>>> >>>> >>> >>> Correct. Have you