Search the Community
Showing results for tags 'clearfog'.
Found 4 results
-
I don't use my Clearfog Base as a filer or anything, but I much prefer to have some snappy storage on systems that I access frequently - and since this system is my firewall, I end up working on it often enough. When I'm not at home it's often where I push files - so running off an SD card is right out. For years now I've been using an m.2 SATA drive which has been fine, but it's got a minipcie slot just sitting there that I've never used... it's not particularly fast (PCIe gen 1 x1) but with one of these and an m.2 NVMe drive (the older the better...), you can get much better perf than SATA. You can't boot off it (at least I don't know how to make that happen) but it's easy enough to do that via an SD card or SATA and use one of these for the root filesystem or /home, etc.
-
I installed the latest stable (and updated) debian image on clearfogpro from SD card. I then chose "boot from SD, install on SATA ..." as I have a M.2 SSD card which is viewed as /dev/sda device, with the "armbian-install" utility. However, this one does not offer to boot directly from M2. SSD, which should be possible as there is a DIP switch configuration for it. I tried to burn the iso image on sata with "dd" and then, to "dd" the u-boot.sata on "/dev/sda" (bs=512 seek=1). When switching to sata boot (dip switch), it begins well, the sata device is found, but nothing happens after, the iso image is not loaded. How can I boot directly from M.2 SSD with system installed on it ?
-
Hello All, root:# hwclock --systohc root:# while true; do date; hwclock -r; sleep 60; done observing drift of 1 sec. even tried this https://github.com/armbian/build/pull/2352/commits/59cdf431ef691d67d649adbfaf973f9d451823bc#diff-dc13c5522aed383d1b20662d765c5be9f2635553256069dce64f29be94f89b69 specs: Armada 38x RTC driver ARM_GLOBAL_TIMER Board : Marvell Armada A385 DB AP Kernel : 4.14 community help will be grateful Regards Hardik
-
Not a feature request, I'm just curious about why things are like this. Context around the error message Line 170: tries to enable ACS but CONFIG_ACS disabled 1 errors found in configuration file '/etc/hostapd/hostapd-5.conf' Failed to set up interface with /etc/hostapd/hostapd-5.conf Failed to initialize interface Most relevant part of hostapd-5.conf ... hw_mode=any ... channel=acs_survey ... Probably the root cause of this $ apt source hostapd ... $ grep CONFIG_ACS wpa-2.10/hostapd/defconfig #CONFIG_ACS=y So my question is, why is CONFIG_ACS disabled when having Automatic Channel Selection (ACS) is useful? Thanks, KES
