Hello,
i managed to update both of my NSA-320 to the latest U-Boot(2016.05) and kernel(4.8.3)
For the half bricked one, i succeeded in kwbooting and then installing u-Boot.
The other one i updated by the regular method ( boot a 4.2.x kernel from SATA hdd , and then following the appropriate steps for flashing nand / creating the files in /boot.
But now, as all is up and running, upon installing lm-sensors, i still have no hwmon module, and the sys/class/hwmon/directory ist still empty.
I did this upgrade to the latest Software partly because i thought all these old-days problems would be sorted out by now...
Is there anything else i have to do (apart from insmod nsa3xx_hwmon, maybe)?
Would log Output (like dmesg or fw_printenv) be of any help?
I run a munin node on the NSAs, which would be complete if it gave me fan RPMs and temperature(s).
This is of course not a must, but would be fancy...
i managed to update both of my NSA-320 to the latest U-Boot(2016.05) and kernel(4.8.3)
For the half bricked one, i succeeded in kwbooting and then installing u-Boot.
The other one i updated by the regular method ( boot a 4.2.x kernel from SATA hdd , and then following the appropriate steps for flashing nand / creating the files in /boot.
But now, as all is up and running, upon installing lm-sensors, i still have no hwmon module, and the sys/class/hwmon/directory ist still empty.
I did this upgrade to the latest Software partly because i thought all these old-days problems would be sorted out by now...
Is there anything else i have to do (apart from insmod nsa3xx_hwmon, maybe)?
Would log Output (like dmesg or fw_printenv) be of any help?
I run a munin node on the NSAs, which would be complete if it gave me fan RPMs and temperature(s).
This is of course not a must, but would be fancy...