Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

Advertisement

Sure but depending on the boot loader you use you need apfs.efi for Clover oder apfs.ffs for Oz otherwise APFS Volumes won't be detected. In case of Clover just put apfs.efi to drivers64UEFI or drivers64 depending on your Clover installation. Use UEFI flavour if installed for UEFI Motherboards or drivers64 if installed for legacy Motherboards.

Share this post


Link to post
Share on other sites

At griven : Was it possible to you to boot High Sierra from the apfs drive?

If your trying to boot clover on a apfs drive you will need to install clover but it will install the files in the root on the drive/partition. You need to mount your EFI and copy the clover files into it and replace the config.plist with yours plus add kexts etc. I hope this helps.

 

Yes for a fresh install on an SSD for me with Beta 4 was apfs only no option to choose not to upgrade. iMac 17,1 smbios.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Unknown CPU Fixed


About this Mac unknown cpu error fixed.


Thius patched worked Haswell-E CPU and  Broadwell CPU


1-Enable in config xcpm_bootstrap_Broadwell or Haswell


2-Enable in config xcpm_cpuid_set_infoBroadwell or Haswell


3-FakeCPUID is Broadwell 0x040674


4.CPU Type is Broadwell 0x0a02


5-FakeCPUID is Haswell 0x0306F2


6.CPU Type is Haswell 0x0a01


 


 


XCPM Brodwell and Haswell.zip


post-413859-0-93605300-1501387320_thumb.png

Share this post


Link to post
Share on other sites

1) it’s not possible to choose anything in Beta 4 for HFS+

2) if I Install clover the drive is not bootable at all and also not visible without an HFS drive.

 

I don't understand these questions. I've made a fresh install. And like others masOS, you can format a hard disk via disk utility (macOS journalized for example) and install Beta 4.

 

For Clover, you can copy clover from usb on EFI mounted partition or post-install it.

 

The installation is no different from the beta 3, you are talking about

Share this post


Link to post
Share on other sites

LOL you can format what ever you want but Developer Beta 4 converts everything to APFS

 

On my config, since Beta 1, there is no convert automatically to Apfs during installation. For Beta 4, Apple say "HDD Macs only can't be converted" in this seed release.

 

Until first Beta,  macOS Installer  indicates the upgrade on some system: just deselect. LOL  Apple make change? Did you do Beta 4 clean install?

post-1110743-0-68753400-1501402670_thumb.png

Share this post


Link to post
Share on other sites
I have tried to install High Sierra in HDD without changing anything in smbios (Configuration suggested by Clover) and the installation DP4 automatically changes APFS.
If you change Bios Version FF and FFM, the installation is done in HFS +.
I had to format HDD a few times without being aware of it, until I made the changes.
 
APFS
post-887245-0-57011700-1501407456_thumb.png
 
HFS+
post-887245-0-16479300-1501407500_thumb.png
 
Update from DP1 to DP4

 

Share this post


Link to post
Share on other sites

LOL you can format what ever you want but Developer Beta 4 converts everything to APFS

I'm on HFS+j too with DP4. 

You asked if it was possible and you got your answer. Multiple people are saying that it is.

You're also told how to make Clover to boot and how to install Clover on APFS.

 

Chris1111 even installed it on HFS+j to actually show you that it is possible. So, what more do you want?

 

If you're not able to install on HFS+j or to boot APFS, then maybe you should tell us how you are trying to do it so that we can help you, instead of questioning someone elses answers.

Share this post


Link to post
Share on other sites

I installed High Sierra Beta 3 to APFS, but I am unable to install any version of Clover to the install drive. The installation does not complete.

Share this post


Link to post
Share on other sites

I installed High Sierra Beta 3 to APFS, but I am unable to install any version of Clover to the install drive. The installation does not complete.

Clover Packages not working in apfs volumes this is already discuss since the first day HS Beta

You need to do this manually for UEFI , Mounting the EFI Partition

Share this post


Link to post
Share on other sites

Maybe creating a second partition and doing this:

 

How to hide a hard drive partition on your Mac
August 27, 2014

HardDriveIconX.png?resize=150%2C150&ssl=Generally when you either partition your Mac’s boot drive, or attach a secondary drive to your Mac, then provided the partition’s formatting is compatible with OS X, you should see it mount and be available in the Finder. However, there may be times when you might wish to keep a partition hidden, either because you do not use it, or because it is not intended to be shown in the first place.

Some examples of this are the “EFI” or “Recovery HD” partitions on your boot drive, that support system functions but are not intended to be accessed directly; however, in some cases (especially in dual-boot environments) you might find these showing up. Of course, modifying the contents of these may destabilize your system or prevent some features from working properly, so you might want to prevent these from mounting.

If you have partitions showing on your Mac that you would like to hide, then you can do so, but will need to get under the hood with some Terminal commands. Don’t worry, the methods used here are entirely harmless and can easily be undone:

1. Get the partition’s UUID

VolumeUUID.png?resize=300%2C216&ssl=1

The volume’s UUID can be found and copied here in the Disk Utility info window (click image for larger view).

Open Disk Utility, where you should see the list of volumes (partitions) for each drive on your Mac. Select the drive you want to hide, and press Command-i to get information on it. Resize the info window that appears to reveal the entire Universal Unique Identifier (UUID) for the drive, and then select and copy the entire UUID.

The UUID can also be found in the Terminal by typing “diskutil info,” followed by a single space, and then dragging the desired hard drive to the Terminal window before pressing Enter. For instance, the following command will get info on a volume called “EFI”:

diskutil info /Volumes/EFI

You can then find “Volume UUID” in the output of this command to find the UUID needed to hide this partition.

2. Edit or create the “fstab” file

The “fstab” file is a hidden system file that is used to specify how partitions are handled in OS X, where you can have them mount at specific points other than the default, or mount only in read mode. We are going to use it to prevent the partition (identified by its UUID) from mounting.

To create or edit this file, open the Terminal and run the following command from an administrative account:

sudo pico /etc/fstab

This will open an editor, in which you will enter the syntax needed to hide the drive.

3. Add the fstab commands to hide the drive

Enter the following command, replacing the UUID consisting of zeros with the one you copied for your partition’s volume.

UUID=00000000-0000-0000-0000-000000000000 none hfs rw,noauto

What this command does is specify the identifier (the UUID), then the mount point (none), followed by the format (hfs), and then options (read/write, and no auto mount). The keys here are that the mount point is set to none, which prevents the drive from mounting, and noauto, which prevents an attempt to automatically mount it.

fstabnomount.png?resize=625%2C286&ssl=1

The UUID specified (arrow) in the fstab file will be set to not mount automatically.

You can specify as many drives you want in the fstab file, by adding one per line. When finished, to save the file press Control-O (this writes out the file), and then press Control-X to exit the editor.

With the fstab file updated and saved, you can now reboot your system, and the specified drives should no longer automatically mount. Keep in mind that this will only pertain to the current operating system, so if you dual-boot your Mac and see these drives load in more than one OS X installation you use, then you will have to follow these instructions to edit the fstab file for each OS.

While this can be used for hiding system partitions like the Recovery HD and EFI, you can also hide any other partitions you might not want inadvertently modified. Just similarly add them to the fstab file, followed by rebooting and they should also hide.

Undoing the changes

If for some reason you no longer want a partition hidden, then simply edit the fstab file and remove the line that specifies the partition. If you have not used the fstab file for other purposes, then you can also simply delete it by running the following command in an administrative account, followed by restarting:

sudo rm /etc/fstab
 
Then install clover in that partition ( I think must be Fat32 ) and format the other partition as APFS.

Share this post


Link to post
Share on other sites

Clover Packages not working in apfs volumes this is already discuss since the first day HS Beta

You need to do this manually for UEFI , Mounting the EFI Partition

I have a legacy BIOS install.

Share this post


Link to post
Share on other sites

What is your HS install method

Only the core.pkg method has worked for me. I am aware of this,  "For APFS you need Drivers UEFI apfs.efi or apfs-64.efi for the Legacy Clover

you must put this drivers into drivers64UEFI or drivers64

Share this post


Link to post
Share on other sites

Another solution is to install as hfs+, install clover to the EFI partition then attach the drive to another HS installation, open disk utility, dismount the drive go to edit and convert it to APFS, the only drawback is that you need another system with HS installed to do this, but I warranty it works, I did it in a Toshiba L855-S5309 and it works. :thumbsup_anim:

 

post-35379-0-03893100-1501432376_thumb.png

Share this post


Link to post
Share on other sites

Another solution is to install as hfs+, install clover to the EFI partition then attach the drive to another HS installation, open disk utility, dismount the drive go to edit and convert it to APFS, the only drawback is that you need another system with HS installed to do this, but I warranty it works, I did it in a Toshiba L855-S5309 and it works. :thumbsup_anim:

 

attachicon.gifScreen Shot 2017-07-30 at 12.41.16 PM.png

I might just try that. 

Share this post


Link to post
Share on other sites

Only the core.pkg method has worked for me. I am aware of this,  "For APFS you need Drivers UEFI apfs.efi or apfs-64.efi for the Legacy Clover

you must put this drivers into drivers64UEFI or drivers64

Core is not good because Imaging is death in HS, Core.pkg or Osinstall.mpkg is depreciated for High Sierra

Core.pkg do not Create a Recovery HD and Volumes VM

 

You can try the new Apple Deploying method startosinstall  its the new way for Deploy recommanding by Apple! 

The tools is inside macOS High Sierra Beta.app, the name startosinstall; you can find in Contents/Resources/startosinstall

This is good for all Hackintosh user

I find it a shame to see so many people have a lot of difficulty with High Sierra

You can see my signature, My Hackintosh Stuff.  I made a program a few weeks ago to use startosinstall, the name is MACOSXInstaller. Clover is included in my program as well as the apfs drivers

 

If you doing this on your way

See Usage: startosinstall bellow

 

Usage: startosinstall --applicationpath <install macOS.app 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. If you do not specify this, the default is YES.--usage, prints this message.

 

 

 

You can start from scratch, Inside macOS Sierra 10.12 ; formatted your SSD or HD in Mac OS Extended journaled / Guid table

 

To do the method manually

FIRST! Install Clover to the SSD or HD in (UEFI) or (ESP boot0af + CloverEFI 64-Bits SATA), not working Legacy

Do not use Clover RC scripts on select volume.

 

Make sure you have on your Applications macOS High Sierra Beta.app (Beta 4 or Public Beta 3)

Select Volume not working in BETA 1,2,3 This is why you need BETA 4 or PB 3

 

 

 

If you doing this on your way

See Usage: startosinstall Upper

 

Its verry fast, when its finish you have to clic Terminate 

See Pics bellow

 

 

68747412.jpg

 

 

 

 

On that way you have Clover install for APFS Volumes or HFS+J

Hope that help and fix your issue

 

Trouble shooting for APFS Install

If you have install to a External SSD you can correct the trouble shooting APFS 

Retry, Reboot and dont install, open the folder in your Install SSD

macOS Install Data verify the file minstallconfig.xml see if the APFS is set to true

like the image in the Spoiler

 

sans_t42.png

 

 

 

Post edited **********

 

​Last Edit 02 August 2017 by chris1111

I edit the post so that people see the Usage startosinstall

Share this post


Link to post
Share on other sites

 

Core is not good because Imaging is death in HS, Core.pkg or Osinstall.mpkg is depreciated for High Sierra

Core.pkg do not Create a Recovery HD and Volumes VM

 

You can try the new Apple Deploying method startosinstall  its the new way for Deploy recommanding by Apple! 

The tools is inside macOS High Sierra Beta.app, the name startosinstall; you can find in Contents/Resources/startosinstall

This is good for all Hackintosh user

I find it a shame to see so many people have a lot of difficulty with High Sierra

You can see my signature, My Hackintosh Stuff.  I made a program a few weeks ago to use startosinstall, the name is MACOSXInstaller

 

You can start from scratch, Inside macOS Sierra 10.12 ; formatted your SSD or HD in Mac OS Extended journaled / Guid table

 

Install Clover to the SSD or HD in (UEFI) or (ESP boot0af + CloverEFI 64-Bits SATA), not working Legacy

Do not use Clover RC scripts on select volume.

 

Make sure you have on your Applications macOS High Sierra Beta.app (Beta 4 or Public Beta 3)

Select Volume not working in BETA 1,2,3 This is why you need BETA 4 or PB 3

 

Rename the SSD Install  for adapte to the command, see --volume /Install

 

The command for APFS  is

( copy and passe the command )

 

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

 

Install is the name of the volumes, you can can change the name if you want but make sure is the name of the SSD you are trying

 

For HFS+J  the command is

 

( copy and paste the command )

 

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

 

Install is the name of the volumes, you can can change the name if you want but make sure is the name of the SSD you are trying

 

Its verry fast, when its finish you have to clic Terminate 

See Pics bellow

 

 

68747412.jpg

 

 

 

 

On that way you have Clover install for APFS Volumes or HFS+J

Hope that help and fix your issue

 

Thank you so much.

Share this post


Link to post
Share on other sites

I'm on HFS+j too with DP4. 

You asked if it was possible and you got your answer. Multiple people are saying that it is.

You're also told how to make Clover to boot and how to install Clover on APFS.

Chris1111 even installed it on HFS+j to actually show you that it is possible. So, what more do you want?

If you're not able to install on HFS+j or to boot APFS, then maybe you should tell us how you are trying to do it so that we can help you, instead of questioning someone elses answers.

HFS+ is only possible to install to an usb drive or an hdd but not on an ssd, if you don’t know what you are talking about then say nothing!

Share this post


Link to post
Share on other sites

HFS+ is only possible to install to an usb drive or an hdd but not on an ssd, if you don’t know what you are talking about then say nothing!

Please stop :rolleyes:  I show you last night install on SSD OCZ Agility 3 120 g  HFS+J ➤ Here

 

 

 

 

captur89.png

 

 

Share this post


Link to post
Share on other sites

HFS+ is only possible to install to an usb drive or an hdd but not on an ssd, if you don’t know what you are talking about then say nothing!

Well then ...

 

Image%202017-07-30%20at%2011.12.17%20PM.

 

 ... if you know the answer yourself, why are you asking then?

Share this post


Link to post
Share on other sites

Guys, wasn't APFS supposed to be the default filesystem? What are we arguing about? I'm sure if you wanna have it in HFS+, you can have it. But then again, why would you want that? :))

 

Just reading you guys' posts made me curious enough to wipe my High Sierra partition, format it as HFS+ (again) and start the upgrade from Sierra.

 

Result? Well, aside from the fact that it didn't ask me to update to APFS, it automatically switched to APFS. Am I mad about it? Not at all! :))) Wasn't that the whole point of APFS? To be default? And the switch to be transparent to the user?

 

Anyway, I have a theory (actually two) since some of you guys have it in HFS+, others (including myself), had it automatically converted to APFS. Which, again, is nothing to be mad about. It's not a bad thing. :))

 

So, a few things I was curious about:

 

1. Did you guys install this build as an upgrade from Sierra? Meaning starting the installation from Sierra? I hope we're all talking about build 17A315i here (just throwing it up there in case that might make a difference).

2. Is it a clean install?

3. Which version of APFS.efi driver are you using? Not sure this makes any difference... I tried with the one from the initial release, installed High Sierra TWICE, and got the exact same result with both the APFS.efi from the initial release, and the one found in Beta 4. So...yeah, probably not relevant...

4. Did you guys have High Sierra previously installed in APFS format on the same SSD? Do you guys think it could be possible that, the first time you install/upgrade to it, something gets saved somewhere, so that it won't ask you every time about it? Like...giving your consent for APFS only once? It's just a theory, of course. And I can't (and won't) wipe my entire SSD just to prove this. :)) I've got other stuff on it. And I need it. :))

5. Are all of you guys' SSDs internal (SATA) SSDs? (looks like they are)

 

Anyway, just a few ideas I would like to discuss with you guys, if you're up to it. :)

 

Also, as a side note, there's no need to argue over such topic. I mean, seriously. :)) We're a community. We don't compete over who's right or wrong. There's no such thing. Anybody can be equally right and wrong. The point here is to learn from each other's successes and failures so we can evolve together as a community.

 

I'm pretty sure that, in this case, the answer is hidden somewhere in the details. We just need to find it. And, to me, there's no better way to do that other than by putting our minds to it, together, as a team.

 

Update:

 

After re-reading Chris' post (thanks Chris), looks like it does occur for SATA SSDs, as well. Cool! That answers our No. 5 question.

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 chebkhaled1960
      Hello everyone
       
      After installing High Sierra

      I have this problem
      Unsupported CPU - Unsupported PCH
      Like in the picture

      Is that normal or i should to care about it ?


      HP Z420 WORKSTATION
      Intel Patsburg C600/X79, Intel Sandy Bridge-EP
      QUAD CORE INTEL XEON E5-1620 03.60 GHz
      RAM: 22 GB ECC RDDR3
      GPU: 2GB NVIDIA GTX 730
       
       

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14GM
      Browse Apple's Developer Beta Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
       
      InstallInfo.plist_edited_10.14beta1.zip
      InstallInfo.plist_edited_10.13.6.zip
    • By WarDoc
      This Post is for helping users with issue that come with Whatevergreen

      Feel free to join in and help users if you know your stuff
      also get the dev's of whatever green to join as well


      Whatevergreen has a few issues

      Multi-monitor Support is lacking as 2 monitors seems to be the limit for some even if the devs say it's not users say it's true

      Some Id's are wrong or missing (hence the nano and 390X not working)

      some GPU names are wrong ( which has been reported many times)

      FOR RYZEN OWNERS with Polaris :
      Modified kext:/S/L/E/AMD9510Controller.kext//Contents/Info.plistfrom:<key>IOPCIMatch</key><string>0x67EF1002</string>to:<key>IOPCIMatch</key><string>0x67FF1002</string> Updating clover to Clover_v2.4k_r4152 and using the config.plist here https://pastebin.com/TYiTEVcMwithbusratio=36 and npci=0x3000 ALSO THIS THREAD IS NOT FOR WHINING in anyway please do not post off topic if you don't like given support in this forum that's all you but majority of use need it.
       
      Source code: repository. FAQ and documentation: link.  
      a real SSDT example https://www.dropbox.com/sh/el66izg1lmk1jiu/AADCZUEjyQyiWWELlmzW2ix-a?dl=0 Credits to Pavo for the hard work of decoding the mess
      Boot argumentsAdd -raddbg to enable debug printing (available in DEBUG binaries).Add -radvesa to disable ATI/AMD video acceleration completely.Add -radoff to disable WhateverGreen.Add -radbeta to enable WhateverGreen on unsupported os versions (10.13 and below are enabled by default).Add -rad24 to enforce 24-bit display mode.Add -radlogo to patch boot logo distortion.Add -raddvi to enable DVI transmitter correction (required for 290X, 370, etc.)Add radpg=15 to disable several power-gating modes (see FAQ, required for 7xxx GPUs). If you Don't Want To use WEG or LILU clover 4297 has a new patch that fixes the same issues without kexts 
      You have to set in config.plist <key>Graphics</key> <dict> <key>RadeonDeInit</key> <true/>
    • By BrianWong11031
      Hi, there
      My desktop hackintosh cannot enter the Sleep Mode.
      I mean it can enter the sleep mode for a few seconds and it will automatically wake up itself.
      How can I fix this issue.
      Thanks for your help.
       
      My BIOS / APM capture:

      My system preference / Energy Saver capture:

       
       
    • By Thereman
      Hello, I'm a noob at installing MacOS on my current PC (which is running Windows 10 x64 Pro).
      Can I do a dual boot with windows 10 and MacOS Mojave? I already have windows 10 installed and I would like to put and MacOS Mojave, can it? If not, should I reinstall from 0 MacOS Mojave and after Windows 10?
       
      P.S: I have already make a topic about "Can I run MacOS" and the export boys on the forum said to me I can run it.
×