Jump to content
Sign in to follow this  
Followers 0
fantomas1

macOS High Sierra 10.13.4 est disponible

11 posts in this topic

Recommended Posts

macos_egpu.jpg

 

Cette mise à jour :

  • Offre désormais la prise en charge des conversations Discussions d’affaires dans Messages aux États-Unis et au Canada
  • Offre également la prise en charge des processeurs graphiques externes (eGPU)
  • Résout un problème de corruption d’éléments graphiques qui affectait certaines apps sur iMac Pro
  • Permet désormais de passer à l’onglet ouvert situé le plus à droite en appuyant sur Commande + 9 dans Safari
  • Permet de trier les signets de Safari par nom ou par URL en effectuant un clic droit et en choisissant « Trier par… »
  • Résout un problème susceptible d’empêcher les aperçus de liens web d’apparaître dans Messages
  • Contribue à la protection des données confidentielles en ne remplissant automatiquement que les noms d’utilisateur et les mots de passe lorsqu’ils sont sélectionnés dans le champ d’un formulaire web dans Safari
  • Affiche des avertissements dans le champ de recherche intelligente de Safari lors d’interactions avec des formulaires requérant des données de carte bancaire ou un mot de passe sur des pages web non chiffrées
  • Affiche des informations supplémentaires décrivant la manière dont vos données personnelles sont utilisées par certaines fonctionnalités

Share this post


Link to post
Share on other sites
Advertisement

Bonjour,

Vous mentionnez prise en charge d'un eGPU?

Mon Xiaomi NotebookAir 13.3 à base de Skylake i5 a une carte graphique NVIDIA 940...

J'ai lu que Optimus, ça ne marchait pas...

@+

 

Share this post


Link to post
Share on other sites

Non, la techno Optimus n'est pas supportée sur Hackintosh. Pourquoi? Parceque Apple utilise sa propre technologie (basée hardware) pour gérer les cas de double GPU. Plus de détails sur recherche Google... Par contre, ça n'exclue pas de pouvoir cependant faire tourner son Hackintosh uniquement sur le dGPU plutôt que l'iGPU. Ca dépend des portables et du raccordement physique des ports vidéo.

 

Mais bon, c'est hors sujet ici et rien à voir avec un eGPU.

Edited by Hervé

Share this post


Link to post
Share on other sites
19 hours ago, bergui45 said:

Bonjour,

Vous mentionnez prise en charge d'un eGPU?

Mon Xiaomi NotebookAir 13.3 à base de Skylake i5 a une carte graphique NVIDIA 940...

J'ai lu que Optimus, ça ne marchait pas...

@+

 

 

iGPU = integrated GPU = processeur graphique intégré = intel HD/Iris/Iris Pro 5xx dans le cas d'un Skylake i5

                                                                                                                                                   }   iGPU + dGPU = Optimus ≠ Hackintosh

dGPU = dedicated GPU = processeur graphique dédié = Nvidia GeForce 9xx MX selon les modèles

 

eGPU = external GPU = processeur graphique externe = la solution qui te permet d'utiliser une carte graphique dite "desktop" dans une configuration dite "laptop".

 

Donc comme te l'a expliqué si bien Hervé, cela n'a rien à voir avec la technologie Optimus  :)  qui a longtemps était réservée aux ordinateurs portables, maintenant réservée aussi aux ordinateurs de bureau, sous le nom Desktop Optimus ou Synergy.   ;)


Utilisation d'un eGPU avec un Mac

 

 

Share this post


Link to post
Share on other sites

Et l'eGPU sur Mac, c'est même parfaitement illustré sur la photo en post #1 de ce fil ! :thumbsup_anim:

 

NB: 1 caramel si tu devines le modèle.

Edited by Hervé

Share this post


Link to post
Share on other sites

Bonjour les frenchies,

 

MERCI pour ces eclaircissements sur le eGPU...

 

Puis-je signaler que j'ai un souci pour redémarrer depuis la Mise à jour de sécurité sur mon Laptop Xiaomi Notebook Air 13.3...

ACPI Error (_DSM) Fake SMCKeystore :started

NameSpace LookUp Failure

AE_ALREADY_EXISTS (20160930/dswload_462)

ACPI Exception : AE_ALREADY_EXISTS, (SSDT.CpuPm) while loading table (20160930/tbxfload-319)

ACPI Error: 1 Table load failures, 10 successful

 

MERCI à celui qui me trouve la SOLUTION...

Share this post


Link to post
Share on other sites

En fait, j'arrive à m'en sortir en installant chaque fois le dernier Clover Configurator sur mon SSD Sandisk 100 gigas en USB à partir de mon MBPro 15"...

Et là BINGO ça Boot nickel!

;-)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
    • By kalpesh2804
      Laptop Inbuilt Wifi and Battery Indicator not working in Catalina. (HP Pavilion 15t-au 100 Laptop)
       
       
      Laptop Config:
      HP Pavilion 15t-au100 * i7-7500u 2.90Ghz * Intel HD 620 Graphic Adapter * Intel Dual Band Wireless AC-3168 * Kingston SATA3 SSD 500 GB * HP Camera
    • 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)
       
    • 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
       
×