Hello

I'm unable to bring up the modem, restarting eg25-manager has no effect, I have no longer any prompt to enter my PIN code. This problem appeared last week on my very first Pinephone which is two years old, the operating system is up-to-date (bookworm). I'm completely stuck as my second Pinephone doesn't work too

I tried:
sudo systemctl restart eg25-manager
mmcli -S

Do you have a suggestion?

When using netfilter on the latest manjaro for example, via wg-quick, it produces an error

I have a PinePhone Beta Edition which doesn't show any signs of even starting to boot (no LEDs and no output on the serial port). It did work for a couple of weeks when it was new, and I'm not exactly sure what has changed. (To be honest, I've been focused on other projects, so it's been in a drawer for many months, but I wouldn't have expected that to cause anything more dramatic than the battery draining.)

I'm using the USB to serial/3.5mm adapter purchased from pine64 (CH340) and dip switch 6 is off. PuTTY or minicom will connect to /dev/usbTTY0 at 115200 8N1 but I get no activity in the terminal at all while attempting to start the phone.

The only signs of life from the phone are:

• When I connect it to PinePower's USB-C PD port, the display shows a voltage of 5.0V (but 0.0A drawn), so the USB power pins can complete a circuit in some form
  
• The green LED in the USB connector of the UART adapter cable stays on while the plug is connected to the phone's audio jack
  
• When I hold the phone's power button for about a second, the green LED blinks once, as if some data were briefly transmitted (but nothing appears in the terminal)
  

• Booting with no SD card
  
• Rewriting the SD card with Jumpdrive, Jumpdrive charging, and various other things like the 17-OS image
  
• Booting with and without the battery in
  
• Fully charging the battery using the external charger (which gives a green LED after a couple hours of charging, so as best I can tell the battery is fine)
  
• Twiddling the other dip switches (in case one of the other components were somehow unhappy enough to inhibit boot?)
  

Look yo! I'm not a tech savy guy, get turned into Linux/unbuntu through a tech wizard buddy, I don't care for windows, I would just like to point out or ask the people that run the pinephone64 website, to put clearly on top of the page, big bold letters what carriers this phone works/compatible with, for not tech savy folks like me!? Like why would you not do that!? Your selling a phone, carriers a pretty important, unless it don't work with none, I could understand Linux, not working with others, I've had, unbuntu a long time, and that's been a struggle with programs over the years!! Unbuntu

Dear all,

I've gotten my hands on a new Pinebook Pro with the pre-installed Manjaro ARM recently. I've been working on it for a few days now and it suits my needs very well.

However, occasionally (I haven't managed to figure out a pattern yet), the laptop starts making weird noises: either a fairly loud "knack" (as if someone closed the lid with force) or a longer higher pitched tone which ends with a "knack". Then I can go on working on the machine for e.g. 20 minutes without any issues until all of a sudden it again makes one of the noises described above.

1. Is/has anyone encountering/encountered the same phenomenon? If this is a known issue, is there a fix for that?
2. Is this software or hardware related? What information do you need from me to evaluate that/narrow down the problem?

In the end I need to know, whether I can fix this myself or whether I need to file a warranty case with PINE.

Thanks in advance for your help!

Hi all,

Put together my new PBP (running Manjaro / XFCE, u-boot is 2022.04-4), NVME-adapter and an Intel 660p 1TB SSD. Drive turned up, partitioning and formatting went fine, started copying data - and suddenly the drive vanished. Was running out of battery (maybe that caused the drive to vanish?), fiddled around some days, connected the original power adapter, drive turned up again.

The second time I wasn't that lucky. Copied data, turned the PBP off - and after starting it again, the drive didn't turn up anymore. Basically I have the same problem as described here . But the solution mentioned (flashing a certain boot loader into SPI), doesn't work for me. As the thread is already 2 years old - has anyone run into this problem recently?

`lspci` lists the controller:

• Several different power supplies.
  
• Fiddling around and reconnecting the drive, adapter board and cable.
  
• Booting from SD-card: Some thread mentioned it would help, but got the same behaviour as described above.
  
• Adding `nvme_core.default_ps_max_latency_us=0` to `/boot/extlinux/extlinux.conf` - no change (see this thread )
  
• Ensuring max_link_speed is 1 in device tree.
  
• Putting the SSD into a USB-adapter - turned up, no problems (on my PBP).
  
• Searching the net. The issue turns up with other notebooks and discs too - but never a proper solution is described.
  

• Are there any new insights into this issue?
  
• Is the Intel 660p really working flawlessly for everyone else but me?
  
• If you ran into these problems with a recent PBP / OS (2022) - what worked for you?
  
• Any information I could provide to solve this?
  

Hello

My very first Pinephone became almost unusable a few days ago, some parts of the touchscreen no longer worked, I had to use a second Pinephone left as is, bought 2 years ago with Manjaro ARM KDE (Plasma Mobile) installed by default.

At first, I quickly realized that the battery couldn't be recharged. I tried to recharge it for hours but I had to use the battery of my first Pinephone to be able to power it on anew.

Secondly, I had no mobile data whereas my mobile operator is the biggest one in France and I was very surprised because I had mobile data support two years earlier with Manjaro and Phosh. I could call but the dialer was broken, I often had to reboot to make it work anew, I couldn't press keys during calls for audiotel systems (i.e "Press zero to choose this option" etc). The SMS barely worked, there was a problem of refresh, I had to restart Spacebar to see them. When I was receiving a call, sometimes it didn't ring, I only saw the dialog with "Accept" and "Decline" buttons. It was impossible to select a language for the system, I was stuck with American English (which is obviously not my mother tongue).

Thirdly, I tried to perform the system upgrade by using the GUI but after hours, the tasks remained stuck at 50% and then it complained about a corrupted package. Retrying gave the same result.

Fourthly, I tried to do it in command line with pacman, it started well but I got a black screen with a message talking about a broken session manager that became unreadable after a rotation of the screen. When rebooting, I just saw the KDE logo and it didn't go any further.

As it's Sunday, I can't buy a microSD card, nobody can contact me. The only suggested solution consists in buying one, which I will do tomorrow in order to install Tow-Boot and probably install a working Linux distribution. If anybody has a better suggestion in the meantime, it will be very welcome.

By the way, it's better than nothing, the first time I used a Pinephone, it was unable to boot whereas this second Pinephone was able to do a very few things.

Quote:[alarm@pinephone ~]$ sudo pacman -S vim
[sudo] password for alarm:
resolving dependencies...
looking for conflicting packages...

Packages (2) vim-runtime-9.0.0000-1  vim-9.0.0000-1

Total Download Size:    8.01 MiB
Total Installed Size:  37.94 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
vim-runtime-9.0.0000-1-aarch64.pkg.tar.xz failed to download
Total (1/2)            8.0 MiB  8.05 MiB/s 00:01 [######################] 100%
error: failed retrieving file 'vim-runtime-9.0.0000-1-aarch64.pkg.tar.xz' from mirror.archlinuxarm.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Hello

Bought new Pinebook Pro, while updating I logged out and crashed login window theme software, I type the password and then it logs me in then logs me out back to login window, so to reinstall Manjaro I burned Manjaro on SD card and booted from that successfully. Manjaro installed itself on another partiton on SD card rather than eMMC, I then followed some tutorial and used a command to install Manjaroo in eMMC while running from SD card, Now I boot into uboot, some text shows up and now it wont boot from from neither SD card like it used to be able to, and not from USB drive. I used Balena etcher on ubuntu to burn the images on SD card and USB drive but both are not booting.

What shall I do to install Manajaroo in eMMC? I used to be able to boot from SD card using  Manjaro-ARM-kde-plasma-pbpro-22.12.img but not anymore. Now it just loads uboot and then goes to black screen forever.

Thanks in advance.

I have a PineBook14 forgotten in a cabinet, which could work quite well, but is actually unusable because of broken case. Screwset fixing screen hinges to the bottom case are all broken, so it is very hard to open it and keep in position.

I would really like to restore it in some way. Few years ago I asked to the support if it is possible to get the spare, but it was't. Now I asked to the sales, and I am waiting for an answer.

Anyone with the same problem have found an alternative solution?

PS: I am quite happy of this device, even if, with hindsight, I would have been taken the 11 version! If anyone have one to sell, I would evaluate this choice.