Jump to content
153 posts in this topic

Recommended Posts

A little off topic - yesterday I was struggling with the launch of itlwm on my hackintosh. I couldn't start it in any way, and only after I installed the drivers on Wi-Fi in Windows, did the Wi-Fi in the hackintosh work for me. Maybe it will be useful to someone (or maybe I invented a bicycle😀)

  • Haha 4

I'm also getting a boot loop after the update installer is created and the first reboot occurs.  For me, the only unusual thing is multiple entries saying "AppleVTD is not yet installed as gSystem".  I don't think, however, that the boot loop has anything to do with VT-d.

HI All

 

Putting -lilubetaall, I can boot Sequoia 15.2 Beta. Unfortunatly, macOS stuck on login screen after entering password. 😒 (Z390, Opencore Nightly 1.0.3).

Edited by Matgen84
  • Sad 1
19 minutes ago, eSaF said:

Is  -lilubetaall boot-arg still mandatory? I stopped using it quite a few Sequoia Betas ago.

I find boot-arg revpatch=sbvmm and RestrictEvents.kext is suffice on my Z490 for booting both Sonoma and Sequoia in any Release.


Without -lilubetaall, my system is crashing. That is why I add it to boot-args. What do you think about my issue: macOS stuck on login screen after entering password.

1 hour ago, eSaF said:

That could be anyone's guess. The best solution is to get aid from any member running a Z390 Board, i.e BIOS version and settings.

The fact that you're experiencing crashes without that boot-arg is strange.

 

Personally I would start looking again at my BIOS settings with a possible BIOS update as well as the config.plist entries.

A daunting process to undertake but a possible necessary one. The Z390 is a solid platform for Hacks and from my own experience you shouldn't be having that problem with any updates if the setup is correct.

 

Strangely, my Z390 system work fine before updating to 15.2 Beta. I continue to investigate.

EDIT: I remove -lilubetaall. Boot Sequoia: always stuck spinning wheel at login screen after password 😒

Edited by Matgen84
  • Like 2
7 hours ago, LockDown said:

For me, it was the VoodooPS2Keyboard that was causing the Panic (early reboot)

Yes, this made the trick here... I had to disable all voodoo related kexts and the upgrade went through successfully. Thank you.

 

Edit: You still need to keep them disabled for this version, otherwise it won't boot once updated, so these kexts need to be updated. (VooDooPS2Controller.kext, VooDooI2C.kext and VoodooI2CHID.kext).

Edited by Dragster27
  • Like 2
58 minutes ago, Dragster27 said:

Yes, this made the trick here... I had to disable all voodoo related kexts and the upgrade went through successfully. Thank you.

 

Edit: You still need to keep them disabled for this version, otherwise it won't boot once updated, so these kexts need to be updated. (VooDooPS2Controller.kext, VooDooI2C.kext and VoodooI2CHID.kext).

 

This information was valid for my laptop. When VoodooPS2controller.kext canceled the installation completed. These kexts need to be updated.

14 hours ago, LockDown said:

For me, it was the VoodooPS2Keyboard that was causing the Panic (early reboot)

 

This was the problem for me.  I disabled all of the VoodooPS2Controller kexts and plugin kexts and it installed just fine.  Unfortunately, you cannot re-enable them after installation.  I am currently using a Bluetooth keyboard/trackpad and it sucks but I'm sure the kext will be updated soon now that it is clear that this is the kext causing the problem for many of us. For me, the error message was with the trackpad only.  I will try to isolate a specific kext/plugin and see if I can maintain keyboard functionality and only disable the trackpad.

 

EDIT:  Disabling the Trackpad plugin kext was not enough. With the other VoodooPS2 kexts, enabled, it still hung when booting up.

 

@1Revenger1 FYI

 

BTW, Here are the error messages I received just prior to restarting.

image.thumb.jpeg.9453d7475b3ca53de1f6b07f9570aa83.jpeg

Edited by mnfesq
  • Like 3

Well, for me and my system, the install of 15.2 went fine.  No surprises or any issues whatsoever, actually.  

 

Whenever I say that, I always wonder what surprises Apple might come up with 15.3 or later.  They do have a history of introducing changes, often in the middle of updates to their OS, that sends many of us scrambling for solutions....🤔

Edited by meg2014
  • Like 3
8 hours ago, 1Revenger1 said:

@mnfesq I am not in the habit of installing beta OSes. If you all have a kernel panic log to share and more specifics about which kext is causing issues, I can take a look.

 

I was not able to find any references to the VoodooPS2Controller in my kp logs.  I have determined that the PS2 Controller kext and the Input kext both load without problem but all three device kexts, keyboard, mouse, and trackpad each individually and together cause the system to restart during boot.  If that's enough to justify taking a look, there are several of us here that would appreciate it.  If you would prefer, we can wait until 15.2 beta 3 comes out  in the next week and see if the problem persists.  I would hate to see you debug an issue that gets resolved in the beta development process.  Whatever you decide, thanks for responding to my post.

In my opinion everything points towards VoodooInput as being responsible for the mentioned issues. I was able to successfully install 15.2 on my Elitebook by disabling VoodooPs2, VoodooI2C, VoodooInput and all their Plugins/sattelites.  Reenabling any of them after the update was installed causes the boot to stall again (no visible kernelpanik at least not in verbose output it just stalls). I am actually not able to provide debug/panik logs since I am @work right now and do not have the machine at hand but I thought It might be a good idea to share my thoughts. 

I've had luck in the past getting a stack trace by adding "cpus=1" to the boot-args - but it's all reliant on "debug=0x100 keepsyms=1" being in the boot-args as well.

 

Does the panic go away if you only disable VoodooInput and nothing else?

Edited by 1Revenger1
29 minutes ago, 1Revenger1 said:

Does the panic go away if you only disable VoodooInput and nothing else?

 

For me the answer unfortunately is no. As soon as any part of VoodooPS2 or Voodooi2c is enabled the boot process stalls also it stalls if only VoodooInput is enabled. In my case the boot simply stops (no reboot, no visible panic at all). Flags used: keepsyms=1 debug=0x100 Quirks used: PanicNoKextdump, PowerTimeoutKernelpanic  

Edited by griven
42 minutes ago, 1Revenger1 said:

Does the panic go away if you only disable VoodooInput and nothing else?

As for me, only acidanthera's VoodooPS2Keyboard causing the panic. KP goes away if i disable that plugin

Edited by LockDown

Same boot loop in clover and opencore. In one of my laptops I use ApplePS2SmartTouchPad.kext because voodoo doesn't work on it. I have the same KP. Disabling just the keyboard plugin, I can boot. I suspect something is changed related with keyboard approach in beta 15.2.

  • Like 4
Guest
This topic is now closed to further replies.
×
×
  • Create New...