Jump to content

oSxFr33k

Members
  • Content Count

    1,129
  • Joined

  • Last visited

Everything posted by oSxFr33k

  1. oSxFr33k

    Clover General discussion

    So explain what I need to do to fix this, run clover as usual choosing the boot0af or boot0ss option, which one? After clover install reboot then run the dd command after clover is installed and which one will I install with the dd command? Can you reply with the complete dd command here please or a link to the procedure. I remember now some bug for legacy bios in some clover legacy installs, requiring the dd command to be run and only the one command not both as Badruzeus had replied with? Thanks!
  2. oSxFr33k

    Clover General discussion

    It just stops booting at that point nothing wrong with USB because the other drive has Catalina on it and it boots just fine. I also have a second Catalina installed onto 2nd volume of first container and first volume of 2nd container. I have to try this instead I have been using boot0af forever with legacy bios, never tried boot0ss, and maybe now with new APFS need boot0ss?. Are you using the legacy only clover installer or the latest clover package that allows for legacy settings? During clover install you chose boot0ss then reboot then in terminal ran dd command? What if I have a second container what would the command be for that, just change to "&& to boot1s1' for example? Is there a new thread going on about this with new APFS and legacy boot would like to get more information on it. Thanks!
  3. oSxFr33k

    Clover General discussion

    Ran into two problems for legacy bios (non EFi). After creating a second volume inside the same APFS container and installing Catalina it won’t boot, clover installed in EFI. The first volume is Mojave no issues. Is it possible clover in EFI won’t boot 2nd 3rd etc volumes in same container? I should say it starts to boot but its never able to complete the boot process. I see from verbose boot it stops in my case at the IOUSBHost Interface and the last thing I see before the screen text becomes frozen and shattered with the prohibited sign is the message ‘still waiting for root device’. I have to assume that the kexts in the EFI partition are not being read? The second problem is when I partition the single hard drive which creates two containers and install Catalina into the 2nd container’s volume, it only goes through the initial first part of the install process after which a reboot there is no second phase to install to MacOS from clover GUI even though the data install folder does exist with the correct size and files inside the 2nd container’s volume. i just now tried this on a SSD with legacy bios same results so it’s not related to the hard drive versus SSD. Is there something more I need to do to have multiple MacOS Installs on the same APFS Hard Drive non SSD? I have not tried this on a modem EFI bios machine just legacy. Should there only be one EFI partition even after you partition the drive into multiple containers? Has anyone tried this on their legacy bios machines getting the same results as me? Edited: This is definitely related to legacy bios I tried the same hard drive in an EFI bios machine no problems booting either volume from the same container, and was able to complete the install if the volume was on the 2nd container. Maybe only related to this motherboard GA-G41M-ES2L? Edited Again: I can confirm with another legacy bios machine some issue between the Bios and more current clover revisions from r5093 through r5097 is what I tested so far.
  4. oSxFr33k

    WhatEverGreen Support Topic

    @Sherlocks Hi I have read many of your posts in the Clover General thread with many useful fixes I have used over time thanks for all that. I Posted a few back from here link below about how to eliminate AppleBackLightFixup for Nvidia Only Laptop, no intel integrated GFX, Asus has disabled it on this G750JX laptop. I would like to use WEG alone and eliminate the fixup kext but from Yosemite and all the way into Catalina I have to use it to actually see the LCD backlight change intensity without it only the Apple Backlight Automation inc/dec will work without Brightness change. Any suggestions on how to make this work or di I have to continue to use the Fixup kext in my situation?
  5. oSxFr33k

    VoodooHDA 2.9.2

    Ah ok I see iMix and PCM set to 90 I should have known better, thanks!
  6. oSxFr33k

    [pre-release] macOS Catalina

    Did you install fresh or over your current install? Every time I install over the previous version things go wrong for me something to do with the Data volume, I think I am suppose to boot to that after the initial somewhat short install it boots to install but its the Data Volume, I am guessing that is where the image is initially placed so when I continue from there it seems to complete the second portion reboots but wants to install again from the Data volume where the image was placed so my install keeps looping over and over. Do I need to remove the Data Volume before proceeding with the install? Is the Beta/Developers preview version in the version.plist?
  7. oSxFr33k

    VoodooHDA 2.9.2

    Is there an alternate way to save the settings for me just the PCM and iMix volume sliders. Thanks!
  8. oSxFr33k

    [pre-release] macOS Catalina

    MY problem solved with LCD brightness. WEG alone does not take care of this for Laptops that have only Nvidia GTX and Intel integrated graphics disabled. We still need AppleBacklightFixup and WEG alone does not work. We still need WEG obviously, but whatever code is in ABF needs to be included in WEG for future releases for NVIDIA support. I was able to get ABF to work again with a bootflag to run on unsupported software such as Beta Catalina so once the final version of Catalina is released it will work without this flag "-applbkldbg' hopefully. We need future release versions of WEG to support exactly what ABF does for Nvidia GFX, and not just Intel.
  9. oSxFr33k

    WhatEverGreen Support Topic

    Possibly help with LCD Brightness on Asus G750JX Laptop everything working fine in Mojave now broken in Catalina. The Apple Display Animation Increment/decrement is working fine just no change in brightness. I posted this in the Beta Catalina thread but no one was able to help just comment that AppleBacklightFixup.kext was depreciated and now taken over by WEG and that it was meant to work for Intel only. Since my Asus has Intel built in GFX disabled by Asus by default I have been able to have LCD brightness work on my Dedicated and Natively supported Nvidia GTX770m, since MacOS Yosemite and all the way up to and including Mojave. Is there some boot option needed to re-enable LCD brightness in Catalina? I have included files to see if we can figure out where the issue may be. Thanks! Edited: Sorry forgot to mention that I need AppleBacklightFixup.kext in Mojave to make LCD brightness work even with WEG. So it sounds like the issue is with AppleBAcklightFixup.kext not compatible with MacOS Catalina. If WEG has taken over the other brightness fix kexts and injectors is there a way to incorporate it for Nvidia Natively supported GFX cards so we can get LCD brightness back in MacOS Catalina? Edited the last time: Problem solved sorry about all the noise above. It won't work in MacOS beta software so there is a bootflag to make it work '-applbklbeta'. But for the future just want to make sure the Nvidia Laptops that depend on this for backlight will still be supported maybe future releases in WEG without ABF? Edited Again 10-4-2019 Added Send me files for working backlight with AppleBAcklightFIxup if it helps to figure out how to get this to work without tha kext? Send me osxfr33ks-MBP.zip Send me osxfr33ks-MBP._working_Backlight_with_Fxiup_Kext.zip
  10. oSxFr33k

    [pre-release] macOS Catalina

    Actually since my GFX is discrete only and Asus has disabled IGPU I can change GFX0 to IGPU in a SSDT and it works as it would for IGPU all the way up to Mojave. So what happened in Catalina to break this or has WEG broken it? All I use is a SSDT for GFX see attached. So the Nvidia card takes the place of the IPGU since its disabled by Asus. Because I have separate SSDT I still need to use Rename in Clover GFX0 to IGPU and not sure why but also still need AppleBAcklightFixup.kext. Need WEG to prevent dark screen on boot. Is there something I need to modify to work in Catalina? SSDT-HDMI-NVIDIA-P0P2.aml.zip
  11. oSxFr33k

    [pre-release] macOS Catalina

    AppleBacklightFixup.kext not working in Catalina any possible fix? My LCD brightness has worked all the way up to and including Mojave now broken in Catalina. The device is in my description signature below, Asus G750JX Intel integrated graphics disabled by ASus only discrete Nvidia GTX770M enabled working natively. PNLF working fine, I have the apple brightness animation increment/decrement but the display does not change brightness.
  12. How are you @MaLd0n, does your patcher work similar to DosDude's Mojave and Catalina patcher for legacy Audio? I can't seem to get AppleALC working after using DosDude's Legacy Audio patcher. I have to assume it replaces Mojave's AppleHDA with one that is more compatible for the legacy which might break AppleALC or not? This is for a Gigabyte Motherboard, chipset G41, GA-G41M-ES2l v1.4. You created the DSDT many years ago for me and it is working perfectly all the way through High Sierra. DSDT HDEF layout is 0x01 I tried 02 not working either. Very very slow boot with AppleALC. Working fine with VoodooHDA but much prefer AppleALC.
  13. oSxFr33k

    [pre-release] macOS Mojave 10.14.5

    Do you still get acceleration with this patch for GT210?
  14. oSxFr33k

    macOS Mojave 10.14.4 is out

    In Bios under CPU, disable Internal PLL overvolt, that fixed mine a few years ago under MacOS El Capitan never tried the setting again in Hi Sierra or Mojave after I updated the Bios. https://hardforum.com/threads/official-asus-response-to-resume-hibernate-problem-with-internal-pll-voltage-enabled.1579942/#post-1036767351
  15. oSxFr33k

    Clover General discussion

    It supports speed step for Server processor Xeon E5-2697v2 12 core ivy processor? I tried plugintype=true and no speed step. It’s stuck at 1.2ghz. I found this quote from another thread for X79 motherboards for controlled speedstep, but that is back from 2014 so Clover has made a lot of changes since then, clover did not have this plugintype option and now does but does it have the values for this specific processor to make speedstep work? we need a extra power state at least 1MHz above our max power state and a extra power state at least 1MHz below our lowest reachable power state. Without these extra states we would never fully reach the lowest or highest state. The "-w 3" in the command below creates the extra states above and below max and min. ssdtPRGen.sh -c 1 -w 3 -turbo 3500
  16. oSxFr33k

    Clover General discussion

    It may support it but it Clover's PluginType 1 does not support the speed step without providing a SSDTgen for Ivy Brdige E5-2697v2. I have to generate SSDT with ssdtPRGen.sh -c 1 -w 3 -turbo 3500. Thats why I asked if maybe there was a unique plugintype provided by Clover for the E5 ivy bridge or some additional settings with PluginType=yes, in order to skip having a SSDT. Speed step doesn't work with Clover PluginType have to use SSDT.
  17. oSxFr33k

    Clover General discussion

    Couple question and my apologies if this was already asked. Does the latest version of clover support plugintype for i9-9900K or do I have to supply a SSDT generated file, not even sure if SSDTgen will export a proper file for this processor. Same question for the E5-2697 v2 ivy bridge processor it seems plugintype 1 didn't work, no speed step so I just re-enabled the SSDT to get speed step working again, unless there is another plugin type I need to choose for either one of these processors? Thanks! Edited: Nevermind I found the answer in another thread the i9-9900k is supported with plugintype=yes, no SSDT needed, however the x79 boards with E5 processors does not support plugintype need to use SSDT unless the new clover versions will support the E5 or not?
  18. @fusion71au Is our 8600M GPU supported in Mojave? I don't think its a metal supported GPU, do you still get acceleration in 10.14.1?
  19. oSxFr33k

    VirtualSMC — SMC Emulator

    So I would need Drivers64EFI folder or Drivers64 folder with VirtualSMC.efi inside if I use FV2 in Legacy Bios?
  20. oSxFr33k

    VirtualSMC — SMC Emulator

    From what I read this will work down to Penryn but will it work if on non UEFI Bios (Legacy Bios) any reasons it may not work? I am not using FileVault2 but if I were to decide to use it for Legacy Bios, isn't VirtualSMC.efi meant for UEFI bios only, unless FileVault2 is not meant to use only on Legacy Bios then it won't matter. I answered my own question works great on Legacy Bios for Notebook Asus G51JX i7-720QM, updated processor to i7-940XM smbios MacBookPro6,2. Unsure about the second part of my question regarding FIleVault2 and VirtualSMC.efi for Legacy Bios.
  21. I have two identical laptops one I did the mod and the other have not. I don't see any difference, and the difference is reinstall of Mojave from recovery correct? I can start the installer from recovery on both laptops but have not gone any further than that. So the one laptop I have not changed with this guide will fail to continue to reinstall or fail at some point of the install?
  22. oSxFr33k

    AppleALC — dynamic AppleHDA patching

    High Sierra: Layout 11 ( 0x0b) no audio Layout 13, 28 and 56 audio works fine headphones with auto switching but still distorted for me. One of those layouts in Mojave has no audio either. I know that 0x38 layout 56 no auto switching with headphones, no output for headphones, same with layout 13 in Mojave, so in Mojave for me the best is layout 11. I'll have to figure out why my headphone is distorted later must be something specific with my audio jack or my audio card. Just checked again in Mojave again, layout 13 no headphone shows up but when . plugged in I have a continuous output noise while internal speakers still activated and working fine. But layout 11 and 28 I have auto detect headphone and I think I am sticking with layout 28 (0x1C) for a while. Sorry Layout 28 seems to just show both speaker and headphone and I have to manually switch between them in Mojave so going back to layout 11.
  23. oSxFr33k

    AppleALC — dynamic AppleHDA patching

    Only layout 11 (0x0B) works for me otherwise headphone does not show up with layout 13 and for layout 28 and 56 headphone does not show up when plugged in. A lot of distortion from the headphone jack for me but must be something with my jack or Mojave because I have the same distortion with VoodooHDA.
  24. @fusion71au Thanks for that procedure and posting the attachment. I have a question for you about this ACPI error "AE Already Exists" also seen before in some of my Desktops, using your latest Clover files and kexts for XPM M1530 linked a page or so back. Kernel log using this terminal script: log show --predicate "processID == 0" --start 2018-08-06 --debug 2018-08-06 16:02:23.600167-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.600169-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.600318-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.600319-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.600964-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.600965-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.606295-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.606297-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.606445-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF8017CD6B10 0002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624) 2018-08-06 16:02:23.606447-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF8017CD6B10 0002C8 (v01 PmRef Cpu0Ist 00003000 INTL 20050624) 2018-08-06 16:02:23.608232-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.608233-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.614391-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.614393-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.614705-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_PPC] 2018-08-06 16:02:23.614706-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_PPC] 2018-08-06 16:02:23.614865-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.614867-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.615975-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.615976-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.622018-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.622020-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.622926-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.622927-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.623580-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.623581-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.630094-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.630096-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.630253-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.630254-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.630843-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.630844-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.636880-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.636882-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.637049-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF801568AD90 0005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624) 2018-08-06 16:02:23.637051-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF801568AD90 0005E5 (v01 PmRef Cpu0Cst 00003001 INTL 20050624) 2018-08-06 16:02:23.639024-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.639025-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.645077-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.645079-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.645397-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_CST] 2018-08-06 16:02:23.645398-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_CST] 2018-08-06 16:02:23.645568-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.645569-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.646657-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.646658-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.653237-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.653239-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.654120-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.654122-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.654812-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.654813-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.662559-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.662561-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.662707-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.662708-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.663264-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.663265-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.669345-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.669346-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.669499-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF8017C10850 0000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624) 2018-08-06 16:02:23.669500-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) SSDT 0xFFFFFF8017C10850 0000C4 (v01 PmRef Cpu1Ist 00003000 INTL 20050624) 2018-08-06 16:02:23.671336-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.671337-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) 2018-08-06 16:02:23.677591-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.677592-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error: 2018-08-06 16:02:23.677889-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_PPC] 2018-08-06 16:02:23.677890-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) [_PPC] 2018-08-06 16:02:23.678051-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.678053-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS 2018-08-06 16:02:23.679194-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.679195-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/dswload-462) 2018-08-06 16:02:23.686292-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.686294-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS, 2018-08-06 16:02:23.687196-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.687198-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) During name lookup/catalog 2018-08-06 16:02:23.687852-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.687853-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psobject-310) 2018-08-06 16:02:23.695352-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.695354-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: 2018-08-06 16:02:23.695517-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: 2018-08-06 16:02:23.695520-0500 0x221 Default 0x0 0 0 kernel: (AppleACPIPlatform) Dynamic OEM Table Load: Thanks you answered above!
  25. My config on usb flash drive and SSD drive has those rt variables set. So a reinstall of v4630 still does not set bootsectors correctly with 0x28 and 0x67 set unless it does work on Mojave and not HS?
×