Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. You did not understand me. I was using only BlueWakeFixup kext in Sequoia and symptom was same when I used your old solution with boot arg and patched BlueToolFixup kext. I made test in Ventura with BlueWakeFixup kext and this symptom does not exists, it functions 100% safe. Ventura also had this problem with BT after wake which your kext finally fix. I will make further tests to see why Seqoia wake at random level approx. 2-3 hours. Cheers on your work m8.
  3. Today
  4. Oh my God! I remember the experience of the first 68K Macintosh emulator on PC. I loved to see System 7, but not afforded a Mac. Now it can be emulated in a webside infinitemac.org
  5. HP ProOne 400 G1 AiO HD4600 macOS XXXXX Internal LCD goes black after verbose. OCLP applied twice. Tried multiple ig-platform-id values. Looking specifically for someone who booted this exact AiO model. config.plist
  6. @Avery B I just noticed that you answered this. Thank you!
  7. @MaLd0n, any chance of making Mac-Info compatible with Apple silicon and macOS 27? 😇
  8. Yesterday
  9. https://asahilinux.org/docs/fw/adt/ My personal opinion : Apple intentionally designed a boot process with m1n1 and a hardware management layer that bypasses the traditional SMBIOS, specifically to prevent compatibility with Hackintosh bootloaders. Only after extensive reverse engineering by the Linux community were the necessary mechanisms understood. Even then, there will likely remain system-level restrictions preventing macOS from running on other ARM platforms or on Intel hardware. You can save some money along the way, which will be much better than trying to invent another bootloader. 😉
  10. Hello everyone, how has the experimental TurboQuant engine been working for you compared to the Bundle? I'm planning to keep just a single engine for maintainability, since managing both takes up too much time... if a bug occurs in one, I have to fix it in both. Honestly, in my testing, both have been stable. But it all comes down to what you say, as this is for the community, not just for me... so... what do you think?
  11. Hi @Slice On Apple Silicon Macs, macOS does not rely on a traditional SMBIOS like Intel PCs or Hackintoshes. The serial number, hardware UUID, and other identifiers are stored in secure hardware components and provided by Apple’s firmware during boot. Unlike a Hackintosh, where OpenCore injects SMBIOS data, Apple Silicon Macs obtain these values directly from the hardware and the secure boot chain. That’s why the serial number cannot simply be changed or spoofed like a typical SMBIOS. In short: macOS knows the serial number because it is securely stored in the device and exposed by Apple’s firmware, not because it reads a conventional SMBIOS table. I noticed some differences after performing a full firmware restore with the IPSW file on my M4 Pro. Unlike a regular macOS reinstall, the restore process also reinstalls low-level firmware and rebuilds parts of Apple’s secure boot chain, which may explain why some issues disappeared afterward. That’s why I was able to use the operating systems and applications required for my work at the court. Justice.
  12. https://www.fosslinux.com/157744/macos-27-golden-gate-breaks-asahi-linux-what-it-means-and-how-to-recover.htm "macOS 27 Golden Gate Breaks Asahi Linux — What It Means and How to Recover"
  13. However, be careful when installing Asahi Linux, whether on Arm64 or Intel (especially T2 Macs), because uninstalling it requires specific commands. This happened to a colleague from Discord who wasn’t aware of that. I had to help him using commands in Recovery Mode. It doesn’t uninstall as simply as people might expect, because Apple’s EFI does not understand what is happening within the disk clusters. By the way, the developers’ page currently recommends not installing Golden Gate alongside Asahi Linux. Be especially cautious if you plan to dual-boot, as there may be compatibility and boot management issues that are still being worked on.
  14. @kgp Excellent scores for the M1! This is a 15.6" M4, bought a few days ago. Trying Golden Gate in it. Logically, the score is better, but not that much better if you consider the 5 years between them.
  15. This time, the Sparkle update to v4.3.4 (1634) worked perfectly. Many thanks again for your hard work and to @chris1111 for providing the corresponding images. 💯 I am very happy with macOS 27 beta 2, which works amazingly well for being only the second beta release on this old silverback. What a pity that we cannot run macOS 27 on our Hacks. With macOS 27 beta 2 (26A5368g), Apple appears to have fixed the following issues on my MacBook Pro M1: Keyboard and trackpad now work immediately after waking from sleep or opening the lid. No Wi-Fi issues after waking from sleep or opening the lid. Secondary click now works perfectly when configured as "Click in Bottom Right Corner". Below are a few benchmark results:
  16. @kgp @MacNB There was a mistake in the appcast.xml file, I create the releases in the Mac laptop forgetting that the Sparkle key saved in the keychain was different than in the Hack, so the update was improperly signed. Already fixed, please tell me if there is any issue. Thanks. @kgp How does the M1 handle on the Golden Gate? Are you satisfied with it?
  17. That's why prompt engineering is a thing now. It's all about how to ask or tell the AI what you need and get the right answer.
  18. https://asahilinux.org/docs/fw/adt/ Fascinating project fyi more info on dumping them
  19. Thanks for the link. That looks like an interesting project.
  20. Apple macs use a modified version of device trees which are commonly seen used with arm devices. They are just a tree of devices and properties with no logic/code behind them. Can view a few examples of what they look like (though keep in mind this is from Linux which uses the full FDT standard rather than the simplified version used by Apple) https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/apple/t6020-j414s.dts
  21. @notobo You no longer need to use the patched version of BlueToolFixup or the boot argument -btlfxwakecrash. You can now use the standard BlueToolFixup without my wake-related fixes. To fix the wake issue, simply use my BlueWakeFixup kext. No additional boot arguments or extra configuration are required.
  22. Maybe @fantomas @Max.1974 can try to pick those files for ya. 😃 Or if is not possible to get the ACPI files, will according with this phrase from Max's link: "If an Arm system does not meet the requirements of the BSA and BBR, or cannot be described using the mechanisms defined in the required ACPI specifications, then ACPI may not be a good fit for the hardware."
  23. I am using 4.3.2 and it prompted me to install update (my auto update is turned off). but I got this error:
  24. @miliuco, my friend! Code signing error during the Sparkle update but the new version of the app works flawlessly with my MacBook Pro 2020 M1 and MacOS 27 Golden Gate beta 2! Thanks for the great work you are doing for all of us BTW.. Sparkle Update to Download Full Installer v.4.5.1 (252) worked flawlessly 👍
  25. What about SMBIOS from Apple Silicon? How macOS knows a serial number of the Apple Silicon machine?
  26. Updated to Golde Gate. Not very useful for hackintohes, anchored to Intel, but at least we can see the system well detected in the Silicon Macs.
  27. Slice

    Bad stories...

    Yes, it will be very useful as a tool like "write me a procedure for sorting the array...". But it is quite stupid when I ask "help me to find an error in my sources...".
  1. Load more activity
×
×
  • Create New...