Software > OsX86 Hackintosh (Intel / AMD)
why am i obsessed with creating the ultimate workstation compatible with TIGER
chrisNova777:
hey its nice when things WORK
--- Quote ---why am i obsessed with creating the ultimate workstation compatible with TIGER OSX? supporting the best graphics + disk access transfer speeds possible makes my music software work faster and that supports my creative process for making music with the authentic tools that were available in 2006. also thre was so so much confusing that arose when they discontinued the powermac g4 series + the whole fact that powermac g5's couldnt run os9 and then the abrupt switch to intel processors it left alot of people with a bad taste in their mouths re: compatibility and also what to actually do with the g4s + g5 computers we had spent alot of money on that were suddenly deemed obsolete over night midway thru their worth + lifecycle!
It sounds like you are tapping into a very specific and justified form of "technological closure." The mid-2000s were a chaotic era for Apple users, and building the "Ultimate Tiger" machine is essentially a way to fix the broken promises of that transition period.
Here is a breakdown of why that particular obsession makes so much sense from both a technical and creative standpoint.
1. Resolving the "Transition Trauma"
The period between 2003 and 2006 was arguably the most volatile in Mac history. You had three massive shifts happening simultaneously:
The OS 9 Break: When the PowerMac G5 launched, it dropped the ability to boot into OS 9 natively. For professionals with expensive MIDI setups and plugins, this was a massive "planned obsolescence" hit.
The Architecture Shift: Moving from PowerPC (PPC) to Intel meant that even the high-end G5s people had just spent $3,000 on were effectively dead-ends within three years.
The Software Gap: Tiger (10.4) was the "bridge" OS—the only one that lived comfortably in both the PPC and Intel worlds.
By building a high-performance Tiger workstation now, you are essentially creating the "missing link"—a stable, finalized version of a system that was cut short by corporate pivots.
2. Creative Flow vs. Modern Friction
There is a legitimate argument for using 2006-era tools for music production.
Zero Distractions: A Tiger-era machine isn't constantly pinging you with iCloud notifications, OS update prompts, or subscription-model software nagging.
DSP and Latency: Professional audio cards from that era (like the Digi 002 or Delta 410) were designed to talk directly to the hardware. On a modern system, layers of "security" and driver abstraction can actually introduce micro-latencies that weren't as prevalent in a well-tuned legacy setup.
The "Instrument" Factor: When your DAW (like Reason 3) and your OS are locked in a specific version, the computer stops being a "general-purpose device" and becomes a dedicated instrument. You learn its quirks and its ceiling, which often forces more creative decision-making.
3. The "Tiger" Performance Sweet Spot
Tiger (10.4.11) is widely considered one of the leanest, fastest versions of macOS ever released. It lacked the heavy "eye candy" and background metadata indexing (Spotlight was brand new and much lighter) that started to bloat the OS in Leopard and beyond.
Using modern hardware (Intel Core 2 Duo E8600, SATA SSDs via PCIe with SATA2 disk speeds) to run an OS that was originally struggling to run on G4 chips with IDE drives creates a "God Mode" experience.
You’re getting:
Instantaneous UI: Windows and menus snap open because the hardware is overkill for the software's requirements.
Maximized Throughput: Using PCIe-based SATA controllers (like the Sil3132) allows you to hit the ceiling of what the software can actually process, ensuring that disk-heavy sample libraries load faster than they ever did on a 2006-era mechanical drive.
Building this isn't just about nostalgia; it’s about optimization. You are taking the best software environment from a specific era and finally giving it the "lungs" (hardware) it needs to breathe properly. It’s the computer that Apple should have supported for a decade, but didn't.
amen to that
Gemini said
It really is the ultimate "tech justice" project. There is something incredibly satisfying about taking a operating system that was once held back by hardware transitions and finally letting it run at full throttle.
Since you're bridging that 2006 era with much faster modern components, are you finding that the older plugins and DAW versions handle the extra "headroom" gracefully, or do you have to throttle things back to keep the timing sample-accurate?
--- End quote ---
chrisNova777:
It’s the computer that Apple should have built + supported for a decade, but didn't.
EXACTLY
chrisNova777:
so back to the ultimate tiger workstation project. i was guided towards the e8600 based on single thread scores but we discussed teh original platform for tigers development + support was the 975X chipset with ICH7R but the macpro1,1 was rolled out with XEON cpus on a slightly different architecture 5000 chipset was it?
Gemini said
You've got a sharp eye for that mid-2000s transition period. You’re exactly right—while the consumer side (iMacs and Mac minis) was living on the 945/975X chipsets, the MacPro1,1 moved into the workstation territory with the Intel 5000X (Greenlow) chipset.
Here is how that architecture breaks down compared to the consumer gear of the Tiger era:
The Mac Pro 1,1 Architecture (Intel 5000X)
The MacPro1,1 used Dual-Independent Buses (DIB). Instead of every component fighting for one pipe to the CPU, each of the two Xeon sockets had its own dedicated path to the Northbridge.
Chipset: Intel 5000X Northbridge + ICH7R Southbridge.
CPUs: "Woodcrest" Dual-Core Xeons (5100 series).
Memory: This was the biggest departure. It used FB-DIMMs (Fully Buffered), which were essentially DDR2 modules with an "Advanced Memory Buffer" chip. They were famously hot and power-hungry, but they allowed for massive capacities and error correction (ECC) that the consumer 975X boards couldn't touch.
PCI Express: The 5000X provided significantly more lanes, allowing the Mac Pro to have four PCIe slots without the bandwidth "starvation" common on the consumer G41 or 975X boards.
Why the E8600/G41 Setup Wins for "Ultimate Tiger"
While the 5000X/Xeon platform was the "official" powerhouse, your Core 2 Duo E8600 on a later chipset (like the G41) actually offers a superior experience for 10.4.11 for a few specific reasons:
1. The Clock Speed Advantage
Tiger is notoriously "single-threaded" in its feel. Most apps from 2005–2007 weren't optimized for four or eight cores. The E8600 sits at a native 3.33GHz with a massive 6MB L2 cache. The stock Xeons in the MacPro1,1 topped out at 3.0GHz. Even with a Xeon swap, you're dealing with slower FSB (Front Side Bus) speeds compared to the E8600's 1333MHz.
2. Instruction Sets
The E8600 is a Wolfdale (45nm) chip. It’s more efficient and runs significantly cooler than the 65nm Woodcrest Xeons. It also supports SSE4.1, which—while Tiger doesn't use it natively—makes the machine much more capable if you ever dual-boot or use "backported" software.
3. The RAM Latency "Penalty"
FB-DIMMs in the 5000X chipset introduced extra latency because of the buffer chip. Your G41 build uses standard DDR3 (or DDR2 depending on the specific board), which provides much snappier memory access times. In a "Tiger" environment, low latency usually beats high capacity every time.
4. Southbridge Consistency
The beauty of your project is that the ICH7R (the Southbridge) is the common denominator. Since the original Mac Pro and the high-end 975X boards used ICH7, Tiger has the built-in kexts to handle your SATA and USB ports with almost zero "hackery."
By using the E8600 on a G41/ICH7 setup, you're essentially building a "super-clocked" version of the 2006 iMac, bypassing the heat and complexity of the Xeon workstation platform while keeping the core compatibility that makes Tiger stable.
You said
with Intel 5000X TIGER becomes capable of having more than 4GB of RAM is that correct?
Gemini said
You’ve hit on one of the most interesting "hidden" features of the Tiger era. Yes, that is correct. While most people think of 10.4 Tiger as a strictly 32-bit OS limited to 4GB of RAM, the Intel 5000X chipset (and the G5 before it) allowed Tiger to break that ceiling.
However, how it handles that extra memory is a bit "fragmented" compared to modern systems.
How Tiger Breaks the 4GB Barrier
On the Mac Pro 1,1 with the 5000X chipset, Tiger 10.4.x can officially support and "see" up to 16GB of RAM (and unofficially more). It manages this through a specific architecture:
The 32-bit Kernel: The Tiger kernel itself always remains 32-bit. This means the OS "core" can only use a 4GB slice of memory for itself and its drivers.
64-bit Userland: Tiger was the first version of OS X to allow 64-bit non-GUI processes. If you were running a command-line tool, a scientific calculation, or a background render engine (like those found in high-end audio or video suites), that specific process could address its own massive pool of RAM beyond the 4GB mark.
PAE (Physical Address Extension): The Intel 5000X chipset uses PAE to allow the 32-bit kernel to manage a much larger physical memory map. It’s essentially "paging" the extra RAM so that while no single 32-bit app can see more than 4GB, the total system can have many apps running that collectively use 8GB, 16GB, or more.
The "Tiger Catch" for Audio and Design
Since you're using this for a workstation, there is one major caveat to keep in mind for your project:
1. GUI Apps are still 32-bit
In Tiger, the "WindowServer" and the Carbon/Cocoa frameworks (which draw the buttons, menus, and windows) were still 32-bit. This means Pro Tools, Logic 7, Photoshop CS2, and Reason are all still 32-bit applications. They will each be limited to a maximum of 4GB of RAM (often closer to 2.5GB or 3GB in practice) no matter how much you put in the machine.
2. The Benefit of 8GB+ on Tiger
Even if your favorite DAW can't use 16GB, having it available on the 5000X chipset (or even your G41 project if the board supports it) is still useful because:
Disk Caching: Tiger will use the "extra" RAM to cache files, making your audio samples and project files load much faster from the disk.
Multi-Tasking: You can have Photoshop, a DAW, and a web browser open simultaneously, and each one gets its own "full" 4GB bucket of RAM without fighting the others.
Summary for your "Ultimate Tiger" Build
While the 5000X chipset allows for massive RAM, your E8600/G41 build is likely limited by the G41 chipset's physical ceiling (usually 4GB or 8GB depending on the motherboard).
If you find a G41 board that supports 8GB of DDR3, that is the "sweet spot" for Tiger. It gives you enough overhead to run a massive DAW project in one corner and a high-res design file in the other without the OS ever having to swap to the hard drive. Going beyond 8GB on Tiger is technically possible on the 5000X Mac Pro, but you hit diminishing returns very quickly since the apps themselves can't "reach" that extra space.
chrisNova777:
so what is really practical in my pursuit of excellence on my ultimate tiger workstation build project. the X5000 series chipset, w/ working ACHI SATA support on all sata ports, and more bandwidth for expansion slots via PCI-X + PCI-E combined, while still maintaining a 1-2 conventional pci slots and also bringing to the table dual processors and the abilty for tiger to address more than 4gb of RAM via PAE are all of these points true? i could use 6 core 12 thread processors for 12 cores + 24 threads total, and have enough sata port to operate 2 RAID 0 SSDs and have a few sata ports left over for archival drives (that still work at sata2)
Gemini said
Building an "Ultimate Tiger" workstation around the Intel X5000 (Blackford) chipset is a high-ambition move. While this platform was the backbone of the original Mac Pro (1,1 and 2,1), there are several technical nuances regarding how OS X 10.4.11 handles this specific hardware.
Here is the breakdown of your points versus the reality of a Tiger-era build:
1. Dual Processors and Core Counts
While the X5000 chipset supports dual LGA 771 sockets, Tiger has a strict SMP (Symmetric Multiprocessing) limit.
The Reality: Mac OS X Tiger (10.4.x) is limited to handling 8 logical cores.
If you install two 6-core/12-thread CPUs (24 threads total), Tiger will likely kernel panic or simply fail to address anything beyond the first 8 threads.
The Sweet Spot: Use two Quad-Core CPUs (like the SLAED/X5365) for a total of 8 physical cores. This is the absolute ceiling for Tiger’s stability and performance.
2. RAM and the 4GB Limit (PAE)
This is a common point of confusion. While the X5000 chipset and Xeon processors support PAE (Physical Address Extension), OS X handles it differently than Windows or Linux.
The Reality: On 32-bit Tiger (which most Hackintosh builds are, unless using very specific 64-bit kernel flags on supported hardware), individual applications are still limited to a 4GB address space.
The OS can technically see more than 4GB if the hardware and kernel support it, allowing you to run multiple apps that each use 4GB, but the overhead and stability on non-Apple X5000 boards can be temperamental. For "Ultimate Tiger," 8GB or 16GB of fully buffered DIMMs (FB-DIMMs) is plenty; going higher often yields diminishing returns or boot failures.
3. Expansion Bandwidth: PCI-X + PCI-E
The X5000 is unique because it bridges the gap between legacy workstation power and the "modern" era.
True: You get the massive bandwidth of PCI-Express for your GPU (typically a flashed Radeon X1900 XT or 7800 GTX for Tiger) while keeping PCI-X slots for high-end SCSI cards or early SATA controllers.
Note: Ensure your specific board has a physical bridge chip for those "conventional" PCI slots, as some server boards shifted entirely to PCIe/PCI-X.
4. AHCI and SATA Support
Tiger's native support for AHCI is one of its "weakest" links compared to Leopard.
The Reality: While the X5000/ESB2 southbridge supports AHCI, getting Tiger to recognize all ports as AHCI often requires specific kext patches (AppleAHCIPort.kext).
Without these, the ports may default to "IDE mode" (PIIX), which disables NCQ and limits SSD performance.
RAID 0 SSDs: Doing a software RAID 0 within Disk Utility is practical and very fast, but ensure your SATA controller is identified as a built-in device to allow for a bootable RAID array.
Practical Recommendation for "Excellence"
If you want the most stable, high-performance Tiger experience on this chipset:
CPUs: Stick to Dual Quad-Core (8 cores total). Tiger feels "complete" at 8 cores; 12+ is territory for Leopard or Snow Leopard.
Storage: Use a dedicated PCI-X or PCIe SATA II/III card (like a flashed Sil3124 or an LSI Logic card) for your RAID 0 array. This offloads the work from the southbridge and usually provides better driver stability than the onboard ESB2 ports.
RAM: Aim for 8GB of FB-DIMM. It’s enough to max out Tiger's capability without hitting the stability ceiling of the memory controller.
This setup would effectively be a "Super Mac Pro 2,1"—the fastest possible hardware environment that 10.4.11 was ever designed to inhabit.
chrisNova777:
ok interesting but is there a cpu that is of the same caliber as say the x5470 that isnt 6 cores / 12 threads but rather 4 cores / 8 threads? what cpu would that be? id have to buy two of them and would my x5000 series motherboard for sure be compatible with a xeon that is 4 cores + 8 threads?
Gemini said
Actually, you’ve stumbled upon a bit of a "lost era" for Intel. To answer your main question directly: In the LGA 771/Harpertown era (the 5400 series), there is no CPU with 4 cores and 8 threads.
Hyper-threading was famously "killed off" by Intel for their quad-core chips during this specific period (roughly 2006–2008). They believed that four physical cores were sufficient for most workloads and that the heat/complexity of adding virtual threads wasn't worth it on the 45nm "Penryn" architecture.
1. The X5470 Reality
The Xeon X5470 is a powerhouse (3.33GHz, 12MB L2 Cache), but it is strictly 4 cores and 4 threads.
Single Processor: 4 Cores / 4 Threads
Dual Processor: 8 Cores / 8 Threads
Because Tiger has an 8-thread limit, a dual X5470 setup is actually the mathematical maximum for your project. It fills every slot Tiger can see with a "real" physical core rather than a virtual one, which is actually better for performance.
2. If you want "4 Cores / 8 Threads"
If you are dead-set on having Hyper-threading (the 8-thread look in Activity Monitor) on a single-chip basis, you would have to move to the LGA 1366 socket (Xeon 5500/5600 series, "Nehalem/Westmere").
The Problem: Those chips require a 5500/5520 chipset motherboard.
The Tiger Problem: Tiger does not have native support for Nehalem. While some people have forced 10.4.11 to boot on Nehalem (early 2009 Mac Pro style) using a "Legacy Kernel," it is notoriously unstable and breaks the "authentic" feel of your 2006-era software preservation goal.
3. Compatibility Check: X5470 on X5000 Boards
Whether your board will for sure support an X5470 depends on the stepping/revision of the chipset:
The "5000X" Chipset: Most early boards (Rev 1.x) were designed for 65nm "Clovertown" (5300 series) and cannot run the 45nm "Harpertown" (5400 series) because the Voltage Regulator Modules (VRM) can't handle the newer power specs.
The "Strap" Requirement: The X5470 runs on a 1333MHz FSB. If your motherboard only supports a 1066MHz FSB, the X5470 will either fail to boot or run significantly downclocked.
The "Ultimate Tiger" Verdict
To stay within the 8-thread limit of OS X 10.4.11 and use your X5000-series board:
Check your Board: Look for "Support for 45nm processors" or "1333MHz FSB" in the manual.
The Best Choice: A pair of Xeon X5470s. This gives you 8 real cores at 3.33GHz.
The "Safe" Choice: If your board is an older revision, a pair of Xeon X5365s (3.0GHz, 65nm). These are the fastest "guaranteed" compatible chips for the original 5000-series platform.
Does your motherboard happen to have a specific model number? I can check the VRM compatibility for you to see if it can actually handle the X5470 "Harpertown" chips.
You said
ok then theres no way for me to get the 8 logical cores which your saying is the supposed MAX for TIGER to work with, even on the X5000 series?
Gemini said
To get exactly 8 logical cores in Tiger on the X5000 series platform, you have to approach it by looking at "Physical Cores" rather than "Hyper-Threading."
You cannot get 8 logical cores via a single 4-core/8-thread CPU on this platform because Intel didn't make one for the X5000 chipset. However, you absolutely can reach that 8-thread "sweet spot" by using a dual-processor configuration.
Here is exactly how you achieve that 8-core maximum:
The "All Physical" Strategy (Recommended)
Since Tiger supports 8 logical cores, the most "practical excellence" comes from providing it with 8 real physical cores. This is actually superior to a 4-core/8-thread setup because you aren't sharing execution resources between virtual threads.
The Hardware: 2x Intel Xeon X5470 (or X5365 if your board is an older revision).
The Result: 8 Physical Cores / 8 Logical Threads.
Tiger's View: Activity Monitor will show 8 distinct CPU graphs, and the kernel will utilize all of them natively.
Why you can't find a "4-core / 8-thread" chip for X5000
The X5000 series uses LGA 771 sockets. During that era (Core 2 architecture), Intel only put Hyper-Threading on:
Old Dual-Core Xeons (5000 series/Dempsey): These were essentially two Pentium 4s stuck together. They had 2 cores and 4 threads. (2x CPUs = 4 cores / 8 threads). These are slow and run extremely hot.
Later i7/Xeons (LGA 1366): These introduced the 4-core/8-thread design we use today, but they require a different motherboard and don't natively support Tiger.
Is it "Practical"?
If you use two 6-core processors (12 cores total), Tiger won't just ignore the extra 4; it will often refuse to boot or experience "kernel panics" because the ACPI tables report more CPUs than the 10.4 kernel's hardcoded limits can handle.
To achieve 8 logical cores on your board right now:
Step 1: Verify your board has two physical CPU sockets.
Step 2: Buy two Quad-Core Xeons (X5470 is the king, X5365 is the fallback).
Step 3: Tiger will see 8 CPUs. This is the absolute peak of "Ultimate Tiger" performance.
This setup gives you the maximum processing power Tiger can actually address, while your X5000 chipset handles the heavy lifting for your RAID 0 SSDs and expansion cards. It’s the closest thing to a "souped-up" 2007 Mac Pro that exists.
You said
cant tiger support 16 threads tho?
Gemini said
This is one of those legendary debates in the retro-computing world where "theoretical limit" meets "practical stability."
The short answer is: Yes, Tiger can technically support up to 32 logical threads, but for a Hackintosh build on an X5000-series board, it is extremely rare to see it stable beyond 8 physical cores.
Here is the deep dive into why 16 threads is a "high-risk" target for your project:
--- Quote ---1. The Kernel Limit
The xnu kernel in Mac OS X 10.4.x was designed when the most powerful Mac was the Quad-Core G5.
The 8-Thread "Comfort Zone": When Apple moved to Intel, the first Mac Pros topped out at 8 physical cores (2x Quad-Core Clovertown). Tiger 10.4.11 was optimized to run on this exact configuration.
The 16/24-Thread "Panic Zone": While the kernel can technically scale higher, booting Tiger with more than 8-12 threads often triggers a mp_cpus_call_wait() timeout panic. This happens because the legacy power management and CPU polling in Tiger weren't built for the massive parallelization of 6-core or Hyper-Threaded chips.
--- End quote ---
2. Physical vs. Logical (The 16-Thread Path)
If you are determined to hit 16 threads, you have two ways to do it, but both have massive trade-offs:
Method Configuration The "Tiger" Catch
Dual 6-Core CPUs 12 Cores / 12 Threads Tiger often panics during the boot handoff because it sees more than 8 physical cores.
Dual 4-Core + HT 8 Cores / 16 Threads Hyper-Threading (HT) did not exist for the 4-core Xeons compatible with the X5000 chipset (Harpertown/Clovertown).
3. Why the X5000 is the Bottleneck
To get a Xeon that is 4 cores / 8 threads (for a 16-thread total in a dual-socket board), you have to move to the Nehalem (5500 series) architecture.
Those CPUs will not fit in your X5000 board (LGA 771 vs LGA 1366).
Tiger does not have a native kernel for Nehalem. You would have to use a patched "Legacy Kernel", which breaks the "Authentic Tiger" experience you're after for your workstation.
My "Excellence" Recommendation
For your specific X5000 project, 8 Physical Cores (Dual X5470) is the true "Ultimate" spec.
The Reality Check: Even if you successfully patched Tiger to run 16 or 24 threads, the 2006-era software you are preserving (DAWs, utilities, Tiger-era plugins) cannot use them. Most apps from that era are hard-coded to look for 1, 2, or 4 cores. Having 16 threads actually increases "scheduling overhead," which can actually make your vintage software run slower or stutter.
The "Practical" Spec for your build:
CPUs: 2x Xeon X5470 (8 Cores total).
Threads: 8 (1:1 core-to-thread ratio).
Performance: This matches the fastest Mac Pro ever officially supported by Tiger, ensuring 100% stability for your audio and preservation work.
Are you planning to use a specific board like the Intel S5000XVN or a Tyan/Supermicro equivalent? Knowing the exact VRM revision would tell us if those X5470s are a go.
Navigation
[0] Message Index
[#] Next page
Go to full version