Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/19/2022 in all areas

  1. Anche su AMD tutto nella norma!
    3 points
  2. Hi, could you try this version? Thanks. HackCheck.zip
    3 points
  3. Yes, this version properly works! Thanks!
    2 points
  4. Anche io aggiornato tutto senza problemi ....
    1 point
  5. Attached is an IORE file from the Z690 mobo, when no SSDTs or DevProp were injected. It is from an initial boot when a Vega 56 (in PCIe slot 1; x16) was used before the 6900XT arrived. The Z690 mobos are different in that the 2-3 on-board NVMe slots share lanes with the PCIe slots. If the 1st NVMe slot (closest to the CPU) is populated, then PCIe slot 3 (x16) disappears. There are only 3 PCIe slots, so this approach is annoying. In the attached IORE file, all 3 NVMe slots are populated. There is a Wifi-BT card in PCIe slot 2 (x1). Z690-noSSDT-noDevProp.ioreg.zip
    1 point
  6. 1 point
  7. Release 0.8.0 Added support for early log preservation Switched to Python 3 in scripts (use python /path/to/script to force Python 2) Added ForceAquantiaEthernet for Aquantia AQtion AQC-107s based 10GbE network cards support, thx @Mieze and @Shikumo Updated builtin firmware versions for SMBIOS and the rest Added Misc -> Serial section to customise serial port properties Added CustomPciSerialDevice quirk for XNU to correctly recognise customised external serial devices
    1 point
  8. @iGPUcould you post an IOREG of Z690 system? Thank you
    1 point
  9. I'm using HackCheck v1.0.2 (1/25/21 release). There seems to be a problem with identifying an I225V network connection in Big Sur on a Z690 mobo. This is a Z690 build (not my usual Threadripper), using OC v080. The mobo is an ASUS Z690 ROG Maximus Extreme with an i9 12900KF CPU (I was given a binned chip and could not resist using it on a new build; the multicore speed is ~same as our Threadrippers, but the single core is faster). With the Z690, the Aquantia AQC113C does not work (this port does work in Monterey; it properly has a red X in Big Sur). Meanwhile, the I225V port works in both Big Sur and Monterey (but not in older macOS like Mojave). The attached image is from Big Sur. From the red X, it implies that this port is inactive, but it is working as shown in the SysInfo window at bottom (and the fact that this is post is being made using the port as it is the only access to the internet). The data gathered about the I225V port is correct (device path, ID, etc). The red X for the I225V is present in Monterey as well as Big Sur, even though, again, the port is active. I was wondering if HackCheck needs updating for the newer mobos?
    1 point
  10. Aggiornamento Monterey 12.1 + integrazione Patch Nvidia non più supportata in Monterey
    1 point
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.