FOXBI

Members
  • Content Count

    51
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by FOXBI

  1. My guess is that the maximum thread represented in DSM is 8. I have not had a system with more than 8 threads, so I have not checked, can you show me the full results of your system cat /proc/cpuinfo ? I have prepared 8 core and above environment and tested it and it seems to be well expressed. If the "/proc/cpuinfo" value is not displayed incorrectly, the assigned value appears normally. If you above 8 cores and check that the result of ch_cpuinfo matches the value of "/proc/cpuinfo" with the actual CPU or the assigned CPU.
  2. 3) Restore the function to backup and restore files easily. But, In the case of 2) Redo, if it is difficult to restore original by updating in lower version (eg. F.cpu .... -> h.cpu ....), It seems to have made. I do not know if it was the right answer to your question.
  3. Just correct cpu information view It does not affect performance or anything.
  4. My guess is that the maximum thread represented in DSM is 8. I have not had a system with more than 8 threads, so I have not checked, can you show me the full results of your system cat /proc/cpuinfo ?
  5. FOXBI

    1.04b CPU 호환성

    이미 오래전에 하신질문이라 이미 해결 하셨을 수도있지만. 결론부터 말씀드리면 v2인 ivybridge는 안됩니다. 저도 E3-1230 v2 환경에서 갖은 방법을 다 동원해봐도 안되었는데 E3-1220 v3으로 바꾸고 그냥 바로 되더라고요.. haswell 이상이어야 된다고 합니다.
  6. Today Update!! Download Available Right Now !!!
  7. Dear Xpenology forum members, I'm come back!!!! I have been very busy at work. So I could not cope with the changed code because I could not upgrade DSM. But! I have recently successfully migrationed the "ivybridge" of existing my systems to "haswell". I also added an additional LAN card. The latest version of "DSM 6.2.2-24922 Update 2" is now available for the DS3615xs, 918+ and other versions. I'll be updating and distributing the "ch_cpuinfo" tool soon so that it will work with the latest version. I'm sorry to have kept you waiting so long, and thank you for waiting. See you soon. Dear @Polanskiman , Thank you for your patience and care for the topic I could not manage. I'll update soon. Dear @gericb , Thank you for your concern and supportive mentality
  8. It looks like the last time I contacted fhocorp + cpu_vendor=' Intel' + cpu_family=' Xeon' + cpu_series=' E5504' The variable contains a blank line. Last time was Nehalem CPU .. Can you show the result of "dmidecode -t processor"? It seems that certain CPUs may be blank when collecting information.
  9. My testing environment is all VM, and I see that phenomenon for the first time. Is it a phenomenon when it is Native? I can not say that I can do that
  10. Maybe you should comment on the result of `sh -x ch_cpuinfo.sh`
  11. Good job You did well. It is important to change the information and not worry about poor tools. You had a lot of efforts to try various things. Thank you.
  12. Thank you. Your "admin_center.js" file is not problem. I think that one thing that I mentioned before is the cause. It seems that line wrapping is still inserted in the process of collecting information and putting it into a variable. Your GATHER_FN function My GATHER_FN function Please compare. Collected CPU information is entered into the line without entering the variables thoroughly. + cpu_vendor=' Intel' + cpu_family=' Xeon' + cpu_series=' E5440' The variables of the collected information are continuously changed and displayed. + cpu_info='f.cpu_vendor=" Intel";f.cpu_family=" Xeon";f.cpu_series=" E5440";f.cpu_cores="4 Cores (1 CPU\/4 Cores | 4 Threads)";' + sed -i 's/f.model]);/f.model]);f.cpu_vendor=" Intel";f.cpu_family=" Xeon";f.cpu_series=" E5440";f.cpu_cores="4 Cores (1 CPU\/4 Cores | 4 Threads)";/g' /root/Xpenology_backup/admin_center.js sed: -e expression #1, char 37: unterminated `s' command This is correct. + cpu_info='f.cpu_vendor="Intel";f.cpu_family="Xeon";f.cpu_series="E3-1230 V2";f.cpu_cores="8 Cores (1 CPU\/8 Cores | 8 Threads)";' + sed -i 's/f.model]);/f.model]);f.cpu_vendor="Intel";f.cpu_family="Xeon";f.cpu_series="E3-1230 V2";f.cpu_cores="8 Cores (1 CPU\/8 Cores | 8 Threads)";/g' /root/Xpenology_backup/admin_center.js Why the space is in the GATHER_FN function should be checked one line at a time. To find out why. in the GATHER_FN function's should be checked one line, one line...by command. I am sorry that I can not solve it right now.
  13. Thank you for your confirmation. There seems to be more problems than I thought. I think I should open the js file and check it myself. Could you attach a file? I'd like to show you both backed up and original files.
  14. If there was no error when executing a separate command, the code is correct. Does it work as a binary file and the result is the same? One more let me know.
  15. There is no abnormality in particular. But, Is there a way to change the line when pasting it like this? Or does it look like the terminal window has changed lines or lines? admin_center.js file copy to admin_center.js_bak Try typing in the terminal to see if there are any errors # sed -i 's/f.model]);/f.model]);f.cpu_vendor="Intel";f.cpu_family="Xeon";f.cpu_series="E5440";f.cpu_cores="4 Cores (1 CPU\/4 Cores | 4 Threads)";/g' /tmp/admin_center.js_bak If you do not get an error, ch_cpuinfo.sh may have been blanked or wrapped in the process of moving it to your DSM. Please run it and let me know the result.
  16. no, That does not mean that. While upgrading ch_cpuinfo from 1.0 to 5.0. Collection methods, results, etc. have been changed. That's why I've been struggling to minimize problems that could occur when using previous ch_cpuinfo users. The "RERUN_FN" function is the function that contains the process of modifying the modified file again. In this process, all users have the same DSM environment, so there is a possibility of errors. I hope I have answered your question correctly. English is too hard
  17. I have made some parts of the old version of ch_cpuinfo that allow me to cope with the problem and some problems may arise. It is also a good idea to proceed after restoring the original with No. 3 restores. If you want to know more exactly where the error is, go to sh -x ch_cpuinfo.sh and show me the error detected part. Thank you
  18. Sorry. As the number goes up, this situation occurs. DSM 6.x and ch_cpu info 5.2. I will correct it. Thank you!!
  19. Please run it as a new source file. I have solved the related problem.
  20. I have been busy a little while and the update is late. Sorry for not responding to your feedback right away. I uploaded a new version file that source after including the work so that it can run even in DSM 5.x version.. It's possible to use !! Publish the source is not only here, but also through github(https://github.com/FOXBI/ch_cpuinfo). For versions DSM 6.x and later, you can use the binary as before. If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh).
  21. In the 5.x version environment, I checked exactly what the problem was after testing. 5.x version is configured as busybox unlike jun's loader of 6.x. busybox does not have bash defined and should use sh or ash. ## DSM 5.x Syno52> ls -lrt /bin/*sh* lrwxrwxrwx 1 root root 7 Nov 8 17:34 /bin/sh -> busybox lrwxrwxrwx 1 root root 7 Nov 8 17:34 /bin/ash -> busybox ## DSM 6.x root@admin:~# ls -lrt /bin/*sh* | grep bash -rwxr-xr-x 1 root root 1024856 May 19 09:35 /bin/bash lrwxrwxrwx 1 root root 4 Aug 15 18:45 /bin/sh -> bash lrwxrwxrwx 1 root root 4 Aug 15 18:45 /bin/ash -> bash It is judged that it is necessary to modify with boths by "/bin/sh". But, binary execution will fail with an error message with "applet not found" (probably because busybox is lite linux base). So, I am worried. About How to distribute in binary format ... (Actually, when I run by shell script, 5.x version also works normally.) I will think more and make a decision. Thanks nvrsk for your information! I apologize for the inconvenience.
  22. It's not just bash's problem. I’ll create a test environment as soon as possible and make it fixed available. Thank you for your feedback.
  23. I feel gratitude for your understanding and support. I can not do everything here, but I will keep improving as time goes on. Thank you!!!
  24. OMG!!! I did not test it in 5.x, so I did not think bash would be there. I'll prepare 5.x version as soon as possible and fix it. As a temporary measure, please test the execution of ch_cpuinfo after doing the following. ln -s /bin/sh /bin/bash ls -l /bin/bash And, Please inform me of ch_cpuinfo command result. Thank you!!