Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 04 Sep 2012 21:19:12 -0700
From:      matt <sendtomatt@gmail.com>
To:        SicoSico <resuscitated_wael@hotmail.com>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: Lenovo Y570 backlight
Message-ID:  <5046D2C0.4080701@gmail.com>
In-Reply-To: <1346770745437-5740634.post@n5.nabble.com>
References:  <1342085203648-5726207.post@n5.nabble.com> <201207121653.32046.erichfreebsdlist@ovitrap.com> <1342094808885-5726236.post@n5.nabble.com> <50004AF0.1010400@gmail.com> <1346704065209-5740445.post@n5.nabble.com> <CAN6yY1tJggN1%2BCS37DBqRPO=mynwEnNM0xs8K-dhQVLma9RzLQ@mail.gmail.com> <1346725868219-5740516.post@n5.nabble.com> <50459608.7050801@gmail.com> <1346770745437-5740634.post@n5.nabble.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 09/04/12 07:59, SicoSico wrote:
> Yes, I did. Some values can be changed like 'hw.acpi.video.lcd0.brightness',
> others don't like 'hw.acpi.video.lcd0.active'. The brightness is max in all
> cases.
>
> #kldload acpi_video
>
> #sysctl hw.acpi.video
> hw.acpi.video.crt0.active: 0
> hw.acpi.video.lcd0.active: 0
> hw.acpi.video.lcd0.brightness: 70
> hw.acpi.video.lcd0.fullpower: 70
> hw.acpi.video.lcd0.economy: 30
> hw.acpi.video.lcd0.levels: 70 30 10 17 23 30 40 50 60 70 80 90 100
> hw.acpi.video.ext0.active: 0
> hw.acpi.video.crt1.active: 0
> hw.acpi.video.lcd1.active: 0
> hw.acpi.video.lcd1.brightness: 70
> hw.acpi.video.lcd1.fullpower: 70
> hw.acpi.video.lcd1.economy: 30
> hw.acpi.video.lcd1.levels: 70 30 10 17 23 30 40 50 60 70 80 90 100
> hw.acpi.video.ext1.active: 0
> hw.acpi.video.ext2.active: 0
> hw.acpi.video.ext3.active: 0
> hw.acpi.video.ext4.active: 0
> hw.acpi.video.ext5.active: 0
>
> #sysctl hw.acpi.video.lcd0.active=1
> hw.acpi.video.lcd0.active: 0 -> 0
> #sysctl hw.acpi.video.lcd0.brightness=30
> hw.acpi.video.lcd0.brightness: 70 -> 30
> #sysctl hw.acpi.video.lcd1.active=1
> hw.acpi.video.lcd1.active: 0 -> 0
> #sysctl hw.acpi.video.lcd1.brightness=30
> hw.acpi.video.lcd1.brightness: 70 -> 30
>
>
>
> --
> View this message in context: http://freebsd.1045724.n5.nabble.com/Lenovo-Y570-backlight-tp5726207p5740634.html
> Sent from the freebsd-x11 mailing list archive at Nabble.com.
> _______________________________________________
> freebsd-x11@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"
>
Are you using KMS? Have you tried xbacklight from ports?

The last shot I can think of beside trying random ACPI handles (You can 
sometimes tell because of checks of \IGD or \PEG that a handle is 
graphics related on at least X220), is to see if there is an address in 
the graphics device's pci space to write a value to with pciconf. I have 
to do something similar on an Asus 1001pxd under debian, sometimes the 
backlight is offset toward high or low, so I do setpci (pciconf is our 
equivalent) XX:YY f4.b=NN where XX:YY is the PCI address and NN is 
16-bit hex value I think. The f4.b part is variable, you'd have to find 
the correct address for your card, and it's possibly quite risky (being 
a user-induced write to the PCI space at goodness knows what address :) 
). This is probably the WrongWayToDoIt (tm) but it may be an option. If 
you see the pciconf manpage, you can see that our equivalent would be 
some variant of pciconf -w

You may have some luck finding this value by digging through (or 
trolling through, whatever floats your boat) Linux forums for backlight 
fixes for your model. I'll take a look at your DSDT if I get a chance.

Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5046D2C0.4080701>