HP Folio 13 Guide! UNIBEAST + parts of MultiBeast

Thanks for your detailed answer RehabMan.

I investigated a little bit more about how Linux manage this since in Linux the button is working fine oob.
And as you pointed out, is using "rfkill", a kernel module and userspace tool that controls the wifi status. It seems that Linux wifi drivers should also use this facility (and they seem to do it in most cases (atheros, intel drivers at least) for rfkill to actually work.

If just for curiosity you or anybody reading this post is interested, you can read this:

https://www.kernel.org/doc/Documentation/rfkill.txt

So it seems that the little button magic is more difficult to achieve in OS X, than just patching DSDT.

On another subject, last night, I updated to 10.9.5 through the AppStore. Result: KP on AppleIntelCPUPowerManagement. I'm attaching a picture in case you don't mind checking it.

jackito said:

...
So it seems that the little button magic is more difficult to achieve in OS X, than just patching DSDT.

Click to expand...

Likely... Yes.

On another subject, last night, I updated to 10.9.5 through the AppStore. Result: KP on AppleIntelCPUPowerManagement. I'm attaching a picture in case you don't mind checking it.

Click to expand...

Normal. The update provided a new/unpatched AppleIntelCPUPowerManagement.kext. You need to boot using your USB installer (use "-f UseKernelCache=No") and install patched AppleIntelCPUPowerManagement.kext from Multibeast.

RehabMan said:

Read from post #36 onward.

Click to expand...

Indeed. You should read all this thread since all the information is there, and quite detailed in some cases thanks to RehabMan.

Regarding the wifi card, I bought a Azurewave NE773 card (Atheros 9280) in ebay and then I rebranded it as 9485 to pass the BIOS whitelist (following a thread from tonymacx86 also shared by Rehabman, you can find the link in this thread).
Keep in mind that at least in my case, after the rebranding, the card is only working in Linux and OS X. In Windows I keep hitting error 10 no matter which driver I try (HP, Atheros for 9280, 9485, 928X, etc), even forcing it and wifi still doesn't work.
Since Linux is my main OS and I almost never boot Windows, I can live with that until I find a way to solve the problem.

Doesn't look easy tough, I'm thinking about rebranding the wifi card again, changing the SUBVENDOR and SUBSYS ids to 9485 more generic one -Azurewave?- instead of HP -103C- as I did before. The risk is that the BIOS will block the card and that will require another rebranding to the IDs I'm currently using (also you can find them in this thread).....

Good luck with the modding!

I recently upgraded to Yosemite and wifi is very stable. A lot better than on Mavericks in my experience.
I used it during a full week without any issues at all.
To be honest Yosemite GUI is great. I like it more than Mavericks GUI (which is already really nice).

I wrote a guide about installing Mavericks and Yosemite on the Folio 13 in case anyone is interested.

RehabMan said:

You could try this patch... I based this off 10.9.5 kext:

Code:

sudo perl -pi -e 's|\x83\xc1\xf9\x83\xf9\x29|\x83\xc1\xf1\x83\xf9\x29|g' AirPortAtheros40

Click to expand...

Hello!
First of all, sorry for bumping this old thread, but I didn't want to start another one about the same exact topic. Thanks for your help here! I was able to finally make my wi-fi card work with El Capitan (10.11.6 here), as long as my problem was pretty much as exotic as similar to jackito's one: unpatched BIOS with whitelist, patched AR9280 and urge to make it work not only with Linux, but also with OS X.

By the way, my rebranded card has now product ID 0x8176, so the quoted fix was not applicable to my situation. So I'd like to suggest another one:

Or, using Clover's config.plist's syntax,

This fix assumes that you're using the card from ar9300 family (older ar5416 family gets dropped). In exchange, it provides more convenient way to set the desired product ID manually (0x002A in my case).