I am new to InsanelyMac. However, I have both hardware and software development experience. I am about to obtain a Gigabyte GA-990FXA-UD5 or UD3 (Revision 1.1 or higher). It will have a FX8350 CPU with 16 GB or more RAM, and a 256 GB SSD for the OS and what not. The data files will be on a totally separate disk.
My observation (after many forum reviews) is that to run Snow Leopard well and in 64 bit mode, sinetek's future mach_kernel update for FX is the best choice. The question I have is whether it will be necessary to obtain the hardware prior to the FX kernel update and assist testing the kernel modifications for this most recent FX processor.
@sinetek: contact me if there is anything I can do to help complete the FX kernel mods.
From a motherboard perspective only, it looks like Crucial 1600 DDR3 memory and the M4 SSD are solid selections. If there are any experiences with this Gigabyte motherboard using Crucial components and Snow Leopard, please post.
I am looking forward to taking advantage of 8 cores on Mac OS X, and want to contribute to a successful AMD FX kernel.
I have finally had enough time to spend on my FX-8350 system. The details:
16 GB Crucial Ballistix DDR3-1600, 8-8-8-24, BLT4KIT4G3D1608DT1TX0
256 GB Crucial SSD (boot drive), CT256M4SSD2, Rev 040H Firmware, 6 Gigabit negotiated link speed (as expected)
1 TB Western Digital Caviar Black (data and applications), WD1001FALS , 3 Gigabit negotiated link speed (as expected)
ATI FirePro v4900
Noctua NH-C12P-SE14 (CPU Heat Sink and 140 mm fan cooling system)
Retail Snow Leopard updated with 10.6.8 Combo Update
The summary is:
- With the MODUSB from Nawcom, followed the translated directions by Akimoa, but realized that the 2.0 rc5 Chameleon Boot loader uses com.apple.Boot.plist in the Extra folder (not org.chameleon.Boot.plist - more recent Chameleon versions use org.chameleon, like Chameleon 2.2)
- Obtained both the December 2012 legacy nawcom kernel and the August 22, 2011 AnV legacy kernel, release 2
- Both boot from the SSD with busratio=20 -force64 (having arch=i386 seems to be ignored)
- Most likely the npci=0x2000 kernel flag is needed for other kernels, but this too seems to not matter for legacy kernels and the 2.0 rc5 Chameleon bootoader
- Both indicate 8 cores, one CPU
- The FSBFreq and CPUFreq are not detected correctly (always says 0MHz), although the TSCFreq is detected to be 4026 MHz
- bdmesg from Chameleon Wizard 2.2 shows 1 core, 8 threads
- About This Mac | More Info | Hardware shows
- 4.03 GHz Processor Speed (assuming this is TSCFreq)
- 1 Processor
- 8 Cores
- 16 GB Memory 800 MHz
- 2 MB L2 Cache per core
- 4 MB L3 Cache
- Mac mini 2,1
- BIOS settings for my Gigabyte are:
- Revision F9
- 4000 MHz CPU Clock (4 GHz)
- 2200 MHz North Bridge Clock (2.2 GHz)
- Core Performance Boost Enabled to 4200 MHz (4.2 GHz)
- FSB Freq 200 MHz
- HT Link Freq 2600 MHz (2.6 GHz)
- Memory Freq 1600 MHz (1.6 GHz)
[*]Obtained the sinetek kernel that starts this thread
- Most likely not ready for an FX-8350, but believe the Chameleon 2.2 boot loader on a USB is not helping things at all (see below)
- Will test booting via SSD later today (March 11, 2013)
[*]Restoring the legacy kernel booting SSD to a USB drive (via Disk Utility)
- Booting from USB fails on the seventh try of boot0, with "boot0: error" (this is the Chameleon 2.0 rc5 bootloader, with no modifications to the restored USB drive content)
- Installing Chameleon 2.2 1187 to the restored USB drive, and renaming the device_hfsplus.png and device_hfsplus_o.png files to device_hfsplus_sl.png and device_hfsplus_sl_o.png, either results in a black screen (apparently forever), or automatic computer restart. Using "-v" or "-v -f" has zero improvement. Using the boot flags that work in Chameleon 2.0 on the SSD accomplishes no joy. Adding arch=i386 also results with no joy. Any of the legacy kernels on the USB results in the same black screen or automatic computer restart. Booting with the sinetek kernel has the same results as the legacy kernel boots. Note: the png files are renamed so you can see which boot drive is selected within 2.2 Chameleon. If this is not done, then moving the arrow keys seems to do nothing, since the boot drives are always lit red. Found a reply on OSX86.net that said the 2.2 Chameleon is operating system aware (Snow Leopard, Lion, Mountain Lion, etc.). The png rename has to occur in order for the green and red lit images to load while in the 2.2 Chameleon boot screen (not a bug though).
- Have observed that before the black screen or automatic computer restart that the number of cores and number of threads are 8 and 8 respectively. This is with the 2.2 Chameleon bootloader and any of the three kernels.
[*]Have not been successful enabling Graphics for my FirePro v4900 (via SSD booting)
- Currently have "Graphics Mode"=1280x960x32
- The Grab application does not display any images, although the Preview application shows pdf content correctly.
- Believe this is expected behavior until the proper v4900 driver (kext) is loaded
- The v4900 is part of the Turks family
- The v4900 device ID is 6749, vendor ID 1002, sub-system device 2B06, with HP as the sub system company (not sure what HP's video card vendor ID is)
- Want to build 2.2 Chameleon with v4900 support and test
- The 2.2 Chameleon source cannot build on either my MacBook Pro i5 Snow Leopard or my FX-8350 Snow Leopard. Both computer systems' 1187 Chameleon builds have exactly the same results, with undefined symbols that are missing from boot_modules.c. This is Xcode 3.2.5 on both systems. Somewhere within the forums (I cannot quickly find which right now), another InsanelyMac member has the same results with Xcode 3.2.6 on Snow Leopard. I suspect that something is not correctly generating the boot_modules.c and boot_modules.h content on SL.
- Have found hints that the Clover bootloader is potentially already supporting the v4900, but installing via Clover's pkg to the restored USB fails to load the Clover boot screen. Installing only Clover to a FAT32 USB stalls at "Loading Operating System..."
- Not confident about installing the 2.2 Chameleon or Clover on my SSD, since so far unsuccessful booting from a USB drive restored from the SSD, then installing 2.2 Chameleon or Clover to the USB drive.
I am not finding some key piece of information, on how to have a restored USB drive from a properly booting system, boot from the USB without modifying the USB drive content. Is there something needing modification with the hidden USB drive's EFI partition from the restoration process? I have also tried using SuperDuper to create the USB from a SuperDuper SSD image (no joy from USB boot). I am in the process today (March 11, 2013) of using SuperDuper to copy the booting SSD directly to the USB. I tried this a bit yesterday, expecting fast joy, but was wrong. I am being more methodocal and tracking combinations today.
I have found the table listing the latest kernels and respective operating systems here
I have been experimenting with DSDT editing using the 2.2 Chameleon Wizard to extract the DSDT, edit with your favorite text editor (e.g. Xcode), and compile from the Wizard. All of the DSDT patching has been only on a USB. Until I get a successful USB drive boot, I am not confident about patching the DSDT for the SSD drive (currently no DSDT patch or SMBios.plist mods are on the SSD drive). What is the preferred tool to do DSDT editing?
The Wizard approach seems okay, but if a tool has more details about things like CreateByteField and CreateWordField, then I would prefer to use the tool. For unknown reasons, the Wizard extracted DSDT has valid warnings creating a byte field from a source and length that is more than 8-bits long. I am also wondering how to edit a DSDT to have the v4900 video driver loading there instead of a kext (is this even possible?). Does anyone know if the more recent Gigabyte boards have the same audio crackling problem that past boards have? I have found a couple sites that modify the DSDT slightly to remove the crackling audio problem. I have not tried audio yet as I am determining how to best load the audio and networking drivers (and where to obtain them). I am concentrating on solving booting, such that I can test future mods via USB boot, then update the SSD drive with successful USB booting flags, kernel files, plist, etc. Any guidance on where and how to correct "restored" USB content from a currently booting system drive would be very helpful.