similar to: [Bug 100922] New: Redundant nv_backlight created on Optimus enabled laptop.

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

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:

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

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

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:

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

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

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

Hello, On my system (Linux 3.3, booting in EFI mode, using Nouveau with nouveau.noaccel=1 due to https://bugs.freedesktop.org/show_bug.cgi?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

mksmbpasswd.sh does not create accounts with the X flag in the password flags field. Does this X matter, and if so, what does it mean? It's not in the man page. ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical

Hi All, I'm sure this has been discussed many times but since I do not have a internet connection, I have to ask this question.. [ow_mh@hmweb Dump]$ sudo mount -t smbfs //129.253.110.160/Dump $HOME/Dump 708: session request to 129.253.110.160 failed (Called name not present) 708: session request to 129 failed (Called name not present) Password: Anonymous login successful 708: tree connect

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-off-by:

Hi All, I've the following in the logs and am wondering why they are there. I also keep getting emails from SAMBA log-deamon (or something like that). [2003/05/19 15:24:29, 0] passdb/pdb_smbpasswd.c:getsmbfilepwent(364) getsmbfilepwent: malformed password entry (uid not number) It's not really serious (at least to me) but it's a cause for concern. Below are the details LInux

Hi All, Perhaps you guys can help me shed some light on this 'problem' I'm facing. I recently added another NIC to my samba server. eth0(10.0.0.251) and eth1(valid dhcp address) ETH0 was added to connect to another PC that acts as the backup server. (dedicated connection) Now, Samba won't come back up.. I can still ssh into the server and all. Any ideas? I know that the wins

Hi All, Any recommendation for a Network Browser for KDE/GNOME/WindowMaker?? Cheers, Mun Heng, Ow H/M Engineering Western Digital M'sia DID : 03-7870 5168

Hi All, On 11/10/23 07:09, Kai-Heng Feng wrote: > Hi Owen, > > On Fri, Nov 10, 2023 at 5:55?AM Owen T. Heisler <writer at owenh.net> wrote: >> >> #regzbot introduced: 89c290ea758911e660878e26270e084d862c03b0 >> #regzbot link: https://gitlab.freedesktop.org/drm/nouveau/-/issues/273 >> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=218124 >

On Fri, Apr 15, 2016 at 11:25 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Fri, Apr 15, 2016 at 11:22 AM, Pierre 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

hello, I want to protect the history file from deleted for all users except user 'root' can do it, is that possible? For my server, many users can log in with root from remote through ssh, so I can not trace which guy do wrong things. So I decide to create new account for every users and let them use 'sudo' then I can trace which guy typed which command and what he

Hi Collective users of Samba, (does has a nice ring to it eh?) Recently I found a my samba server being infected by win32 viruses. Though it does not affect the server in any way, I do find them to be an annoyance. I understand also that I can perform "veto" of files like *.exe in smb.conf but find that to be a wee bit restrictive. There are some users who stores valid executables in