- #MAC MINI MID 2010 HIGH SIERRA FULL#
- #MAC MINI MID 2010 HIGH SIERRA PRO#
- #MAC MINI MID 2010 HIGH SIERRA SOFTWARE#
- #MAC MINI MID 2010 HIGH SIERRA MAC#
- #MAC MINI MID 2010 HIGH SIERRA WINDOWS#
#MAC MINI MID 2010 HIGH SIERRA MAC#
Apps and features will be easier to navigate, especially in Photos, and Siri is getting an overhaul designed to let it understand users better as well as speaking less robotically. iMac: Late 2009 or later MacBook: Late 2009 or later MacBook Pro: Mid 2010 or later MacBook Air: Late 2010 or later Mac Mini: Mid 2010 or later Mac Pro. The updated operating system will also bring a new version of the Metal API (designed to make games run faster), a new sidebar and editing tools in the Photos app, and will allow developers to create interactive virtual reality experiences on Macs. Mac OS High Sierra will deliver a number of new features to Mac computers, including a new Apple File System (it replaces the old one, called HFS Plus), which will streamline chores like duplicating files and finding specific ones.
#MAC MINI MID 2010 HIGH SIERRA PRO#
To run it, you’ll need a MacBook or iMac computer released in late 2009 or newer, a MacBook Pro, Mac Mini or Mac Pro released mid-2010 or newer, a MacBook Air released in late 2010 or newer, or an iMac Pro released in 2017. Now, the system does not look for the faulty FireWire port/driver anymore and it boots into High Sierra without problems.MacOS High Sierra will work with these computersĪpple’s new macOS High Sierra operating system has the same requirements as macOS Sierra: it’s compatible with Apple computers introduced in either late 2009, mid-2010 or later. Deleting the kext file using rm -rf /System/Library/Extensions/IOFireWireFamily.kext ( ).Give writing privileges to the user by running mount -rw / ( ).Enter in Single User mode ( Command+ S).Allegedly, this could be achieved using several methods, such as chmod 000 the kext, moving it, unloading it or deleting it. Now, I need to deny the kernel access to the IOFireWireFamily kext, in order to disable the FireWire support. From here, I just ran csrutil disable command to disable the SIP. Since I cannot boot into Recovery mode, I used Single User Recovery mode, by holding Command+ R+ S (as suggested in ). Therefore, based on a combination of other answers to similar questions, I did the following:įirst, I must disable SIP, so I can use the Single User mode with writing privileges. Since I do not really need FireWire, I figured I could disable it. The verbose boot lead me to believe that the problem had something to do with the FireWire port/driver. If it helps, I can also successfully boot into Single User mode, where I have access to a sh terminal.
#MAC MINI MID 2010 HIGH SIERRA SOFTWARE#
The FireWire timeout and the exceeded memory limit related to software updates. So, by my understanding there are two main issues here, possibly. IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 IOConsoleUsers: time(0) 0->0, lin 0, llk 1, Hfs: unmount initiated on Recovery HD on device disk1s3īusy timeout, (60s): ´IOFireWireLocalNode´ Hfs: mounted Recovery HD on device disk1s3 I booted using verbose mode and the boot seems to hang at this point: busy timeout, (60s): ´IOFireWireLocalNode´ĮXC_RESOURCE -> sftwareupdated exceeded mem limit: ActiveSoft 500 MB (non-fatal)
#MAC MINI MID 2010 HIGH SIERRA WINDOWS#
Just display, keyboard and mouse connected to the Mac.įunny thing is I had an old SSD where a Windows distro was installed and if I plug it to the mac via USB adapter and select its EFI file by holding the Option key during boot, it goes right into a fully functional Windows environment, making me think that there is no hardware problem with it. I also tried safe boot, resetting NVRAM and PRAM, and an installation USB thumb drive.
#MAC MINI MID 2010 HIGH SIERRA FULL#
I tried Internet Recovery, both using Option+ Command+ R and Shift+ Option+ Command+ R (however, this last option yields a slightly different outcome: it gets stuck in the screen with the apple logo, but instead of the full bar, I get the spinning wheel). I have three HDs installed on my Mac Pro, and my boot HD is the original Apple 512 SSD that came with the Mac. I have Logic Pro X installed on this machine, and plan to use it exclusively for music recording and production. I tried to boot into the Recovery partition and the same thing happens. I have a Mac Pro 5.1 mid-2010 (2.4ghz eight core) running El Capitan that I use in my music home studio. Is is worth mentioning that the bar progresses relatively fast until it reaches the middle and then it goes really slowly until the end. The Apple logo appears and the progress bar underneath goes all the way to the end, but it does not go beyond that point. I verified that everything was working and then turned off the machine. When it arrived I turned it on and it booted regularly into macOS High Sierra, since this is the last version supported by this model. I bought a used Mac Mini mid-2010 server.