Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

Good to know, thanks.

 

 

Same thing here. Also using APFS.efi seems to increase the time between BIOS screen finishing and Clover loading.

 

 

So, the two alternatives still both show a few lines? That's mildly annoying. I won't worry about a fix until they can be removed completely, but I appreciate the reply.

CsmVideoDxe.efi doesn't do anything to the logs on my gigabyte board.

Csm disabled.

 

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites
Advertisement

CsmVideoDxe.efi doesn't do anything to the logs on my gigabyte board.

Csm disabled.

 

 

Sent from my SM-G930F using Tapatalk

Oh, I'm using Gigabyte but I have not tested it.

I just mentioned this problem yesterday and think this only happen to me  :lol:. Now I know many people also see these text like me, the apfs logs  :yes:

Share this post


Link to post
Share on other sites

CsmVideoDxe.efi doesn't do anything to the logs on my gigabyte board.

Csm disabled.

 

 

Sent from my SM-G930F using Tapatalk

It used to work on my rig but not anymore. I still see few lines of APFS log.

Share this post


Link to post
Share on other sites

hi,someone tells me how to install from usb in hfs mode and not like apfs 

thank you

 

Somewhere in this topic someone mentioned changing the firmware features, which forces the installer to install on HFS+j:

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2471719

 

Not sure if it still works though

 

Alternatively you could:

 

1. Install on a separate disk or partition, format another harddisk or partition as HFS+j and clone your installation to the HFS+j formatted disk or partition or

2. From an installation on another disk or partition, directly deploy the install on another HFS+j disk or partition by using the startosinstall method and --converttoapfs NO

"/Applications/Install macOS High Sierra Beta.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS High Sierra Beta.app" --converttoapfs NO --volume /Volumes/DEST_DISK --rebootdelay 30 --nointeraction

 

Share this post


Link to post
Share on other sites

hi,someone tells me how to install from usb in hfs mode and not like apfs 

thank you

 

Also try this,

Format as hfs+j, before stage 2 start to install, try to edit true to be false. It may works fine.

 

/macOS Install Data/minstallconfig.xml

    <key>ConvertToAPFS</key>

    <false/>

Share this post


Link to post
Share on other sites

Hi, 

After apfs gm install I have full tracked options in system preferences to configure with rehab man's vodoops2controller.kext.

 

But after a couple of boots the trackpad pref pane show no tracked found though I have full functionality as I had configured earlier.

 

What's the problem? I removed nvram plist, repaired permissions, reinstalled rehab mans vodoops2controller.kext but still empty, pref pane.

 

Any suggestions

 

Thanks.

Share this post


Link to post
Share on other sites

Somewhere in this topic someone mentioned changing the firmware features, which forces the installer to install on HFS+j:

http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/?p=2471719

 

Not sure if it still works though

 

Alternatively you could:

 

1. Install on a separate disk or partition, format another harddisk or partition as HFS+j and clone your installation to the HFS+j formatted disk or partition or

2. From an installation on another disk or partition, directly deploy the install on another HFS+j disk or partition by using the startosinstall method and --converttoapfs NO

"/Applications/Install macOS High Sierra Beta.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS High Sierra Beta.app" --converttoapfs NO --volume /Volumes/DEST_DISK --rebootdelay 30 --nointeraction
If follow what you mentioned, no need to change xml file? Can i keep hfs+j when update new version?

 

Now installer always force to change hfs+j to apfs.

 

I dont know info your terminal command.

 

Thanks in advance.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

If follow what you mentioned, no need to change xml file? Can i keep hfs+j when update new version?

 

Now installer always force to change hfs+j to apfs.

 

I dont know info your terminal command.

 

Thanks in advance.

 

나의 LG-F800S 의 Tapatalk에서 보냄

There's no need to change the xml file indeed. I've been on HFS+j myself from DP1 up to DP8 without any issue. I believe that as long as the OS is on HFS+j disk, an update won't convert to APFS. At least, it was for me like that in the DP's... I don't know how it will be after the HS release.

 

The terminal command is a command to deploy the High Sierra installation directly into the destination disk. You can parse "--converttoapfs NO" to it to disable the APFS conversion:

Usage: startosinstall --volume <target volume path>

Arguments
--applicationpath, a path to copy of the OS installer application to start the install with.
--license, prints the user license agreement only.
--agreetolicense, agree to license the license you printed with --license.
--rebootdelay, how long to delay the reboot at the end of preparing. This delay is in seconds and has a maximum of 300 (5 minutes).
--pidtosignal, Specify a PID to which to send SIGUSR1 upon completion of the prepare phase. To bypass "rebootdelay" send SIGUSR1 back to startosinstall.
--converttoapfs, specify either YES or NO on if you wish to convert to APFS.
--installpackage, the path of a package to install after the OS installation is complete; this option can be specified multiple times.
--usage, prints this message.
--volume, path to the target volume.

Example: startosinstall --volume /Volumes/Target --converttoapfs YES 

More info: https://forums.developer.apple.com/thread/48793

Share this post


Link to post
Share on other sites

There's no need to change the xml file indeed. I've been on HFS+j myself from DP1 up to DP8 without any issue. I believe that as long as the OS is on HFS+j disk, an update won't convert to APFS. At least, it was for me like that in the DP's... I don't know how it will be after the HS release.

 

The terminal command is a command to deploy the High Sierra installation directly into the destination disk. You can parse "--converttoapfs NO" to it to disable the APFS conversion:

Usage: startosinstall --volume <target volume path>

Arguments
--applicationpath, a path to copy of the OS installer application to start the install with.
--license, prints the user license agreement only.
--agreetolicense, agree to license the license you printed with --license.
--rebootdelay, how long to delay the reboot at the end of preparing. This delay is in seconds and has a maximum of 300 (5 minutes).
--pidtosignal, Specify a PID to which to send SIGUSR1 upon completion of the prepare phase. To bypass "rebootdelay" send SIGUSR1 back to startosinstall.
--converttoapfs, specify either YES or NO on if you wish to convert to APFS.
--installpackage, the path of a package to install after the OS installation is complete; this option can be specified multiple times.
--usage, prints this message.
--volume, path to the target volume.

Example: startosinstall --volume /Volumes/Target --converttoapfs YES 
More info: https://forums.developer.apple.com/thread/48793
Thank you so much

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

/Applications/Install macOS High Sierra Beta.app" --converttoapfs NO ,work from usb installer ??

No, it's a tool within the installer.app to deploy directly onto a harddisk or ssd. When the tool is done your system will reboot to start the installation from that disk. In other words: You'll need a working macOS install, the macOS High Sierra beta.app from the AppStore and a spare empty harddisk or SSD. 

 

If you insist in creating an USB installer, I'd try the method from camillionario I linked to earlier.

 

Edit: Or maybe it depends on in which way you created the USB. I think if the install .app is on the USB, it might be possible. Not sure though.

Share this post


Link to post
Share on other sites

Goodevening to all, sorry in advance but is quite difficult to follow all the 191 pages...

i have installed Mac OS 10.13 GM in apfs from scratch on my first system in rig (I have even create a new "default" config.plist instead of using the one from Sierra)

in summary, the system boots fine but I'm having graphic glitches on my gtx 660ti gfx after a while... at first it looks good ( I mean when the os boot up) but after a while (I don't know what happens or what kind of app or something else related) it starts to give me the glitches attached...

do you know if on my gfx can I install some Nvidia driver to avoid this??

i also attach my current config.plist file (p.s. I don't have anymore a "custom" dsdt.aml file in the appropriate folder)

 

thank you for your feedback

Archivio.zip

Share this post


Link to post
Share on other sites

Now that the final release is nearly here i think its time i fixed my bluetooth issue on my laptop.

I lose bluetooth sometimes after sleep and i can not get it back by rebooting, i have to shutdown then boot up.

I have attached ioreg of before sleep and after sleep with bluetooth not available in the hope someone can point me in the right direction.

BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext and both installed to S/L/E

 

Vendor:14E4, Device: 43B1

 

 

EDIT: Seems ok now after a decent sleep bluetooth came back.

I updated AirportBrcmFixup.kext to latest  :thumbsup_anim:

 

Edit 2: I stand corrected, after a longer sleep bluetooth is gone again  :( please help

config.plist.zip

Shane’s MacBook Pro.zip

Shane’s MacBook Pro after sleep.zip

Shane’s MacBook Pro after sleep reboot.zip

Share this post


Link to post
Share on other sites

Hi, 

After apfs gm install I have full tracked options in system preferences to configure with rehab man's vodoops2controller.kext.

 

But after a couple of boots the trackpad pref pane show no tracked found though I have full functionality as I had configured earlier.

 

What's the problem? I removed nvram plist, repaired permissions, reinstalled rehab mans vodoops2controller.kext but still empty, pref pane.

 

Any suggestions

 

Thanks.

 

- Rightclick -> show content on VoodooPS2Controller.kext

- Go to Contents -> Plugins -> VoodooPS2Trackpad.kext

- Rightclick -> Show content

- Edit Info.plist, replace:

<key>Darwin 16.x</key>

with

<key>Darwin 17.x</key>

Share this post


Link to post
Share on other sites

 

- Rightclick -> show content on VoodooPS2Controller.kext

- Go to Contents -> Plugins -> VoodooPS2Trackpad.kext

- Rightclick -> Show content

- Edit Info.plist, replace:

<key>Darwin 16.x</key>

with

<key>Darwin 17.x</key>

Hi I have both Darwin 16.x and 17.x both already in the info.plist.

post-179304-0-43170600-1506091560_thumb.jpeg

Share this post


Link to post
Share on other sites

Hi I have both Darwin 16.x and 17.x both already in the info.plist.

Do we still need this method? AFAIK since VoodooPS2 v1.8.27 (latest is 1.8.28) @Rehabman has given support for 10.13 (Beta)  :)

Share this post


Link to post
Share on other sites

can anyone try to identify the problem I have with USB...I have installed 10.13 GM everything was fine using 10.13 beta 8-9 USB port limitation patch, then I have restored my 10.12 to the new SSD running 10.13 and now looks like I have a problem of USB port limitation...is the patch different for the GM release?

if so can you please let me know what should I change?

running 10.13 on APFS

 

 

figure out that the problem is not port limitation...my keyboard/mouse connected via USB HUB my keyboard is apple keyboard with USB HUB, when i connected the mouse directly to PC i have no problems, but when connecting the keyboard i have problem, connecting general keyboard is working fine.

the Apple keyboard is working fine under 10.12 and 10.13 GM (without the restore i did) also the HUB...so it make me wonder what could have been changed once i restored my system...? anyone have any idea?

Share this post


Link to post
Share on other sites

My High Sierra GM boot slower compared to Sierra. It stop at this verbose boot screen for about 15s. Will erase this disk make it go faster through this line? Any solution? Thanks

 

post-1767774-0-66818400-1506175280_thumb.png

 

After 15s

post-1767774-0-89845400-1506175333_thumb.jpg

 

And then 

post-1767774-0-47795600-1506175378_thumb.png

Share this post


Link to post
Share on other sites

My High Sierra GM boot slower compared to Sierra. It stop at this verbose boot screen for about 15s. Will erase this disk make it go faster through this line? Any solution? Thanks

 

 

Disable TRIM. It doesn't work well on apfs formatted SSD's with SandForce controllers and maybe several other old controllers...

Share this post


Link to post
Share on other sites

I don't know if that's still applicable with GM release but High Sierra beta versions used to run terribly slow on a HDD with APFS partitions. This made APFS suitable only for SSD. If you have a mechanical drive, you should probably re-install on a legacy HFS+ partition.

 

If you have an SSD (as it would seem) and had to disable TRIM, you might as well revert to HFS+ format too, TRIM being highly desirable on an SSD... Personally, HiSie runs perfectly with APFS on 2 of my laptops with different SSDs and all have TRIM enabled.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Clover r5051 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r5051 for VMware.zip". Mount Clover-v2.5k-5051-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
      BaseSystem_PLK.tool_Catalina.zip
    • By Slice
      I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
      I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
       
      Hardware
      Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
      Chipset Intel 7 series, no patches needed
      Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
      LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
      Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
      SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
      USB3.0 works natively if not disabled in DSDT
      PS2 keyboard and touchpad works with VoodooPS2.
      WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
      LCD Screen 1366x768
      BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
      For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
       
      WiFi
      It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
      I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
      As well a patch for channels.
      I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
       
      VideoCards
      In Bios we can set Optimus = Enable/Disable
      If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
      If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
      But here there is contradiction with WiFi with required Board-ID from MacBookAir.
      So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
      Set BoardID like iMac13,2 to make Nvidia working.
      Patch BoardID in Brcm4360 to make WiFi working.
      Now I have
      Inject->
      ->Intel=YES
      ->Nvidia=YES
      and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
      For Intel graphics there is a patch against 8 apples at start.
      This Nvidia 5200 is Fermi and works in ElCapitan.
       
      Brightness
      No special kexts.
      The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here  #72 
       
      DSDT and SSDT
      This is very long story and finally I have working sleep in both cases Intel or Nvidia.
       
      Sensors
      I use my HWSensors3 with FakeSMC 3.5.2.
      I got monitoring:
      CPU temperature
      GPU temperature
      GPU main frequency
      GPU shader frequency
      Battery state % full, time to charged or time to empty.
      Battery voltage dinamically.
      Battery amperage dynamically. I can see it changes on heavy games.
      HDD temperature.

       
      Audio
      I like VoodooHDA and have no problems with it.
      The sound is clear, loud, and switchable between internal speaker and headphone.
      Mic is working.
       
      Bluetooth
      Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
      For 10.13.6 there is other kext BRCMInjector.
       
      Keyboard, Touchpad and Touchstick
      Post #14
      I made my fork of the VoodooPS2 driver, take here sources and release version
      https://github.com/SergeySlice/VoodooPS2-for-ALPS
       
      My config, ACPI files and kexts are in attachment.
      05.12.2017
      EFI.7z
       
      EDITED:
      Better DSDT in the post #6.
      Sleep working even when AC inserted.
       
      EDITED 06.12.2018
      Now I have HighSierra and this is my EFI folder. Note, HighSierra is possible only with Intel graphics (Optimus is enabled in BIOS)
       

       
       
      Welcome to discussion!
      EFI-E6430.7z
      BRCMInjector.kext.zip
    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI CLOVER Z390 DESIGNARE.zip
       
      ---OPENCORE FOLDER---
      *Use this folder with FULL DSDT PATCHED
      EFI OPENCORE Z390 DESIGNARE.zip
       
      ---DSDT patch requests is here---
       
      https://olarila.com/forum/viewtopic.php?f=19&t=1131
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
      Mac Downloader (thanks to ricoc90)
      Stuck boot in Beta 5 (thanks to MaLd0n)
       
×