search for: nv_backlight

https://bugs.freedesktop.org/show_bug.cgi?id=100922 Bug ID: 100922 Summary: Redundant nv_backlight created on Optimus enabled laptop. Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau...

Currently, every backlight interface created by Nouveau uses the same name, nv_backlight. This leads to a sysfs warning as it tries to create an already existing folder. This patch adds a incremented number to the name, but keeps the initial name as nv_backlight, to avoid possibly breaking userspace; the second interface will be named nv_backlight1, and so on. Fixes: fdo#86539 Signed-...

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: Driver/nouveau Assignee: nouveau at l...

On 11:06 AM - Apr 15 2016, Ilia Mirkin wrote: > On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: > > Currently, every backlight interface created by Nouveau uses the same name, > > nv_backlight. This leads to a sysfs warning as it tries to create an already > > existing folder. This patch adds a incremented number to the name, but keeps > > the initial name as nv_backlight, to avoid possibly breaking userspace; the > > second interface will be named nv_backlight1, and so...

https://bugs.freedesktop.org/show_bug.cgi?id=110407 Bug ID: 110407 Summary: /sys/class/backlight/nv_backlight doesn't work on Dell Precision 7530 GP107GLM [Quadro P1000 Mobile] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Dri...

On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: > Currently, every backlight interface created by Nouveau uses the same name, > nv_backlight. This leads to a sysfs warning as it tries to create an already > existing folder. This patch adds a incremented number to the name, but keeps > the initial name as nv_backlight, to avoid possibly breaking userspace; the > second interface will be named nv_backlight1, and so on. > >...

From: Pierre Moreau <pierre.morrow at free.fr> Currently, every backlight interface created by Nouveau uses the same name, nv_backlight. This leads to a sysfs warning as it tries to create an already existing folder. This patch adds a incremented number to the name, but keeps the initial name as nv_backlight, to avoid possibly breaking userspace; the second interface will be named nv_backlight1, and so on. Bugzilla: https://bugs.f...

...i?id=27501 ), I can't figure out how to change the backlight or switch which of the two graphics cards (I have an Nvidia 9600M GT and a 9400M, both are recognized by nouveau but only the 9400M is ever used) Linux uses for the framebuffer or X uses for the output. I have /sys/class/backlight/nv_backlight, and writting to nv_backlight/brightness does change the value in nv_backlight/actual_brightness, but no actual screen changes occur. I'm using the in-tree staging version of nouveau, so I wasn't sure which ML this should go to. Cheers, Shea Levy

https://bugs.freedesktop.org/show_bug.cgi?id=31920 Summary: Brightness control is erratic (/sys/class/backlight/nv_backlight/max_brightness is wrong) Product: xorg Version: git Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lis...

On Sun, Nov 13, 2016 at 08:57:06PM +0100, Pierre Moreau wrote: > From: Pierre Moreau <pierre.morrow at free.fr> > > Currently, every backlight interface created by Nouveau uses the same name, > nv_backlight. This leads to a sysfs warning as it tries to create an already > existing folder. This patch adds a incremented number to the name, but keeps > the initial name as nv_backlight, to avoid possibly breaking userspace; the > second interface will be named nv_backlight1, and so on. > >...

Currently, every backlight interface created by Nouveau uses the same name, nv_backlight. This leads to a sysfs warning as it tries to create an already existing folder. This patch adds a incremented number to the name, but keeps the initial name as nv_backlight, to avoid possibly breaking userspace; the second interface will be named nv_backlight1, and so on. Bugzilla: https://bugs.f...

Currently, every backlight interface created by Nouveau uses the same name, nv_backlight. This leads to a sysfs warning as it tries to create an already existing folder. This patch adds a incremented number to the name, but keeps the initial name as nv_backlight, to avoid possibly breaking userspace; the second interface will be named nv_backlight1, and so on. Bugzilla: https://bugs.f...

...r> > wrote: > > On 11:06 AM - Apr 15 2016, Ilia Mirkin wrote: > >> On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> > wrote: > >> > Currently, every backlight interface created by Nouveau uses the same > name, > >> > nv_backlight. This leads to a sysfs warning as it tries to create an > already > >> > existing folder. This patch adds a incremented number to the name, > but keeps > >> > the initial name as nv_backlight, to avoid possibly breaking > userspace; the > >> > second int...

...("drm/nouveau/fbcon: fix NULL pointer access in nouveau_fbcon_destroy") which was already included in the 4.18 tree. These patches make it so I can unload the module without a panic but there is a warning when unloading the module: sysfs group 'power' not found for kobject 'nv_backlight' WARNING: CPU: 2 PID: 1434 at fs/sysfs/group.c:235 sysfs_remove_group+0x76/0x80 RIP: 0010:sysfs_remove_group+0x76/0x80 Call Trace: device_del+0x56/0x350 ? down_write+0xe/0x40 device_unregister+0x16/0x60 nouveau_backlight_exit+0x4a/0x60 [nouveau] nouveau_display_destroy+0x29/0x80 [n...

...Moreau <pierre.morrow at free.fr> wrote: > On 11:06 AM - Apr 15 2016, Ilia Mirkin wrote: >> On Fri, Apr 15, 2016 at 10:57 AM, Pierre Moreau <pierre.morrow at free.fr> wrote: >> > Currently, every backlight interface created by Nouveau uses the same name, >> > nv_backlight. This leads to a sysfs warning as it tries to create an already >> > existing folder. This patch adds a incremented number to the name, but keeps >> > the initial name as nv_backlight, to avoid possibly breaking userspace; the >> > second interface will be named nv_backli...

with your patches I get this in dmesg when removing nouveau: [ 202.510730] ------------[ cut here ]------------ [ 202.510731] sysfs group 'power' not found for kobject 'nv_backlight' [ 202.510736] WARNING: CPU: 0 PID: 8156 at fs/sysfs/group.c:235 sysfs_remove_group+0x71/0x80 [ 202.510736] Modules linked in: nouveau(-) r8168(O) ttm zram [last unloaded: nouveau] [ 202.510740] CPU: 0 PID: 8156 Comm: rmmod Tainted: G W O 4.17.6-gentoo #2 [ 202.510741] Hardware nam...

..._dev_register(). So during backlight registration the connectors are not probed yet and the drm_connector->status == connected check in nv50_backlight_init() would now always fail. Replace the drm_connector->status == connected check with a drm_helper_probe_detect() == connected check to fix nv_backlight no longer getting registered because of this. Fixes: 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") Link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/202 Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- drivers/gpu/drm/nouveau/nouveau_backlight.c |...

...g backlight registration the connectors are > not probed yet and the drm_connector->status == connected check in > nv50_backlight_init() would now always fail. > > Replace the drm_connector->status == connected check with > a drm_helper_probe_detect() == connected check to fix nv_backlight > no longer getting registered because of this. > > Fixes: 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") > Link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/202 > Signed-off-by: Hans de Goede <hdegoede at redhat.com> > --- > drivers/gpu...

https://bugs.freedesktop.org/show_bug.cgi?id=51281 Bug #: 51281 Summary: X server restarts on brightness change Classification: Unclassified Product: xorg Version: 7.6 (2010.12) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component:

...access in nouveau_fbcon_destroy") which was already included in >> the 4.18 tree. >> >> These patches make it so I can unload the module without a panic but >> there is a warning when unloading the module: >> sysfs group 'power' not found for kobject 'nv_backlight' >> WARNING: CPU: 2 PID: 1434 at fs/sysfs/group.c:235 sysfs_remove_group+0x76/0x80 >> RIP: 0010:sysfs_remove_group+0x76/0x80 >> Call Trace: >> device_del+0x56/0x350 >> ? down_write+0xe/0x40 >> device_unregister+0x16/0x60 >> nouveau_backlight_...