Humour me

[keef247]

OK, so I updated my EFI to contain the latest OpenCore and Kexts.
I then wasted an hour with the seriously lacking guide for USBMap off the Github page:

GitHub - corpnewt/USBMap at tahoe-test

Python script for mapping USB ports in macOS and creating a custom injector kext. - GitHub - corpnewt/USBMap at tahoe-test

github.com

This seems to lack quite a lot of info

For a start, does it actually save/update my existing USBMap file in it's original location, once I've updated it? Or does it place it somewhere? It doesn't add another to the Results folder, unless you choose a different option.

Regarding the USBMap files, I used USBToolBox original for Sequoia and previous OS versions - I've never had a problem?
So all I have relating to USB mapping kexts, are USBToolBox.kext and UTBMap.kext - that's it?
When you goto update/modify the files using USBMap.command, it doesn't seem to mention these files but does support opening them in USBMapInjectorEdit.command ?

What I want to know is, are the USBToolBox.kext and UTBMap.kext files even supported in Tahoe? Or do I mess with them in USBMap.command and export them with the same filenames I currently use i.e. 'USBToolBox.kext and UTBMap.kext'?
When watching or reading any guide, they simply mention pasting the modified version of 'USBMap.kext' into your kexts - I've never had this file? Only the aforementioned above files?
Then what, do you then use ProperTree (what I always use) to do a CleanOCSnapShot like before with these files and add the entries to update the config.plist to support Tahoe?

The Github guide for USBMap is honestly so lacking and rubbish, it goes so vague when it comes to updating the config.plist and conflicts with what I've red on other guides?

I'm properly stuck here! It's very frustrating as this shouldn't be hard to do?

When I try and boot off the installer, I just get a No Entry symbol with apple.com/support - which obviously doesn't tell me anything.

Also I've red elsewhere that using IntelBluetoothPatcher, could cause issues running the installer or Tahoe itself - something I need to use.

Even if I create this USBPorts.kext - what do I do with it once I've pasted it into my Kexts folder and preformed a 'CleanOCSnapshot' in ProperTree? As I never had this file before, as I was using USBToolBox.kext and UTBMap.kext - so how will my EFI/config.plist know what to do with it, or the installer?

@Edhawk @Shaneee any ideas mate?

 

[Edhawk]

What I want to know is, are the USBToolBox.kext and UTBMap.kext files even supported in Tahoe?

No, as they lack the additional USB port entries required for Tahoe.

This is a screenshot of my old USBMap.kext for my Asus X570 system. Showing the first USB controller XHC1.
Works in Catalina to Sequoia, but not in Tahoe.

This is a screenshot of my new USBMap.kext for the Asus X570 system. Showing part of the first USB Controller XHC (previously was named XHC1).
Works in Catalina to Tahoe.

You can see the highlighted entries in the new USBMap.kext/Contents/Info.plist. These are required for the ports to work in Tahoe.

Neither USBPorts.kext or UTBMAp.kext add these additional entries, so neither USB kext will work in Tahoe.

Using USBMap is very similar to using USBToolBox Tool in Windows. As USBToolBox Tool was a Windows clone of the USBMap script. If you know how to create a UTBMap.kext then you already know how to generate a USBMap.kext. The instructions in the script Terminal window are nearly identical.

When you have created the new USBMap.kext simply, which will be generated in the 'Results' folder within the USBMap-Master folder, copy it to your /EFI/OC/Kexts folder and add an entry for the kext to your config.plist.

You will need to remove the USBToolBox.kext and UTBMap.kext files and config.plist entries, as you should never use two USB configurations in your OC setup.

When I try and boot off the installer, I just get a No Entry symbol with apple.com/support - which obviously doesn't tell me anything.

The Error message you are seeing is USB related, basically the system drops the USB port you are using to install macOS Tahoe and so the installation kernel panics. You could try using a different USB port to see if the installation continues. A USB 2 port would be the best option, if your motherboard contains one on the rear I/O plate.

It is commonly advised to use a really pared down set of kexts in OpenCore when installing macOS Tahoe. To prevent any issues. Any kext you remove can be added back once you are on the Tahoe Desktop. Problematic kexts include but are not limited to to the following:

• WhateverGreen.kext
• AppleALC.kext
• Bluetooth kexts
• Sensor kexts

AppleALC.kext can't be added to the OpenCore setup, as Apple have dropped the use of AppleHDA.kext from Tahoe. There is a work around for this issue. But you need to get Tahoe installed before you attempt that fix. I have attached a link on how to fix the AppleHDA issue in Tahoe.

https://www.tonymacx86.com/threads/how-to-recover-applehda-under-tahoe.332294/

 

[keef247]

No, as they lack the additional USB port entries required for Tahoe.

This is a screenshot of my old USBMap.kext for my Asus X570 system. Showing the first USB controller XHC1.
View attachment 18065 Works in Catalina to Sequoia, but not in Tahoe.

This is a screenshot of my new USBMap.kext for the Asus X570 system. Showing part of the first USB Controller XHC (previously was named XHC1).
View attachment 18066 Works in Catalina to Tahoe.

You can see the highlighted entries in the new USBMap.kext/Contents/Info.plist. These are required for the ports to work in Tahoe.

Neither USBPorts.kext or UTBMAp.kext add these additional entries, so neither USB kext will work in Tahoe.

Using USBMap is very similar to using USBToolBox Tool in Windows. As USBToolBox Tool was a Windows clone of the USBMap script. If you know how to create a UTBMap.kext then you already know how to generate a USBMap.kext. The instructions in the script Terminal window are nearly identical.

When you have created the new USBMap.kext simply, which will be generated in the 'Results' folder within the USBMap-Master folder, copy it to your /EFI/OC/Kexts folder and add an entry for the kext to your config.plist.

You will need to remove the USBToolBox.kext and UTBMap.kext files and config.plist entries, as you should never use two USB configurations in your OC setup.


The Error message you are seeing is USB related, basically the system drops the USB port you are using to install macOS Tahoe and so the installation kernel panics. You could try using a different USB port to see if the installation continues. A USB 2 port would be the best option, if your motherboard contains one on the rear I/O plate.

It is commonly advised to use a really pared down set of kexts in OpenCore when installing macOS Tahoe. To prevent any issues. Any kext you remove can be added back once you are on the Tahoe Desktop. Problematic kexts include but are not limited to to the following:

• WhateverGreen.kext
• AppleALC.kext
• Bluetooth kexts
• Sensor kexts

AppleALC.kext can't be added to the OpenCore setup, as Apple have dropped the use of AppleHDA.kext from Tahoe. There is a work around for this issue. But you need to get Tahoe installed before you attempt that fix. I have attached a link on how to fix the AppleHDA issue in Tahoe.

https://www.tonymacx86.com/threads/how-to-recover-applehda-under-tahoe.332294/

Thanks mate. OK, so I did do some of this but might not have explained it very well lol Sorry about that.

So TLDR, I've already made that USBMap.kext earlier in the Results folder.

Can I simply, delete the USBToolBox.kext and UTBMap.kext and then use Propertree to perform a clean-oc-snapshot, and that'll remove the entries, right?

Then with the newly created USBMap.kext put into my Kexts folder and doing the same thing in Propertree, it should add it to my config.plist - right?

Or use one something like OCAuxileryTools to open my config.plist, and tick the kext for USBMap.kext, save, and then it should 'just work'?

If I use USBMap to make the kext, I take it I don't have to mess about doing the following that I red in another guide:

5. Replace com.apple.driver.AppleUSBMergeNub with com.apple.driver.AppleUSBHostMergeProperties in CFBundleIdentifier and AppleUSBMergeNub with AppleUSBHostMergeProperties in IOClass.

6. Locate IOKitPersonalities and expand ports under IOProvideMergeProperties. You should have something like following

7. Create two New Child with the name usb-port number and usb-port-type in each of the ports (HSXX and SSXX) defined in the mapped kext and set the Class (value type) as Data for usb-port-number and Number for usb-port-type.

8. Match the value with that of the existing configuration i.e. UsbConnector with usb-port-type and port with usb-port-number as explained above. For example, the HS03 has UsbConnector set as 3 (USB 3.0) and port as 03000000 respectively. Similarly, change the values to the new key to match yours.

As USBMapTool, will have done this for me right? Or do I still have to mess about adding stuff to the config.plist myself, despite using USBMapTool to adjust the USBMap.kext file to suit Tahoe?

EDIT:
I forgot to say, I have my onboard LAN and soundcard disabled, and simply use my graphics card's HDMI and DP for sound - so can I delete AppleALC.kext and remove it from my config.plist?

I have WhateverGreen, VirtualSMC, Lilu, itlwm, IntelBTPatcher, IntelBluetoothFirmware, BlueToolFixup, AppleReporterDisabler, and AMDRyzenCPUPowerManagement kext's in my kext folder - so do I even 'need' WhateverGreen, VirtualSMC, Lilu, for a 5700X, B450i, RX 6800?
Thanks again for your help mate!

 

[keef247]

EDIT:
I forgot to say, I have my onboard LAN and soundcard disabled, and simply use my graphics card's HDMI and DP for sound - so can I delete AppleALC.kext and remove it from my config.plist?

I have WhateverGreen, VirtualSMC, Lilu, itlwm, IntelBTPatcher, IntelBluetoothFirmware, BlueToolFixup, AppleReporterDisabler, and AMDRyzenCPUPowerManagement kext's in my kext folder - so do I even 'need' WhateverGreen, VirtualSMC, Lilu, for a 5700X, B450i, RX 6800?
Thanks again for your help mate!

 

[Edhawk]

Can I simply, delete the USBToolBox.kext and UTBMap.kext and then use Propertree to perform a clean-oc-snapshot, and that'll remove the entries, right?

YES.

Then with the newly created USBMap.kext put into my Kexts folder and doing the same thing in Propertree, it should add it to my config.plist - right?

YES.

You could do both at the same time, i.e. only use the OC Clean Snapshot once to undertake both the add and delete actions.

Nothing else is required when using the latest release of USBMap.kext. Just generate the kext with the ports set correctly, then add the kext to your OC setup and it will work in macOS.

Do not use the option to generate the Legacy kext in USBMap. You don't need it in your AMD system running Sequoia or Tahoe. It is for older versions of macOS, such as High Sierra and Mojave.

 

[keef247]

YES.


YES.

You could do both at the same time, i.e. only use the OC Clean Snapshot once to undertake both the add and delete actions.

Nothing else is required when using the latest release of USBMap.kext. Just generate the kext with the ports set correctly, then add the kext to your OC setup and it will work in macOS.

Do not use the option to generate the Legacy kext in USBMap. You don't need it in your AMD system running Sequoia or Tahoe. It is for older versions of macOS, such as High Sierra and Mojave.

Sweet, I'll try that in a second, thanks dude!

Regarding my edit,
I forgot to say, I have my onboard LAN and soundcard disabled, and simply use my graphics card's HDMI and DP for sound - so can I delete AppleALC.kext and remove it from my config.plist?

I have WhateverGreen, VirtualSMC, Lilu, itlwm, IntelBTPatcher, IntelBluetoothFirmware, BlueToolFixup, AppleReporterDisabler, and AMDRyzenCPUPowerManagement kext's in my kext folder - so do I even 'need' WhateverGreen, VirtualSMC, Lilu, for a 5700X, B450i, RX 6800?
Thanks again for your help mate!

 

[Edhawk]

I forgot to say, I have my onboard LAN and soundcard disabled, and simply use my graphics card's HDMI and DP for sound - so can I delete AppleALC.kext and remove it from my config.plist?

YES.

I have WhateverGreen, VirtualSMC, Lilu, itlwm, IntelBTPatcher, IntelBluetoothFirmware, BlueToolFixup, AppleReporterDisabler, and AMDRyzenCPUPowerManagement kext's in my kext folder - so do I even 'need' WhateverGreen, VirtualSMC, Lilu, for a 5700X, B450i, RX 6800?

You only need the following kexts.

• Lilu.kext
• VirtualSMC.kext
• AppleReporterDisabler.kext
• Your Ethernet controller kext
• Your USBMap.kext

If you use WiFi for internet access you probably won't be able to use it during the installation, as Itlwm.kext won't work without the Heliport app being installed first.

Use a Wired mouse and keyboard or a combo setup (Logitech or similar) that uses as specific USB dongle. Do not use a keyboard and mouse that requires the Intel Bluetooth to be working.

Everything else is fluff that can be added to the OC setup after the macOS Tahoe installation has completed.

You need to watch for the FileVault option during the later stages of the installation process. Make sure you unselect the option to use FileVault on your macOS Drive. If you miss this option, i.e skip past the tab, you will regret it.

I would recommend not using the iCloud sign in option during the installation Wizard, it can throw up some issues that are completely unnecessary. Just create your local account and sign in to iCloud once the installation has completed.

 

[keef247]

YES.


You only need the following kexts.

• Lilu.kext
• VirtualSMC.kext
• AppleReporterDisabler.kext
• Your Ethernet controller kext
• Your USBMap.kext

If you use WiFi for internet access you probably won't be able to use it during the installation, as Itlwm.kext won't work without the Heliport app being installed first.

Use a Wired mouse and keyboard or a combo setup (Logitech or similar) that uses as specific USB dongle. Do not use a keyboard and mouse that requires the Intel Bluetooth to be working.

Everything else is fluff that can be added to the OC setup after the macOS Tahoe installation has completed.

You need to watch for the FileVault option during the later stages of the installation process. Make sure you unselect the option to use FileVault on your macOS Drive. If you miss this option, i.e skip past the tab, you will regret it.

I would recommend not using the iCloud sign in option during the installation Wizard, it can throw up some issues that are completely unnecessary. Just create your local account and sign in to iCloud once the installation has completed.

None of that worked mate.
Mapped the USB ports selecting only 9 out of 18 that displayed. Made sure I selected the 9 that displayed after swapping in/out USB2/3 devices into each port individually.
Removed all the other Kexts and just left: Lilu, VirtualSMC, AppleReporterDisabler, and USBMAP.
Updated those kexts to the latest, along with the latest OpenCore, performed a Clean OC Snapshot with Propertree.

Same BS issue with the no entry symbol.

What a joke.

 

[Edhawk]

Why only 9 of the 18 USB ports?

You aren't limited to 15 ports. Your AMD system will have 2 or more USB controllers and each controller can activate 15 x ports. You should be activating all the ports you had active in your UTBMap.kext.

I have assumed the following:

1. You have the latest Tahoe compatible AMD Kernel Patches in your config.plist.
2. You are using OC 1.0.5
3. You have the latest versions of the essential kexts in your Kexts folder.
4. You are using MacPro7,1 SMBIOS, as iMacPro1,1 system definition has been dropped for Tahoe.

Post a copy of your EFI folder with the Serial Number deleted/redacted from the config.plist.

 

[etorix]

If you have a good USB map for earlier versions, the easiest way should be to edit the plist it contains to add the usb-port-type and usb-port-number entries for Tahoe, as shown by @Edhawk 's screenshots.

 

[keef247]

Why only 9 of the 18 USB ports?

You aren't limited to 15 ports. Your AMD system will have 2 or more USB controllers and each controller can activate 15 x ports. You should be activating all the ports you had active in your UTBMap.kext.

I have assumed the following:

1. You have the latest Tahoe compatible AMD Kernel Patches in your config.plist.
2. You are using OC 1.0.5
3. You have the latest versions of the essential kexts in your Kexts folder.
4. You are using MacPro7,1 SMBIOS, as iMacPro1,1 system definition has been dropped for Tahoe.

Post a copy of your EFI folder with the Serial Number deleted/redacted from the config.plist.

Ah OK, well I'll try it with more ports
Yep everything up to date, but the SMBIOS is named iMacPro19,1 - so just generate a new one as a MacPro7,1 then it'll work?
Is it true that you have to plug in 1 USB 2.0 then 3.0 device in each port, 1 at a time after each 5 second pass? As some guides say to, and some don't?
Will GenSMBIOS change my existing system definition without me having to make an entire config.plist from scratch - it's been a while since i've used it

If you have a good USB map for earlier versions, the easiest way should be to edit the plist it contains to add the usb-port-type and usb-port-number entries for Tahoe, as shown by @Edhawk 's screenshots.

Yeah, that didn't work, that's what I tried first

 

[Edhawk]

iMac19,1 isn't supported in Tahoe.

If you want to use an iMac SMBIOS you need to use iMac20,1 or iMac20,2. As they are the only 2 x iMac SMBIOS that work in Tahoe. Apple have dropped all the others.

You have to plug in a USB2 and a USB3 pen drive/device to discover all 18 x ports. Each port needs to be tested, some ports will only work with USB2, some will require testing with both USB2 and USB3.

If you have any Type-C ports on the front or rear of the case, then you need a test them with a Type-C device, if you plan to include them in the kext.

This is the method I use to configure the USB ports.

USB2 (0) - Physical USB2 ports on rear I/O plate, these ports always have a Black coloured tang.​

​

USB3 (3) - Physical USB3 ports on rear I/O plate, these ports can have a Red, Blue, Yellow or Cyan coloured tang.​

Virtual USB2 ports - served from physical USB3 ports should be set the same as the physical port​

​

USB3 (3) - Motherboard Header, usually serving the case front USB3 ports.​

Virtual USB2 ports - served from physical USB3 ports should be set the same as the physical port​

​

Internal (255) - Motherboard USB2 header, this will be any device served from a header port, such as Bluetooth module, case front USB2 ports, case front card reader etc.​

​

Internal (255) - Built-in M.2 WiFi/BT connector, motherboard LEDs and CPU Cooler USB connection.​

​

Type-c+sw (9) - will only show two ports being available, 1 x Physical Type-C and 1 x virtual USB2 port.​

​

Type-c (10) - will show 4 x ports being available.​

This occurs when the Type-C device initially inserted, then removed, is flipped 180° and reinserted in the same port, 2 x Type-C and 2 x virtual USB2 ports.​

Using GenSMBIOS to generate a new iMac20,x SMBIOS is what I would do.
You need to copy the Serial Number, MLB, ROM and SystemUUID from the Terminal Window to the PlatformInfo > Generic section of your config.plist, overwriting your current SMBIOS data.

As always make a copy of your current config.plist before overwriting anything.

Unless you are running a Clean installation of Tahoe on another drive, i.e. not updating your current macOS Sequoia drive. I would recommend signing out of iCloud, Music, App Store, Messages and FaceTime before you change the SMBIOS. Otherwise you could end up with issues signing in to iCloud etc.

 

[keef247]

So, I got a bit further this time, it's running the installer and I get the following:

00:000 00:000 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:065 00:065 AAPL: #[EB.H.IS|!] Err(0xE) <- RT.GV boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
00:129 00:063 AAPL: #[EB|H:IS] 0
00:203 00:074 AAPL: #[EB|LOG:INIT] 2025-09-27T14:40:49
00:269 00:065 AAPL: #[EB|VERSION] <"bootbase.efi 583~2470 (Official), built 2025-08-02T22:15:32-0700">
00:333 00:064 AAPL: #[EB|BUILD] <"BUILD-INFO[402]:{"DisplayName":"bootbase.efi","DisplayVersion":"583~2470","RecordUuid":"1A89C5D5-29A9-40A2-8456-BCC87A2D6CB2","BuildTime":"2025-08-02T22:15:32-0700","ProjectName":"efiboot","ProductName":"bootbase.efi","SourceVersion":"583","BuildVersion":"2470","BuildConfiguration":"Release","BuildType":"Official","Compiler":"clang-1700.3.17.1","SdkVersion":"26.0","SdkBuild":"25A333","TargetArchitectures":"x86_64"}">
01:316 00:982 AAPL: #[EB.CFG.DEV|!] Err(0xE) <- RT.GV booter-strict-xmlparser 7C436110-AB2A-4BBB-A880-FE41995C9F82
01:379 00:063 AAPL: #[EB|CFGEV] r5 0x0 0x0
01:443 00:063 AAPL: #[EB|H:IS] 0
01:509 00:066 AAPL: #[EB|WL:MODE] 0
01:574 00:064 AAPL: #[EB|CFG:ARG] boot-save-log 0x0000000000000002 (0x0000000000000002 < 0xFFFFFFFFFFFFFFFF) default
01:640 00:066 AAPL: #[EB|CFG:ARG] wake-save-log 0x0000000000000002 (0x0000000000000002 < 0x0000000000000002) default
01:705 00:064 AAPL: #[EB|CFG:ARG] console 0x0000000000000001 (0x0000000000000001 < 0x0000000000000001) default
01:779 00:074 AAPL: #[EB|CFG:ARG] serial 0x0000000000000001 (0x0000000000000001 < 0x0000000000000000) default
01:846 00:066 AAPL: #[EB|CFG:ARG] preoslog 0x0000000000000001 (0x0000000000000001 < 0xFFFFFFFFFFFFFFFF) default
01:911 00:065 AAPL: #[EB|CFG:ARG] timestamps 0x0000000000000000 (0x0000000000000000 < 0xFFFFFFFFFFFFFFFF) default
01:974 00:063 AAPL: #[EB|CFG:ARG] log-level 0x0000000000000001 (0x0000000000000001 & 0x0000000000000021) default
02:038 00:063 AAPL: #[EB|CFG:ARG] breakpoint 0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) default
02:104 00:066 AAPL: #[EB|CFG:ARG] kc-read-size 0x0000000000100000 (0x0000000000100000 < 0xFFFFFFFFFFFFFFFF) default
02:169 00:064 AAPL: #[EB|CFG:ARG] force-error 0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) default
02:235 00:066 AAPL: #[EB|H:IS] 0
02:299 00:064 AAPL: #[EB|WL] 0 0 0x01 0x01 0 0x00
02:375 00:075 AAPL: #[EB|BRD:NV] Mac-AF89B6D9451A490B
02:441 00:066 AAPL: #[EB|B:VAw]
02:506 00:064 AAPL: #[EB|B:IAw]
02:572 00:066 AAPL: #[EB|WL] 0 0 0x01 0x01 2 0x00
02:647 00:074 AAPL: #[EB.BST.IDT|+]
02:712 00:065 AAPL: #[EB|BM] J185FAP
02:778 00:065 AAPL: #[EB.BST.IDT|-]
02:844 00:066 AAPL: #[EB|WL] 0 0 0x01 0x01 3 0x00
02:908 00:064 AAPL: #[EB|WL] 0 0 0x01 0x01 4 0x00
02:974 00:066 AAPL: #[EB|BRD:NV] Mac-AF89B6D9451A490B
03:039 00:064 AAPL: #[EB|WL] 0 0 0x01 0x01 5 0x00
03:105 00:066 AAPL: #[EB.H.CHK|BM] 0x0000000000000000
03:170 00:064 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:244 00:074 AAPL: #[EB|WL] 0 0 0x01 0x01 23 0x0E
03:311 00:066 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:376 00:065 AAPL: #[EB|WL] 0 0 0x01 0x01 24 0x0E
03:439 00:063 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.GV boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:503 00:063 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-signature 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:578 00:074 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image-key 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:643 00:065 AAPL: #[EB.H.LV|!] Err(0xE) <- RT.SV- boot-image 7C436110-AB2A-4BBB-A880-FE41995C9F82
03:709 00:066 AAPL: #[EB|H:NOT]
03:774 00:064 AAPL: #[EB|SB] 0x1
03:840 00:066 AAPL: #[EB.B.MN|BM:+SB]
03:904 00:064 AAPL: #[EB|LIMGP] Acpi(PNP0A03,0)/Pci(8|1)/Pci(0|3)/Usb(6, 0)/HD(Part2,SigC1EBD1E7-C9D3-46D8-A8FA-34F980D7EEB6)
03:970 00:066 AAPL: #[EB|LIMG:FP] \System\Library\CoreServices\boot.efi
04:035 00:064 AAPL: #[EB|LIMG:OPT]
04:101 00:066 AAPL: #[EB|RPS] 0 0 0
04:177 00:076 AAPL: #[EB.OPT.LXF|F] <"\\System\\Library\\CoreServices\\com.apple.Boot.plist">
04:241 00:063 AAPL: #[EB.LD.LF|IN] 0 1 <"\\System\\Library\\CoreServices\\com.apple.Boot.plist"> <"0">
04:305 00:063 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"\\System\\Library\\CoreServices\\com.apple.Boot.plist">
04:371 00:066 AAPL: #[EB.OPT.LXF|LF!] Err(0xE)
04:435 00:064 AAPL: #[EB.OPT.LXF|F] <"Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist">
04:510 00:074 AAPL: #[EB.LD.LF|IN] 0 1 <"Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist"> <"0">
04:579 00:068 AAPL: #[EB|KF] <"root-dmg=file:///BaseSystem/BaseSystem.dmg">
04:644 00:064 AAPL: #[EB|MBA:CL] <"">
04:710 00:066 AAPL: #[EB|MBA:NV] <"keepsyms=1 debug=0x100 agdpmod=pikera -v slide=113">
04:774 00:064 AAPL: #[EB|MBA:KF] <"root-dmg=file:///BaseSystem/BaseSystem.dmg">
04:840 00:066 AAPL: #[EB|MBA:OUT] <"keepsyms=1 debug=0x100 agdpmod=pikera -v slide=113 root-dmg=file:///BaseSystem/BaseSystem.dmg">
04:905 00:064 AAPL: #[EB|LOG:VERBOSE] 2025-09-27T14:40:54
05:244 00:339 AAPL: #[EB.CSR.S|VAR] 0x00000040
05:311 00:066 AAPL: #[EB|OPT:BM] 0x200082
05:375 00:063 AAPL: #[EB.OPT.LXF|F] <"\\System\\Library\\CoreServices\\PlatformSupport.plist">
05:438 00:063 AAPL: #[EB.LD.LF|IN] 0 1 <"\\System\\Library\\CoreServices\\PlatformSupport.plist"> <"0">
05:504 00:065 AAPL: #[EB|P:CPR] N
05:570 00:066 AAPL: #[EB|P:MPI] N
05:645 00:074 AAPL: #[EB|P:BPI] N
05:710 00:065 AAPL: #[EB.OPT.RKS|!] Err(0xE) <- BS.LocP EDB4A040-6D8A-11EC-8FAD-3E22FB93ADCF
05:776 00:066 AAPL: #[EB|KMR] 374165504
05:841 00:064 AAPL: #[EB.CS.CSKSD|+]
05:907 00:066 AAPL: #[EB.CS.CSKSD|!] Err(0xE) <- RT.GV boot-info-payload 8D63D4FE-BD3C-4AAD-881D-86FD974BC1DF
05:971 00:064 AAPL: #[EB.G.CS|-?] Ok(0)
06:038 00:066 AAPL: #[EB.LD.LF|IN] 0 1 <"<null string>"> <"1">
06:155 00:117 AAPL: #[EB.B.SBS|SZ] 723512
06:225 00:070 AAPL: #[EB|B:SHA] <7d2bd8e2de771bf2c50d460648598705601d500b>
06:300 00:074 AAPL: #[EB.WL.PWLFNV|!] Err(0xE) <- RT.GV wake-failure 7C436110-AB2A-4BBB-A880-FE41995C9F82
06:364 00:064 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV
06:430 00:066 AAPL: #[EB.WL.PWLFRTC|NONE]
06:495 00:064 AAPL: #[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFRTC
06:561 00:066 AAPL: #[EB.LD.LKC|D] <"System\Library\KernelCollections\BootKernelExtensions.kc.development">
06:637 00:075 AAPL: #[EB.LD.LF|IN] 0 1 <"System\\Library\\KernelCollections\\BootKernelExtensions.kc.development"> <"0">
06:705 00:067 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"System\\Library\\KernelCollections\\BootKernelExtensions.kc.development">
06:770 00:064 AAPL: #[EB.LD.LKC|R.2] <"System\Library\KernelCollections\BootKernelExtensions.kc">
06:836 00:066 AAPL: #[EB.LD.LF|IN] 0 1 <"System\\Library\\KernelCollections\\BootKernelExtensions.kc"> <"0">
16:815 09:978 AAPL: #[EB|SB] 0x1
16:883 00:067 AAPL: #[EB|SB:SBGMFNS] j185fap.im4m
16:947 00:064 AAPL: #[EB|SB:MF] System\\Library\\KernelCollections\\BootKernelExtensions.kc.j185fap.im4m
17:014 00:066 AAPL: #[EB.LD.LF|IN] 0 1 <"System\\Library\\KernelCollections\\BootKernelExtensions.kc.j185fap.im4m"> <"0">
17:220 00:206 AAPL: #[EB|SB:MKRN]
17:304 00:083 AAPL: #[EB.LD.LKFS|-?] Ok(0)
17:370 00:066 AAPL: #[EB.LD.LKC|-?] Ok(0)
17:438 00:067 AAPL: #[EB|BST:REV1]
17:504 00:066 AAPL: #[EB|CSR:OUT] 0x00000040
17:580 00:075 AAPL: #[EB.BST.FBS|+]
17:646 00:066 AAPL: #[EB.BST.FBS|ADSZ] 0
17:710 00:064 AAPL: #[EB.BST.FBS|KSSZ] 0
17:777 00:066 AAPL: #[EB|SB:SBGMFNS] j185fap.im4m
17:841 00:064 AAPL: #[EB|RHF] usr\standalone\OS.dmg.root_hash
17:908 00:066 AAPL: #[EB|RH:MF] <"usr\\standalone\\OS.dmg.root_hash.j185fap.im4m">
17:973 00:064 AAPL: #[EB.LD.LF|IN] 0 1 <"usr\\standalone\\OS.dmg.root_hash"> <"0">
18:040 00:067 AAPL: #[EB.LD.OFS|OPEN!] Err(0xE) <"usr\\standalone\\OS.dmg.root_hash">
18:105 00:064 AAPL: #[EB.RH.LRH|P!] Err(0xE) <- EB.LD.LF
18:180 00:074 AAPL: #[EB.BST.FBS|!] Err(0xE) <- EB.RH.LRH
18:247 00:067 AAPL: #[EB|LOGT] 2025-09-27T14:41:07
18:313 00:065 AAPL: #[EB|LOG:EXITBS:START] 2025-09-27T14:41:07

Any ideas @Edhawk @Shaneee

Also, is there even a way that IntelBluetooth can work, otherwise it's pointless me upgrading, I have a MITX so don't have a 2nd pci-e slot for another card and the range on USB ones is rubbish.

If not I think I'll just stay on Sequoia, as everything works.

 

[Edhawk]

I have a couple of test systems running Tahoe. I don't intend to keep them running that OS. I will be reverting them back to just Sequoia and Windows 11. It might be worth another look in a month or two, when Apple have got around to fixing the bugs and other crap they have provided (Safari 26!).

In my opinion Tahoe n it's state offers nothing over Sequoia, in fact I think it is a step backwards compared to 15.6.1.