Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

Advertisement

Thanks but 1) + 2) are present in my clover, rc script installed too

I don't understand well your EFI but I think all those lines could be related to z270 chipset

Now I am in a clean High Sierra GM and I will wait few days for Nvidia driver

Problem you have should be related to patched nvidiaweb not loaded

if you have patched with nvidia graphics updater app could you post patched kext present in tour S/L/E?

I would like to take a look to its info.plist

Share this post


Link to post
Share on other sites

I don't understand well your EFI but I think all those lines could be related to z270 chipset

Now I am in a clean High Sierra GM and I will wait few days for Nvidia driver

Problem you have should be related to patched nvidiaweb not loaded

if you have patched with nvidia graphics updater app could you post patched kext present in tour S/L/E?

I would like to take a look to its info.plist

Is there any news on a nVidia official web driver or you're just hoping for a new driver like the rest of us? :)

Share this post


Link to post
Share on other sites

take a look here

 

Here the file!

 

thanks

 

the one attached should be fine..

you have to instal with kext utility app or similar...

Also to explain better

You have had success to install an unsigned nvidiaweb driver unlocked to be installed in every osx version

but then you have to match osx version you use now.. if it is GM you have to put 17A362a

post-468967-0-10872500-1505667193_thumb.png

post-468967-0-32887700-1505667219.png

NVDAStartupWeb.kext.zip

Edited by fabiosun

Share this post


Link to post
Share on other sites

take a look here

 

 

the one attached should be fine..

you have to instal with kext utility app or similar...

Also to explain better

You have had success to install an unsigned nvidiaweb driver unlocked to be installed in every osx version

but then you have to match osx version you use now.. if it is GM you have to put 17A362a

 

Installed with kext utility :

 

https://uploads.tapatalk-cdn.com/20170917/92835f93fcc6f4c4e9845817d3061352.heic

Share this post


Link to post
Share on other sites

why I am not see Recovery Partition on Clover GUI even I didn't hide it?

I had the same issue with my laptop. I had to reinstall over the top to get it to show up.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites
Hello,
in High Sierra , after activating the trim, the boot stays about 15 seconds before these rows:

 

kernel: (apfs) er_state_obj_get_for_recovery:3682: No ER state object - rolling is not happening, nothing to recover.

kernel: (apfs) handle_mount:254: vol-uuid: 42581E64-0633-4338-A556-AFBEFF7E020F block size: 4096 block count: 58556556 (unencrypted; flags: 0x1; features: 1.0.2)

kernel: (apfs) apfs_vfsop_mount:1331: mounted volume: VM

kernel: (apfs) apfs_load_inode:3805: *** reset ino 775206 size back to 29314 (from 29989)

 

without trim no breaks.

 

A goodwill coder might explain to me why?

Thanks in advance.

Share this post


Link to post
Share on other sites

Hello guys,

 

After the computer has been idle for a while the monitor screen goes black, when clicking the mouse to get back to desktop it looks weird, please see attached picture. I have an Intel HD520. Everything works 100% except for this issue. Anyone knows what the problem could be?

 

All help and suggestions will be greatly appreciated.

 

Thanks :)

 

Configuration:

- Clover Intel IGPU injections disabled.

- DSDT: IGPU device + injection of ig-platform-id 0x1916 as the _only_ injected property, without this it doesn't seem to work.

- Lilu + DVMT fixup + Graphics Fixup. Tested without Grephics Fixup and same result. DVMT fixup is mandatory to boot the computer.

- Clover version 4210.

post-78274-0-62571500-1505686288_thumb.jpg

Share this post


Link to post
Share on other sites

anyone getting blinitializelibrary failed 0xc00000bb error at boot usually when APFS.efi loads before clover? started on my machine after upgrading a working DP9 to GM. same efi folder works fine from USB. googling the error I just find machines that mine bitcoin with the issue when having 3 or 4 video cards but this is a laptop with only Iintel IGPU

Share this post


Link to post
Share on other sites

Happens on my machine as well. Typically after I open it and switch to another open application.

 

i found something. i always used chrome after boot. it means that chrome always opened.

i have a old chrome version. if open chrome, itunes forced close(crash) randomly. i updated chrome now. and tested many times. seems no issue

 

as result, old chrome causes itunes forced close(crash).

 

sorry for my bad english

Share this post


Link to post
Share on other sites

in GM my EVGA GTX660 SC is recognised correctly and hardware acceleration is working, but after 2-3 minutes on the desktop artefacts starts to appear and disappear on the screens.

Does anyone else see this?

Share this post


Link to post
Share on other sites

in GM my EVGA GTX660 SC is recognised correctly and hardware acceleration is working, but after 2-3 minutes on the desktop artefacts starts to appear and disappear on the screens.

Does anyone else see this?

 

I have had the exact same issue since starting the 10.13 betas. What mother board do you have. I have only found one other person who is experiencing this and by "coincidence" they have the exact same hardware as myself: ASUS Maximus VII Impact with EVGA GTX660. I am also using an old Apple Cinema 30 monitor. At 2560x1600 the artifacts are worse but if I drop down to 2048x1280 or lower they seem to go away.

Share this post


Link to post
Share on other sites

After install High Sierra should I still need NvmExpressDxe-64.efi?

 

Update: I removed NvmExpressDxe-64.efi from CLOVER/drivers64UEFI and nothing change. Everything working without a problem. My High Sierra is fully working.

 

post-803029-0-83291600-1505752323_thumb.pngpost-803029-0-63735700-1505752340_thumb.pngpost-803029-0-76252000-1505752347_thumb.pngpost-803029-0-24762100-1505752353_thumb.pngpost-803029-0-01398100-1505752360_thumb.pngpost-803029-0-23299400-1505752364_thumb.pngpost-803029-0-80778100-1505752369_thumb.pngpost-803029-0-96315600-1505752526_thumb.png

 

 

Share this post


Link to post
Share on other sites

Ok, so, for anyone concerned, upgrading from Sierra to High Sierra, while FileVault enabled, results in an unbootable system. For as far as I could see, the installation files are not copied to the root directory. Also, after reboot, there's nothing to start off the installation (because of the first issue), and the current installation asks for password to unlock the computer (which is normal), but doesn't start loading anything. It just displays the transparent screen with nothing on it. No loading bar, no loading, nothing.

 

The only way I found to fix this, was to decrypt the current partition before upgrading to High Sierra, and encrypt it again afterwards. This way the upgrade works with no issues.

Share this post


Link to post
Share on other sites

in GM my EVGA GTX660 SC is recognised correctly and hardware acceleration is working, but after 2-3 minutes on the desktop artefacts starts to appear and disappear on the screens.

Does anyone else see this?

 

 

I have had the exact same issue since starting the 10.13 betas. What mother board do you have. I have only found one other person who is experiencing this and by "coincidence" they have the exact same hardware as myself: ASUS Maximus VII Impact with EVGA GTX660. I am also using an old Apple Cinema 30 monitor. At 2560x1600 the artifacts are worse but if I drop down to 2048x1280 or lower they seem to go away.

 

I updated my machine to the 10.13 GM a couple of days ago and see the same behavior on my machine.

I assume this to be corrected by NV Web drivers hopefully sooner than later.

Share this post


Link to post
Share on other sites

I updated my machine to the 10.13 GM a couple of days ago and see the same behavior on my machine.

I assume this to be corrected by NV Web drivers hopefully sooner than later.

 

What's your hardware profile, motherboard and graphics? Curious if it's anything related to the EVGA 660 or ASUS Maximus VII Impact BIOS. Is you IGPU disabled? I found that enabling both the HD4600 IGPU and the Nvidia 660 the artifacts are not as bad or as often. I have the IGPU disabled as I experience Safari freeze and reboot. iTunes also crashes with the HD4600 enabled.

Share this post


Link to post
Share on other sites

in GM my EVGA GTX660 SC is recognised correctly and hardware acceleration is working, but after 2-3 minutes on the desktop artefacts starts to appear and disappear on the screens.

Does anyone else see this?

 

My GV-N660WF2-2GD have artefacts still in GM, but it was not happen except for HiDPI mode with SwitchResX.  

Share this post


Link to post
Share on other sites

I have had the exact same issue since starting the 10.13 betas. What mother board do you have. I have only found one other person who is experiencing this and by "coincidence" they have the exact same hardware as myself: ASUS Maximus VII Impact with EVGA GTX660. I am also using an old Apple Cinema 30 monitor. At 2560x1600 the artifacts are worse but if I drop down to 2048x1280 or lower they seem to go away.

 

I have a Gigabyte Z77-DS3H board with two monitors. One is LG IPS277 27-inch (1920 x 1080) and the other Dell P2715Q 27-inch (3840 x 2160). I don't want to have web drivers, I prefer to go with Apple ones as it's just easier to update. No need to wait for Nvidia to update the drivers as well.

 

Anyway I'm going to update my video card with RX 580 Pulse because of the feedback it has in our community. 

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
      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 ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?

      How to make 10.13 installer for MBR (MBR-Automatic-Method)?
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, new for 10.13+.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       


       
    • 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!!!
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
×