Sniki Posted November 24, 2020 Share Posted November 24, 2020 Question regarding Ivy Bridge DRM. What is the best solution / combo for Ivy Bridge on Big Sur to have working DRM content / AppleTV. (SMBIOS & shikigva ) Seems tricky right now both for IGPU and DGPU desktops. Link to comment Share on other sites More sharing options...
MacNB Posted November 25, 2020 Share Posted November 25, 2020 10 hours ago, Sniki said: Question regarding Ivy Bridge DRM. What is the best solution / combo for Ivy Bridge on Big Sur to have working DRM content / AppleTV. (SMBIOS & shikigva ) Seems tricky right now both for IGPU and DGPU desktops. Your question is not related to OpenCore so it is really off topic here. However, here is my observation. I have an Ivy Bridge rig with RX580 but I do not use it for watching Netflix, prime, etc BUT I do use it to encode/decode H.263 & HEVC. The only combo/solution I have is to get macOS to use the RX580 for encode/decode of those codecs by setting the Model ID iMacPro1,1 AND disable the IGPU in BIOS. If the IGPU is enabled, the CPU is used for HEVC decode/encode and the IGPU is used for H.264 decode. To continue this convo, I suggested you move it to the Graphics forum. Link to comment Share on other sites More sharing options...
149113 Posted November 25, 2020 Share Posted November 25, 2020 21 hours ago, Max.1974 said: @149113 thanks for information, are you can explain in details or show your config.plist? Its because i have 2 OC EFI, one is for desktop and boot up Windows 7 normally without issue. But another, for my Lenovo, just up with Clover, i have no idea why, because both plist are the same, just different on drivers and kexts... Attaching my config.plist. I did not need to add any Windows 10 entries to my config file. Opencore just finds the EFI information on my Windows 10 instance and it appears as an additional icon in the Opencore menu. I think it helps to have Windows installed on a second NVMe drive config.plist 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted November 25, 2020 Share Posted November 25, 2020 (edited) On 11/25/2020 at 10:12 AM, 149113 said: Attaching my config.plist. I did not need to add any Windows 10 entries to my config file. Opencore just finds the EFI information on my Windows 10 instance and it appears as an additional icon in the Opencore menu. I think it helps to have Windows installed on a second NVMe drive config.plist Thanks my friend, im will try your plist...!!! Edit: Hi all, im spend few days (and nights) try put BS with Opencore EFI together with Windows in Dual boot at the same drive for my Laptop. Almost impossible with compiled DSDT. Im not advanced user, but if some good soul could explain why DSDT cause crash with Windows boot, im will appreciate that. Im try everything that Bless Entries or UUID etc, without success. With SSDT from Olarila, boot fine on Windows, and BS, but problems with BT not working good. If is possible, someone understand, like developers, a part or section on DSDT that cause this issue, and if will be possible use OpenCore to make bootable in Dual Boot. Clover was nice, im using with Catalina, but my knowledge not reach on this level to make boot on Big Sur, and i have perfect EFI from OC (and I like him now more Thant Clover) to install and run High Sierra, Catalina, and Big Sur, but not work on Windows. Thanks guys, always your effort. Edited November 26, 2020 by Max.1974 Link to comment Share on other sites More sharing options...
HenryV Posted November 26, 2020 Share Posted November 26, 2020 (edited) What is IO80211Family.kext not loading issue with open core 0.6.3/0.6.4 and Big Sur 11.0.1? Booting Big Sur 20B29 with OC securebootmodel disabled and IO80211Family.kext not loading as confirmed by kextstat | grep IO80211Family.kext. Then I find this: Set SecureBootModel to Default to make sure IO80211Family loads properly. Workaround for Users with Prelinked Kernel without ImmutableKernel Force IO80211Family to load. 「Supports OpenCore and Clover(not tested)」 (Read the Kernel - Force section in OpenCore's manual for more info) Load AirportItlwm from Terminal (Continuity features may not work) Extract IO80211Family from the system, insert AirportItlwm as a Plugin, and load the bundle with a bootloader. Or disable SIP and install AirportItlwm into /Library/Extensions (Take your own risk) The latter two methods are not recommended, hence details are not provided. So set SecureBootModel to Default and no boot with security warning. Then I find this: https://dortania.github.io/OpenCore-Post-Install/universal/security/applesecureboot.html#special-notes-with-securebootmodel Troubleshooting Due to an annoying bug on Apple's end, certain systems may be missing the secure boot files themselves on the drive. Because of this, you may get issues such as: OCB: LoadImage failed - Security Violation To resolve, run the following in macOS: # First, find your Preboot volume diskutil list # From the below list, we can see our Preboot volume is disk5s2 /dev/disk5 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +255.7 GB disk5 Physical Store disk4s2 1: APFS Volume Big Sur HD - Data 122.5 GB disk5s1 2: APFS Volume Preboot 309.4 MB disk5s2 3: APFS Volume Recovery 887.8 MB disk5s3 4: APFS Volume VM 1.1 MB disk5s4 5: APFS Volume Big Sur HD 16.2 GB disk5s5 6: APFS Snapshot com.apple.os.update-... 16.2 GB disk5s5s # Now mount the Preboot volume diskutil mount disk5s2 # CD into your Preboot volume # Note the actual volume is under /System/Volumes/Preboot in macOS # however in Recovery it's simply under /Volumes/Preboot cd /System/Volumes/Preboot # Grab your UUID ls 46923F6E-968E-46E9-AC6D-9E6141DF52FD CD844C38-1A25-48D5-9388-5D62AA46CFB8 # If multiple show up(ie. you dual boot multiple versions of macOS), you will # need to determine which UUID is correct. # Easiest way to determine is printing the value of .disk_label.contentDetails # of each volume. cat ./46923F6E-968E-46E9-AC6D-9E6141DF52FD/System/Library/CoreServices/.disk_label.contentDetails Big Sur HD% cat ./CD844C38-1A25-48D5-9388-5D62AA46CFB8/System/Library/CoreServices/.disk_label.contentDetails Catalina HD% # Next lets copy over the secure boot files, recovery will need different commands # Example commands for inside macOS # Replace CD844C38-1A25-48D5-9388-5D62AA46CFB8 with your UUID value cd ~ sudo cp -a /usr/standalone/i386/. /System/Volumes/Preboot/CD844C38-1A25-48D5-9388-5D62AA46CFB8/System/Library/CoreServices # Example commands for Recovery # Replace Macintosh\ HD and CD844C38-1A25-48D5-9388-5D62AA46CFB8 with # your System Volume's name and Preboot's UUID cp -a /Volumes/Macintosh\ HD/usr/standalone/i386/. /Volumes/Preboot/CD844C38-1A25-48D5-9388-5D62AA46CFB8/System/Library/CoreServices Now you can enable SecureBootModel and reboot without issue! And since we're not editing the system volume itself we don't need to worry about disabling SIP or breaking macOS snapshots. So after copying the boot keys per above directions and SecureBootModel re-enabled still get the security warning. OCB: LoadImage failed - Security Violation Is there a resolution to this? itlwm/AirportItlwm/Heliport.app worked fine in beta with SecureBootModel disabled but with 20B29 11.0.1 SecureBootModel has to be enabled to load IO80211Family.kext? Is this an issue with open core? Update 091220: Itlwm/AirportItlwm/Heliport issues resolved with firmware update. Edited December 9, 2020 by HenryV resolved 2 Link to comment Share on other sites More sharing options...
AntarcticP Posted November 28, 2020 Share Posted November 28, 2020 Hi I have a working version of Big Sur installed on a fresh SSD, AMD Fx system (990fxa-UD5, fx8350 processor, AMD580x graphics). Booting from my OpenCore USB stick works perfectly. I copied the content of my USB to the SSD EFI partition. So I would expect this would work, like it always did in the past with all previous MacOS versions. Not this time. When I select the Big Sur in the boot picker, I get an immediate kernel panic. I included the OpenCore log for the 'Working USB' and the 'Not working SSD' EFI. Again, it's an exact copy, so I do not get why this does not boot. Has anyone seen this before? Thanks! Opencore logs.zip Link to comment Share on other sites More sharing options...
H4cktosh Posted November 29, 2020 Share Posted November 29, 2020 (edited) hi i have installed latest big sur on my laptop (Specs are on my Signature) and provisly installed High Sierra and used for years but yesterday when i boot to macos HS for first time after BS installation, the Big Sur Boot volume is Disappeared from opencore boot menu. i have try to reinstall Big sur one more time. but when i boot to high sierra big sur boot entry is disappear Edited November 29, 2020 by H4cktosh Link to comment Share on other sites More sharing options...
TheBloke Posted November 29, 2020 Share Posted November 29, 2020 (edited) Hi all Is it normal when installing Big Sur - or updating to Big Sur - for the filesytem seal to be broken? Like this: The above screenshot is taken from a brand new Big Sur 11.0.1 install, to a blank drive. But the same also happens if I update an existing Catalina install to Big Sur. I have working NVRAM. I am using OpenCore 0.6.3. I have SecureBootModel = j160 (for MacPro 7,1 SMBIOS). I installed with SIP fully disabled (csr-active-config = 00000000). I have not modified the system filesystem, and this happens on a brand new fresh install. Is this expected, or is something wrong? Do I need to set ApECID for Full Security in order to avoid the seal being broken? I'm quite confused about this, as I am not sure what is the normal/expected result. Thanks in advance for any info. Edited November 29, 2020 by TheBloke Link to comment Share on other sites More sharing options...
eSaF Posted November 29, 2020 Share Posted November 29, 2020 16 minutes ago, TheBloke said: Is it normal when installing Big Sur - or updating to Big Sur - for the filesytem seal to be broken? Like this: This appears to be normal, whether this is how it now appears with these latest BS versions Released and Betas is any ones guess. As you said your installation is a fresh install so you have nothing to worry about it also appears like that on my system (see attached) and my system is rock solid. You do not need to set ApECID for Full Security leave it as it is in the config.plist. 1 Link to comment Share on other sites More sharing options...
TheBloke Posted November 29, 2020 Share Posted November 29, 2020 Thanks @eSaF - yes now I'm thinking maybe every Hackintosh has a broken seal. At the least, everyone I've asked has the same thing. 1 Link to comment Share on other sites More sharing options...
eSaF Posted November 29, 2020 Share Posted November 29, 2020 3 minutes ago, TheBloke said: Thanks @eSaF - yes now I'm thinking maybe every Hackintosh has a broken seal. At the least, everyone I've asked has the same thing. Actually the Snapshot is still sealed for security reasons, if you look at the bottom of the printout you will see what I mean. Link to comment Share on other sites More sharing options...
TheBloke Posted November 29, 2020 Share Posted November 29, 2020 Yeah I saw that. I don't entirely understand the difference between the snapshot being sealed but the filesystem itself not being. Does it imply that the filesystem seal was broken after the snapshot was taken? Would that suggest that rolling back to the snapshot would re-seal the main FS? Though actually I just re-read the Dortania guide and realised I had mis-read it before. The Dortania guide says to look for the snapshot being sealed, not the main FS So on that basis, our systems do check out OK. I'd still like to understand why exactly the main FS shows "Sealed: Broken" and whether that has any implications or not. But I do see now that actually I'm not seeing anything unexpected. 1 Link to comment Share on other sites More sharing options...
ameenjuz Posted November 30, 2020 Share Posted November 30, 2020 anyone know exactly how to install kexts in /L/E and rebuild kernel colloction in Big Sur 11.0.1 released version i do this following procedure but do not work and corruppted my boot system sudo cp -R *kexts /Library/Extensions sudo touch /Library/Extensions && sudo kmutil install --volume-root / --update-all sudo /usr/sbin/kcditto anyone guide me about rebuilding kernel colloction using terminal Link to comment Share on other sites More sharing options...
HenryV Posted November 30, 2020 Share Posted November 30, 2020 (edited) Manually install kexts to System/Library/Extensions. Change the paths for /Libary/Extensions You need to enter recovery mode, open terminal, type at prompt csrutil status hit enter verify response is "disabled" if not run at prompt: csrutil disable type at prompt csrutil authenticated-root status hit enter verify response is "disabled" if not run at prompt: csrutil authenticated-root disable reboot into recovery mode if required open terminal, at prompt run: mount hit enter verify volumes, disk numbers, slices. confirm with: diskutil list at prompt type: diskutil mountDisk diskXsY where X is the Big Sur disk number and Y is the Big Sur slice. hit enter , at prompt type: mount -uw /Volumes/your Big Sur volume name hit enter at prompt type: mount hit enter Your Big Sur volume should no longer indicate read-only at prompt: cp -r where/ever/your/kext/is/whatever.kext /Volumes/your Big Sur volume name/System/Library/Extensions hit enter for each kext: at prompt: chown -R 0:0 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext && chmod -R 755 /Volumes/your Big Sur volume name/System/Library/Extensions/target.kext hit enter then type at prompt: touch /Volumes/your Big Sur volume name/System/Library/Extensions/whatever.kext(s) hit enter then type at prompt: kmutil install --volume-root /Volumes/your Big Sur volume name --update-all --force hit enter, wait for finish then type at prompt: /Volumes/your Big Sur volume name/usr/sbin/kcditto hit enter, wait for finish then type at prompt: bless --folder /Volumes/your Big Sur volume name/System/Library/CoreServices --bootefi --create-snapshot hit enter, wait for finish reboot Edited November 30, 2020 by HenryV remvised to insert SIP disable check 1 Link to comment Share on other sites More sharing options...
HenryV Posted November 30, 2020 Share Posted November 30, 2020 (edited) itwlm/Heliport/AirportItlwm Problem: Fresh reinstall. Clover 5127 and Open Core 0.6.4 booting Big Sur both load kexts with subsequent failure to detect networks on 20B29 11.0.1. Big Sur beta loaded itlwm/Heliport and detected networks without issues. Clover 5122 booting Catalina, all works well with itlwm and Heliport. What gives? Is this a Bug Sur issue or bootloader issue or both? Doing something wrong? Only thing have seen is different is that IONetworkingFamily version number from the AirportItlwm dependency info.plist and the installed system IONetworkingFamily version number. Anyone have a clue? Update 091220: Itlwm/AirportItlwm/Heliport issues resolved with firmware update. Edited December 9, 2020 by HenryV resolved Link to comment Share on other sites More sharing options...
Modmike Posted December 1, 2020 Share Posted December 1, 2020 I'm running OpenCore 5.7 on Catalina. My board is an Asus Z390 with a 1560 wifi card. Everything has been working well for 8 months until I updated to 6.3 and lost wifi. Any tips? 1 Link to comment Share on other sites More sharing options...
Tecnicaso Rico Posted December 1, 2020 Share Posted December 1, 2020 2 hours ago, Modmike said: I'm running OpenCore 5.7 on Catalina. My board is an Asus Z390 with a 1560 wifi card. Everything has been working well for 8 months until I updated to 6.3 and lost wifi. Any tips? There are two injectors inside AirportBcrmFixup.kext. Check if AirPortBcrm4360_Injector,kext is set to False. 3 Link to comment Share on other sites More sharing options...
Max.1974 Posted December 1, 2020 Share Posted December 1, 2020 Try this config on OpencoreConfigurator: uncheck that kext partial on Kernel section. If you need see this video too: "How to make wifi broadcom work in MacOS Big Sur Beta 2 on Hackintosh OpenCore" Works fine for me... Lenovo and GA Z270 i7 1 Link to comment Share on other sites More sharing options...
HenryV Posted December 1, 2020 Share Posted December 1, 2020 (edited) 1Revenger1 can not receive messages. Thank you for your reply. Can you tell me how best to resolve this: https://www.insanelymac.com/forum/topic/338516-opencore-discussion/?page=262 itlwm/Heliport/AirportItlwm Problem: Fresh reinstall. Clover 5127 and Open Core 0.6.4 booting Big Sur both load kexts with subsequent failure to detect networks on 20B29 11.0.1. Big Sur beta loaded itlwm/Heliport and detected networks without issues. Clover 5122 booting Catalina, all works well with itlwm and Heliport. What gives? Is this a Bug Sur issue or bootloader issue or both? Doing something wrong? Only thing have seen is different is that IONetworkingFamily version number from the AirportItlwm dependency info.plist and the installed system IONetworkingFamily version number. Anyone have a clue? wifi log: Mon Nov 30 20:55:35.713 Usb Host Notification NOT activated Mon Nov 30 20:55:35.750 <airport[193]> _bsdDriver_init: registration for monitoring bssSteeringRequest event Mon Nov 30 20:55:35.750 Mon Nov 30 20:55:35.750 <airport[193]> psCallback: set powersave(7) failed, 5 (Input/output error) Mon Nov 30 20:55:35.793 <kernel> Not adding subscription due to missing boot-arg wlan.iorsubscriptions Mon Nov 30 20:55:35.906 <kernel> Not adding subscription due to missing boot-arg wlan.iorsubscriptions Mon Nov 30 20:55:35.917 <kernel> Creating all peerManager reporters Mon Nov 30 20:55:36.102 <airport[193]> _initLocaleManager: Started locale manager Mon Nov 30 20:55:36.102 <airport[193]> _initInterface: Failed to query current SSID (Input/output error) Mon Nov 30 20:55:36.167 <airport[193]> airportdProcessDLILEvent: <en1> event=9, flags=0xFFFF8863, lastPowerPref=off Mon Nov 30 20:55:36.167 <airport[193]> airportdProcessDLILEvent: en1 attached (up) Mon Nov 30 20:55:36.235 <airport[193]> _bsdDriver_init: registration for monitoring bssSteeringRequest event Mon Nov 30 20:55:36.235 Mon Nov 30 20:55:36.236 <airport[193]> psCallback: set powersave(7) failed, 5 (Input/output error) Mon Nov 30 20:55:36.236 <airport[193]> psCallback: set powersave(7) failed, 5 (Input/output error) Mon Nov 30 20:55:36.253 <airport[193]> _bsdDriver_init: registration for monitoring bssSteeringRequest event Mon Nov 30 20:55:36.253 Mon Nov 30 20:55:36.253 <airport[193]> psCallback: set powersave(7) failed, 5 (Input/output error) Mon Nov 30 20:55:36.253 <airport[193]> psCallback: set powersave(7) failed, 5 (Input/output error) Mon Nov 30 20:56:39.598 <airport[193]> ERROR: ControlCenter (474) is not entitled for com.apple.wifi.events, but allowing anyways for event type 2 Mon Nov 30 20:56:53.092 <airport[193]> Could not set property APPLE80211_REGKEY_AWDL_MAC_ADDRESS_IN_USE to 0 Mon Nov 30 20:56:53.122 <airport[193]> Could not set property APPLE80211_REGKEY_AWDL_MAC_ADDRESS_IN_USE to 0 Mon Nov 30 20:57:12.220 <kernel> en1: setting diversity to: -1 Mon Nov 30 20:57:12.220 <kernel> en1: Error configuring antenna diversity (index = -1). Mon Nov 30 20:57:12.220 <kernel> en1: setting tx antenna: -1 Mon Nov 30 20:57:12.220 <kernel> en1: Error configuring transmit antenna (index = -1). Mon Nov 30 20:57:12.247 <kernel> Setting BTCoex Profile: band:8 Mon Nov 30 20:57:12.247 <kernel> Profile[0]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:12.247 <kernel> Profile[1]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:12.247 <kernel> Profile[2]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:12.250 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:13.471 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:19.683 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:22.680 <kernel> IO80211VirtualInterface::handleSIOCSIFFLAGS : Source handleIoctlGated calling peerManager->disable Mon Nov 30 20:57:24.370 <kernel> en1: setting diversity to: -1 Mon Nov 30 20:57:24.370 <kernel> en1: Error configuring antenna diversity (index = -1). Mon Nov 30 20:57:24.370 <kernel> en1: setting tx antenna: -1 Mon Nov 30 20:57:24.370 <kernel> en1: Error configuring transmit antenna (index = -1). Mon Nov 30 20:57:24.376 <kernel> Setting BTCoex Profile: band:8 Mon Nov 30 20:57:24.378 <kernel> Profile[0]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.378 <kernel> Profile[1]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.378 <kernel> Profile[2]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.399 <kernel> Setting BTCoex Profile: band:8 Mon Nov 30 20:57:24.399 <kernel> Profile[0]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.399 <kernel> Profile[1]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.399 <kernel> Profile[2]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.400 <kernel> Setting BTCoex Profile: band:8 Mon Nov 30 20:57:24.400 <kernel> Profile[0]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.400 <kernel> Profile[1]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.400 <kernel> Profile[2]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.404 <kernel> Setting BTCoex Profile: band:8 Mon Nov 30 20:57:24.404 <kernel> Profile[0]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.404 <kernel> Profile[1]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.404 <kernel> Profile[2]: mode:0; desense:0; desense_level:0; chain_power_offset:<kernel> 0,<kernel> 0,<kernel> 0,<kernel> 0,<kernel> Mon Nov 30 20:57:24.865 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:26.074 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:27.079 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:28.085 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:29.091 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:30.099 <airport[193]> systemWokenByWiFi: System Wake Reason not found Mon Nov 30 20:57:32.406 <kernel> IO80211VirtualInterface::handleSIOCSIFFLAGS : Source handleIoctlGated calling peerManager->disable Mon Nov 30 21:32:38.766 Usb Host Notification NOT activated Edited December 2, 2020 by HenryV Code tag/typo Link to comment Share on other sites More sharing options...
AlfredoM Posted December 5, 2020 Share Posted December 5, 2020 No Schema how can I make the error messages "No Schema" .... always visible? These (there are probably about 6 messages) go away within 1 second and then the boot menu comes up, so that I can't read where the individual errors for "No Schema" are. Is there an option when booting with Open Core 0.6.3? Thanks for tips. 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted December 5, 2020 Share Posted December 5, 2020 4 hours ago, AlfredoM said: No Schema how can I make the error messages "No Schema" .... always visible? These (there are probably about 6 messages) go away within 1 second and then the boot menu comes up, so that I can't read where the individual errors for "No Schema" are. Is there an option when booting with Open Core 0.6.3? Thanks for tips. Do you check your config.plist via OcValidate utility ! 1 Link to comment Share on other sites More sharing options...
luky35 Posted December 5, 2020 Share Posted December 5, 2020 (edited) In OC EFI, I have a normal itlwm and Airporttiliwm and when I turn on my pc, it doesn't show any wifi connection. Can you please look at the attached config.plist? Thanks. config.plist.zip Edited December 5, 2020 by luky35 Link to comment Share on other sites More sharing options...
TheBloke Posted December 5, 2020 Share Posted December 5, 2020 6 minutes ago, luky35 said: In OC EFI, I have a normal itlwm and Airporttiliwm and when I turn on my pc, it doesn't show any wifi connection. Can you please look at the attached config.plist? Thanks. You must not use itlwm and AirportItlwm at the same time. Use one or the other. You should read the Itlwm docs carefully: https://openintelwireless.github.io/itlwm/Installation.html Link to comment Share on other sites More sharing options...
luky35 Posted December 5, 2020 Share Posted December 5, 2020 14 minutes ago, TheBloke said: You must not use itlwm and AirportItlwm at the same time. Use one or the other. You should read the Itlwm docs carefully: https://openintelwireless.github.io/itlwm/Installation.html What about itlwm + Heliport? Link to comment Share on other sites More sharing options...
TheBloke Posted December 5, 2020 Share Posted December 5, 2020 2 minutes ago, luky35 said: What about itlwm + Heliport? Yes, if you use itlwm you need Heliport. But that's an application, not a kext. Read the instructions on the link I sent you carefully, all the info is there. 1 Link to comment Share on other sites More sharing options...
Recommended Posts