Linux Setup Notes: July 2025

yay -S ttf-ms-fonts ttf-selawik

To achieve Microsoft-level font clarity on Arch Linux after installing Microsoft fonts, you'll need to configure several rendering components:

Font Rendering Configuration

Install necessary packages:

yay -S freetype2 fontconfig cairo ttf-selawik

Enable subpixel rendering (equivalent to ClearType): Edit /etc/fonts/local.conf or ~/.config/fontconfig/fonts.conf:

<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <match target="font">
    <edit name="lcdfilter" mode="assign">
      <const>lcddefault</const>
    </edit>
    <edit name="rgba" mode="assign">
      <const>rgb</const>
    </edit>
    <edit name="hinting" mode="assign">
      <bool>true</bool>
    </edit>
    <edit name="hintstyle" mode="assign">
      <const>hintslight</const>
    </edit>
    <edit name="antialias" mode="assign">
      <bool>true</bool>
    </edit>
  </match>
</fontconfig>

Enable subpixel rendering in freetype2: Uncomment or add to /etc/profile.d/freetype2.sh:

export FREETYPE_PROPERTIES="truetype:interpreter-version=40"

Set font priorities: Configure fontconfig to prefer Microsoft fonts by adding font substitution rules in your fontconfig file:

<alias>
  <family>sans-serif</family>
  <prefer>
    <family>Segoe UI</family>
    <family>Arial</family>
  </prefer>
</alias>

Desktop Environment settings:

Enable subpixel rendering in Tweaks and set font to Selawik semibold and Selawik (for docs)
Configure font smoothing/antialiasing in your desktop environment settings
Set appropriate DPI scaling if needed

Rebuild font cache:

fc-cache -fv

The key is that Linux's freetype2 + fontconfig combination can achieve similar quality to Windows' font rendering, but requires manual configuration to match Microsoft's defaults.

By default, the ethtool setting for Wake-on-LAN does not persist across reboots on most Linux systems. To make Wake-on: g permanent for your network interface (enp69s0), you have several reliable options:

1.

Create a custom systemd service that sets WOL after the network interface is up:

Create the service file /etc/systemd/system/wol@.service with the following content:


text
[Unit]
Description=Enable Wake-on-LAN for %i
Requires=network.target
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/ethtool -s %i wol g

[Install]
WantedBy=multi-user.target

Enable the service for your interface:
```
text
sudo systemctl enable wol@enp69s0.service
```
This ensures the command runs at every boot, after the network is initialized1 23.

2.

Alternatively, you can use a udev rule to apply the setting whenever the interface appears:

Create the file /etc/udev/rules.d/81-wol.rules with:
```
text
ACTION=="add", SUBSYSTEM=="net", NAME=="enp69s0", RUN+="/usr/bin/ethtool -s enp69s0 wol g"
```
This ensures the setting is applied every time the device is added (e.g., at boot or after suspend)45.

3.

If you manage your network with NetworkManager, you can set WOL via:


text
nmcli connection modify <connection-name> 802-3-ethernet.wake-on-lan magic

Replace <connection-name> with the actual connection name for enp69s0. This will set the WOL option at the NetworkManager level4.

When connecting two Linux devices directly via Ethernet (without a switch/router), common issues include:

: By default, neither side provides DHCP, so both devices may not get an IP address, resulting in connection errors.
NetworkManager Misconfiguration: If the connection profile is not set to "shared" or "link-local", automatic IP assignment may fail.
: Windows uses APIPA to assign addresses automatically, but Linux requires explicit configuration.

Option 1: Use NetworkManager's "Shared" Method

On your Arch system, run:


text
nmcli con add type ethernet ifname enp69s0 con-name direct-pi ipv4.method shared
nmcli con up direct-pi

This will assign a local IP and enable basic network sharing67.

: Manual Static IPs

Assign static IPs on both devices. For example:
- On Arch: sudo ip addr add 10.0.0.1/24 dev enp69s0
- On Raspberry Pi: sudo ip addr add 10.0.0.2/24 dev eth0
Now you should be able to ping each device from the other8.

Ensure the Ethernet cable is good and supports direct connections (modern devices usually auto-negotiate, but older ones may need a crossover cable).
Disable or configure firewalls if needed for testing.
If using Avahi/mDNS for .local hostnames, ensure nss-mdns is installed and configured on both systems6.

Task	Recommended Solution
Persist WOL setting	systemd service (`wol@enp69s0.service`) or udev rule
Fix direct LAN "connection errors"	Use NetworkManager's "shared" method or assign static IPs on both devices

By following these steps, you can make Wake-on-LAN persistent and resolve direct LAN connection errors between your Arch Linux system and Raspberry Pi.

Linux Setup Notes

Friday, July 25, 2025

Microsoft fonts on Arch

Font Rendering Configuration

Monday, July 14, 2025

Raspberry Pi WOL via cable

1.

2.

3.

Saturday, July 5, 2025

Using rclone to integrate Google Drive in Arch

KDE's Own Distro

Report Abuse

Friday, July 25, 2025

Microsoft fonts on Arch

Font Rendering Configuration

Monday, July 14, 2025

Raspberry Pi WOL via cable

Making Wake-on-LAN (WOL) Persistent on Arch Linux

1. Using a systemd Service

2. Using a udev Rule

3. NetworkManager (Optional)

Diagnosing "Connection Errors" with Direct LAN to Raspberry Pi

Solution: Set Up IP Addressing

Additional Tips

Summary Table

Saturday, July 5, 2025

Using rclone to integrate Google Drive in Arch

KDE's Own Distro

1.

2.

3.