Jump to content
XPEnology Community

FOXBI

Developer
 View Profile  See their activity

  • Posts

    159

  • Joined

  • Last visited

  • Days Won

    14

 Content Type 

Everything posted by FOXBI

  1. FOXBI
    Please understand that I am not good at English, so I used Google Translate. A request to AMD CPU users. Hello, I am the creator of ch_cpuinfo. Recently, it has been confirmed that the number of cores and threads counts of AMD CPUs are different from those of Intel, and I am not using AMD, so I need information about that. So, we need help from AMD users. Access Xpenology with ssh and type "cat /proc/cpuinfo". I would appreciate it if you could provide a full log. From older models such as Athlon to recent times such as Ryzen, if various information is gathered, it will be better organized. It would be better if you save it as a txt file. Then I will wait.
  2. FOXBI
    Tanks Arithon, The information you showed made me understand what the status was. In the case of Intel, the value of 'siblings' is used to determine the physical core and HT, and it is induced to show the threads value, but in the case of AMD, it is confirmed that this value does not exist. It's like Intel's HT, it's 6 core, but it's supposed to use 12 threads, but it seems to have to be modified so that it can be organized with information from cpuinfo. Thanks for the information. I'll update it soon when it's done.
  3. FOXBI
    thank you for feedback!! If you look at your cpuinfo shown last time, you can see that the total number of processors is 12 Of course, it was made based on Intel's standards, but I think 12 is correct because it is based on the number of processors in your cpuinfo. If you give information on the BIOS or OS about 6core, I will study the AMD counting method again. Below is your cpuinfo file. cat-proc-cpuinfo output.txt *p.s : Oh, and if the serial in the screenshot is genuine, it would be better to cover it.
  4. FOXBI
    I updated new version ch_cpuinfo !!! I hope this version goes well
  5. FOXBI
    good job!! I will update right away
  6. FOXBI
    At first I thought it was happening when using AMD. I found the cause by looking at the execution log you gave me. In a variable called cpu_familry It is designed to contain only one line of CPU name. I don't know why, but the result is entered as two lines. In the past, some people did this manually for this reason. "sort -u" may not be working properly. As-Is + cpu_family='Ryzen 5 2600X Six-Core Ryzen 5 2600X Six-Core ' To-Be + cpu_family='Ryzen 5 2600X Six-Core' There is a need for work to make this happen. I modified the source a bit. Please execute it once again with ch_cpuinfo.sh attached below. The version is v2.4.1-r02. ch_cpuinfo.sh
  7. FOXBI
    OMG!!! It seems to be solved by looking at the status when an error occurs. Would you show me again run to sourcefile "sh -x ch_cpuinfo.sh" full logging. ch_cpuinfo.sh
  8. FOXBI
    I updated new version ch_cpuinfo !!! Unlike Intel, AMD reconfirmed and corrected errors in the process of gathering and sorting information. I don't know the exact result because I don't use AMD, so I think the error was caused by making the source. I'm so sorry for any inconvenience caused to AMD users. I hope this version goes well
  9. FOXBI
    Thanks for the your dsm information. Unlike Intel, AMD reconfirmed and corrected errors in the process of gathering and sorting information. Please re-check the new version v2.4.1-r01.
  10. FOXBI
    Would you show me resualt "sh -x ch_cpuinfo.sh" And, show me "cat /proc/cpuinfo" too.
  11. FOXBI
    It seems to be a problem when getting AMD information. Try again with the new version (v2.3.2-r01)
  12. FOXBI
    It seems to be a problem when getting AMD information. Try again with the new version (v2.3.2-r01)
  13. FOXBI
    It seems to be a problem when sedding admin_center.js. Try again with the new version (v2.3.2-r01)
  14. FOXBI
    It seems to be a problem when getting AMD information. Try again with the new version (v2.3.2-r01)
  15. FOXBI
    It seems to be a problem when getting AMD information. Try again with the new version (v2.3.2-r01)
  16. FOXBI
    I updated new version ch_cpuinfo !!!
  17. FOXBI
    Thank you for the kind explanation of @flyride. I think @flyride's answer is enough to answer the questions of @ed_co and @ssuper2k. ch_cpuinfo has no function other than simply outputting the contents recorded in the current hardware information. It would be good to know with common sense that only /proc/cpuinfo is output, and most models only use up to 8 cores.
  18. FOXBI
    Thank you for showing your information. ch_cpuinfo no longer uses dmidecode. It is confirmed that there are 8 cores activated through your /proc/cpuinfo. The low value(Core Count: 8/Core Enabled: 8/Thread Count: 16) of dmidecode is not the active information, but the information of the CPU(i9-9900K) itself. if your system dedicated, check if the Hyper Threading (HT) value of CMOS is Enabled.
  19. FOXBI
    ch_cpuinfo no longer uses dmidecode. Compare 'cat / proc / cpuinfo' and 'dmidecode -t processor' except grep.
  20. FOXBI
    I am even more impressed that you have commented in Korean. Thank you. 😀
  21. FOXBI
    Cool!!! AMD also works great!
  22. FOXBI
    I'm so sorry.... I didn't know if the keyword to search for was changed in 6.2.3-25423, (Change ".model]);" to ".model])}") but it was checked and fixed while debugging through error reporting. Thanks!! Thanks @TRTL74, @Loweack, @smileyworld for 6.2.3-25423 user who want to refresh Overwrite the two unzipped files admin_center.zip (admin_center.js / admin_center.js.gz) to DSM location /usr/syno/synoman/webman/module/AdminCenter/
  23. FOXBI
    I'm so sorry. It seems that there was an error in modifying the source while changing the collection method. I am currently looking for the cause. I'll edit it and upload it again
  24. FOXBI
    This is the file and folder for backup in the place where ch_cpuinfo was executed. ex) ch_cpuinfo, Xpenology_backup
  25. FOXBI
    Perhaps the information entered through dmidecode is different from the collection method changed this time, so it seems that the reinstallation did not proceed normally. 1. go to synology download center 2. download .pat file 3. decompress .pat file 4. decompress hda.tgz file 5. decompress hda file 6. open folder "usr\syno\synoman\webman\modules\AdminCenter" 7. copy overwrite admin_center.js, admin_center.js.gz files to DSM's sam location. 8. Delete ch_cpuinfo and related files and folders 9. run to ch_cpuinfo 10. select 1) fist run Do it and tell the result
×
×
  • Create New...