Jump to content
XPEnology Community

FOXBI

Developer
 View Profile  See their activity

  • Posts

    158

  • Joined

  • Last visited

  • Days Won

    14

 Content Type 

Everything posted by FOXBI

  1. FOXBI
    Are you using DSM with DS920+ or DS918+? The number of cores available is limited depending on the DSM you use. Please refer to the link below.
  2. FOXBI
    Editing files may not be easy. You need to edit both admin center.js and admin center.js.gz files. Can you give me your cat /proc/cpuinfo so that it can be reflected in the next update?
  3. FOXBI
    Unfortunately, I don't think it's possible in the app. There was already a mention at the time of the initial development of the script, so I looked at it. It is not a form of opening a web page in the app, but it is thought to be a separate hard-coded method or a method of importing information within the app itself. Instead, it is applied to the page that can be viewed by going to the DSM mobile menu in the app.
  4. FOXBI
    It's a matter of parsing the new model. I will take it into account and reflect it in the next update. thank you for the information.
  5. FOXBI
    Unfortunately, the ch_cpuinfo tool is not involved in clock speed. That value is retrieved by other logic in DSM.
  6. FOXBI
    loader has no jobs I'm working on lately. In addition, the task of inserting the device driver is so difficult that I cannot do it. I think it would be good to ask those who are currently active. Sorry for not being able to help. T.T
  7. FOXBI
    New version Updated! Thanks for the @Mentat report
  8. FOXBI
    great. it has been restored to its original Run ch_cpuinfo again. At this time, delete the Xpenology_backup folder in the same path and proceed.
  9. FOXBI
    The new version is well reflected through your cpuinfo. If there is a problem with the previous application, please restore the file below and perform it.(This file is for 7.1.1) Download : admin_center.tar source path - /usr/syno/synoman/webman/modules/AdminCenter After unpacking the tar, overwrite the admin_center.js file and admin_center.js.gz in the original path.
  10. FOXBI
    It seems to be an error caused by running redo while a new function has been added. It seems to have been applied for some reason, but if it is not applied, it is better to recover from the previous version, delete the 'xpenology_backup" folder, and then run it again for the first time. I should have thought about that part, but I'm sorry for the inconvenience. In the next version, I will reflect that part and apply it. or If recovery does not work, refer to the comments below to restore the original file and delete the Xpenology_backup folder before proceeding. If there is a problem with the previous application, please restore the file below and perform it.
  11. FOXBI
    @davido31 Solved and available as v4.2.0-r01. Application of AMD's CPU information collection function improvement
  12. FOXBI
    Thank you In addition, I would like the cat /proc/cpuinfo result as well. The name is too long, so it seems that the parsing is not good.
  13. FOXBI
    Wow CPU names are collected very long!! If the detail link was created normally, it seems to be a success link Please let me know the connection result I put a lot of effort into the AMD result this time
  14. FOXBI
    - Support for changing CPU information in Surveillance Station System information Tested DSM 7.x version & Surveillance Station 6.0.3-4473
  15. FOXBI
    I checked that there is no problem in getting cpu information. Did you proceed with the Internet connection blocked when running ch_cpuinfo? If so, you may not be able to get the cpu information normally. This is because it has been changed to refer to ark.intel.com for complete detail link and generation information. Please check your internet connection and try again.
  16. FOXBI
    There may be something I'm missing. show me the output of your cat /proc/cpuinfo
  17. FOXBI
    Updated with new features added. with AMD users This will be helpful for Intel 12th gen and above users!!
  18. FOXBI
    pup is not a basic command, so you can't do it. However, surprisingly, many shell script regular expressions can be implemented as basic functions. Here's the code for you. https://github.com/FOXBI/xpenlib/blob/main/cpu_info.sh Modified to output the generation in the existing cpu_info library. However, to get the generation value, you must be connected to the Internet. It is made based on DSM's shell, so you may need to add "--no-progress-meter" to the curl option to perform it in TC. It is judged that the desired classification can be made with the generation value extracted from the cpu information. Thanks to this, ch_cpuinfo will be updated soon to reflect the corresponding source. ps : whisper // please send me a note next time at 2cpu
  19. FOXBI
    I think it's probably a DS920+ or DS918+ that only supports up to 8 cores if your DSM is 7.x or higher. as you know ch_cpuinfo simply displays information from /proc/cpuinfo. Currently, it seems that only up to 8 cores are recognized. If you want to show all the cores you have, you will have to build and use it with a DSM that supports 16 cores or more. I think the link below will help. dsm 6.x platform link dsm 7.x platform link
  20. FOXBI
    @gericb model name : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz If you parse your cpu information as it is in the source, you can see that it is working normally. In the case of others in the past, it seems that "Unknown" occurs because two lines are processed when parsing, and eventually the cpu family information (yours is i7-3770) cannot be called. And when reinstalling DSM, it is recommended to proceed with the first run. @vipnetant The ch_cpuinfo tool does not modify /proc/cpuinfo information, but only serves to fetch, parse, and put the information into the view page. When DSM is updated/upgraded, the area is initialized, and it is better to make it new rather than re-run. Also, the DSM version information on the shell reads "/etc.default/VERSION" if there is a "/etc.default" path, and "/etc/VERSION" if there is no path. If the past version is displayed, it may be because some past information remains. In general, if you run ch_cpuinfo as the first run after upgrading DSM, normal output will be displayed.
  21. FOXBI
    In addition, I confirmed that the "DSM 7.1.1-42962 Update 1" version is also normally applied.
  22. FOXBI
    Thanks to you, it has been confirmed once again that the applied code works well as long as the major version of DSM does not change. Thank you for your confirmation.
  23. FOXBI
    Maybe... 24 threads. Please refer to the link below.
  24. FOXBI
    Are you sure you are running it as root? # id Or did you give the file execute permission? # chmod 755 ch_cpuinfo
  25. FOXBI
    ch_cpuinfo does not get the value of the cpu frequency. In DMS for each model, it seems that the cpu name is expressed as a fixed value, but the rest of the values are called flexibly.
×
×
  • Create New...