Jump to content


  • Content count

  • Joined

  • Last visited

About myr1

  • Rank
    InsanelyMac Protégé
  1. I have the same blinking light on Surface Pro 1. I have been using it with OS X (10.11) for quite some time (occasional usage for ~ 2 years) without any issues. I think the blinking light just means that some hardware is not initialised (SAM? or something else?*), so nothing to worry about. (This is just my opinion, I would love to hear others' ideas.) (* this could probably be determined by running Windows in a virtual machine and connecting SAM/other USB devices to it and letting it install drivers for it)
  2. @Timelord83 1) If I remember correctly, this was caused by original/unpatched DSDT and AppleIntelFramebufferCapri.kext. Try to live with it during the installation – I'm not sure whether this has been fixed. If the white screen still appears after booting the installed OS X, check that you are using the correct DSDT and AppleIntelFramebufferCapri.kext. 2) This may be caused by an expired certificate. Apple signs Installer packages for verification before installation. If the signature is no longer valid (certificates expire after some time), it can trigger this error. Check that your date/time is set correctly (e.g. in Windows, if you still have those installed, or in the installer: Utilites > Terminal, then type date). If it is correct, try changing your date to ~1 week after the release of the version of OS X you are trying to install. See here for more information: http://apple.stackexchange.com/questions/216730/this-copy-of-the-install-os-x-el-capitan-application-cant-be-verified-it-may-h
  3. If it didn't ask you for language, you may want to look at Clover's config.plist into GUI/Language. (Docs here)
  4. @caleidosCope Have you tried reinstalling the previously used AppleIntelFramebufferCapri.kext (via KextDrop)? The 10.11.2 update contains a new version of that kext that would need re-patching.
  5. @caleidosCope (and others with battery detection issues) There you are! (see the attached dsdt) Please let me know if it works. About the AppStore/iMessage problems, as @futaris said, you should install RehabMan's NullEthernet.kext. You may also need to generate "your own" valid serial number. You can find more details in the Mavericks thread. (sorry I can't help you with the wireless dongle issues, I use an Ethernet connection) dsdt.aml.zip
  6. @caleidosCope Do you have AcpiBatteryManager.kext in EFI/CLOVER/kexts/10.11 or Other? Is it loaded? (is org.rehabman.driver.AppleSmartBatteryManager in kextstat's output?) If yes, there could still be a problem with multiple batteries. There are two battery devices (BAT0: the internal and BAT1: probably prepared for the "Surface Power Cover" accessory). Deleting or disabling BAT1 may help. (Let me know if you want a patched DSDT without it.) Re: How did you edit your dsdt? Take a look at the history of commits that changed dsdt.asl file at the github repository: https://github.com/myr1/SurfacePro1-DSDT/commits/master/dsdt.dsl After selecting a specific commit you should see what changed (added/removed lines) along with a short description (commit message).
  7. Yes. (Tested with Reflector 2 as I don't have an Apple TV)
  8. @ducati996 I don't see any entry, just this text: "This computer doesn't contain any PCI cards or devices. If you installed or connected, a PCI card or device, make sure they’re properly installed." Is there supposed to be any? (Even my MBP shows the same text.)
  9. @coasda Thank you for the info. I also dug a little deeper into the bluetooth problem. The Wi-Fi/Bluetooth device has not been even enumerated by OS X, which pointed me to a lower-level problem (a USB controller kext or DSDT). Booting without DSDT (without audio, video acceleration, ...) indeed worked (the bluetooth device was visible), therefore the error is in DSDT. So I tried to compare the "vanilla" DSDT and the one linked from the first post by JahStories, but I could not wrap my head around it (the diff of disassembled asl's was too complex for me to understand) so I decided to start from scratch, doing only the necessary edits to the DSDT. I took the stock DSDT (maybe just autopatched by Clover), fixed graphics, backlight, audio, battery and added NullEthernet. Everything seems to work the same as with the previous DSDT, but the bluetooth device is now visible and AvastarFwLoader successfully loads the firmware to it, so the bluetooth works! The resulting DSDT (see the attachment) differs from the JahStories' DSDT from the first post in following: no IRQ changes no device or variable renamed no unnecessary _DSM method added (there was probably the issue that caused Avastar not to be detected) no smbus device added no ADFU device added (what is it?) used different (simpler?) battery patch I hope the new DSDT will be a bit easier to maintain since there is nothing that does not have to be there. I have published the process here: https://github.com/myr1/SurfacePro1-DSDT The resulting DSDT is attached. Bonus: it has not crashed on boot yet (which happened to me a few times with the older DSDT). Might be just a coincidence though. dsdt.aml.zip
  10. @JahStories You are right, but it did not show any audio *input* device on my Surface Pro, only outputs. Maybe it was just my error... @coasda Regarding the Bluetooth mystery (working for you while according to jape it technically can not work): Did you do a "cold boot" or did you just reboot from Windows/Linux/other OS where Bluetooth works (or attached the bluetooth device to a virtual machine with such a system)? It is possible that the firmware has been loaded by another driver in another system, but survived until OS X finished booting... (An offtopic question for programmers more experienced with EFI: would it be possible (and practical) to implement the AvastarFwLoader as an "EFI application" that would be somehow (as Clover plugin?) executed from Clover during every boot? If yes, we could (hopefully) avoid future problems caused by changes in the OS X API.)
  11. Hi, if anyone is interested in audio input, you can try using the patched AppleHDA kext (AppleHDA-272.18.1-ALC280.zip) from http://www.insanelymac.com/forum/topic/298663-applehda-for-yosemite/?do=findComment&comment=2027485. With that kext I see following audio devices: Speaker and Internal microphone (without headphones connected) or Headphones and Line in (with headphones connected). Speaker, Internal microphone and headphones work, but I am not sure if the Line in works. Blowing into the headphones' microphone did not show up in the "VU-meter" in System Preferences (maybe the signal was just too weak). (I would prefer having an external microphone instead of line in. I think it should be achievable by patching layout*.xml.zlib in kext's Resources.) In addition to the "new" AppleHDA I use the newest version of EAPDFix.kext (with the same configuration (in "Info.plist") as the one included in the file pack). The modified EAPDFix.kext is attached. (To install: remove the previous kexts from /System/Library/Extensions/, then install both new kexts with Kext Drop and reboot.) EAPDFix.kext (v2.0.1), SP1.zip
  12. (surfaceosx) Thanks! After replacing DSDT and SSDT from "SP1 0.4 (Re-FIXED).zip" I have managed to boot into vanilla OS X Yosemite 10.10 Beta1 (installed on a USB drive on MacBook Pro) on Surface Pro 1.
  13. (surfaceosx), maybe even (surface2osx) For anyone who would like to use a "keyboard shortcut" to increase/decrease the brightness level: I may have found a way how to do it. Try pressing "volume up"/"volume down" buttons on the side of your tablet while holding the "windows logo" key below the screen. The "volume down" button increases the brightness, "volume up" decreases it. Bonus: there may be a way how to change the resolution from an attached keyboard. Open "Keyboard Viewer" (needs to be enabled in System Preferences) before pressing the described key shortcut to see which strange key combination it causes. You can then try to press the same keys on your keyboard, if possible. As I don't have the Surface keyboard ([Type|Touch] Cover) I have no way of trying it myself. P.S. Thanks for the great work!
  14. myr1

    DSDT for HP TC4400

    Try pressing the "wireless switch" (hardware button to turn on/off BT+WiFi) and restarting. I think it showed me the normal (not crossed) bluetooth icon. I didn't have any luck with installing the card reader kext. I've tried many, but none of them worked. (Probably just needs to have edited Info.plist inside the kext or the binary should be patched. It could also be completely incompatible with Mac OS X just like Intel wireless, which is unlikely.)
  15. myr1

    DSDT for HP TC4400

    Here is a new version of DSDT. Changes in RTC, HPET, LPCB, TIMR and PIC. This means USB is working at its full speed (480 Mb/s), lower CPU temperatures, Bluetooth fixed. Still not working: Sleep (not tested), Wi-Fi (Intel) - missing kext. I forgot to mention that I am using bautzen's kexts and bootloader from bautzen's guide: http://www.kexts.com/downloads.php?do=file&id=1716 Enjoy dsdt.aml_7IRQFIXES_HPET_RTC_TIMR_PIC_.zip