Jump to content

mikey1953

Trusted Member
  • Content Count

    31
  • Donations

    $0.00 
  • Joined

  • Last visited

  1. Hello - I have a Dell T3600 workstation running 10.11.6, with a single Xeon 8-core E5-2670 v1 with 32 GB ECC RAM, ATI HD5770 gfx. I set it up as a MacPro 6,1 smbios. Clover EFI legacy boot, no DSDT, no patches. Same boot flags as you, they work for me for both Yosemite and El Capitan, GFX work excellent as MacPro 6,1.
  2. I am using the newest version of iStat, v. 5.11. Here are 2 screenshots, taken after a fresh reboot, with no apps open ( other than activity monitor). Screenshot #1 is the "memory pressure" display, #2 is the "traditional" display. ? For some odd reason, now it isn't taking the 1.8-2 GB that it was earlier. Hmmm. ?
  3. But now I have another question - under the iStat menus "traditional" memory setting, why does OSX take up 1.8-2 GB of memory? That's an awfully large footprint - is it the memory swap that is the reason? I use Logic Pro as my DAW, and even with only 6 GB of RAM, I have never ran out of memory yet! Curious to say the least!
  4. Thanks so much - but I found the problem! I had also updated iStat menus, and under the memory section, the display format had changed from my usual setting of "Memory pressure" to "Traditional" setting. I had uninstalled the old iStat menus app? before I upgraded to the new one, so it must have deleted the old settings preferences. DOH! My bad! But I am glad it was an easy fix ! As far as your suggestions, I was aware of them already - but I sure appreciate your prompt consideration ! I love you guys !!!? GOOD HACK? to all !
  5. Help !!!!?????? I installed this package: HWSensors EFI v6.18.1394 pkg V2. I installed? the HW Monitor app.,? and Fake SMC ( for Yosemite) with the CPU and GPU plugins. Before I installed this, my system was using about 500-550 MB RAM at idle. After install my system is now using about 2-2.4 GB at idle !? iStats now shows that 585 MB is "wired" ( the amount of RAM my system used to use at idle) and now about 1.8 GB is "Active". iStats never showed 1.8 GB "Active" at idle before this install. I have ran Kext Wizard and Pandora's box in an effort to fix it. I was using (FakeSMC) v. 6.14.1364 previously, I reinstalled it after this issue, and still no luck. Any suggestions??? ?
  6. Help !!!!?????? I installed the HW Monitor app.,? and Fake SMC ( for Yosemite) with the CPU and GPU plugins. Before I installed this, my system was using about 500-550 MB RAM at idle. After install my system is now using about 2-2.4 GB at idle !? iStats now shows that 585 MB is "wired" ( the amount of RAM my system used to use at idle) and now about 1.8 GB is "Active". I don't remember? iStats ever showing 1.8 GB "Active" at idle before this install. I have ran Kext Wizard and Pandora's box in an effort to fix it. No luck. Any suggestions??? ? For some reason I am not seeing my signature on this post. This is my machine>>> Dell 435MT, Intel i7 920 @ 2.66GHz, XFX HD5770, 6 GB DDR3, MBox 2 Pro (Firewire), Clover 3276, OSX 10.10.5.
  7. Doesn't work on Athlon II X2 240 or Phenom II X4 980. Perhaps danutzgtx480 could take Alekseyii's advice and post a screenshot, or a link to a video, of this running successfully. Methinks this is bogus.
  8. It turns out that for whatever reason, this combination of AMD, Clover, and Mavericks is the cause of the gfx issues. After reverting to Chameleon on the same HDD, the problem has totally disappeared. The problem only appeared after switching to Clover in the first place. My system has now been up for 4 days straight. Surfing with 3 different browsers, playing games, Photoshop, and DAW recording hasn't crashed it once. So, there is no issue at all with the kernel ( AMD Kernel for OS X Mavericks 10.9.4 {XNU:13.3.0} V2.0 ) or the Vervet framebuffer. So I will stay with Chameleon without a DSDT on my AMD, and stay with Clover and compile a DSDT for the Intel i7. I have had real Macs for 17 years now, but Hackintosh is great!? On behalf of all of us users, a big thanks goes to this community, the staff, the crew and all of the developers for the vision, hard work, and support!!! GOOD HACK
  9. I need help with a dsdt for my AMD. Attached is the acpi_dsdt from AIDA64,? the .dsl from MaciASL, ioreg output, and my clover config plist. I have tried several times, but methinks this subject is somewhat over my humble head. I use both computers for DAW recording (using Logic nodes) but I plan to sell my older Intel i7 setup, and upgrade soon to a current Intel MB/CPU. My AMD running 10.9.4 is stable except for random graphic issues (screen flashes and goes to a colored background with vertical lines a few times per day). What's great is that all the ports on the XFX HD5770 work, I am driving 2 monitors and a TV/monitor at once, but I get the screen issues even with just one monitor connected.Some of my audio hardware is not supported on Yosemite, so i will remain on Mavericks for a while longer. After many successful builds over the past 4 years using Chameleon and no dsdt, I recently switched to Clover, and feel it is time to use a custom dsdt. One more question - I used AIDA64/Windows 7 to extract the dsdt, but there was no acpi/tool/ssdt option available. Is that because I am on an AMD? Thanks ahead of time to anyone that can help! ? DSDT.zip
  10. This reply is only to point to the above post as the correct answer... GOOD HACK !!!
  11. For anyone experiencing the clock gaining or losing time in Mavericks , this is the solution: My original post was written with the belief that the issue was with Mavericks on AMD using Clover as the boot loader. My initial installation was with Chameleon, and I never noticed the problem. That's not saying it wasn't there, I just wasn't aware of it. Then I switched to ?Clover, and noticed the problem. I then discovered that my Intel was doing the exact same thing. I use Clover on the Intel now too, and boot into Mavericks rather than Yosemite when I use my DAW because my MBox 2 Pro (firewire) is not supported under Yosemite (yet). ? So, I found myself getting really mad and frustrated. After a shower and some hot cocoa, I decided to look for a solution elsewhere.... ? I guess it was easy to get hung up on the idea that since they are Hackintosh machines, the problem must be with the busratio, or the bootloader, or the?config.plist, or the?chameleon.boot.plist, or the fact that one computer is an AMD. We were barking up the wrong tree. ? Voila! I found the true problem and solution! ? It is a bug in Mavericks that Apple knows about, but hasn't addressed yet. ? I found the answer on the Apple Support Communities forum : ? " ?Tim JervisJan 26, 2014 5:21 PM? Re:?Clock runs slow when I leave iMac on all the timein response to JDW1 I have had a similar problem, the clock was running slow on a Mavericks MacBook Pro I look after. After trying out several leads, one solution that worked was to change the value of the "Set date and time automatically" field in the System Preferences -> Date & Time -> "Date & Time" tab. Editing the text in the field from (in my case) "Apple Europe (time.euro.apple.com.)" to "time.euro.apple.com" fixed the problem for me. ? It appears that the text in this field gets written almost verbatim into the /etc/ntp.conf?file, which is then used to look up the time servers. Not only does "time.euro.apple.com." lead nowhere (due to the trailing "."), but Mavericks will even add "Apple" and "Europe" into the file. The end result is the time system appears unable to get a time fix, and so the clock time drifts, uncorrected. ? If you are in Japan, you might want to try "time.asia.apple.com" in that field. The key thing is to avoid the trailing ".". Just change the text in the field an close window. ? I should add that this wasn't the only step I took to debug my slow clock issue. Other steps included deleting and re-creating the /etc/ntp.conf?file and exploring the "pacemaker" process. However, I don't think these steps were necessary in the end and simply adjusting the text in the field above should suffice. I could be wrong. ? Needless to say you might have a different issue and this might not help. Good luck! ? Tim ?". ? So - The only thing I needed to do was correct the entry in the "set date and time automatically" field to > (time.apple.com) ?? I entered the new information yesterday, and all appeared well. I left the computer on all night. Checked it this morning.? The clock ?is accurate. All is well ! ? In summary, the problem is not AMD, or the boot loader, or the busratio . There is no problem with the TSCSync. The problem is a bug in Mavericks and how it writes to the /etc/ntp.conf?file. ? HAPPY CAMPER!!! GOOD HACK !!!?
  12. I found the solution to the clock gaining or losing time in Mavericks... I also discovered that my Intel was doing the exact same thing. I use Clover on the Intel, and boot into Mavericks rather than Yosemite, when I use my DAW because my MBox 2 Pro (firewire) is not supported under Yosemite (yet). ? So, I found myself getting really mad and frustrated. After a shower and some hot cocoa, I decided to look for a solution elsewhere.... ? I guess it was easy to get hung up on the idea that since it is a Hackintosh machine, the problem must be with the busratio, or the bootloader, or the?config.plist, or the?chameleon.boot.plist, or the fact that one computer is an AMD. We were barking up the wrong tree. ? Voila! I found the true problem and solution! ? It is a bug in Mavericks that Apple knows about, but hasn't addressed yet. ? I found the answer on the Apple Support Communities forum : ? " ?Tim JervisJan 26, 2014 5:21 PM? Re:?Clock runs slow when I leave iMac on all the timein response to JDW1 I have had a similar problem, the clock was running slow on a Mavericks MacBook Pro I look after. After trying out several leads, one solution that worked was to change the value of the "Set date and time automatically" field in the System Preferences -> Date & Time -> "Date & Time" tab. Editing the text in the field from (in my case) "Apple Europe (time.euro.apple.com.)" to "time.euro.apple.com" fixed the problem for me. ? It appears that the text in this field gets written almost verbatim into the /etc/ntp.conf?file, which is then used to look up the time servers. Not only does "time.euro.apple.com." lead nowhere (due to the trailing "."), but Mavericks will even add "Apple" and "Europe" into the file. The end result is the time system appears unable to get a time fix, and so the clock time drifts, uncorrected. ? If you are in Japan, you might want to try "time.asia.apple.com" in that field. The key thing is to avoid the trailing ".". Just change the text in the field an close window. ? I should add that this wasn't the only step I took to debug my slow clock issue. Other steps included deleting and re-creating the /etc/ntp.conf?file and exploring the "pacemaker" process. However, I don't think these steps were necessary in the end and simply adjusting the text in the field above should suffice. I could be wrong. ? Needless to say you might have a different issue and this might not help. Good luck! ? Tim ?". ? So - The only thing I needed to do was correct the entry in the "set date and time automatically" field to > (time.apple.com) ?? I entered the new information yesterday, and all appeared well. Then, I un-ticked the box "set date and time automatically", and left the computer on all night. Then re-ticked it this morning.? The clock ?is accurate. All is well ! ? In summary, the problem is not AMD, or the boot loader, or the busratio . There is no problem with the TSCSync. The problem is a bug in Mavericks and how it writes to the /etc/ntp.conffile. ? HAPPY CAMPER!!! GOOD HACK !!!?
  13. It can't be the bus ratio, the info I entered in CC is the info that Chameleon reported when booting in verbose mode, before I installed Clover. I tried the solution suggested , clock still runs fast, but I am not sure if it runs more accurately. ?CPU speed of 3700 / multiplier of 18 = 205.555. So I entered BusSpeedkHz=205555 in CC. Geekbench 32-bit runs ok, Geekbench 64-bit crashes, ?it didn't crash using Chameleon. I ?also tried multipliers of 18.5, and 19, and entered the resulting bus speed in CC. No difference. VoodooTSCSyncAMD.kext is for older AMD cpus, it isn't needed and makes no difference on a K8 or better cpu. Mine is K10. Tried every cache/maintenance utility. Updated the dyld shared cache. I have a feeling I have come across an unknown issue with the combination of Mavericks, AMD, and Clover. My initial install used Chameleon, and I had no problems whatsoever. Before I switch back to Chameleon, any more suggestions?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.