On 04/05/12 18:33, Любомир Григоров wrote:
Hey Matt, a couple of things, since I am experiencing a different situation



> Yes, it should be possible if your sources are in synchronization with world/kernel. > Just make the edit and go to /usr/src/sys/modules/acpi/acpi_ibm and type make && make install I unloaded, recompiled that part, and rebooted, but I see no change for the hotkeys. Most still don't work. Only volume mute work, but that worked before the change. Trying to change the brightness didn't "corrupt" the fan. Neither from hotkeys, nor from acpi_call

> You'll notice that fan speed becomes something ugly after trying to set brightness, but everything will work otherwise as far as I have tested. > I have found that the machine gets quite hot on its own especially with turbo core on the i7 and heavy usage, even with power tuning. > Adjusting fan speed could be dangerous, I would certainly keep a close eye on temperatures during something like buildworld to be sure. On the other side, my temp now drops below 50C to about 46C. The fan goes into its lowest spin. I didn't have this before. At 50C it kicks to next step, at 60C it kicks to the crazy speed (usually on compile or 720p video).


P.S. All tests were done from X with Konstantin's patch on 9.0-STABLE with powerd and no other mods. X220 with i5 2520M, BIOS 1.28, IPS, 9cell batter, 16GB RAM, Intel 1000-N, SSD.

P.S.S. Workaround for fan corruption can be changing the brightness while it boots, before OS starts, function keys work there. But I don't have the crazy fan. If by crazy fan you mean not the lowest spin, then I had that before LEN change as well.

--
Lyubomir Grigorov (bgalakazam)

We have the same bios at least, only difference is 8gb RAM here and i7-2720M. For what it's worth the i5 and i7 are the same as far as I know except amount of L3 cache...maybe amt or vt-d? The corrupt fan speed value occurs only when setting lcd brightness in dev.acpi_ibm.0.lcd_brightness (from memory, so not sure if that's exact). It doesn't affect brightness as only bypassing \_SB.PCI0.LPC.EC.BRNS() seems to change the brightness for us (by using acpi_call to call \VBRC).

The hotkeys are interesting, I assume you're familar with the way the mask works etc...once you "enable" the hotkeys with sysctls, they are then supposed to be handled by devd, I believe, so you would have to create a script to capture the keys and execute some commands.

It's been a while since I did this, as I usually didn't use hotkeys...so in this case you *could* capture brightness hotkeys in devd and call acpi_call, but that seems like a hack...I think the best case is to allow ACPI to handle the hotkeys (which it's doing fine) but figure out why the hw.acpi.video.lcd0.brightness (again from memory) has no effect...as the hotkeys do change this value out of the box.

Matt
_______________________________________________
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"

Reply via email to