similar to: NVAC "No Signal"

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 >

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

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

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=37669 Summary: [NVAC] problem when disabling external monitor Product: xorg Version: unspecified Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=86539 Bug ID: 86539 Summary: [NVAC] Trying to register nv_backlight after NV96 did it Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

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

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

https://bugs.freedesktop.org/show_bug.cgi?id=98677 Bug ID: 98677 Summary: [NVAC] iMac9,1 effective backlight brightness range changes after S3 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hi Robert, After trying to write a proper patch for Nouveau, we realised we were missing a few pieces of information. ----- Mail original ----- > Hi Robert, > > Thanks a lot for your response! > > ----- Mail original ----- > > On Wed, Oct 22, 2014 at 12:55:23AM +0200, pierre.morrow at free.fr > > wrote: > > [...] > > > After some investigation, I found

(Sending it to the correct Nvidia mailing list, sorry for the spam) Hi, When using acceleration with Nouveau on MacBook Pros with an 9400M (NVAC) card, a PFIFO interrupt 0x00400000 is thrown during the initialisation of that card (sometime after PFIFO and PGRAPH initialisation) and the laptop will lockup [1], forcing users to load Nouveau without acceleration. After some investigation, I found

Hi, When using acceleration with Nouveau on MacBook Pros with an 9400M (NVAC) card, a PFIFO interrupt 0x00400000 is thrown during the initialisation of that card (sometime after PFIFO and PGRAPH initialisation) and the laptop will lockup [1], forcing users to load Nouveau without acceleration. After some investigation, I found that enabling bit 1 of register 100c14 fixes the issue on that card.

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

https://bugs.freedesktop.org/show_bug.cgi?id=82726 Priority: medium Bug ID: 82726 Assignee: nouveau at lists.freedesktop.org Summary: [NV96][NVAC] [Regression] [Bisected] Probe failed with error -12 QA Contact: xorg-team at lists.x.org Severity: blocker Classification: Unclassified OS: Linux (All)