Jump to content

MSI H55M-ED55 Level 1 Tested


abq-pete

Recommended Posts

Key specs:

H55 and JMB363 chipsets providing 6 SATA ports, 1 eSATA port, 1 IDE port, 2 x8 PCI-e slots, 1 x1 PCIe Slot and a single PCI Slot, onboard video (VGA, HDMI and DVI) via Clarksdale CPUs, onboard speaker, Realtek 8111DL LAN.

 

Test setup:

i3-530 CPU, 4GB G.Skill ECO ram, 2 Supermicro AOC-SASLP-MV8, Corsair HX750, 1 WD20EADS (parity), 2 WD20EARS (with jumpers for data) running unRAID 4.5.6.  Other cards rotated in include Adaptec 1430SA and Syba 2 port PCI-e.

 

I've run parity checks 3 times with no incidents (last syslog attached).  I've transferred about 500GB of data in one session (couple of hours) without any network issues.  I've tried a number of configurations verifying speed and functionality on each of the different ports (onboard SATA, eSATA, AOC-SASLP-MV8, Adaptec 1430SA and a Syba 2 port).  No problems noted in any of the configurations.  The things I did not test were the IDE and PCI slots.

 

Experts, please take a look at the syslog and let me know what you think.  My intention is to replace my main rig's Intel D975XBX2 / Intel E2180 setup with this more energy efficient one.

 

Regards,  Peter

 

2010-08-17 edited to correct CPU info

syslog_MSI_SuperMicroAOCx2.txt

Link to comment

Without resorting to port-multipliers or using the PCI bus it can support 25 drives: 6 SATA MB, 1 eSATA to internal SATA cable, 8 SATA Supermicro AOC-SASLP-MV8, 8 SATA Supermicro AOC-SASLP-MV8, 2 SATA PCI-Express 1x card.

 

One thing to remember that I think WeeboTech or BubbaQ mentioned, the AOC-SASLP-MV8 supports port multipliers and under a brief test didn't seem to impact the overall speed compared to non-port multiplier setup.

 

I too jumped on the bargain to pick up this motherboard. I haven't converted my unRAID server over to it yet, but it's working great so far under Slackware64 Current on a Linux 2.6.35.2 kernel.

 

Here's some info from my running system including cpuinfo, sensors, cpufreq-info and ethtool. I pruned what I copied from cpuinfo and cpufreq-info down to 1 from 4 cores; the other 3 cores are identical.

 

# cat /proc/cpuinfo

processor       : 3
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Core(TM) i3 CPU         530  @ 2.93GHz
stepping        : 2
cpu MHz         : 1200.000
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
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 rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm arat tpr_shadow vnmi flexpriority ept vpid
bogomips        : 5879.97
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

# sensors

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +27.0°C  (high = +89.0°C, crit = +105.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 2:      +27.0°C  (high = +89.0°C, crit = +105.0°C)

f71889fg-isa-0a00
Adapter: ISA adapter
in0:         +1.74 V
in1:         +0.99 V  (max =  +2.04 V)
in2:         +0.76 V
in3:         +0.99 V
in4:         +1.10 V
in5:         +1.11 V
in6:         +1.14 V
in7:         +1.61 V
in8:         +1.66 V
fan1:       1216 RPM
fan2:          0 RPM  ALARM
fan3:          0 RPM  ALARM
temp1:       +29.0°C  (high = +255.0°C, hyst = +251.0°C)  ALARM
                      (crit = +255.0°C, hyst = +251.0°C)  ALARM  sensor = Intel PECI
temp2:       +36.0°C  (high = +255.0°C, hyst = +251.0°C)  ALARM
                      (crit = +255.0°C, hyst = +251.0°C)  ALARM  sensor = thermistor
temp3:       +26.0°C  (high = +255.0°C, hyst = +253.0°C)  ALARM
                      (crit = +255.0°C, hyst = +253.0°C)  ALARM  sensor = transistor

# cpufreq-info

cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 1.20 GHz - 2.93 GHz
  available frequency steps: 2.93 GHz, 2.80 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz
  available cpufreq governors: ondemand, userspace
  current policy: frequency should be within 1.20 GHz and 2.93 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz (asserted by call to hardware).

# ethtool -i eth0

driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info: 0000:03:00.0

# ethtool eth0

Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
        Link detected: yes

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...