Skip to content

Borealis installation docs update for OpenSUSE 16.0#575

Merged
tjk584 merged 10 commits into
developfrom
docs/suse16_update
May 27, 2026
Merged

Borealis installation docs update for OpenSUSE 16.0#575
tjk584 merged 10 commits into
developfrom
docs/suse16_update

Conversation

@tjk584

@tjk584 tjk584 commented May 6, 2026

Copy link
Copy Markdown
Contributor

Recently installed Borealis on a pair of OpenSUSE 16.0 machines, this PR reflects changes I needed to make while installing.

tjk584 added 5 commits May 6, 2026 12:01
Added extra zypper packages needed for installing Borealis on OpenSUSE 16.0
Updated NTP and PPS instructions for OpenSUSE 16.0
Updated installation instructions for restart_borealis
Updated expected location for .daemon script
@RemingtonRohel

Copy link
Copy Markdown
Contributor

ReadTheDocs error:

looking for now-outdated files... /home/docs/checkouts/readthedocs.org/user_builds/borealis/checkouts/575/docs/source/starting_the_radar.rst:87: ERROR: Error in "literalinclude" directive:
invalid option value: (option: "language"; value: None)
argument required but none supplied.
..  literalinclude:: ../../scripts/restart_borealis.service
    :linenos:
    :language:
    :caption: restart_borealis.service [docutils]
none found

@RemingtonRohel RemingtonRohel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good other than the RTD build and one question about configuring chrony.

Comment on lines +361 to +377
#. *Optional:* If PPS is not working with chrony, ``chronyc sources`` will look similar to below,
with an "x" next to PPS: ::

MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#x PPS 0 4 7 9 +465ms[ +465ms] +/- 376ns
^- tick.usask.ca 1 10 377 493 +921us[ +929us] +/- 16ms
^* tock.usask.ca 1 10 377 554 -795us[ -788us] +/- 15ms

In this situation, the PPS signal is offset from the expected clock by 465 ms. To account for
this, modify the PPS line in ``/etc/chrony.conf`` as shown below. Adjust the offset to match
what is shown in the ``chronyc sources`` table. ::

refclock PPS /dev/ppsx refid PPS offset 0.465

After restarting chrony, the sample should be in the microsecond range, instead of milliseconds.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this be fixed by restarting the computer instead of setting an offset for chrony?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restarting didn't fix the issue when I was testing. The root cause might be my configuration of the PPS card within the computer, I haven't confirmed this though. This fix is a little jank but it works

Comment thread docs/source/starting_the_radar.rst Outdated
WantedBy=multi-user.target
.. literalinclude:: ../../scripts/restart_borealis.service
:linenos:
:language:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is breaking the ReadTheDocs build

@RemingtonRohel

Copy link
Copy Markdown
Contributor

Path for swappiness value write has changed, file should be made at /etc/sysctl.d/99-swappiness.conf.

@RemingtonRohel

Copy link
Copy Markdown
Contributor

Actually I think I may be wrong, the old path might still be valid. Information online doesn't seem to be specific to openSUSE 16.0, there looks to be multiple places that sysctl looks for configuration values.

@tjk584 tjk584 merged commit 7bf04c9 into develop May 27, 2026
3 checks passed
@tjk584 tjk584 deleted the docs/suse16_update branch May 27, 2026 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants