Hi there,

after running quite smoothly for several years, since the upgrade to Debian trixie, my ROCKPro64 has become quite unstable.

I am using a JMicron Technology Corp. JMB58x AHCI SATA controller in the PCIe slot. The first symptom I had was that after the reboot after the upgrade, the status LEDs on the controller did not turn on. I connected a monitor on HDMI and there was no signal.

I have now advanced a couple iterations of debugging and here is what I have.

If the PCIe card is in, I get panics related to PCIe, such as:

hi, ive got a new unused pp keyboard case and LoRa backplate listed on ebay right now, you can find them by simple
search, they are only available through this auction btw... just spreading the word. thanks

PinePhone 16 GB – Free to a Good Home

I’m giving away a PinePhone (16 GB) that I no longer need.

If you can pick it up in Bonn, Germany, or send me 20 euros via PayPal (assuming that’s enough to cover shipping to your location), it’s yours.

Included:

• a cracked but still sort of functional screen
  
• an extra replacement screen for repairing the phone
  
• no battery
  
• a cracked back cover (still usable, though a piece between the buttons is missing) with a Debian logo
  
• a yellowed & unsightly, transparent rubber protective case
  
• no warranty of any kind
  

As the device was officially discontinued, it would be interesting to know the user base's size: is there an information on the amount of units delivered since it was announced, on October 15, 2021? 

Are there any estimates towards the amount of "active" users?

Looks like this has been going on for a while,takingffmpeg components as their own and then releasing on an incompatible Apache license.  This is gonna burn PPpro and Pinetab users I think, guess we will wait and see.
https://github.com/rockchip-linux/mpp
looks like the other repos are up and only media acceleration is DCMA'ed.
https://hackaday.com/2026/01/05/github-d...a-request/
though someone could just fork and re-license correctly I think...

Hello, I just ran`sudo apt update`via ssh on my V2 PineNote and I'm receiving the following warning

Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://pinenote.mweigand.net/repo_pn_stable trixie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E0B6906147A709C6

Hi everyone, I’m experimenting with creating custom watch faces for my PineTime. I noticed that some of my more complex designs seem to drain the battery faster than simpler ones. Has anyone done a detailed comparison of different watch face elements (animations, colors, update rates) and how they impact battery life? I’m curious if there’s a set of “best practices” for designing battery-efficient faces without losing visual appeal.

Hi all,
The Supernote Nomad is a nice bit of hardware with user replaceable battery, memory, case and more.

It also happens to have identical CPU to the PineNote.

Additionally, Supernote has open sourced the U Boot and some other bits.

I unfortunately do not have the skill to attempt to try and flash the new PineNote firmware to it, but it would be very cool to see Debian/Arch running on the Nomad, and I would be willing to contribute toward a bounty to see it happen.

Resources here:
https://github.com/Supernote-Ratta?tab=repositories

I can see a PRCM register for CPU1_PWR_CLAMP that looks relevant for powering up a 2nd core.  But I cant find any info about this, and since it seems to be an 8 bit value I am very relucatant to hack it.  Is it documented anywhere please? or in general the whole 2nd core startup would be useful.  I can take a guess at some of the steps, but it would be nice to follow something official and not melt my chip

So, I bought myself a PineNote like a month ago (my device is a batch 2, I think), and I'm having some issues with the Pinenote Helper extension and Maximized by default extension. 

I recently used a script https://git.sr.ht/~diederik/pinenote-bat...all-fixes/ to upgrade my system (heads up to people, using sudo apt upgrade seems to put the device in a boot loop. I had to re-flash the OS). I don't know if its the script or the upgrades themselves that did this, but the PineNote Helper extension and the Maximized by default extension appear to be completely broken after upgrading. They each give separate warnings inside of the Extension Manager. I tried re-installing the Pinenote Helper extension, but it only added back the display refresh button and nothing else. 

Pinenote Helper error:

Quote:An error has occurred in this extension. This could cause issues elsewhere in the system. It is recommended to turn the extension off until the error is resolved. 


Error details: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UknownMethod:
Unknown method SetNoOffScreen

Quote:The installed version of this extension (1.3.1+pn) is incompatible with the current version of GNOME (48.4). The extension has been disabled.