Hello all.

I was doing some package upgrades on my pinetab2 running danctnix and I started noticing some errors with the shell:

-bash: symbol lookup error: -bash: undefined symbol: rl_completion_rewrite_hook

Recklessly, I rebooted and now I can't log in.

It boots up to the graphical login screen. I authenticate, and something happens and I come back to the graphical login screen.

If I try to log in via ssh, I get the error above.

How can I boot into single user? I'm not finding much.

I'm thinking I should try to boot into single user and try to fix it, but I don't know how.

Any other advice?

Thanks!

I've been distro-hopping and am trying out PostmarketOS 25 with Plasma right now.

It's nice but man is it slow/laggy. Push a button, count out loud 1-1000, 2-1000, 3-1000 and then the action happens.

So far, the only highly-performant current-day distro I have found is PostmarketOS 24 with SXMO de Sway. That's fast, but of course that's not too surprising given that it is running a window manager and not a desktop environment.

What else out of current-day distros run decently? I'd like to try them.

Thanks!

Both cards have some SMS TAN set up, so if my bank needs additional authentication, I should be forwarded via the 3DSecure intermediate to my banks site to enter the security information. But nothing like this happens either.

So, what is wrong? When can I order and pay with credit card? (and not PayPal)?

Browser: Firefox and chromium.

Or, can you make the conversion from USD to EUR? PayPal gets really expensive in doing currency conversions.

irradium - source based Linux distribution CRUX adhering to ideology keep it simple, has its own package system, also supports the port system.

irradium development

packages aarch64
packages riscv64

installation README.TXT
kernel 6.6.88

mirror 1, mirror 2, mirror 3

irradium-3.8-riscv64-core-starpro64-6.6.88-build-20250714.img.zst
irradium-3.8-riscv64-core-starpro64-6.6.88-build-20250714.img.zst.sha256
irradium-3.8-riscv64-xfce-starpro64-6.6.88-build-20250714.img.zst
irradium-3.8-riscv64-xfce-starpro64-6.6.88-build-20250714.img.zst.sha256

I have recently rediscovered my older PBP I think its number 328, hence I am curious what if any preemptive fixes would be advised for such a system and can be done regarding the broken plastic around the ports?

How to donate to the maintainers of DanctNix Arch Linux?

Thanks

I'm having an issue where my PinePhone can use the 4G network for data and SMS/MMS (in/out), but I'm unable to hold a call on the 4G network. Currently the call immediately degrades to the 3G network, and if I force exclusive usage of the 4G network, my calls fail to connect entirely.

Here's my current setup:
PinePhone v1.2b Beta Edition
postmarketOS (systemd; edge release) -- Phosh UI
calls 48.2 (GNOME)
default firmware for the Quectel EG25-G modem (I've not yet tried https://github.com/the-modem-distro/pinephone_modem_sdk).

network: Public Mobile (Canadian subsidiary of TELUS)

I've been following https://pine64.org/documentation/PinePhone/Modem/ to attempt to set up VoLTE.

Using the default profile ROW_Generic_3GPP and subsequently trying the profile Telus-Commercial_DO, I've sent AT commands in this way:

Hi

When is it expected that I can  buy a PineNote Community Edition (Europe)?

Hi all, I’m building a logger platform with the Pine A64 board that collects environmental data from multiple ESP32 modules, and I’m deciding whether to use MQTT over local Wi‑Fi or direct USB/UART communication. I recently found this guide on ESP32 MQTT setup and found it an excellent primer for structuring reliable publishing from sensors:
https://www.theengineeringprojects.com/2...-mqtt.html
I’ve also been exploring how to implement MQTT on ARM boards using Mosquitto on Armbian, and came across a hands-on ESP32 + MQTT + Node-RED sensor dashboard project. My main concern is latency, long-run stability, and ease of integration via UART. Has anyone built a similar real-time logging system on Pine A64 with multiple ESP32s? Which communication method worked best for you in terms of reliability and scalability?

I am at my second PinePhone, the first one having had a hardware failure that made the modem, among other things, inoperable (and the outer parts: screen, case, buttons having been damaged enough to make a mainboard replacement not worthwhile).

So I bought this PinePhone in March 2023 from the EU Store. Sadly, this means that the compulsory EU warranty (2 years) has expired 3-4 months ago. So far, I was happy with it (and the outside is in good condition), but…

I have noticed 2 failures this week – I cannot prove that they happened simultaneously, but the coincidence seems odd:

1. The USB-C port works for charging only. The data lines appear to be completely dead. I first noticed this (a few hours ago) trying to boot into JumpDrive, to connect the PinePhone to my computer (because I wanted to back up and then replace the installed OS through USB, trying to switch from Manjaro ARM stable, last updated over a year ago, to postmarketOS 25.06). There was no way I could get the computer to detect the PinePhone. I tried 2 different cables, 3 different USB-A ports on the computer, rebooting the PinePhone several times and the computer twice, nothing helped. Then I took out the JumpDrive microSD card, booted back into the installed OS, and tried using the "convergence package" dock stick to plug in my (USB-A) notebook mouse. Nothing, no way I could get the PinePhone to see the mouse at all, either. Charging works even through the dock (using its USB-C power input), but nothing else works. One would think that this is clearly a failure of the USB-C daughter board, but…
   
2. The audio jack on the other end of the phone also stopped working. I first noticed that this Thursday. When I try to connect the PinePhone to a hardware audio mixer, or to my small home stereo, it fails to detect that there is anything plugged in and does not produce any audio output. Tried 2 different cables, 2 different ports on the audio mixer, and even another output device (my stereo), nothing worked. This time, at least, there is some output in the journal, but it sounds like a typical "bad contact" on-and-off scenario: Within 1 second, I get around 20 times:
   
   Code:

   Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-in Jul 07 00:11:26 plasma-mobile kernel: jack: irq plug-out
   So, while the PinePhone did detect that something was plugged in, it comes and goes (and comes back and goes again), around 20 times per second.
   

• The WiFi has become much worse at keeping connections alive. Running ping commands (doing a ping every second) either from the PinePhone to somewhere else or from the computer to the PinePhone makes it better, but the WiFi used to work much better even without that workaround.
  
• Bluetooth stopped pairing successfully with one particular audio device (the same hardware audio mixer that I first tried using the audio jack with), but the PinePhone pairs successfully with other Bluetooth devices (at least a small Bluetooth receiver and my computer), and other smartphones pair successfully with the audio device that the PinePhone has trouble with. In the particular pairing that stopped working, I always get the same "br-connection-unknown" error. It used to work fine for months, then suddenly started failing around 2 weeks ago.