ipilcher
commented
4 months ago Not surprised that the RPM doesn't work. I haven't updated it (or the docs) for quite a while. I'll try to provide an overview of what you'll need to do.
First you'll need an updated version of freecusd, directly from the repo.
$ git clone https://github.com/ipilcher/n5550
Cloning into 'n5550'...
remote: Enumerating objects: 828, done.
remote: Counting objects: 100% (239/239), done.
remote: Compressing objects: 100% (150/150), done.
remote: Total 828 (delta 151), reused 170 (delta 88), pack-reused 589
Receiving objects: 100% (828/828), 229.89 KiB | 1.96 MiB/s, done.
Resolving deltas: 100% (561/561), done.
$ cd n5550/freecusd
$ gcc -Os -Wall -Wextra -pthread -o freecusd *.c -lcipThen build the S.M.A.R.T. helper.
$ gcc -Os -Wall -Wextra -pthread -o freecusd-smart-helper smart/helper.c -latasmartInstall the freecusd binary in /usr/local/bin; install freecusd-smart-helper in /usr/local/libexec.
Create /etc/freecusd.conf, based on the freecusd/freecusd.conf template in the repo.
Then you'll need a systemd unit file for the service (in /etc/systemd/system/freecusd.service).
[Unit]
Description=Thecus N5550 NAS monitoring daemon
[Service]
Type=simple
ExecStart=/usr/local/bin/freecusd -s -d
[Install]
WantedBy=multi-user.targetThat gets you the monitoring service, but you'll still need to get the kernel modules built (and rebuilt for every kernel update) and loaded & configured on every boot.
You'll need 2 kernel modules.
n5550_board- Latest source and makefile are at https://github.com/ipilcher/n5550-v2/tree/main/n5550_board.ledtrig-blkdev- Latest source is at https://github.com/ipilcher/ledtrig-blkdev/blob/v6.9%2B/drivers/leds/trigger/ledtrig-blkdev.c. You'll need to select the correct branch for your kernel version; Fedora 39 is currently on kernel 6.8, so you'll want the trigger module from thev6.8+branch. Makefile is at https://github.com/ipilcher/n5550-v2/blob/main/ledtrig-blkdev/Makefile.
Put the ledtrig-blkdev and n5550_board module source files and makefiles in /usr/src/n5550/ledtrig-blkdev and /usr/src/n5550/n5550_board respectively.
I use a dracut module to automatically rebuild the modules every time a new kernel is installed. Create /usr/local/lib/dracut/modules.d/99n5550/module-setup.sh with the following contents.
#!/bin/bash
n5550_do_module() {
local MODULE=$1
[ -e $srcmods/n5550/$MODULE.ko ] && return
pushd $(mktemp --directory)
cp /usr/src/n5550/$MODULE/{$MODULE.c,Makefile} .
make KERNEL=$kernel || return 1
strip --strip-debug $MODULE.ko
mkdir -p $srcmods/n5550
cp $MODULE.ko $srcmods/n5550/
popd
}
check() {
n5550_do_module ledtrig-blkdev || return 1
n5550_do_module n5550_board || return 1
depmod -A $kernel
return 0
}
installkernel() {
hostonly='' instmods n5550_board ledtrig-blkdev
}Create a symbolic link, so that dracut can find the module.
# ln -s /usr/local/lib/dracut/modules.d/99n5550 /usr/lib/dracut/modules.d/99n5550You'll need some udev rules and a helper script to "link" the LEDs to the correct disks and create create stable paths for the hardware sensors (coretemp and it87) and the PCA9532 GPIO chip.
/etc/udev/rules.d/99-n5550.rules:
# Create a stable path (/run/n5550/coretemp) to the coretemp module's monitoring attributes
ACTION=="add", SUBSYSTEM=="hwmon", ATTR{name}=="coretemp", RUN{program}+="/bin/sh -c 'mkdir -p /run/n5550 && ln -s /sys$devpath /run/n5550/coretemp'"
# Do the same for the it87 module (/run/n5550/it87) and also set the system fan speed - rule for newer kernels
ACTION=="add", SUBSYSTEM=="hwmon", ATTR{name}=="it8728", ATTR{pwm3_enable}="1", ATTR{pwm3}="255", RUN{program}+="/bin/sh -c 'mkdir -p /run/n5550 && ln -s /sys$devpath /run/n5550/it87'"
# Older kernels put the it87 module's attributes under the platform device, not the hwmon device
ACTION=="add", SUBSYSTEM=="platform", DRIVER=="it87", ATTR{name}=="it8728", ATTR{pwm3_enable}="1", ATTR{pwm3}="255", RUN{program}+="/bin/sh -c 'mkdir -p /run/n5550 && ln -s /sys$devpath /run/n5550/it87'"
# Link the data disks to the LED triggers (if necessary)
ACTION=="add", SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", DRIVERS=="ahci", DEVPATH=="/devices/pci0000:00/0000:00:1f.2/ata*/host[1-5]/*", RUN{program}+="/usr/libexec/n5550-link-ledtrig $devpath $devnode"
# Stable path for the PCA9532 GPIO "chip"
ACTION=="add", SUBSYSTEM=="gpio", ATTRS{name}=="pca9532", SYMLINK+="gpio-pca9532"/usr/libexec/n5550-link-ledtrig:
#!/bin/sh
DEVPATH=$1
DEVNODE=$2
# Extract the AHCI controller port from the device path
PORT=${DEVPATH#/devices/pci0000:00/0000:00:1f.2/ata*/}
PORT=${PORT%%/*}
PORT=${PORT#host}
# Link the disk to the LED trigger, if present (host0 is the DOM, so subtract 1)
LED=/sys/class/leds/n5550:green:disk-act-$((PORT-1))
[ -e $LED/link_dev_by_path ] && echo $DEVNODE > $LED/link_dev_by_pathMake the helper script executable.
# chmod 0755 /usr/libexec/n5550-link-ledtrigCreate a dracut configuration file to include some additional kernel modules and other files in the initial ramdisk and run the n5550 module that you created above.
/etc/dracut.conf.d/n5550.conf:
install_items+=" /etc/udev/rules.d/99-n5550.rules /usr/libexec/n5550-link-ledtrig "
add_drivers+=" i2c_i801 leds_pca9532 leds_gpio gpio_ich lpc_ich libahci "
add_dracutmodules+=" n5550 "Create a modprobe configuration file.
/etc/modprobe.d/n5550.conf:
options it87 fix_pwm_polarity=1
softdep n5550_board pre: lpc_ich i2c_i801 ledtrig-blkdev n5550_ahci_leds gpio_ich leds_pca9532 leds_gpioCreate a configuration for systemd-modules-load.service.
/etc/modules-load.d/n5550.conf:
it87
n5550_boardYou should now be able to rebuild your initial ramdisk (usually just dracut -f), whith will build the modules for your kernel and include all of the required kernel modules and other files. You can examine the contents of your initial ramdisk with the lsinitrd command. If everything works, it should look something like this.
# lsinitrd | grep n5550
n5550
-rw-r--r-- 1 root root 138 Sep 3 2022 etc/modprobe.d/n5550.conf
-rw-r--r-- 1 root root 17 Sep 3 2022 etc/modules-load.d/n5550.conf
-rw-r--r-- 1 root root 1226 Dec 1 21:36 etc/udev/rules.d/99-n5550.rules
-rwxr-xr-x 1 root root 386 Aug 24 2022 usr/libexec/n5550-link-ledtrig
drwxr-xr-x 2 root root 0 Mar 19 19:00 usr/lib/modules/6.9.0-0.rc5.20240424git9d1ddab261f3.46.fc40.x86_64/n5550
-rw-r--r-- 1 root root 40480 Mar 19 19:00 usr/lib/modules/6.9.0-0.rc5.20240424git9d1ddab261f3.46.fc40.x86_64/n5550/ledtrig-blkdev.ko
-rw-r--r-- 1 root root 31744 Mar 19 19:00 usr/lib/modules/6.9.0-0.rc5.20240424git9d1ddab261f3.46.fc40.x86_64/n5550/n5550_board.ko(The kernel version will be different.)
When you reboot, your green disk activity LEDs should work, and freecusd should be able to start and display the NAS status on the built-in LCD.
That said, I've almost certainly forgotten something. Please give it a shot let me know if you run into any problems.
velocithrills21
So I know that nowhere in the doc is it indicated this is meant to work on Fedora, but I figured I'd give it a shot. I was thrilled to find this and figured it was a longshot it would work, so if it's a relatively easy fix due to a new version of glibc or something (found similar errors posted online where others indicated this might be the case) I'd greatly appreciate any help you're willing to provide.
Thanks in advance
I worked my way through most of the steps in the quickstart guide, successfully compiled and installed libcip-devel version 0.1.1.6, but the n5500-0.6 rpmbuild fails on compilation of freecusd. Specifically it fails with an error when trying to manually fire the compile commands from the spec file:
Running rpmbuild command: