Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • A Argon One Daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DarkElvenAngel
  • Argon One Daemon
  • Issues
  • #45
Closed
Open
Issue created Sep 25, 2022 by WireRydr@wirerydr

Experimental Support : Fedora-Server 37 (aarch64)

Hello there;

Fedora 37 has recently gone into beta with support for Raspberry PI 4. I have gotten Fedora 37 (Server) installed onto an 8GB rpi4b, and completed a preliminary port of Argon One Daemon. I leveraged learnings from issues #43 (closed) and #9 (closed). Thank you very much for laying down the groundwork for this port in those issues; The porting effort ended up being trivial as a result.

At this point, temp-monitoring and fan-management seems to be working for me. I'm not confident that powerbutton-handling is functioning: I find that a single-press does nothing (including nothing emitted in /var/log/argononed.log), while holding the button down for a few seconds triggers a system-shutdown that I'm not sure is being caused by argononed.

Unlike Fedora IoT, Fedora Server does not use a read-only filesystem, so I didn't bother handling that like in the fedora-iot port.

I initially tested with USE_SYSFS_TEMP=/sys/class/hwmon/hwmon1/temp1_input as within fedora-iot, and then again without. It seems to work without (/dev/gpiochip0 exists). So I've left it in but commented-out as a placeholder.

I'm not a frequent user of GitLab so I haven't set up a repo from which I could send you a pull-request, but the changes are relatively trivial, and shown as follows:

### FILE: OS/fedora-server/OS.conf

STATUS="EXPERIMENTAL"
INITSYS="SYSTEMD"
BOOTLOC="/boot/efi"
I2CHELPER=1
#USE_SYSFS_TEMP=/sys/class/hwmon/hwmon1/temp1_input
### FILE: OS/fedora-server/makefile.in

install:: install-overlay
ifeq ($(I2CHELPER), 1)
        @$(BASH) OS/fedora-server/i2c-helper.sh 2> /dev/null
endif
### FILE: OS/fedora-server/i2c-helper.sh

#!/bin/bash
MODULES="i2c-dev"
MODULE_FILE="/etc/modules-load.d/10-i2c.conf"

if [[ -a $MODULE_FILE ]]; then
    for MODULE in $MODULES
    do
        echo -n "Check for module ${MODULE}  "
        if grep -q $MODULE "${MODULE_FILE}"; then
            echo "FOUND"
        else
            echo "${MODULE}" >> $MODULE_FILE 2>/dev/null && echo "ADDED" || { echo "ERROR:  Can't write to file ${MODULE_FILE}"; exit 1; }
        fi
    done
else
    echo "INFO:  ${MODULE_FILE} Not Found"
    for MODULE in $MODULES
    do
        echo "${MODULE}" >> $MODULE_FILE 2>/dev/null || { echo "ERROR:  Can't write to file ${MODULE_FILE}"; exit 1; }
    done
    echo "INFO:  ${MODULE_FILE} Created Successfully"
fi

exit 0
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking