[Nouveau] [Bug 100760] Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display

https://bugs.freedesktop.org/show_bug.cgi?id=100760 --- Comment #3 from m...@advancedcontrols.com.au --- Many thanks Ilia for those helpful suggestions. The results of the experiments are, that in ZaphodHeads mode: 1. Running "DISPLAY=:0.1 gnome-terminal" under all window managers makes the

[Nouveau] [Bug 100760] Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display

https://bugs.freedesktop.org/show_bug.cgi?id=100760 --- Comment #2 from Ilia Mirkin --- While Zaphod is considered a legacy feature, that doesn't mean that things should break. Just that it's unlikely to be extended to support new things. There has recently been some bugs

[Nouveau] [Bug 100760] Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display

https://bugs.freedesktop.org/show_bug.cgi?id=100760 --- Comment #1 from m...@advancedcontrols.com.au --- Further information: 1. The graphics card is a GeForce 7600 GT (NV4B/G73). Would ZaphodHeads be more likely to work in a recent card? 2. The working single-X-display mode is using XRandR (I

[Nouveau] [Bug 100760] New: Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display

https://bugs.freedesktop.org/show_bug.cgi?id=100760 Bug ID: 100760 Summary: Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display Product: xorg Version: unspecified Hardware: x86-64 (AMD64)

[Nouveau] [ANNOUNCE] xf86-video-nouveau 1.0.15

Ben Skeggs (1):   fix null pointer deref when building against >=libdrm 2.4.78 Ilia Mirkin (1):   Add Pascal family support, identical to Maxwell Lyude (1):   Bump version to 1.0.15 Mariusz Bialonczyk (1):   Do not register hotplug without RandR git tag:

Re: [Nouveau] [PATCH v4 2/5] nouveau_hwmon: Add nouveau_hwmon_ops structure with .is_visible/.read_string

2017-04-22 11:24 GMT+02:00 Oscar Salvador : > This patch introduces the nouveau_hwmon_ops structure, sets up > .is_visible and .read_string operations and adds all the functions > for these operations. > This is also a preparation for the next patches, where most of

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #7 from Kevin Winchester --- Thank you, I'm going to try 4.11-rc7 which is available in the Arch AUR. -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #6 from Ilia Mirkin --- (In reply to Kevin Winchester from comment #5) > After this crash, I rebooted and I'm currently running sway on wayland and > things seem to work well, but I've been having trouble with

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #5 from Kevin Winchester --- After this crash, I rebooted and I'm currently running sway on wayland and things seem to work well, but I've been having trouble with X for weeks now. I first noticed issues

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #4 from Kevin Winchester --- [kevin@karpov ~]$ cat /etc/X11/xorg.conf.d/20-nouveau.conf Section "Monitor" Identifier "LVDS" Option "PreferredMode" "1600x900_60.0" Option

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #3 from Kevin Winchester --- 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 230M] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 365c

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #2 from Kevin Winchester --- Created attachment 130982 --> https://bugs.freedesktop.org/attachment.cgi?id=130982=edit Xorg log -- You are receiving this mail because: You are the assignee for the

[Nouveau] [Bug 100758] Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 --- Comment #1 from Kevin Winchester --- Versions: Linux karpov 4.10.11-1-ARCH #1 SMP PREEMPT Tue Apr 18 08:39:42 CEST 2017 x86_64 GNU/Linux core/linux 4.10.11-1 extra/xorg-server 1.19.3-2 extra/xf86-video-nouveau

[Nouveau] [Bug 100758] New: Kernel Oops when starting X nv50_dma_push

https://bugs.freedesktop.org/show_bug.cgi?id=100758 Bug ID: 100758 Summary: Kernel Oops when starting X nv50_dma_push Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

Re: [Nouveau] [PATCH] volt: Improve min/max deteaction of range based volting

2017-04-22 16:46 GMT+02:00 Roy Spliet : > Response in-line: > > > Op 22-04-17 om 13:22 schreef Karol Herbst: >> >> info.min and info.max doesn't always represent the actual voltage range we >> can use. Do the same as with the entry based volting. >> >> Fixes "ERROR: Can't get

Re: [Nouveau] [PATCH] volt: Improve min/max deteaction of range based volting

Response in-line: Op 22-04-17 om 13:22 schreef Karol Herbst: info.min and info.max doesn't always represent the actual voltage range we can use. Do the same as with the entry based volting. Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors in sensors. Signed-off-by:

Re: [Nouveau] [PATCH] volt: Improve min/max deteaction of range based volting

deteaction -> detection On 22/04/17 15:22, Karol Herbst wrote: info.min and info.max doesn't always represent the actual voltage range we can use. Do the same as with the entry based volting. Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors in sensors. Signed-off-by:

[Nouveau] [PATCH] volt: Improve min/max deteaction of range based volting

info.min and info.max doesn't always represent the actual voltage range we can use. Do the same as with the entry based volting. Fixes "ERROR: Can't get value of subfeature in0_min: Can't read" errors in sensors. Signed-off-by: Karol Herbst ---

[Nouveau] [PATCH v4 3/5] nouveau_hwmon: Remove old code, add .write/.read operations

This patch removes old code related to the old api and transforms the functions for the new api. It also adds the .write and .read operations. Signed-off-by: Oscar Salvador --- drivers/gpu/drm/nouveau/nouveau_hwmon.c | 722 +++- 1 file

[Nouveau] [PATCH v4 5/5] nouveau_hwmon: Change permissions to numeric

This patch replaces the symbolic permissions with the numeric ones, and adds me to the authors too. Signed-off-by: Oscar Salvador --- drivers/gpu/drm/nouveau/nouveau_hwmon.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git

[Nouveau] [PATCH v4 4/5] nouveau_hwmon: Add support for auto_point attributes

This patch creates a special group attributes for attrs like "*auto_point*". We check if we have support for them, and if we do, we gather them all in an attribute_group's structure which is the parameter regarding special groups of hwmon_device_register_with_info. Signed-off-by: Oscar Salvador

[Nouveau] [PATCH v4 2/5] nouveau_hwmon: Add nouveau_hwmon_ops structure with .is_visible/.read_string

This patch introduces the nouveau_hwmon_ops structure, sets up .is_visible and .read_string operations and adds all the functions for these operations. This is also a preparation for the next patches, where most of the work is being done. This code doesn't interacture with the old one. It's just

[Nouveau] [PATCH v4 1/5] nouveau_hwmon: Add config for all sensors and their settings

This is a preparation for the next patches. It just adds the sensors with their possible configurable settings and then fills the struct hwmon_channel_info with all this information. Signed-off-by: Oscar Salvador --- drivers/gpu/drm/nouveau/nouveau_hwmon.c | 72

[Nouveau] [PATCH v4 0/5] replace hwmon_device_register for hwmon_device_register_with_info

Kbuild sent me an e-mail due to a fixup I introduced in v3. It complains due to an incompatible pointer type and it doesn't build. This version reverts it. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return