Inquiry regarding the installation of 7700x, 6900xt, and B650E Tahoe.

[kth]

현재 Windows 11을 실행하는 PC에 Tahoe를 설치하려고 합니다.
macOS를 처음 사용하는 경우는 Hackintosh 관련 환경과 로켓을 사용하지 않는 것입니다. 내가 아는 것은 Windows에 있는 것 같아요.
제 PC 사양은 다음과 같습니다:
AMD 7700X, RX6900XT, 기가바이트 B650E Aorus Master.


내가 만든 EFI로 시동하면 이미지를 선택하지 않고, "금지 표시?" 동일한 이미지가 작동하는 시스템이 교체됩니다.
로그 파일도 첨부 파일에 감사하겠습니다.


온라인 검색을 보면 "일련번호"라는 것을 발견했습니다. "일련번호", "생산 코드", "제품명" 중 실제로 어떤 것을 보여주나요?
그리고 이 값 중 하나를 입력해야 할까요?


저는 여러분에게 도움을 요청해 주셔서 감사하겠습니다!

 

[kth]

검색을 통해 번호 문제를 해결할 수는 없지만 Apple 금지 마크는 더 이상 사용할 수 없습니다. 제가 업로드한 데이터와 동일합니다.

 

[leesurone]

검색을 통해 번호 문제를 해결할 수는 없지만 Apple 금지 마크는 더 이상 사용할 수 없습니다. 제가 업로드한 데이터와 동일합니다.

The prohibition sign usually indicates no valid USB Port is found, which if you are trying to install Tahoe makes sense. You will need to remap your USB Ports using CorpNewts newest version to work with Tahoe. Please see the linked post for more information.

Post in thread 'USB port mapping'

Jun 15, 2025

Use the Tahoe-Test version of Corpnewt's USBMap script. Apple have made a few changes to the USB Configuration, again.

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

Hackintool is useless for configuring AMD USB ports, it is aimed at Intel systems and older ones at that.

• Edhawk

• 

 

[kth]

The prohibition sign usually indicates no valid USB Port is found, which if you are trying to install Tahoe makes sense. You will need to remap your USB Ports using CorpNewts newest version to work with Tahoe. Please see the linked post for more information.

Post in thread 'USB port mapping'

Jun 15, 2025

Use the Tahoe-Test version of Corpnewt's USBMap script. Apple have made a few changes to the USB Configuration, again.

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

Hackintool is useless for configuring AMD USB ports, it is aimed at Intel systems and older ones at that.

• Edhawk

• 

"I followed the method you suggested by adding USBToolBox.kext and customizing UTBMap.kext, but I'm still getting the same result. I'm attaching the log and the EFI folder I'm currently using for your reference."

 

[fabiosun]

"I followed the method you suggested by adding USBToolBox.kext and customizing UTBMap.kext, but I'm still getting the same result. I'm attaching the log and the EFI folder I'm currently using for your reference."

this EFI is completely different from previous one you posted
it has stuff not useful for you if you are trying to instal a new OS
i suggst if possible to use a opencore debug version and to enable SysReport to have a printout of your ACPI folder
From this you can produce then useful SSDT and ACPI patches for your motherboard bios (also MMIO whitelist)
Remember to use 4G on /Uefi on / CSM OFF and disable fast boot from your mb bios option

 

[kth]

this EFI is completely different from previous one you posted
it has stuff not useful for you if you are trying to instal a new OS
i suggst if possible to use a opencore debug version and to enable SysReport to have a printout of your ACPI folder
From this you can produce then useful SSDT and ACPI patches for your motherboard bios (also MMIO whitelist)
Remember to use 4G on /Uefi on / CSM OFF and disable fast boot from your mb bios option

Thank you for your help.
Even after applying the USBMAP/USBToolBOX method, I'm still stuck in the same situation, whether I use the previous EFI or the later EFI.
I suspect the cause is different, but I can't figure it out.
So, I'm wondering if the problem lies in the fact that the original image and recovery image were created on Windows.

 

[Edhawk]

USBMap.kext shouldn’t be used with USBToolBox.kext.

UTBMap.kext is to be created and used with USBToolBox.kext.

 

[leesurone]

Thank you for your help.
Even after applying the USBMAP/USBToolBOX method, I'm still stuck in the same situation, whether I use the previous EFI or the later EFI.
I suspect the cause is different, but I can't figure it out.
So, I'm wondering if the problem lies in the fact that the original image and recovery image were created on Windows.

If you are trying to install Tahoe my first post still applies, Apple changed how USB Ports are accounted for and now requires different mapping criteria. USBToolBox.kext and UTBMap.kext which you have enabled in your attached EFI will not work. You should probably try Sonoma or Sequoia with your upload instead as there are other issues with your EFI that will prevent Tahoe from loading. Maybe you already have but your posts are unclear.