sszpila

- 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

- 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

- 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

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

-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

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

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

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.

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

Everything work fine.

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

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.

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

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.

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