Apu2 led control?

doktornotor

That's a BIOS bug. Try with 4.0.7 (or the experimental 4.5.5).

P.S. Trim in enabled by default on ZFS, so not really sure whether the messing is worth the time.

xbipin

im on the 4.0.7 already and its happening there only.

well during install i selected UFS so is it recommended to use UFS or ZFS, i read that UFS has a bunch of issues. Im currently using RAM disk for /var and /tmp on UFS currently

doktornotor

Definitely ZFS for me. Way too many boxes already bricked with UFS filesystem corruption that's unfixable with the broken fsck tool.

P.S. For sure cannot confirm that the console corruption is 4.0.7-only issue. Reported pretty much since the very beginning on PC Engines forums with various coreboot versions.

xbipin

but does zfs need 2 storage devices, i just have the msata inside it and no plans to add a second

Jailer

Nope.

xbipin

Well I don't run any package other than cron and I have the var and tmp in ram disk so what difference does it anyways make using ufs or zfs coz on power failure it isn't going to corrupt anyways right?

For ppl using squid etc they would definitely benefit coz I had just one instance of a full install corrupting due to power failure

doktornotor

@xbipin:

Well I don't run any package other than cron and I have the var and tmp in ram disk so what difference does it anyways make using ufs or zfs coz on power failure it isn't going to corrupt anyways right?

Actually, yes, it is going to corrupt. Most often corruption happens with /etc. UFS == junk.

xbipin

ok i formatted to ZFS now, i have the /tmp and /var in RAM disk, how do i check TRIM status? (/tmp /var shows using UFS when in RAM disk, and isnt SWAP supposed to be disabled, is this fine?)

steve_v

2.4 running pretty smoothly on my APU2C4, with some (presumably benign) complaints from the bootloader:

gptzfsboot: error 12 lba 32
gptzfsboot: error 12 lba 7710712
gptzfsboot: error 12 lba 1

ZFS working nicely (bonus, a use for the 4GB of ECC RAM on this board), hopefully no more hosed filesystems…

To return to the OT, the led driver mentioned above works just fine in 2.4, as does gwled. Here's a precompiled .ko for the lazy.

However...

The current blinkled binary segfaults, at least for me. Anyone else getting this?

apuled.ko.gz

xbipin

thanks for the info, could u kindly mention how to install this ko file or how to compile the one mentioned on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189772 as it seems perfect for the job?

steve_v

@xbipin:

thanks for the info, could u kindly mention how to install this ko file or how to compile the one mentioned on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189772 as it seems perfect for the job?

Download the attached apuled.ko.gz (compiled for FreeBSD 11) and put it somewhere on your pfsense box (e.g. /root/), then:
Decompress```
gunzip apuled.ko.gz

Load```
kldload /root/apuled.ko

You can then set the kldload command to run at startup.

There's probably a better way to include it in pfsense, but this lazy method works just fine. ;)

To compile it yourself:
Install FreeBSD (10 for pfsense 2.3.x, 11 for 2.4) in a VM.
Install the matching kernel sources.
Download and unpack apuled.tgz from the bug report (and optionally the updated apuled.c for APU3 support).
Run 'make' in the directory containing apuled.c and Makefile.
Rename produced 'apuled.o' to 'apuled.ko'.
Copy to pfsense and load as above.

xbipin

for testing i copied the ko file to /boot/modules and then load it using loader.conf and it works fine.

i noticed the /dev/led folder has igb0-1, are those to disable the nic leds or something else?

steve_v

@xbipin:

are those to disable the nic leds

Control of NIC LEDs, yes. Handy as all-get-out for identifying ports.

Veldkornet

I installed the driver, and that seems to be okay.

However I can’t get gwled or blinkled to start… is it just me?