search for: listnouveau

..._______________________________________________ > > > > Nouveau mailing list > > > > Nouveau at lists.freedesktop.org > > > > https://lists.freedesktop.org/mailman/listinfo/nouveau > > _______________________________________________Nouveau mailing > listNouveau at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/nouveau -- Cheers, Lyude Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20190622/2f980af5/attachment-0001.html>

...au, git regression] - I2C PWM fan control broken on nv50 a... | | | _______________________________________________ Nouveau mailing list Nouveau at lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau _______________________________________________Nouveau mailing listNouveau at lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau -- Cheers, Lyude Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20190623/59e2e23a/attachment.html>

Hi Mar, Could you file a bug (bugs.freedesktop.org under xorg -> Driver/nouveau) with a summary of this info (i.e. a problem statement, that reverting the commit in question fixes it, the lspci output) and additionally, your VBIOS. You can obtain this with nouveau loaded by doing cp /sys/kernel/debug/dri/0/vbios.rom /tmp This will help centralize all the info. Thanks, -ilia On Sun, Jun

Mar - can you provide the output of lspci -nn -d 10de: On Sat, Jun 22, 2019 at 2:17 PM Lyude Paul <lyude at redhat.com> wrote: > Hi, is this actually an nv50 GPU, or some other model? I can try to take a > closer look at this > > On Sun, 2019-06-16 at 10:28 -0400, Ilia Mirkin wrote: > > I don't really see anything between v5.0..v5.1 which would account for > this.

I don't really see anything between v5.0..v5.1 which would account for this. Could have been a subtle change to the i2c logic somewhere. The fastest way to identify the problem would be to do a bisect on the kernel to identify the commit that caused this. There are many guides for this online. On Sat, Jun 15, 2019 at 12:17 PM Mar Mel <marmel6942 at yahoo.com> wrote: > Unfortunately,

Oops, the FBIOPAN_DISPLAY ioctl error was a stupid mistake on mistake on my part.? Thanks for the info on where the validation code was.? Comparing against that made it easy to find the mistake.? It's working now, well...where I have been able to get over-allocation working!? Thanks for the help.? If I can't get the over-allocation to work on my other systems, I'll take it up in