<?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 - Linux on Pinebook Pro]]></title>
		<link>https://forum.pine64.org/</link>
		<description><![CDATA[PINE64 - https://forum.pine64.org]]></description>
		<pubDate>Fri, 24 Apr 2026 05:54:52 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Touchpad tap to click]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20173</link>
			<pubDate>Mon, 19 Jan 2026 19:38:34 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=11475">Der Geist der Maschine</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20173</guid>
			<description><![CDATA[Debian 13 / xfce with Daniel Thompon's ancient 5.7 kernel and updated touchpad firmware (too long ago that I remember the details).<br />
<br />
Under xfce -&gt; settings -&gt; mouse and touchpad, I checkmarked "tap touchpad to click". Tap to click works with one finger taps, only. For 2 or 3 finger clicks, I need to press the touchpad.<br />
<br />
On other computers running Debian / xfce, I can tap with two and three fingers as well.<br />
<br />
What about you? Does it work for you on the Pinebook Pro and I just need to dig deeper?]]></description>
			<content:encoded><![CDATA[Debian 13 / xfce with Daniel Thompon's ancient 5.7 kernel and updated touchpad firmware (too long ago that I remember the details).<br />
<br />
Under xfce -&gt; settings -&gt; mouse and touchpad, I checkmarked "tap touchpad to click". Tap to click works with one finger taps, only. For 2 or 3 finger clicks, I need to press the touchpad.<br />
<br />
On other computers running Debian / xfce, I can tap with two and three fingers as well.<br />
<br />
What about you? Does it work for you on the Pinebook Pro and I just need to dig deeper?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Window Maker Live for Pinebook Pro]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=20098</link>
			<pubDate>Mon, 01 Dec 2025 13:14:39 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=21682">vajak</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=20098</guid>
			<description><![CDATA[As was just verified, the arm64 UEFI variant of the Window Maker Live Linux distribution based on Debian/Trixie boots just fine on towboot enabled Pinebook Pro. This also includes the graphical debian installer routine, avoiding the need to bother with the awkward serial console for installations. I didn't complete a full installation yet on my own bare metal PBP because the machine needed for development is not suitable also for testing, and all installation testing has been done only in qemu so far.<br />
<br />
See <a href="https://wmlive.sourceforge.net" target="_blank" rel="noopener" class="mycode_url">https://wmlive.sourceforge.net</a> for more details and descriptions, screenshots, and download options.<br />
<br />
Before you start downloading the ISO image for trying it out yourself, be aware that with the exception of the freely usable i386 version, the ISO images for both arm64 and amd64 are distributed as encrypted 7z archives which require a password to unpack them. Due to personal circumstances i am currently not in the position to just give away the fruits of my time and efforts investment without asking for a return. Until it will finally be publicly disclosed at the end of this year, this password is therefore provided only to people who are donating some cash to the project. <br />
<br />
On the other hand, the sources to enable people to build any variant of the ISO themselves are, of course, readily available. So if you can't afford even any minimal donation and don't want to wait for the public password disclosure at the end of the year, you can simply create your own custom ISO image.<br />
<br />
For interested people who are contributing any publicly accessible open source work themselves, the password will be freely provided without any donation requirement. Please contact me privately if this is of interest for you.]]></description>
			<content:encoded><![CDATA[As was just verified, the arm64 UEFI variant of the Window Maker Live Linux distribution based on Debian/Trixie boots just fine on towboot enabled Pinebook Pro. This also includes the graphical debian installer routine, avoiding the need to bother with the awkward serial console for installations. I didn't complete a full installation yet on my own bare metal PBP because the machine needed for development is not suitable also for testing, and all installation testing has been done only in qemu so far.<br />
<br />
See <a href="https://wmlive.sourceforge.net" target="_blank" rel="noopener" class="mycode_url">https://wmlive.sourceforge.net</a> for more details and descriptions, screenshots, and download options.<br />
<br />
Before you start downloading the ISO image for trying it out yourself, be aware that with the exception of the freely usable i386 version, the ISO images for both arm64 and amd64 are distributed as encrypted 7z archives which require a password to unpack them. Due to personal circumstances i am currently not in the position to just give away the fruits of my time and efforts investment without asking for a return. Until it will finally be publicly disclosed at the end of this year, this password is therefore provided only to people who are donating some cash to the project. <br />
<br />
On the other hand, the sources to enable people to build any variant of the ISO themselves are, of course, readily available. So if you can't afford even any minimal donation and don't want to wait for the public password disclosure at the end of the year, you can simply create your own custom ISO image.<br />
<br />
For interested people who are contributing any publicly accessible open source work themselves, the password will be freely provided without any donation requirement. Please contact me privately if this is of interest for you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Armbian fix, current version now works]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19943</link>
			<pubDate>Fri, 08 Aug 2025 14:49:07 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28616">Sb2024</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19943</guid>
			<description><![CDATA[A user on the armbian forum figured out how to get armbian to work. I was able to follow these instructions and update my machine. This requires tow boot on the spi. My system is on an nvme. <br />
<br />
The forum pst is here:<a href="https://forum.armbian.com/topic/50474-experiences-installing-on-pinebook-pro/" target="_blank" rel="noopener" class="mycode_url">https://forum.armbian.com/topic/50474-ex...ebook-pro/</a>]]></description>
			<content:encoded><![CDATA[A user on the armbian forum figured out how to get armbian to work. I was able to follow these instructions and update my machine. This requires tow boot on the spi. My system is on an nvme. <br />
<br />
The forum pst is here:<a href="https://forum.armbian.com/topic/50474-experiences-installing-on-pinebook-pro/" target="_blank" rel="noopener" class="mycode_url">https://forum.armbian.com/topic/50474-ex...ebook-pro/</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PulseAudio dropouts after Manjaro Testing 2025.07.26 update]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19938</link>
			<pubDate>Tue, 05 Aug 2025 05:31:28 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=17064">Dendrocalamus64</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19938</guid>
			<description><![CDATA[I see on the Manjaro forums they have a thread for every ARM Unstable Update.<br />
<a href="https://forum.manjaro.org/c/arm/100" target="_blank" rel="noopener" class="mycode_url">https://forum.manjaro.org/c/arm/100</a><br />
<br />
They say that only ARM Unstable is maintained anymore, but Testing seems to be getting updates too.<br />
<br />
This Testing update arrived around 07.26 (Sat).  Videos that used to play fine in mpv started getting debilitating amounts of audio dropouts with a buffer underrun message each time.<br />
<br />
At first I thought it was due to video decompression getting less efficient and eating all the CPU, but playing the same files with --no-video and top running showed the system lightly loaded (~8% CPU), and yet the audio dropouts occured in the exact same places.<br />
<br />
I tried updating to the Megi 6.15 kernel and rebooting.  mpv no longer said "Audio device underrun detected" but the dropouts still occured, and pulseaudio was now hanging all the time and needing to be killed &amp; restarted.<br />
<br />
Start reading through this loooong page:<br />
<a href="https://wiki.archlinux.org/title/PulseAudio/Troubleshooting" target="_blank" rel="noopener" class="mycode_url">https://wiki.archlinux.org/title/PulseAu...leshooting</a><br />
<br />
Try running with pulseaudio -v, notice that it seems to be suspending too much.<br />
<br />
Section 4.8, unload-module module-suspend-on-idle<br />
<br />
And that fixed the problem completely.<br />
<br />
(I had tried various other things since 07.26 like turning timer-based scheduling on and off, and adjusting buffer sizes, and so far none of it had helped.)<br />
<br />
So pulseaudio suspend-on-idle is currently completely broken, at least with the default config.  It thinks it's "idle" while it's playing back a video and the laptop is actively being used.<br />
<br />
Next problem was pulseaudio sometimes starts endlessly spamming to the console,<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>W: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-sink.c: Resume failed, couldn't restore original sample settings.<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-sink.c: Trying resume...<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-util.c: Cannot disable ALSA period wakeups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-util.c: Device hw:rockchipes8316c doesn't support 48000 Hz, changed to 44100 Hz.</code></div></div><br />
Solution to that was to edit /etc/pulse/daemon.conf and set both default-sample-rate and alternate-sample-rate to 44100.]]></description>
			<content:encoded><![CDATA[I see on the Manjaro forums they have a thread for every ARM Unstable Update.<br />
<a href="https://forum.manjaro.org/c/arm/100" target="_blank" rel="noopener" class="mycode_url">https://forum.manjaro.org/c/arm/100</a><br />
<br />
They say that only ARM Unstable is maintained anymore, but Testing seems to be getting updates too.<br />
<br />
This Testing update arrived around 07.26 (Sat).  Videos that used to play fine in mpv started getting debilitating amounts of audio dropouts with a buffer underrun message each time.<br />
<br />
At first I thought it was due to video decompression getting less efficient and eating all the CPU, but playing the same files with --no-video and top running showed the system lightly loaded (~8% CPU), and yet the audio dropouts occured in the exact same places.<br />
<br />
I tried updating to the Megi 6.15 kernel and rebooting.  mpv no longer said "Audio device underrun detected" but the dropouts still occured, and pulseaudio was now hanging all the time and needing to be killed &amp; restarted.<br />
<br />
Start reading through this loooong page:<br />
<a href="https://wiki.archlinux.org/title/PulseAudio/Troubleshooting" target="_blank" rel="noopener" class="mycode_url">https://wiki.archlinux.org/title/PulseAu...leshooting</a><br />
<br />
Try running with pulseaudio -v, notice that it seems to be suspending too much.<br />
<br />
Section 4.8, unload-module module-suspend-on-idle<br />
<br />
And that fixed the problem completely.<br />
<br />
(I had tried various other things since 07.26 like turning timer-based scheduling on and off, and adjusting buffer sizes, and so far none of it had helped.)<br />
<br />
So pulseaudio suspend-on-idle is currently completely broken, at least with the default config.  It thinks it's "idle" while it's playing back a video and the laptop is actively being used.<br />
<br />
Next problem was pulseaudio sometimes starts endlessly spamming to the console,<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>W: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-sink.c: Resume failed, couldn't restore original sample settings.<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-sink.c: Trying resume...<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-util.c: Cannot disable ALSA period wakeups&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
I: [alsa-sink-ff890000.i2s-ES8316 HiFi ES8316 HiFi-0] alsa-util.c: Device hw:rockchipes8316c doesn't support 48000 Hz, changed to 44100 Hz.</code></div></div><br />
Solution to that was to edit /etc/pulse/daemon.conf and set both default-sample-rate and alternate-sample-rate to 44100.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Can’t login to Linux]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19930</link>
			<pubDate>Sun, 27 Jul 2025 06:30:04 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29433">fnosai</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19930</guid>
			<description><![CDATA[Hello, I am a newbie in Linux and I have a problem with login to Manjaro linux.<br />
I bought pinebook pro Pine64 in Canada and I can use it normally. After I transfer to Thailand I cannot login to Linux screen and screen turn on as shown below.<br />
<br />
Welcome to Manjaro-Arm<br />
Website : <a href="https://manjaro.org" target="_blank" rel="noopener" class="mycode_url">https://manjaro.org</a><br />
Forum :<br />
IRC:<br />
Matrix:<br />
Last login: <br />
<br />
(Xxx@xxxx)&#36;<br />
<br />
How can I fix this?<br />
Please help.]]></description>
			<content:encoded><![CDATA[Hello, I am a newbie in Linux and I have a problem with login to Manjaro linux.<br />
I bought pinebook pro Pine64 in Canada and I can use it normally. After I transfer to Thailand I cannot login to Linux screen and screen turn on as shown below.<br />
<br />
Welcome to Manjaro-Arm<br />
Website : <a href="https://manjaro.org" target="_blank" rel="noopener" class="mycode_url">https://manjaro.org</a><br />
Forum :<br />
IRC:<br />
Matrix:<br />
Last login: <br />
<br />
(Xxx@xxxx)&#36;<br />
<br />
How can I fix this?<br />
Please help.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[I need help deciding if my PBP can be updated]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19860</link>
			<pubDate>Tue, 10 Jun 2025 16:54:05 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=12663">ColoBill</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19860</guid>
			<description><![CDATA[Pinebook Pros,<br />
<br />
I need to update my PBP and want your advice.<br />
<br />
Here is my Linux background. I've had Linux as my desktop since about 1992. Softlanding Linux right when it came out and supported X-Windows.  Others came and went over the next 30 years like Slackware, Red Hat, CentOS, Fedora, Mint, Ubuntu.  I'm now back to Debian 12 with the MATE desktop. Before all that it was SunOS (Unix) on my desktop.<br />
<br />
I ordered my Pinebook Pro when it was announced and finally received it in 2019.  Then I added Manjaro to my list of Linux desktops.  The PBP is not powerful but has been all I've needed in a laptop.  I do all my primary work on desktops.  I've used my PBP on three continents so far and am headed to another continent in the fall.  I'm trying to decide if I can bring it up-to-dated.  Manjaro doesn't seem to be keeping up.<br />
<br />
Questions:<br />
<br />
1) Linux Version<br />
  * Is Debian a good option now for PBP?<br />
  * Are there guides for installation?<br />
  * Can I use MATE?<br />
<br />
2) Updates<br />
  * Are there firmware updates that I should apply.  It's never been updated.<br />
  * I've never gotten it to suspend or sleep.  Or I've never gotten it to wake back up.  But, I've found that I don't really need that for how I use it.<br />
  * Some of the function keys don't work the way they are advertised but the ones I use work fine.<br />
<br />
3) Hardware<br />
  * The left side hinge doesn't open correctly.  It's doesn't really bother me but I might try to fix that when/if I re-build the whole thing.  Are that any good pages showing the proper way to crack into the case?<br />
  <br />
Thanks!<br />
<br />
Bill]]></description>
			<content:encoded><![CDATA[Pinebook Pros,<br />
<br />
I need to update my PBP and want your advice.<br />
<br />
Here is my Linux background. I've had Linux as my desktop since about 1992. Softlanding Linux right when it came out and supported X-Windows.  Others came and went over the next 30 years like Slackware, Red Hat, CentOS, Fedora, Mint, Ubuntu.  I'm now back to Debian 12 with the MATE desktop. Before all that it was SunOS (Unix) on my desktop.<br />
<br />
I ordered my Pinebook Pro when it was announced and finally received it in 2019.  Then I added Manjaro to my list of Linux desktops.  The PBP is not powerful but has been all I've needed in a laptop.  I do all my primary work on desktops.  I've used my PBP on three continents so far and am headed to another continent in the fall.  I'm trying to decide if I can bring it up-to-dated.  Manjaro doesn't seem to be keeping up.<br />
<br />
Questions:<br />
<br />
1) Linux Version<br />
  * Is Debian a good option now for PBP?<br />
  * Are there guides for installation?<br />
  * Can I use MATE?<br />
<br />
2) Updates<br />
  * Are there firmware updates that I should apply.  It's never been updated.<br />
  * I've never gotten it to suspend or sleep.  Or I've never gotten it to wake back up.  But, I've found that I don't really need that for how I use it.<br />
  * Some of the function keys don't work the way they are advertised but the ones I use work fine.<br />
<br />
3) Hardware<br />
  * The left side hinge doesn't open correctly.  It's doesn't really bother me but I might try to fix that when/if I re-build the whole thing.  Are that any good pages showing the proper way to crack into the case?<br />
  <br />
Thanks!<br />
<br />
Bill]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PinePhone keyboard not registering input properly]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19817</link>
			<pubDate>Fri, 25 Apr 2025 09:37:52 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=29165">Feemphynead</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19817</guid>
			<description><![CDATA[I've recently got my PinePhone with the keyboard case.<br />
<br />
Everything was going well at first, but I’m now noticing that some keys don’t register consistently, especially the spacebar and a few on the top row. Sometimes I have to press harder than usual.<br />
<br />
I'm running postmarketOS and haven’t done much customization beyond updates.<br />
<br />
Is this a known issue with the keyboard hardware, or should I be looking into software configs or firmware?]]></description>
			<content:encoded><![CDATA[I've recently got my PinePhone with the keyboard case.<br />
<br />
Everything was going well at first, but I’m now noticing that some keys don’t register consistently, especially the spacebar and a few on the top row. Sometimes I have to press harder than usual.<br />
<br />
I'm running postmarketOS and haven’t done much customization beyond updates.<br />
<br />
Is this a known issue with the keyboard hardware, or should I be looking into software configs or firmware?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PBP does not power on (or only 1 in 10 times)]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19708</link>
			<pubDate>Mon, 24 Feb 2025 21:15:40 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=23439">zkajdan</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19708</guid>
			<description><![CDATA[Hi,<br />
<br />
I have a PBP which when I press the power button, powers on about 1 in 10 times. Otherwise, the power light does not come on.<br />
<br />
Has anyone encountered this? What could I do?<br />
<br />
One thing I noticed is that successes and failures seem to appear in a row, e.g., 9 failures - 3 successes - 6 failures...<br />
Also, it seems like when it had been powered off for some minutes, it always starts with a series of failures - as if it had to "warm up" somehow?<br />
(Of course, that may be nonsense, it but wanted to mention just in case it is not :-))<br />
<br />
Many thanks for any hints!!]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
I have a PBP which when I press the power button, powers on about 1 in 10 times. Otherwise, the power light does not come on.<br />
<br />
Has anyone encountered this? What could I do?<br />
<br />
One thing I noticed is that successes and failures seem to appear in a row, e.g., 9 failures - 3 successes - 6 failures...<br />
Also, it seems like when it had been powered off for some minutes, it always starts with a series of failures - as if it had to "warm up" somehow?<br />
(Of course, that may be nonsense, it but wanted to mention just in case it is not :-))<br />
<br />
Many thanks for any hints!!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[PBP does not start from postmarket OS image burnt to sd card]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19701</link>
			<pubDate>Wed, 19 Feb 2025 18:45:15 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=23439">zkajdan</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19701</guid>
			<description><![CDATA[Hi,<br />
<br />
I have burnt the latest stable PBP image to an sd card, but after insertion and booting the display stays black (even though the light is on).<br />
<br />
The output of lsblk (on my laptop) looks like<br />
<br />
```<br />
mmcblk0                                      179:0    0  29.5G  0 disk  <br />
├─mmcblk0p1                                  179:1    0  228M  0 part  <br />
└─mmcblk0p2                                  179:2    0  4.1G  0 part  /run/media/key/pmOS_root<br />
```<br />
<br />
which could be a problem maybe - there is no boot partition on mmcblk0p1 (I remember there was when recently I had flashed a manjaro image...)?<br />
<br />
BTW for burning to sd I used the standard command,<br />
<br />
```<br />
dd if=some.img of=/dev/mmcblk0 bs=4M status=progress<br />
<br />
```<br />
<br />
It would be awesome if someone could help!! Thanks!]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
I have burnt the latest stable PBP image to an sd card, but after insertion and booting the display stays black (even though the light is on).<br />
<br />
The output of lsblk (on my laptop) looks like<br />
<br />
```<br />
mmcblk0                                      179:0    0  29.5G  0 disk  <br />
├─mmcblk0p1                                  179:1    0  228M  0 part  <br />
└─mmcblk0p2                                  179:2    0  4.1G  0 part  /run/media/key/pmOS_root<br />
```<br />
<br />
which could be a problem maybe - there is no boot partition on mmcblk0p1 (I remember there was when recently I had flashed a manjaro image...)?<br />
<br />
BTW for burning to sd I used the standard command,<br />
<br />
```<br />
dd if=some.img of=/dev/mmcblk0 bs=4M status=progress<br />
<br />
```<br />
<br />
It would be awesome if someone could help!! Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Doing a fresh install]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19663</link>
			<pubDate>Sun, 02 Feb 2025 18:31:22 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28921">docFarto</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19663</guid>
			<description><![CDATA[My friend gave me their old Pinebook Pro 14" after not using it very much.<br />
They do not remember the password, so I would like to put a fresh install onto it.<br />
They got this one in 2022 I believe.<br />
<br />
I have a couple of questions I have not able find answers to on the forums.<br />
firstly I have seen this: <a href="https://wiki.pine64.org/wiki/Pinebook_Software_Releases#Factory_Restore_KDE_Neon_Community_Build_Image_.5BmicroSD_to_eMMC.5D_.5B20181028.5D" target="_blank" rel="noopener" class="mycode_url">https://wiki.pine64.org/wiki/Pinebook_So...0181028.5D</a><br />
<br />
but I am not sure what the standard OS on pinebook is. I do not want to do anything fancy just get the original OS and flash it on.<br />
So what is the standard OS for the Pinebook Pro?<br />
<br />
Also is flashing that OS on through micro SD the best method for a fresh install.<br />
<br />
Thanks for reading, any help is appreciated!]]></description>
			<content:encoded><![CDATA[My friend gave me their old Pinebook Pro 14" after not using it very much.<br />
They do not remember the password, so I would like to put a fresh install onto it.<br />
They got this one in 2022 I believe.<br />
<br />
I have a couple of questions I have not able find answers to on the forums.<br />
firstly I have seen this: <a href="https://wiki.pine64.org/wiki/Pinebook_Software_Releases#Factory_Restore_KDE_Neon_Community_Build_Image_.5BmicroSD_to_eMMC.5D_.5B20181028.5D" target="_blank" rel="noopener" class="mycode_url">https://wiki.pine64.org/wiki/Pinebook_So...0181028.5D</a><br />
<br />
but I am not sure what the standard OS on pinebook is. I do not want to do anything fancy just get the original OS and flash it on.<br />
So what is the standard OS for the Pinebook Pro?<br />
<br />
Also is flashing that OS on through micro SD the best method for a fresh install.<br />
<br />
Thanks for reading, any help is appreciated!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[pbp with manjaro arm seems to not find any hardware[no wifi, blutooth or battery]]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19653</link>
			<pubDate>Thu, 30 Jan 2025 07:49:09 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28729">frank_philip</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19653</guid>
			<description><![CDATA[I decided to try with manjaro arm again. I've got it running but recently my device seems to be unable to most needed hardware. It seems to think it has no wifi, or blutooth and I can't see the battery status(seems to think it's always on wired power)<br />
<br />
<br />
Has anyone encountered this issue before? I've currently got this issue when I boot from sd card(with Manjaro-ARM-gnome-pbpro-23.02) or from the emmc.]]></description>
			<content:encoded><![CDATA[I decided to try with manjaro arm again. I've got it running but recently my device seems to be unable to most needed hardware. It seems to think it has no wifi, or blutooth and I can't see the battery status(seems to think it's always on wired power)<br />
<br />
<br />
Has anyone encountered this issue before? I've currently got this issue when I boot from sd card(with Manjaro-ARM-gnome-pbpro-23.02) or from the emmc.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[new manjaro install: wlan0 stuck in setting network address]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19650</link>
			<pubDate>Tue, 28 Jan 2025 17:50:17 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=23439">zkajdan</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19650</guid>
			<description><![CDATA[Hi,<br />
<br />
I am following this post:<br />
<br />
<a href="https://forum.pine64.org/showthread.php?tid=10403" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=10403</a><br />
<br />
to install current Manjaro on the ponebook. So far, I have successfully installed Manjaro 23.02 on the sd card. <br />
But from the new sd card installation, I cannot use wifi to download an image for the emmc install:<br />
wlan0 is forever hanging in "connecting"/"setting network address".<br />
<br />
ip link shows the interface as dormant. NetworkManager is running, and the nameserver setting is correct in /etc/resolv.conf. I can also ping the nameserver.<br />
But ip route does not return anything.<br />
<br />
Would anyone have an idea what is going wrong? Many thanks in advance!!]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
I am following this post:<br />
<br />
<a href="https://forum.pine64.org/showthread.php?tid=10403" target="_blank" rel="noopener" class="mycode_url">https://forum.pine64.org/showthread.php?tid=10403</a><br />
<br />
to install current Manjaro on the ponebook. So far, I have successfully installed Manjaro 23.02 on the sd card. <br />
But from the new sd card installation, I cannot use wifi to download an image for the emmc install:<br />
wlan0 is forever hanging in "connecting"/"setting network address".<br />
<br />
ip link shows the interface as dormant. NetworkManager is running, and the nameserver setting is correct in /etc/resolv.conf. I can also ping the nameserver.<br />
But ip route does not return anything.<br />
<br />
Would anyone have an idea what is going wrong? Many thanks in advance!!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Improved battery life with TLP daemon]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19593</link>
			<pubDate>Mon, 30 Dec 2024 13:46:15 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=8488">Surehand53</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19593</guid>
			<description><![CDATA[In one of the recent Manjaro system updates <span style="font-weight: bold;" class="mycode_b">TLP</span> was mentioned as an option to <span style="font-weight: bold;" class="mycode_b">p</span><span style="font-weight: bold;" class="mycode_b">ower-pr</span><span style="font-weight: bold;" class="mycode_b">ofiles-dae</span><span style="font-weight: bold;" class="mycode_b">mon</span> to manage battery life for the Pinebook Pro.<br />
<br />
On the Pinebook Pro the TLP power management gives subjectively better battery performance over power-profiles-daemon. Especially sleep lasts over night without problems. My PBP is one of the earliest (second batch, I believe) and yet with TLP the battery performance is great.<br />
<br />
The downside is that the PBP user interface feels slightly more sluggish in KDE Plasma. Everything seems to be a bit slower than it used to be. This might be different in a simpler (tiling) window manager. The TLP documentation mentions that their power management suits light users best (writing, etc).<br />
However, the battery performance feels much improved.<br />
<br />
If you are interested:<br />
<br />
## Install TLP<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo pacman -S tlp</code></div></div><br />
<br />
You will be asked to uninstall **power-profiles-daemon**, say yes.<br />
<br />
There is an additional package `tlp-rdw`, check in the docu if you want that.<br />
<br />
To enable the service use (and reboot)<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo systemctl enable tlp.service</code></div></div><br />
## Config<br />
I have used this config change to improve performance when power is plugged in:<br />
Edit <span style="font-weight: bold;" class="mycode_b">/etc/tlp.conf</span> and un-comment and update:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">CPU_ENERGY_PERF_POLICY_ON_AC=performance</span><br />
<br />
You can check the config with: <br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>tlp-stat --config<br />
tlp-stat -p<br />
tlp-stat -p -v</code></div></div><br />
<br />
If you want you can set `<span style="font-weight: bold;" class="mycode_b">CPU_ENERGY_PERF_POLICY_ON_BAT</span>` to `<span style="font-weight: bold;" class="mycode_b">performance</span>` as well.<br />
<br />
Here is a link to the TLP <a href="https://linrunner.de/tlp/index.html" target="_blank" rel="noopener" class="mycode_url">documentation</a><br />
<br />
# power-profiles-daemon<br />
To switch back to the **power-profiles-daemon**:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo pacman -S power-profiles-daemon<br />
&#36; sudo systemctl enable power-profiles-daemon</code></div></div><br />
<a href="https://linuxconfig.org/how-to-manage-power-profiles-over-d-bus-with-power-profiles-daemon-on-linux" target="_blank" rel="noopener" class="mycode_url">And here is the link to some power-profiles-daemon documentation</a>]]></description>
			<content:encoded><![CDATA[In one of the recent Manjaro system updates <span style="font-weight: bold;" class="mycode_b">TLP</span> was mentioned as an option to <span style="font-weight: bold;" class="mycode_b">p</span><span style="font-weight: bold;" class="mycode_b">ower-pr</span><span style="font-weight: bold;" class="mycode_b">ofiles-dae</span><span style="font-weight: bold;" class="mycode_b">mon</span> to manage battery life for the Pinebook Pro.<br />
<br />
On the Pinebook Pro the TLP power management gives subjectively better battery performance over power-profiles-daemon. Especially sleep lasts over night without problems. My PBP is one of the earliest (second batch, I believe) and yet with TLP the battery performance is great.<br />
<br />
The downside is that the PBP user interface feels slightly more sluggish in KDE Plasma. Everything seems to be a bit slower than it used to be. This might be different in a simpler (tiling) window manager. The TLP documentation mentions that their power management suits light users best (writing, etc).<br />
However, the battery performance feels much improved.<br />
<br />
If you are interested:<br />
<br />
## Install TLP<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo pacman -S tlp</code></div></div><br />
<br />
You will be asked to uninstall **power-profiles-daemon**, say yes.<br />
<br />
There is an additional package `tlp-rdw`, check in the docu if you want that.<br />
<br />
To enable the service use (and reboot)<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo systemctl enable tlp.service</code></div></div><br />
## Config<br />
I have used this config change to improve performance when power is plugged in:<br />
Edit <span style="font-weight: bold;" class="mycode_b">/etc/tlp.conf</span> and un-comment and update:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">CPU_ENERGY_PERF_POLICY_ON_AC=performance</span><br />
<br />
You can check the config with: <br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>tlp-stat --config<br />
tlp-stat -p<br />
tlp-stat -p -v</code></div></div><br />
<br />
If you want you can set `<span style="font-weight: bold;" class="mycode_b">CPU_ENERGY_PERF_POLICY_ON_BAT</span>` to `<span style="font-weight: bold;" class="mycode_b">performance</span>` as well.<br />
<br />
Here is a link to the TLP <a href="https://linrunner.de/tlp/index.html" target="_blank" rel="noopener" class="mycode_url">documentation</a><br />
<br />
# power-profiles-daemon<br />
To switch back to the **power-profiles-daemon**:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>&#36; sudo pacman -S power-profiles-daemon<br />
&#36; sudo systemctl enable power-profiles-daemon</code></div></div><br />
<a href="https://linuxconfig.org/how-to-manage-power-profiles-over-d-bus-with-power-profiles-daemon-on-linux" target="_blank" rel="noopener" class="mycode_url">And here is the link to some power-profiles-daemon documentation</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[What's a good image to use now? [tutorial help as well]]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19568</link>
			<pubDate>Mon, 16 Dec 2024 11:09:20 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28729">frank_philip</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19568</guid>
			<description><![CDATA[I'm trying to get my pinebook pro up and running again. What's a good OS to put on it now? Can someone also recommend a video tutorial for how to put a new OS on the pinebook pro?]]></description>
			<content:encoded><![CDATA[I'm trying to get my pinebook pro up and running again. What's a good OS to put on it now? Can someone also recommend a video tutorial for how to put a new OS on the pinebook pro?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Void Linux: missing firmware from pinebookpro-firmware?]]></title>
			<link>https://forum.pine64.org/showthread.php?tid=19567</link>
			<pubDate>Sun, 15 Dec 2024 19:58:29 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forum.pine64.org/member.php?action=profile&uid=28757">remph</a>]]></dc:creator>
			<guid isPermaLink="false">https://forum.pine64.org/showthread.php?tid=19567</guid>
			<description><![CDATA[I'm running Void on my pbp, which currently is working fine, but during installation wifi didn't work, and `ip a` said that wlan0 didn't exist at all, and the privacy switches didn't help. The unbind/bind trick:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind &lt;&lt;&lt; 'fe310000.mmc'</code></div></div>complained through dmesg of error -2 when looking for brcm/brcmfmac43455-sdio, which indeed didn't exist, so I copied it over from the stock Manjaro install on the eMMC (here eMMC is mounted under `/run/mount/manjaro' and void SD card is mounted under `/run/mount/void'):<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>cd /run/mount/manjaro/<br />
cp --parents -Pvt ../void/ lib/firmware/{brcm/brcmfmac43455-sdio.{bin,clm_blob,'pine64,pinebook-pro.txt'},cypress/cyfmac43455.*}</code></div></div>Now it works. Should those files be in pinebookpro-firmware?]]></description>
			<content:encoded><![CDATA[I'm running Void on my pbp, which currently is working fine, but during installation wifi didn't work, and `ip a` said that wlan0 didn't exist at all, and the privacy switches didn't help. The unbind/bind trick:<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>sudo tee /sys/bus/platform/drivers/dwmmc_rockchip/{un,}bind &lt;&lt;&lt; 'fe310000.mmc'</code></div></div>complained through dmesg of error -2 when looking for brcm/brcmfmac43455-sdio, which indeed didn't exist, so I copied it over from the stock Manjaro install on the eMMC (here eMMC is mounted under `/run/mount/manjaro' and void SD card is mounted under `/run/mount/void'):<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>cd /run/mount/manjaro/<br />
cp --parents -Pvt ../void/ lib/firmware/{brcm/brcmfmac43455-sdio.{bin,clm_blob,'pine64,pinebook-pro.txt'},cypress/cyfmac43455.*}</code></div></div>Now it works. Should those files be in pinebookpro-firmware?]]></content:encoded>
		</item>
	</channel>
</rss>