File system check exit code is 8

[JMB13]

Correct

I followed the tutorial but BT doesn't activate. I tried different orders, tried the USBToolbox kext prio to bluetooth kexts also, but no success

https://drive.google.com/file/d/1U4auDTqCcJyzeVf0EFlolT_gdupvgiPd/view?usp=sharing

Edit :

And n,ow whenn I want to eject trhe EFI partition, I have 3 messages :

VM disk can't be ejected because it is used by one or several programs
Preboot disk can't be ejected because it is used by one or several programs
Update disk can't be ejected because it is used by one or several programs

 

[EliteMacx86]

I followed the tutorial but BT doesn't activate. I tried different orders, tried the USBToolbox kext prio to bluetooth kexts also, but no success

https://drive.google.com/file/d/1U4auDTqCcJyzeVf0EFlolT_gdupvgiPd/view?usp=sharing

Edit :

And n,ow whenn I want to eject trhe EFI partition, I have 3 messages :

VM disk can't be ejected because it is used by one or several programs
Preboot disk can't be ejected because it is used by one or several programs
Update disk can't be ejected because it is used by one or several programs

Does the BT firmware loads? Those messages are normal and you can use apps like Hackintool, OCC to safely eject the ESP.

 

[JMB13]

Does the BT firmware loads? Those messages are normal and you can use apps like Hackintool, OCC to safely eject the ESP.

Yes they did, but I think it is now solved it for the BT and the freeze too. First the IntelBluetoothFirmware and IntelBTPatcher were version 2.4 and I found a version 2.5.0 for for both of them, now at least the BT Icon in the menu bar is enabled and I managed to connect a magic mouse, but very difficult or impossible to connect my android phone. Not a big deal. So I use IntelBluetoothFirmware.kext, IntelBTPatcher.kext and BlueToolFixup.kext right after itlwm.kext. And of course the 00/00000000000000...00000 NVRAM entry.

I ran the machine all night long (in automatic), about 12h in a rank on quite openGL stuff intensive (55% constant GPU load on the RX 6800 XT) anf it is still "alive", up and running. Need some real life usage now (network acces, etc) to see if the machine is stable.

I think the clean reinstall helped, maybe the AppleIGC kext, and removing the Fenvi card. I don't really need BT, but I consider that if something is not working or at least activated it could be a stability problem in the future. I may be wrong. also updated to OC 1.0.7 but I don't think it was part of the solution.

I'm gonna keep it like that, resintall everything, make a secure backup, and maybe try to update to Taohe. Is this update a nightmare or is it simple ?

Edit : OCC can't eject the ESP. The ficntion doesn't work

 

[EliteMacx86]

Yes they did, but I think it is now solved it for the BT and the freeze too. First the IntelBluetoothFirmware and IntelBTPatcher were version 2.4 and I found a version 2.5.0 for for both of them, now at least the BT Icon in the menu bar is enabled and I managed to connect a magic mouse, but very difficult or impossible to connect my android phone. Not a big deal. So I use IntelBluetoothFirmware.kext, IntelBTPatcher.kext and BlueToolFixup.kext right after itlwm.kext. And of course the 00/00000000000000...00000 NVRAM entry.

There was a known issue with the Intel's BT and a crucial function (LE) was broken in Sequoia, causing Magic Mouse like devices not to work. Starting from Ventura, the bluetooth daemon expects an LE PHY Update Complete event to be triggered from the controller before starting the connection to LE devices (Magic Mouse, Logitech MX Master etc)

I ran the machine all night long (in automatic), about 12h in a rank on quite openGL stuff intensive (55% constant GPU load on the RX 6800 XT) anf it is still "alive", up and running. Need some real life usage now (network acces, etc) to see if the machine is stable.

Great.

I think the clean reinstall helped, maybe the AppleIGC kext, and removing the Fenvi card. I don't really need BT, but I consider that if something is not working or at least activated it could be a stability problem in the future. I may be wrong. also updated to OC 1.0.7 but I don't think it was part of the solution.

Once you verify that current scenario is working fine, without crashes even with your software, then simply remove AppleIGC and then check. If it works, keep that off. Then, in next attempt, turn off Onboard Intel WiFi/BT and use Fenvi by patching the BT and WiFi (requires extra step). After you're done, monitor the crash. Of course, make backup of the system first so that you don't have to reinstall again.

I'm gonna keep it like that, resintall everything, make a secure backup, and maybe try to update to Taohe. Is this update a nightmare or is it simple ?

Tahoe still has some sort of problems on the newer machines, especially with the Realtek hardware. So, wait for a little more.

Edit : OCC can't eject the ESP. The ficntion doesn't work

This is weird. Did you formatted the entire disk when reinstalling from Disk Utility?

 

[JMB13]

There was a known issue with the Intel's BT and a crucial function (LE) was broken in Sequoia, causing Magic Mouse like devices not to work. Starting from Ventura, the bluetooth daemon expects an LE PHY Update Complete event to be triggered from the controller before starting the connection to LE devices (Magic Mouse, Logitech MX Master etc)

BT is wirking fine, I even managed to have a stable connexion with wy andrkid smartphone and did some BT file tranfer.

Great.

Almost great... I finished the reinstall of my system (including softwares), I reinstalled Carbon Copy Cloner, it did his job but after a very intensive backup (not system backup, storage backup) it froze... What I was doing was : CCC backup (on a 12 Go mechanical HD) and surfing with FireFox in the mean time. I don't remmeber if previous freezes occured during CCC backups, but FireFox was in the game. I think it also happened with SAfari.

Question : as it may be possible that the HD hosting the CCC backup was on the same port than the disk being backup (didn't remember if it was another HD or somme SSD), could it be a "too much" on USB port that causes the freeze ?

Would TimeMachine be more "gentle" ?

Would a NAS be a better solution ? Because when CCC is worj-king it seems to be veeeery intense on the tranfer.

Could NVMeFix kext be of any help because I read that its purpose was to fix somme non apple NVme compatibility ?

Once you verify that current scenario is working fine, without crashes even with your software, then simply remove AppleIGC and then check. If it works, keep that off. Then, in next attempt, turn off Onboard Intel WiFi/BT and use Fenvi by patching the BT and WiFi (requires extra step). After you're done, monitor the crash. Of course, make backup of the system first so that you don't have to reinstall again.

For now I wnat to try to find the culprit, because I hade 3 days without any issues and a very stable Hackintosh.£


Edit : I just read this article on Dortania's guide

RAM speed

Maybe lowering my RAM frequency woul d help ?

 

[JMB13]

Here is a rapport taht appeared on the reboot after a new freeze. Could the "Palette master" app a culprit (it is the calibration software on my benQ display)

 

[JMB13]

In the mean time I asked claude AI to look at my freeze report and it mentionned Palette Master Ultimate as a culprit. ThenI ran :

while true; do echo "$(date +%H:%M:%S) : $(sudo zprint | grep "ipc.kmsgs")"; sleep 60; done | tee ~/Desktop/ipc_

And I got this result (I closed Palette Master Ultimate just after the line 15:55:47) :

 while true; do echo "$(date +%H:%M:%S) : $(sudo zprint | grep "ipc.kmsgs")"; sleep 60; done | tee ~/Desktop/ipc_kmsgs_log.txt
Password:
15:50:44 : ipc.kmsgs                    256     108216K     108216K     432864      432864      432349     4K     16  C
15:51:46 : ipc.kmsgs                    256     119760K     119760K     479040      479040      478461     4K     16  C
15:52:46 : ipc.kmsgs                    256     131856K     131856K     527424      527424      526862     4K     16  C
15:53:46 : ipc.kmsgs                    256     145208K     145208K     580832      580832      580329     4K     16  C
15:54:46 : ipc.kmsgs                    256      86340K     147404K     345360      589616        2503     4K     16  C
15:55:47 : ipc.kmsgs                    256      55216K     147404K     220864      589616        2509     4K     16  C
15:56:47 : ipc.kmsgs                    256      20288K     147404K      81152      589616        2508     4K     16  C
15:57:47 : ipc.kmsgs                    256      14340K     147404K      57360      589616        2507     4K     16  C
15:58:47 : ipc.kmsgs                    256      10508K     147404K      42032      589616        2509     4K     16  C
15:59:47 : ipc.kmsgs                    256       7520K     147404K      30080      589616        2510     4K     16  C
16:00:47 : ipc.kmsgs                    256       5804K     147404K      23216      589616        2533     4K     16  C
16:01:47 : ipc.kmsgs                    256       5276K     147404K      21104      589616        2593     4K     16  C
16:02:47 : ipc.kmsgs                    256       5072K     147404K      20288      589616        2534     4K     16  C
16:03:47 : ipc.kmsgs                    256       5072K     147404K      20288      589616        2542     4K     16  C
16:04:47 : ipc.kmsgs                    256       4896K     147404K      19584      589616        2548     4K     16  C

Could this be a good culprit ?