Jump to content

zxv

Members
  • Content Count

    192
  • Joined

  • Last visited

Everything posted by zxv

  1. Been getting "Error allocating 0x… pages at 0x… alloc type 2 Couldn't allocate runtime area" failure messages at boot ever since I updated to 10.14.4. Booting into recovery and inputing "kextcache -invalidate /Volume/Macintosh\ HD" allows system to start normally. But issue usually returns at next reboot.
  2. zxv

    Hackintool v1.8.3

    A name change makes sense of course. It's just that "Hackintool" seems so generic and non-informative. Of the 3, this one appears best.
  3. zxv

    Hackintool v1.8.3

    Why the name and icon change? I dislike it.
  4. zxv

    Clover problems report & features request

    Cool. Good to know we're removing useful information from standard builds.
  5. zxv

    Clover problems report & features request

    Clover not detecting XMP profiles anymore it seems (no mention of XMP in bdmesg). Not sure if something changed on newer boards (Z390).
  6. zxv

    VirtualSMC — SMC Emulator

    It works. Though I seem to have lost GPU sensor data in iStat, as well as some temperature readings. Is there additional configuration I need to set in order get correct SMC output for my model (iMac17,1)?
  7. zxv

    [pre-release] macOS Mojave

    I think your explanation is good. As far as I can tell (at least according to the HW monitors) the iGPU is always in some state of low-level activity alongside the dGPU. Far more noticeable of course when video is playing. Inserting a 'headless' ig-platform-id specific to one's iGPU is apparently helpful as well.
  8. zxv

    Clover General discussion

    NVMe drives boot natively via UEFI since macOS 10.13—nothing extra is necessary. I've been using one since September of last year. No clue re: legacy (no idea why anyone should care anymore either).
  9. zxv

    Site Issues

    Can't upload images to change profile pic (nor as attachments). Admin might check permissions on server uploads directory.
  10. zxv

    [pre-release] macOS Mojave

    Silly to expect any hardware to be indefinitely futureproof. There may be deeper optimizations in Mojave that necessitate this move. We don't know yet. Either way I don't think Apple is being at all unreasonable cutting off support for hardware 7+ years old.
  11. zxv

    [pre-release] macOS Mojave

    It burns through more development resources than people realize to try and continually support legacy hardware, and delays rollouts of newer features. It's nice to not have to upgrade every couple years (like we used to). But nowadays people get lazy and self-entitled thinking they deserve to be able to run modern software on antiques.
  12. zxv

    [pre-release] macOS Mojave

    No. At some point people need to suck it up and upgrade. AMD 7000 series is almost 7 years old.
  13. zxv

    [pre-release] macOS Mojave

    Deleted: /Library/Preferences/SystemConfiguration/Settings.plist /Library/Preferences/SystemConfiguration/preferences.plist Now working normal. @surfinchina this should resolve your issue as well. Edit: Okay. It's stable for ~15mins, then goes haywire again. Strangeness. Edit2: Disabled ASPM in BIOS. Network connectivity stable for over 30mins now. 10.14 might be more aggressive about increasingly annoying power savings "features". Edit3: Ethernet connectivity reverts to throwing a fit & dying when attempting to iTunes sync iPhone over WiFi.
  14. zxv

    [pre-release] macOS Mojave

    Thanks. I'll give it a shot. Not sure what the difference is supposed to be other than its degraded to build on 10.11 SDK bc people are way too into old things here.
  15. zxv

    [pre-release] macOS Mojave

    That's happening to me too… or was. It's ceased now for whatever reason. Also doesn't do it when there's aggressive throughput (multi MB/s). Could be a power management issue? Edit: Never mind, keeps randomly disconnecting again.
  16. zxv

    HWSensors3

    Looking good here. Great work my dude.
  17. zxv

    HWSensors3

    Lol, it happens. Ah, okay. Yes that'd be good. I think default behavior should be IO > SMC… at least for Radeon GPUs, since typically not much info is given by the (very few known) SMC keys. Nvidia may be different, we'll have to see what people post.
  18. zxv

    HWSensors3

    It's probably because I have the HD530 configured in "headless" mode (ig-platform-id 0x19120001) so it can act as a video decoder (which dramatically reduces CPU utilization). I'll try booting through it sometime tonight and seeing what's output. You had it right… AMDCPUMonitor is for AMD CPUs, no? RadeonMonitor for Radeon GPUs—it's what was giving me core temps before. But now it's possible to retrieve that and more without. I'd say for now list them automatically (like everything else already does afaik). Giving users preference is better of course, but it'd be awkward to have one display submodule customizable while others are not. Maybe later that customizability can be expanded upon.
  19. zxv

    HWSensors3

    Ha, still shows without RadeonMonitor. They must be exposed through the Metal framework?
  20. zxv

    HWSensors3

    Just noticed Performance Statistics returns dynamic values for properties like: Fan Speed(RPM) Fan Speed(%) Core Clock(MHz) Device Utilization % GPU Activity(%) … Would be useful to have these integrated into the main HWMonitor display (which currently only shows GPU core temp).
  21. zxv

    HWSensors3

    Very cool. Getting more accurate output now: Thank you.
  22. zxv

    HWSensors3

    Doesn't exist. The IOPCIClassMatch attribute only appears in these items:
  23. zxv

    HWSensors3

    Interesting. I see IOPCIMatch for AMDRadeon, but no IOPCIPrimaryMatch.
  24. zxv

    HWSensors3

    Awesome. Not using FakeID. Lemme know if anything else appears amiss:
×