Jump to content
3741 posts in this topic

Recommended Posts

4 minutes ago, jm26200 said:

Hello Sir

But where does the info.plist file come from, in which you can modify the USB ports?

 

I use this USBMap-master and after  letters D, Q, P, A, K 
I get the USBMap.kext file, but there's no improvement upon reboot.

regards

 

I did all that too and @Anto65 was kind enough to edit my file but still can’t boot installer. Does yours stop with an error message in verbose mode?

9 minutes ago, D-an-W said:

 

I did all that too and @Anto65 was kind enough to edit my file but still can’t boot installer. Does yours stop with an error message in verbose mode?

hi

no error message but  with the famous lines

KextLog: Loading FilesSet KC(s)

Edited by jm26200

Mapping USB is just one of the problem not getting instalation boot properly, without mapping os still can boot, on installation i m not using any usbmap/port yet, onlu ACPI, so some of my usb port is missing and BT not working. 

 

if you are not able to boot the installer so make sure to check the EFI, the OC version, use minimal kext that required only, dont use usbinjectall and some kext that not ready for tahoe.. makesure that bios seeting is correct and alloc config is right 

 

 

 

  • Like 1
9 minutes ago, jm26200 said:

hi

no error message but  with the famous lines

KextLog: Loading FilesSet KC(s)


Mine is stopping in a similar place…

 

 

kernelmanagerd is not active KextLog: kernelmanagerd is not active

KextLog: Loading FileSet KC(s)

KextLog: Loading Pageable KC from file /System/Library/KernelCol lections/BaseSystemKernelExtensions.kc

  • Sad 1
28 minutes ago, Anto65 said:

Solved there, do things slowly and without haste, my mistakeimage.thumb.png.f7a1c0090d7ab4c691a12ed26cc8f144.png is that I added all the HS and SS devices but in the unavailable ones I put # working in both systems

 

 

  • Like 3
15 minutes ago, kaoskinkae said:

Solved there, do things slowly and without haste, my mistake is that I added all the HS and SS devices but in the unavailable ones I put # working in both systems

 

And yes, you have to do it calmly, I understand that after several unsuccessful attempts, one makes some mistakes
As someone told me
the mistake is almost always between the chair and the desk (but it has nothing to do with the chair) :hysterical:

  • Like 4
  • Haha 5
16 minutes ago, Anto65 said:

 

Deeveedee had already eliminated the chair last time, actually I hadn't thought about the desk... I'll have to eliminate that too 🤣

u can laugh about anything, but not with everyone.

 

🤣

@arya  @Anto65

 

Indeed, USBMAp.kext was wrong, I rebuild it again (BT internal port as 255) and Fenvi Bluetooth works as before.

USBMap.kext has the properties it used up until Sequoia along with the new ones required by Tahoe. It seems to work fine on Tahoe and earlier macOS.

 

Spoiler

Properties.thumb.png.3a23df514eb6e7d8069dcc3778ba8010.png


As a bonus, Hackintool displays USB ports correctly, which wasn't the case before.

 

Spoiler

USB-ports.thumb.png.892faec3cda7c8758dba57c83f1ccde3.png

 

  • Like 2

I can now confirm and brag that my Teaho is 100% working. Even my trackpad is now working without having to first plug a usb mouse. Thank you everyone for your assistance and guidance  in this Hackintosh journey. I am now waiting to see what the next beta is going to bring our way and wish everyone still struggling to eventually get it right 😁 

  • Like 1

Guys, this past couple of days have been really challenging for me, with Tahoe and all that. And...unfortunately, it kinda did some damage on my current Sequoia installation, even though it was installed on a separate partition.

I kept running into black screens, no matter what I do. I even reverted everything to the old versions of OC and kexts, and STILL got the same issue. The only way I was able to boot into the os was after a fresh clean nvram. So something was really f-ed up there.

 

In the end, I wiped the Tahoe partition, thinking it might fix it somehow. It didn't.

 

I thought maybe the config was somehow corrupted or so, so I reverted to the backup one. Nope. Same issue.

 

It was getting frustrating because I didn't know what the hell was going on! So, what I did, and what I would recommend you do, too, in case you come to this issue, is reinstall Sequoia from Recovery. No need for wipe, just use the Reinstall option from recovery. That (finally!) fixed it for me.

Also, another frustrating fact was that OCLP was complaining that my SIP was enabled and SecureBootModel was set to Default instead of Disabled (they were not). And OpenCoreConfigurator was complaining that: "The bootloader looks like it is not installed or your NVRAM isn't native". Both issues have been fixed, thankfully, with that reinstall.

 

So yeah, quite a roller coaster. Personally I'll be waiting for some updates from Apple before I give it another try. I'm not giving up. Just giving it time. :)

 

Update: looks like the issue I was facing above (boot to black screen with cursor and only being able to boot after clearing NVRAM and booting immediately after, without rebooting), was caused in the context of OCLP root patches being applied. If you don't want to reinstall the OS, as I was mentioning above, and you can't boot to your OS cause of the issue described above, the solution is simple: boot in Safe Mode. With OC, if you want to boot to Safe Mode, just press and hold Shift key while selecting the boot option in boot picker. When you get to the Desktop again, just remove root-patches and reboot. Now you should be able to boot again with no issues (but also with no patches) :)).

I'm still not sure what exactly causes this. Probably it doesn't work well when you have multiple OSes on the same SSD. But, in case you have this issue, this is another way you can fix it.

 

TL;DR: alternate workaround: boot in Safe Mode and remove root-patches if you have them applied.

Edited by arsradu
  • Like 3
22 minutes ago, Mirone said:

Has anyone had any success with the Z370 motherboard? I managed to install it, but then I got stuck in an infinite loop and didn’t look into it much afterward.

 

H370 

If you are in "prepare computer for first login fase", chose import from disk, choose your home folder and settings. After that you need to reinstall in same partition. At the end you will be able to log on.

Edited by Stefanalmare
  • Like 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...