Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

How can I check which kexts are currently injected on my booted Catalina install?
Simply type kextstat. This will generate a complete list. We can choose to display third party kexts as follows: kextstat | grep -v apple.
 
I managed to do kextstat | grep -v com.apple and I do see the older versions. Should I update them on my Clover EFI before switching to OC?

Also, I can't touch anything inside /System, as it's read-only

Code:
➜  ~  sudo touch /System/Library/Extensions
touch: /System/Library/Extensions: Read-only file system
The older Kexts are most likely inside a cache that macOS maintains. MacOS copies kexts from /Library/Extensions into a folder buried somewhere inside the /System folder. This is why the newer kexts in OpenCore are not being injected -- because the macOS cache contains kexts of the same names.

It's okay to just do sudo touch /Library/Extensions and reboot. Other kexts should not be updated at this time. Let's get the original problem resolved.
 
It's okay to just do sudo touch /Library/Extensions and reboot. Other kexts should not be updated at this time. Let's get the original problem resolved.

I don't use Kext Utility, preferring to do it the old fashioned, CLI way. I've always run `sudo kextcache -i /` after chmod/chown the /S*/L*/E* and /L*/E* directories, though. Is kextcache command not needed?
 
It's working fine here.

Just back to home from French Police Department

A group of hackers trying to install crypto-currency miner system on my server.
Excessive numbers of requests (specially on HackinDROM) since about 10 days kept shutting down the entire system, including HackinDROM, not cool. The reason of that "502 bad gateway"!

I tracked them during theses days and all log files are now at PD of my city.
I also got an e mail from Netcraft noticing me about this problem.

I'm working to add more nice features to HackinDROM, so I would like to spend my time on it and not to run behind hackers.
I think and hope the hackers aren't from our community.
 
Hey everyone - got a question around external drives (such as USB flash drives and external HDDs for backup).

If I leave a USB flash drive connected, my Mac won't sleep, with pmset -g assertions giving the reason as:

Code:
2020-08-13 18:02:10 +0100
Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  1
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 507(mds_stores): [0x00000204000b82d5] 00:00:17 BackgroundTask named: "com.apple.metadata.mds_stores.power" 
   pid 506(mds): [0x0000015a000b8277] 00:03:06 BackgroundTask named: "com.apple.metadata.mds.power" 
   pid 68(powerd): [0x000001220008824d] 00:04:03 ExternalMedia named: "com.apple.powermanagement.externalmediamounted" 
   pid 109(hidd): [0x00000205000982d6] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100000698 name:AppleHIDKeyboardEve product:Magic Keyboard eventType:3" 
    Timeout will fire in 180 secs Action=TimeoutActionRelease
Kernel Assertions: 0xc=USB,BT-HID
   id=504  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14500000 owner=4-Port USB 2.0 Hub
   id=506  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14f00000 owner=4-Port USB 3.0 Hub
   id=508  level=255 0x8=BT-HID mod=01/01/1970, 01:00 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice
   id=509  level=255 0x8=BT-HID mod=01/01/1970, 01:00 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice
   id=511  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14d00000 owner=Ultra USB 3.0
Idle sleep preventers: IODisplayWrangler

Therefore, is this a general Mac problem, or is there a way I can still get my Hack to sleep if there's a USB drive plugged in? It's not really an issue now, but in the future I'm planning on getting a cheap external USB 3 drive for backing up movies etc.

Thanks!
 
Hey everyone - got a question around external drives (such as USB flash drives and external HDDs for backup).

If I leave a USB flash drive connected, my Mac won't sleep, with pmset -g assertions giving the reason as:
...
Therefore, is this a general Mac problem, or is there a way I can still get my Hack to sleep if there's a USB drive plugged in? It's not really an issue now, but in the future I'm planning on getting a cheap external USB 3 drive for backing up movies etc.

Thanks!
Hopefully others will report their experiences as well, but the first 3 systems listed in my signature don't have this problem. I can connect both USB flash drives and SATA SSDs in external USB 3.0 enclosures without any sleep/wake issue.

Something that surprised me recently:
  • I've installed Big Sur on a SATA SSD mounted in an external USB 3 enclosure.
  • Big Sur will sleep and wake properly.
I recall this being a problem with Catalina, which would eject external drives during sleep. If macOS happened to be on an external disk, it would not reconnect and hence the system would not wake from sleep. I should add that this behavior [with Catalina] was observed using Clover, whereas Big Sur is (currently) bootable only with OpenCore.
 
Hey everyone - got a question around external drives (such as USB flash drives and external HDDs for backup).

If I leave a USB flash drive connected, my Mac won't sleep, with pmset -g assertions giving the reason as:

Code:
2020-08-13 18:02:10 +0100
Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  1
   PreventUserIdleSystemSleep     0
   NetworkClientActive            0
Listed by owning process:
   pid 507(mds_stores): [0x00000204000b82d5] 00:00:17 BackgroundTask named: "com.apple.metadata.mds_stores.power"
   pid 506(mds): [0x0000015a000b8277] 00:03:06 BackgroundTask named: "com.apple.metadata.mds.power"
   pid 68(powerd): [0x000001220008824d] 00:04:03 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
   pid 109(hidd): [0x00000205000982d6] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:100000698 name:AppleHIDKeyboardEve product:Magic Keyboard eventType:3"
    Timeout will fire in 180 secs Action=TimeoutActionRelease
Kernel Assertions: 0xc=USB,BT-HID
   id=504  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14500000 owner=4-Port USB 2.0 Hub
   id=506  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14f00000 owner=4-Port USB 3.0 Hub
   id=508  level=255 0x8=BT-HID mod=01/01/1970, 01:00 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice
   id=509  level=255 0x8=BT-HID mod=01/01/1970, 01:00 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice
   id=511  level=255 0x4=USB mod=01/01/1970, 01:00 description=com.apple.usb.externaldevice.14d00000 owner=Ultra USB 3.0
Idle sleep preventers: IODisplayWrangler

Therefore, is this a general Mac problem, or is there a way I can still get my Hack to sleep if there's a USB drive plugged in? It's not really an issue now, but in the future I'm planning on getting a cheap external USB 3 drive for backing up movies etc.

Thanks!
No single problem :)
 
Hopefully others will report their experiences as well, but the first 3 systems listed in my signature don't have this problem. I can connect both USB flash drives and SATA SSDs in external USB 3.0 enclosures without any sleep/wake issue.

Something that surprised me recently:
  • I've installed Big Sur on a SATA SSD mounted in an external USB 3 enclosure.
  • Big Sur will sleep and wake properly.
I recall this being a problem with Catalina, which would eject external drives during sleep. If macOS happened to be on an external disk, it would not reconnect and hence the system would not wake from sleep. I should add that this behavior [with Catalina] was observed using Clover, whereas Big Sur is (currently) bootable only with OpenCore.
No single problem :)

Thanks both! I think I'll live with it for now, especially as Casey's Big Sur findings seem good. I'm going to save my patience and brain power for the Casey Big Sur guide in the coming months!
 
I don't use Kext Utility, preferring to do it the old fashioned, CLI way. I've always run `sudo kextcache -i /` after chmod/chown the /S*/L*/E* and /L*/E* directories, though. Is kextcache command not needed?
Good question. From the built-in man page for kextcache:


KEXTCACHE(8) BSD System Manager's Manual KEXTCACHE(8)

NAME
kextcache -- create kext cache files

SYNOPSIS
kextcache -prelinked-kernel filename [options] [--] [kext_or_directory ...]
kextcache -system-prelinked-kernel [options] [--] [kext_or_directory ...]
kextcache -system-caches [options]
kextcache -update-volume os_volume [options]

DESCRIPTION
The kextcache program creates kext caches, which speed up kext loading operations.
It is invoked automatically as needed to rebuild system caches.

Caution: Incorrect use of kextcache can render a volume incapable of startup. Installers

and administrators should not use this program to update system kext caches. Instead they
should run touch(1) on the /System/Library/Extensions/ directory of the installation target
volume after they have finished, which invalidates the existing caches and causes the
system to update all
necessary kext caches. kextcache -update-volume can be used to wait
for this process to complete. See ``Apple Developer Technical Q&A QA1319: Installing an
I/O Kit Kext Without Rebooting'' for information on updating kext caches on prior releases
of macOS.
 
Back
Top