Recent content by agiorlando

I get no response from keyboard input, resetting the SMC did nothing either. I unplugged it and held the power button until I got the little blip feedback telling me the SMC was cleared, still the same symptoms.

And I read that entire thread, every single post of every page. My question still remains: ARE THOSE THE ONLY METHODS?

I put a new SSD in my Mac Mini and accidentally launched a Clover-based USB installer. I had no idea this thing could brick my Mac. All I did was attempt to launch the installer, and was met with a black screen for about 10 minutes. I chose to power down. Upon starting, I get the repeating...

I originally had no BT. I've had success with the AW-CE123H in my last laptop (Alienware), and got BT working with it in Yosemite. It also had both antennas for Main and Aux. My current laptop only has one cable for the Main, no secondary cable for Aux.

Sorry, that was very outdated. I've updated my signature. I'm also on El Capitan, I should have just attempted Sierra but read there are unresolved issues.

Thanks for the link and that is good to know, I was not aware of USB changes (my USB 2 and 3 ports worked immediately post-install). One more question. I wasn't even able to get the bluetooth on this AWE-CE123H working in Windows, no matter what drivers I found. Is it reasonable to assume, that...

There were no EmbeddedControl or EC references. I applied the GPE patch (it allowed me to), but still nothing in the system log.

I checked all SSDT files as well, nothing. I did skip the SSDT X files. I'll do a more accurate problem report shortly.

Sorry, here it is.

Using AzureWave-CE123H, and I am currently stuck on Step 2/BT4LE. I am on El Capitan currently, and installed BrcmPatchRam2.kext and BrcmFirmwareRepo.kext, and I am not getting any Bluetooth. Enabling WiFi was very straightforward and easy. IOReg attached.

Using AzureWave-CE123H, and I am currently stuck on Step 2/BT4LE. I am on El Capitan currently, and installed BrcmPatchRam2.kext and BrcmFirmwareRepo.kext, and I am not getting any Bluetooth. Enabling WiFi was very straightforward and easy. IOReg attached. Edit, posted on wrong thread, was...

Quick question, maybe you can answer. This is the part I'm having a problem with, it says "0 Changes" and does not allow me to Apply this patch. Everything up until this point has worked perfectly (no PS2 codes generated, using your kext). It appears my DSDT doesn't have the same _QXX labeling...

I will try another pair of headphones and see if that works. Thanks for trying!

No problem with cable, works in rear. Front panel works inside Windows and Linux.

Same thing as in MIDI setup, it's recognizing the headphones.