Jump to content
ErmaC

Clover General discussion

19,036 posts in this topic

Recommended Posts

Posted (edited)
43 minutes ago, Andres ZeroCross said:

Now i test it again, use Clover r4840.

1. Delete BootChimeDxe.efi di Drivers64Uefi
2. Just use AudioDxe.efi in Drivers64UEFI
4. Set audio device from shell (There is sound when command applied)
5. Put sound wav and sound_night.wav in BGM_SVG folder

There is no sound before GUI CLOVER or in CLOVER (PlayAsync=False).

There is log "not found AudioIo" in preboot log.

Try reset Nvram (F11 in Gui clover), set from shell but no change

Thanks

Sent from my Mi Note 2 using Tapatalk

 

This shows that there is just no audio io protocol installed on any of the devices, did you check to make sure you have nvram variables after configuring and restart?

 

EDIT: Nevermind, it wouldn't have gotten that far if they didn't exist. There should be a line that prints out the device path of the selected device, I bet it is being converted incorrectly so it doesn't match the one clover is using exactly.

EDIT2: Please run this command on your EFI partition and upload the file it generates:

dmpstore -all > nvram.txt

 

Edited by apianti

Share this post


Link to post
Share on other sites
Advertisement
 
This shows that there is just no audio io protocol installed on any of the devices, did you check to make sure you have nvram variables after configuring and restart?
 
EDIT: Nevermind, it wouldn't have gotten that far if they didn't exist. There should be a line that prints out the device path of the selected device, I bet it is being converted incorrectly so it doesn't match the one clover is using exactly.
Sorry, i am not sure how to check it?

Sent from my Mi Note 2 using Tapatalk

Share this post


Link to post
Share on other sites
Posted (edited)

Please run this command on your EFI partition and upload the file it generates:

dmpstore -all > nvram.txt
 
Edited by apianti

Share this post


Link to post
Share on other sites
Posted (edited)

Sorry forgot you need to specify -all or it doesn't dump anything but globals.

dmpstore -all > nvram.txt

 

Edited by apianti

Share this post


Link to post
Share on other sites
23 minutes ago, apianti said:

This shows that there is just no audio io protocol installed on any of the devices, did you check to make sure you have nvram variables after configuring and restart?

 

EDIT: Nevermind, it wouldn't have gotten that far if they didn't exist. There should be a line that prints out the device path of the selected device, I bet it is being converted incorrectly so it doesn't match the one clover is using exactly.

If i use all the files from here, i have to rename sound.wav to sound_night.wav else no sound. but if i make my own sound.wav/sound_night.wav, i got no sound.

 

So maybe @apianti's EDIT: above make sense.

 

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, cecekpawon said:

 

Yeah, that's why I wanted to see the variable value. I imagine he is still using the older version though, which could also have an issue with matching the string.

 

10 minutes ago, ellaosx said:

If i use all the files from here, i have to rename sound.wav to sound_night.wav else no sound. but if i make my own sound.wav/sound_night.wav, i got no sound.

 

So maybe @apianti's EDIT: above make sense.

 

 

These are unrelated problems. For the sound.wav to sound_night.wav, yes that is problem for raster theme as I posted before. For your own sounds, see here:

 

Edited by apianti

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, cecekpawon said:

@apianti BootChimeCfg may caused another problems in the future if you guys not also importing it into Clover, just guessing, since AudioPkg has rapid development and could be hard to resync from time to time _/|\_

 

I agree, it should have been external dependency or entire project imported.

 

EDIT: Windows build is sooooo f u c k i n g broken. I just give up trying to maintain it, it's constantly messed up because no one seems to care about data types. And cbuild.bat is borked from slices changes....

Edited by apianti

Share this post


Link to post
Share on other sites
Posted (edited)

Hmmb, and it seems.. still has stability issue (at least, on my mach). ¯\_(ツ)_/¯

Previously worked fine with a same r4840, also a same *.wav.. but now I hear nothing after mach powered off.

Both sound.wav & sound_night.wav are available on my loaded "Theme Name" dir, though.

Ah, my eyes are sick reading what's "dmpstore -all > nvram.txt" wanna tell?

nvram_dmpstore_all_a43sj.txt.zip

Edited by Badruzeus

Share this post


Link to post
Share on other sites
29 minutes ago, Badruzeus said:

Hmmb, and it seems.. still has stability issue (at least, on my mach). ¯\_(ツ)_/¯

Previously worked fine with a same r4840, also a same *.wav.. but now I hear nothing after mach powered off.

Both sound.wav & sound_night.wav are available on my loaded "Theme Name" dir, though.

Ah, my eyes are sick reading what's "dmpstore -all > nvram.txt" wanna tell?

 

This is device path protocol, so you are using new version which won't produce the string in nvram so incompatible with current clover:

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 50                                               *P*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

Share this post


Link to post
Share on other sites
Posted (edited)
17 minutes ago, apianti said:

This is device path protocol, so you are using new version which won't produce the string in nvram so incompatible with current clover:


Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 50                                               *P*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

 

Yeah, I have 3 diff. AudioDxe & BootChimeCfg depend on their commits on github AudioPkg project.
OK so.. to not make thing complicated, I rolling back using @Slice prebuilt since now. (not sure what has he done to make it becomes "compatible with current Clover" LoL).

Edited by Badruzeus

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, apianti said:

Sorry forgot you need to specify -all or it doesn't dump anything but globals.


dmpstore -all > nvram.txt

 

Sorry,, i have something to do before in real lif. Here is the nvram.txt

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites
[mention=749318]apianti[/mention] BootChimeCfg may caused another problems in the future if you guys not also importing it into Clover, just guessing, since AudioPkg has rapid development and could be hard to resync from time to time _/|\_
I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

Sent from my Mi Note 2 using Tapatalk

2 hours ago, apianti said:

 

Yeah, that's why I wanted to see the variable value. I imagine he is still using the older version though, which could also have an issue with matching the string.

 

 

These are unrelated problems. For the sound.wav to sound_night.wav, yes that is problem for raster theme as I posted before. For your own sounds, see here:

 



It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Badruzeus said:

 

Yeah, I have 3 diff. AudioDxe & BootChimeCfg depend on their commits on github AudioPkg project.
OK so.. to not make thing complicated, I rolling back using @Slice prebuilt since now. (not sure what has he done to make it becomes "compatible with current Clover" LoL).

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

1 hour ago, Andres ZeroCross said:

Sorry,, i have something to do before in real lif.

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string:

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 03 1F 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

50 minutes ago, Andres ZeroCross said:

I hope we can use bootchimedxe.efi too. Sound before apple loading bar is funny for me (like real mac)

It works now,, i use BootChimeCfg.efi and AudioDxe.efi from Slice Prebuilt. So what's wrong?? BootChimeCfg.efi (to generate variable value in nvram) or AudioDxe.efi??

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

Edited by apianti

Share this post


Link to post
Share on other sites
7 minutes ago, apianti said:

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

Share this post


Link to post
Share on other sites
13 minutes ago, ellaosx said:

If we use the newer version of Goldfish, should we use both of his AudioDxe & BootChimeDxe or only the BooChimeDxe?

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.

Share this post


Link to post
Share on other sites
24 minutes ago, apianti said:

 

The previous version of AudioPkg used the device path string, which is not compatible across firmware as each does it differently. This is the one clover currently uses. The newest version uses the device path protocol, which is uniform across firmwares, and what clover should be changed to use. It really only takes reading the variable differently then converting it to a string in the way clover does for every device path protocol, then it will work again with newest. However, it might just be better to remove from clover and have external dependency on AudioPkg instead, since it is better to let Goldfish64 maintain the sound devices then add more to clover that will lag behind.

 

 

No problem, me too. Yeah its same issue, it set device path protocol in nvram instead of string:


Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 64                                               *d*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 03 1F 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

 

Problem is with mismatching versions that do different things. The correct way is to set the device path protocol, so the newest AudioPkg is what should be done. Clover needs fixed to work with it as it uses older device path string method which is not reliable. Just make sure you use the binaries slice provided for now.

 

EDIT: You can use BootChimeDxe.efi if you make sure all the binaries match newest and don't have sound(_night).wav for clover, or are older and have sound(_night).wav.


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

Share this post


Link to post
Share on other sites
Just now, Andres ZeroCross said:


I don't understand about New and old. Can we say The prebuilt AudioDxe.efi and BootChimeCfg.efi from Slice are Older??? And AudioDxe.efi and BootChimeCfg.efi from GoldenFixh are New???

i try boot with AudioDxe.efi and BootChimeCfg.efi from Slice and use BootChimeDxe.efi from Golden fish, sound from Clover theme is loaded and good and chime sound from BootChimeDxe.efi is good too. But i can't enter desktop screen. There is no loading bar progress,,, i should delete bootchimedxe.efi to boot (i delete it from Shell)

 

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

Share this post


Link to post
Share on other sites
4 minutes ago, apianti said:

 

You need to use all three binaries from his newest in that case. Make sure clover does not have a sound(_night).wav present in your theme.


I Read this,, so i can use CLOVER r4840 without editing / commenting some line in Clover file first???? if yes, i can try it right now

Share this post


Link to post
Share on other sites
27 minutes ago, Andres ZeroCross said:


I Read this,, so i can use CLOVER r4840 without editing / commenting some line in Clover file first???? if yes, i can try it right now

in my experience, i needed to edit it regardless if youl use old or new 

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, apianti said:

 

They are both from Goldfish64, it's just there are changes in the source to change the behavior. You need to use the matching binaries from the same version. Read my previous comment.

I used AudioDxe.efiBootChimeDxe.efi and BootChimeCfg.efi from GoldFish64. Just put sound.wav in Theme Folder
So
1. My time is 21.00 here, so it's night.. I reset NVRAM from clover. AFter that set Audio and volume from shell with BootChimeCfg.efi. And boot to desktop and reboot. And when i boot again, i only can hear sound from BootChimeDxe.efi, no sound from Theme Sound (Sound before CLOVER GUI). I generate Preboot.log before boot and i see log about "no sound found". I think this's because my time. so i set my time to 13.15 (day time). And reboot,

2. And i got No sound from Theme Sound (sound before CLOVER GUI),, boot into desktop and i only can hear Chime from BootChimeDXE.efi only. I pressed F2  and get preboot.log  before and i see "no AudioIo".

So, what's wrong??? What should i do to get sound from Theme and sound from BootChimeDxe.efi????

i use Clover r4840.

Edited by Andres ZeroCross

Share this post


Link to post
Share on other sites

It's a pity Goldfish64 changed definition for "device" variables without back compatibility.

See how apple does:

efi-boot-device	<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>33D4733F-CBAF-4B8E-A33E-6EB6244C5BF2</string></dict></dict></dict></array>
efi-boot-device-data	%02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%ff%ff%00%00%04%01*%00%07%00%00%00%c0Y%c3%1e%00%00%00%00%a81l%06%00%00%00%00?s%d43%af%cb%8eK%a3>n%b6$L[%f2%02%02%7f%ff%04%00

Same but different representation.

 

I will propose to create own audio configurator as Clover already knows all audio devices. Just give user a choice for output number and volume.

Also I can think about digital sound and about Speaker/Headphone autoswitch absent in original driver by Goldfish64.

Just take a time.

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By SepehrM
      I'm trying to install High Sierra 10.13.3 on an ASUS N552VW laptop, and I get stuck after this message:
      "could not recover SATA HDD after 5 attempts, terminating" 
      And some other warnings afterwards.
      Specs:
      CPU: Intel Skylake 6700HQ 2.6GHz
      RAM: 16GB DDR4
      2TB HDD + 128GB SSD
      GPU: Intel HD Graphics 530 + Nvidia GTX960m
      I'm installing using a 16GB USB3 flash drive on one of HDD volumes (UEFI Mode)
       
      I uploaded the verbose log and clover config.plist
      config-new.plist

    • By Reel
      All work except camera
      You need SwitchResX that the screen does not freeze
         


    • By RougeOne
      Budget Workstation MacOS 10.14.1 build: z370 AORUS Gaming 5 - i5-8600K - RX 580 - UHD 630
      flawless iGPU/dGPU integration, fast FCPX editing/rendering, great overall performance for ~$1200 / ~£1000
       
      Update: updated WhateverGreen and Lilu, then updated OS to 10.14.3 and everything is fine! Even iMessage, which previously I hadn't been able to make work, is now working - possibly the update flushed the NVRAM?
       
      I'm gonna come straight out and admit it - I used newb tools which are considered taboo on InsanelyMac, and so this isn't so much an installation guide as it is a green flag to anyone considering the same hardware. My first and previous Hackintosh project was just over ten years ago and this site was massively helpful, so this is my (very small) way of giving back.
       
      EFI DIRECTORY
      http://s000.tinyupload.com/index.php?file_id=97606131925137056003
       
      HARDWARE
      CPU: Intel i5-8600K 3.6GHz hexacore (contains UHD 630 iGPU)
      CPU Cooler: be quiet! Pure Rock Slim (no paste needed, and fan facing front)
      Mobo: GIGABYTE z370 AORUS Gaming 5 (WIFI)
      RAM: 1x 8GB CORSAIR Vengeance LPX C16 2666MHz (in first slot)
      GFX Card: Sapphire RX 580 NITRO+ SE
      SATA: used ports 0, 1, 3, 5 (HDD problems when connected to port 4)
      HDD: generic
      DVD Drive: generic
      PSU: EVGA 500W Semi Modular (but you should get 650W!)
      Case: CoolerMaster CM590 III
      Fans: 2x stock case fans (one sucky on front, one blowy on back), 3x be quiet! BL046 120mm fans (two blowy on top, one sucky on front). Airflow near-perfectly balanced.
       
      ADVICE
      With the Clover configuration, you want to pay close attention to all things relating to graphics. There are some specific settings for ACPI, Boot, Devices and Graphics which should be copied exactly in order to get the iGPU and dGPU to work in perfect harmony. For instance, make sure you use ig-platform-id 59120003 rather than 59120000 if you want FCPX to be usable. With the right settings, FCPX will not only run, but run flawlessly.
       
      I was not able to figure out how to make NVRAM/PRAM behave itself, and I got errors when I tried to issue relevant commands. As a result, I could not at first get iMessage to work properly. It worked once on my first installation attempt but not from subsequent attempts. This Clover configuration therefore has no consideration whatsoever toward iMessage reliability - however, iMessage ended up working somehow, anyway - I noticed it after I'd updated to 10.14.3 but this may just have been coincidence.
       
      Onboard WiFi does not work. There is no driver for it. I'm using wired ethernet to a bridge router as it was cheaper than getting a compatible PCI card.
       
      Audio is working well after I installed the z370 audio patch, then the ALC1220 codecs, then AppleALC.
       
      With kexts for generic 3rd party SATA and generic 3rd party eSATA, my HDDs and DVD drive work perfectly well.
       
      Sleep/Wake functions run perfectly. iCloud functions run perfectly. Shutdown leaves the mobo LEDs on, annoyingly.
       
      My USB 3 ports seem to suffer from low power output, and I don't know why.
       
      Overall, this system appears to run about as well under MacOS 10.14 Mojave as it does under Windows 7. I would solidly recommend this build to anyone looking to build a computer for workstation purposes, on a budget.
    • By JhonneR
      Good morning, everyone, I'm sorry if I was wrong in choosing the topic but I need help.
      I have found it extremely difficult to mount a Hackintosh in my acer.
      Setup;
      I5 2430m 2.4 6GB RAM
      Mobo P5we0 - Intel intel Graphics 3000
      At the moment I have not found out what my audio codecs are.
      but I'll leave the link on the motherboard.
      however, my real problem is several.
      I have already used the itakos image, I have already used several images that could be installed normally and that after installing the image I do not have internet via cable or wireless.
      And another, I already looked in other forums and I know that I will be called a donkey in the logical question but I have not been able to install the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or clover to start from the Hard Disk, so I do not know what to do.At the moment I still do not know if there has already been someone who has already installed the High Sierra or just the Sierra in this notebook model and obtained permanent success.
      If anyone can help me, I'll be grateful.
      Installations without success, but with the system already installed in ACER;
      SIERRA
      HIGH SIERRA
      MOJAVE
      All with the same symptom. Starting only by the bootable USB stick and without internet connection via cable and wireless.
      Appreciate ! Acer 5750 Official Page
×