Leaderboard

@apianti, well, obviously, it is not (constantly) in SMM, just constantly busy-loops in 0 ring within SmmCommProtocol->Communicate (you may check its src). Should have been slightly more clear. The functions are pretty much irrelevant, though I am aware of them. Unmapping of UEFI Runtime cannot happen. For all the others: you have no other choice but AptioMemoryFix + EmuVariableEfi. Other insanity will doom you.

AMD RX 590 8GB Polaris 30 works in Mojave! I picked up a PowerColor RX 590 Red Devil today and tested it works like the RX 580/RX480 and is recognized in Clover as 0x67DF1002. In About this Mac it shows as a Radeon Polaris. Mojave 14.2 dev beta 3

Si scusa, intendevo lo sleep Però non è importante per ora, vedo nel weekend di sperimentare un pochino Intanto grazie mille ancora

Eh si, ma dall'ultima volta che avevo seguito la guida da github sono passati credo 2 anni, non pensavo fosse nemmeno più valida Per fortuna ci siete voi che ci tirate su Mi manca di capire il "STOP" ma credo dipenda dal mio DSDT, mi documento un pò PS: ho aspettato con ansia il keynote perchè volevo seriamente farmi un macmini, appena finita la presentazione ho cambiato idea

OK! ho fatto tutte le prove e per la mia mobo e cpu il layout corretto è il 5, se dovesse servire a qualcuno

ok va bene anche così ma problemi "a monte"... prima la stessa tipologia di iniezione era ok... adesso no "parti" su ioreg a riguardo non corrette.. va beh.. Comunque ottimo..lascia così e non ritoccare nulla Capisco ... ma io parlo di ioreg e quello "non mente".. e dico che ci sono cose diverse e molto strane confrontandoli l'uscita ottica soundbar.. è un discorso a se... e non diciamo attinente a quello che stavo dicendo

Ciao in base alla ultima Clover di Gengik84 ho fatto alcune modifiche come in immagini prova il mio configplist , inserisci il Layout x audio se avvia fai Ioregistryexplorer , sono modifiche a livello funzionale , aggiunto altre varie FIX puoi confrontare tu stesso se apri con Clover Configurator config.plist.zip

well, unfortunately, I've read about this guide somewhere, and my first config is almost 90% similar to this. but my situation is a little different here, because this board only have one hdmi 1.4 output, so my 4k monitor is useless with igpu, I have to use my old nv 970 card as dgpu, so that's why I'm still stuck with 10.13.6. and with these setting, the AptioFix2-free2000 driver also gives me a allocation error, and can not boot at all. but all the config.plist so far about this ga-z390 aorus master as one common big mistake, which is that this board comes with a CNVi wifi/bluetooth. the bluetooth works only if you boot into windows first, then back to mac, then you will find out that the bluetooth works. of course without instant hotspot and continuexxx(I have chinese version, so I forgot how to spell this correctly). so this cnvi bluetooth problem is that when cold boot into mac, there is no way to upload the firmware. so this random hangup only happens when I use AptioMemoryFix, with or without nvramemu, it always hangs when reboot/shutdown. the core cause this TLB error is totally random. anyway, thank you Matgen84 and apianti. I can use this bluetooth to pair with headphone, iphone, android. So I'm very positive about this bluetooth works. why need a 3rd 4.2/4.1/4.0 bluetooth while you can have a bluetooth 5.0?

Ok, well this guide shows that AptioFix2-free2000 (such a bad driver...) and EmuVar work which means you can see if this panic happens still or if it is related to only the prevention of the relocation of runtime code regions.

Check if work DSDT.aml.zip

Ok was just curious, thought I saw somewhere that we need to add “Daytime” to embeddedthemetype in config.plist. Hopefully custom images for custom entries will be implemented soon. Sent from my iPhone using Tapatalk

I couldn’t get the Manjaro icon to appear using the old method as it looks for icons in the images folder and I can see svg themes don’t have an images folder. Usually it’s something like Images\os_manjaro.png Besides setting the theme BGM_SVG are there any other settings needed to activate the day / night option? Or is it default? Sent from my iPhone using Tapatalk

well, with my board, it's not possible to use AptioFix2/3, they always failed to start, but with AptioMemoryFix, I only got this panic when I try to reboot/shutdown mac. but it boots fine. so, is there possible solution that I can help test?

While this theory does sound interesting, I am afraid it is not correct. UEFI Memory map does include both shims and and other areas, so it is not correct to assume that the virtual address is unmapped, as it is reserved by XNU. The panic literally means that one of the cores stalled within UEFI runtime, and while the rest of the system reached userspace unmapping, the UEFI runtime thread still did not finish its job. Most likely it is infinitely waiting for SMI.

Yeah I’ll give that a go when I can. It looks like it leaves behind the first part of the “m” in macOS in my case. Edit: Lowering the font size down to 20pixels has solved the issue. .FontSizeMessageRow{font-size:20px;} @blackosx This also leads to how do we set custom linux images instead of the penguin with SVG themes?

Is there any reason for the little | before the volume name in BGM_SVG from thememanager? It's not on all, just 2 of 3.

I finally got it working. Method that finally worked was New extract and patch of my DSDT Remove all settings in Clover/Graphics section. Only using Inject Intel = true PlatformID blank, FakeID - 0x0 Intel QuickSync enabled now in VideoProc and MacX. iGPU idles at 0.20Ghz and scales to 1.25Ghz when encoding. CLOVER.zip

have you tried "sudo log erase --all " ?

i pay a very nice price in one X99-Gaming G1 WIFI, Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz with Vega

new toy with new update

I would like a patch to modify the USB device product ID for: ScanSnap S1500: Product ID: 0x11a2 Vendor ID: 0x04c5 (Fujitsu Ltd.) To become: ScanSnap iX500: Product ID: 0x132b Vendor ID: 0x04c5 (Fujitsu Ltd.) So I can try to use the new 64bit drivers that don't support the older S1500's device ID. More info on the problem in the comments here

Thanks for the tip, I'm giving this a try https://gist.github.com/stefanocoding/923931ae84333e2db7d60aafbb5a4f7b edit: I think usb_modeswitch is for those 3G modems that can either be the modem or a storage device i.e. with the driver software usually on it. Says here "The program does not change the product ID. That's entirely up to the device. " http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=97

I don't think so, Mac's don't have VGA ports

Good to have. Well, the second picture makes it very clear. XNU kernel invokes APTIO RuntimeServices SetVariable code, and then this code never returns. What we have in SetVariable is the following code coming from NvramDxe, I can tell that it did not change anyhow since the source leak, and the one in the source leaks are known to work. The code relevant to SMM switching looks the same too, and EFI_SMM_COMMUNICATION_PROTOCOL implementation is provided by EDK2. They still allocate the SMM communication buffer as EfiRuntimeServicesData, and still pass its address via NvramMailbox NVRAM variable, so it should be guarded by AptioMemoryFix. As a result I believe that the infinite loop happens somewhere on the way to NvramSmm (which now represents former Smi and Smm code glued together). However, the brief checking of the binary and the source shows that the Smi handler (NvramSmmCommunicationHandler, SetVariableSmmHandler) is pretty much the same too. This leaves us in an uneasy situation, where we do not know where to look for the problem. What I could suggest is writing a EFI runtime driver (by ripping off the known APTIO V source) that will reimplement communication with SMM: 1. Allocate a new communication buffer. 2. Check & overwrite the address of the old communication buffer in MailBox variable 3. Overwrite EFI_RUNTIME_SERVICES Variable functions with APTIO code but the new communication buffer. The above will result in having a complete path prior to SMM code under our control. Afterwards we should be able to get this code fully functional on some working APTIO V system (e.g. Skylake or Kaby Lake), and try it on the new problematic system. By changing the logic via the return codes it should be easy to ensure where the issue is: DXE or SMM driver. Other than it may even help us to understand whether the SMI handler exists at all. If it is SMM, I would probably try replacing NvramSmm with NvramSmm & NvramSmi from some Z370 BIOS first and reflashing the firmware. Then… perhaps reverse-engineer/reimplement NvramSmm with the new changes and try to debug it too. If you like the idea, I can share APTIO src and let you proceed.

In this short tutorial I will show you how to monitor your GPU performance in macOS High Sierra and macOS Mojave HACKINTOSH and absolutely FOR FREE !!!