Jump to content

Napka

Members
  • Content Count

    16
  • Joined

  • Last visited

About Napka

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Napka

    ThunderBolt Drivers

    I’ve tried both miniDP inputs and both TB3 ports.
  2. Napka

    ThunderBolt Drivers

    I can’t make Apple Thunderbolt Display work with GC-Alpine Ridge, ASUS board and Apple TB3->TB2 adapter. I don’t need hotplug, etc. Display doesn’t turn on at all. Any ideas?
  3. No urge at all, but it would be nice to have microcode updates for security reasons.
  4. I’ve missed it too. Is it safe to upgrade bios/firmware with Above 4G Decoding option set to Auto?
  5. @Vladie I had similar problems with latest BIOS v1602. Reverted to 1503 and everything’s good again.
  6. Hi! MacOS: 10.13.6 Clover revision: 4644 Bios 1401 with patches as described in the header message. I was able to install MacOS with unpatched BIOS, but it was slow and glitchy. I'm busy with my project now, had no time to update BIOS, Clover and even MacOS drivers64UEFI contents: ApfsDriverLoader-64.efi, AppleImageCodec-64.efi, AppleKeyAggregator-64.efi, AppleUITheme-64.efi, AptioInputFix-64.efi, AptioMemoryFix-64.efi, DataHubDxe-64.efi, FirmwareVolume-64.efi, FSInject-64.efi, SMCHelper-64.efi, UsbKbDxe-64.efi, VBoxHfs-64.efi. Some of the drivers above are for FileVault2 boot support. I believe your problem is related to AptioMemoryFix-alike driver. Make sure you use the release version of AptioMemoryFix. Clover bundle may contain development version compiled from project git. Remove old memory-related drivers, e.g. OsxAptioFix*, OsxLowMemFixDrv, etc.
  7. My little report. I haven't found a solution yet. When I try to fix USB power during sleep (UsbConnector = 3, kUSB* properties), USB current drops dramatically for this ports. At first, I've thought that's T2 chip controlling USB power. But now it looks like another chip (Apple 338S00268?) is doing power management. With 10.13.6 update there're new properties for ports in IOReg: kUSBBusCurrentAllocation (=0x96) and kUSBBusCurrentSleepAllocation (=0). That matches my port current drops and power off during sleep. Of course, I couldn't inject those properties with SSDT. These values match real iMac Pro IOReg when nothing's plugged in port. If you want to investigate, there should be properties kUSBWakePortCurrentLimit and kUSBSleepPortCurrentLimit. 0x834 should be enough. High values may lead to problems, too. UsbConnector must be set to 0 for USB2 and 3 for USB3 ports. Please note: you'll be unable to use this ports with most USB hardware! So I just set UsbConnector to 255 (or 0xFF, internal port) for all ports except one I'm playing with, and it's HS/USB2 companion. Regarding TUF X299 Mark1 motherboard sensors: After playing with FakeSMC sensors sources and reading the NCT6796D datasheet, some internal motherboard sensors and fan RPM sensor are still mysterious to me. Maybe they are provided by some other chip. The funniest thing is that I can see them working in BIOS, I can see all values in the iOS app, but I can't see some sensors in MacOS, Windows, and even ASUS fan control software. I finished up plugging fans to visible motherboard case fans connectors. I can see water temperature sensor (temp sensor #1 input), air temperature sensor (temp sensor #2 input), pump and fans RPM. BIOS controls fans depending on water/air temperatures, so I'm happy with this for now. As far as I can see it now, my TUF Mark1 motherboard setup works perfectly. It's time to upgrade, add thunderbolt board, etc.
  8. Thanks for the link! No CPU cores mess anymore. But I yet need to jump into sensors source code. Lots of motherboard/external temperature sensors and some fan headers still missing. That was expected, other tools do not display them too.
  9. My ASUS TUF X299 Mark 1 is stable now. Yay! I have to do more testing for sure. I have two problems to solve now: 1. Any USB device can wake up a computer, but nothing charges during sleep. External disks are losing connection and "Disk Not Ejected Properly" is shown on wake up. Including Time Machine disk, unfortunately. It looks like USB current during sleep is too low. I'm trying to find a solution, but out of ideas. The problem's wider than I thought at first. Needs more investigation. 2. Not all temperature, rpm, etc. sensors are available for motherboard configuration in Contents/Info.plist. I'm investigating this right now. Commented this later.
  10. CPU core ratio is set to "Per core", I didn't OC my CPU yet. I have nice temps and CPU is delidded, but I want to make sure everything's perfectly stable first. I'll check AVX offsets now. I've successfully patched 1401, all replaces were successful. I'll try to apply other methods (disable MSR LOCK, TSCAdjustReset.kext, etc.). I'll rename remaining cores now. Every check takes time, my system doesn't panic after a brief sleep.
  11. I'm using your config.plist with Nvidia injection enabled, DSDT patches integrated into it, changed serials, etc. One thing I didn't finish yet is I didn't rename offline CPU devices. My build is in the progress, I didn't get a new CPU/RAM/GPU/M.2 SSD yet, was busy with modding the case and my custom loop. I've patched BIOS. As far as I understand, no need to use TSCAdjustReset.kext in this case? I've double checked all the settings. I didn't OC CPU yet and all offsets are set to Auto. It was painfully slow, but with BIOS patches everything looks almost perfect now except wake problem and some strange CPU Core 11 temperature sensor :D But I didn't edit FakeSMC sensors yet.
  12. Hello. Thank you for such a detailed manual. I made my setup with ASUS TUF X299 Mark 1. I have the following problem. After some hours of sleep, I get kernel panic on wake up. Any ideas?
×