Jump to content
XPEnology Community

medric

Member
  • Posts

    62
  • Joined

  • Last visited

Everything posted by medric

  1. you are correct 3615 stops at 8 and 3617 stops at 16 it looks like 918 stops at 8 so you would have to stick with 3617 if want greater than 8 threads. It looks like I am in the same boat I was hoping that 918 would support 16 since more cpu are getting more and more cores.
  2. My Intel Shows Intel Genuine and not that name and each core shows up independently intel E5-2628 x12 dmidecode -t processor # dmidecode 2.12 # SMBIOS entry point at 0x000f04d0 SMBIOS 2.7 present. Handle 0x0004, DMI type 4, 42 bytes Processor Information Socket Designation: SOCKET 0 Type: Central Processor Family: Xeon Manufacturer: Intel ID: E2 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 62, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Genuine Intel(R) CPU @ 2.30GHz Voltage: 0.0 V External Clock: 100 MHz Max Speed: 4000 MHz Current Speed: 2300 MHz Status: Populated, Enabled Upgrade: Socket LGA2011 L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: 0x0007 Serial Number: Not Specified Asset Tag: 87B21280655F7413 Part Number: Not Specified Core Count: 12 Core Enabled: 12 Thread Count: 24 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Power/Performance Control cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 62 model name : Genuine Intel(R) CPU @ 2.30GHz stepping : 2 microcode : 0x20d cpu MHz : 2301.000 cache size : 30720 KB physical id : 0 siblings : 12 core id : 0 cpu cores : 12 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 4599.80 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 62 model name : Genuine Intel(R) CPU @ 2.30GHz stepping : 2 microcode : 0x20d cpu MHz : 2301.000 cache size : 30720 KB physical id : 0 siblings : 12 core id : 1 cpu cores : 12 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 4599.80 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: -----------| | \ / processor : 11 vendor_id : GenuineIntel cpu family : 6 model : 62 model name : Genuine Intel(R) CPU @ 2.30GHz stepping : 2 microcode : 0x20d cpu MHz : 2301.000 cache size : 30720 KB physical id : 0 siblings : 12 core id : 13 cpu cores : 12 apicid : 26 initial apicid : 26 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms bogomips : 4599.80 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management:
  3. very useful I have amd opteron 6272 that works with DSM 6.2 3615 but not 3617 dont know why i have tried a lot of stuff but cant get it to work, any thoughts Supermicro H8SGL-F c1E disable the reason i wanted 3617 DSM 6.2 is i know it supports 16 cores ( i have tested it the an intel cpu) cat /proc/cpuinfo | grep "cpu cores" | sort -u | awk '{print $NF}'
  4. very useful I have amd opteron 6272 that works with DSM 6.2 3615 but not 3617 dont know why i have tried a lot of stuff but cant get it to work, any thoughts Supermicro H8SGL-F c1E disable the reason i wanted 3617 DSM 6.2 is i know it supports 16 cores ( i have tested it the an intel cpu) cat /proc/cpuinfo | grep "cpu cores" | sort -u | awk '{print $NF}'
  5. Can you do this for the D3617xs as well?
  6. medric

    DSM 6.1.x Loader

    yeah its odd my 9211 card works both windows and xpe the 9240 flash to it mode works windows load in bios drives are found but xpe has issues with it. i will look at it some more later this week
  7. medric

    DSM 6.1.x Loader

    I am not sure what happen to this card it works with windows and bios sees in in both computer however the other card works fine i have two cards one p20 9211 and a p19 9240 flash to it mode which bios sees b ut does not load properly in xpe
  8. +1 That is great news we just have to have some let Jun know the importance of hyper-v drivers.
  9. medric

    DSM 6.1.x Loader

    very odd i will try to flash again that is very very odd so it has to be a bad flash (even though windows sees it fine and drives all work under windows) hmm
  10. medric

    DSM 6.1.x Loader

    my setup is normal is baremetal lsi 9211-it p19 1.02b so i know it works but why is it not working is the real question do i need to downgrade further i added my log where it shows something weird if a dev can step in and have a look .
  11. medric

    DSM 6.1.x Loader

    what version of firmware you're running on your card? that could be the difference i had my on the avago p20 downgrade it to the 19 if i need to go to an older code i can get it and flash it tonight let me know
  12. I have downgrade my lsi 9211-it sas2008 from p20 to p19 and i still does not work using jun 1.02b ds3617 6.1.3 can someone respond? [ 3.119995] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 200 6) [ 3.125607] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 3.142392] Fusion MPT base driver 3.04.20 [ 3.142395] Copyright (c) 1999-2008 LSI Corporation [ 3.152978] Fusion MPT SPI Host driver 3.04.20 [ 3.158430] Fusion MPT SAS Host driver 3.04.20 [ 3.163786] Fusion MPT misc device (ioctl) driver 3.04.20 [ 3.163888] mptctl: Registered with Fusion MPT base driver [ 3.163891] mptctl: /dev/mptctl @ (major,minor=10,220) [ 3.174735] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 3.180708] mpt2sas version 20.00.00.00 loaded [ 3.180846] scsi6 : Fusion MPT SAS Host [ 3.181255] mpt2sas 0000:08:00.0: enabling device (0000 -> 0002) [ 3.181309] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (660 51852 kB) [ 3.181321] mpt2sas0: sending diag reset !! [ 3.332476] mpt2sas0: diag reset: FAILED [ 3.332635] mpt2sas0: _base_get_ioc_facts: failed getting to correct state [ 3.332903] mpt2sas0: mpt2sas_base_unmap_resources [ 3.332941] mpt2sas0: Controller resources are already freed [ 3.332943] mpt2sas0: failure at //source/lsi-mpt2sas/mpt2sas_scsih.c:11743/_ scsih_probe()! [ 3.339862] mpt3sas version 13.00.00.00 loaded
  13. medric

    DSM 6.1.x Loader

    I have downgrade my lsi 9211-it sas2008 from p20 to p19 and i still does not work using jun 1.02b ds3617 6.1.3 can someone respond? [ 3.119995] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 200 6) [ 3.125607] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 3.142392] Fusion MPT base driver 3.04.20 [ 3.142395] Copyright (c) 1999-2008 LSI Corporation [ 3.152978] Fusion MPT SPI Host driver 3.04.20 [ 3.158430] Fusion MPT SAS Host driver 3.04.20 [ 3.163786] Fusion MPT misc device (ioctl) driver 3.04.20 [ 3.163888] mptctl: Registered with Fusion MPT base driver [ 3.163891] mptctl: /dev/mptctl @ (major,minor=10,220) [ 3.174735] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 3.180708] mpt2sas version 20.00.00.00 loaded [ 3.180846] scsi6 : Fusion MPT SAS Host [ 3.181255] mpt2sas 0000:08:00.0: enabling device (0000 -> 0002) [ 3.181309] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (660 51852 kB) [ 3.181321] mpt2sas0: sending diag reset !! [ 3.332476] mpt2sas0: diag reset: FAILED [ 3.332635] mpt2sas0: _base_get_ioc_facts: failed getting to correct state [ 3.332903] mpt2sas0: mpt2sas_base_unmap_resources [ 3.332941] mpt2sas0: Controller resources are already freed [ 3.332943] mpt2sas0: failure at //source/lsi-mpt2sas/mpt2sas_scsih.c:11743/_ scsih_probe()! [ 3.339862] mpt3sas version 13.00.00.00 loaded
  14. i am using ds3617 jun 1.02b works but my sas2008-it does not seem to work i am using the latest firmware is this a firmware issue and if so which version is recommended and if not then what can i do to get this working?
  15. medric

    DSM 6.1.x Loader

    i have tried the ds3617 and that works with efi boot but still my card does not work its sas2008-it mode it is using the latest firmware the avago (sp) could that be the issue? and if so which firmware should i be using. also for the ds3615 i am only showing 2 cpu and for ds3617 i am only showing 4
  16. medric

    DSM 6.1.x Loader

    just installed ds3615 on my machine it worked great the motherboard is a supermicro x9 inte e5-2695 v2 it boots but it does not see my lsi 9211 hba it is not showing up i thought the driver for this was already built into the kernel or do i have to inject it back
  17. Here is the info that i pulled from https://github.com/kref/scripts juns script i can read and understand a bit of it but its a bash script not my strong suite https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/ https://github.com/HuxyUK/xpenology-3.x old but still has good info http://xpenology.com/wiki/en/building_xpenology old style for building the pat file but again has good place to start https://help.ubuntu.com/community/Kernel/Compile standard compile for linux https://github.com/0xAX/linux-insides/blob/master/Misc/how_kernel_compiled.md sandard compile for linux
  18. I have found a lot of info but dont have a lot of coding skills only used in school and that was assembly programming I will post all the info i have found and i think we can work on this together to get this done i know we can we just need to put all the pieces together. later tonight i will link to all my sources
  19. I uses windows 10 bash and download the source and tool chains and used old guides and drivers compiling as reference and compiled my own kernel with better cpu support for my 12 core cpu (E5-2695 v2 sandy bride) and then i took the bzimage and renamed it to zimage and use osfmount to copy over the org zimage but it did not boot (it booted normally with the org zimage file) I could use some pointers on how or what to do next. (please don't mention how powerful that cpu is and what i would use it for)
  20. quote Hide if adding an larger cpu size would break updates and other things I was wondering on a LTS image to get changing CONFIG_NR_CPUS= (>8) greater that 8 so it could work to bypass the limit and most system should not need a lot of updates anyway once in use I am asking cause the virtual option would be a win if you could actually use it without having to skimp on the vm's synology has a rs3617 that has more cpu core so it can handle virtualization properly 8 is kind of tough. Please provide your thoughts and feedback if it really needs to be a one off build if you could pass on some knowledge would be greatly appreciated been learning about compiling and i know i am close but missing a few key information i would like to run baremetal intel xeon x12 ht so i see how to get to menu and i can change from max 8 to 24 but when i am compiling this how do i make this into snynoboot file or could i use juns and edit it with my zimage ?
  21. can someone help with adding hyper-v synthetic drivers
  22. I was able to get 6.0 running in gen 1 hyper-v but it comes up as 100mbps and the image i use did not allow upgrade. What i am going to try is to do the nic SR-IOV and see if that works in gen 2 hyper-v; will net you now
  23. Did you try to convert the VMware image to Hyper-V and give it a try? I have had a ton of different VMware images ive converted and worked fine, always worth a shot in the name of SCIENCE! Not working. The loader needs the Hyper-V integration drivers. Mostly for the network part. Sent from my iPhone using Tapatalk I did get it to work with generation 1 hyper-v and with a tool from http://xpenology.com/forum/viewtopic.php?f=2&t=16114&hilit=DSM_DS3615xs_7393 [spoiler=](it seems the download link is gone but i have them if anyone needs them) DS3615xs_7393.iso i was able to install using the install option iso and then updating use the DS3615xs_7393.pat you have to use the install option for every boot and the nics only the show 100mbps
  24. It seems like they are working on a Hyper-v solution so i will put my money where my mouth is and send that money to the devs for there hard work. I appreciate good work we all do and we should not be afraid to pay it forward to keep good working on going.
×
×
  • Create New...