Recent content by jafd

Well, I'm not complaining about something that I want a solution to. Just posted a workaround for people who might have the same symptoms, a possibility to look into. Took me almost a day to get to the bottom of it, but... I do have sound now, after all. I have reasons to suspect that...

This is not true, the reason being the rest of the properties do get injected.

Just a heads up for those who are using the latest Lilu (1.2.7 unreleased) and the latest AppleALC (1.3.1 or 1.3.2), and cannot enable sound. I've found a bit of strangeness, and hope they will fix it. I'm reluctant to report it in their support forums because I can practically feel the...

Just chiming in for a quick heads up: there is new firmware, 0.2.7.1 (previous: 0.2.6.2). The list of updates is: Improve startup stability when the RTC battery voltage is low Support eGFX devices I don't know if updating will mess with UEFI variables for DVMT and similar. Bugfixes, of...

MVM only :( It's when the vast majority of Intel cards present on the market still are DVM. A valid use case is people who want to put macOS onto their machine without popping in a newer/other wireless card or messing with their BIOSes.

The problem with CoreBrightness is that it exclusively uses Metal. If your GPU doesn't support Metal, you're out of luck.

In a private message, a user named sneitzel, asked me how I got OS X 100% running on a Thinkpad W510. It turned out I could not answer in a private message, as I don't have enough posts here, so I will respond here, intending to address more general audience. The shortest answer is no. It's...

Can't really say about Yosemite. Ditched it to experiment with El Capitan. When I had Yosemite on it, I didn't fix brightness in DSDT and didn't have ACPIBacklight, otherwise my guess is that it *would* work. The DSDT is being interpreted correctly and consistently, the registers it pokes at...

Another interesting find: whatever I move the brightness slider to, gets applied at next reboot.

Then, I think, bummer? Googling "nvidia acpi brightness" turns up lots of advice to use acpi_brightness=vendor under Linux (read: effectively bypass ACPI and mess with the hardware directly). But then again, the output switching thing...

Brought ACPIBrightness back. The slider came back, too. This time I put a lot of debug statements into my DSDT, and here what it gives if I move the slider... Method (_BCM, 1, NotSerialized) { \RMDT.P2 ("[DSDT]...

This is laptop #2 from my signature. Thinkpad W510. It's not a SandyBridge machine (i7-720QM), and it has no integrated graphics at all. My other two laptops are Sandy Bridge. MacbookPro6,2 would be a good match if I could grab at some good SMBIOS values. Meanwhile: _LID is checked once on...

The ioreg is attached. I haven't yet had a chance to instrument _LID, as it's only now that I've only now got time to tinker. Firing up ACPIDebug to see what's being played. Unloading ACPIBacklight.kext made keys work (brightness slider appears), but the actual brightness does not change...

Nope, I don't want it to sleep. I just want it to disable the built-in display. Otherwise some windows end up on a screen which I can't see. The Intel HD3000 laptops handle this correctly: closing/opening the lid triggers "detect displays" and the built-in display is disabled/enabled...

So far, adding PNLF, moving the methods from SSDT to DSDT and dropping that SSDT helped in that the internal display shows up as internal, and the brightness slider is displayed. However, the slider does nothing. Will debug with ACPIDebug to get at it, and will post the results once I have them...