**The problem** When I use my laptop, it always heats up a lot in the center above the touch bar on top. I can feel it quite heated below as well under the top center. The CPU is fine (no processes going crazy). Fans are not really loud at all and I suspect they are working below the speed they should be. This was an issue when I bought it as well. **SMC reset** I did (multiple) SMC resets when I first bought, as this was an issue straight away. After the reset it worked fine for a few weeks and then I'd do another reset. A year and a half later thouhg, when I do an SMC reset, I don't notice the heat going away and it's still working the same way. P.S. Since I have been working from home, I often connect to an external monitor, no-surprise there that this causes heat. When I don't work with one, it's still warmer that it should be in my opinion. Any idea what may be the causing the issue and how can I fix it? My Macbook has the following specs: MacBook Pro (15-inch, 2018) Processor 2.6 GHz 6-Core Intel Core i7 Memory 32 GB 2400 MHz DDR4 Graphics Radeon Pro Vega 20 4 GB Intel UHD Graphics 630 1536 MB

I am trying to mod an old iMac 21" late 2009 with an Intel CPU and repurpose it as a monitor. I was hoping to find the PSU pinout, which is a 14 pin one. My further goal is to allow the button on the back to turn on the PSU. So far I have identified: 1. GND in pins 01, 08, 07, 14. 2. 3.7V in pin06. 3. 12V in pin04. This is on a turned off PSU, connected to AC. I have to mention here that the pin06 is not connected to the motherboard connector but to the jst4 that is connected to the LCD controller. Here with your help I have found a pin guide: - PSU/logic board pinout voltages Pin12 suggests that it is waiting for a signal from the logic board, possibly the 3.7V on Jst4. I tried connecting the 3.7V via a 1K resistor to pin 12 but nothing happened, voltages across the pinhead remained the same. The momentary switch has a very small resistance about 24ohm. Will I need some additional circuitry, like a transistor, to accomplish the turn on. Is there any other resource for finding how to mod this iMac and use its PSU?

I spilled a glass of water on my 2019 MacBook Pro. I immediately turned it off, then left it to drain for 48 hours. After turning it on, the display remained black, but first I saw the whole Touch Bar and heard a voice saying "user name." I force-restarted it: now I just see the "esc" button on the Touch Bar, nothing else. The caps lock LED is working. I tried with an external monitor without success. I also tried to restart it in safe mode or reset the PRAM/NVRAM, but without luck. Do you have any suggestions before I take it for repair?

I own since many years a Mac Pro early 2008. Few days ago it stopped working. It starts, fans spin, but no chime. Initially, I thought it was a RAM problem, but soon understood that the problem is "before" RAM is used. I already did the usual checks (battery removed, internal SYS_RST button, all the non-necessary boards removed etc.). I also took it apart, disconnecting and reconnecting all the connectors. No change. Diagnostic LEDs are all OFF, but when i press the DIAG button, I get LED 2 (STDBY) and LED 8 (PWRGD). Keeping the main key pressed, the Mac switches off normally. The SYS_RST button has no effect at all. Did anybody have a similar experience? Thanks

While running a CPU intensive task (solving a linear programming model), my 16-inch MacBook Pro suddenly restarted and then displayed this error:

panic(cpu 2 caller 0xfffffe003dfdd994): Sleep transition timed out after 35 seconds while creating hibernation file or while calling rootDomain's clients about upcoming rootDomain's state changes. Thread 0x107138.
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 24F74
Kernel version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041
Fileset Kernelcache UUID: 829162939C4BF76F77DA5D9A9458C889
Kernel UUID: AC87C755-49A7-3579-B1AA-F76DDC4D4304
Boot session UUID: AD7B4A9A-FA61-4F46-91AB-8BEB78691E9B
iBoot version: iBoot-11881.121.1
iBoot Stage 2 version: iBoot-11881.121.1
secure boot?: YES
roots installed: 0
Paniclog version: 14
Debug Header address: 0xfffffe001c055000
Debug Header entry count: 3
TXM load address: 0xfffffe002bfd4000
TXM UUID: B4BB7D20-BB31-3FBA-8FF5-48C2D9C3EDC7
Debug Header kernelcache load address: 0xfffffe003bfd4000
Debug Header kernelcache UUID: 82916293-9C4B-F76F-77DA-5D9A9458C889
SPTM load address: 0xfffffe001bfd4000
SPTM UUID: B836244C-CF63-3BC5-BCA2-51C7B978748F
KernelCache slide: 0x0000000034fd0000
KernelCache base:  0xfffffe003bfd4000
Kernel slide:      0x0000000034fd8000
Kernel text base:  0xfffffe003bfdc000
Kernel text exec slide: 0x0000000036738000
Kernel text exec base:  0xfffffe003d73c000
mach_absolute_time: 0x1d8405053be
Epoch Time:        sec       usec
  Boot    : 0x687213c9 0x00014f33
  Sleep   : 0x68737816 0x000c1bc6
  Wake    : 0x68737848 0x00039ea4
  Calendar: 0x68738368 0x0003b788

Zone info:
  Zone map: 0xfffffe101a000000 - 0xfffffe361a000000
  . VM    : 0xfffffe101a000000 - 0xfffffe15e6000000
  . RO    : 0xfffffe15e6000000 - 0xfffffe1880000000
  . GEN0  : 0xfffffe1880000000 - 0xfffffe1e4c000000
  . GEN1  : 0xfffffe1e4c000000 - 0xfffffe2418000000
  . GEN2  : 0xfffffe2418000000 - 0xfffffe29e4000000
  . GEN3  : 0xfffffe29e4000000 - 0xfffffe2fb0000000
  . DATA  : 0xfffffe2fb0000000 - 0xfffffe361a000000
  Metadata: 0xfffffea2d6010000 - 0xfffffea2df810000
  Bitmaps : 0xfffffea2df810000 - 0xfffffea2ef810000
  Extra   : 0 - 0

CORE 0 recently retired instr at 0x0000000000000000
CORE 1 recently retired instr at 0x0000000000000000
CORE 2 recently retired instr at 0x0000000000000000
CORE 3 recently retired instr at 0x0000000000000000
CORE 4 recently retired instr at 0x0000000000000000
CORE 5 recently retired instr at 0x0000000000000000
CORE 6 recently retired instr at 0x0000000000000000
CORE 7 recently retired instr at 0x0000000000000000
CORE 8 recently retired instr at 0x0000000000000000
CORE 9 recently retired instr at 0x0000000000000000
CORE 10 recently retired instr at 0x0000000000000000
CORE 11 recently retired instr at 0x0000000000000000
CORE 12 recently retired instr at 0x0000000000000000
CORE 13 recently retired instr at 0x0000000000000000
CORE 14 recently retired instr at 0x0000000000000000
CORE 15 recently retired instr at 0x0000000000000000
TPIDRx_ELy = {1: 0xfffffe1883569760  0: 0x0000000000000002  0ro: 0x0000000000000000 }
CORE 0: PC=0xfffffe003d8fae30, LR=0xfffffe003d8fae2c, FP=0xfffffe7ed2a2fe40
CORE 1: PC=0xfffffe003d8fae30, LR=0xfffffe003d8fae2c, FP=0xfffffe7ed0d57e40
CORE 2 is the one that panicked. Check the full backtrace for details.
CORE 3: PC=0xfffffe003d8fae30, LR=0xfffffe003d8fae2c, FP=0xfffffe7ed202fe40
CORE 4: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84e128, FP=0xfffffe7ed2b074f0
CORE 5: PC=0xfffffe003d7cbb18, LR=0xfffffe003d7cbb18, FP=0xfffffe7ed272bed0
CORE 6: PC=0xfffffe003d7cbb18, LR=0xfffffe003d7cbb18, FP=0xfffffe7ed187fed0
CORE 7: PC=0xfffffe003d7cbb18, LR=0xfffffe003d7cbb18, FP=0xfffffe7ed0a6fed0
CORE 8: PC=0xfffffe003d7cbb18, LR=0xfffffe003d7cbb18, FP=0xfffffe7ed18dfed0
CORE 9: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84e128, FP=0xfffffe7ed15d34f0
CORE 10: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84fd70, FP=0xfffffe7ed2c3b720
CORE 11: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84e128, FP=0xfffffe7ed08534f0
CORE 12: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84fd70, FP=0xfffffe7ed03d3720
CORE 13: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84e128, FP=0xfffffe7ed22db4f0
CORE 14: PC=0xfffffe003d7a71b4, LR=0xfffffe003d84e128, FP=0xfffffe7ed053b4f0
CORE 15: PC=0xfffffe003d7a71b4, LR=0xfffffe003d850240, FP=0xfffffe7ed0cdf6c0
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xfffffe2317fedc90: 0 pages, 774 threads: pid 0: kernel_task
Panicked thread: 0xfffffe1883569760, backtrace: 0xfffffe7ed2c2f490, tid: 1034867
		  lr: 0xfffffe003d78e470  fp: 0xfffffe7ed2c2f520
		  lr: 0xfffffe003d8f6ffc  fp: 0xfffffe7ed2c2f590
		  lr: 0xfffffe003d8f5218  fp: 0xfffffe7ed2c2f650
		  lr: 0xfffffe003d741d28  fp: 0xfffffe7ed2c2f660
		  lr: 0xfffffe003d78dd64  fp: 0xfffffe7ed2c2fa70
		  lr: 0xfffffe003e032760  fp: 0xfffffe7ed2c2fa90
		  lr: 0xfffffe003dfdd994  fp: 0xfffffe7ed2c2fdc0
		  lr: 0xfffffe003df056b0  fp: 0xfffffe7ed2c2fdf0
		  lr: 0xfffffe003d7f5460  fp: 0xfffffe7ed2c2fe30
		  lr: 0xfffffe003d7f6490  fp: 0xfffffe7ed2c2ff20
		  lr: 0xfffffe003d742768  fp: 0x0000000000000000

last started kext at 918848103901: com.apple.driver.usb.IOUSBHostHIDDevice	1.2 (addr 0xfffffe003ca778d0, size 6811)
loaded kexts:
**OMISSIS**


** Stackshot Succeeded ** Bytes Traced 614982 (Uncompressed 1505520) **

I am not expert enough to understand the real cause of the malfunction, yet I am a bit worried as it happened when the computer was quite hot and the fans were not running. Could you translate the error above into a more easily understandable description? Is this fault due to the hardware, the software or a mix of both? Here is the [detailed report (2.3MB)](https://drive.google.com/file/d/11GFpiJck-c_pLuptsFZ5y6gCWo5BQAY1/view?usp=sharing) from /Library/Logs/DiagnosticReports/. After the malfunction I run Apple Diagnostic as explained here but no issue was found (other than the power cable being detached when the diagnostic was run). System details: - Apple MacBook Pro M4 Max - 128 GB - 2TB SSD - macOS Sequoia 15.5

Pretty sure the answer is no; wanted to check for sure. I have a 2022 MacBook Pro with water damage. Only boots into recovery mode. I have AppleCare. Genius Bar said for $300 I can send it off in the mail and they’ll repair it. I don’t have $300 right now. The computer probably has a good turn-in value (if perfect condition). Do I have to pay $300, get it repaired, then try to turn it in (if I wanted the cash), or is it possible Apple can deduct the price I would have paid for the repair, and I can turn it in as is, for its post-AppleCare turn-in value, because they know I have AppleCare?

There are whole industries founded on the use of Intel Intrinsics for CPU parallelisation (with SIMD). For example, the community of Lattice QCD physicists depend on that for boost in the efficiency of lattice simulations. Intel-based macs can be and are routinely used by such professionals to do their job. However, there are rumours about Apple replacing Intel CPU with ARM cpus in future Macs. Will these professionals have to replace Macs with other Intel-based computers, or are there alternatives to Intel Intrinsics for C that are supported on ARM-based CPUs?

I have a 16 inch MacBook Pro. The webcam on it was working fine before the update. But since the update, when I open FaceTime, it shows I guess what is the first frame, and that's it - there's no video feed from the webcam, just a dark, static image of the first frame: Has anyone else faced this issue? And how do I fix it? I tried restarting the system a couple of times, but that didn't fix the issue.

# Brief Summary 2019 MBP 16" 2.3Ghz i9 shows severe thermal throttling * CPU Frequency hovers around 1.9-2.0 Ghz * Power draw doesn't exceed 30W * Max Temperature only 76ish degrees Celcius * Exporting a 5min clip on Adobe Premiere Pro which slams all 8 cores I've attached screenshots below showing just how much the new MBP 16" i9 throttles. I haven't really had a problem with it until recently... but there are 2 variables: ## What's Changed? * Catalina upgrade to 10.15.5 recently * Applecare service replaced the logic board ## Questions * Is it likely that the replacement logic board is not up to snuff? * I haven't heard any complaints online (reddit, stack exchange, apple support) of thermal throttling lately. How does one test abnormal throttling? ## Screenshots * terminal output after running

-g thermlog

* intel power gadget showing the aforementioned stats holding steady despite high CPU Utilization.

Two months ago I was given away a Mac Pro 1,1 (A1186), in perfect working condition. Some days later, I had the bright idea of testing a working PCI express video card I removed from a PC on my Mac, but it didn’t turn on. So I removed the video card, reinstalled the old one, and again, it didn’t turn on. I removed the 3V battery to reset the PRAM, replaced it with a new one, performed a SMC reset, and tried everything I read on the forums, with no luck. I checked the logic board status LED’s and I noticed they all remained off. Suspecting the culprit was the PSU, I ordered a second-hand PSU on eBay (Delta DPS-980AB A), I installed it yesterday but my Mac still doesn’t turn on. No status lights, no clicking sound, no spinning fans. I checked all the connectors again. I tested it by unplugging connector # 4 and shorting ‘PS_ON’ plug and ground together with a paper clip. The PSU switches on, all the fans start spinning, all the led’s on the RAM raiser light up, but the logic board LED’s don’t light up, the switch-on button doesn’t respond and as soon as I remove the paper clip, the PSU switches off. Conclusion: the “new” PSU works fine, so does the old PSU (I tested the voltages on both of them), and my logic board is toasted, I’m afraid. Is there any “miraculous” procedure to revive my Mac, or do I have to buy a second-hand logic board?

I have a Macbook Pro 2019. I recently purchase the Corsair K68 RGB keyboard which has a common USB Type-A connector. I used OTG for USB A to USB C. The first time mac detects the new device. Worked great.
When I disconnected and reconnected the keyboard it only detects keys from A-Z. Not even spacebar or num keys. Tried going to keyboard settings >> Change Keyboard Type. It does not detect my keyboard. It only starts to work again when I restarted my mac. Now every time if my keyboard unplugged accidentally, I have to restart my mac. Is there any other way to do it without restarting macbook again and again everytime?

After a recent repair my MacBook Air M2 was working good as new. I used it 5 hours and shut it down. The next day after start up the keyboard was unresponsive. Touch pad was okay but no key worked. A restart and a power button restart did not help. I read about the SMC reset for older Macs not knowing the M2 does not have System Management Control. I pressed Shift + Control + Option + Power Button. The M2 started and the keyboard was still dead. I pushed the same key combination with power on. The M2 restarted **and the keyboard functioned again.** I understand those key presses are for DFU mode. I had no second Mac connected to the M2 with dead keys so no DFU action was taken. The M2 had gone bad after a glass of wine was spilled upon it. A local non-Apple authorized fix it shop replaced two capacitors and cleaned the circuit board and keyboard with isopropyl. I'm typing right now on the M2 that was broken, fixed, then lost its keyboard, then got its keyboard back by the key presses mentioned above. *Does anyone have an idea of what happened here? How could pressing DFU mode keys with no second Mac connected revive a dead keyboard?* I have bought an M4 since the keyboard quit on the M2 after the repair. I am thinking something else may also go bad on it at any time, but maybe not. It would be nice to have the $900 back for the M4 if this repaired M2 is good to go. Is there a keypress that will test the Mac M2 system for functionality and tell me if this repaired computer has an unseen issue?

I've had this MacBook Pro (16-inch, 2019) for a while now, but today it glitched out with huge green fields in all apps. After a reboot I see this checkered black/green glitch pattern in Google Chrome on some sites, in some "sizes". Basically if I resize the browser window the glitch goes away, but if I resize it too much it comes back. Happens both on the internal and on external display. I am hoping this is a software glitch, but I am afraid it's my graphics card. Would be very grateful if someone knows the answer. Here's the stackoverflow logo with the glitch:

I have an M1 Mac Mini running Sonoma 14.3. I would like to be able to put it to sleep or shut it down when not in use to conserve energy. But, I also want to be able to remotely power it up so I can access it when I need to using VNC, SMB, or SSH. I have typically done this by sending WOL (WakeOnLan) magic packets from my home router which is pfSense. This has always worked fine—until this Mini. I've checked the Energy Saver prefs, made sure womp=1 in pmset -g and even tried mucking around with nvram / darkwake settings. I'm sure the Ethernet MAC address is correct. Nothing has worked. WOL to an Intel NUC sitting on the same network works as expected. What happens when I send the WOL packet is one of: - absolutely nothing: no lights, no activity, screen remains dark. - power LED comes on, Mac becomes "pingable", screen stays dark, but after 5-10 seconds, the Mac goes back to sleep. At no point during this sequence am I able to connect via VNC. Is this a hardware bug with the M1's? Anyone know of a solution?

I own a mid-2009 MBP with OS X Mavericks installed. I'm a hi-tech enthusiast who wants to use the fingerprint scanning feature made available by many scanners on the market to login into my account after boot and unlock the screen after the screensaver has started. The scanner I'm willing to buy is a DigitalPersona U.are.U-5160 which is not only FIPS 201 PIV certified, but it's also designed to work in harsh environments and situations. See: http://www.fulcrumbiometrics.com/Digital-Persona-U-are-U-5160-p/101106.htm Please note that **I've already read *this article*** on StackExchange (https://apple.stackexchange.com/questions/65282/how-can-i-enable-fingerprint-authentication-on-a-mac-what-compatible-scanners-a) which talks about the same, **but** I've found nothing interesting in it. In particularly, supposed that I've gotten all the Smart Card Services/CAC Libraries: 1. How do I switch from password login to fingerprint login? 2. Can I use fingerprint login with FileVault 2 too? (i.e. decrypting the HD using my fingerprint, *with no passwords to type*) I think these features require dedicated API's or SDK's, and Apple stopped deploying them since it bought AuthenTec. Now, all fingerprint-scanning feature are officially unsupported by Apple except for the iPhone 5S. I've read somewhere that LastPass does a very similar job indeed, and is used for the purposes I've listed. How can I achieve this?

Got a 2023 Mac Pro (M2 Ultra) earlier this year, which forced me to upgrade my OS from Monterey to Ventura (and now Sonoma). It started as soon as I got the 2023 Mac Pro and migrated all my stuff from my previous Mac, which was still running Monterey. The Mac Pro purchase effectively forced me to upgrade to Ventura, since the 2023 Mac Pro cannot run Monterey. Upgrading to Sonoma (at Apple's request) has only made the problem worse Ever since then, have been experiencing a recurring problem that starts happening after several hours of uptime. There is a whole cluster of symptoms, but the most obvious and common ones are the following: 1. It becomes impossible to edit pictures (HEIC, PNG, JPEG) in Preview. For example, I open a full size HEIC pic from my iPhone and I go to resize it down to 1000 pixels wide. Sometimes I get visual artefacts while the Resize dialog is open (note the grey boxes here): And then when I press OK either I get a blank (instead of a small picture): Or the picture is resized, but then it is impossible to save it. I get an error that says “The document could not be autosaved”: And even if I try to revert the change, I get "The operation could not be completed”: This does not just affect Preview. In this state, I find that when I open pictures in a third-party image editor like Pixelmator Pro or Affinity Photo 2, the app displays a blank (empty artboard) right away instead of the actual picture, even before I try to resize it. Crucially, in Affinity Photo 2, there is a setting to disable Hardware Acceleration (under Performance). If I disable it, quit and relaunch the app and then try to open a picture file, it works fine. Hence my suspicion that this is a bug involving hardware acceleration. 2. Another very common symptom in macOS when the cluster of symptoms starts happening is that, in various apps, buttons in dialog boxes become invisible which makes them impossible to read. This happens, for example, in the Notifications dialog box in the Podcasts app: This affects regular buttons and also checkboxes, which disappear altogether when they are checked and reappear when they are unchecked. If I leave the dialog box open and switch to something else, the buttons reappear in their background form. They disappear again when I bring the dialog back to the foreground. 3. There are many, many other symptoms that start occurring at the same time, once the Mac is in this state. For example, screen recording stops working altogether. The Maps application also starts acting up. Zooming in and out no longer works, things start flickering like crazy, or going completely black. I have, much more rarely, also seen video corruption in Firefox or Google Chrome, which can be alleviated by turning hardware acceleration off in these apps and relaunching them. Otherwise, quitting and relaunch the affected app does not help at all. However, I have found that: - Quitting a “big” app like Safari temporarily alleviates some of the symptoms. But when I relaunch Safari the problem starts happening again. - If I **quit all running apps**, the problem disappears for a longer while. But when I relaunch things, the problem comes back after a while. - If I reboot the Mac completely, then I am OK for a few hours, and then eventually the problems start reoccurring. *** I have been in contact with AppleCare and have had to try all kinds of things. None of the things they have made me do have helped so far: - I did a 100% clean install of macOS on a new volume. I need about 20 third-party apps just to be able to function for my work. But I did only reinstall the essential ones, and even that was enough to cause the problem to start happening again (within less than 48 hours). - And, because of the Affinity Photo 2 scenario, and also the rarer video corruption in Google Chrome and Firefox, which are the only apps I know where hardware acceleration can be turned off, usually with dramatic improvement, it seems that it is a bug that involves hardware acceleration. - I have run the hardware diagnostic on the Mac Pro and there are no reported issues. That said, if it is not a hardware defect, I have yet to come across a single report of any other Mac user experiencing the same thing. I had been running the same software on a 2020 Mac Pro for years before this new purchase without any such problem. Like I said, Apple has been unhelpful so far. Their requirement to completely eliminate third-party software and try to reproduce the problem is quite unrealistic. I usually (successfully) help other Mac users fix their problems. But I am at a loss here. Is there really no hope? So I am now turning to this community of experienced Mac users. Maybe someone has some ideas.

Recently I bought a brand new iPhone XR. When its screen is activated by some application (not necessarily a GSM call or a Wi-Fi thing), it affects other speakers or headphones around it. All of them sounds exact same 4 "buff" like sounds consecutively. It reminds me of the way old mobile phones affected the speakers around them. Is there anyone knows why it happens and how to prevent it? It annoys me and I really need a solution.

I've only began experiencing this issue this morning, I first noticed it at around 4 AM. Its 1 PM now. What I've done so far: - Reset PRAM & SMC - Switched Left & Right Speakers. The right speaker was consistently the one that popped, which makes me wonder why both the macbook speaker and logitech speaker had the crackling. - Updated Audio MIDI setup - Changed the output device (used built in speakers before, & Logitech X-140 2 Piece Speaker Set now). Both had popping. - Switched format to 2 ch 32 bit Float 44.1 kHz Usually it'll be 1-2 consecutive pops every 10 minutes or so. It's loud and high pitched - it's about the same pitch as white noise. It doesn't seem to be related with volume. It doesn't crackle when the volume gets louder, and the crackling isn't at all synced with any peaks of the sound (in which there are barely any, the sound quality otherwise is good). In fact, most of the crackling happens when the volume is quiet, and even when nothing is playing. I haven't dropped or damaged the MacBook in any way. What can I do to fix this, and if Apple Repair is necessary, how much would it cost? Also, is it still a hardware issue when both the built in speaker and plugged in speaker experienced the same popping?

I just switched from a Windows PC to a Mac Mini M4. When I open a few apps, I notice the GPU temperature gets to around 80-90 degrees Celsius (seems to me pretty high). I saw people recommend using a fan control app (used to do it from the BIOS in Windows), but I'm not sure how it works in a Mac, so kind of scared to ruin something. For example, I don't see in the Mac's Fan Control app an option to define a curve, just a single temperature. Also, how does it affect the fans? If there is some recommended setting, I would love to hear =)

I am reconfiguring a working Apple Xserve (Early 2009) [Xserve3,1][model A1279][MB449LL/A] which does not currently have an SSD installed, neither the factory 128GB SATA, nor any aftermarket. I'm planning to replace the standard 3-drive SATA *Drive Interconnect Backplane* with the Apple *Xserve RAID Card*. The fans howl something fierce, so I plan to replace the *Fan Array*. I also plan to replace the single processor *Logic Board* with the dual processor *Logic Board*. It seems to me that performance would be better, and overhead lower if I install a current generation PCIe SSD in the *PCI-E Riser Card* (ie, PCIe “backplane”), rather than install an Apple circa-2009 SATA SSD (which connects through the Front Panel Board). Has anyone successfully installed a PCIe SSD in an Xserve *PCI-E Riser Card*?