Jump to content


  • Content count

  • Joined

  • Last visited

About rd8111

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  1. Hello, I realize this reply is a bit old to answer your question. However, I have been doing personal and professional research the last few days into the Ryzen Threadripper. I am looking for taking advantage of the NVME SSD speeds to boot. So far, I cannot find a single motherboard manufacturer that has more than three M.2 connections on the motherboard. I am very disappointed motherboard vendors not having an already implemented method to support four M.2 connections. From many sources including AMD, the ability to boot an NVME based RAID with PCIe x4 support is a free software update September 25, 2017. I expect a simple firmware modification by the various motherboard vendors will easily support an NVME RAID boot. AMD itself does not currently know of a four NVME M.2 connector motherboard release. I hope some are coming soon. Before then, I believe a PCIe x4, Generation 3.0 to M.2 adapter card, in at least an x4 Gen 3 PCI slot, will support the fourth NVME SSD. At that moment, it will be up to the motherboard BIOS details to fully support booting with NVME RAID 10. Only ASRock clearly states in its x399 Taichi manual that NVME boot is supported. Eventually, I will be testing a Ryzen Threadripper NVME RAID 10 boot hackintosh (maybe an Epyc). That is likely no earlier for me than mid 2018. Regardless, to address your question on using an AMD hackintosh based on Ryzen, I believe it is possible for a stable running system. It will likely take some more time by the various people who love to figure these things out. When I get my Gigabyte FX8350 successfully running OS X Snow Leopard and Lion, it takes a bit of time over the course of a couple months. You will see the hardware details in my signature. I recommend waiting a bit yet before taking the Ryzen Threadripper hackintosh plunge. The biggest thing I see that can cause delay for a stable system for the render work, is making absolutely sure that the video card(s) you select are verified, working as expected in the hackintosh Ryzen Threadripper combination. It might be best to have one multiple output video card. I have read reviews of 4.0 GHz stable Threadripper operation using a water cooling solution. I prefer using Noctua manufactured heat sink air cooling. The temperatures are likely going to be in the 50C range. Oh, I also like Arctic Silver thermal paste. Once my FX8350 gets the Arctic Silver usage time complete, the typical operating temperatures are cooler by more than 8C. The massive Noctua heat sink design dissipates heat very well. The huge air flow fan is quiet too.
  2. Hello, it may not matter too much for Snow Leopard (SL) installations. But, if someone wants to find the Use LCD font smoothing setting on SL, it is located at System Preferences | Personal | Appearance (near the bottom as with General). Mavericks has the Appearance choice renamed to General. I am not sure which OS X version this rename began. Screen layout wise, both are in the same System Preferences location between SL and Mavericks.
  3. [AMD] Working Builds!

    AMD FX-8350 4.0 GHz - Factory Setting Gigabyte GA-990FXA-UD5 MB: - Audio codec RTL ALC889 working with Voodoo HDA, tests with HDAEnabler and Modifed kexts for ALC8889 have failed so far - LAN RTL 8111E working with the RTL Mac drivers for SL and Lion here - 2 rear USB 3.0 ports, PXHCD for SL here, Generic USB XHCI for Lion here - 14 USB 2.0 ports, 8 rear, two front, others are motherboard headers, all working - 2 rear eSATA - PS2 working - Firewire 1394a (does not connect to My Book in Lion, wait for like 20 minutes in SL and the drive usually appears) - Firewire 2x 1394b & 1x 1394a - SYBA SD-PEX30009 PCI Express - Installed Card, Turned On Computer, My Book Connects just like on my MacBook Pro at 1394b (SL & Lion)!!! Smoothest install of an expansion card ever!!! ATI FirePro V4900 DVI/HDMI: QE/CI with all outs in both Snow Leopard and Lion with GraphicsEnabler=N, HDMI audio appears in sound list with VoodooHDA, but not tested yet. Injected FirePro Device ID Vendor ID combination into ATI6000Controller.kext, Tutorial here Wireless LAN via USB 2.0 Realtek RTL8188CUS - Working with RTL Mac drivers. Realtek says the RTL 8191US drivers are used for SL and Lion here. Have to use the Microsoft solution (power cycle the wireless radio) upon first OS start. After that, the wireless connection is usually present the whole time. It is a very economical wirless network solution. If dying to know more about it, it is here. Logitech USB key for MX1000 Mouse 16 GB RAM: Crucial Ballistix DDR3-1600, 8-8-8-24, using all four slots 2 Internal HDs: 1x 256GB - 85 GB for SL, Lion, and ML (future), Crucial M4, 040 Firmware, SATA III, 250 MB/s Write, 500 MB/s Read (factory specification) 1x 1TB - 500 GB Data and Applications, 500 GB Time Machine, Caviar Black, WDFALS1001, SATA II, 108 MB/s read & write (factory specification) External HD: 500 GB Seagate Momentus 7200.4, connected with the Anker eSATA, USB 3.0/2.0 Hard Drive Enclosure. SATA I negotiated link speed. 82 MB/s read & write in eSATA and USB 3.0 (matches non Seagate benchmark throughput tests). Works perfectly. Snow Leopard 10.6.8, 32-bit kernel from AnV with 64-bit user land: boots very quickly when using kernel cache, about 5 seconds or less. Shuts down or restarts in about 10-15 seconds. Bootflags with Chameleon 2, r726 are busratio=20 arch=i386 -force64 GraphicsEnabler=N npci=0x2000 Lion 10.7.5. 32-bit boot: in 32-bit mode (arch=i386 npci=0x2000), the Cinebench OpenGL test executes successfully and video files on YouTube play correctly. Chameleon 2.1 r2089. Lion 10.7.5. 64-bit boot: npci=0x2000 or -v USBBusFix=Yes, UseMemDetect=Yes UseKernelCache=Yes npci=0x2000 or UseKernelCache=Yes UseMemDetect=Yes npci=0x2000 Chameleon 2.1 r2089 or Chameleon 2.2 r2187 CineBench OpenGL has the red pixel problem and covers the cars with red. I have to use the -v flag to boot with USBBusFix=Yes, otherwise kernel panic on boot. Flash and other video files do not appear on the screen. Installed Lion with Chameleon bootloader 2.2, r2187, injected the Lion ATI6000Controller.kext prior to executing the Lion retail installation purchased mid March 2013: Chameleon 2187 pkg is here. Chameleon bootloader 2.1: This version successfully boots 32-bit and 64-bit 10.7.5 Lion with the Bronzovka kernel. The Chameleon 2.1 2089 pkg is here Geekbench 64bit: 12622! Geekbench 32bit: 11330! Compares to the 64-bit 5891 Geekbench score on my 2010 MacBook Pro i5, 2.53GHz, 8GB RAM Cinebench: 6.95 pts CPU (64-bit or 32-bit), 42.74 fps OpenGL (32-bit Lion boot) Other notes: I also tested the Lion installation with myHack onto my external Seagate. It installed and worked correctly too, but I wanted to have a different boot loader solution that would support booting SL or Lion as I wish. Presently I can only boot SL successfully with Chameleon 2, r726. Any other boot loader version I have tried (Clover 1050, 12XX) cannot boot both SL and Lion. Chameleon 2.1 and 2.2 boot Lion via USB Flash formatted as HFS+ Journaled.
  4. Thanks for this information. After placing the EvOreboot.kext in the /S/L/E, rebuilding with Kext Wizard, the Lion install successfully reboots. I have restarted about a dozen times over the last few days to test it.
  5. HWSensors

    Thanks. I will monitor a bitbucket update, as well as compiling in Xcode and test in the next few days.
  6. I do not have a DVD device in my AMD system either. I am sharing my MacBook Pro DVD on my home network, but never have seen the Remote Disc device appear in the AMD Finder (Lion or SL). I have been moving files between the two Mac's Public Folders both before and after injecting the SATA controllers though.
  7. I found how to have your system's SATA controller information displayed correctly within the Serial-ATA section of the System Profiler / System Information pages. As long as you can obtain the Device ID and Vendor ID of what the system has, then it should be fairly simple. Procedure: 1) Use a program like lspci or System Info to list the devices. 2) Find all SATA storage devices, making sure each unique combination is recorded. 3) Proceed to copy AppleAHCIPort.kext to your favorite working directory from /System/Library/Extensions, as well as copying the original version to a location separate from this working directory. You may need to put the original back into /System/Library/Extensions if there is a problem later. 4) Once in the Finder, open the kext with Show Package Contents and navigate to the Contents directory, expanding it to open the internal Info.plist. 5) Once editing Info.plist with your favorite xml editor, navigate to the IOKitPersonalities section and add the necessary details for each SATA controller. Start by copying an existing entry that closely resembles the details for the added controller. I used one that already has the IOPCIPrimaryMatch sub-key. After that, proceed to modify the main key for the controller you are adding. For example, my system has both a Marvell 88SE9172 and AMD SB950. I made the sub-keys immediately below IOKitPersonalities my own invention, following the pattern of the already existing ones. For example, I entered: Marvell88SE9172AHCI AMDSB9x0AHCI 6) The Chipset Name sub-key is modified to something meaningful. The vendor name sub-key is pre-pended in the Memory section, so it may as well be absent in this value string. For example, mine are: 88SE9172 SATA AHCI Controller SB950 SATA AHCI Controller 7) Modify the IOPCIPrimaryMatch to match the Device ID and Vendor ID within your system. For example, mine are: 0x91721b4b 0x43911002 8) Finally, update the the Vendor Name to match the SATA Controller vendor within your system. For example, mine are: Marvell AMD 9) Save this working copy Info.plist to your working directory. 10) Copy this Info.plist into the AppleAHCIPort.kext | Contents directory within /System/Library/Extensions, replacing the Info.plist already there. 11) Answer the prompt for authenticating this replacement. 12) Use your favorite method to update the /System/Library/Extensions caches and permissions to be sure all is well. I use Kext Wizard, since I get tired of typing all of the commands within Terminal. 13) Reboot. 14) Inspect and confirm the new SATA controller details are now showing in the System Profiler / System Information | Hardware | Serial-ATA section. Note that no binary files are affected by this addition to the AppleAHCIPort.kext | Contents | Info.plist. Here is what the raw xml looks like inside Info.plist. The IOKitPersonalities and MCP79AHCI keys are shown for reference to assist understanding that the new controller entries have been placed alphabetically under the IOKitPersonalities key. The entries I made look like: AMD SB 950 SATA Controller Entry: <key>IOKitPersonalities</key> <dict> <key>AMDSB9x0AHCI</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleAHCIPort</string> <key>Chipset Name</key> <string>SB950 SATA AHCI Controller</string> <key>IOClass</key> <string>AppleAHCI</string> <key>IOPCIPrimaryMatch</key> <string>0x43911002</string> <key>IOProbeScore</key> <integer>2000</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>Vendor Name</key> <string>AMD</string> </dict> . . . . . . Marvell 88SE9172 SATA Controller Entry: <key>Marvell88SE9172AHCI</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleAHCIPort</string> <key>Chipset Name</key> <string>88SE9172 SATA AHCI Controller</string> <key>IOClass</key> <string>AppleAHCI</string> <key>IOPCIPrimaryMatch</key> <string>0x91721b4b</string> <key>IOProbeScore</key> <integer>2000</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>Vendor Name</key> <string>Marvell</string> </dict> <key>MCP79AHCI</key> <dict> . . . . . . I did this for both the retail Snow Leopard and Lion installations on my FX-8350 system.
  8. Hello, Does anyone know why I have to set UseMemDetect=Yes for 10.7.5 retail Lion to properly indicate 16 GB Ram, 1600 MHz in the System Information | Hardware | Memory area? This is with the 2.2 Chameleon r2187 on a FX-8350. My sig has additional hardware details. I have added the memory details into smbios.plist and they are ignored. If booted without setting the flag yes, the System Information Memory section says, "There was a problem while gathering this information." Thanks
  9. Am trying the RC12 on my FX-8350 now. For the past 30 minutes, the behavior matches the older 10.7.5 kernel. I have tried X86_64 with Cinebench, 1Password, 32-bit application for Wireless USB Key network access, Firefox, Safari, Grab, etc. Loading i386 only works with the 2.1 2059 Chameleon. With the 2.2 2187 Chameleon and i386, I get a kernel panic on the EFINvRam kext. Restart from the Apple menu has never worked with Lion. I believe it has to do with not making any DSDT modifications and/or having an smbios.plist set for iMac 12,2. The 13,2 iMac more closely matches my hardware, but Lion refused to install to a 13,2 iMac. When in i386 mode, Cinebench has the ATI FirePro V4900 with 44.03 fps. The older kernel in i386 mode is 43.87 fps. I cannot get the OpenCL_OceanWave_Bandwidth_V161 application to run the benchmark. Every time I open that one, regardless of kernel version, 64-bit mode, 32-bit mode, the program says, "Error in OpenCL bandwidth measure task." The FirePro firmware has not been modified since opening the shipping box and installing into the motherboard. The OpenCL 1.1 version is currently inside the FirePro. I have never observed the computer memory details in Lion. Is there something special to disable within Chameleon? When I boot to SL with Chameleon 2 RC5, r726, I see the memory information in the System Profiler. I have tried adding memory details within smbios.plist for Lion. No matter what I add into smbios.plist, the Memory details always say, "There was an error while gathering this information." Obviously the memory is found and the computer behaves, because other parts of the system do correctly show 16 GB at 1600 MHz, DDR3. The Lion boot logs also clearly show the same information that displays in the SL System Profiler memory section.
  10. Tried that. Still do not have the multiple core graph on the main Activity Monitor. The number of processors is always one on the System Profiler.
  11. Card: ATI FirePro V4900 Device ID: 0x67491002 Ports: 1 DVI, 2 Standard DisplayPort, HDMI (HDMI not tested yet, need to find best audio kext solution) System: 10.7.5 - 64-bit, Bronzovka 11.4.2 kernel and RC 10 Performance: Works with Safari, Grab, Preview, iCal, etc. The CineBench red pixel problem prevents OpenGL test execution. The CPU test runs though. Wake from monitor sleep works. Method to get it working: Injected my device id, vendor id combination 0x67491002 inside the ATI6000Controller.kext prior to installing Lion 10.7.5 with 2187 Chameleon. GraphicsEnabler=No, PCIRootUID=0. no mods to AppleHDA or DSDT - HDEF, DSDT - HDMI yet. After completing the initial screens for a new OS X install, some basic details, reboot, and the resolution settings are in the System Preferences | Displays. Driving two monitors (1 DVI, 1 DisplayPort to DVI adapter). Both monitors are running per resolution and refresh rate settings, screen saver, and wake from monitor sleep.
  12. I have been testing RC 10 for the last hour with large file copies (160 GB) and forcing a spotlight re-index of a 1 TB drive (about half full space wise). The system seems to behave normally. This is on an FX-8350, 16 GB RAM (sig has more details). mdworker seems to sleep and continue as needed, since the copy is from the 1 TB drive to an eSATA drive. Generally speaking, the work is being spread across all eight cores. If you want to see the usage graph of each core, you have to right click on the Activity icon in the Dock, then navigate to Monitors | Show CPU Usage. After four cores in a system, the main Activity Monitor merges the CPU Usage graph into a single chart.
  13. HWSensors

    Hello, I have installed the I installed the 2.3.5 (4503) HWMonitor version (5.1.57.zip binary). Is the History Graph supposed to close the monitor application after a few to 30 seconds? I have installed this on Lion 10.7.5, Bronzovka 11.4.2 kernel. Other specs: Gigabyte GA-990FXA-UD5 FX-8350, factory clock speed of 4 GHz 16 GB RAM DDR3-1600 ATI FirePro V4900 Chameleon 2.1 boot loader from the 3.2 MyHack install and Chameleon 2.2 r2187 boot loader The system log says: [0x0--0x28028].org.hwsensors.HWMonitor[277]: terminate called throwing an exception com.apple.launchd.peruser.501[134] ([0x0-0x28028].org.hwsensors.HWMonitor[277]): Job appears to have crashed: Abort trap: 6 This happens every time I view something for more than a few seconds. I have the GPUSensors and LPCSensors plug-ins, HWMonitor, and FakeSMC installed.
  14. Clover General discussion

    Thanks, theconnactic
  15. Clover General discussion

    Hello All, After reviewing the ati.c source some more and looking hard at the other ATI graphics cards with Device IDs around 6749 (e.g. the HD6570, Device ID 0x6759, and HD6670, Device ID 0x6758, most closely match the three connector output style of the v4900), I estimated that the Pithecia chip family is highly likely correct for the v4900. Note that the Device IDs listed for the 6570 and 6670 do indeed have odd looking values (out of sequence relative to model number). Anyhow, after determining this, I decided to test this by adding the FirePro to the ati.c listing right before 0x674A, setting everything up appropriately, compiling, creating a test 1179 build package, installing on my flash drive, and booting again. After waiting about 90 seconds while the Clover booting system inspected the system, I have finally reached the Main Clover GUI screen. I will test this more and see what happens next. When I am pleased with the results, I would like to update the ati.c source code. What is the proper procedure to add this change to the Clover source? Should the exact line be posted for someone else to add the change? The line is: { 0x6749, 0x00000000, CHIP_FAMILY_TURKS, "ATI Radeon FirePro V4900", kPithecia }, Sincerely, rd8111