<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[PINE64 - General Discussion on ROCK64]]></title>
		<link>https://forum.pine64.org/</link>
		<description><![CDATA[PINE64 - https://forum.pine64.org]]></description>
		<pubDate>Tue, 21 Apr 2026 09:59:24 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Disable MicroSD reader for extra GPIO]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19365</link>
			<pubDate>Sun, 28 Jul 2024 04:08:44 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28389">mxruben</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19365</guid>
			<description><![CDATA[Hello! I am working on a project that requires nearly all of the GPIO pins on the rock64. 7 of the GPIO pins are unusable while the microSD card reader is in use. To fix this, I installed armbian onto a usb drive and am booting from it now instead. However, I am still unable to set the GPIO pins that were in use by the microSD card reader. My guess is that it is still active, even though it is not reading anything. I think I need to do something to disable it. Has anyone found a way to access these GPIO pins?]]></description>
			<content:encoded><![CDATA[Hello! I am working on a project that requires nearly all of the GPIO pins on the rock64. 7 of the GPIO pins are unusable while the microSD card reader is in use. To fix this, I installed armbian onto a usb drive and am booting from it now instead. However, I am still unable to set the GPIO pins that were in use by the microSD card reader. My guess is that it is still active, even though it is not reading anything. I think I need to do something to disable it. Has anyone found a way to access these GPIO pins?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Rock64 No Audio @ Debian 12]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19137</link>
			<pubDate>Fri, 15 Mar 2024 15:01:24 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=8433">dmitrymyadzelets</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19137</guid>
			<description><![CDATA[How to reproduce:<ul class="mycode_list"><li>Install <a href="https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/" target="_blank" rel="noopener" class="mycode_url">Debian 12</a><br />
</li>
<li>Observe the "<span style="font-weight: bold;" class="mycode_b">platform analog-sound: deferred probe pending</span>" message in the output of <span style="font-weight: bold;" class="mycode_b">dmesg</span><br />
</li>
</ul>
Expected: no such message.<br />
<br />
The above is the root of the problem, IMHO.<br />
<br />
Additionally, you may:<ul class="mycode_list"><li>Install <span style="font-weight: bold;" class="mycode_b">alsa-utils</span><br />
</li>
<li>Observe no <span style="font-weight: bold;" class="mycode_b">analog-sound </span>in the output of <span style="font-weight: bold;" class="mycode_b">alsa -l</span> command, but <span style="font-weight: bold;" class="mycode_b">spdif-sound </span>and <span style="font-weight: bold;" class="mycode_b">hdmi-sound</span> do exist.<br />
</li>
</ul>
<br />
Expected: Three sound interfaces: analog-sound, spdif-sound, hdmi-sound (as described in the Device Tree file located in <span style="font-weight: bold;" class="mycode_b">/boot/dtbs/.../rk3328-rock64.dtb</span>).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Linux rock 6.1.0-18-arm64 #1 SMP Debian 6.1.76-1 (2024-02-01) @ Rock64 v2</span>]]></description>
			<content:encoded><![CDATA[How to reproduce:<ul class="mycode_list"><li>Install <a href="https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/" target="_blank" rel="noopener" class="mycode_url">Debian 12</a><br />
</li>
<li>Observe the "<span style="font-weight: bold;" class="mycode_b">platform analog-sound: deferred probe pending</span>" message in the output of <span style="font-weight: bold;" class="mycode_b">dmesg</span><br />
</li>
</ul>
Expected: no such message.<br />
<br />
The above is the root of the problem, IMHO.<br />
<br />
Additionally, you may:<ul class="mycode_list"><li>Install <span style="font-weight: bold;" class="mycode_b">alsa-utils</span><br />
</li>
<li>Observe no <span style="font-weight: bold;" class="mycode_b">analog-sound </span>in the output of <span style="font-weight: bold;" class="mycode_b">alsa -l</span> command, but <span style="font-weight: bold;" class="mycode_b">spdif-sound </span>and <span style="font-weight: bold;" class="mycode_b">hdmi-sound</span> do exist.<br />
</li>
</ul>
<br />
Expected: Three sound interfaces: analog-sound, spdif-sound, hdmi-sound (as described in the Device Tree file located in <span style="font-weight: bold;" class="mycode_b">/boot/dtbs/.../rk3328-rock64.dtb</span>).<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Linux rock 6.1.0-18-arm64 #1 SMP Debian 6.1.76-1 (2024-02-01) @ Rock64 v2</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Rock64 doesn't boot]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18958</link>
			<pubDate>Wed, 20 Dec 2023 00:10:09 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=27032">dstallmo</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18958</guid>
			<description><![CDATA[I have a setup running 4 Pine 1 boards (the first board developed by Pine).  Earlier this year I purchased a Rock64-2G as well as the power supply listed in the Pine website to use for the Rock64.  I also downloaded the Armbian software listed for the Rock64 on the Pine website.  Using the Etcher executable on Windows I installed Armbian on a micro sdcard.  Then after plugging a ethernet plug, an HDMI plug, a keyboard and mouse and finally the power cord.  A red light on the card turns on but nothing appears on the HDMI terminal.  Again, this setup works fine for my Pine 1 boards.  Does anyone have any idea what I am doing wrong?]]></description>
			<content:encoded><![CDATA[I have a setup running 4 Pine 1 boards (the first board developed by Pine).  Earlier this year I purchased a Rock64-2G as well as the power supply listed in the Pine website to use for the Rock64.  I also downloaded the Armbian software listed for the Rock64 on the Pine website.  Using the Etcher executable on Windows I installed Armbian on a micro sdcard.  Then after plugging a ethernet plug, an HDMI plug, a keyboard and mouse and finally the power cord.  A red light on the card turns on but nothing appears on the HDMI terminal.  Again, this setup works fine for my Pine 1 boards.  Does anyone have any idea what I am doing wrong?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[hi, am new here. What happend to openbsd/krjdev ?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=18180</link>
			<pubDate>Sat, 29 Apr 2023 10:35:27 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26804">newestssd</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=18180</guid>
			<description><![CDATA[hi,<br />
<br />
What happend to openbsd/krjdev?<br />
<br />
<br />
any working builds 2023 or any instructions?<br />
<br />
thank you]]></description>
			<content:encoded><![CDATA[hi,<br />
<br />
What happend to openbsd/krjdev?<br />
<br />
<br />
any working builds 2023 or any instructions?<br />
<br />
thank you]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Latest Manjaro Update fails HDMI]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17787</link>
			<pubDate>Fri, 06 Jan 2023 16:47:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=23456">Flagtrax</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17787</guid>
			<description><![CDATA[After updating a Rock64 Ver. 2 board running Manjaro/Plasma, and running update, and then the obligatory reboot, the HDMI output was/is broken. The original system is as follows:<br />
<br />
<br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: 'times new roman', serif;" class="mycode_font">Operating System: Manjaro-ARM<br />
KDE Plasma Version: 5.24.4<br />
KDE Frameworks Version: 5.92.0<br />
Qt Version: 5.15.3<br />
Kernel Version: 5.17.1-4-MANJARO-ARM (64-bit)<br />
Graphics Platform: X11<br />
Processors: 4 × ARM Cortex-A53<br />
Memory: 3.9 GiB of RAM<br />
Graphics Processor: Mali450</span></span><br />
<br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: times new roman, serif;" class="mycode_font">I've downloaded the version labeled "Manjaro-ARM-gnome-rock64-22.06.img" and it creates the same issue. When I return to the older version HDMI is fine again. Then the system notifies that updates are required and the cycle begins again <img src="https://forum.pine64.org/images/smilies/confused.png" alt="Confused" title="Confused" class="smilie smilie_13" /></span></span><br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: times new roman, serif;" class="mycode_font">Anyone know of a solution?<br />
</span></span><br />
<br />
As an update I've imaged the Armbian OS and booted from the SD fine. Then manually updated the system. Again it booted up fine. The only problem so far is the HDMI output  flickering. It increases when system activity increases. For example; rolling the mouse over desktop icons will cause the screen to flicker. If the system sits idle the video stabilizes but if ANY activity is introduced, the flicker begins again. This makes it difficult to do anything with it. So in essence  neither of these OS's are usable as indicated.]]></description>
			<content:encoded><![CDATA[After updating a Rock64 Ver. 2 board running Manjaro/Plasma, and running update, and then the obligatory reboot, the HDMI output was/is broken. The original system is as follows:<br />
<br />
<br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: 'times new roman', serif;" class="mycode_font">Operating System: Manjaro-ARM<br />
KDE Plasma Version: 5.24.4<br />
KDE Frameworks Version: 5.92.0<br />
Qt Version: 5.15.3<br />
Kernel Version: 5.17.1-4-MANJARO-ARM (64-bit)<br />
Graphics Platform: X11<br />
Processors: 4 × ARM Cortex-A53<br />
Memory: 3.9 GiB of RAM<br />
Graphics Processor: Mali450</span></span><br />
<br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: times new roman, serif;" class="mycode_font">I've downloaded the version labeled "Manjaro-ARM-gnome-rock64-22.06.img" and it creates the same issue. When I return to the older version HDMI is fine again. Then the system notifies that updates are required and the cycle begins again <img src="https://forum.pine64.org/images/smilies/confused.png" alt="Confused" title="Confused" class="smilie smilie_13" /></span></span><br />
<span style="color: #222222;" class="mycode_color"><span style="font-family: times new roman, serif;" class="mycode_font">Anyone know of a solution?<br />
</span></span><br />
<br />
As an update I've imaged the Armbian OS and booted from the SD fine. Then manually updated the system. Again it booted up fine. The only problem so far is the HDMI output  flickering. It increases when system activity increases. For example; rolling the mouse over desktop icons will cause the screen to flicker. If the system sits idle the video stabilizes but if ANY activity is introduced, the flicker begins again. This makes it difficult to do anything with it. So in essence  neither of these OS's are usable as indicated.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[rock64 v3  spiflash]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17671</link>
			<pubDate>Mon, 28 Nov 2022 20:18:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26127">Macgyver</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17671</guid>
			<description><![CDATA[Is it possible to add spi_flash ship to this board then use it to boot to usb? If so how?<br />
if not why?]]></description>
			<content:encoded><![CDATA[Is it possible to add spi_flash ship to this board then use it to boot to usb? If so how?<br />
if not why?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ROCK64 v3 can it boot from USB?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17612</link>
			<pubDate>Tue, 15 Nov 2022 11:32:29 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26062">Tsagualsa</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17612</guid>
			<description><![CDATA[Helllo, looking at the new ROCK64 the spi flash chip is no longer included so my question is if it is possible to boot from an ssd connected via USB?]]></description>
			<content:encoded><![CDATA[Helllo, looking at the new ROCK64 the spi flash chip is no longer included so my question is if it is possible to boot from an ssd connected via USB?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[How well does Rock64 deal with HDR and Atmos on Kodi?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17606</link>
			<pubDate>Mon, 14 Nov 2022 04:11:44 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=26053">drvlikhell</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17606</guid>
			<description><![CDATA[I'm looking to use the Rock64 for emulation and media playback. I will be running RetroPie, Batocera, Recalbox, Lakka, or RetroArch. Which ever one runs the best, or is easiest to set up will be fine. I plan to install Kodi into which ever OS I go with. One of them even has Kodi preinstalled. The emulation capabilities of the Rock64 are just fine for my expectations but I'm curious about how well it handles HDR video and also passthrough audio with Atmos. I searched around to see what people had to say but most of the posts are from two years ago or more, and I know that development usually moves along pretty quickly so issues from two years ago may have been solved by now.<br />
<br />
I will be playing media locally with Kodi. Files will be in h.265 10 bit with HDR and most will have Dolby Digital Plus with Atmos, some will be Dolby TrueHD with Atmos. Output will be via HDMI into a home theater receiver that fully supports the above audio codecs.<br />
<br />
Does anybody have any recent experience with this type of setup? Any problems with either HDR or Atmos passthrough?]]></description>
			<content:encoded><![CDATA[I'm looking to use the Rock64 for emulation and media playback. I will be running RetroPie, Batocera, Recalbox, Lakka, or RetroArch. Which ever one runs the best, or is easiest to set up will be fine. I plan to install Kodi into which ever OS I go with. One of them even has Kodi preinstalled. The emulation capabilities of the Rock64 are just fine for my expectations but I'm curious about how well it handles HDR video and also passthrough audio with Atmos. I searched around to see what people had to say but most of the posts are from two years ago or more, and I know that development usually moves along pretty quickly so issues from two years ago may have been solved by now.<br />
<br />
I will be playing media locally with Kodi. Files will be in h.265 10 bit with HDR and most will have Dolby Digital Plus with Atmos, some will be Dolby TrueHD with Atmos. Output will be via HDMI into a home theater receiver that fully supports the above audio codecs.<br />
<br />
Does anybody have any recent experience with this type of setup? Any problems with either HDR or Atmos passthrough?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Rock64 won't boot]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17553</link>
			<pubDate>Thu, 03 Nov 2022 02:22:32 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=25996">luminosity7</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17553</guid>
			<description><![CDATA[Hi:<br />
<br />
I have a new Rock64. So far I am 0/2 in terms of getting OSes to boot. First I tried DietPi (DietPi_ROCK64-ARMv8-Bullseye.7z) . Followed directions, unzipped OS, flashed with Etcher.  It never booted just had a flashing red light. Next I tried one of the recommended Ambian (Armbian_22.08.8_Rock64_jammy_current_5.15.74_xfce_desktop). This was one actually booted into the command line but once I made a user and tried to get the desktop going it crapped out on me. I just ended up with a black screen with a flashing white cursor in upper left hand corner. Both these issues seem to be in the forums/online but with no apparent solutions. The Rock64 DietPi thread goes back years ago.  So if anyone has recently successfully installed and run one of the recommended OSes in the getting started guide for the Rock64 please let me know. Any help would be greatly appreciated.<br />
<br />
Matt]]></description>
			<content:encoded><![CDATA[Hi:<br />
<br />
I have a new Rock64. So far I am 0/2 in terms of getting OSes to boot. First I tried DietPi (DietPi_ROCK64-ARMv8-Bullseye.7z) . Followed directions, unzipped OS, flashed with Etcher.  It never booted just had a flashing red light. Next I tried one of the recommended Ambian (Armbian_22.08.8_Rock64_jammy_current_5.15.74_xfce_desktop). This was one actually booted into the command line but once I made a user and tried to get the desktop going it crapped out on me. I just ended up with a black screen with a flashing white cursor in upper left hand corner. Both these issues seem to be in the forums/online but with no apparent solutions. The Rock64 DietPi thread goes back years ago.  So if anyone has recently successfully installed and run one of the recommended OSes in the getting started guide for the Rock64 please let me know. Any help would be greatly appreciated.<br />
<br />
Matt]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[my rock64 dosen't work]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17442</link>
			<pubDate>Sat, 08 Oct 2022 01:50:26 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=23953">rookie_267</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17442</guid>
			<description><![CDATA[I put my ROCK64 on the desktop for a period of time, but it didn't work properly today.I try to reflash the SD card,and it still didn't work,and shows ''Unable to handle kernel paging request at virtual address ffffffc0ffa3fe30''.Here is my boot log<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/txt.png" title="Log" border="0" alt=".log" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=2709" target="_blank" title="">teraterm.log</a> (Size: 38.04 KB / Downloads: 557)
<!-- end: postbit_attachments_attachment -->]]></description>
			<content:encoded><![CDATA[I put my ROCK64 on the desktop for a period of time, but it didn't work properly today.I try to reflash the SD card,and it still didn't work,and shows ''Unable to handle kernel paging request at virtual address ffffffc0ffa3fe30''.Here is my boot log<br /><!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forum.pine64.org/images/attachtypes/txt.png" title="Log" border="0" alt=".log" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=2709" target="_blank" title="">teraterm.log</a> (Size: 38.04 KB / Downloads: 557)
<!-- end: postbit_attachments_attachment -->]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Rock64 u-boot for eMMC Build Error]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=17366</link>
			<pubDate>Sun, 18 Sep 2022 20:29:27 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=25801">mexicanflyer</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=17366</guid>
			<description><![CDATA[I have a Rock64 4GB board which I would like to turn into a FreedomBox server.<br />
<br />
Since the Rock64 boards are no longer sold with SPI flash, I am trying <br />
to build U-Boot to flash onto the eMMC module. I am following the instructions<br />
for building here:<br />
<br />
<a href="https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html" target="_blank" rel="noopener" class="mycode_url">https://u-boot.readthedocs.io/en/latest/...kchip.html</a><br />
<br />
However, when I get to here:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>make CROSS_COMPILE=aarch64-linux-gnu-</code></div></div><br />
<br />
I get this error:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ModuleNotFoundError: No module named 'distutils.core'<br />
make[2]: *** [scripts/dtc/pylibfdt/Makefile:30: rebuild] Error 1<br />
make[1]: *** [scripts/Makefile.build:398: scripts/dtc/pylibfdt] Error 2<br />
make: *** [Makefile:2047: scripts_dtc] Error 2</code></div></div><br />
<br />
Some investigation tells me pylibfdt is not yet compatible with python3, and it will<br />
be a while before the developers will be able to solve the problem, as it causes many other issues. <br />
I installed python2, but I get this error:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>scripts/dtc/pylibfdt/libfdt_wrap.c:154:11: fatal error: Python.h: No such file or directory<br />
  154 | # include &lt;Python.h&gt;<br />
      |           ^~~~~~~~~~<br />
compilation terminated.<br />
error: command '/usr/bin/cc' failed with exit code 1<br />
make[2]: *** [scripts/dtc/pylibfdt/Makefile:30: rebuild] Error 1<br />
make[1]: *** [scripts/Makefile.build:398: scripts/dtc/pylibfdt] Error 2<br />
make: *** [Makefile:2047: scripts_dtc] Error 2</code></div></div><br />
<br />
What am I able to do in order to work around this issue?<br />
<br />
For clarity, will the u-boot and FreedomBox installations exist on the same eMMC module in the end, or must I install one to an SD card and the other on the eMMC module?<br />
<br />
<br />
Thank you for reading the post. I would appreciate any advice you have to offer.]]></description>
			<content:encoded><![CDATA[I have a Rock64 4GB board which I would like to turn into a FreedomBox server.<br />
<br />
Since the Rock64 boards are no longer sold with SPI flash, I am trying <br />
to build U-Boot to flash onto the eMMC module. I am following the instructions<br />
for building here:<br />
<br />
<a href="https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html" target="_blank" rel="noopener" class="mycode_url">https://u-boot.readthedocs.io/en/latest/...kchip.html</a><br />
<br />
However, when I get to here:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>make CROSS_COMPILE=aarch64-linux-gnu-</code></div></div><br />
<br />
I get this error:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>ModuleNotFoundError: No module named 'distutils.core'<br />
make[2]: *** [scripts/dtc/pylibfdt/Makefile:30: rebuild] Error 1<br />
make[1]: *** [scripts/Makefile.build:398: scripts/dtc/pylibfdt] Error 2<br />
make: *** [Makefile:2047: scripts_dtc] Error 2</code></div></div><br />
<br />
Some investigation tells me pylibfdt is not yet compatible with python3, and it will<br />
be a while before the developers will be able to solve the problem, as it causes many other issues. <br />
I installed python2, but I get this error:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>scripts/dtc/pylibfdt/libfdt_wrap.c:154:11: fatal error: Python.h: No such file or directory<br />
  154 | # include &lt;Python.h&gt;<br />
      |           ^~~~~~~~~~<br />
compilation terminated.<br />
error: command '/usr/bin/cc' failed with exit code 1<br />
make[2]: *** [scripts/dtc/pylibfdt/Makefile:30: rebuild] Error 1<br />
make[1]: *** [scripts/Makefile.build:398: scripts/dtc/pylibfdt] Error 2<br />
make: *** [Makefile:2047: scripts_dtc] Error 2</code></div></div><br />
<br />
What am I able to do in order to work around this issue?<br />
<br />
For clarity, will the u-boot and FreedomBox installations exist on the same eMMC module in the end, or must I install one to an SD card and the other on the eMMC module?<br />
<br />
<br />
Thank you for reading the post. I would appreciate any advice you have to offer.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ROCK64 - Not start]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=16994</link>
			<pubDate>Mon, 11 Jul 2022 09:49:55 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=8441">mathieu</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=16994</guid>
			<description><![CDATA[hello, <br />
<br />
I have a rock64 4G with a 32Gb emmc, I wanted to reinstall it a debian OS <a href="https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/stretch-minimal-rock64" target="_blank" rel="noopener" class="mycode_url">https://github.com/ayufan-rock64/linux-b...mal-rock64</a> -0.9.14-1159-arm64.img.xz.<br />
<br />
But once installed when I turn it on it never goes all the way through loading it always freezes randomly on booting the OS. You can see screenshots.<br />
<br />
Do you have an idea?<br />
<br />
Thank you in advance for your answers.<br />
<br />
<br />
regards,<br />
<br />
<a href="https://drive.google.com/file/d/1Rr3D45vtsoiYAz-4EK-azxLtsDTFlkYs/view?usp=sharing" target="_blank" rel="noopener" class="mycode_url">https://drive.google.com/file/d/1Rr3D45v...sp=sharing</a><br />
<br />
<a href="https://drive.google.com/file/d/1WnjwB-9qGNFuA3WM1B73YRnO9rkPB1Dw/view?usp=sharing" target="_blank" rel="noopener" class="mycode_url">https://drive.google.com/file/d/1WnjwB-9...sp=sharing</a>]]></description>
			<content:encoded><![CDATA[hello, <br />
<br />
I have a rock64 4G with a 32Gb emmc, I wanted to reinstall it a debian OS <a href="https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/stretch-minimal-rock64" target="_blank" rel="noopener" class="mycode_url">https://github.com/ayufan-rock64/linux-b...mal-rock64</a> -0.9.14-1159-arm64.img.xz.<br />
<br />
But once installed when I turn it on it never goes all the way through loading it always freezes randomly on booting the OS. You can see screenshots.<br />
<br />
Do you have an idea?<br />
<br />
Thank you in advance for your answers.<br />
<br />
<br />
regards,<br />
<br />
<a href="https://drive.google.com/file/d/1Rr3D45vtsoiYAz-4EK-azxLtsDTFlkYs/view?usp=sharing" target="_blank" rel="noopener" class="mycode_url">https://drive.google.com/file/d/1Rr3D45v...sp=sharing</a><br />
<br />
<a href="https://drive.google.com/file/d/1WnjwB-9qGNFuA3WM1B73YRnO9rkPB1Dw/view?usp=sharing" target="_blank" rel="noopener" class="mycode_url">https://drive.google.com/file/d/1WnjwB-9...sp=sharing</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Rock 64 failure / kernel panic]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=16938</link>
			<pubDate>Thu, 30 Jun 2022 15:59:04 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=25352">n0021913</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=16938</guid>
			<description><![CDATA[Hi, I am using Rock64 computers for a product and a few of them are failing in the field.  The symptom is that the computers lock up with a kernel panic (kernel paging request fail) and then do nothing until a power reset is performed.  It seems that the problem is memory related as we have started running memory tests on them and some of them fail the memory tests in as little as 5 minutes or less.  We have tried it with the 1 GB Rock64’s and also with the 2GB Rock64’s and they all exhibit the same failure issues.<br />
<br />
Has anyone come across these issues? And is there any workaround or fix for it??]]></description>
			<content:encoded><![CDATA[Hi, I am using Rock64 computers for a product and a few of them are failing in the field.  The symptom is that the computers lock up with a kernel panic (kernel paging request fail) and then do nothing until a power reset is performed.  It seems that the problem is memory related as we have started running memory tests on them and some of them fail the memory tests in as little as 5 minutes or less.  We have tried it with the 1 GB Rock64’s and also with the 2GB Rock64’s and they all exhibit the same failure issues.<br />
<br />
Has anyone come across these issues? And is there any workaround or fix for it??]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OMV - Updates and Plug-in install broken]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=16923</link>
			<pubDate>Sun, 26 Jun 2022 19:21:51 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=7983">MotoTom</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=16923</guid>
			<description><![CDATA[Not sure if this is the right place but I just did a fresh install of stretch-openmediavault-rock64-0.9.14-1159-armhf.img on my Rock64. Now I can not update the system or install any plugins using the OMV Control Panel. I was able to update the system using Putty but i never had to do this with previous install (stretch-openmediavault-rock64-0.8.3-1141-armhf.img). Below is the log file from my most recent attempt to install shellinabox<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-missing --allow-unauthenticated --reinstall install openmediavault-shellinabox 2&gt;&amp;1' with exit code '100': Reading package lists...<br />
<br />
Building dependency tree...<br />
<br />
Reading state information...<br />
<br />
The following NEW packages will be installed:<br />
  openmediavault-shellinabox<br />
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.<br />
Need to get 13.3 kB of archives.<br />
After this operation, 157 kB of additional disk space will be used.<br />
Err:1 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main armhf openmediavault-shellinabox all 3.4<br />
  502  Bad Gateway<br />
Err:1 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main arm64 openmediavault-shellinabox all 3.4<br />
  502  Bad Gateway<br />
E: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/arrakis/pool/main/o/openmediavault-shellinabox/openmediavault-shellinabox_3.4_all.deb  502  Bad Gateway<br />
E: Internal Error, ordering was unable to handle the media swap<br />
&lt;&lt;&lt; *************************************</code></div></div><br />
Any suggestions are greatly appreciated.<br />
<br />
Thanks for reading.<br />
<br />
Tom]]></description>
			<content:encoded><![CDATA[Not sure if this is the right place but I just did a fresh install of stretch-openmediavault-rock64-0.9.14-1159-armhf.img on my Rock64. Now I can not update the system or install any plugins using the OMV Control Panel. I was able to update the system using Putty but i never had to do this with previous install (stretch-openmediavault-rock64-0.8.3-1141-armhf.img). Below is the log file from my most recent attempt to install shellinabox<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --allow-downgrades --allow-change-held-packages --fix-missing --allow-unauthenticated --reinstall install openmediavault-shellinabox 2&gt;&amp;1' with exit code '100': Reading package lists...<br />
<br />
Building dependency tree...<br />
<br />
Reading state information...<br />
<br />
The following NEW packages will be installed:<br />
  openmediavault-shellinabox<br />
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.<br />
Need to get 13.3 kB of archives.<br />
After this operation, 157 kB of additional disk space will be used.<br />
Err:1 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main armhf openmediavault-shellinabox all 3.4<br />
  502  Bad Gateway<br />
Err:1 https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch/main arm64 openmediavault-shellinabox all 3.4<br />
  502  Bad Gateway<br />
E: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/arrakis/pool/main/o/openmediavault-shellinabox/openmediavault-shellinabox_3.4_all.deb  502  Bad Gateway<br />
E: Internal Error, ordering was unable to handle the media swap<br />
&lt;&lt;&lt; *************************************</code></div></div><br />
Any suggestions are greatly appreciated.<br />
<br />
Thanks for reading.<br />
<br />
Tom]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OpenWRT on the Rock64]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=16305</link>
			<pubDate>Sun, 13 Mar 2022 01:11:47 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=24065">CanadianBacon</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=16305</guid>
			<description><![CDATA[I have started the process of getting OpenWRT working on the Rock64.<br />
<br />
I have a working image alongside a custom repo for packages which can be found here, download links for the SD Card images are front and centre: <a href="https://openwrt.cdnbcn.net/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.cdnbcn.net/</a><br />
<br />
When installing the SD Card image, you will have to manually configure /etc/opkg/distfeeds.conf with my custom repo, however I'll fix this in a later build.<br />
<br />
The main issues currently are as follows:<br />
    - USB3 port isn't working<br />
    - Onboard Ethernet doesn't reset correctly 100% of the time<br />
<br />
The source code can be found at <a href="https://github.com/CanadianBaconBoi/openwrt/tree/rock64" target="_blank" rel="noopener" class="mycode_url">https://github.com/CanadianBaconBoi/openwrt/tree/rock64</a>.<br />
It is based on the work of lucize however it has been updated for a modern version of OpenWRT.<br />
<br />
There is a thread with some fixes for the aforementioned issues below, however I have been short on time recently and haven't been able to get around to implementing them yet.<br />
<a href="https://forum.pine64.org/showthread.php?tid=11012" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=11012</a><br />
<br />
Any help would be greatly appreciated in pulling these in, I'll continue to host the package repo for free until this is pulled into upstream.]]></description>
			<content:encoded><![CDATA[I have started the process of getting OpenWRT working on the Rock64.<br />
<br />
I have a working image alongside a custom repo for packages which can be found here, download links for the SD Card images are front and centre: <a href="https://openwrt.cdnbcn.net/" target="_blank" rel="noopener" class="mycode_url">https://openwrt.cdnbcn.net/</a><br />
<br />
When installing the SD Card image, you will have to manually configure /etc/opkg/distfeeds.conf with my custom repo, however I'll fix this in a later build.<br />
<br />
The main issues currently are as follows:<br />
    - USB3 port isn't working<br />
    - Onboard Ethernet doesn't reset correctly 100% of the time<br />
<br />
The source code can be found at <a href="https://github.com/CanadianBaconBoi/openwrt/tree/rock64" target="_blank" rel="noopener" class="mycode_url">https://github.com/CanadianBaconBoi/openwrt/tree/rock64</a>.<br />
It is based on the work of lucize however it has been updated for a modern version of OpenWRT.<br />
<br />
There is a thread with some fixes for the aforementioned issues below, however I have been short on time recently and haven't been able to get around to implementing them yet.<br />
<a href="https://forum.pine64.org/showthread.php?tid=11012" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=11012</a><br />
<br />
Any help would be greatly appreciated in pulling these in, I'll continue to host the package repo for free until this is pulled into upstream.]]></content:encoded>
		</item>
	</channel>
</rss>