From 77ae39920b2af0a7f63c3d1ebd6eff732e4b6034 Mon Sep 17 00:00:00 2001 From: x1y <23239177+x1y@users.noreply.github.com> Date: Thu, 10 Oct 2024 20:36:49 +0200 Subject: [PATCH] Correction of admonitions for adoc --- .../General/Mainline_Hardware_Decoding.adoc | 4 +-- .../documentation/General/Overclocking.adoc | 28 +++++++++---------- .../Software/Software_state.adoc | 4 +-- .../PineTab2/Getting_started.adoc | 4 +-- .../SOPINE/Software/Releases.adoc | 4 +-- 5 files changed, 22 insertions(+), 22 deletions(-) diff --git a/content/documentation/General/Mainline_Hardware_Decoding.adoc b/content/documentation/General/Mainline_Hardware_Decoding.adoc index 6e89ce1e..348f2f10 100644 --- a/content/documentation/General/Mainline_Hardware_Decoding.adoc +++ b/content/documentation/General/Mainline_Hardware_Decoding.adoc @@ -9,9 +9,9 @@ menu: weight: --- -{{% admonition type="note" %}} +{{< admonition type="note" >}} This page is incomplete, you're welcome to improve it. -{{% /admonition %}} +{{< /admonition >}} *Mainline Hardware Decoding* refers to video decoding done using hardware accelerators on the mainline Linux kernel (i.e. what sits in Linus' tree). diff --git a/content/documentation/General/Overclocking.adoc b/content/documentation/General/Overclocking.adoc index ac435df3..18217356 100644 --- a/content/documentation/General/Overclocking.adoc +++ b/content/documentation/General/Overclocking.adoc @@ -13,13 +13,13 @@ menu: There is the possibility of damaging your equipment by overclocking. Do so at your own risk! {{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} This page is incomplete, you're welcome to improve it. -{{% /admonition %}} +{{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it https://elinux.org/Device_Tree_Reference[here]. -{{% /admonition %}} +{{< /admonition >}} Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware). @@ -63,13 +63,13 @@ Save the DTS file, and recompile the DTB. In order to check if the overclock was The file may be slightly different and you may need to enter the values as hexadecimals {{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed. -{{% /admonition %}} +{{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} Remember to run a benchmark tool (such as glmark2-es2) to help check stability. -{{% /admonition %}} +{{< /admonition >}} === CPU @@ -115,9 +115,9 @@ The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (u The user _somefoo_ was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load|The silicon lottery will dictate how well you can undervolt. {{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as _stress-ng_) to ensure stability. -{{% /admonition %}} +{{< /admonition >}} === DRAM @@ -125,13 +125,13 @@ The exact voltages and frequencies that you can achieve will depend on your devi It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit. {{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} Make sure to set your DRAM to a multiple of 24. -{{% /admonition %}} +{{< /admonition >}} -{{% admonition type="note" %}} +{{< admonition type="note" >}} The current frequency your DRAM is running at can be found using this command: `cat /proc/device-tree/memory/ram_freq` -{{% /admonition %}} +{{< /admonition >}} When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however. diff --git a/content/documentation/PinePhone_Pro/Software/Software_state.adoc b/content/documentation/PinePhone_Pro/Software/Software_state.adoc index c4f6cb32..d7f15738 100644 --- a/content/documentation/PinePhone_Pro/Software/Software_state.adoc +++ b/content/documentation/PinePhone_Pro/Software/Software_state.adoc @@ -20,9 +20,9 @@ The following table lists the feature functionality status of the unaltered pre- * Matrix: https://app.element.io/#/room/#pinephone:matrix.org * Telegram: https://t.me/pinephone -{{% admonition type="note" %}} +{{< admonition type="note" >}} The software is *written by the community*, any contributions towards the community projects are greatly appreciated! Please see "link:/documentation/Introduction/How_to_contribute[How to Contribute]" to learn about how to contribute to the software projects and "link:/documentation/Introduction/Where_to_report_bugs[Where to Report Bugs]" to learn about where to report bugs. -{{% /admonition %}} +{{< /admonition >}} [cols="2,2,1,1,4"] |=== diff --git a/content/documentation/PineTab2/Getting_started.adoc b/content/documentation/PineTab2/Getting_started.adoc index fe34f59a..67802d0f 100644 --- a/content/documentation/PineTab2/Getting_started.adoc +++ b/content/documentation/PineTab2/Getting_started.adoc @@ -24,9 +24,9 @@ The second box has the keyboard in it. The PineTab2 can be started by pressing and holding the power button for two seconds. The device is initialized at the first boot and will power-cycle while the partition table is populated. -{{% admonition type="info" %}} +{{< admonition type="info" >}} If the initialization process is interrupted it might lead to a corrupted operating system installation. In that case reinstall the operating system as explained below. -{{% /admonition %}} +{{< /admonition >}} The PineTab2 ships with _DanctNix Arch Linux_ and comes with a pre-set user and the default password `123456`. diff --git a/content/documentation/SOPINE/Software/Releases.adoc b/content/documentation/SOPINE/Software/Releases.adoc index 6d6aa208..e48c23e7 100644 --- a/content/documentation/SOPINE/Software/Releases.adoc +++ b/content/documentation/SOPINE/Software/Releases.adoc @@ -84,9 +84,9 @@ Download: * http://files.pine64.org/os/SOPINE/nems/NEMS_v1.5-SOPine-Build1.zip[Direct download from pine64.org] (supports the microSD card, 16GB or more, MD5 of the xz file is _5ad0d684296d50b4c1fcbac6db205ae0_) * https://nemslinux.com/download/nagios-for-pine64.php[Download torrent seed from NEMS Linux] (supports the microSD card, 16GB or more, MD5 of the xz file is _6e2088922c5d197db8b8ba3057120389_) -{{% admonition type="info" %}} +{{< admonition type="info" >}} The installation guide can be found https://docs.nemslinux.com/installation[here]. -{{% /admonition %}} +{{< /admonition >}} |=== 2+| Default credentials