Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. @notobo Thank you for your testing and feedback!
  3. Today
  4. Updated Unknown imageset, thanks to @chris1111 https://github.com/perez987/About-This-Hack/releases/tag/4.3.5
  5. @kgp Sorry, I was thinking about Intel hack. With real Macs (Intel or Silicon) audio info is different to be collected. This is the reason why About This Hack doesn't have audio tab, it was a complicated thing for me. @MaLd0n can do it, sure.
  6. @miliuco, neither USB nor Thunderbolt. It’s just the built-in native audio of my MacBook Pro M1. Since Apple silicon Macs don’t use AppleALC or VoodooHDA, perhaps Mac-Info or About This Hack could also recognize the native Apple audio implementation in the future. The same applies to the network interface, which could also be added to About This Hack. @MaLd0n could also use the more general term "Bootloader" instead of specifically showing "OpenCore/Clover version".
  7. Ok, thanks!
  8. @kgp Are you using audio by USB or Thunderbolt? @MaLd0n 's app says "HDMI/DP/GPU is ignored", maybe he can add "HDMI/DP/GPU/USB/TB is ignored" since the app looks only for AppleALC or VoodooHDA audio.
  9. Device trees and the like are very widely used with Arm devices. The Arm ecosystem is not homogenized into a set of standards like x86 systems are - you see a lot more variety in firmware, boot loaders, hardware, peripherals, etc. I doubt any of this has been purposely done to prevent hackintoshes. We are just seeing the side affects of them having custom silicon and having their own security requirements with regards to their boot chain. Remember too that they've been using ##### and their own silicon as far back as some of their earliest iPhones - bootloaders like u-boot were nowhere near as fleshed out back then than as they are now. You also see a lot of proprietary bootloaders afaik with android devices too. M1n1 was created by Asahi for what it is worth heh. You are probably thinking of #####. Edit: #####/i boot is getting censored? Huh? https://en.wikipedia.org/wiki/##### I'm not talking about anything related to tonymac or their tools, I'm trying to talk about Apple's bootloader ;-;
  10. Now need add things for silicon 🙂 I'll check it soon.
  11. https://limewire.com/d/GzrVC#guBBDPzzzx Check what missing with this
  12. 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.
  13. 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
  14. @Avery B I just noticed that you answered this. Thank you!
  15. @MaLd0n, any chance of making Mac-Info compatible with Apple silicon and macOS 27? 😇
  16. Yesterday
  17. https://asahilinux.org/docs/fw/adt/ My personal opinion : Apple intentionally designed a boot process like m1n1 (e.g. = exempli grātia) 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. 😉
  18. 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?
  19. 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.
  20. 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"
  21. 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.
  22. @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.
  23. 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:
  1. Load more activity
×
×
  • Create New...