Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,805 posts in this topic

Recommended Posts

maxb2000
maxb2000
Posted
Posted

Hi guys,

 

1980-01-01 02:04:41.308484+0200  localhost kernel[0]: Kext ru.joedm.SMCSuperIO did not stop (return code 0x5).
1980-01-01 02:04:41.308498+0200  localhost kernel[0]: Kext ru.joedm.SMCSuperIO can't unload - module stop returned 0xdc008017.

 

I have these in the logs, should I no longer use SMCSuperIO ? I don't even now for what is for. Maybe sensors ?

 

Second question:

 

I want to boot directly into macOS without a delay but still to have access to hotkeys like on a real Mac, what changes should I make ?

 

Thanks !

Link to comment
Share on other sites
hardcorehenry
hardcorehenry
Posted
Posted (edited)
8 hours ago, maxb2000 said:

Hi guys,

 

1980-01-01 02:04:41.308484+0200  localhost kernel[0]: Kext ru.joedm.SMCSuperIO did not stop (return code 0x5).
1980-01-01 02:04:41.308498+0200  localhost kernel[0]: Kext ru.joedm.SMCSuperIO can't unload - module stop returned 0xdc008017.

 

I have these in the logs, should I no longer use SMCSuperIO ? I don't even now for what is for. Maybe sensors ?

 

Second question:

 

I want to boot directly into macOS without a delay but still to have access to hotkeys like on a real Mac, what changes should I make ?

 

Thanks !

 

To resolve problems with loading SMCSuperIO, try NVRAM>Add>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14>oem-product, oem-vendor, oem-board.
You’d have to change Misc>Security>ExposeSensitiveData to 14

Example for ASUS H81M-E

Spoiler

431195285_ScreenShot2020-09-09at10_19_09AM.png.f6c9eefcac37891b380ea608266140ae.png

 

Here you can find out more.

 

EDIT:

Noticed, that even with this additional info in NVRAM SMCSuperIO loads randomly, which means it doesn’t solves the problem.

Edited by hardcorehenry
  • Like 1
Link to comment
Share on other sites
nmano
nmano
Posted
Posted

I update OC 0.6.2

Stuck on Failed to find SB mode Disabled

Please help me How to fix this error.

Thanks.

IMG_4480.thumb.jpg.0ccdfa7b55ccc284268584a367f3494d.jpg

  • Confused 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
41 minutes ago, nmano said:

I update OC 0.6.2

Stuck on Failed to find SB mode Disabled

Please help me How to fix this error.

Thanks.

 

 

Check you config.plist SecureBootModel=Disabled not Disable :) Update your config.plist for others missing keys.
 

You update to Release 0.6.1 or 0.6.2 Beta !!!

 

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites
nmano
nmano
Posted
Posted
28 minutes ago, Matgen84 said:

 

Check you config.plist SecureBootModel=Disabled not Disable :) Update your config.plist for others missing keys.
 

You update to Release 0.6.1 or 0.6.2 Beta !!!

 

OC 0.6.2 worked now.

Spelling mistake Thank you.

Link to comment
Share on other sites
voyager99
voyager99
Posted
Posted (edited)

Hello, would appreciate any advice on a slow boot issue I'm having. I am currently running Catalina 10.15.6 (build 19G2021 August 12, 2020) using OpenCore 0.60 with an i7-10700K on an MSI MPG Z490M GAMING EDGE WIFI board. The system is stable, but the boot time is running about 15 seconds slower than it should. Running the command:

 

log show --last boot --style syslog

Update: System kernel log from HackinTool:

 

I believe I've identified the issue (about a 15 second delay) as an incompatible wifi module (Intel AX201) on this motherboard. In my config.plist, my smbios is set to iMac19,1 to allow it to work with Intel Comet Lake CPU's.

 

Partial log file displaying the issue I believe is the problem.

New kernel log below:

2020-09-09 14:31:05.743794-0400  localhost kernel[0]: BSD root: disk4s5
2020-09-09 14:31:05.743795-0400  localhost kernel[0]: , major 1, minor 14
2020-09-09 14:31:05.743872-0400  localhost kernel[0]: (IOStorageFamily) <IOStorageFamily`dkreadwritecompletion(void*, void*, int, unsigned long long)> disk4s5: device is not readable.
2020-09-09 14:31:05.743875-0400  localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs_mountfs: buf_meta_bread failed with 13
2020-09-09 14:31:05.743878-0400  localhost kernel[0]: (HFS) <HFS`hfs_mount> hfs_mount: hfs_mountfs returned error=13 for device unknown-dev
2020-09-09 14:31:05.743880-0400  localhost kernel[0]: hfs_mountroot failed: 13
2020-09-09 14:31:05.743882-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mountroot:1502: apfs: mountroot called!
2020-09-09 14:31:05.743980-0400  localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:294: /dev/disk4: device accelerated crypto: 0 (compiled @ Jul  6 2020 11:46:26)
2020-09-09 14:31:05.743983-0400  localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:297: /dev/disk4: device_handle block size 4096 block count 249999948 features 16 internal solidstate
2020-09-09 14:31:05.744050-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1121: /dev/disk4: initializing cache w/hash_size 16384 and cache size 40960
2020-09-09 14:31:05.753043-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1385: /dev/disk4: checkpoint search: largest xid 36575, best xid 36575 @ 114
2020-09-09 14:31:05.753428-0400  localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 40957 extent 1 omap 550 snap_meta 1 er: 0 udata: 2665387 fs_alloc_count 2710321
2020-09-09 14:31:05.753430-0400  localhost kernel[0]: (apfs) <apfs`log_debug> er_state_obj_get_for_recovery:4639: No ER state object for volume hack1nt0sh - rolling is not happening, nothing to recover.
2020-09-09 14:31:05.753432-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1318: Promoter has been locked for /dev/disk4
2020-09-09 14:31:05.753470-0400  localhost kernel[0]: (apfs) <apfs`log_info> handle_mount:329: vol-uuid: B6C8D021-9BB7-4A78-87BF-3EC54A7EA42A block size: 4096 block count: 249999948 (unencrypted; flags: 0x1; features: 1.0.12)
2020-09-09 14:31:05.754127-0400  localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:342: setting dev block size to 4096 from 512
2020-09-09 14:31:05.754130-0400  localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:383: ROSV: apfs mounted RO and is the system volume of a volume group and mounted as the root fs: creating the shadow fs_root
2020-09-09 14:31:05.754134-0400  localhost kernel[0]: (apfs) <apfs`log_debug> fs_setup_shadow_fs_root_tree:1452: Created the shadow_fs_root tree <private>
2020-09-09 14:31:05.754156-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_volume_group_update:6431: Set volume (role 0x1) to 41d xid 0
2020-09-09 14:31:05.754181-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1489: mounted volume: hack1nt0sh
2020-09-09 14:31:05.754250-0400  localhost kernel[0]: ioqueue_depth = 256,   ioscale = 8
2020-09-09 14:31:05.754849-0400  localhost kernel[0]: NOTE: Attempting ROSV mount
2020-09-09 14:31:05.754850-0400  localhost kernel[0]: NOTE: DETECTED ROSV CONFIG
2020-09-09 14:31:05.754851-0400  localhost kernel[0]: attempting kernel mount for data volume...
2020-09-09 14:31:05.756079-0400  localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 89881 extent 1509 omap 1944 snap_meta 1 er: 0 udata: 7946200 fs_alloc_count 8088476
2020-09-09 14:31:28.797446-0400  localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2020-09-09 14:31:28.799850-0400  localhost kernel[0]: PMRD: power event 4 args 0x3b773984eebb8303 0x0
2020-09-09 14:31:28.804643-0400  localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x0
2020-09-09 14:31:28.804644-0400  localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x0
2020-09-09 14:31:28.804651-0400  localhost kernel[0]: PMRD: destroyed capability client set 0x3b773984f0f90833
2020-09-09 14:31:28.804658-0400  localhost kernel[0]: PMRD: PowerChangeDone: ON_STATE->ON_STATE
2020-09-09 14:31:28.804858-0400  localhost kernel[0]: PMRD: power event 12 args 0x3b773984f0f924e3 0x0
2020-09-09 14:31:28.804860-0400  localhost kernel[0]: PMRD: SleepWake UUID queued: B3ED6BB3-1B07-4D88-8C04-DB703B6CA917
2020-09-09 14:31:28.805129-0400  localhost kernel[0]: Waiting for DSMOS...
2020-09-09 14:31:28.815566-0400  localhost kernel[0]: ifnet_attach: All kernel threads created for interface en0 have been scheduled at least once. Proceeding.
2020-09-09 14:31:28.857175-0400  localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs: mounted samsung1Tb on device disk2s1
2020-09-09 14:31:29.045311-0400  localhost kernel[0]: PMRD: power event 5 args 0x3b773984eebb8303 0x0
2020-09-09 14:31:29.046825-0400  localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToSleep = 60
2020-09-09 14:31:29.046830-0400  localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToDim = 60
2020-09-09 14:31:29.047114-0400  localhost kernel[0]: PMRD: aggressiveness changed: system 0->60, display 60
2020-09-09 14:31:29.047115-0400  localhost kernel[0]: PMRD: idle time -> 0 secs (ena 1)
2020-09-09 14:31:29.047115-0400  localhost kernel[0]: PMRD: idle sleep timer enabled

 

My question is, can you please tell me how I can prevent Catalina from trying to load/enable Wifi (I tried disabling Wifi and Bluetooth in the BIOS without success)? Can I disable it in the devices section in my config.plist or by editing a .kext? Thank you for any help you can provide.

I have 2 NVME SSD's (1 Samsung 970 and 1 ADATA SX8200 Pro).

Trim support has been enabled.

Any ideas on how to resolve the boot delay? Appreciated!

Edited by voyager99
Link to comment
Share on other sites
voyager99
voyager99
Posted
Posted
2 hours ago, iCanaro said:

https://openintelwireless.github.io/itlwm/Compat.html

Hey, thanks, appreciate your feedback!

I tried installing the itlwmx kext for the Intel AX201, but unfortunately that had no effect (the driver failed to load as well).

However, I have an update.

The kernel log extracted using HackinTool is pointing to a different issue:

 

2020-09-09 14:31:05.743794-0400  localhost kernel[0]: BSD root: disk4s5
2020-09-09 14:31:05.743795-0400  localhost kernel[0]: , major 1, minor 14
2020-09-09 14:31:05.743872-0400  localhost kernel[0]: (IOStorageFamily) <IOStorageFamily`dkreadwritecompletion(void*, void*, int, unsigned long long)> disk4s5: device is not readable.
2020-09-09 14:31:05.743875-0400  localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs_mountfs: buf_meta_bread failed with 13
2020-09-09 14:31:05.743878-0400  localhost kernel[0]: (HFS) <HFS`hfs_mount> hfs_mount: hfs_mountfs returned error=13 for device unknown-dev
2020-09-09 14:31:05.743880-0400  localhost kernel[0]: hfs_mountroot failed: 13
2020-09-09 14:31:05.743882-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mountroot:1502: apfs: mountroot called!
2020-09-09 14:31:05.743980-0400  localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:294: /dev/disk4: device accelerated crypto: 0 (compiled @ Jul  6 2020 11:46:26)
2020-09-09 14:31:05.743983-0400  localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:297: /dev/disk4: device_handle block size 4096 block count 249999948 features 16 internal solidstate
2020-09-09 14:31:05.744050-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1121: /dev/disk4: initializing cache w/hash_size 16384 and cache size 40960
2020-09-09 14:31:05.753043-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1385: /dev/disk4: checkpoint search: largest xid 36575, best xid 36575 @ 114
2020-09-09 14:31:05.753428-0400  localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 40957 extent 1 omap 550 snap_meta 1 er: 0 udata: 2665387 fs_alloc_count 2710321
2020-09-09 14:31:05.753430-0400  localhost kernel[0]: (apfs) <apfs`log_debug> er_state_obj_get_for_recovery:4639: No ER state object for volume hack1nt0sh - rolling is not happening, nothing to recover.
2020-09-09 14:31:05.753432-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1318: Promoter has been locked for /dev/disk4
2020-09-09 14:31:05.753470-0400  localhost kernel[0]: (apfs) <apfs`log_info> handle_mount:329: vol-uuid: B6C8D021-9BB7-4A78-87BF-3EC54A7EA42A block size: 4096 block count: 249999948 (unencrypted; flags: 0x1; features: 1.0.12)
2020-09-09 14:31:05.754127-0400  localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:342: setting dev block size to 4096 from 512
2020-09-09 14:31:05.754130-0400  localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:383: ROSV: apfs mounted RO and is the system volume of a volume group and mounted as the root fs: creating the shadow fs_root
2020-09-09 14:31:05.754134-0400  localhost kernel[0]: (apfs) <apfs`log_debug> fs_setup_shadow_fs_root_tree:1452: Created the shadow_fs_root tree <private>
2020-09-09 14:31:05.754156-0400  localhost kernel[0]: (apfs) <apfs`log_debug> nx_volume_group_update:6431: Set volume (role 0x1) to 41d xid 0
2020-09-09 14:31:05.754181-0400  localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1489: mounted volume: hack1nt0sh
2020-09-09 14:31:05.754250-0400  localhost kernel[0]: ioqueue_depth = 256,   ioscale = 8
2020-09-09 14:31:05.754849-0400  localhost kernel[0]: NOTE: Attempting ROSV mount
2020-09-09 14:31:05.754850-0400  localhost kernel[0]: NOTE: DETECTED ROSV CONFIG
2020-09-09 14:31:05.754851-0400  localhost kernel[0]: attempting kernel mount for data volume...
2020-09-09 14:31:05.756079-0400  localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 89881 extent 1509 omap 1944 snap_meta 1 er: 0 udata: 7946200 fs_alloc_count 8088476
2020-09-09 14:31:28.797446-0400  localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2020-09-09 14:31:28.799850-0400  localhost kernel[0]: PMRD: power event 4 args 0x3b773984eebb8303 0x0
2020-09-09 14:31:28.804643-0400  localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x0
2020-09-09 14:31:28.804644-0400  localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x0
2020-09-09 14:31:28.804651-0400  localhost kernel[0]: PMRD: destroyed capability client set 0x3b773984f0f90833
2020-09-09 14:31:28.804658-0400  localhost kernel[0]: PMRD: PowerChangeDone: ON_STATE->ON_STATE
2020-09-09 14:31:28.804858-0400  localhost kernel[0]: PMRD: power event 12 args 0x3b773984f0f924e3 0x0
2020-09-09 14:31:28.804860-0400  localhost kernel[0]: PMRD: SleepWake UUID queued: B3ED6BB3-1B07-4D88-8C04-DB703B6CA917
2020-09-09 14:31:28.805129-0400  localhost kernel[0]: Waiting for DSMOS...
2020-09-09 14:31:28.815566-0400  localhost kernel[0]: ifnet_attach: All kernel threads created for interface en0 have been scheduled at least once. Proceeding.
2020-09-09 14:31:28.857175-0400  localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs: mounted samsung1Tb on device disk2s1
2020-09-09 14:31:29.045311-0400  localhost kernel[0]: PMRD: power event 5 args 0x3b773984eebb8303 0x0
2020-09-09 14:31:29.046825-0400  localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToSleep = 60
2020-09-09 14:31:29.046830-0400  localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToDim = 60
2020-09-09 14:31:29.047114-0400  localhost kernel[0]: PMRD: aggressiveness changed: system 0->60, display 60
2020-09-09 14:31:29.047115-0400  localhost kernel[0]: PMRD: idle time -> 0 secs (ena 1)
2020-09-09 14:31:29.047115-0400  localhost kernel[0]: PMRD: idle sleep timer enabled

 

I have 2 NVME SSD's (1 Samsung 970 and 1 ADATA SX8200 Pro).

Link to comment
Share on other sites
Planet X
Planet X
Posted
Posted (edited)

I did change to OpenCore lately because I want to be prepared for Big Sur. I have a working config.plist now. Everything works fine and sleep does work as well. So first thank you for the good job guys! But somehow I don't understand the manual on the Dortina website. I use a Coffee-Lake CPU i7 8700k on an ASUS Z370 Prime A motherboard. From the installation guide I should use "EnableWriteUnprotector NO" and therefor use "RebuildAppleMemoryMap YES" and "SyncRuntimePermissions YES". I can use the 3 options enabled altogether without problems, but as soon when I disable "EnableWriteUnprotector" I cannot boot anymore. It stays on the black screen with the Apple Logo. So for now I keep "EnableWriteUnprotector" enabled and because of the warning in the Dortina guide I have disabled "RebuildAppleMemoryMap" and "SyncRuntimePermissions". And still everything just works fine. Could you please tell me what "SyncRuntimePermissions" really does in more human words than has been written on Dortina guide? Should I leave it disabled or is there an advantage when I would make use of it?  Also what could happen if I would use "EnableWriteUnprotector" and "RebuildAppleMemoryMap" and "SyncRuntimePermissions" enabled?

Edited by Planet X
  • Like 1
Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted

@Planet X SyncRuntimePermissions is more of a bug fix to make RebuildAppleMemoryMap properly on most machines. The idea of using RebuildAppleMemoryMap instead of EnableWriteUnprotector is to let the OS map memory more securely, i.e. memory that should be writable cannot be executed from and vice-versa. With EnableWriteUnprotector, all memory is writable (when calling UEFI, NOT during regular OS runtime) and most data is executable, violating common security patterns. However, if EnableWriteUnprotector cannot be disabled with both on, you are out of luck for now regarding security.

  • Like 3
  • Thanks 2
Link to comment
Share on other sites
dionnode
dionnode
Posted
Posted (edited)

Hi there,

using OC 0.6.0, during boot, I have some message like this:

" No scheme for arch at 0 index context...."

 

I have no problem at all with this version of OC on Catalina, just wondering about that message abnormal

 

Thanks in advance 

 

please take a look my config.plist

 

config.plist

Edited by dionnode
Link to comment
Share on other sites
feartech
feartech
Posted
Posted
6 minutes ago, dionnode said:

Hi there,

using OC 0.6.0, during boot, I have some message like this:

" No scheme for arch at 0 index context...."

 

I have no problem at all with this version of OC on Catalina, just wondering about that message abnormal

 

Thanks in advance 

 

please take a look my config.plist

 

config.plist

The arch sections was introduced in 0.6.1 either remove the entries or update to 0.6.1

  • Like 1
Link to comment
Share on other sites
dionnode
dionnode
Posted
Posted (edited)
28 minutes ago, feartech said:

The arch sections was introduced in 0.6.1 either remove the entries or update to 0.6.1

 

Thanks for your reply (feartech),

it's working now, no more abnormal message. I deleted every arch

Edited by dionnode
  • Like 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

I'm trying to boot an X220 with OpenCore.

I got stuck at  

52:215 00:030 OCAK: Symbol _panic was resolved for kext as.vit9696.VirtualSMC to FFFFFF800026B9A0
52:246 00:030 OCAK: Symbol _strlcpy was resolved for kext as.vit9696.VirtualSMC to FFFFFF8000345F70
52:276 00:030 OCAK: Symbol _strlen was resolved for kext as.vit9696.VirtualSMC to FFFFFF800037D860
52:307 00:030 OCAK: Symbol _version_major was resolved for kext as.vit9696.VirtualSMC to FFFFFF800094AF10
52:337 00:030 OCAK: Symbol _vm_protect was resolved for kext as.vit9696.VirtualSMC to FFFFFF80003381A0
52:380 00:043 OC: Prelinked injection VirtualSMC.kext () - Success
52:410 00:030 OC: Prelink size 70012928 kext offset 69742592 reserved 270336
52:573 00:162 OCAK: com.apple.driver.AppleIntelCPUPowerManagement got KXLD 0 0
52:627 00:053 OCAK: com.apple.driver.AppleAHCIPort got KXLD 0 0
52:658 00:031 OCAK: IOAHCIPort replace count - 1
52:688 00:029 OCAK: Patch success com.apple.driver.AppleAHCIPort
52:721 00:033 OCAK: com.apple.iokit.IOUSBHostFamily got KXLD 0 0
52:751 00:030 OCAK: Skipping port patch IOUSBHostFamily on 170700
52:807 00:055 OCAK: com.apple.driver.usb.AppleUSBXHCI got KXLD 0 0
52:837 00:030 OCAK: RemoveUsbLimitV2 replace count - 1
52:867 00:030 OCAK: Patch success com.apple.driver.usb.AppleUSBXHCI
52:924 00:056 OCAK: com.apple.driver.usb.AppleUSBXHCIPCI got KXLD 0 0
52:955 00:031 OCAK: RemoveUsbLimitV1 base lookup failure Not Found
52:986 00:030 OCAK: Failed to apply legacy port patch AppleUSBXHCIPCI - Not Found
53:016 00:030 OCAK: Assuming success for legacy port AppleUSBXHCIPCI on 170700
53:048 00:031 OCAK: com.apple.iokit.IOPCIFamily got KXLD 0 0
53:079 00:031 OCAK: AppleIoMapper replace count - 1
53:110 00:030 OCAK: Patch success com.apple.iokit.IOPCIFamily AppleIoMapper
53:164 00:053 OC: Prelinked status - Success
53:228 00:064 Saving to B849C018, given 4096, requested 71
53:259 00:031 OCABC: MMIO devirt start
53:290 00:030 OCABC: MMIO devirt 0xF80F8000 (0x1 pages, 0x8000000000000001) skip 0
53:320 00:030 OCABC: MMIO devirt 0xFED1C000 (0x4 pages, 0x8000000000000001) skip 0
53:351 00:030 OCABC: MMIO devirt end, saved 20 KB

Following that, there a lot of 0 in the log.

 

Any idea ?

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

AppleDebug was activated.

I replaced OpenCore.efi, OpenRuntime.efi and Bootstrap.efi by revision 0.6.1 I found on your site. Before it was my own compilation (NOOPT_XCODE5).

 

I was able to go further.

The log file now is only 262144 byte 0. But I got a panic file containing "No HPETs available...CPU(s) configured incorrectly". Should be too hard to find the cause.

 

Is the 256KB block of 0 in the log file a known bug ?

Link to comment
Share on other sites
mhaeuser
mhaeuser
Posted
Posted (edited)
6 minutes ago, Jief_Machak said:

Is the 256KB block of 0 in the log file a known bug ?

No, it's by design. The log has a generous constant file size to limit FS operations to a minimum - Aptio IV FAT driver is know for corruptions.

 

6 minutes ago, Jief_Machak said:

AppleDebug was activated.

Were there Apple messages in the log, just outside of the pasted range?

 

6 minutes ago, Jief_Machak said:

But I got a panic file containing "No HPETs available...CPU(s) configured incorrectly". Should be too hard to find the cause.

I guess your FW lacks the HPET device (borked name?), or it's conditionally disabled?

Edited by Download-Fritz
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted
2 minutes ago, Jief_Machak said:

What's still unclear is : could I override the whole DSDT by a custom one. Starting from the original DSDT, I made a custom one that doesn't require any further patch. In OpenCore, it looks like everything should be SSDT.

You can load a custom DSDT using OpenCore like you would load a SSDT.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...