This is the FFC connector we use: https://www.lcsc.com/product-detail/FFC-FPC-Connectors_JUSHUO-AFC07-S40ECC-00_C11097.html

Pins 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40 are ground Pins 8, 9, 10 are 3.3V Pin 11 is ID_SD Pin 12 is ID_SC Pin 13 is GND on J9 and 3.3V on J10 Pin 14 is GPIO4 on J9 and GPIO6 on J10 Pin 15 is GPIO5 or J9 and GPIO7 on J10 Pins 1-7 on J9 and J10 are all tied together. ID_SD and ID_SC have internal pullups on the CM4. Pins 14 and 15 have 1.8K pullups on the interceptor. Our PoE board uses an AW9523 to add GPIO to control LEDs. We connected it on Pin 11/12 and use pin 13 to set the address pin of the AW9523 so that both AW9523s can be on the same i2c bus. Pins 14/15 should also be suitable for i2c.

You actually can update the bootloader/boot config without the IO board. Refer to /sbin/boot.sh to see how our installer accomplishes this.

That should be the rtl8367 switch, which isn't actually an i2c device. There are no fan speed controllers on the board (which is why the fan connectors are not 4-pin).

Passive PoE is supported and will be detected as class 0, but the PoE voltage is expected to be within 44-57V. I do not think it will work if the voltage is less than 30V.

You can change the resolution, or increase the dpi (scale) in .config/wayfire.ini. For example: ``` [output:HDMI-A-2] scale = 1.5 ``` See https://github.com/WayfireWM/wayfire/wiki/Configuration#output

So there is a linux kernel bug with enabling battery backup for the rv3028 rtc. We workaround this with a script that executes when the installer runs. If you did not have the battery installed or removed it since running the installer, battery backup does not work, and you will see a low voltage warning in dmesg. I've pasted the script below. We should probably also execute this script when using the system settings tool. # check level switching mode local backup=$(i2cget -y 0 0x52 0x37) if (((backup & 0x0c) == 0x0c)); then echo 'Battery backup already enabled.' return 0 fi echo 'Enabling battery backup...' # disable auto refresh local control=$(i2cget -y 0 0x52 0x0f) i2cset -y 0 0x52 0x0f $((control | 0x08)) # enable level switching mode i2cset -y 0 0x52 0x37 $((backup | 0x0c)) # update eeprom i2cset -y 0 0x52 0x27 0x00 i2cset -y 0 0x52 0x27 0x11 sleep 1 # enable auto refresh i2cset -y 0 0x52 0x0f $control

Easiest way to configure wifi: ``` wpa_passphrase <ssid> <passphrase> | sudo tee /etc/wpa_supplicant/wpa_supplicant-wlan0.conf sudo systemctl enable wpa_supplicant@wlan0 ``` It will default to DHCP. To set a static IP, bring up the system settings tool by clicking the clock in the upper right.

@Bill Kreutz If you switched to NetworkManager as you indicate in another thread, you might have to fix your /etc/resolv.conf file.

@Bill Kreutz I just reran these commands and they worked for me, and ethernet continues to work. Your error above indicates you did not create wpa_supplicant-wlan0.conf. Perhaps you forgot the *-wlan0* part of the filename?

Ok, you are asking about the root password. Like most modern Linux distributions, there is no root password set by default, but you can login as admin, and then become root with `sudo su`.

If you haven't forgotten your password, and just want to change it, you only need to type `passwd` from the terminal.

This is what works for me: ``` wpa_passphrase <ssid> <passphrase> | sudo tee /etc/wpa_supplicant/wpa_supplicant-wlan0.conf sudo systemctl enable wpa_supplicant@wlan0 ``` /etc/systemd/network/wlan0.conf is already configured for DHCP. If you don't want to use systemd-networkd, you can disable it: `systemctl disable systemd-networkd`.

The installer prompts you for a password for admin. If you have forgotten the password, select "Bash" from the boot menu. Then you can change the admin password as follows (mmcblk0p2 below assumes you installed to eMMC). ``` mount /dev/mmcblk0p2 /mnt chroot /mnt passwd admin exit umount /mnt exit ```

Network/IP configuration is handled by systemd-networkd. This is different than the official PI OS which uses dhcpcd. The networkd config files are located in /etc/systemd/network

There is a script that configures the VLANs: `/usr/libexec/config-rtl8367rb.sh`. This script gets executed by udev once the driver for the rtl8367 loads. The script uses `swconfig` to set up the VLANs and then creates the virtual VLAN interfaces. See the openwrt docs for `swconfig` if you are not familiar with it. On the rtl8367: * port 0 is the CM4 * ports 1-4 are the 4 ports on the back of the box * ports 6 and 7 are RGMII interfaces that are exposed by the FPC connectors. wpa_supplicant works like it does on any linux distro. You do need to enable it with systemctl. You can use wpa_passphrase to create the contents of wpa_supplicant.conf.

While the FFC connectors are intended for a future networking expansion, it can be used for other things. Each FFC connector includes I2C, 2 GPIO, and power. The I2C can be connected to a chip like AW9523 to create additional GPIOs. One of the connectors exposes GPIO4/5, and the other connector exposes GPIO6/7. Each connector also provides 1.5A @ 3.3V. If there is interest, we will document the pinout.