Jump to content

[Pre Release] macOS Sequoia 15.2


97 posts in this topic

Recommended Posts

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.

Link to comment
Share on other sites

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. 

Link to comment
Share on other sites

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
Link to comment
Share on other sites

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
Link to comment
Share on other sites

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
Link to comment
Share on other sites

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
Link to comment
Share on other sites

52 minutes ago, Stefanalmare said:

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.

Link for ApplePS2SmartTouchPad.kext ?

Link to comment
Share on other sites

Thanks to the advices of the patient developers of Insanelymac (aka Gandhivelopers in my case) I was able to update without problems. If it wasn't  for these  f.. graphics problems and these damned black boxes on mail and co..it would be perfect. 

Link to comment
Share on other sites

5 minutes ago, calmesal said:

Appriciate if som one could upload the working voodoops2.kext here.

 

There isn't one. That seems to be the big surprise about 15.2 beta 2.

  • Like 5
Link to comment
Share on other sites

Hello,

 

Successfully updated from 15.1 but I do get that on every boot the updatenotificationmanager window pops up which asks for my admin password and then it is gone. However it is annoying. Does someone else here have the same problem and what is the solution for that?

 

Screenshot 2024-11-08 at 10.57.11.png

  • Like 1
Link to comment
Share on other sites

On 11/6/2024 at 2:39 PM, 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.

 

As you may have seen from above, we all are having trouble with the keyboard kext.  I cannot get the mouse or trackpad kexts to load with the keyboard kext disabled as well.  Here is the kp log file created upon reboot.  I also saved the system diagnostic files created upon reboot but they exceed the size limit I can share here. Thanks for any help you can provide.  Unless you instruct me to do so, I will not also create a bug report on Github as I don't want to submit duplicate requests on this. Thanks.

 

Kernel-2024-11-08-162037.panic

Link to comment
Share on other sites

3 hours ago, mnfesq said:

 

As you may have seen from above, we all are having trouble with the keyboard kext.  I cannot get the mouse or trackpad kexts to load with the keyboard kext disabled as well.  Here is the kp log file created upon reboot.  I also saved the system diagnostic files created upon reboot but they exceed the size limit I can share here. Thanks for any help you can provide.  Unless you instruct me to do so, I will not also create a bug report on Github as I don't want to submit duplicate requests on this. Thanks.

I am going to wait until 15.2 is out of beta as nothing pops out to me as wrong with VoodooPS2 itself. May need to wait until new sources come out for IOHIDFamily/xnu - a reserved function is getting called that shouldn't be.
I'm a little hesitant to make changes for a beta.

  • Like 3
Link to comment
Share on other sites

1 hour ago, 1Revenger1 said:

I am going to wait until 15.2 is out of beta as nothing pops out to me as wrong with VoodooPS2 itself. May need to wait until new sources come out for IOHIDFamily/xnu - a reserved function is getting called that shouldn't be.
I'm a little hesitant to make changes for a beta.

 

Understood. I will be reverting back to 15.1 so that I can use my laptop without the BT keyboard that is driving me crazy because it is not full size.  I look forward to a resolution of this issue and only hope that 15.2 does not have 6 betas and 2 RCs before it comes out in final form.  Maybe it will be resolved in the next beta. 

  • Like 4
Link to comment
Share on other sites

On 11/6/2024 at 8:33 PM, mnfesq said:

 

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

 

Same for me on my Lenovo T490 Notebook. In the end, I disabled almost every kext besides the bare minimum of kexts and the installer still crashed early. I have no clue what the issue is.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...