Good!!
My Mac mini late 2009 is working High Sierra Beta Developer 6
but Original WIFI card is not Working
Please tell me method to recognize Swapped WIFI card
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS High Sierra (10.13) Unsupported Macs Thread
- Thread starter foxlet
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Good!!
My Mac mini late 2009 is working High Sierra Beta Developer 6
but Original WIFI card is not Working
Please tell me method to recognize Swapped WIFI card
The number of your Beta release in the attached photo is for DEV BETA5
Apple Seeds macOS High Sierra Developer Beta 5 Build (17A330h)
Apple Seeds macOS High Sierra Developer Beta 6 Build (17A344b)
Has anyone with a Mac Pro 3,1 managed to get it to boot HS 10.13 beta 5 or 6 normally (not Safe mode) with a GPU other than the HD2600 XT or nVidia 8800 GTX?
If you have, please report which GPU and whether it was a genuine Apple card or a flashed PC card with efi.rom.
If you have, please report which GPU and whether it was a genuine Apple card or a flashed PC card with efi.rom.
All you have to do is get creative with the actual fisical instalation of the wifi card, because it’s not the same size as the original, other than that macOS recognizes it as soon as you boot...
[doublepost=1503154063][/doublepost]
Ups my bad, I really thought I had developer beta 6...
First, a big thanks to dosdude1 for his tool. Just installed macOS 10.13 on my laptop and it works well. Out of curiosity, what's the state of APFS on unsupported Macs?
Has anyone ended up with a usable Recovery Partition using the 1.1.2 or 1.1.3 High Sierra Patcher? The documentation which was posted at http://dosdude1.com/highsierra/ shows the Recovery Partition Patch unselected for the default patch selections which is puzzling.
This is unlikely, since the processors don't support SSE 4.1, and no supported processor types do. This support is necessary to run Sierra or High Sierra and likely any OS moving forward. I think that El Capitan (using non Apple supported install tools) is the best that you will be able to do with that machine. Even my 3,1 Mac Pro is unlikely to run OS versions much beyond High Sierra using install methods unsupported by Apple. For what I use my computer for, I could probably go on with Sierra or High Sierra for several years beyond them being the current OS and still be fine. You may be okay with El Capitan for several more years depending on your needs. Your results may vary.
I have a Macbook Pro 13 mid-2009 (MacbookPro5,5) that I successfully upgraded to Sierra. Now I am trying to try to upgrade to High Sierra. Downloaded Public beta High Sierra install and dosdude1's patch files.
I ran the patch file, successfully verified the high sierra install file, and went ahead to patch.
During patching and transferring the the patch to my USB drive, I got these messages on the verbose window:
/dev/disk2s1 EFI
/dev/disk2s2 Apple_HFS /Volumes/InstallESD
cp: /Volumes/RedUSB32G/System/Installation/Packages: File exists
cp: /Volumes/InstallESD/Packages: unable to copy extended attributes to /Volumes/RedUSB32G/System/Installation/Packages: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/Core.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/EmbeddedOSFirmware.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/FirmwareUpdate.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/OSInstall.mpkg: No such file or directory
cp: directory /Volumes/RedUSB32G/System/Installation/Packages does not exist
cp: directory /Volumes/RedUSB32G/System/Installation/Packages does not exist
When booting up from the USB to install high sierra, I DO NOT get a window/prompt to proceed with installation. Just the typical "Restore from Time Machine Backup, Reinstall OS X, Dos Utility, etc".
Any clues on what I possibly did wrong? Any help is appreciated. And I apologize for the long post.
Thanks and ~Aloha~
I ran the patch file, successfully verified the high sierra install file, and went ahead to patch.
During patching and transferring the the patch to my USB drive, I got these messages on the verbose window:
/dev/disk2s1 EFI
/dev/disk2s2 Apple_HFS /Volumes/InstallESD
cp: /Volumes/RedUSB32G/System/Installation/Packages: File exists
cp: /Volumes/InstallESD/Packages: unable to copy extended attributes to /Volumes/RedUSB32G/System/Installation/Packages: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/Core.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/EmbeddedOSFirmware.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/FirmwareUpdate.pkg: No such file or directory
cp: /Volumes/RedUSB32G/System/Installation/Packages/OSInstall.mpkg: No such file or directory
cp: directory /Volumes/RedUSB32G/System/Installation/Packages does not exist
cp: directory /Volumes/RedUSB32G/System/Installation/Packages does not exist
When booting up from the USB to install high sierra, I DO NOT get a window/prompt to proceed with installation. Just the typical "Restore from Time Machine Backup, Reinstall OS X, Dos Utility, etc".
Any clues on what I possibly did wrong? Any help is appreciated. And I apologize for the long post.
Thanks and ~Aloha~
Last edited:
This is an issue with v1.1.2 and older of the tool. It has been fixed in v1.1.3, so ensure you're using that version and try creating your drive again.
[doublepost=1503261886][/doublepost]
That was actually intentional, as I consider the recovery partition patch to be non-essential (not required for High Sierra to function normally on an unsupported machine). If you think it'd be more beneficial to have that set as a default option, though, I can definitely make that change.
I have macOS High Sierra Developer Beta version 6 (17A344b) on my MacBook Pro (15-inch, Mid 2009). The file system is APFS. I boot to the internal SSD from a USB stick after setting nvram boot-args="rd=disk1s1". It is working well for an unsupported MBP. The install was using dosdude1's macOS High Sierra Patcher tool, many thanks! Having to use the USB stick to boot is a bit ackward, but once booted can be removed and I do not have access to the Recovery partition as it is apfs also. Is there any discussion or recommendation as to native boot for an unsupported MBP apfs partition? The unsupported MBP's are very unlikely to receive a firmware update from Apple, but anything is possible. My Boot ROM Version: MBP53.00AC.B03 and SMC Version (system): 1.48f2. The future of macOS is based on APFS.
I had the same problem with D.B6 (17a344b), solved by copying the Packages folder in manual from patch v.1.0b3 that works fine, in System / Installation / Packages in patch v.1.1.3 ...... .
The paciocco( mess or similar to the game of the three cards ) worked, I could install it without the poroblemi .....
It's not a solution but it worked.
The odd thing about patch v.1.1.3 works well with versions P.B5 & D.B5 ..... I did not understand why ....
Anyway thank you for immanent work....
Please explain yourself better... how you explained it’s not right... untouched original firmware on unsupported macs in no way boot APFS, at this point only @foxlet has a dual boot method to do such a task...
@dosdude1 patch is works blissfully using HFS, and so far does not support APFS...
I’ve tied that myself, you format a drive to APFS, and it does do the installation, but when it reboot’s it does not go to the installed sytem because it can’t find it cause it’s in APFS...
I see what he did. He essentially used a USB flash drive, possibly containing a macOS installer, to begin the booting process. When passed the desired boot volume as a boot argument, in this case using NVRAM with the command "nvram boot-args="rd=disk1s1"", the kernel will load (off the HFS-formatted USB drive), but will continue booting off the volume specified, rather than the volume the boot was initially started from like it would normally. Not sure doing this is something I'd recommend, but it works, I guess. I know I've mentioned this before, but I personally see no real benefit to using APFS as a boot volume, especially on unsupported machines.
I did, at least for the 1.1.2 High Sierra Patcher, try rerunning the post-install patching with the recovery partition patching enabled and that didn't produce a recovery partition which fully booted. I believe I also tried that from a clean install as well with the post-install patching having the recovery partition patching enabled. When the recovery partition patching isn't applied, the recovery partition produces the null icon on boot. When it is patched, the boot only proceeds partially through the recovery partition boot. So that area of the High Sierra Patcher seems broken (on a MacPro 3,1 anyway).
Hello... I did exactly as dosdude1 further explained. It is not elegant, but works just fine. The USB drive does contain a macOS installer. The USB drive contains the installer created using dosdude1's macOS High Sierra Patcher. I did not mean to raise controversy, just would like to show what is simply possible. Ultimately, I would like to boot directly to the APFS volume without my demented method. I am delighted that we are having this discussion as it may lead to a more elegant self boot in the future.
So forgive me my dumbness, but basically he just used the HFS flash drive containing the macOS High Sierra installer as a bypass to be able to boot APFS?
[doublepost=1503273157][/doublepost]
Please you did not raise any controversy at all, actually I thank you very much for contributing with that very valid piece of information, it's good to know it's possible how you did it! That is awesome in my view that, that method works!
Im even more exited to see ( even as he mentioned he doesn't personally think APFS isn't that important for unsupported Macs) he knows and understood like immediately what you did, maybe that even against what he thinks he will maybe find a way to implement it somehow in that wounder patcher of his
So thanks a lot for your share and if find out about more cool things we humbly accept them
Last edited:
Just out of curiosity - why is that? Why is it not a benefit to use APFS on unsupported macs? Of all High Sierra features this is the one that I’ve been looking forward to the most.
Last edited:
Great question, after all the direction of Apple is APFS. Is is an effort to deal with cyber security, one step ahead or maybe just a faster user experience. As a developer, if you immerse yourself in the years of concentration and development that has led us to this juncture it becomes obvious that we need a file system that addresses the many core problems with HFS+. Data integrity, encryption, snapshots, and many more are what leads us to APFS. Lets find a way to embrace it for unsupported macs. It does have limitations. It does not take advantage of byte-addressable non-volitle ram and does not support compression, at least not yet. We are working with High Sierra beta software. Lets keep the vision alive and continue asking questions. Look forward. Apple has decided to leave us behind by not supporting our hardware, actually firmware. We can come together and support ourselves.
As the unsupported possibly we could consider a small HFS+ boot partition with kernel that points at the APFS partition internally, somewhat like my use of the USB HFS+ drive to use my APFS install. Again many thanks to dosdude1 for his inspiration.
I love ocean sailing!!
From the most remote island on the planet.
As the unsupported possibly we could consider a small HFS+ boot partition with kernel that points at the APFS partition internally, somewhat like my use of the USB HFS+ drive to use my APFS install. Again many thanks to dosdude1 for his inspiration.
I love ocean sailing!!
From the most remote island on the planet.
Last edited:
Is the Packages folder you mentioned above from the "macOS High Sierra Patcher.app" or from the "Install macOS High Sierra Beta.app"? And what file(s) should I copy from source to destination?
Thanks and ~Aloha~
The latest version of my tool should create the drive properly with no modifications needed... Can you try downloading the latest version of my tool off my webpage, and let me know if you still get the same errors?
you can boot the afps volume if you install the latest clover to the EFI partition. that is what I did so I wouldn't have to use a usb all the time. It takes a few extra seconds to boot because it takes a little bit to default to Clover once it realizes it can't find a drive.
I personally like afps on unsupported ssd Macs. I think it runs more smoothly.
How did you get it to install on the ssd without it failing using afps?
Apple's High Sierra Developer Beta 7 is now out, very exicted! Closer and closer to GM, I believe it is 1 or 2 more betas to go!
Awesome! Your latest tool (version 1.1.4) worked great --- no errors. I am now in the process of installing High Sierra Beta (not sure what version) on to my mid-2009 Macbook pro 13".
Thanks again. Great work on your tool!
~Aloha!~