search

acidanthera / bugtracker

Acidanthera Bugtracker
385 stars 45 forks source link

Sequoia doesn't function correctly without -lilubetaall #2431

Closed EAZYBLACK closed 1 month ago

EAZYBLACK commented 1 month ago

The issue is that if i dont add -lilubetaall, even if all my kexts have sequoia constants, it stucks in a ramrod loop in stage 3 (it finishes like takes 5min , reboots and same thing again), adding -lilubetaall fixed it, i had also heard someone had no graphics accel without -lilubetaall

TonyC5 commented 1 month ago

@EAZYBLACK All of my hacks boot Sequoia 15.0 and 15.1 Beta without -lilubetaall when using the latest Acidanthera kexts with Open Core 1.0.1 (Release). If I need BluetoolFixup.kext 2.6.8 with Sequoia, I use boot-arg -btlfxbeta.

Without any information about your hack (or Mac), your version of Open Core, the version of kexts in your EFI and crash diagnostics, it may be difficult for anyone to diagnose and assist you.

holy-dev commented 1 month ago

The issue is that if i dont add -lilubetaall, even if all my kexts have sequoia constants, it stucks in a ramrod loop in stage 3 (it finishes like takes 5min , reboots and same thing again), adding -lilubetaall fixed it, i had also heard someone had no graphics accel without -lilubetaall

Could you please help me? I'm having the same issue. It's not working even with the flag.

Krazy-Killa commented 1 month ago

@EAZYBLACK All of my hacks boot Sequoia 15.0 and 15.1 Beta without -lilubetaall when using the latest Acidanthera kexts with Open Core 1.0.1 (Release). If I need BluetoolFixup.kext 2.6.8 with Sequoia, I use boot-arg -btlfxbeta.

Without any information about your hack (or Mac), your version of Open Core, the version of kexts in your EFI and crash diagnostics, it may be difficult for anyone to diagnose and assist you.

I am curious where you found -btlfxbeta.. I've checked the BrcmPatchRAM Repo and seen no mention of this.

TonyC5 commented 1 month ago

@Krazy-Killa Inspect the BluetoolFixup.cpp source.

Krazy-Killa commented 1 month ago

@Krazy-Killa Inspect the BluetoolFixup.cpp source.

Just did. Been using -lilubetaall for my setup, xD. Glad to know there's one to only enable BlueToolFixup. :)

vedantmgoyal9 commented 1 month ago

https://github.com/acidanthera/BrcmPatchRAM/pull/33 - this fixes the need of -btlfxbeta. If someone can contact the maintainer and get it merged :)

Andrey1970AppleLife commented 1 month ago

acidanthera/BrcmPatchRAM#33 - this fixes the need of -btlfxbeta. If someone can contact the maintainer and get it merged :)

Done

EAZYBLACK commented 1 month ago

@EAZYBLACK All of my hacks boot Sequoia 15.0 and 15.1 Beta without -lilubetaall when using the latest Acidanthera kexts with Open Core 1.0.1 (Release). If I need BluetoolFixup.kext 2.6.8 with Sequoia, I use boot-arg -btlfxbeta.

Without any information about your hack (or Mac), your version of Open Core, the version of kexts in your EFI and crash diagnostics, it may be difficult for anyone to diagnose and assist you. these are the kexts image all lilu based kexts are updated to latest version and should work without lilubetaall also lilubetaall is only needed to get past ramrod loop

Sooly890 commented 1 month ago

This appears to still break. I've seen reports of the whole Lilu breaking, AppleALC, WhateverGreen, and RestrictEvents, without -lilubetaall on Sequoia. This should be reopened, BlueToolFixup appears not to be the only broken thing here.

Krazy-Killa commented 1 month ago

This appears to still break. I've seen reports of the whole Lilu breaking, AppleALC, WhateverGreen, and RestrictEvents, without -lilubetaall on Sequoia. This should be reopened, BlueToolFixup appears not to be the only broken thing here.

Nothing wrong with the latest versions of those kexts as they are setup to function with Sequoia.. Update your kexts.

Sooly890 commented 1 month ago

Nothing wrong with the latest versions of those kexts as they are setup to function with Sequoia.. Update your kexts.

I'm aware that they are setup to support Sequoia. These people are on the latest kexts.

TonyC5 commented 1 month ago

@Sooly890 Just to clarify ... you are not experiencing this problem yourself, but you have been kind enough to observe the problem with others and are reporting it here. Is that correct?

Would it be possible for you to gain first-hand knowledge so that you can provide details (or tell those who are experiencing the problem to report their details here)? Just my opinion, but hearsay without evidence isn't a reason to reopen this.

Sooly890 commented 1 month ago

@Sooly890 Just to clarify ... you are not experiencing this problem yourself, but you have been kind enough to observe the problem with others and are reporting it here. Is that correct?

Yes, that's correct

Would it be possible for you to gain first-hand knowledge so that you can provide details (or tell those who are experiencing the problem to report their details here)? Just my opinion, but hearsay without evidence isn't a reason to reopen this.

Sure, I can do that (both)

Sooly890 commented 1 month ago

Humm, actually is seems like a user error for now. The people I was referring to had some weird Kexts enabled. My bad for falsely resurrecting this.