CMMChris Posted March 21, 2020 Share Posted March 21, 2020 Nope, necessary to boot. Without Fake ID same issue again. They still didn't fix Vega20 drivers... Poor Mac Pro users 1 1 Link to comment Share on other sites More sharing options...
SandyMacOs Posted March 21, 2020 Share Posted March 21, 2020 (edited) @CMMChris: CPU Fake ID 0x040674 worked for me, Beta 6 running on i5-9600K @Chris1111: Thanks for the voodooHDA 2.9.2.V15 release, finally got audio working properly (ALC 1220-VB) Edited March 21, 2020 by SandyMacOs Too many Chris's 2 Link to comment Share on other sites More sharing options...
CMMChris Posted March 21, 2020 Share Posted March 21, 2020 12 minutes ago, SandyMacOs said: Thanks for the voodooHDA 2.9.2.V15 release Uh? I am not related to this. You mistake me with @chris1111 1 Link to comment Share on other sites More sharing options...
enlaid Posted March 21, 2020 Share Posted March 21, 2020 40 minutes ago, SandyMacOs said: CPU Fake ID 0x040674 worked for me, Beta 6 running on i5-9600K Is fake id needed for native CPU from iMac19,1? Not good... Link to comment Share on other sites More sharing options...
Sherlocks Posted March 21, 2020 Share Posted March 21, 2020 Is fake id needed for native CPU from iMac19,1? Not good...we know this true. it is temporary solutuon to boot in beta6 until check next beta.나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Pavo Posted March 21, 2020 Share Posted March 21, 2020 13 hours ago, CMMChris said: They still didn't fix Vega20 drivers... Poor Mac Pro users Seems to be running pretty good to me. Link to comment Share on other sites More sharing options...
MorenoAv Posted March 21, 2020 Share Posted March 21, 2020 Update made, thanks to user with the CPU Fake ID 0x040674 idea, that made the trick... 3 Link to comment Share on other sites More sharing options...
moozuki Posted March 22, 2020 Share Posted March 22, 2020 21 hours ago, AlfredoM said: my question, does anyone know what you can use for a fakeCPUID so that this 2nd Hacki boots Beta 6 again and the Beta6 is then full can install? Thanks for tips. UPDATE: Also runs with the same FakeCPUID on my 2nd Hacki with Intel i5-6600K. Is probably a universal fakeCPUID - I didn't have to use FakeCPUID at all, no problem with the update. Intel i5-6600 Link to comment Share on other sites More sharing options...
C.Frio Posted March 22, 2020 Share Posted March 22, 2020 1 hour ago, MorenoAv said: Update made, thanks to user with the CPU Fake ID 0x040674 idea, that made the trick... Hi.. Did you edited with clover configurator? C.frio Link to comment Share on other sites More sharing options...
MorenoAv Posted March 22, 2020 Share Posted March 22, 2020 9 hours ago, C.Frio said: Hi.. Did you edited with clover configurator? C.frio Hi @C.Frio, No I didn't edit nothing I only put the fake id in clover and it updated... 1 Link to comment Share on other sites More sharing options...
C.Frio Posted March 22, 2020 Share Posted March 22, 2020 13 hours ago, MorenoAv said: Update made, thanks to user with the CPU Fake ID 0x040674 idea, that made the trick... hi... thanks for the guy that found the trick...and @MorenoAv...it worked on z370..with 8600K c.frio 1 Link to comment Share on other sites More sharing options...
wern apfel Posted March 22, 2020 Share Posted March 22, 2020 It appears to be a MSR lock patch issue. Since clover recognises the lock, the XCPM/PM patch is activated automatically. Howerver the XCPM patch no longer works with beta 6. With enabled MSR lock activated, my KabyLake stops with the known message, but works with the MSR lock deactivated. Therefore, the pre-Skylake machines work (they use AICPM). This is my observation! 2 Link to comment Share on other sites More sharing options...
Sherlocks Posted March 22, 2020 Share Posted March 22, 2020 (edited) 11 minutes ago, wern apfel said: It appears to be a MSR lock patch issue. Since clover recognises the lock, the XCPM/PM patch is activated automatically. Howerver the XCPM patch no longer works with beta 6. With enabled MSR lock activated, my KabyLake stops with the known message, but works with the MSR lock deactivated. Therefore, the pre-Skylake machines work (they use AICPM). This is my observation! i'm using only pm patch in kernel patch of clover. does it means rehabman patch broken? i will check part 나의 SM-N960N 의 Tapatalk에서 보냄 Edited March 22, 2020 by Sherlocks Link to comment Share on other sites More sharing options...
C.Frio Posted March 22, 2020 Share Posted March 22, 2020 (edited) 24 minutes ago, wern apfel said: It appears to be a MSR lock patch issue. Since clover recognises the lock, the XCPM/PM patch is activated automatically. Howerver the XCPM patch no longer works with beta 6. With enabled MSR lock activated, my KabyLake stops with the known message, but works with the MSR lock deactivated. Therefore, the pre-Skylake machines work (they use AICPM). This is my observation! Hi just to inform..maybe can help on a 9600k (z390), it works without issue..clover 5097 but the 8600k(z370) does not...clover 5106 nor 5097 (worked adding fake cpu ID 0x040674) c.frio Edited March 22, 2020 by C.Frio 1 Link to comment Share on other sites More sharing options...
wern apfel Posted March 22, 2020 Share Posted March 22, 2020 40 minutes ago, Sherlocks said: i'm using only pm patch in kernel patch of clover. does it means rehabman patch broken? i will check part 나의 SM-N960N 의 Tapatalk에서 보냄 Could be. 25 minutes ago, C.Frio said: Hi just to inform..maybe can help on a 9600k (z390), it works without issue..clover 5097 but the 8600k(z370) does not...clover 5106 nor 5097 (worked adding fake cpu ID 0x040674) c.frio You can see in bootlog whether the MSR lock is activated. 0:507 0:000 MSR 0xE2 before patch 00008000 0:507 0:000 MSR 0xE2 is locked, PM patches will be turned on 0:507 0:000 MSR 0xCE 00080838_F1012A00 2 Link to comment Share on other sites More sharing options...
C.Frio Posted March 22, 2020 Share Posted March 22, 2020 hi... sorry but how can I see this bootlog, as the boot dos not go.. and at a text before the +++++ line it stops..and those lock text didn't appears is this stored on my usb boot pen drive? or this is only to check the lock after I can boot... with F4? thank you.. c.frio Link to comment Share on other sites More sharing options...
wern apfel Posted March 22, 2020 Share Posted March 22, 2020 12 minutes ago, C.Frio said: hi... sorry but how can I see this bootlog, as the boot dos not go.. and at a text before the +++++ line it stops..and those lock text didn't appears is this stored on my usb boot pen drive? or this is only to check the lock after I can boot... with F4? thank you.. c.frio You can try VerifyMsrE2.efi via the shell or a working macOS 2 Link to comment Share on other sites More sharing options...
C.Frio Posted March 22, 2020 Share Posted March 22, 2020 hi... thanks ,but it is too deep for me... I'm a curious M.D. lucky... I will read about... thank you..and I have both working.. c.frio Link to comment Share on other sites More sharing options...
Sherlocks Posted March 22, 2020 Share Posted March 22, 2020 okay i found solution.i booted skylake cpuid.need to improve kernel patch.i will research all macos kernel and correct and cleanup patch. 나의 SM-N960N 의 Tapatalk에서 보냄 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted March 22, 2020 Share Posted March 22, 2020 FYI, issue is not limited to beta 6 10.15.4. I have the same problem booting "Beta Security update 2020-002 10.14.6" and I guess it'll be the same for "Beta Security update 2020-002 10.13.6".please upload kernel of 10.13.6나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
polyzargone Posted March 22, 2020 Share Posted March 22, 2020 5 minutes ago, Sherlocks said: please upload kernel of 10.13.6 Sorry, I thought there was a Beta Security update 2020-002 for 10.13.6 but I was wrong. There's nothing in the Software Update panel for this version. However, I can upload the Beta Security update 2020-002 10.14.6 kernel if needed. Just let me know ;). 2 Link to comment Share on other sites More sharing options...
Sherlocks Posted March 22, 2020 Share Posted March 22, 2020 Sorry, I thought there was a Beta Security update 2020-002 for 10.13.6 but I was wrong. There's nothing in the Software Update panel for this version. However, I can upload the Beta Security update 2020-002 10.14.6 kernel if needed. Just let me know .okay upload 10.14.6.i will check all kernel and cleanup patch for all macos and prepare next macos.나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
polyzargone Posted March 22, 2020 Share Posted March 22, 2020 Here you go! kernel_Mojave.zip 1 Link to comment Share on other sites More sharing options...
Dragster27 Posted March 22, 2020 Share Posted March 22, 2020 Hi there. I've updated to 10.15.4 beta 6 without issues.. but I'm having problems with sleep/wake up..it used to work well until 10.15.3 but now the machine reboots when I try to wake it up... Haswell/IntelHD 4600... clover 5106 + latest Lilu + WEG. Any help will be appreciated. Cheers, D. Link to comment Share on other sites More sharing options...
Rocky12 Posted March 22, 2020 Share Posted March 22, 2020 Done X58 issue is peshu Clover version 5103 Link to comment Share on other sites More sharing options...
Recommended Posts