Jump to content

Ploddles

Members
  • Posts

    389
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ploddles

  1. Thanks for taking a look. I have removed the Slide value now I have tested it and found it didn't change anything. I followed your method on page 7 to obtain and calculate the Whitelist, it is only the last 3 or 4 values that are different from everybody else's and following the recommendations earlier I have enabled them all except the last 4. Next thing to try is to remove all the USB devices, except the keyboard and mouse, to see if they affect Sleep. When I put it to sleep, the keyboard, mouse and monitors turn off and then the MB clicks and the BIOS output LEDs start to count up. The mouse, keyboard and monitor do not turn back on and the BIOS codes stop at 30. On a normal start/restart it counts up to AA. There is nothing in the manual about what '30' indicates and a google search wasn't fruitful.
  2. I finally had a chance to test the MMIOWhitelisting, disabling the last 3/4 entries but enabling all the others. There was no difference between disabling the last 3 or 4 and the system booted fine. Shutdown and restart still work as previous. Sleep still does not work. I also calculate my Slide value, which worked out as 80, but again, this doesn't seem to affect anything. I cannot boot at all with Above 4G enabled and the debug version of OC does not show any MMIO values in the report. Attached is my DSDT file to add to the collection - Gigabyte AORUS Xtreme. DSDT.aml.zip
  3. To rub salt into the wound, currently the new Nvidia cards will only achieve their full potential on AMD motherboards, as they require PCIe 4 for that. No Intel boards currently have PCIe 4 until Tiger Lake CPUs are released. The 490Z may support PCIe 4 but with only a CPU change so that is an ouch for anybody who currently has a 10 series CPU as they will have a spare CPU to move on to somebody.
  4. If I remember correctly, it was all to do with Metal. Nvidia said they wouldn't support it and wanted Apple to stick with OPenGL. AMD ceased the opportunity to try to hammer Nvidia and said they would support Metal. It may be more complex than that but that is it put simply.
  5. @Pavo @fabiosun I have too many versions of OC downloaded, I could have used the wrong one by mistake. To make sure I have the right one I will download a fresh copy from Github and test again. I think I will delete all my old versions so that I have nice clean copies of release and debug and make sure I don't mix them up by mistake. I don't think I will have time tonight but will upload any useful text files I get. Thank you for your patience.
  6. Hi @fabiosun, Although my system is running well now, apart from sleep, I am happy to do tests when I can. As you say, it can advance all our knowledge by seeing what does and does not work. I tried with all the various setting of Above 4G but none of them let me successfully boot into Catalina or Big Sur. Checking the debug txts they never get to the stage of saving the MMIO info so it is not possible to create a Whitelist. Attached are a series of the text files saved to the EFI when trying to boot. I don't know if they are useful at all but maybe you will see something useful in them. Archive.zip
  7. @tsongz, which kext, there are a few flying about with varying results? I previously tries a couple on my Z390 with dubious results.
  8. @Jaidy, My EFI and BIOS files are on page 22. Copy the BIOS file onto a USB drive and plug that in before you turn the machine on. Go to the last tab in BIOS where you save and exit. Select the Load settings option and you can then load the file from the USB drive. This overwrites your current settings so make sure you have saved your settings first. After loading the file save and exit. @fabiosun, do you know if removing the boot argument and enabling above 4G Encoding change the MMIO values we use in the Whitelist? If so, do you want me to disable the Whitelist or go through the process of replacing them with new values?
  9. @meina222, very strange as I am not sure what has changed that could possibly affect sleep but it was working earlier this week. After doing the sound tests for @fabiosun I checked sleep again. In Catalina, the monitors, keyboard and mouse turn off but the fans are still running. but I cannot now get it to come back on. In BigSur, the same happens but I hear a click after the monitors, keyboard and mouse turn off but the fans are still running. Cannot get it to turn back on. There is another test I want to do but the F1 Racing is now on............ 🙂
  10. @fabiosun, as promised, I disabled the AppleACL.kext and removed alcid in boot arguments. I then cleared NVRAM. The system was shut down and turned off before each test. Below are the results of my sound tests:-
  11. @meina222 Sorry I didn't credit you earlier on the 'wake on lan' setting. By the time I had caught up reading all the posts, I couldn't remember or see again when skimming through who had mentioned it. Credit where credit is due, I would never have thought of that as a possible reason for the shutdown issue. Kudos to you 🙂
  12. Sorry I didn't say, it was the L port that I plugged my headphones into. Later today I will disable AppleALC.kext and remove the alcid parameter and test again. @rressl, Please find below my BIOS/Uefi setting file. Ploddles.zip
  13. @fabiosun Eureeka!! The bottom 2 port on the MB are controlled by the ASMedia Controller. I have an NVMe in the M2C socket which disables ports on the controller. I remember now when I first connected the SATA drives I tried them in the bottom 2 ports thinking these were SATA0 & SATA1 which are the only 2 that will work on the main controller if I have something in M2C. It is the other way round though, 0 & 1 are at the top, silly me. Swapped them over and all is OK. Thanks for the spot. I have now also fixed the shutdown issue and Shutdown now does a proper shutdown and turns off, no reboot. The fix for this was a BIOS setting, turning off "Wake on Lan". @Jaidyplease note this fix for our MB. Now for the interesting bits about the sound. I get different results in Catalina and Big Sur. Gigabyte boards work best (from my experience with Z370 & Z390 boards) with ALCID=11 or ALCID=16. Below, where I have put "Yes" then Realtec appears in the sound output and works with headphones plugged in. Where I have put "Nothing plugged in - Yes" then it still appears as an option you can select. In summary, use ALCID=16 for Big Sur but ALCID=11 for Catalina. Please also note there is no Green output on the Xtreme as you can connect things differently (see pictures below) ALCID=16 Catalina Front case port - Yes Rear Panel port - No Nothing Plugged in - No Big Sur Front case port - Yes Rear Panel port - Yes Nothing Plugged in - Yes ALCID=11 Catalina Front case port - Yes Rear Panel port - Yes Nothing plugged in - Yes Big Sur Front case port - Yes Rear Panel port - No Nothing plugged in - No
  14. Well spotted 😀. The board has 2 SATA controllers, if I remember correctly now you mention it - I'll check later. I'll have to check which SATA ports are available on the other controller, as some are disabled as they share lanes with the M2 slots.
  15. I have 2 SATA drives connected. 1, a 256GB SSD, is formatted as APFS. The other is a 3TB spinner with 3 partitions. 1TB exFat, 1TB APFS and 1TB NTFS. Neither show up in Disk Utility, gui nor from Terminal.
  16. @fabiosun This is the exact EFI (original from @iGPU with a few changes, eg my own Whitelist) I used for a fresh install of Big Sur and what boots Catalina as well. I haven't tried reinstalling Catalina. No need to clear NVRAM between different OS's boots. NVRAM works, Sleep works, Restart works, Shutdown does the usual startup after shutting down. The only issue I currently have is that SATA drives are not showing, M2 drives show fine - they (3) are all NVMe but I would guess if they were M2 SSDs that they would be OK. Later today I will connect some headphones into the green audio jack and test as your have asked. I don't have speakers as such (I use a USB sound bar) but headphones should be the same. When you say "see your Realtek 2.0 device " do you mean as an option in Preferences | Sound | Output?
  17. @fabiosun, Attached is my EFI for your info. @rressl, try this. Just put your serial numbers etc in and you will need to add the pikera boot argument as you have a different dGPU. If you want, later today I can save my BIOS settings profile to a file that you can upload to yours to try, just let me know if you want it. EFI.zip
  18. @rressl, the network kext you need for your MB is attached. I have the same MB as you. @fabiosun FYI. SmallTreeIntel8259x.kext.zip
  19. On my MB, the Gigabyte Aorus Xtreme, it was just a case of dong the MMIO Whitelisting and using the NVRAM SSDT. Since doing the Whitelisting I have had no problems with crashes, freezing etc. My only problem at the moment is the lack of any SATA drives showing up and being accessible. They show up in Windows and at the OC picker (one of them has an old CCC bootable backup on it and presents as an option to load at the picker stage) but disappear as soon as macOS starts up. If I select the CCC clone it starts to load but crashes out - I'm guessing because it disappears as the SATA drives disappear.
  20. Happy to report that I managed to install BS onto an NVMe thanks to @iGPU's EFI. No issues with it at all at the moment. The only remaining problem I have is the lack of any SATA drives once Catalina or BS load up. I can see them at the Opencore Picker and within Windows and Mint, so it is restricted to macOS. As I have pretty much no idea when it comes to SSDTs, I'm guessing the problem, and solution, will be in there somewhere. Attached is my IOREG if anyone can point me in the right direction. Thanks. Ploddles IOREG.ioreg.zip
  21. I've just reattached 2 SATA disks, a 3TB spinner that I used as a backup of my files and also as a CCC of the system, and a 256GB SSD that I want to try BigSur on. In Windows they show up fine and the CCC backup on the spinner appears in the OpenCore picker, so OpenCore can see the disks at that stage. When I boot into Catalina, both SATA drives completely disappear. Disk Utility can't see them and in Terminal diskutil list does not show them either. I'm assuming this is either a SSDT problem, or I'm missing a rename somewhere in my config.plist. To check it wasn't something just in Catalina, I started the BigSur installation but couldn't see the SATA drives in there to choose as an installation point. Time to do some checking to see where the problem is 🙂 and then give a BigSur installation a try.
  22. Have you changed the config.plist to include your MMIO Whitelist? The same was happening to mine until I went through the process. Now it Restarts without any issue and NVRAM is working fine. On Shutdown though I still get reboot. I also had to change the Debug bits in the config file, leaving it as enabled etc it would take up to 5 minutes before it would fully boot into Catalina after selecting that from the picker. One other change I made was to the ScanPolicy, changing it back to 0, the reason being leaving it at 19596035 resulted in me not seeing the Windows NVMe - as I dual boot Windows it was the quickest way to get that back into the picker rather than hitting F12 to be able to choose that to boot from.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.