Jump to content

Pene

Coders
  • Content Count

    224
  • Joined

  • Last visited

  • Days Won

    2

Pene last won the day on October 24 2019

Pene had the most liked content!

About Pene

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

5,162 profile views
  1. Pene

    Clover General discussion

    Exactly.
  2. Pene

    Clover General discussion

    Just like what Slice posted earlier, I also had a PRRE device which included (among others) An address base of 0xFE000000 and Address Length of 0x00020000. I didn't disable it though, and just added the suggested SSDT-PMC.dsl, and it still worked without any problem. Does it at all matter though? (Is the PNP Motherboard Resources device taken into consideration at all by OSX?) What may be worth mentioning, is that on my Z390 (and actually on all other DSDTs I looked at), the PRRE device specifies for this address base a length of 0x20000 while the suggested SSDT-PMC specifies it with a length of 0x10000. Another thing which may be worth mentioning, is that I looked also on a Z370 (which does not have the nvram problem at all), and the whole the PRRE device is identical between the Z370 and the Z390.
  3. Pene

    Clover General discussion

    I guess it wasn't clear from my post that the reservation mentioned was taken from the newly added SSDT-PMC.dsl. Or I didn't get what you mean.
  4. Pene

    Clover General discussion

    Yes, I confirm it is working. OsxAptioFix3 without SSDT-PMC - native nvram not working (tested now again, just to be sure). OsxAptioFix3 with SSDT-PMC - native nvram working. (Probably the same also with AptioMemoryFix and OcQuirks - didn't test though). Didn't have to do any modifications. I have an Asrock Z390 Phantom ITX/AC, and at my memory map (posted some time ago), you see I have this: Type Start End # Pages Attributes MMIO 00000000FE000000-00000000FE010FFF 0000000000000011 8000000000000001 Edit: which is actually 1 page more (?) than what's specified at the PMCR device in the newly added SSDT-PMC: Memory32Fixed (ReadWrite, 0xFE000000, // Address Base 0x00010000, // Address Length )
  5. Pene

    Clover General discussion

    Hi Slice, no, not yet. I was away for a few days. Will probably test today evening and report.
  6. Pene

    Clover General discussion

    Any update about this?
  7. Pene

    Clover General discussion

    As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix?
  8. Pene

    Clover General discussion

    Hey apianti Long time no see. Well, apparently Apple is using it too: look here (at "But there is more") - but that's about all I found about it. The thing is I don't physically have access to that computer, so I will ask for ACPI dumps too see, but will take some time.
  9. Pene

    Clover General discussion

    Following the problem I reported in my post some time ago with a specific pair of DIMMs when trying to install macOS that stops with the error "An error occurred validating the installer data. The download is either damaged or incomplete. Redownload the installer and try again.": We followed Sherlock's idea of manually setting the info for memory, but problem continues. The error is still displayed with the problematic pair, and works with the pair that worked, so basically nothing changed in behavior. But, the strange this, is that now with memory info manually set, the ONLY difference between the SMBIOS of the two cases is in table 219: With pair that is working: Handle 0x0026, DMI type 219, 81 bytes Header and Data: DB 51 26 00 01 03 01 45 02 00 90 06 03 00 60 20 00 00 00 04 40 08 00 00 00 00 00 00 00 00 40 02 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 03 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Strings: 4D 45 49 31 00 "MEI1" 4D 45 49 32 00 "MEI2" 4D 45 49 33 00 "MEI3" And the pair that is not working gives: Handle 0x0026, DMI type 219, 81 bytes Header and Data: DB 51 26 00 01 03 01 45 02 00 90 06 03 00 66 20 00 00 00 04 40 08 00 00 00 00 00 00 00 00 40 02 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 03 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Strings: 4D 45 49 31 00 "MEI1" 4D 45 49 32 00 "MEI2" 4D 45 49 33 00 "MEI3" (difference is in end of first line "Header and Data", 60 20 vs 66 20) Any idea what is this table 219 and if it could be related to the problem?
  10. Pene

    Clover Problems and Solutions

    edk2-stable201911 is released. What do you think, maybe update? As we are using an intermediate release due to the autogen bug.
  11. Pene

    Clover General discussion

    The feature is meant to be used for injecting properties depending on which card is the monitor connected to when system boots up. It checks which card has the GOP active (that will be the card where you see the POST output), and allows you to inject properties judging by that. For example, if you want to always disable the card which was not active when booting, you can inject to SecondaryGPU. As in your case you always want to disable a specific card, it is better to inject directly to it, as you are already doing.
  12. Pene

    Clover General discussion

    So it must not be (olny) it. But it would be good if we got to the bottom of this.
  13. Pene

    Clover General discussion

    The dimm where install fails is a rank1 8gb x2 chips each (Corsair, total 16gb) Install was ok with rank 2 8gb x2 chips (Gskill, total 16gb) And also was ok on with rank 2 16gb x2 chips (Corsair, total 32gb) That's why I thought it is probably related to rank, as there was no other major difference between the chips where it worked and failed. Same size also as you see. He was using iMac19,2 model.
  14. Pene

    Clover General discussion

    Hi Slice, Thanks. Meanwhile. he tested with changed Rank (Attributes=2, before your latest changes) but unfortunately there was no change, install still failed. So changing this in smbios didn't really help He said he will send me the memory chips so that I can make more investigations. But it will take a while till he sends them. What is your memory rank in dmidecode -t 17? Also, your error is the exact one that my friend is reporing?
  15. Pene

    Clover General discussion

    Well my friend can reproduce it every time if he tries clean install with both Catalina and Mojave with that single rank ram. But I don't really have an idea what solution to offer for him to test...
×