Date: Thu, 02 Feb 2023 20:58:58 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "parv/FreeBSD" <parv.0zero9+freebsd@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211 Message-ID: <202302022058.312Kwwj8003814@critter.freebsd.dk> In-Reply-To: <CABObuOoik3j_fsM=LciqRC8QrjJAs4o-hBYU_ZDE9wx=WJBBVw@mail.gmail.com> References: <CABObuOoUDHrUF6FyTwEXTrnt3ztkoAR4x5vzjcNp7H-4F4XE7A@mail.gmail.com> <CABObuOoik3j_fsM=LciqRC8QrjJAs4o-hBYU_ZDE9wx=WJBBVw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- parv/FreeBSD writes: > > Does backlight(8) works for you? > > Thanks for the clue. It does! It does ... > > - I get the same number back via "backlight" without any arguments as > what I gave it earlier. There was no reporting of value being > subtracted by one; Sorry for the delay in reporting back. I consistently read one less back, except for 0 and 100. (This could easily be a BIOS bug) It also looks like the "no-op" behaviour I reported previously have gone away with my latest kernel update. But I see a new behaviour, but this may be intentional: When it comes out of screen-blanking, it goes to 100 (and reports 100). Also happens when an external monitor is connected, which is a bit annoying... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202302022058.312Kwwj8003814>