I'm trying to connect my Mac Pro tower (2020) to my network using ethernet but am experiencing problems if use my Netgear GS105 switch, this setup results in the MacPro saying "Cable connected but self-assigned IP". I've renewed DHCP leases, changed all sorts of settings including on my router but nothing works, I have also validated that this setup does work fine with every other computer (including a MacPro Trashcan) and if I connect the MacPro Cheese-grater directly to the router it works so to recap: This does *not* work: [Router]----[Switch]----[MacPro2020] This does work: [Router]----[Switch]----[MacPro Trashcan] These also work: [Router]----[MacPro2020] [Router]----[MacPro2020] I've also tried different cables in place of both and and it doesn't improve the situation, every possible combo works except if I have the MacPro 2020 Tower plugged in via the Netgear switch. Is there some issue with unmanaged switches and MacPro 2020 Towers?

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

I want to run Windows 10 on my flashed 2009 Mac Pro 5, 1 with Bootcamp. Currently OS X 10.11.6 and the Nvidia GT 120 are present. I am able to start the process to create the bootable USB drive but every time the progress bar stops midway and says that there is not enough space on my USB drive. The USB is 123GB and completely cleared. The Windows 10 ISO is around 6GB. I have also tried reformatting it to FAT32 and exFAT, with no luck. I have also disabled Time Machine and automatic backups. Does anyone know a fix to this or should I just install Windows 10 via DVD?

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 couple of older (High-Sierra) Apple products that I use for some non-essential tasks, for some reason after some kind of update the audio stopped working on both of them. After pulling my hair out for the past week trying to solve the issue I finally figured it out and wanted to post here with the solution in case anyone else runs into the same problem: **The Problem** - Computer updates and restarts (not sure what exactly is being updated...) - After restart no sound devices are working and the Sound section of System Preferences is inaccessible. **Everything I Tried (That Failed)** - Restarting/Shut-Down - Disk First-Aid - Booted to Safe Mode - PRAM and SMC reset - Terminal commands to restart coreaudiod - Reinstall of OS (Command-R on boot)

I have a few "cheese graters" rack mounted and I cannot seem to locate the exterior serial number. I see the older ones have it near the add-on cards but these Intel rack mounted ones have nothing printed on the rear. Did Apple print this identification anywhere on the outside of the case?

Mac pro 2009 4,1 Boots up but no video output (black screen). It was working fine on the old OS that was on it(not sure which OS). I want to update to the highest OS (el capitan) it can run. So I did. But after that I get an black screen. I tried to reset some things like time code, vram etc. Nothing works. Can't even go to the BIOS to reset everything (or I've got the wrong key combination). I have also added two other hdds. And on one of them was an Windows installation. So I hold the option key on startup to choose an other hdd and choose the Windows one. And that was just working fine. What can I do to run Mac OS again? Also tried an Bootable USB with el Capitan but It won't recon the USB flash drive I've made on my 2019 Macbook pro. When I use Option + Command + P + R And waited till the second time hearing the startup sound it looks like it's working fine. But still no output. I see the Apple logo in the beginning but after that no output. De Mac pro itselfs keeps running with no errors or blinking lights. Gpu is an ATI Radeon HD 4870 512MB Mac Pro Graphics Card 6gb ddr3 ram And de standard Xeon 2,66 MHz cpu Ive downloaded El Capitan, (it's in the downloads folder, DMG FILE). Then I go to the terminal and I fill in: sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/THENAMEOFMYFLASHDRIVE --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app Fill in my password next, and than it says: ' sudo: /Applications/Install OS X El Capitan.app/Contents/Resources/createinstallmedia: command not found. Catalina can't put it in de application folder for some wierd reason...

I have an early 2008 Mac Pro which will only run up to El Capitan (10.11). Is there any hardware upgrade I can do to run later versions (10.13 and later)?

I have a Mac Pro 3,1 with an ATI Radeon RX580 8GB graphics card, a dosDude Catalina (10.15.6) install on an internal SSD and and a Windows 10 Pro (latest Version and updates) install on an internal HD. Both macOS and the Windows work fine along with all parts of the Mac. As I a have the Radeon card I do not have a boot screen until either Catalina has mostly started up or Windows has started to boot, so I cannot change the booting by holding down the Option key. I previously ran El Capitan instead of Catalina, and with that I had installed in Windows the Boot Camp 4 drivers, which allowed me to select macOS from the Boot Camp Assistant and reboot from Windows into El Capitan. From El Capitan I could select the Windows drive in the start up disc control panel and reboot into Windows. However, since upgrading to Catalina, I can still select the Windows drive in the start up disc control panel and reboot into Windows. However if I select macOS from the Boot Camp Assistant and reboot the Mac, it always reboots into Windows. My current work around is to shut down, remove the Windows drive, reboot in to Catalina, select Catalina in the Startup Disk control panel, reboot into Catalina, shut down, re-install the windows drive, start up and it starts up into Catalina again with the Windows disk mounted. I can then just select the Windows drive in the start up disc control panel and reboot into Windows when I need to. From what I have read it's an issue with boot camp not liking the APFS file system Catalina uses. I have also read that a newer version of Boot Camp would fix the issue. I have upgraded Boot Camp to version 6, but this cause other issues in Windows and in the end I had to format the windows drive and re-install it from scratch along with the Boot Camp 4 drivers. Can anybody tell me how I can get this issue sorted out so I can just switch using Boot Camp? Many thanks Duncan

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.

Let's say I have 2 MacPros: - MacPro at work - MacPro at home I am currently able to do the standard screen sharing using my work MacPro from home, and can also normally access its folders etc. My question relates to ensuring privacy of the work content in case someone walks by while I'm using that remote computer. Unplugging the work computer's monitors would not be a fully working solution, as it would only partially resolve this issue. I wonder if there is any way I could access my MacPro at work from home using the screen sharing method, **without** anything being visible on the monitors of said MacPro at work?

I have a 2009 Mac Pro that I'd like to add a hardware RAID card to. I am running VMware ESXi with various OSes running as VMs. The Apple RAID card is not what I'm looking for. I would also like to utilize the 4 hard drive bays and get 6G speeds. I have run into a few potential solutions, but have not been impressed. Anyone found a good solution?

Booting a Linux distribution generates the following: > error: no sultable video mode found. > Booting in blind mode Configuration: - Mac Pro 1,1 Late 2006 - Apple ATI Radeon HD 5870 - DVD drive works - 6 GB RAM Booting from USB Mint: Linux Mint 22 Xfce 64 bit The GRUB script is the default:

setparams 'Start Linux Mint 22 Xfce 64-bit'

    set gfxpayload-keep
    linux        /casper/vmlinuz boot=casper username=mint hostname=mi\  
nt iso-scan/filename=${iso_path} quit splash  
    initrd        /casper/initrd.lz

I have seen suggestions to change splash to nosplash and add debug nomodeset Also consulted Matt Gadient's excellent website. I have tried various other distributions and versions: Ubuntu, Arch and most of those do not show an EFI from the Mac boot device selection. Nothing seems to work although many people have reported success with this configuration. Can anyone suggest a fix?

Can't Option Boot Mac Pro or boot into Safe Mode. I get a black screen, no cursor. - Mac Pro (Early 2008) - El Capitan OS X 10.11.6 - 28 GB RAM - 369.06 GB of space on Hard Drive Using Apple Aluminium keyboard and wired Apple mouse. Tried Disk Utility, Disk Warrior, resetting PRAM. Any ideas on what to do next? Thanks.

*cross-posted MacRumors forum* I am running a MacPro 5,1 which can triple boot MacOS Sonoma, Ventura and Ubuntu/Linux from separate SSDs. In the past two days I could not boot Linux 6.8.0. MacOS and Linux 6.50 boot fine. I use OpenCore Legacy patcher (OCLP) on the MP 5,1 to select the required boot drive (each OS on separate SSD). I do the following to attempt to boot Linux Select the Linux boot drive from OCLP menu. When screen clears press ESC once. The Grub 2.06 menu appears Select Advanced options Two Linux kernels, and recover mode, appear for selection on GRUB2 menu 1) If I select linux 6.8.0-40-generic and press ESC to display boot message the boot gets to various points then hangs. A regular sequence of messages includes: Mounting bootefi, … Finished load kernel module efi-pstore. At this point the boot does not proceed , the machine hangs for about 30 seconds then the screen goes blank. The fans ramp up speed for 2 seconds then stop and the machine just displays a blank screen. I have to press the power button for about 5 seconds to switch off the machine. 2) If I select linux 6.5.0-45-generic the machine boots fully, I can sign on and all attached screens display. 3) If I select linux 6.8.0-40-generic (recovery mode) the machine boots fully, I can sign on and one attached screen displays – the other screens are blank. Any suggestions on how I diagnose and fix the 6.8.0-40 boot problem? I can work perfectly fine with 6.5.0 but the boot process is inconvenient. Thanks

I am wondering if the NVidia Mellanox 100G network cards can be used in the 2023 Mac Pro. In an older thread on the Nvidia forums titled "100g connectX 5 slow speed between Mac to Proxmox TrueNAS VM" the answer was "At this moment NVIDIA ConnectX Adapters are not supported on the Mac OS platform ". On the Sonnet Desktop website the NVidia Mellanox 10G and 25G cards are mentioned as being supported. Can anyone confirm or report on compatibility? A thread in the Macrumors forums suggest that ATTO cards work .

I have a Mac Pro 2013 which I bought in 2018. I’ve read they are upgradeable (macsales.com has a video on how to do it). I bought a 12 core chip to replace the 6 core chip it came with. I tore the whole thing down and got to the heat sink retainer clip. Every video or website I’ve read (iFixIt has a text version, and there are several videos on YouTube including the OWC video) shows a total of 8 screws. Four outer screws, which I think are T8. And four inner screws. The four inner screws are not screws on my unit. They’re just round nubs. I’ve applied a little bit of pressure attempting to pry them loose but they won’t budge. I don’t want to get too rough with it because I don’t want to damage the board or the original CPU given it seems like Apple changed this to be not-upgradeable. What I’m a missing here? Was such a change made? Is it safe to pry until they pop off, or are they rivets and not designed to be removable? ![Photo of heat sink retainer clip showing the four inner fittings ][1]

I'm looking to update from the stock graphics card in my my Mac Pro 3,1 (2008). The logic board only has two 6-pin ATX connectors, and the card I'm looking at (a GeForce GTX 760) requires one 6-pin and one 8-pin ATX connector. From my research the power supply should be able to handle it, as I don't have any other PCI devices. There are 6-pin to 8-pin ATX adapters available, but I'm not sure the tracks on the logic board would be rated for the higher power, and may burn out. I do, however have a spare molex 4-pin power connector for an IDE disk drive. What is the rated power for one of these type connectors, and is there any way to use that, or a combination of that and the other 6-pin ATX connector to provide enough power to the card? Thanks!

I have a Mac Pro 5,1 running macOS Monterey via Open Core Legacy Patcher (OCLP) and I just purchased a flashed RX 6600 video card from MacVidCards.eu . According to the specs on the MacVidCards website, the card is capable of 8k @ 60Hz. The card I purchased appears to be a flashed XFX Speedster SWFT 210 AMD Radeon™ RX 6600 with the following ports: > ‍DisplayPort: 1.4 with DSC > HDMI™: 2.1 VRR and FRL The manufacturer website does not include maximum resolution in the specs, but the same card by Sapphire does: > HDMI™: 7680×4320 > DisplayPort1.4: 7680×4320 So I have no reason to believe this card should be incapable of achieving 6k @ 60Hz. My monitor is a Dell UltraSharp 32" 6K HDR Video Conferencing Monitor . It is capable of 6K 6144 x 3456 at 60 Hz. In addition to Thunderbolt 4, it has the following video inputs: > HDMI 2.1 > Mini DisplayPort 2.1 I have purchased 3 different video cables: - 8k mDP 1.4 cable: https://www.amazon.com/dp/B0CL6GH63X - 16k mDP 2.1 cable: https://www.amazon.com/dp/B0CHVSPNCZ - 8k HDMI 2.1 cable: https://www.amazon.com/dp/B09CHH8TRC Using either of the 2 mDP cables connected to my PC with an RX 2080ti, the monitor reports a resolution of 6k @ 60Hz, 24-bit: Using the HDMI cable on the PC with the 2080ti, I get 4k @ 60Hz, 24-bit: Now, using the same DP cables connected to the RX 6600 in the Mac, the monitor will only sync to 5k @ 60Hz, 24-bit: Finally, using the same HDMI cable connected to the RX 6600 in the Mac, the monitor will only sync to 5k @ 60Hz, 30-bit: While connected to HDMI, running the following command on Terminal results in the following output: system_profiler SPDisplaysDataType |grep Resolution > 2024-03-31 12:30:55.464 system_profiler[43589:961215] Device PreExisted [000000010000076f] AMD Radeon RX 6600 > Resolution: 5120 x 2880 (5K/UHD+ - Ultra High Definition Plus) Since posting this question, I also found something interesting. While using HDMI, I can increase the resolution (scale up??) to what "looks like" 3008 x 1692 (have been running 5k with what "looks like" 2560 x 1440). Running the system_profiler command again, here's what I found: > 2024-03-31 12:37:46.658 system_profiler[43745:966153] Device PreExisted [000000010000076f] AMD Radeon RX 6600 > Resolution: 6016 x 3384 The screen still looks clear, and here's what System Profiler shows: But, the monitor is still only connected/synced to the computer at 5k: I can increase the resolution all the way up to 7680 x 4320 (8k) and the image is clear, but the monitor is still connect/synced at 5k and the System Profiler shows: > 2024-03-31 12:46:57.626 system_profiler[43945:973094] Device PreExisted [000000010000076f] AMD Radeon RX 6600 > Resolution: 7680 x 4320 (4320p/8K UHD 2 - 8K Ultra High Definition) System Profiler shows: It's worth noting that my M2 MacBook Pro connected via Thunderbolt connects to the monitor at 6K @ 60Hz, 30-bit and the available resolutions in Sonoma are different that what I'm getting on the Mac Pro. For example, on the MacBook Pro, I can set the resolution all the way up to 6144 x 3456, or I can set it to half this, 3072 x 1728. Neither of these options are available on the Mac Pro in Monterey. It's hard to say for sure, but the Macbook Pro appears to be just a tad sharper. So am I truly achieving 8K (surpassing 6k even), or am I running at 5K and just scaling?

Mac OS Monterey running on Mac Pro 5,1 patched with Open Core Legacy Patcher I have observe the following odd behaviour. * Attach a microsoft mouse to one of the back USB ports. Works. * Detach and plug in on front port. Mouse LED flashes once, and mouse does not connect. * Detach and plug in on back port again. LED flashes. No connect. * Reboot mac, with mouse attached with either port. Works. * Attach a hub to the mac, using one of the ports that the mouse doesn't work on. Attach mouse to hup. Works. I have seen this behaviour with USB keyboards too. *** I have another mac running Big Sur. Unplugging and repluging in USB devices works as expected there.