I wonder if I should update my Arch installation.  It's been running for a tear and I havn't updated anything.  I'm afraid to do so because I'm afraid something will break and the phone/cpu will become unusable.
I'm sure I'm in over my head with Arch Linux, but this is what I'm stuck with.

QuickJS is a small JavaScript Engine that supports POSIX Functions. Can we run QuickJS on Apache NuttX RTOS? And Blink the LED in 4 lines of JavaScript?

  const ULEDIOC_SETALL = 0x1d03;
  const fd = os.open("/dev/userleds", os.O_WRONLY);
  os.ioctl(fd, ULEDIOC_SETALL, 1);
  os.ioctl(fd, ULEDIOC_SETALL, 0);

In this article we…
(1) Run QuickJS on NuttX with Ox64 BL808 RISC-V SBC
(2) Blink the LED by adding the ioctl() function
(3) Reconfigure the NuttX App Stack (because it’s too tiny)
(4) Analyse the Memory Footprint of QuickJS (Code + Data + Heap Size)
(5) Test QuickJS in the Web Browser with NuttX Emulator (and a Simulated LED)

QuickJS is perfect for Iterative, Interactive Experiments on NuttX! Check out the article:
https://lupyuen.codeberg.page/articles/quickjs.html

Lup


   

I have a good understanding of computer technology but in recent years find myself moving towards near complete digital detox, I think there is far too much waved connection.

I run a Mudita Pure e-ink dumb phone which works as a modem and a rooted & degoogled Onyx Boox Note Air 2 Plus for everything else, at least that is the idea. The privatized Boox tablet firmware (controversial because of GPL) has proved a nuisance and thus I find myself using the linux laptop I intend to sell. 

I like a rough, physical, healthy lifestyle, so to compliment it, I would like a rugged / metal Pinenote to work in tandem with a simple phone. Also, my opinion is that a colour e-ink display option would allow for a better multi-purpose device, I have had trouble reading backroad / topographic map-books in grayscale, and colour is helpful for the odd online purchase as well.

Simple e-ink devices seem to me a better path or at least compromise in the balance of things.

So, my take:

• Rugged & metal
  
• Optional colour display
  
• Not too big
  

o Signal for Pinefon is 'signal-desktop_6.44.1_arm64.deb' at Gitlab (Requires
  Signal on your android)...

    - https://gitlab.com/undef1/signal-desktop...s/22135879

Download both files (?.deb and ?.deb.sig) in same dir. Click on the ^ next
to the getlab .deb file and get the check sum. Go to that download dir and
check signature w/...

>sha256sum signal-desktop_6.44.1_arm64.deb
Output: long number
Check long number against the check sum

o  Install...

      >dpkg -i signal-desktop_6.44.1_arm64.deb

-wigan-

I'm looking for the specification for the ribbon cable connecting the track pad to the main board connector. I have a Pinebook Pro that I picked up that does not have the ribbon cable for the track pad on it. Is there anyone who happens to know the specifications? (i.e number of pins, width, etc) Many thanks for any help.

The Quectel modem EG25GGBR07A08M2G of a recently (January 2024) purchased PinePhone Pro Explorer Edition became non-functional after an attempt to replace its firmware with the community one:

https://wiki.pine64.org/wiki/PinePhone#Firmware_update

The described process with the fwupd (0.7.2 is the latest version available there) on Mobian 12 ended up with the modem stably disappeared from the system, without returning back after rebooting or un-/re-powering the device. The recipes from the community repository helped to boot the modem in the QDL mode and flash it again - but it doesn't function any more: it is visible to the system and is generally responding to the AT interface, but it can't be enabled. In particular, some of the AT commands fail - e.g. it is impossible to return IMEI or SN. This seems regardless of firmware: the latest (0.7.4) community version and all the stock versions from the recovery repository were tried with the same result.

So the questions I have:

1. What is the exact version of the stock firmware for the Quectel EG25GGBR07A08M2G modem which the PPP Explorer Edition are being shipped with today?
   
2. Is there any further way to diagnose and fix the issue?
   

I ordered this replacement battery for my Pinebook Pro and it won't charge. The laptop will power on with the new battery, the OS correctly identifies when it's plugged in, but the charge light blinks red and the charger (USB-C or barrel) doesn't draw any discernible power from the wall. Charging works as expected with the old battery plugged back in.

I notice that the old battery has a white wire in the center of the connector, while the new one does not. The second suspect thing is that the new battery is 33g lighter than the old.

Any thoughts on this? Does this missing white wire indicate a problem was inevitable, or could I have just gotten a bad battery? I have sent a message to the seller but haven't heard back yet.


Thank you!

Every day we’re auto-building Apache NuttX RTOS for Ox64 BL808 RISC-V SBC... Can we test NuttX on Ox64 automatically after building?

Yes we can! With a little help from the Ox64 BL808 Emulator that we created last week. In this article, we fill in the missing pieces of our Ox64 Emulator and run it for Automated Testing...

(1) Booting NuttX RTOS in Supervisor Mode (instead of Machine Mode)
(2) Emulate OpenSBI for setting the System Timer
(3) Emulate the UART Interrupts for Console Input
(4) Execute everything with Expect Scripting (based on TCL)
(5) Which becomes our Daily Automated Testing (triggered every day by GitHub Actions)

Here's the article:

Automated Testing with Ox64 BL808 Emulator (Apache NuttX RTOS)

Lup

   

Is anyone else having an issue with the Pinebook Pro with Debian 12 installed draining battery even when powered off.  In order to keep it charged I must keep it plugged into the USB Type C charger.

What is the state of USB Type C DiplayPort out on Debian 12 for the Pinebook Pro?  It seems like all the required kernel modules are loading, but it doesn't work.  Is this a Debian 12 kernel issue or a U-Boot Issue?