Thu, 7 Apr 2016 22:05:26 +0200 (CEST) Mark Kettenis
> > There are a few instances of this bug. You can also see it with cpu
> > frequency and audio volume.
> >
> > Most drivers maintain soft state that should mirror the hardware
> > state. Except when it doesn't. Sometimes the driver has a bug,
>
> There are a few instances of this bug. You can also see it with cpu
> frequency and audio volume.
>
> Most drivers maintain soft state that should mirror the hardware
> state. Except when it doesn't. Sometimes the driver has a bug,
> sometimes the hardware lies, sometimes something else goes
> w
Hi Ted,
On 04/07/16 16:22, Ted Unangst wrote:
Most drivers maintain soft state that should mirror the hardware state. Except
when it doesn't. Sometimes the driver has a bug, sometimes the hardware lies,
sometimes something else goes wrong. The many layers of abstraction and acpi
don't help eithe
Ted Unangst wrote:
> It's a bug and it's worth reporting as much info about your hardware as
> possible, but don't expect a quick fix. As a workaround, just run
'xbacklight
> 50 ; xbacklight 100' or whatever you want.
>
Hello, I've an ASUS K53SV and the brightness also behaves oddly.
Values for
Riccardo Mottola wrote:
> "xbacklight" tells me however "100".
> if I lower it with "-set 90" I actually notice it gets brighter, setting
> it to "-set 100" .. it goes to full brightness.
>
> It looks as if initially the value is read back incorrect from a status
> register?
There are a few ins
Hi,
I noticed that on an HP 4530 laptop (using the intel video card, the
extra video card which wasn't properly initialized and used in OpenBSD
is directly disabled in the bios) comes up both in console and in X with
a pretty dim screen brightness.
"xbacklight" tells me however "100".
if I l
6 matches
Mail list logo