[DSM 6.2.3-25423 - Recalled on May 13]

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-24922 Update 6

- Loader version and model: Jun's Loader v1.03B 3615XS

- Using custom extra.lzma: No

- Installation type: BAREMETAL - HP Microserver  Gen7 N54L

- Additional comments: Intel nic N360T, USB3 card

[DSM 6.2.2-24922 Update 6 - Re-released March 24]

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.2-24922- update 4

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP Microserver Gen7

- Additional comment: Reboot required | NIC: HP NC-360T

[DSM 6.2.2-24922 Update 2]

- Outcome of the update:  SUCCESSFUL

- DSM version prior update:DSM 6.2.2-24922

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP N54L gen7 + NC360T + USB3 Renesas 720202

- Additional comment: Reboot required

[n40l usb3 pci-e card not functioning in DSM 6.2]

Hi.

I managed to get my uPD720202 work again. I flashed newest firmware (2.0.2.6) for this card and everything works. Firmware downloaded from Station Drivers

 

https://www.station-drivers.com/index.php?option=com_remository&Itemid=353&func=fileinfo&id=1348&lang=en

 

Flasher is for windows only, so I must boot microserver from USB with Windows PE

[DSM 6.2.1-23824 Update 4]

-Outcome of the update: SUCCESSFULL
-DMS version prior update: DSM 6.2.1-23739
-Loader version and model: Jun's loader V1.03b -DS3615xs
- Using custom extra.lzma: NO
- Installation type: BAREMETAL - N54L
- Additional comments:

• NIC : HP NC360T internal nic deactivated
• USB3: uPD720202 not recognize any connected device
• Restart+ Shutdown: OK

[DSM 5.2-5967 Update 6]

updated from 4 to 6 directly from web gui. No problems so far from couple of days. HP N54L

[DSM 5.2-5967 Update 4]

Can you do a reboot after update installation? To confirm that any "bomb" or volume dissappear occurs?

Wysłane z mojego 2014811 przy użyciu Tapatalka

[HP Gen7 n54L - Anyone successful in updating to 5.2?]

Maybe this is a hint? People going from 5.1 5022 or even 5.0 has problems. Maybe upgrade from version 5.1 5055 will be without any problems.

[HP Gen7 n54L - Anyone successful in updating to 5.2?]

And anybody try fresh install with keep files and restore previous configuration from wersion 5.1 ?

[Virtualbox and phpVirtualbox on XPEnology]

Everything work fine.

[cpufreq and powernow-k8 modules]

Tankowiec> cpufreq-info
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
 driver: powernow-k8
 CPUs which run at the same hardware frequency: 0
 CPUs which need to have their frequency coordinated by software: 0
 maximum transition latency: 8.0 us.
 hardware limits: 800 MHz - 2.20 GHz
 available frequency steps: 2.20 GHz, 1.90 GHz, 1.60 GHz, 1.30 GHz, 800 MHz
 available cpufreq governors: conservative, powersave, performance, ondemand, userspace
 current policy: frequency should be within 800 MHz and 2.20 GHz.
                 The governor "conservative" may decide which speed to use
                 within this range.
 current CPU frequency is 800 MHz (asserted by call to hardware).
 cpufreq stats: 2.20 GHz:0.29%, 1.90 GHz:0.59%, 1.60 GHz:1.68%, 1.30 GHz:2.56%, 800 MHz:94.88%  (317669)
analyzing CPU 1:
 driver: powernow-k8
 CPUs which run at the same hardware frequency: 1
 CPUs which need to have their frequency coordinated by software: 1
 maximum transition latency: 8.0 us.
 hardware limits: 800 MHz - 2.20 GHz
 available frequency steps: 2.20 GHz, 1.90 GHz, 1.60 GHz, 1.30 GHz, 800 MHz
 available cpufreq governors: conservative, powersave, performance, ondemand, userspace
 current policy: frequency should be within 800 MHz and 2.20 GHz.
                 The governor "conservative" may decide which speed to use
                 within this range.
 current CPU frequency is 800 MHz (asserted by call to hardware).
 cpufreq stats: 2.20 GHz:0.06%, 1.90 GHz:0.07%, 1.60 GHz:0.08%, 1.30 GHz:0.16%, 800 MHz:99.63%  (13669)
Tankowiec>

 

As you see, my cpus are sitting at lowest frequency for most of time. Even if governors were revert to performance, for max 10 minutes they will back to conservative. I noticed that wake disks from hibernation changes governor to performance.

[cpufreq and powernow-k8 modules]

Sure

#!/bin/sh

for c in $(ls -d /sys/devices/system/cpu/cpu[0-9]*);
do if ! grep -q 'conservative' $c/cpufreq/scaling_governor ;
   then echo conservative >$c/cpufreq/scaling_governor ;
fi
done

 

Script i fired on every ten minutes by cron.

[cpufreq and powernow-k8 modules]

Yes, I made a script to check what governor is set and change it back to conservative. It runs from crontab every ten minute.

 

Tapnięte z lenovo a820

[cpufreq and powernow-k8 modules]

Maybe "conservative" governor is better for nas? In FreeNAS it's default governor. I have switched from ondemand, cpu now sit with lowest frequencies, occasionally switch to higher ones. With ondemand it jumps from min to max frequency, ommiting middle cpu states.

[Trial of Nanoboot (4493) - 5.0.3.1]

Maybe try to compile kernel module from DSM source? Then put it in the /lib/modules and try to insmod it?

I have made powernow-k8 kernel module for N54L in that way

 

Tapnięte z lenovo a820

[Trial of Nanoboot (4493) - 5.0.3.1]

Nanoboot 5.0.4.1 is for DSM 5.0-4528, no more drivers was added.

So far, the DSM 5.1-5021 only test within the team, but will soon be released.

 

Is there a way of getting USB 3.0 working on with new dsm 5.1 ?

 

Really good news. i'll donate for it.

 

But USB3.0 work well on DSM5.0 with NEC uPD720xxx renesas chipset. I have 2 port card on uPD720202 in N54L.