Jump to content

Careless

Members
  • Content Count

    432
  • Joined

  • Last visited

About Careless

  • Rank
    InsanelyMac Sage

Recent Profile Visitors

3,393 profile views
  1. 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.
  2. 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?
  3. 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.
  4. 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!
  5. 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?
  6. 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.
  7. 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.
  8. 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.
  9. since updating to macOS 10.12.14, I've been seeing a recurring problem with my audio cutting out during streams and causing any browser player to show a spinning buffer icon until audio reconnects. my setup is as follows i7-2600k on Asus P8P67 Deluxe running with a good DSDT, and using clover to generate C/P states (works great) Bios version 3602 Sony Playstation Wireless Headset It's truly a one file install (DSDT), and it never suffered from audio issues like this before macOS Sierra update. The last time I tried to get audio working, it was determined that the Toleda or voodooHDA drivers or any ALC audio drivers do not work with Bios 3602, but that's fine because I don't use speakers, I use wireless headsets all the time. The bios update was a necessity to allow me to run a true UEFI boot, as I discovered that clover UEFI booting does not work with previous versions of the motherboard bios. So with the wireless headset in mind, I've been trying to figure out why I have these audio issues, and why the audio engine is disconnecting and reconnecting my devices I caught this in the console log just as it was happening. default 01:46:10.690571 -0400 kernel + IOAudioEngine[0xffffff91eefc5000]::stopAudioEngine() default 01:46:10.692424 -0400 kernel +-IOAudioEngine[0xffffff91eefc5000]::setState(0x0. oldState=0x1) default 01:46:10.692453 -0400 kernel + IOAudioDevice[0xffffff803160dc00]::audioEngineStopped() - numRunningAudioEngines = 1 default 01:46:10.692456 -0400 kernel + IOAudioDevice[0xffffff803160dc00]::scheduleIdleAudioSleep: idleSleepDelayTime = 00 default 01:46:10.692459 -0400 kernel + IOAudioDevice[0xffffff803160dc00]::initiatePowerStateChange(0x0) - current = 2 - pending = 1 default 01:46:10.692463 -0400 kernel + IOAudioDevice[0xffffff803160dc00]::protectedCompletePowerStateChange() - current = 2 - pending = 1 default 01:46:10.692468 -0400 kernel - IOAudioDevice[0xffffff803160dc00]::protectedCompletePowerStateChange() - current = 1 - pending = 1 returns 0x0 default 01:46:10.694827 -0400 kernel +- IOAudioDevice[0xffffff803160dc00]::flushAudioControls() default 01:46:10.694839 -0400 kernel - IOAudioDevice[0xffffff803160dc00]::initiatePowerStateChange(0x0) - current = 1 - pending = 1 returns 0x0 default 01:46:10.694842 -0400 kernel - IOAudioDevice[0xffffff803160dc00]::scheduleIdleAudioSleep: idleSleepDelayTime = 00 default 01:46:10.694845 -0400 kernel - IOAudioDevice[0xffffff803160dc00]::audioEngineStopped() - numRunningAudioEngines = 0 default 01:46:10.694848 -0400 kernel - IOAudioEngine[0xffffff91eefc5000]::stopAudioEngine() returns 0x0 default 01:46:12.128837 -0400 blued Connect to audio device default 01:46:12.129497 -0400 blued Connection complete (null) e00002bc My audio device (wireless headset) reconnects, and it resumes playing of youtube streams or whatnot, but I can't figure out what triggers the problem or why stopAudioEngine( ) is performed by the kernel. Any ideas?
  10. I just copy the EFI partition to a secure storage on my NAS server. if I ever need to format a USB key with EFI I just prepare it in windows with an installer of some kind (in this case, BD Utility), and then overwrite the contents of the partition with the last known good configuration. I have every EFI backup from r3065 that is known working- up to the latest r4049 that I just pushed to the live EFI partition that gets booted on system start up. much easier, and i don't need access to OSX or macdrive to retrieve the folder- and i know it works and exactly which version it is. I can access it from any OS or any device.
  11. I used BD Utility to create a windows bootable USB EFI drive, and then I copied my config into there along with the associated drivers, using the newest Clover 4049, and it booted fine! Thanks for your advice. I was concerned about updating, but now I'll just move the EFI folder I just configured over to my Local EFI folder and keep this one as a spare bootable on my desk.
  12. Hi Perdu, Our computers are nearly the same, almost identical. I have the exact same video card, and same CPU, almost same motherboard as well. Mine is showing the same information within "Graphics/Monitor". Can you describe your problem a little more? Clover seems to work fine with my configuration. I can speak a little bit of italian too, but I am not understanding what the problem is.
  13. i can access EFI from my windows install by using diskpart to mount the drive. Can I just pop the new clover CLOVERX64.efi file into the EFI\CLOVER folder and try again, or do I need to replace a lot more files?
  14. tried this, did not work for me. I am using DVI for display. I plugged HDMI cable in before booting, and unplugged at black screen, didn't fix. I plugged HDMI cable in at the black screen and waited, and unplugged, didn't fix. hmmmmmm
  15. indeed, it is booting beyond the black screen because it goes out of verbose mode console and into the black screen when booting -v, so we know it's not crashing. are you saying you got it to boot to a regular log-in screen after many attempts? so just plug in an HDMI cable and then disconnect?
×