[SOLVED] Strange PowerNap/SMBIOS(Board-ID)/Airport behavior

[kusakata]

OK so after much reading, apparently you need a Retina for PowerNap. I've maybe discovered some off behavior.
I have an Elitebook 8470p running El Cap, everything is working (including PM); I've used the various PBI guides in the past and my SMBIOS has always been MacBookPro9,2 as this is an i5 Ivy Bridge laptop.
So I thought it would be fun to screw around and try to get PowerNap working, since I did install an SSD. Initially I just the "magic wand" in Clover to switch to a MacBookPro10,1 SMBIOS. Rebooted and voila PowerNap is available under Energy Prefs, HOWEVER, Wi-Fi now says "No hardware installed" :\
Okay, so I went back into the configurator, and started to try and narrow down exactly what kills Wi-Fi, long story short, in my testing it seemed to be the "Board-ID", I loaded my original MacBookPro9,2 SMBIOS, and edited ONLY the Board-ID field, with the value I had gotten from the 10,1 SMBIOS. Next reboot, system profiler confirms model 9,2--however PowerNap options are still in Energy Saver! But Wi-Fi remains unavailable. Bluetooth, sound, battery, etc. continue to work perfectly, I tried trashing the NetworkInterfaces.plist and preferences.plist from /Library/Preferences/SystemConfiguration, but it did not make a difference.

I'm attaching a screenshot, showing the SMBIOS set to 9,2 but PowerNap available, with defunct WiFi. There must be some way around this...
Sorry @ long post, a crappy explanation would be much worst

 

[RehabMan]

OK so after much reading, apparently you need a Retina for PowerNap. I've maybe discovered some off behavior.
I have an Elitebook 8470p running El Cap, everything is working (including PM); I've used the various PBI guides in the past and my SMBIOS has always been MacBookPro9,2 as this is an i5 Ivy Bridge laptop.
So I thought it would be fun to screw around and try to get PowerNap working, since I did install an SSD. Initially I just the "magic wand" in Clover to switch to a MacBookPro10,1 SMBIOS. Rebooted and voila PowerNap is available under Energy Prefs, HOWEVER, Wi-Fi now says "No hardware installed" :\
Okay, so I went back into the configurator, and started to try and narrow down exactly what kills Wi-Fi, long story short, in my testing it seemed to be the "Board-ID", I loaded my original MacBookPro9,2 SMBIOS, and edited ONLY the Board-ID field, with the value I had gotten from the 10,1 SMBIOS. Next reboot, system profiler confirms model 9,2--however PowerNap options are still in Energy Saver! But Wi-Fi remains unavailable. Bluetooth, sound, battery, etc. continue to work perfectly, I tried trashing the NetworkInterfaces.plist and preferences.plist from /Library/Preferences/SystemConfiguration, but it did not make a difference.

I'm attaching a screenshot, showing the SMBIOS set to 9,2 but PowerNap available, with defunct WiFi. There must be some way around this...
Sorry @ long post, a crappy explanation would be much worst

http://www.tonymacx86.com/threads/g...book-using-clover-uefi-hotpatch-10-11.189416/

 

[kusakata]

I'm a little bit confused, everything /does/ work on my laptop, there's no stability problems or other issues; I was just curious as to why changing just the Board-ID impacted only the Wi-Fi(and enabled PowerNap), I read the entire post.
I will go that route when installing Sierra, I guess I don't need PowerNap enough to completely change out all the patches, as I have a stable working setup.

Also, for the webcam issues after sleep, mentioned in the post (I didn't have these in Yosemite, but do in El cap), I found a solution that doesn't require resleeping the laptop:

sudo killall VDCAssistant
sudo killall AppleCameraAssistant

Thanks for the reply

 

[RehabMan]

I'm a little bit confused, everything /does/ work on my laptop, there's no stability problems or other issues; I was just curious as to why changing just the Board-ID impacted only the Wi-Fi(and enabled PowerNap), I read the entire post.
I will go that route when installing Sierra, I guess I don't need PowerNap enough to completely change out all the patches, as I have a stable working setup.

Depending on which WiFi you have, requires SMBIOS whitelist patch. Since you didn't follow my guide, you likely do not have the correct patch for other SMBIOS.

Also, for the webcam issues after sleep, mentioned in the post (I didn't have these in Yosemite, but do in El cap), I found a solution that doesn't require resleeping the laptop:

sudo killall VDCAssistant
sudo killall AppleCameraAssistant

Yes, problem with webcam is specific to 10.11+. I will add a note to the guide based on your feedback.

 

[kusakata]

So, I decided what the hell, why not
I now have PowerNap working, with functional WiFi also I kept the model at MacBookPro9,2 since its closer to actual HW but used the Board-ID from the retina SMBIOS to get the PowerNap functions in Energy Saver.

However, for the life of me I can't get sound to work. I never have gotten sound to work in el capitan. I've just been using AppleHDA from Yosemite, which always loaded first boot without any fuss or issues, but it's not working since following the guide; I've booted a couple times now without caches, with and without AppleHDAIDT.kext, but no go
I used Pacifist to extract AppleHDA from latest 10.11.6 update

Seems like all the kexts are loading, but I still have no sound, reboot after reboot

$ kextstat | grep -y hda
  91    2 0xffffff7f82b72000 0xf000     0xf000     com.apple.iokit.IOHDAFamily (274.12) C6423C28-4CFB-32A8-BDD1-2D149DE52F74 <5 4 3 1>
  92    1 0xffffff7f82c3a000 0x1e000    0x1e000    com.apple.driver.AppleHDAController (274.12) 5F94D8E3-B1E5-35D7-AB7A-6419C3AAC3B5 <91 90 77 12 7 6 5 4 3 1>
  118    0 0xffffff7f82da6000 0xb3000    0xb3000    com.apple.driver.AppleHDA (274.12) 436B78B7-FA08-3C53-B97D-5C617CB7EB28 <117 92 91 90 84 77 12 11 6 5 4 3 1>
  121    0 0xffffff7f82b81000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (274.12) 3F8189BB-F49C-3E8B-AB4D-E6CA6A96619C <4 3>

 

[RehabMan]

So, I decided what the hell, why not
I now have PowerNap working, with functional WiFi also I kept the model at MacBookPro9,2 since its closer to actual HW but used the Board-ID from the retina SMBIOS to get the PowerNap functions in Energy Saver.

However, for the life of me I can't get sound to work. I never have gotten sound to work in el capitan. I've just been using AppleHDA from Yosemite, which always loaded first boot without any fuss or issues, but it's not working since following the guide; I've booted a couple times now without caches, with and without AppleHDAIDT.kext, but no go
I used Pacifist to extract AppleHDA from latest 10.11.6 update

Seems like all the kexts are loading, but I still have no sound, reboot after reboot

$ kextstat | grep -y hda
  91    2 0xffffff7f82b72000 0xf000     0xf000     com.apple.iokit.IOHDAFamily (274.12) C6423C28-4CFB-32A8-BDD1-2D149DE52F74 <5 4 3 1>
  92    1 0xffffff7f82c3a000 0x1e000    0x1e000    com.apple.driver.AppleHDAController (274.12) 5F94D8E3-B1E5-35D7-AB7A-6419C3AAC3B5 <91 90 77 12 7 6 5 4 3 1>
  118    0 0xffffff7f82da6000 0xb3000    0xb3000    com.apple.driver.AppleHDA (274.12) 436B78B7-FA08-3C53-B97D-5C617CB7EB28 <117 92 91 90 84 77 12 11 6 5 4 3 1>
  121    0 0xffffff7f82b81000 0x2000     0x2000     com.apple.driver.AppleHDAHardwareConfigDriver (274.12) 3F8189BB-F49C-3E8B-AB4D-E6CA6A96619C <4 3>

My guide does not use AppleHDAIDT.kext. It also does not patch AppleHDAHardwareConfigDriver.

Install vanilla AppleHDA.kext, remove AppleHDAIDT.kext, then follow the guide as written.

 

[kusakata]

Yeah that's what I thought, it was a remnant of PBI, only reason I even saw it was because of the blue dot "Tag". I've been working with the vanilla (10.11.6, 274.12) file. No more hardwareconfigdriver either, but still no sound. I'm working on collecting the support files as I write this

 

[RehabMan]

Yeah that's what I thought, it was a remnant of PBI, only reason I even saw it was because of the blue dot "Tag". I've been working with the vanilla (10.11.6, 274.12) file. No more hardwareconfigdriver either, but still no sound. I'm working on collecting the support files as I write this

When you have the "Problem Reporting" files, attach them to a new reply.

 

[kusakata]

** Resolved

 

[kusakata]

Okay so after what seems like the 100th restart, the sound now works. I didn't do anything special, first boot without caches, ran "sudo touch /System/Library/Extensions && sudo kextcache -u /" (just like everytime else), rebooted, no sound, reboot again, no sound. But this particular time it complied. No idea; making time machine backup now
Thanks for all the help @RehabMan