After performing a reboot my date is wrong stucked at august 27th, I must fixed it every time using 'date --set'
I started having this issue today.

Hello

Yesterday I noticed that the Gnome Document Viewer disappeared, I tried to reinstall it (sudo apt install evince) without success. It depends on the package libgnome-desktop-3-19 which cannot be installed. Am I missing something obvious? I assume that I'll have to wait for a fix.

Hello,
I'm using Mobian bookworm since a long time now.
Since last update the Wifi has been broken and I can't connect to my AP. So I can't update.
Also I've had tons of held back package updates since a long time.
I'm thinking about reinstalling the whole OS from scratch but I would like to keep my data.
Do we have a guide on this?
Thank you.

I just saw this, apple is going to have what looks to be a globalstar(for the size etc I suspect it is the L-band slow data uplink monoplex service), you apparently need to aim as there is no way to get a good gain on-band antenna inside a skinny phone
https://mobile.slashdot.org/story/22/09/...rgency-sos
We could easily beat them by releasing even a limited run exposition prototype with a globalstar $100 data module integrated into a Pinephone back cover using the pogo pins.
Maybe this is is the TU-144 vs the Concord thinking but we could and should beat them, SPOT messenger has been around for maybe ten years already, this is not new ground except integrating with a mobile phone.
I suppose it is the cool factor and being better than crap brands but I cant watch apple be the only one selling satcom on their phones.
Someone get one of these and a pogo pin ribbon and post it on Hackaday.com
https://www.globalstar.com/en-us/products/iot/stingr
they are still available just not direct from globalstar.

Hi,

Has anyone installed a Pine64-supplied eMMC module on a Rockpro64?

  SKU: 64G eMMC (SDINBDA4-64G) mmc 5.1

I bought one because my older eMMC modules are unreliable:

  SKU: "Sandisk: 64G mmc 4.5

I can't get the Pine64-supplied (mmc 5.1) module to work, so Pine64 support kindly send me a replacement part in case the one they first sent was faulty. However, neither of them work and it is very difficult to even detect them in uBoot unless I do a cold-start, but they stop working as soon as I try to write to them. Most recently, I tested them by booting the latest Manjaro for the Rockpro64 from SD, which has the latest uBoot for the Rockpro64. Unfortunately, this made no difference at all (previously, I was using Debian to run OMV from SD card, but I want to run it from eMMC.

If you've had success using any eMMC module on the Rockpro64, please let me know the SKU and where you got it from.

Thanks,

  Tony.

Hey pinefriends! This is my first post. 


I got my Pinephone Pro Explorer Edition in the mail a couple days ago. I've installed Tow-Boot, Mobian Phosh, and the 0.6.8 firmware update for the modem. I did this via the 'firmware' app from the software center. Currently I have an AT&T SIM card in the phone but plan to switch to Google-Fi before long. Almost every time the screen turns off I completely loose LTE such that the mobile connection section of the settings app disappears. It also happens, much more rarely, in the middle of actively using the phone. It's happened while writing a text message, while browsing on firefox, and even just while scrolling through the apps section. It does not loose it's connection to WiFi when this happens, so I know it's not the whole modem shutting off. Before updating the EG25 firmware I had to reboot the phone each time this happened. Now it consistently reappears when I enter the network settings and start the process of creating a new wired connection. 

  https://forum.pine64.org/showthread.php?tid=14342  --this thread gave me the idea to try systemctl edit --full ModemManager to change --test-quick-suspend-resume to --test-no-suspend-resume

I didn't see that line or anything like it in the file that was opened. 

Please if anyone knows why this is happening or has advice on how to fix it that would be lovely. It's really the main thing standing between me and PPP as a daily driver.

Thanks to whoever increased my rank to Adept, but I think you might be mistaken,, To those who have read my posts, and everyone else as well,  I used to patch program in Fortran 4 and 77 and plain "C".  I have lots of general engineering knowledge but absolutely none of the skills needed to develop firmware for Pine64 devices.  Please consider my rants to be questions about reliability and ease of use-- basic design and engineering concerns.  My only software concerns revolve around Pine64's apparent unwillingness to provide, out of the box a, basic and reliable boot firmware for each of their devices so that those of us who are less adept at machine language will have a reliable starting point at which to aim our porting efforts. As an example, the mess that Manjaro has made of the uboot which is a part of the system supplied on the Pinebook Pro and which is making a nightmare for those of us who want to run literally anything else.  I'm simply not adept enough to get that deep into hardware.  Please call me a rank amateur, a simpleton, even a crank if you  wish, but fix this problem!

Hi
I have RISC OS up and running on the pbp. It is essentially bare metal, and I am having some issues with reliable clocking at higher speeds
I note many reporting that they are running A72 at 1.8GHz + ,and at the expected voltages in in u-boot. Would someone please report a bit of info for me from a working machine. I need the contents of the CRU module. This is at a physical address of 0xff760000, and I need the dump from (ideally) 0xff760000 to ff760500. If that isnt possibly I at least need to know the content of 0xff760020, 0xff760024, 0xff760108 and 0xff76010c

This should provide a sanity check here. I think I'm setting all I need, but suspect there is just something I have missed.
Any help here would be appreciated.
Thanks
John

After the last update, I can't send new messages on chatty. The "+" button is gray and can't be clicked.

after todays update it was solved

Hi,

I have a weird issue with the linux console.  I am trying to setup a rockpro64 and in doing that I am using an old Dell monitor with a 1680x1050 resolution.

When the rockpro64 boots, the first thing that I see is the output from uboot. This is OK. Then linux is booted and for a short time I see a patterned screen. After this, there is the linux boot output.

The issue is that as soon as uboot gives control to the linux kernel, the display becomes terrible: all trembling and slightly distorted. The monitor reports that the output is at 1400x1050@55Hz, which is obviously not correct. However, /sys/class/graphics/fb0/modes correctly shows U:1680x1050p-0.

Obviously, I suspect that the poor display is due to using an output format that is not suited for the monitor. However:

• Why does uboot pick the right display mode and linux does not?
  
• What would be the proper way to instruct linux to use a more correct display mode for its console?