Contribute
Register

Ohchang's build: Gigabyte Z590 Vision G + i7-10700K + AMD RX580

I was wondering if any of you have problems with DP/HDMI Audio? I'm experiencing a crackling issues when listening to music (YuTube, VLC, etc.) My build is Z590 VISION D F6, GA RX580 GAMING 4GB. When using the onboard ALC 4080 I have no issues. This is happening when I'm connecting more than one monitor. Testet with Big Sur 11.6, Monterey 12.0.1, with and without AppleALC/U. Note: DP/HDMI Audio is working on Windows and Linux perfectly. When the crackling issues are happening and I put load to the GPU, problems goes away. I'm start to thinking this GPU is too old...
 
Last edited:
tsanko.dimitrov said:
I was wondering if any of you have problems with DP/HDMI Audio? I'm experiencing a crackling issues when listening to music (YuTube, VLC, etc.) My build is Z590 VISION D F6, GA RX580 GAMING 4GB. When using the onboard ALC 4080 I have no issues. This is happening when I'm connecting more than one monitor. Testet with Big Sur 11.6, Monterey 12.0.1, with and without AppleALC/U. Note: DP/HDMI Audio is working on Windows and Linux perfectly. When the crackling issues are happening and I put load to the GPU, problems goes away. I'm start to thinking this GPU is too old...
Click to expand...
If HD audio is working fine in Linux and Windows, as you say, then it seems more likely to me that there's something funky in your OpenCore/macOS configuration. I wouldn't think the RX 580 is failing, unless you dropped it on a tiled floor at some time.
 
zzmadd said:
I solved using Bios F4 but it's more of a workaround than a real understanding of what happens...
Click to expand...
Thanks for the info! Going back to F4, no more reboot after wake (so far)!

Guys! Stick with F4 or go back to it!
 
Hi, I have the same motherboard and CPU with you. I want to know why you set the SMBIOS to be iMac20.2. It's said in dortania OC guide that I should choose iMac20.1 for 'i7-10700K and lower(i.e. 8 core and lower)' or iMac20.2 for 'i9-10850K and higher(i.e. 10 core)', so I'm confused. Is iMac20.2 more compatible with the 10700K system than iMac20.1?

I'm a new one to build a hackintosh, but I'm glad to study everything. So, before beginning to install I want to be careful and learn everything as clear as possible. I would be very grateful if I could get the answer.
 
lqgmeow said:
Hi, I have the same motherboard and CPU with you. I want to know why you set the SMBIOS to be iMac20.2. It's said in dortania OC guide that I should choose iMac20.1 for 'i7-10700K and lower(i.e. 8 core and lower)' or iMac20.2 for 'i9-10850K and higher(i.e. 10 core)', so I'm confused. Is iMac20.2 more compatible with the 10700K system than iMac20.1?

I'm a new one to build a hackintosh, but I'm glad to study everything. So, before beginning to install I want to be careful and learn everything as clear as possible. I would be very grateful if I could get the answer.
Click to expand...
I suppose that reference from Dortania was more of a failsafe. In practice, though, iMac20,1 and iMac20,2 are fairly interchangeable with some motherboards (even Z590's). In fact, iMac20,2 can be quite well suited for both i7, and i9 CPU's; but with 10-core (or greater), that's anybody's guess.

The Prime Z490-A (with an i7-10700K) uses the iMac20,2 definition, which has solved several issues, in my case. The default is iMac20,1, which it most closely emulates.

If you're unsure, just use iMac20,1. Cheers.
 
Last edited by a moderator:
After over one week of no issues, my system crashed again (while doing a TimeMachine backup) over the network. I have now switched back to F2158680 and will report back how it performs over time. Does somebody know, where to find the kernel panic log file for Monterey 12.1 beta 3?
 
root2 said:
After over one week of no issues, my system crashed again (while doing a TimeMachine backup) over the network. I have now switched back to F2158680 and will report back how it performs over time. Does somebody know, where to find the kernel panic log file for Monterey 12.1 beta 3?
Click to expand...
Use /Applications/Utilities/Console.app. That should give what you want. Cheers.
 
Thanks found it here:

Code: 
/Library/Logs/DiagnosticReports/Retired/Kernel-2021-11-21-002115.panic

The error is, I think, network related (as I said, at the time it did a TimeMachine backup using SMB onto my NAS). Do you think it is worth switching back from F3158680 to F2158680? Or is this panic completely unrelated and not worth bothering?

Code: 
"timestamp":"2021-11-21 00:21:15.00 +0100"
"bug_type":"210",
"os_version":"macOS 12.1 (21C5039b)"

panic(cpu 6 caller 0xffffff8001f1d514): assertion failed: hash_entry->soflow_db->soflow_db_feat_ctxt_cnt > 0,
file: /System/Volumes/Data/SWE/macOS/BuildRoots/c40be6c978/Library/Caches/com.apple.xbs/Sources/xnu/xnu-8019.60.69/bsd/net/content_filter.c, line: 5819
Panicked task 0xffffff8bba9a4ce0: 5 threads: pid 250: mDNSResponder

Backtrace (CPU 6), panicked thread: 0xffffff8bb8989540, Frame : Return Address
0xffffffd103253a10 : 0xffffff8001688e8d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd103253a60 : 0xffffff80017e8da5 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd103253aa0 : 0xffffff80017d8573 mach_kernel : _kernel_trap + 0x533
0xffffffd103253af0 : 0xffffff8001628a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd103253b10 : 0xffffff800168925d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd103253c30 : 0xffffff8001688a16 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd103253c90 : 0xffffff8001f16cd9 mach_kernel : _panic + 0x54
0xffffffd103253d00 : 0xffffff8001f1d514 mach_kernel : _panic_machine_check64 + 0x72d
0xffffffd103253d10 : 0xffffff8001ac5622 mach_kernel : _cfil_sock_data_pending + 0x1832
0xffffffd103253d30 : 0xffffff8001ac5485 mach_kernel : _cfil_sock_data_pending + 0x1695
0xffffffd103253d60 : 0xffffff8001d0b8df mach_kernel : _soflow_detach + 0x73f
0xffffffd103253d90 : 0xffffff8001d0b31b mach_kernel : _soflow_detach + 0x17b
0xffffffd103253dd0 : 0xffffff8001ccb657 mach_kernel : _soclose_locked + 0x837
0xffffffd103253e20 : 0xffffff8001ccbacb mach_kernel : _soclose + 0xab
0xffffffd103253e40 : 0xffffff8001c347c3 mach_kernel : _kern_close_file_for_direct_io + 0x463
0xffffffd103253eb0 : 0xffffff8001c352db mach_kernel : _fdt_exec + 0x70b
0xffffffd103253f40 : 0xffffff8001d9f5f4 mach_kernel : _unix_syscall64 + 0x204
0xffffffd103253fa0 : 0xffffff8001629226 mach_kernel : _hndl_unix_scall64 + 0x16

Process name corresponding to current thread (0xffffff8bb8989540): mDNSResponder
Boot args: -v keepsyms=1 debug=0x100 shikigva=40 shiki-id=Mac-7BA5B2D9E42DDD94 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21C5039b

Kernel version:
Darwin Kernel Version 21.2.0: Thu Nov 11 00:10:13 PST 2021; root:xnu-8019.60.69~7/RELEASE_X86_64
Kernel UUID: F6233E1D-1FDF-3B24-9FFB-F434FCDC4A91
KernelCache slide: 0x0000000001400000
KernelCache base:  0xffffff8001600000
Kernel slide:      0x0000000001410000
Kernel text base:  0xffffff8001610000
__HIB  text base: 0xffffff8001500000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 37541454625547
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00002224cd113d02
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000013bcbfe497 0x0000000000000000
Zone info:
Foreign   : 0xffffff800861e000 - 0xffffff800862b000
Native    : 0xffffff808759c000 - 0xffffffa08759c000
Readonly  : 0xffffff8554268000 - 0xffffff86edbfc000
Metadata  : 0xffffffff4c7b9000 - 0xffffffff6cfa9000
Bitmaps   : 0xffffffff6cfa9000 - 0xffffffff84fa9000
 
root2 said:
The error is, I think, network related (as I said, at the time it did a TimeMachine backup using SMB onto my NAS). Do you think it is worth switching back from F3158680 to F2158680? Or is this panic completely unrelated and not worth bothering?
Click to expand...
The mDNSResponder is suggestive of it being network related, but beyond that, it's difficult to guess. Boot arguments can sometimes be a cause. keepsyms=1, particularly, while useful for debugging, can be a potential candidate for all kinds of random crashes. shikigva=80 might be worth trying (instead of 40). Is hardware acceleration enabled on your GPU? If not, maybe that's a contributing factor.

That said, an ill-chosen device-id could might still be the culprit. Maybe try F3150000 or F2150000.
root2 said:
Process name corresponding to current thread (0xffffff8bb8989540): mDNSResponder
Boot args: -v keepsyms=1 debug=0x100 shikigva=40 shiki-id=Mac-7BA5B2D9E42DDD94 chunklist-security-epoch=0 -chunklist-no-rev2-dev
Click to expand...
 
macntosh said:
I suppose that reference from Dortania was more of a failsafe. In practice, though, iMac20,1 and iMac20,2 are fairly interchangeable with some motherboards (even Z590's). In fact, iMac20,2 can be quite well suited for both i7, and i9 CPU's; but with 10-core (or greater), that's anybody's guess.

The Prime Z490-A (with an i7-10700K) uses the iMac20,2 definition, which has solved several issues, in my case. The default is iMac20,1, which it most closely emulates.

If you're unsure, just use iMac20,1. Cheers.
Click to expand...
Ok, got it. Thanks very much!
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top