Yesterday evening I decided to wipe out NetBSD-Current/earmv6hf from my SD card and try Void (void-rpi2-musl-PLATFORMFS-20171007.tar.xz ) on RPi3 Model B. Here I’m providing a couple of observations and tips, hoping new users will eventually find them useful.
Overall feedback: very good; stable; practically nonexistent boot time, even shorter than RC/BSD-Init, which had proven the fastest so far; unparalleled performance: handles 2 Qupzilla instances quite well; xbps, well it’s xbps, fast as always; wireless drivers/firmware up to date and working flawlessly on a WPA2-Personal connection using wpa_supplicant.
My filesystem (32Gb SD)
- 512MB FAT16 /boot partition
- 29 GB F2FS root partition
- 1 GB swap
# <file system> <dir> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid,nodev 0 0 /dev/mmcblk0p1 /boot vfat defaults,noatime 0 2 /dev/mmcblk0p2 / f2fs defaults,noatime,acl,active_logs=6,user_xattr 0 1 /dev/mmcblk0p3 none swap sw 0 0
Once set a wireless connection up and running, I encountered the same problem described in thread: [SOLVED] Xbps cant install packages (certificate verificacion failed). In fact, since most ARM SoCs have no hardware clock and I hadn’t enabled ntpd -like the fool I am-, date had remained set to to 1st Jan 1970 .
I configured nptd to synchronize time with ntp-pool Italian servers, adding to
server 0.it.pool.ntp.org iburst server 1.it.pool.ntp.org iburst server 2.it.pool.ntp.org iburst server 3.it.pool.ntp.org iburst
However, after reboot, I noticed date had not been reset, despite chrony daemon was running, so I went looking up
/etc/sv/ntpd/run and found:
#!/bin/sh exec chronyd -n -u chrony
the problem was that since
chrony user didn’t exist, process was failing to be assigned to any UID after boot; hence I simply changed that user name to match mine, and got date/time correctly synchronized no sooner had I restarted the ntpd service.
I was curious to see which extent the latest armv7 Linux kernel (and Void?) would bear overclocking the Rpi3 to (owning a couple of aluminium heat sinks and a mini fan). And that’s more or less the highest stable and not overheating configuration I was able to set (inside
gpu_freq=600 gpu_mem=512 arm_freq=1400 core_freq=600 sdram_freq=600 over_voltage=8 sdram_schmoo=0x02000020
In addition, since I’m using my Rpi3 with an old 1024x768 VGA monitor, I had tweak /boot/config.txt in order to force output to be displayed correctly through a HDMI2VGA converter:
hdmi_ignore_edid=0xa5000080 hdmi_force_hotplug=1 hdmi_drive=2 config_hdmi_boost=7 hdmi_group=2 hdmi_mode=16 framebuffer_depth=16 framebuffer_width=1024 framebuffer_height=768 disable_overscan=1
Which is more or less the same configuration I used on NetBSD, with a couple of additions due to wrong display y axis alignment
Maybe other Void/Pi3 users will like to share their experience, point out any correction and provide further useful suggestions