uglyJoe Posted February 23, 2019 Share Posted February 23, 2019 ApfsDriverLoader from https://github.com/acidanthera/AppleSupportPkg/releases/tag/2.0.6 with GUID: 18F0F325-E54C-2994-E37E-E6949EC94D45 ApfsDriverLoader-v2.0.6.zip Link to comment Share on other sites More sharing options...
uglyJoe Posted February 23, 2019 Share Posted February 23, 2019 (edited) @cecekpawon While creating a new oz firmware I realized that someone removed the DXE dependency section from the Ozmosis.ffs Was this intended to make KernextPatcher and Co. work together with Ozmosis? btw. To avoid the need of DevProp and EfiDevicePathPropertyDatabase, I stored the device properties to my dsdt/ssdt. Now all the required stuff fits into my 64MB flash rom without removing anything Edited February 23, 2019 by uglyJoe Link to comment Share on other sites More sharing options...
Tusskan Posted February 23, 2019 Share Posted February 23, 2019 (edited) Hello guys, it's been a long time, afaik now that 10.14.4 requires new kext injection method, DO I need to insert any new updates to my rom or it work just fine with the latest updates that came when Mojave was released ? Edited February 23, 2019 by Tusskan Link to comment Share on other sites More sharing options...
uglyJoe Posted February 23, 2019 Share Posted February 23, 2019 @Tusskan If this is your current setup "Ozmosis Bootloader v167X-MASS | High Sierra 10.13.1" you must update your Ozmosis to the XMAX version and add the KernextPatcher with a recent configuration. If you have Intel HD4600 active, you may have to dig a little deeper and read from here ... Link to comment Share on other sites More sharing options...
witjojo Posted February 23, 2019 Share Posted February 23, 2019 (edited) On 2/16/2019 at 2:28 AM, uglyJoe said: No EFI, no ROM but all files you need and a short guide how to add them to your firmware. Ozmosis 167X-HD46.zip @uglyJoe I have created a new GA-Z97-D3H ROM with your files. Sierra and High Sierra also runs with my GTX 650 TI graphics card but the internal HD 4600 does not work. I only replaced the 'Raw section" of OzmosisDefaults with my OzmosisDefaults.plist. .... <key>DisableIntelInjection</key> <false/> <key>DisableNvidiaInjection</key> <true/> <key>AAPL,ig-platform-id</key> <integer>220332035</integer> .... Otherwise I did not make any changes. I do not have to change the DarBoot.plist and KernextPatcher.plist right? They are up to date.But I think I may have to change the DevProp.plist with my values to run the HD4600. I don't know what I have to change in DevProp.plist to patch the HD 4600. Where can I get the values from? Or I have fundamentally done something wrong. Or do other things have to be changed, such as DSDT? Maybe you could help me and build me a ROM for testing. Here is my original ROM. Z97D3H.F9 Edited February 23, 2019 by witjojo Link to comment Share on other sites More sharing options...
uglyJoe Posted February 23, 2019 Share Posted February 23, 2019 @witjojo Ozmosis-HD46 does not inject any device properties. You can do this with DevProp or via DSDT/SSDT. I add DevProp to your firmware, check if the path is correct for your system <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>DeviceProperties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data>AwAiDQ==</data> <key>device-id</key> <data>EgQAAA==</data> </dict> </dict> <key>Preferences</key> <dict> <key>Debug</key> <false/> <key>Off</key> <false/> <key>SaveLogToFile</key> <false/> <key>SaveLogToDeviceTree</key> <false/> <key>SaveLogToNvram</key> <false/> </dict> </dict> </plist> For further testing, you can put your own to /Volumes/EFI/EFI/DevProp.plist Defaults.plist is for iMac14.1, best way change this is 'extract -> edit -> replace' or put your own to ESP. Z97D3H_OZ-HD46.F9 Link to comment Share on other sites More sharing options...
witjojo Posted February 24, 2019 Share Posted February 24, 2019 (edited) @uglyJoe I have tested it. Unfortunately the ROM does not work, like my ROM before. What should I check for a path in DevProp.plist? I don't understand what comes in there to patch the HD4600. I attached my logs. Maybe you will find something. DarBootLog.txt DevPropLog.txt KernextPatcherLog.txt Edited February 24, 2019 by witjojo Link to comment Share on other sites More sharing options...
uglyJoe Posted February 24, 2019 Share Posted February 24, 2019 (edited) Check PCI path for your igpu with gfxutil iMac:~ me$ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) Did you activate your igpu from your firmware setup ? Edit: First you you need a working setup with your IGPU and High Sierra So perform the obligatory steps - Enable IGPU - Set 32MB and MAX - ... - maybe remove your Nvidia temporary Did you made your firmware by your self? If not, you have to check DSDT/SSDT for applied patches that are non-cooperative. Edited February 24, 2019 by uglyJoe Link to comment Share on other sites More sharing options...
cecekpawon Posted February 24, 2019 Share Posted February 24, 2019 15 minutes ago, uglyJoe said: Did you activate your igpu from your firmware setup ? From witjojos log, no. The class for gpu should be: 0300XX / 0380XX. Only his nvidia were detected. Place "pci.ids" on "\EFI\pci.ids" to get more devices description in log. 21 hours ago, uglyJoe said: While creating a new oz firmware I realized that someone removed the DXE dependency section from the Ozmosis.ffs Was this intended to make KernextPatcher and Co. work together with Ozmosis? Try to manually rebuild Ozmosis ffs by adding missing depex, take from this script as example. Link to comment Share on other sites More sharing options...
uglyJoe Posted February 24, 2019 Share Posted February 24, 2019 (edited) @cecekpawon it's missing in all XMAX I found so far. I extract the dependency form XMAS and put it in HD46 already, but I didn't tested it yet. Was waiting for your answer, to go Edit: Done, all fine. Ozmosis HD46 with DXE dependency section: Ozmosis-HD46+DXE.zip Edited February 24, 2019 by uglyJoe Link to comment Share on other sites More sharing options...
qutongming Posted February 24, 2019 Share Posted February 24, 2019 On 1/8/2019 at 5:35 PM, cecekpawon said: I guess you will need AudioDxe.ffs and BootChimeDxe.ffs, which not provided by developer yet. Go extract file in attachment to test (warning: i have not test my self, please use at your own risk). As I mentioned above, BootChimeDxe will have super size to embed, since they have default sound inside binary. And Im too lazy to reapply my previously diffs. [!] Also experienced boot hang with my Aptiofix with latest commit, could be caused by overridden ExitBS in BootChimeDxe, not sure here. * I have made a new driver to work with AudioDxe here which similar to BootChimeDxe, I think ;))) FIRMWARE.Fv.zip Hello, Can give it to I? Driver BeepBeep.ffs Thank you Link to comment Share on other sites More sharing options...
Tusskan Posted February 24, 2019 Share Posted February 24, 2019 17 hours ago, uglyJoe said: @Tusskan If this is your current setup "Ozmosis Bootloader v167X-MASS | High Sierra 10.13.1" you must update your Ozmosis to the XMAX version and add the KernextPatcher with a recent configuration. If you have Intel HD4600 active, you may have to dig a little deeper and read from here ... I have updated my rom when Mojave entered drop the current sig cause I haven't updated it since too long, but how about the new 10.14.4 Do I need to add anything or it is just fine right now I'm on Mojave 10.14.3 with supplemental update running fine without any problem. I don't want to risk updating to beta. Link to comment Share on other sites More sharing options...
uglyJoe Posted February 24, 2019 Share Posted February 24, 2019 18 minutes ago, qutongming said: Hello, Can give it to I? Driver BeepBeep.ffs Thank you Please stop screaming and start reading here Link to comment Share on other sites More sharing options...
uglyJoe Posted February 24, 2019 Share Posted February 24, 2019 10 minutes ago, Tusskan said: I have updated my rom when Mojave entered drop the current sig cause I haven't updated it since too long, but how about the new 10.14.4 Do I need to add anything or it is just fine right now I'm on Mojave 10.14.3 with supplemental update running fine without any problem. I don't want to risk updating to beta. There are new kernel patches for 10.14.4 ... but I am also on 10.14.3 Link to comment Share on other sites More sharing options...
qutongming Posted February 24, 2019 Share Posted February 24, 2019 1 hour ago, uglyJoe said: Please stop screaming and start reading here Please help I don't understand English. I rely on translation. I want this one (BeepBeep.ffs) Thank you 1 Link to comment Share on other sites More sharing options...
cecekpawon Posted February 24, 2019 Share Posted February 24, 2019 @qutongming qutongming.zip 1 Link to comment Share on other sites More sharing options...
qutongming Posted February 24, 2019 Share Posted February 24, 2019 2 minutes ago, cecekpawon said: @qutongming qutongming.zip Thanks very much 1 Link to comment Share on other sites More sharing options...
qutongming Posted February 24, 2019 Share Posted February 24, 2019 (edited) 1 hour ago, cecekpawon said: @qutongming qutongming.zip Please help Is this configuration correct? Thank you Edited February 24, 2019 by qutongming Link to comment Share on other sites More sharing options...
uglyJoe Posted February 24, 2019 Share Posted February 24, 2019 If someone like to try... KextToFfs-Reloaded-1.0.zip Link to comment Share on other sites More sharing options...
cecekpawon Posted February 24, 2019 Share Posted February 24, 2019 (edited) @qutongming Wrong LOL. The easiest way you may use BootChimeCfg to configure devicepath, port and also volume. BeepBeep will able to read BootChimeCfgs saved config. Leave those properties in plist empty (or add some prefix to comment out / just simply delete it). For audio filepath, just rename and place your audio file in “\EFI\BeepBeep.wav” (default audio filepath), or embed it into ffs as a raw section. Edited February 24, 2019 by cecekpawon 1 Link to comment Share on other sites More sharing options...
witjojo Posted February 25, 2019 Share Posted February 25, 2019 (edited) 20 hours ago, uglyJoe said: Check PCI path for your igpu with gfxutil iMac:~ me$ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) Did you activate your igpu from your firmware setup ? Edit: First you you need a working setup with your IGPU and High Sierra So perform the obligatory steps - Enable IGPU - Set 32MB and MAX - ... - maybe remove your Nvidia temporary Did you made your firmware by your self? If not, you have to check DSDT/SSDT for applied patches that are non-cooperative. @uglyJoe Ok - First i removed my Nvidia and activate my IGPU in my firmware setup. ...Did you made your firmware by your self? ... I used the ROM you created for me before. I also deactivated my DSDT. When i boot Sierra or Mojave it stops at the boot with the "IGPU" message. Then I start windows to see if there are logs in the EFI partition from the boot. But there are no logs. Why Windows? Because it is not possible to boot in any Apple system with the HD4600.And when I start again with Nvidia the logs will be overwritten or recreated. That happened to me before. So no logs are created. Why? Or is that still too early in the phase when booting? And how should I run ./gfxutil -f IGPU if I can not start a system with the HD4600? See pictures @cecekpawon What you mean with? .... Place "pci.ids" on "\EFI\pci.ids" to get more devices description in log. Edited February 25, 2019 by witjojo Link to comment Share on other sites More sharing options...
uglyJoe Posted February 25, 2019 Share Posted February 25, 2019 @witjojo Did you try with your old firmware? Ozmosis XMASS should detect your IGPU. Link to comment Share on other sites More sharing options...
Ur4ela Posted February 26, 2019 Share Posted February 26, 2019 (edited) Ozmosis can load the OS from the disk Nvme? Edited February 26, 2019 by Ur4ela Link to comment Share on other sites More sharing options...
TypeThree Posted February 27, 2019 Share Posted February 27, 2019 (edited) @uglyJoe First of all thanks for your effort in this thread in the last period of time! 10.14.4 patches can be found here as well: Have you analysed the effect of KxldUnmap on Ozmosis? Does a race condition appear in the mentioned case without the use of the patch? The missing DXE Dependency section was not really intended. XMAX was released as a beta only and during testing no problems appeared when DXE Dep was missing (which doesnt really justify leaving it out though). After the Beta-Release I did some tests with readded DXE Dep as well (also regarding HD4600) but couldn't detect any advantage so I decided it was not worth updating all the ROMs again because of that. IMHO with the recent updates on HD4600 and all the drivers now commonly used in XMAX roms etc. DXE Depex should be rewritten (if even possible, probably no without source/inf and dsc) to ensure Ozmosis is loading at the intended time, I don't know if that is possible though, you are free to look into that if you want to Edited February 27, 2019 by TypeThree Link to comment Share on other sites More sharing options...
qutongming Posted February 27, 2019 Share Posted February 27, 2019 On 2/24/2019 at 9:11 PM, cecekpawon said: @qutongming qutongming.zip Was Grund!Keine soundkarte Nur grafikkarten _____ _____ _____ _____ _____ || U ||| E ||| F ||| T ||| W || https://github.com/cecekpawon/UEFTW ||___|||___|||___|||___|||___|| BeepBeep (r#49 | 2019-02-24 20:08:00) |/___\|/___\|/___\|/___\|/___\| On 2019-02-25 03:42:26 00:100 (00:100) | No Apple boot-args found 00:100 (00:000) | Running from: MemoryMapped(0xB,0xC1073004,0xC19A7003)/FvFile(E509B49D-B273-4DF6-992F-4FBE3A671467) 00:100 (00:000) | SelfDirPath = \EFI 00:100 (00:000) | Get Plist from: NVRAM ... Not Found 00:100 (00:000) | Get Plist from: ESP ... Not Found 00:100 (00:000) | Get Plist from: FV: MemoryMapped(0xB,0xC1073004,0xC19A7003)/FvFile(E509B49D-B273-4DF6-992F-4FBE3A671467) ... Success 00:101 (00:001) | Parsing plist: ... Success 00:101 (00:000) | Preferences->Off: No 00:101 (00:000) | Preferences->Debug: No 00:101 (00:000) | Preferences->SaveLogCompress: No 00:101 (00:000) | Preferences->SaveLogToFile: Yes 00:101 (00:000) | Preferences->SaveLogToDeviceTree: No 00:101 (00:000) | Preferences->SaveLogToNvram: No 00:106 (00:004) | Got AppleAudioVolume (64) 00:112 (00:005) | Load Audio File '\EFI\BeepBeep.wav' ... Success 00:112 (00:000) | WAVE Length (451654) Format (16) Channels (2) Freqs (44100) Bits (16) Samples (451584) 01:333 (01:221) | Controller Name : NVIDIA GK110 HD Audio Controller 01:333 (00:000) | Codec Name : NVIDIA (Unknown) ... Success 01:333 (00:000) | AFG Function Id : 0x1 (unsol 0) ... Success 01:333 (00:000) | Vendor Id : 0x10DE0044 ... Success 01:333 (00:000) | Revision Id : 0x100100 ... Success 01:333 (00:000) | AudioIo (0) Skip (0) DevicePath 'PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)' 01:333 (00:000) | Got (4) OutputPorts ... Success 01:333 (00:000) | 00) HDMI @ Other Internal (N) 01:333 (00:000) | 01) HDMI @ Other Internal (N) 01:333 (00:000) | 02) HDMI @ Other Internal (N) 01:333 (00:000) | 03) HDMI @ Other Internal (Y) 01:333 (00:000) | StartPlaybackOnEvent: OnBoot 01:413 (00:080) | Setup Playback Output (3) Volume (90%) ... Success 01:413 (00:000) | Start (Async (1)) Playback ... Success 07:675 (06:262) | ((( Ozmosis is currently running ))) 07:735 (00:059) | Found Booter (OS: 10.12 | Ver: 361.220.1) 07:735 (00:000) | Booter Path: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,E35E0A12-9D1F-4EF8-9ACF-315888C287D4,0x64028,0x1DC8F260)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A9EA89BFBC97DC47BE909886D5C42AF9)/\System\Library\CoreServices\boot.efi 07:736 (00:001) | OSVersion: 10.14.3 | BuildVersion: 18D109 10:213 (02:476) | Found BootArgs at 0xB2741000 10:213 (00:000) | BeepBeep: End bootchimecfg.efi -t Outputted devices: 1. HDMI - other internal 2. HDMI - other internal 3. HDMI - other internal 4. HDMI - other internal 5. SPDIF - other internal 6. Line - rear external 7. Line - rear external 8. Line - rear external 9. Headphones - front external 10. SPDIF - rear external Link to comment Share on other sites More sharing options...
Recommended Posts