Jump to content

Careless

Members
  • Content Count

    439
  • Joined

  • Last visited

About Careless

  • Rank
    InsanelyMac Sage

Recent Profile Visitors

3,647 profile views
  1. Hi Krazubu, Thanks for directing me to this fix in the other thread about 3602 bios during Catalina install. I managed to have the ALC codec working for a while now, I just never knew how or where to put the alcid=layout flag or didn't notice that it was a requirement, lol! I always thought I must have done something wrong. Anyway, I applied your patch to my rom anyway and flashed and reconfigured bios after taking cell phone pics to put the settings back to previous config. Everything seems great now. I don't use the audio onboard anyways, I only have headphones connected via bluetooth- but the latest versions of macOS do not allow video playback without an audio device connected. Sometimes when I am editing video and my headphones are charging, I require an audio device present to preview editing changes. I had been using Soundflower fake audio rerouting driver, but this fix allows me to use AppleALC instead of Soundflower.kext which is no longer supported for future updates anyway. Thanks again! EDIT: I just switched to alcid=11 to see if it reduced the number of input/outputs in the sound device list, and it looks like it works well. I only have 'Digital Out' and 'Internal Speaker' now, which is just what I needed. I don't use the integrated audio IO anyways, so I just need something there to allow audio-off video playback. The layout 11 menu is less cluttered. Have not tried layout 12 but see no reason to.
  2. I will check out the Sound fix. Thank you for investigating and finding a solution. As for Catalina, I have not checked my BIOS, but I just updated it now after doing some EC corrections to the DSDT.aml, and aside from having to reconfigure the keyboard modifier keys, everything went super smooth. I have not yet restarted, but at the last clover boot screen before this current boot-up, it was all purple and screwed up with the r9 280x that I am using. Not sure if it will be there when I reboot, but otherwise, no real issues. I had to switch from MacPro5,1 to MacPro6,1 to get Catalina to make an appearance, but it nothing wrong there either so far.
  3. do you know which bios version you have? I don't have the exact numbers maybe but; - 2602 I believe was compatible with ALC Audio codec - 3203 I believe (which is what I am using) does not have a compatible ALC Audio codec type defined, but it allows UEFI options that were unavailable in 2602 (which is why I chose to use it). I wonder if it only affects one version of the bios, because I've never had issues with it after upgrading to the 32xx series, except for audio which is not a problem considering I use headphones at all times.
  4. I guess my computer would be affected as well, as I have a P8P67 b3 Deluxe. is there any known way to prevent it at this point, or should we wait? Is there a particular guide you recommend for dumping the current bios and settings and restoring them should this occur in the future?
  5. Hi real3x do you know how I can extract a vanilla IOPlatformPluginFamily.kext. Been searching everywhere for one, can't find my backup either. I'm on 10.14.5 as of this morning.
  6. ---------------------------------------------------------------------------- UPDATE 2 - [SOLVED!] ---------------------------------------------------------------------------- So the problem seems to lie within whatever version ApfsDriverLoader-64.efi I was using prior to update, or perhaps the OS needed to load one last time to enable some sort of permission for accessing the apfs.efi file from the /usr/standalone/i386/ folder that I am unaware of??? Either way, I am marking this solved at this point- just update your ApfsDriverLoader-64.efi in your drivers64UEFI folder with the latest (2.0.7 release as of this post) https://github.com/acidanthera/AppleSupportPkg/releases I just dumped all the files in the Driver folder within the latest zip into my drivers64UEFI and removed apfs.efi from my previous "Update 1" edit, and it booted with no issues.
  7. [SOLVED TEMPORARILY - SEE END OF POST] Upgrading from Mojave 10.14.4, I did not make any changes to my Clover EFI folder. The version BEFORE upgrade was r4920, and latest necessary kexts to boot 10.14.5 were already installed and working for me on 10.14.4, so everything was ready to go. 10.14.4 worked fine with no issues for a while now, with the latest Clover and kexts. Upon installing macOS update, after completing the grey progress bar / apple logo screen, the computer rebooted and now Clover is not loading, and I am greeted with this screen: It's just a black screen with a solid cursor. No mouse input, no keyboard input, nothing else loads. Left it there for a while- no progress. to be clear: CLOVER DOES NOT LOAD if I select the UEFI 'Clover HDD' entry on my boot selection list. it shows the screen above I then created a bootable USB via my hackintosh laptop using the Mojave Installer and installed Clover UEFI on the ESP of the bootable USB, and then overwrote the EFI folder with my known good EFI folder backup. result: CLOVER DOES NOT LOAD if I select 'UEFI: Bootable USB' entry on my boot selection list. it shows the same screen above. I then attempted to create a bootable legacy CLOVER USB via windows: result: CLOVER BOOTS as LEGACY USB. The resulting Clover is indeed r4920 as it should be, but it does NOT list any of the MacOS partitions, I am trying now again with APFS loader for legacy . I cannot boot into UEFI Shell either on USB or on Clover drive. I tried EasyUEFI to redirect the UEFI entries to the SHELL-X64.efi file so that I can perhaps inspect the UEFI boot table to see if there is something wrong: result: Shell does not boot. Same screen as above. What is the possibility that the UEFI table in my bios suddenly corrupted? If possible, why does my Windows Boot Manager entry seem to work fine? Anyone ever experience something similar? ---------------------------------------------------------------------------- [SOLVED TEMPORARILY] The problem lies with ApfsDriverLoader.efi I managed to fix the issue by doing the following: Boot into Windows 10 Used UFS Explorer Standard Trial version to browse the newly updated, but unbootable MacOS 10.14.5 to retrieve the apfs.efi file from /usr/standalone/i386/apfs.efi Used Explorer++ opened with Administrator Privileges to access EFI partition on MacOS drive: Remove ApfsDriverLoader.efi Replace with apfs.efi from macOS drive in previous step. Reboot using MacOS EFI partition that was just modified Successfully booted and typed this post update It seems there may be an issue with ApfsDriverLoader-64.efi. Has anyone experienced anything similar? I am going to try again now with the latest version, which I believe I tried already- but perhaps it needed to do one final last load for some reason before being able to use the loader file and report back.
  8. Thanks so much, Maniac10. I'll play around with it in a day or two. Need to use the computer for some work, so I don't want any downtime. Your explanation was thorough, so I think I got all I need to tackle this further. Do you mind sending me your SSDT and your config.plist for Clover? Would help a bit to see if I have anything set incorrectly, and I can compare.
  9. Hi Maniac10. I did this modification just now, and booted back in with MacPro5,1 using the modifications you suggested. How can I be sure that it is using the appropriate P-states, or how do I go about making sure it is? Are there any other steps? Please advise. I've booted in to the new SMBIOS profile and am typing from there now. Seems the same as without the change? Do I need to add a specific ssdt now? edit: I added SDST.aml generated from ssdtPRgen, and here's what the bootlog says. 7:928 0:000 === [ DropSSDT ] ========================================== 7:928 0:000 Drop tables from XSDT, SIGN=SSDT TableID= Length=0 7:928 0:000 Table[4]: SSDT SataTabl 877 dropped 7:928 0:000 Table[5]: SSDT Cpu0Ist 2474 dropped 7:928 0:000 Table[6]: SSDT CpuPm 2706 dropped 7:928 0:000 === [ ACPIPatchedAML ] ==================================== 7:928 0:000 Unsorted 7:928 0:000 Inserting SSDT.AML from EFI\CLOVER\ACPI\patched: wrong table 7:930 0:001 CPUBase=0 and ApicCPUBase=1 ApicCPUNum=8 7:930 0:000 Cleanup XSDT: count=8, length=100 7:930 0:000 corrected XSDT count=5, length=76 "wrong table" ... is something amiss here? why do I need to change to MacPro5_1, anyway? can you point me to a post with more information?
  10. Hi Friends, I recently updated from High Sierra to Mojave on my Asus P8P67 Deluxe + i7-2600K system and everything is operating great, except I only have two processor states: 1600mhz & 3400-ish mhz. Understandably, this is due to my Sandy Bridge "second generation" processer not being compatible with the board-id for a iMac13,1- thus it would seem that the P-states or C-states generated via DropOEM SSDT and Generate P/C-states in the latest Clover are not compatible? Mojave would not allow installation unless I was using a newer chassis model, so this was my stop-gap measure for allowing the install at this time, as I had a few hours to fiddle with it this weekend between other things. Within High Sierra, I had all P-states, and as a result, my average CPU temp was a bit lower (But it's ok for now). I had the iMac12,3 SMBios loaded in clover- and everything worked great. I attempted to force/target a generated sdst.dsl using ssdtPRgen.sh, and attempted to use it in Clover- but nothing changed??? (perhaps I am using it wrong- any info here would be appreciated). My question is... how do I go about getting proper processor power management states in Mojave with a Sandy Bridge processor? Is there a way to spoof the OS into generating them via clover, or is there another chassis I can select... Or is there a way to select iMac 12,3 again which will not interfere with any Mojave specific settings or permissions or features, and can it be done without breaking anything now that I've installed? For the time being it runs ok, and I can always fall back on Win10 dual booted OS for repair or for work if need be.
  11. Careless

    Apple released macOS 10.13.4 Update

    Got it updated! I went through the second phase after making that post, and it restarted a few times throughout the process, and the clover entry disappeared on the last boot. I had a feeling it was updated- and voila! she was! I updated to the latest Clover r4428 and the AFPS.efi that someone posted earlier before selecting the "macOS Install" boot entry just to be safe. Seems all good here. Thanks!
  12. Careless

    Apple released macOS 10.13.4 Update

    Is there a way of finding out why the update keeps coming up in my App Store after rebooting during the install? It seems as though it does not want to finish the update. There is also a new clover entry, "mac OS install on Macintosh HD". Do I boot from that one after initiating the install?
  13. I have been running on a P8P67 ASUS mobo and i7-2600k with the same 16gb ram and same HD6870 video card for a number of years now. as of January, I have been controlling fan speed for both CPU and GPU using "Macs Fan Control" app, and it works well and keeps my temps stable and my fans quiet most of the time. Before applying the latest update to macOS (10.13.3), I had the ability to view the GPU Core temp within Macs Fan Control, and use it as a basis for further rules/speed settings. After updating to 10.13.3, I can no longer see the GPU Core temp, and have noticed that there is limited information in the System Information dialog... namely it says ATI 6XXX Video Card and that it is a PCIe x4 speed... I am almost certain this was not the case before the update. I installed the older version of Macs Fan Control (it also updated), just to be sure that it wasn't the problem, and it also does not show the GPU Core temp. I use Macs Fan Control because I have a larger 120mm fan mounted to the video card since the original fans started to make a lot of noise. Since doing that modification, I have plugged it into the chassis fan connector on the mobo and use Macs Fan Control to adjust the fan speed of the "chassis fan" using the temp of the GPU Core (though the fan is really mounted to the video card heatsink). Does anyone have any idea what would cause this? Have the ATIController6000.kext files been changed in the latest update? I am in Windows 10 right now on the same computer (clover dualboot) and the fan is definitely working in Windows 10. I can hear it whooshing air. That sound is gone in MacOS ever since the update.
  14. So I installed the latest 10.13.3 security update as of this post (Feb 28 was the install date). I have two 120gb mechanical SATA drives that I have reserved for large games and various types of file storage, and they are formatted to be accessed by windows. Prior to updating to 10.13.3, I had followed this guide (https://discussions.apple.com/docs/DOC-7942) and successfully disabled macOS from mounting the drives so that they would not show up in Finder or under usage of my High Sierra boot partition. After successfully completing the latest 10.13.3 update, the drives constantly spin up, coast for a minute or two with no audible access (clicking), and then shut off... only to be spun up again. This repeats over and over, and I've checked all my settings and re-checked the guide posted above to make sure the entries still matched and were still there. The drives are not mounted. They are not visible in Finder. And checking Disk Utility shows they are not accessible... yet macOS seems to want to fire them up without mounting them. I monitored the Utilities/Console.app to see what messages come up when macOS is starting/stopping these drives, but cannot find anything leading to the powering of these drives- nor could I find any information on any log errors that did seem obscure via using web searches of all kinds. Is there a way to tell macOS to just NOT power up/down these drives aside from the link I've posted? The Energy Saver prefpane has no effect on this. I have also disabled any monitoring programs that ask for drive temperature, as I am aware that this can cause the drive to be spun up to check its current temperature reading in various macOS taskbar apps that allow the use of sensor values to initiate other computer functions like fan control, etc. I have disconnected the PSU power cables from the drive temporarily, but I am hoping there is a way around this.
  15. Careless

    Apple releases macOS 10.12.5 update

    updated and working on P8P67 Deluxe with i7-2600k and Radeon HD6870 upon first reboot to finish install, during the apple logo loading screen, it said "11 minutes to go" and just quickly booted into the OS without login, with the OS completely loaded in the background. I found it odd, but it's running well so far.
×