FOXBI

Members
  • Content Count

    57
  • Joined

  • Last visited

  • Days Won

    6

FOXBI last won the day on August 8

FOXBI had the most liked content!

Community Reputation

40 Excellent

2 Followers

About FOXBI

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. do use 7zip 1. extract DSMxxx.pat check of hda1.tgz file 2. extract hda1.tgz check of hda1 follder 3. extract hda1 check of hda1~ folder eg.) c:\DSM_DS3615xs_24922\hda1\hda1~\usr\syno\synoman\webman\modules\AdminCenter 4. you can find original admin_center.js & admin_center.hs.gz 5 do use sftp, upload and overwite two files. After checking back your DSM information and then you do run again.
  2. when i made ch_cpuinfo, i think ed about only DSM version upgrade. but, may be don't thinked about hardware change. if you can find path file location "/usr/syno/synoman/webman/modules/AdminCenter/admin_center.js" ""/usr/syno/synoman/webman/modules/AdminCenter/admin_center.js.gz" after extract original file in DSMxxx.pat, copy to overwrite location. or edit by vi tool source. and then you do run again.
  3. two case is dmidecode is wrong. i make ch_cpuinfo refer to 1st dmidecode after 2nd /proc/cpuinfo. i'll modify source change to procedure ch_cpuinfo next version. Thank you!!
  4. Can you show me command result “dmidecode -t process”. I think... may be script running first “dmidecode” after refer “/proc/cpuinfo”.
  5. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 2 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - HP ML310 v2 (1220v3/32GB) VMWare ESXi 6.0 Update3 + RDM/USB Disable/NIC E1000e) - Additional comments: REBOOT REQUIRED - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 2 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - HP ML310 v2 (1220v3/32GB) VMWare ESXi 6.0 Update3 /USB Enable/NIC vmxnet3) - Additional comments: REBOOT REQUIRED
  6. 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.
  7. 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.
  8. Just correct cpu information view It does not affect performance or anything.
  9. 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 ?
  10. FOXBI

    1.04b CPU 호환성

    이미 오래전에 하신질문이라 이미 해결 하셨을 수도있지만. 결론부터 말씀드리면 v2인 ivybridge는 안됩니다. 저도 E3-1230 v2 환경에서 갖은 방법을 다 동원해봐도 안되었는데 E3-1220 v3으로 바꾸고 그냥 바로 되더라고요.. haswell 이상이어야 된다고 합니다.
  11. Today Update!! Download Available Right Now !!!
  12. 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
  13. 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.
  14. 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