Jump to content

applCore

Members
  • Content Count

    8
  • Joined

  • Last visited

About applCore

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

473 profile views
  1. applCore

    Lilu — kext and process patcher

    I'm having a devil of a time with a real Mac Pro with Mojave (10.14) and a Gigabyte AORUS Radeon RX 580 8GB (GV-RX580AORUS-8GD). I'm getting panics like this with various applications and games: panic(cpu 0 caller 0xffffff8014ad01dd): "PHYSMAP_PTOV bounds exceeded, 0xffffff96fffffc00, 0xfffffe9700000000, 0xfffffeb800000000"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.261.4/osfmk/i386/pmap.h:515 Apple seems to be a real putz about the situation and are washing their hands of the issue. Is it possible that running Lilu with WhateverGreen (previously Shiki) would resolve such issues on a Mac Pro? Are there any gotchas that one should be aware of when loading these kexts up without Clover? Would I need to load this directly into the system kexts, non-system library kexts or something else with EFI?
  2. applCore

    What does this error mean in the console?

    I'd also like to understand this better as I'm having it on an actual Mac Pro with Mojave. Really concerns me since I'm having some strange hangs and such issues that seem filesystem related in some way, but all hardware is testing out as good. Console contents: error 10:01:01.123456 -0000 deleted fsctl error: Inappropriate ioctl for device, using HARDCODED low disk threshold 10737418140 for volume_size: 9314695214218 It might be worth looking closer at https://apple.stackexchange.com/questions/254810/what-is-the-deleted-daemon-in-macos-sierra I'm wondering what process is triggering the `deleted` CacheDelete service (daemon) in this case. It doesn't seem clear about how to isolate this kind of information, but I have to assume something is registered to CacheDelete and causing this and has to be trackable somehow. One thing that we can do is to use `lsof -p <PID_NUMBER>` from Console info down below and get some more info like this: $ lsof -p 779 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME deleted 779 USERNAME cwd DIR 1,26 2048 2 / deleted 779 USERNAME txt REG 1,26 495200 133407003 /System/Library/PrivateFrameworks/CacheDelete.framework/deleted deleted 779 USERNAME txt REG 1,26 22520 133451272 /Library/Preferences/Logging/.plist-cache.A8Idtkno deleted 779 USERNAME txt REG 1,26 303464 134085235 /Library/Application Support/CrashReporter/SubmitDiagInfo.domains deleted 779 USERNAME txt REG 1,26 27154320 133440473 /usr/share/icu/icudt62l.dat deleted 779 USERNAME txt REG 1,26 973824 133435892 /usr/lib/dyld deleted 779 USERNAME 0r CHR 3,2 0t0 353 /dev/null deleted 779 USERNAME 1u CHR 3,2 0t0 353 /dev/null deleted 779 USERNAME 2u CHR 3,2 0t0 353 /dev/null deleted 779 USERNAME 3r REG 1,26 303464 134085235 /Library/Application Support/CrashReporter/SubmitDiagInfo.domains
  3. Yesterday's WWDC has set a huge number of real Mac owners into an angry spiral. Many users have systems that are good enough to run 10.14, but are now excluded for likely largely financial and marketing positioning from Apple. For example 2009 Mac Pros with Metal capable video cards shouldn't be blocked whatsoever, but there are many others too who should be pretty much fine if they're not doing serious gaming or animation on their iMacs or Mac Minis. We need to start figuring out or pulling together some instructions (if it's already possible) for real Macs to run Clover and to define custom SMBIOS entries. Basically I'm 100% on board with running real Macs as Hackintosh systems at this point. I'm not willing to flush over $20,000 of Apple hardware down the toilet, especially when these systems still run faster than most current systems and are working great for even VR game dev. Can someone give some insight as to what may need to be done to start moving down this road now so we can start testing this out now on spare systems that have been blacklisted by Apple?
  4. applCore

    VoodooHDA 2.9.2

    @mnfesq Bongiovi directly interacts with the audio and provides an extra output so that it modifies your audio system wide. The system's definitely powerful enough (4 GHz i7 + 64 GB RAM). The base mobo is a ROG Maximus VIII Hero Alpha so the audio is a SupremeFX 2015 (All recommendations I see say either ALC1150 or VoodooHDA (which seems better or more reliable).) The only audio problem that has manifested itself is with apps like this that enhance or modify the overall system audio, otherwise system audio is fine.
  5. applCore

    VoodooHDA 2.9.2

    I'm finding problems with some apps like Bongiovi working with VoodooHDA (garbled or stuttery sound; sounds like the sound is being 90% chopped off, but some is still getting out as almost a rapid beat). Is there a way to troubleshoot this or get some help here to figure out what's wrong?
  6. Has anyone had trouble installing 10.13 on a 2010 Mac Pro? This system is entirely supported, but not installing. I have succeeded in installing it on NON supported Mac Pros from 2009, but this 2010 issue is so far a mystery! The installer prompts to shut down and hold the power button in as per usual. After doing as instructed and holding the power button in to get the fast blink + long chime for firmware / EFI update, the system then issues the normal chime (again, this is usual), but instead of going into the installation, it just goes right back to 10.12 and starts the installer again which has the same old shutdown + hold power prompt. I can do this 20 times and there is no difference. I have reset the NVRAM, no change. Unfortunately this has been the same with the last few betas and final release. Same results each and every time for this one. Thought maybe the NVRAM might be buggered up so I cmd-opt-p-r'd the {censored} out of it and still no joy. The thing that I'm seeing is that the boot ROM is stuck at version: MP51.007F.B03 (SMC Version (system): 1.39f11). This should be updated to MP51.0084.B00 by the final 10.13 release. Even my several firmware hacked 2009 systems show MP51.0084.B00 while my 2010 is not taking the firmware. Anyone think there is a way to use some hackintosh methodology to manually check and place the payload in the EFI?
×