Jump to content
1961 posts in this topic

Recommended Posts

2 hours ago, D-an-W said:

Has anyone else notice FileVault turned on after first reboot and also know how I can turn it off(!) please?

 

Just go to here and try disable password to make logon (login) on boot screen and than system will offer to you Disable Encrypting 

 

 

Captura de Tela 2024-06-11 às 10.17.22.png

  • Like 1
  • Thanks 2
1 hour ago, turko35408 said:

@Shaneee  Hi. All kernel patches are ok. The BIOS settings have been reviewed, but this is the case. The same EFI opens Sonoma without problems.20240611_031309.thumb.jpg.fc17a68b1c2e1a236019fb3f6143fc7c.jpg

 

 

config.plist 63.32 kB · 4 downloads

 

You've only added the updated PAT patch. There's another new one and others need their MaxKernel adjusted. Paste over the patches replacing what you've got and set your core count again in the top patches.

  • Like 1
  • Thanks 1
2 minutes ago, Shaneee said:

 

You've only added the updated PAT patch. There's another new one and others need their MaxKernel adjusted. Paste over the patches replacing what you've got and set your core count again in the top patches.

I'll try, thanks. :)

5 hours ago, Max.1974 said:

 

Just go to here and try disable password to make logon (login) on boot screen and than system will offer to you Disable Encrypting 

 

 

Captura de Tela 2024-06-11 às 10.17.22.png

My encryption appears to be paused at 13% and as yet not found a way to resume it or turn it off.

 

EDIT: Got it to complete the process using Terminal in Recovery.

Edited by D-an-W
  • Like 1

I installed and tried it on my 2018 MacBook Pro last night and does not seem much different to Sonoma. Maybe some different placements for some settings and Safari looks different but not much. Runs smooth has well. 

Edited by surenmunoo
1 hour ago, D-an-W said:

My encryption appears to be paused at 13% and as yet not found a way to resume it or turn it off.

 

EDIT: Got it to complete the process using Terminal in Recovery.

 

Very awesome, to me works very fast, unless 3 minutes. How command are you using to make disable on Recovery mode? Thanks! 

5 minutes ago, Max.1974 said:

 

Very awesome, to me works very fast, unless 3 minutes. How command are you using to make disable on Recovery mode? Thanks! 

 

It was a post on Reddit I found that enabled me to complete the process which means I can now turn off FileVault in the OS (Taking much longer than 3 minutes though!).

  • Like 1
7 minutes ago, eSaF said:

I hazard a guess there is serious misconfiguration on your system.

I am using Chrome to watch Amazon and Netflix movies no problem.

You need to look at your setup again.

I agree but no clue how and where to look. I am typing this in sonoma using chrome at the moment. All other browsers working fine with Sequoia.

voodooI2C touchpad is not working on on macOS Sequoia beta 1 I don't have any idea

anyone can help me

pushed latest pull request https://github.com/VoodooI2C/VoodooI2CHID/pull/75 by @1Revenger1

I don't know it is fixed by him or not 

Edited by ameenjuz
  • Like 2

Sequoia beta1 runs perfectly on all Macs and my Hacki.
I updated OC 0.9.4 (everything also worked well with Sonoma 14.5) to OC 1.0.0 and added Sequoia as

bootarg -lilubetaall and everything works.

One thing annoys me a little, that Apple is now releasing half-finished OS so that the newer options like

iPhone are not yet available on the Mac screen. Otherwise there are no really amazing new features, you could just stick with Sonoma.

I'm just doing it to pass the time and for fun.

  • Like 1
2 hours ago, ameenjuz said:

voodooI2C touchpad is not working on on macOS Sequoia beta 1 I don't have any idea

anyone can help me

pushed latest pull request https://github.com/VoodooI2C/VoodooI2CHID/pull/75 by @1Revenger1

I don't know it is fixed by him or not 

Badly timed push haha. It's a fix for an HP device that has the trackpoint wired to the touchpad.
The fix that everyone is probably looking for is in a PR for VoodooInput 😉

Edited by 1Revenger1
  • Like 1

I initially forgot to add -lilubetaall as a boot arg, doing so rectified the memory misconfiguration message I was seeing.

 

Can that boot arg be made to only apply when booting into Sequoia?

 

I am still getting a panic reported when rebooting which seems to be happening on shutdown / reboot.

 

Spoiler

panic(cpu 0 caller 0xffffff8010dd3d86): IONetworkController.cpp:1093 Assertion failed: m

Panicked task 0xffffff8c0d507698: 6 threads: pid 1: launchd

Backtrace (CPU 0), panicked thread: 0xffffff90d8257b30, Frame : Return Address

0xffffffd1006db580 : 0xffffff80105644e1

0xffffffd1006db5d0 : 0xffffff80106cfefc

0xffffffd1006db610 : 0xffffff80106bfbad

0xffffffd1006db6b0 : 0xffffff80104fa971

0xffffffd1006db6d0 : 0xffffff80105647d7

0xffffffd1006db7d0 : 0xffffff8010563e72

0xffffffd1006db840 : 0xffffff8010dd3d58

0xffffffd1006db930 : 0xffffff8010dd3d86

0xffffffd1006db940 : 0xffffff8012773d35

0xffffffd1006db950 : 0xffffff8012769175

0xffffffd1006db970 : 0xffffff80142bdb71

0xffffffd1006db9b0 : 0xffffff80142bf376

0xffffffd1006db9e0 : 0xffffff80142bf771

0xffffffd1006dba10 : 0xffffff80142c12f2

0xffffffd1006dba30 : 0xffffff8012768681

0xffffffd1006dba60 : 0xffffff8012769e7f

0xffffffd1006dba90 : 0xffffff8010cfced8

0xffffffd1006dbaf0 : 0xffffff8012769eff

0xffffffd1006dbb50 : 0xffffff8012769fad

0xffffffd1006dbb70 : 0xffffff8012763a61

0xffffffd1006dbbb0 : 0xffffff8012769e7f

0xffffffd1006dbbe0 : 0xffffff8010cfced8

0xffffffd1006dbc40 : 0xffffff8012769eff

0xffffffd1006dbca0 : 0xffffff801276376e

0xffffffd1006dbcf0 : 0xffffff80107d2d72

0xffffffd1006dbd50 : 0xffffff80107d30b1

0xffffffd1006dbe20 : 0xffffff80107e0aee

0xffffffd1006dbe50 : 0xffffff801083c562

0xffffffd1006dbe70 : 0xffffff80107d072d

0xffffffd1006dbeb0 : 0xffffff8010af2895

0xffffffd1006dbf00 : 0xffffff8010b14790

0xffffffd1006dbf40 : 0xffffff8010c3fd52

0xffffffd1006dbfa0 : 0xffffff80104fadb6

      Kernel Extensions in backtrace:

         com.apple.iokit.IONetworkingFamily(3.4)[FCB9BFDD-93F0-3784-8274-3D4DB73BF90E]@0xffffff801275f000->0xffffff8012774fff

         com.sxx.AppleIGC(1.3d1)[CB6C763C-0BB3-3646-BEC5-B37D7270541A]@0xffffff80142bc000->0xffffff80142d4fff

            dependency: com.apple.iokit.IONetworkingFamily(3.4)[FCB9BFDD-93F0-3784-8274-3D4DB73BF90E]@0xffffff801275f000->0xffffff8012774fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[66EF1AD6-83DC-372B-ADD3-D0DF76FE019C]@0xffffff80129c1000->0xffffff80129f3fff

 

Process name corresponding to current thread (0xffffff90d8257b30): launchd

Boot args: agdpmod=pikera e1000=0

It is known that Intel Wifi works with itlwm.kext + Heliport.app but I wonder how to Airdrop with just those. Airdrop also needs Bluetooth and I tried using Bluetoolfixup + Intelbluetoothfirmware + IntelBTPatcher on my Laptop but I couldn't Fix the Bluetooth. My computer crashes as soon as it boots up to the middle of the apple loading bar (I don't turn on Verbose).

11 hours ago, dreamwhite said:

Hi there, has anyone any clue on why Voodoo ItwoC (thanks tapatalk for messing) kexts? I’m using GPIO Interrupt mode if it matters

Hi, did you come right with the voodooinput.kext issue?

8 minutes ago, Takiller said:

Hi, did you come right with the voodooinput.kext issue?

Good morning, yeah. I used the artifact from there https://github.com/1Revenger1/VoodooInput/actions/runs/9475484687. Discussion: https://github.com/VoodooI2C/VoodooI2CHID/pull/75/

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