Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/20/2020 in all areas

  1. you can assign it, either as a device (for .img files) by adding -device if=virtio,format=raw,file=/path/to/device -device if=ide,format=raw,file=/path/to/image,id=someId ... or simply with -cdrom /path/to/iso Qemu has some very good docs, read those first. It covers a lot and there are examples. You can find a lot in other places. Windows is a {censored} - so for virtio to work you must (!?!) a virtual driver made by redhat or use if=ide instead of if=virtio, go with if=ide if you dont plan a long-term VM use otherwise download the iso with drivers from fedora: 'google virtio drivers win10 iso' --- Dude, you need to clean that screen... gross! Dude, you need to clean that screen... gross!
    3 points
  2. Sorry, been busy updating to build 19F94a. All good, by the way. So..yeah. This is a bit confusing. Cause mine is set to AdviseWindows=NO (so..that would be boolean false). EFI partition is the first one. Obviously UEFI boot. And it's booting perfectly fine between BootCamp Windows and MacOS. I was reading the documentation, as well, and I think it does that when it's set to true. Failsafe (default) is false though. Now, if these FirmwareFeatures are the same ones as the ones in SMBIOS and PlatformNVRAM, I already have mine set to 37E10FE0 00000000. So...whether that's already good enough or not, I don't know. Never really understood what they do. But it sounds like it's adding both, for both cases (Legacy and UEFI boot). By the way, about the updates, I absolutely love how seamless it is to update MacOS with OC. It always goes to the installer, it always selects the correct partition to boot from. Awesome! You really don't need to touch anything. You set it to update and come back when it's done.
    2 points
  3. Oh. I didn't know that. I mean, I knew it's because of the Recovery partition, since we've just discussed this earlier. But I didn't know that AdviseWindows fixes it. My Windows takes no advises from anyone. :))
    2 points
  4. The future major update: Windows 2004 A little bit funny too.
    2 points
  5. 1909?! That was a long time ago. Windows 10 wasn't even around at that time. :)) Windows itself wasn't around. Bill Gates wasn't around either! Bad dorky joke..? Ok... Sorry...
    2 points
  6. Since 1909, this is the default partioning for Windows 10.
    2 points
  7. @arsradu, actually, it is even more interesting. When I merged AudioDxe to OpenCorePkg a couple days ago, I did not merge the latest changes to AudioDxe. So AudioDxe version built from master a few minutes ago was exactly the one you got from AppleSupportPkg 2.1.7 release. There were exactly four changes to AudioDxe: https://github.com/acidanthera/AppleSupportPkg/commit/b0fd9471c9a1a3967875f3260631e91e6fc860c0 (no-op for XCODE5) https://github.com/acidanthera/OpenCorePkg/commit/fd7cc9e325fce98528d438cdebc59954ef0a121d (new constants, basically no-op for old code) https://github.com/acidanthera/AppleSupportPkg/commit/4225cc346914d0292f219da83bba027fdf2a8db0 (not present in master before 2020-05-20 10:53 MSK) https://github.com/acidanthera/AppleSupportPkg/commit/5a698b8cb8a876c916c933f876477a5e75e97c98 (not present in master before 2020-05-20 10:53 MSK) Here is where merged the last two AudioDxe changes into master: https://github.com/acidanthera/OpenCorePkg/commit/3b051a797a60b79627437206fa6eec3238e68350 For this reason I am afraid it is your compilation setup that is broken. Are you sure that you use macbuild.tool (now named build_oc.tool) and Xcode 11.4.1? Perhaps testing my compiled version will be more practical. AudioDxe-REL-3b051a79-edk2.zip
    2 points
  8. @arsradu@eSaF, it is not clear to me from the description of what is broken AudioDxe or OpenCore. Does older AudioDxe work with OpenCore from master? From your reports I am starting to suspect that you have your audio codec not resetting across the reboots, and thus you get random audio failures. This is what you can try to troubleshoot by multiple reboots and/or cold resets (full poweroff and then power up). @makk, regarding your last question, IOHIDSystem is a plist-only kext commonly used instead of IOHIDFamily. The warning is rather harmless, but it is indeed best to fix the kext to contain IOHIDFamily instead of IOHIDSystem, as the former is not in kernelcache, and OpenCore has to workaround it.
    2 points
  9. Here is version 1.0.0d5 in which I enabled TSO. The attached archive contains prebuilt binaries for Catalina and Mojave. I verified that it loads under Mojave. In case you want to build from source with Mojave, you have to use Xcode 10.3. Good luck testing! Mieze LucyRTL8125Ethernet-V1.0.0d5.zip
    2 points
  10. Introduction I basically wrote down everything i did the last few days to get Sierra working on my Surface Pro. To safe you guys the hassle i've been trough i wrote this "little" guide.. Hope you enjoy it. Access to a real Mac or Hackintosh needed for the next 5 steps! 1. Download those 3 Files: - Sierra EFI files, Kexts & Kextdrop - OS X Sierra installation App - latest Clover 2. Prepare the USB Stick using Disk Utility in OS X, format the Stick to HFS and name it „SierraStick“ (necessary for the next step). 3. Apply the Installer to the Stick using this Command: sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/SierraStick/ --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction 4. Install Clover, Choose the SierraStick as location, click on Customize and tick exactly what is shown below (there’s no need for themes, as there’s one in my EFI folder). - Make sure Clover Created the EFI Partiton! 5. Copy My EFI folder you downloaded from the Link above straight to the Root of the EFI Drive (replace/merge the files/folder if needed). Now insert the clover’d SierraStick into the Surface! 6. Make sure the Surface is turned off, press the Volume down and the Power button - keep the Volume down one pressed. 7. Once booted to Clover start the Setup by simply pressing enter. 8. Once the Setup ran trough the Surface reboots, make sure you booted clover again (like 2 steps before) - choose the Drive you installed OS X to and press enter. 9. Setup continues… 10. Reboot once again, boot into the OS X partition and make sure everything works as it should. If everything worked like it should you should now have a fully working Sierra installation now, congrats. Place Clover to the Mac EFI: "If it runs on your stick its runs on your disc" - caleidosCope 1. Download Clover Configurator and mount the EFI Partition of the Setup Stick. Clover Configurator 2. Copy the EFI folder to your desktop. 3. Reboot OS X (that’s just to be sure you’re not messing the EFI partitions, if you’re careful enough you can skip that). 4. Remove the Stick once OS X booted and run the Configurator again, this time mount the Mac EFI. 5. Copy the EFI folder from the desktop to the Mac EFI partition (replace/merge the files/folder if needed). 6. Reboot to make sure it boots clover. The journey just began.. No, really.. We’re not fully done yet! Whats up next? As you may or may not noticed there seem to be some things not working: - Bluetooth - Audio - Appstore (partially works, installing doesn’t while updates do) Just follow the following steps to get the above things working: 1. Run the Kext Drop you downloaded in my EFI package at the first post and „kextdrop“ the 3 files included right next to it. (NullEthernet.kext, AvastarFwLoader.kext & AppleHDA.kext) 2. Run Clover Configurator you downloaded before, mount your EFI as described above and open the EFI partition 3. Navigate to EFI/Clover/ and open the „config.plist“ by double clicking it - Clover Configurator should now pop up. 4. Within the Configurator navigate to SMBIOS on the lift side and click on the magic wand button on the right side. 5. Now choose the MacBook Air (no matter which one, its up to you), and press „ok“ in the next appearing window. Save the changes with cmd+s and reboot the system. Congratulations, now everything stated above should work, Appstore will allow you to download apps, sound will play and the microphone should work now too. Its up to you now, be wise with what you do next! Last but to least, special thanks to: caleidosCope (danke für deine „nerven“ ) ClaudesTech (initial inspiration to write this guide) JahStories (some files here and there) Whoelse I might missed (please PM me)
    1 point
  11. @MacNB I think your boot entry "issue" is "by design" with the newly introduced boot policy. BlessOverride at all times was the prefered way to add options, custom entries are more or less only for the case of multiple OSes per partition, which is not a thing at all in Apple land. So to say, an extension of ours to what Apple gave us to work with. To rename an option, you can just use the .contenDetails file as described in the PDF fine with no need for a custom entry.
    1 point
  12. I found a workaround to my issue with OC 0.5.9 booting Windows via System Preferences Startup Disk option. In OC 0.5.8 it worked fine but updating to 0.5.9 broke this - it would restart the system and boot the first macOS disk instead of windows. I had a custom entry in Misc->Entries: <key>Entries</key> <array> <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <false/> <key>Name</key> <string>Windows 10 Pro</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,A4CE4F1A-43C6-492D-BB16-2DD6EABCE4EF,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string> </dict> </array> ...so that I could customise the name displayed in the boot Picker to "Windows 10 Pro". In 0.5.8, this entry was always selected on restart. But in 0.5.9, it's is ignored. Workaround: Disable the Misc->Entries ->0 Added the Misc->BlessOverride->0-> \EFI\Microsoft\Boot\bootmgfw.efi Now OC 0.5.9 boots Windows from System Preferences Startup Disk. I say this is a workaround since it's not what I wanted to happen. I wanted a custom entry so that I can label the drive name that's display on boot picker.
    1 point
  13. Yes that's what I believe happens. That is, Setting AdviceWindows = YES, sets those TWO bits in the FirmwareFeatures variable. That variable is stored in the Platforminfo->PlatformNVRAM. So it could help you.
    1 point
  14. Yeah but the what do you think about the 2 bullet points there? Does it mean that when I set AdviseWindows=YES then it conditionally handles the two points? Because the first point is applicable to me, while the second are applicable to others like @arsradu. Or there's something to do besides setting it to YES.
    1 point
  15. My friend you and I are kindred spirits
    1 point
  16. I just know my girlfriend would do the same. :)) So, I totally understand what you're going through, man. And yeah, I'm the same. I don't like it when things don't make sense. Anyway, enjoy!
    1 point
  17. Hey how did you know about the rug thing - you been talking to my wife? Yea it was a little stressful as I hate to know something is beating me, but alls well that ends well
    1 point
  18. LOOOOOOLLL!!!!! :))) That's good to know! Anyway, I'm really happy you managed to fix it! It's been a pleasure talking to you, man! Really. I love talking to people like you. And I'm really glad I could help (even if it wasn't really much at all). Now you can sleep well tonight. And not on the rug outside the door. :))
    1 point
  19. Hey guys an update on my Boot-Chime woes. It turns out that the Boot-chime was there all along but for some reason the signal from the sound card was at the headphone jack and then would switch to speaker port at the back of the case once it reaches the desktop. I would like to thank arsradu and vit9696 for all the suggestions but the big Hero of the day is the man himself Audiogod, quite an apt title. His suggestion was spot on - Change your audio output to a value until you get Boot-Chime at startup and that was the answer
    1 point
  20. Thank for the note. No, this is just a bug fixed now. Take Clover commit 3b48782 You have to draw all elements as vectors. Else they will be replaced by embedded icons which are not scalable.
    1 point
  21. This bit from the docs is interesting.
    1 point
  22. https://github.com/acidanthera/OcBinaryData/tree/master/Drivers
    1 point
  23. Catalina is on separate NVMe drive and yes it's on the first partition. Mojave is on separate SSD drive and it's the only partition. Widows is on yet another SSD and it's effectively the first partition followed by High Sierra. I think you are right in that OC can't really boot Windows and seems to default to the NVMe drive (with Catalina). I love the OC documentation, but the description of the new DeduplicateBootOrder is not super clear to me. Thanks for the tip. I had AdviseWindows = NO in 0.5.8 it worked fine. But I tried setting AdviseWindows = Yes in the current 0.5.9 and it made no difference. I can boot Windows but only via boot picker - not via Startup Disk selection. Something in 0.5.9 has changed for me. Need to go back to 0.5.8 and try again. UPDATE: reverting back to 0.5.8 and all is working - switching between macOS and Windows via Startup disk and Windows Bootcamp control panel. Hmmmm
    1 point
  24. Stupid Windows.... I feel to wipe out my partitions now and rebuild it the bootcamp way so my mind is at ease and drive looks correct cos it’s annoying me now... @arsradu I blame you! (Jokes)
    1 point
  25. thanks again. I wouldn't need the usb 2 hub in the rear (I have a dedicated on underneath my table) but I will just go with your kext atm.
    1 point
  26. No worries buddy and I’m all about the internals and betas of everything aswell
    1 point
  27. Did you try setting AdviseWindows to Yes? @arsradu this is what happens when the recovery drive is the first partition on windows instead of the EFI but setting AdviseWindows=Yes sorts it out.
    1 point
  28. Coolio buddy, I did it so all USB ports are open. And the front and the two usb3 ports right under the usb2 hub are usb3 and 2 as well. @dredhorse what you can also do is go into the kext itself and edit the ports and change them to whatever you want too. thats what i would do personally as it would only take a few seconds to do it.
    1 point
  29. okay.. I've got this far with 5117 by uncommenting the DBG statements 9:562 0:000 === [ InitXTheme ] ============================== 9:562 0:000 use Daylight theme 9:602 0:040 Theme view-bounds: w=1366.000000 h=768.000000 units=px 9:602 0:000 using scale 1.406250 9:741 0:138 Background parsed [1688, 1080] 9:741 0:000 Banner position at parse [594,164] 9:769 0:028 parsed banner->width=741 height=411 9:772 0:002 parse func_about status Success 9:776 0:004 parse func_options status Success 9:780 0:004 parse func_clover status Success 9:785 0:004 parse func_secureboot status Success 9:788 0:003 parse func_secureboot_config status Success 9:792 0:003 parse func_reset status Success 9:797 0:004 parse func_shutdown status Success 9:801 0:004 parse func_help status Success 9:805 0:004 parse tool_shell status Success 9:807 0:002 parse tool_part status Not Found 9:808 0:000 parse tool_rescue status Not Found 9:808 0:000 parse pointer status Success 9:811 0:002 parse vol_internal status Success 9:816 0:004 parse vol_external status Success 9:820 0:003 parse vol_optical status Success 9:822 0:001 parse vol_firewire status Not Found 9:825 0:003 parse vol_clover status Success 9:831 0:006 parse vol_internal_hfs status Success 9:837 0:006 parse vol_internal_apfs status Success 9:844 0:006 parse vol_internal_ntfs status Success 9:851 0:007 parse vol_internal_ext3 status Success 9:856 0:005 parse vol_recovery status Success 9:859 0:002 parse selection_small status Success 9:863 0:004 parse selection_big status Success 9:881 0:017 parse os_mac status Success 9:893 0:011 parse os_tiger status Not Found 9:904 0:011 parse os_leo status Success 9:937 0:032 parse os_snow status Success 9:975 0:038 parse os_lion status Success 10:011 0:036 parse os_cougar status Success 10:041 0:029 parse os_mav status Success 10:062 0:021 parse os_yos status Success 10:083 0:020 parse os_cap status Success 10:108 0:024 parse os_sierra status Success 10:137 0:029 parse os_hsierra status Success 10:165 0:027 parse os_moja status Success 10:178 0:013 parse os_cata status Not Found 10:191 0:012 parse os_linux status Success 10:216 0:024 parse os_ubuntu status Success 10:239 0:023 parse os_suse status Success 10:262 0:023 parse os_freebsd status Success 10:286 0:023 parse os_freedos status Success 10:309 0:023 parse os_win status Success 10:332 0:023 parse os_vista status Success 10:344 0:011 parse radio_button status Success 10:345 0:000 parse radio_button_selected status Success 10:345 0:000 parse checkbox status Success 10:346 0:000 parse checkbox_checked status Success 10:358 0:011 parse os_unknown i=51 status Success 10:370 0:012 parse os_clover i=52 status Not Found 10:371 0:000 parsing svg theme finished 10:371 0:000 svg file theme.svg not parsed 10:371 0:000 GlobalConfig: BGM_SVG not found, get embedded theme 10:371 0:000 using embedded theme Could it be that BGM_SVG does not include selection_indicator? in /rEFIt_UEFI/libeg/VectorGraphics.cpp //selection for bootcampstyle XIcon *NewIcon = new XIcon(BUILTIN_ICON_SELECTION); Status = ParseSVGXIcon(BUILTIN_ICON_SELECTION, "selection_indicator"_XS8, &NewIcon->Image, &NewIcon->ImageSVG); if (!EFI_ERROR(Status)) { Status = ParseSVGXIcon(BUILTIN_ICON_SELECTION, "selection_indicator_night"_XS8, &NewIcon->ImageNight, &NewIcon->ImageSVGnight); } EDIT: Yes. Success! Adding the selection_indicator code from Clovy theme fixes the issue. 10:306 0:001 parsing svg theme finished 10:306 0:000 Using vector theme 'BGM_SVG' (EFI\CLOVER\themes\BGM_SVG) 10:306 0:000 chosen theme BGM_SVG So why is 'selection_indicator' mandatory for vector themes now? EDIT2: Moving forward, can there be some kind of list of all new additions to Clovy theme which other themes MUST also add? Or can VectorGraphics.cpp be changed to not fail parsing because of a new missing element? EDIT3: It seems my Silver vector theme already had selection_indicator in place and I added it to CloverSgvThemeBuilder in back in January 2019. So my bad for not updating BGM_SVG.
    1 point
  30. @1337ftw, Please provide your problem reporting files as described in Post #1 of this thread. @vbmota, Yes - I am using BrcmPatchRAM3 in E/C/k/O for Mojave (and High Sierra and Catalina). I am using the same EFI and /L/E for ALL three of my macOSes: High Sierra, Mojave and Catalina.
    1 point
  31. @Slice I posted the other day that I could load my BGM_SVG theme with r5117 but I've not been able to load it again since. What I see is the grey background of the embedded theme, with no icons, but the green font is correct.? Looking at bootlog I see 0:103 0:000 === [ GetListOfThemes ] ========================= 0:106 0:002 - [00]: BGM_SVG 0:117 0:010 - [01]: Flat3 0:120 0:003 - [02]: Clovy .... 7:426 0:000 === [ InitXTheme ] ============================== 7:463 0:037 Theme view-bounds: w=1366.000000 h=768.000000 units=px 7:463 0:000 using scale 1.406250 7:549 0:086 Background parsed [1688, 1080] 7:550 0:000 Banner position at parse [594,164] 7:556 0:006 parsed banner->width=741 height=411 8:056 0:500 got day icon 24 name{selection_small} 8:056 0:000 got day icon 23 name{logo} 8:056 0:000 got day icon 101 name{scrollbar_holder} 8:056 0:000 got day icon 45 name{os_vista} 8:056 0:000 got day icon 46 name{radio_button} 8:056 0:000 got day icon 47 name{radio_button_selected} 8:056 0:000 got day icon 48 name{checkbox} 8:056 0:000 svg file theme.svg not parsed 8:056 0:000 theme BGM_SVG chosen from nvram is absent, using theme defined in config: BGM_SVG 8:088 0:031 Theme view-bounds: w=1366.000000 h=768.000000 units=px 8:088 0:000 using scale 1.406250 8:172 0:084 Background parsed [1688, 1080] 8:172 0:000 Banner position at parse [594,164] 8:179 0:006 parsed banner->width=741 height=411 8:679 0:500 got day icon 24 name{selection_small} 8:679 0:000 got day icon 23 name{logo} 8:679 0:000 got day icon 101 name{scrollbar_holder} 8:679 0:000 got day icon 45 name{os_vista} 8:679 0:000 got day icon 46 name{radio_button} 8:679 0:000 got day icon 47 name{radio_button_selected} 8:679 0:000 got day icon 48 name{checkbox} 8:679 0:000 svg file theme.svg not parsed 8:679 0:000 GlobalConfig: BGM_SVG not found, get embedded theme 8:679 0:000 using embedded theme So with 'svg file theme.svg not parsed' I guess there's an error parsing the theme? But why? I have not changed the theme file. EDIT: Scrapped memory question and memmap.. (for now) EDIT2: Testing old clover releases, my guess is it started in Clover r5109. With: r5108 9:525 0:000 === [ InitTheme ] =============================== 9:525 0:000 use daylight theme 9:565 0:039 Theme view-bounds: w=1366 h=768 units=px 9:565 0:000 using scale 1.406250 9:565 0:000 theme contains font-family=PTMono-Regular 9:676 0:111 background parsed 9:677 0:000 Banner position at parse [594,164] 9:704 0:027 Banner parsed 9:704 0:000 parsed banner->width=741 9:723 0:019 icon 9 not parsed take common icons\tool_part 9:723 0:000 icon 10 not parsed take common icons\tool_rescue 9:730 0:006 icon 15 not parsed take common icons\vol_firewire 9:750 0:020 icon main size=[203,203] 9:761 0:011 OSicon os_tiger not parsed 9:901 0:140 OSicon os_cata not parsed 9:983 0:082 OSicon scrollbar_background not parsed 9:984 0:000 OSicon scrollbar_holder not parsed 9:984 0:000 parsing theme finish With: r5110 9:513 0:000 === [ InitXTheme ] ============================== 9:513 0:000 use daylight theme 9:553 0:039 Theme view-bounds: w=1366.000000 h=768.000000 units=px 9:553 0:000 using scale 1.406250 9:691 0:138 Background parsed [1688, 1080] 9:691 0:000 Banner position at parse [594,164] 9:720 0:028 Banner parsed 9:720 0:000 parsed banner->width=741 height=411 10:303 0:583 svg file theme.svg not parsed 10:303 0:000 GlobalConfig: BGM_SVG not found, get embedded theme 10:303 0:000 using embedded theme 10:303 0:000 got embedded sound So with r5109 when big changes where made.. Maybe issue is somewhere in /rEFIt_UEFI/libeg/VectorGraphics.cpp ParseSVGXTheme()? Well done @pkdesign Good to see someone else trying vector themes.
    1 point
  32. Yeah its always been there with me too tbh, I always put it down to macOS but its always bugged me as to why it happens. I never thought it was OC or any other boot loader related. When you have OCD like I do it can send you a little loopy but mind you I'm little loopy full stop..
    1 point
  33. For the love of all things good and hackable, can some kind person please look through my EFI Folder and tell me what I am missing causing a previous Boot-Chime working in OC 0.5.8 not to work in OC 0.5.9 - Cold boot, hot boot, different permutations you name I done it. I went to bed at 3.00 am this morning mumbling to my self with the wife threatening to send me to the spare bedroom. I am not desperate to have it's just the thought that something so simple (well I thought it was) is doing my head in. I don't usually ask for help, I tend to quietly just to figure things out, nothing to with pride just scared of looking and sounding stupid but as the saying goes ...'A Faint Heart Never ....... etc, etc. Ok enough of the mindless rambling please save my sanity, my marriage (rambling again!!!) and my Hack, take a look at the folder please (personal data removed) Thanks. EFI.zip
    1 point
  34. As far as I am aware between the two MacBookPro15,X and MacBookPro16,1 have no differences besides cosmetic The 9th gen and 8th gen Intel CPUs are both Coffee Lake https://en.wikipedia.org/wiki/Coffee_Lake
    1 point
  35. @arsradu, stuff like that is often caused by APFS. With time it may need maintenance across the reboots like snapshot cleaning, trim, and so on. You can always inspect the verbose log for more details.
    1 point
  36. @arsradu please upload your compiled release binary from master if it does not work for you.
    1 point
  37. You have a valid point. We still need to determine whether it's AudioDxe or OpenCore. For what I can tell, I'd say it's AudioDxe. And, for what I can tell, this doesn't look random. In fact, with AudioDxe from AppleSupport 2.1.7 (the one I posted above, the one I was using with 0.5.8) combined with latest OC 0.5.9, I DO have boot sound. Reliably. 5 consecutive restarts with NVRAM reset in between. And no change to anything else. The only thing I'm noticing (but that might be normal), is a slight delay in playing the sound immediately after NVRAM reset. If you fully boot up and then restart, it doesn't occur. But just after reset NVRAM, you will likely only hear the last part of the boot chime, right before the picker is displayed. But as I said, it could be normal. Or could be something specific to my machine. And also, it's still better than the AudioDxe from 0.5.9, which, in my tests, doesn't play at all. I did not try debug version of 0.5.9... Not sure why that would be any different. But I can try, and come back with more details. Also, I tried to narrow down the issue to a specific commit of AppleSupportPkg, but...just like with OpenCore, I can't build older commits... So, the only thing I can tell is that something happened from May 4th (the date of the 2.1.7 AppleSupport pkg, which, at least for me, when it comes to AudioDxe, works fine, including with OpenCore 0.5.9) and today. I saw a few commits regarding AudioDxe in this timeframe. So...maybe one of those breaks something. But, as I said, I can't build, so I can't test. UPDATE: Looks like @MacNB was right. It does make a difference whether it's AudioDxe DEBUG or RELEASE. The Debug version works, indeed. But the Release one does not. Here's the test results (all tests are using only the latest OC 0.5.9, just mixing Debug with Release): OC release + AudioDxe release - doesn't work (no boot sound) OC debug + AudioDxe debug - works OC debug + AudioDxe release - doesn't work (no boot sound) OC release + AudioDxe debug - works
    1 point
  38. run this in terminal and see what's the output: sysctl -n machdep.cpu.brand_string if the results is the exact model of your CPU then what's shown in the About This Mac is cosmetic which can also be changed by adding the correct CPU type in the config.
    1 point
  39. Well actually there is Only one branch of OC and is the one you'r actually posting in, then, wouldn't be a bad idea if you took the time to read a bit around this thread, just to have at least an idea of what's going on... Anyway his fork as it is should build normally since it's around 2 weeks ndk Does not update his OC fork... and around one month for the bootpicker Looking at the names your directories have i would suppose there's something wrong in the way you get them, OpenCorePkg-master is nowhere to be found simply because it does not exists. If you are not familiar on how to get files from git, you will find plenty of informations just reading a few posts. If you'r trying to get the bootpicker working with last OC (official) just forget it... it will never happen, to get a working copy you should get the branch for 0.5.8 from git and build against it. Themes/Default is the directory where you have all the icons, and its still there, Not to be rude but since you as far as i can see, you just have 2 posts in this forum, wouldn't be a bad idea to first reading around, As I just suggested to Oxone, same goes for you
    1 point
  40. @kidooe That's nothing to worry about and it happens sometimes if both devices don't agree on the best speed. it's a hardware issue which can be resolved easily with manual intervention. Mieze
    1 point
  41. So...while in isolation....with some time... I built 0.5.9. Bootchime works fine for me using the newly generated AudoDxe.efi. I tried to break it by changing the .efi driver order (I put AudioDxe.efi last in the list of Drivers) but it still produced a chime. I was using the DEBUG version. Have not tried the RELEASE version (yet).
    1 point
  42. I would like to share the results of experiments with CPU microcode updates. The current BIOS v3102 has a version of 0x02000060 CPU microcodes. UBU 1.77 Utility allows you to upgrade to version 0x02006901. Before 0х02006901 there were versions 0х02000064, 0х02000065, 0х02000068 but the version 0х02006901 is the newest at the moment. CPU microcode update went without problems. And BIOS update as well (via the flashback). And I was hoping to see some changes, especially with the non-functional Configure Lock. However, no changes have taken place, is ConfigureLock enabled/disabled, MSR 0xE2 still locked. Therefore, you should probably not expect a positive from future versions of the BIOS with newer versions of CPU microcodes. And probably problem is in some other place... Many users reported same situation with MSR 0xE2 when lock/unlock switcher presented in new Cascade Lake BIOS but has no effeckt. @maleorderbride, what is situation on you Asrock x299 MoBo with MSR 0xE2? Also: ASUS WS C422 Pro/SE still boot OK on untouched Cascade Lake BIOS (v3003, v3102) + Clover + kernel patches for locked MSR 0xE2 and 0x1AA + SSDT.aml for AWAC device. Also Serial Port always enabled in my BIOS and no problems, still supported in Catalina and probably still can do work Because you has no success with patched BIOS, may be best way is find reason non bootablity on untouched Cascade Lake BIOS? @obus, KP during wakeup still persist(on unlocked and microcode updated BIOS 3102). Thank you. And sorry my google translated English.
    1 point
  43. @Alectardy98 appleALC is not responsible for bluetooth audio the fault with you has another cause yes, ALCPlugFix no longer necessary with ID15 I will look at Mic again in the next few days @EmiZanotti (trial1) The coupling of the two internal speakers in MidiSetup makes no sense if both internal speakers do not output any sound. (trial2) In the second Kext I tried to connect the connections directly in AppleALC, which apparently does not work.
    1 point
  44. I've built and bundled ophcrack version 3.8.0 for Catalina. Enjoy Windows password cracking ophcrack.zip
    1 point
  45. Hi, I'm using the OpenCore 058 Z390 Mater 1,1 040520 EFI Folder. This contains an USBPorts.kext. I guess that kext is responsible for the missing USB ports. How can I make my own port mapping? Just remove the USBPorts.kext and use Hackintool to create a new one?
    0 points
  46. Ordered a PCI-e 4 port SATA card off eBay and it arrived yesterday. https://www.ebay.com.au/itm/SATA3-0-4Port-6G-PCI-E-to-SATA3-0-Expansion-Card-SSD-HDD-Adapter-Controller-Card/114124787125?ssPageName=STRK%3AMEBIDX%3AIT&amp;_trksid=p2057872.m2749.l2649 Couldn't get it to work showing all drives last night. Today got home and applied this kext patch in the Clover config file and now works fine. Find --> 40600200 Replace --> 00000000 AppleAHCIPort On another note I sometimes have an issue when booting, only occurs occasionally (maybe AppleAHCIPort might fix it :)). Just recently converted to NVME boot drive and using AudioGods latestest EFI and config file using clover. Image attached, any ideas? I'm assuming its something that needs to be tweaked in the boot arguments.
    0 points
×
×
  • Create New...