Jump to content

syscl

Coders
  • Content Count

    290
  • Joined

  • Last visited

  • Days Won

    9

Reputation Activity

  1. Like
    syscl got a reaction from genzai in Patch for using NVMe under macOS Sierra is ready.   
    For those who have issue on Disk Utility identified issue on some LiteOn, Plextor, Hynix NVMe.
     
    Here's the code we need to change
    test cl, 0x10 jne 0x41d1 search for 
    0xF6 0xC1 0x10 0x0F 0x85 0x1C 0x01 0x00 0x00 change the value 0x10 into 0x01 or 0x02, 0x04 and 0x08 to see which one works for your drive.
     
    For example, here's the patch I found for LiteOn CX2-1024
    Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha Name: IONVMeFamily find: <f6c1100f 851c0100 00> replace: <f6c1010f 851c0100 00> Then enjoy your NVMe

     
    Good luck,
    syscl

    One of my friend has lent her new MacBook9,1 for me, and I soon found some properties rooted in Device (SSD0):
     
    "deep-idle", here's the patch I applied for my XPS 13 9350:
    #Created by syscl for Dell XPS 13 9350 patches #Note: SSD0 must present under RP09 #NVMe _DSM stripped down credit Pike R. Alpha #NVMe "deep-idle" property stripped down credit syscl #NVMe Eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl into device label SSD0 parent_adr 0x001D0000 remove_entry; into device name_adr 0x001D0000 insert begin Device (SSD0)\n {\n Name (_ADR, Zero)\n Name (NVME, One)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n { Return (Buffer (One)\n {\n 0x03\n })\n }\n If (LEqual (NVME, One))\n {\n Return (Package (0x06)\n {\n // "deep-idle" property stripped down credit syscl\n "deep-idle", \n One,\n "use-msi", \n One, \n "nvme-LPSR-during-S3-S4", \n One\n })\n }\n Else\n {\n Return (Package (0x02)\n {\n // refined else-if case credit syscl\n // eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl\n "use-msi", \n One, \n })\n }\n }\n }\n end; #PRT0 information property credit Pike R. Alpha into device label PRT0 remove_entry; into device label SAT0 insert begin Device (PRT0)\n {\n Name (_ADR, 0xFFFF)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n {\n Return (Buffer (One)\n {\n 0x03\n })\n }\n Return (Package (0x02)\n {\n "io-device-location", \n Buffer (0x04)\n {\n "SSD"\n }\n })\n }\n }\n end; Notice, you need to change RP09 to your NVMe location(e.g. RP01, RP02 ...).
     
    We no more need "sats-express-power-off" and "ssd-off-in-S4". And, yes, after injecting deep-idle, we can see this property in ioreg

     
    syscl
     
     
  2. Like
    syscl got a reaction from Deniryer in [GUIDE] Dell XPS 15 (9550) Mojave 10.14 / 10.15 Quick Installation   
    Hi @All,
     
    About data corruption on XPS Skylake series, I want to clarify something we(@darkhandz, @gujiangjiang @shixuev5 @lzt7star ...) discussed here in GitHub[in Chinese].
     
    4 brief conclusions:
    data corruption has nothing to do with HWP(syscl and @darkhandz have experienced data corruption even with GenerateC/PState) data corruption has nothing to do with specific hard disks, because Toshiba XG3, Hynix PC300 have same issue  data corruption seems to be triggered when we put macOS into sleep, but data corruption will not always happen when we put computer to sleep data corruption has nothing to do with system version, both El Captain and Sierra have the data corruption issue @darkhandz has captured some important screenshots after data corruption indicating AppleFSCompression error. But Pike didn't think this log is sufficient to pinpoint the issue. Some suggestion from Pike can be referred here[see posts part]
     
    We need more information, so guys don't hesitate to upload or share your experiences once the data corrupt. Thank you!
     
    syscl
  3. Like
    syscl got a reaction from genzai in Patch for using NVMe under macOS Sierra is ready.   
    For those who have issue on Disk Utility identified issue on some LiteOn, Plextor, Hynix NVMe.
     
    Here's the code we need to change
    test cl, 0x10 jne 0x41d1 search for 
    0xF6 0xC1 0x10 0x0F 0x85 0x1C 0x01 0x00 0x00 change the value 0x10 into 0x01 or 0x02, 0x04 and 0x08 to see which one works for your drive.
     
    For example, here's the patch I found for LiteOn CX2-1024
    Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha Name: IONVMeFamily find: <f6c1100f 851c0100 00> replace: <f6c1010f 851c0100 00> Then enjoy your NVMe

     
    Good luck,
    syscl

    One of my friend has lent her new MacBook9,1 for me, and I soon found some properties rooted in Device (SSD0):
     
    "deep-idle", here's the patch I applied for my XPS 13 9350:
    #Created by syscl for Dell XPS 13 9350 patches #Note: SSD0 must present under RP09 #NVMe _DSM stripped down credit Pike R. Alpha #NVMe "deep-idle" property stripped down credit syscl #NVMe Eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl into device label SSD0 parent_adr 0x001D0000 remove_entry; into device name_adr 0x001D0000 insert begin Device (SSD0)\n {\n Name (_ADR, Zero)\n Name (NVME, One)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n { Return (Buffer (One)\n {\n 0x03\n })\n }\n If (LEqual (NVME, One))\n {\n Return (Package (0x06)\n {\n // "deep-idle" property stripped down credit syscl\n "deep-idle", \n One,\n "use-msi", \n One, \n "nvme-LPSR-during-S3-S4", \n One\n })\n }\n Else\n {\n Return (Package (0x02)\n {\n // refined else-if case credit syscl\n // eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl\n "use-msi", \n One, \n })\n }\n }\n }\n end; #PRT0 information property credit Pike R. Alpha into device label PRT0 remove_entry; into device label SAT0 insert begin Device (PRT0)\n {\n Name (_ADR, 0xFFFF)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n {\n Return (Buffer (One)\n {\n 0x03\n })\n }\n Return (Package (0x02)\n {\n "io-device-location", \n Buffer (0x04)\n {\n "SSD"\n }\n })\n }\n }\n end; Notice, you need to change RP09 to your NVMe location(e.g. RP01, RP02 ...).
     
    We no more need "sats-express-power-off" and "ssd-off-in-S4". And, yes, after injecting deep-idle, we can see this property in ioreg

     
    syscl
     
     
  4. Like
    syscl got a reaction from genzai in Patch for using NVMe under macOS Sierra is ready.   
    For those who have issue on Disk Utility identified issue on some LiteOn, Plextor, Hynix NVMe.
     
    Here's the code we need to change
    test cl, 0x10 jne 0x41d1 search for 
    0xF6 0xC1 0x10 0x0F 0x85 0x1C 0x01 0x00 0x00 change the value 0x10 into 0x01 or 0x02, 0x04 and 0x08 to see which one works for your drive.
     
    For example, here's the patch I found for LiteOn CX2-1024
    Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha Name: IONVMeFamily find: <f6c1100f 851c0100 00> replace: <f6c1010f 851c0100 00> Then enjoy your NVMe

     
    Good luck,
    syscl

    One of my friend has lent her new MacBook9,1 for me, and I soon found some properties rooted in Device (SSD0):
     
    "deep-idle", here's the patch I applied for my XPS 13 9350:
    #Created by syscl for Dell XPS 13 9350 patches #Note: SSD0 must present under RP09 #NVMe _DSM stripped down credit Pike R. Alpha #NVMe "deep-idle" property stripped down credit syscl #NVMe Eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl into device label SSD0 parent_adr 0x001D0000 remove_entry; into device name_adr 0x001D0000 insert begin Device (SSD0)\n {\n Name (_ADR, Zero)\n Name (NVME, One)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n { Return (Buffer (One)\n {\n 0x03\n })\n }\n If (LEqual (NVME, One))\n {\n Return (Package (0x06)\n {\n // "deep-idle" property stripped down credit syscl\n "deep-idle", \n One,\n "use-msi", \n One, \n "nvme-LPSR-during-S3-S4", \n One\n })\n }\n Else\n {\n Return (Package (0x02)\n {\n // refined else-if case credit syscl\n // eliminate "sata-express-power-off" and "ssd-off-in-S4" credit syscl\n "use-msi", \n One, \n })\n }\n }\n }\n end; #PRT0 information property credit Pike R. Alpha into device label PRT0 remove_entry; into device label SAT0 insert begin Device (PRT0)\n {\n Name (_ADR, 0xFFFF)\n Method (_DSM, 4, NotSerialized)\n {\n If (LEqual (Arg2, Zero))\n {\n Return (Buffer (One)\n {\n 0x03\n })\n }\n Return (Package (0x02)\n {\n "io-device-location", \n Buffer (0x04)\n {\n "SSD"\n }\n })\n }\n }\n end; Notice, you need to change RP09 to your NVMe location(e.g. RP01, RP02 ...).
     
    We no more need "sats-express-power-off" and "ssd-off-in-S4". And, yes, after injecting deep-idle, we can see this property in ioreg

     
    syscl
     
     
  5. Like
    syscl reacted to Sherlocks in Clover Problems and Solutions   
    No. Its not bug. Only has same name on Imac17,1 model in smbios dump 
    나의 LG-F410S 의 Tapatalk에서 보냄
  6. Like
    syscl got a reaction from Sherlocks in Clover Problems and Solutions   
    Thank you for your handwork, will try this day! Wish I'll recover from illness soon  
     
    syscl
  7. Like
    syscl reacted to Sherlocks in Clover Problems and Solutions   
    here is report.
     
    your script seems to have unmount issue or other.
     
     
    FrodoKenny script is best now for me. but i'm not legacy user. maybe need to add some code for legacy users.
     
    thank you.
     
    add. i made script file from FrodoKenny's patch file, attached FrodoKenny script file. maybe it will be help.
     
    FrodoKenny script log
    80.save_nvram_plist.local.zip
  8. Like
    syscl reacted to tluck in Clover Problems and Solutions   
    NVRAM file followers - i have made some revisions to syscl's 1.5 script and it works quite well now.
     
    added some addition logic and conditions
    checks for Legacy Clover or EmuVariable present to decide whether to write the nvram to ESP that has a CLOVER folder in it.
    so looks at all disks and checks if ESP mounted - if so, use it
    or mount ESP on new mount point
    write NVRAM only if different from existing file
    unmount (without a force) ESP
     
    Note:
    it seems best to disable indexing and spotlight for ESP
    i mounted all my ESP and ran this:
    mdutil -d /Volumes/ESP*
     
    here is v1.6 script sample output:
     
    3 disks - 2 have Clover - mounted one ESP
    so i change brightness
    run
    run again
    $ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local; cat /Library/Logs/CloverEFI/rc.shutdown.log v1.6 (c) 2017 syscl/lighting/Yating Zhou Found ESP on disk0s1 and found Clover in /Volumes/ESP-01/EFI/CLOVER Found ESP on disk1s1 and found Clover in /Volumes/ESP-1/EFI/CLOVER Found ESP on disk2s1 Target path: /Volumes/ESP-01 saved new values to NVRAM Target path: /Volumes/ESP-1 saved new values to NVRAM $ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local; cat /Library/Logs/CloverEFI/rc.shutdown.log v1.6 (c) 2017 syscl/lighting/Yating Zhou Found ESP on disk0s1 and found Clover in /Volumes/ESP-01/EFI/CLOVER Found ESP on disk1s1 and found Clover in /Volumes/ESP-11/EFI/CLOVER Found ESP on disk2s1 Target path: /Volumes/ESP-01 no change in NVRAM Target path: /Volumes/ESP-11 no change in NVRAM v1.6-80.save_nvram_plist.local.zip
  9. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
  10. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
  11. Like
    syscl got a reaction from gujiangjiang in Clover Problems and Solutions   
    Thanks, and thank you @Sherlock who provided some more detail information such that I can refine the script to v1.5+. Maybe the new script will release this week. Improvements will be:
    Safe mode(-x) dump NVRAM to EFI/ Installation mode dump NVRAM to EFI/ Use just logoutHook method Use unmount with argument -f to force release EFI/ just in case ...  
    syscl
  12. Like
    syscl got a reaction from gujiangjiang in Clover Problems and Solutions   
    Thanks, and thank you @Sherlock who provided some more detail information such that I can refine the script to v1.5+. Maybe the new script will release this week. Improvements will be:
    Safe mode(-x) dump NVRAM to EFI/ Installation mode dump NVRAM to EFI/ Use just logoutHook method Use unmount with argument -f to force release EFI/ just in case ...  
    syscl
  13. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
  14. Like
    syscl got a reaction from MaLd0n in Get system log from 10.12+ much much easier(by just a simply click)   
    @smolderas @BreBo, thanks for your tips, I've added the suggestion, please try v1.2 in my GitHub.
     
    Wish you all enjoy!
     
    syscl
  15. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
  16. Like
    syscl got a reaction from Deniryer in Get system log from 10.12+ much much easier(by just a simply click)   
    I reboot macOS frequently, I need to see if one of my patch work or not instantly.
     
    I don't think the new logging system is good for debugging. If people want to log that way, that's OK. But, Apple should not hide the system.log for users in old school. About how to log, it's up to users.
     
    By hiding the system.log, we will get bug free macOS now. Clever move Apple. Now no one can blame them(Apple) for error messages. Can you imagine if they removed the fuel indicator on a car because you complained weren't getting enough MPG as reported? Same on 10.12.2, Apple removed time remaining estimate for laptop users.
     
    syscl
  17. Like
    syscl got a reaction from MaLd0n in Get system log from 10.12+ much much easier(by just a simply click)   
    @smolderas @BreBo, thanks for your tips, I've added the suggestion, please try v1.2 in my GitHub.
     
    Wish you all enjoy!
     
    syscl
  18. Like
    syscl got a reaction from MaLd0n in Get system log from 10.12+ much much easier(by just a simply click)   
    @smolderas @BreBo, thanks for your tips, I've added the suggestion, please try v1.2 in my GitHub.
     
    Wish you all enjoy!
     
    syscl
  19. Like
    syscl reacted to smolderas in Get system log from 10.12+ much much easier(by just a simply click)   
    Last edit with the addition of BreBo:
    log show --predicate 'process == "kernel" OR eventMessage CONTAINS "kernel"' --style syslog --source --info --start $(date "+%Y-%m-%d")
  20. Like
    syscl reacted to BreBo in Get system log from 10.12+ much much easier(by just a simply click)   
    How about only loading the entries of today?
    log show --predicate "processID == 0" --start 2017-01-08 --debug
  21. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
  22. Like
    syscl reacted to webhappyboy070 in Clover Problems and Solutions   
    I can confirm @syscl's script work prefectly
    Last login: Sun Jan 8 10:26:33 on ttys000 DremaboatdeMac-Pro:~ zhanghongmin$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log Password: v1.4 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Found EFI disk1s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram Target path: /Volumes/EFI11>> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local n DremaboatdeMac-Pro:~ zhanghongmin$
     
    I propose Clover could merge syscl's 1.4. It's great!
  23. Like
    syscl reacted to Sherlocks in Clover Problems and Solutions   
    Me too. Laptop need brightness value refesh if we change brighness before reboot. 
    Syscl script shown best result now. I tested it during 2 days
    Stable and generated nvram in ESP.
     
    나의 LG-F410S 의 Tapatalk에서 보냄
  24. Like
    syscl reacted to cjfly in Clover Problems and Solutions   
    hi syscl  , 1.4 works like a charm, and if I do not change brightness, the /Volumes/EFI/nvram.plist will not be updated, nice!
     
    Seems like it's almost the final version?
     
    Cheers
    v1.4 (c) 2017 syscl/lighting/Yating Zhou Found EFI disk0s1 Target path: /Volumes/EFI01 EmuVariable is present dump nvram
  25. Like
    syscl got a reaction from webhappyboy070 in Get system log from 10.12+ much much easier(by just a simply click)   
    Well, as of 10.12, Apple removed /var/log/system.log, which made developers' life much more inconvenient. Especially for further debugging. Though we can use log command to print out all the log from system, but hey, why should we use such a ridiculous way every time to see log?? That's why I started this project maclog for Sierra to make our life much easier. 
     
    How to use?
    Download executable program from my GitHub: https://github.com/syscl/maclog Double left click to execute maclog(P.S. for first time use: right click -> open) That's it. No more command you need to type in.
     
    If you enjoy this project don't hesitate to star it
    If you have good idea please don't hesitate to let me know
     
    Wish you all enjoy
     
    Best wishes,
    syscl
     
×