Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


goodwin_c last won the day on September 11 2017

goodwin_c had the most liked content!

1 Follower

About goodwin_c

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender

Recent Profile Visitors

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

  1. Hmm, very interesting. Big tnx for pointing on this! Will try to check on free hours.
  2. Actually, CTRL+ESC is starting Dell Bios Recovery 2. And it is tricky - it is starting only when it can find recovery file. If file is not found - it will just start and shutdown in few seconds, and even without showing anything on screen. To start Bios Recovery properly, do next steps: - Download bios update file from Dell site (it will be .exe file) - Rename this file to BIOS_IMG.rcv (yes, from exe to rcv. file name should have perfect match) - Take some not-too-big USB flash drive, format it in FAT32 fs - Copy BIOS_IMG.rcv to the root of flash drive - Insert flash drive to left USB port on laptop (shouldn't be difference in which port, but from my personal experience left one is better ) - Start laptop with CTRL+ESC. If flash drive has activity led - it should blink at least few times. If machine is not physically damaged - it will run bios recovery with options to reset BIOS settings and re-flash BIOS image
  3. Yes, it is done to be sure that part inside of "if" will be triggered only once (on first call of XOSI function), as XOSI function is used few times in original DSDT.
  4. Try to replace your SSDT-XOSI with next code: DefinitionBlock ("", "SSDT", 2, "hack", "XOSI", 0x00000000) { External (_SB.TBFP, MethodObj) External (USTP, UnknownObj) Name (CNT1, Zero) Method (XOSI, 1, NotSerialized) { CNT1++ IF (CNT1 == 0x1) { \_SB.TBFP (One) USTP = One } Local0 = Package (0x0A) { "Windows", "Windows 2001", "Windows 2001 SP2", "Windows 2006", "Windows 2006 SP1", "Windows 2006.1", "Windows 2009", "Windows 2012", "Windows 2013", "Windows 2015" } Return ((Ones != Match (Local0, MEQ, Arg0, MTR, Zero, Zero))) } } This will: - permanently enable TB controller (USB-C works like a charm ) - should make VoodooI2C attaching to TPD acpi device
  5. Thanks. That is what i was thinking - on my machine it didn't catch TPD1 device. Even, i don't see TPD1 in IOReg. Will try to debug ACPI to find out what is going on.
  6. Could you share your IOReg with VoodooI2C working?
  7. Using Samsung 960 Pro for last few months on High Sierra - no problems so far (sure, i have regular TM with me :-D )
  8. If somebody there has 9550 with 4K matrix (QHD version) and has Windows installed - could you please help me? Here is my ask http://forum.notebookreview.com/threads/dell-xps-15-skylake-9550-owners-lounge.783377/page-391#post-10665553 In short - i did screw up my screen controller firmware and now need working dump from other machine.
  9. goodwin_c


    @vit9696 Btw, with this two efi drivers - NVRAM works as expected, but keyboard in Clover menu is now almost unusable - it works in very weird manner, sometimes it accepts every button press but sometimes only after 3-5 retries. Is there any conflict with default Clover drivers that we should be aware, or this is issue directly related with your driver and we have to debug what's going on? P.S. If you need, you can find my hardware description in my signature on Applelife forum
  10. Talking about NVRAM globally: - don't try to work with NVRAM directly if you are not 150% sure what you are doing - UEFI system are very sensitive to NVRAM content, and you can make hard-break to your board if you will do mistake (i did - and was recovering with hardware flasher over SOIC clip on my bios chip ) - NVRAM contains all permanent-changeable data. It contains internal board settings, UEFI user setting etc., as well as some OS/user settings. All this is separated by GUID. So having GUID + Variable name you can take some value (if such exists in NVRAM) Now - about cleaning. First - don't try to clean whole NVRAM - you will for 100% break hardware. Next - taling about Apple specific data in NVRAM - there are two options. First - you can use "sudo nvram -c" in system. This will wipe all data from NVRAM that are laying under Apple GUID (this is safe, you will not break anything) - this may be sometimes useful when you have issues with system. Also, if your system is not booting - you can use F11 hotkey in Clover - in theory, should do same as "nvram -c", but I had no time and effort to check this in clover sources. Except Apple GUID - macOS can also change some generic variables - like Boot* variables that are responsible for boot options in F12 menu (believe me - you will see this effect - after enabling hardware NVRAM your macOS will care about you and will add extra option "Mac OS X" pointing to default BOOT/bootx64.efi) Outside of scope of Apple GUID and some few generic variable - don't touch anything without good knowledge - it is even more sensitive than glass on corner of table.
  11. Will do later. In airplane atm.
  12. Big news for everybody - we have working NVRAM! Here is link http://www.insanelymac.com/forum/index.php?app=core&module=attach&section=attach&attach_id=280640 In this attachment you may find two .efi drivers - this are updated AptioFix drivers - v1 and v2. Both are fixed for working NVRAM on Skylake+ platforms. Choose which one you prefer more (normally, v2 with calculated slide should be preferable) And say big thanks to vit9696 and Download-Fritz for this fix They deserve it.
  13. Looks like native NVRAM is close There are already first reports that fix is possible and it is working. Thanks to CodeRush, vit9696, Download-Fritz and others - i hope soon we will see fully working universal solution
  14. goodwin_c

    EFI Variable Store on Aptio V (Haswell-E and up)

    Man, I'm not complaining anybody in any way. And my big thanks for all contribution - if you'll check Clover svn log - there are some small patches by me, so i know who is working actively