Sim card network is registered i cannot make calls modem is enabled

I have been working to get the LCD working on Armbian using the notes here:

https://pine64.org/documentation/Quartz6...I_display/

I was able to make the dtbo file, but the command to update uboot, doesn't work and I can't find a package to install it it. Does anyone have any advice here?

small update. I think that the overlay I built is not compatible with armbian. @CounterPillow made it for mainline and I believe armbian is using BSP. I tried to build with DTC and get errors. I tried to boot a plebian image(older mainline built image), but I can't seem to get them to power up. Will follow up if I make any headway.

I’m new to the PINE64 community and just got my hands on a Pinebook Pro. Super excited to dive into the world of ARM-based Linux laptops, but I’m running into some issues when trying to use an external monitor via USB-C.

I installed Manjaro KDE, which I read is one of the more supported distros for the Pinebook Pro. However, when I connect my USB-C to HDMI adapter, nothing happen - no output, and the display settings don’t seem to recognize the second screen. I’ve checked a few things:

The adapter works fine on another laptop, so it’s not faulty.

Tried different distros (Armbian and Debian) with similar results.

Running xrandr only shows the internal display (eDP-1), no external monitor detected.

Looked at dmesg logs after plugging in the adapter, but I don’t see any clear indication that the system recognizes it.


Does the Pinebook Pro’s USB-C port natively support video output, or does it require extra configuration?

I have flashed multiple distros to my Pinephone many times.  However, now, Etcher is not picking up my Pinephone anymore.  

The jumpdrive is 100% functioning (my Pinephone screen is visibly showing the jumpdrive graphic) but Etcher is still not showing the eMMc option (or whatever its called) in the list.  

Any ideas on what is going on here?  Any solution suggestions?

Recently I updated Mobian to Trixie, followed by updating the kernel from 5.15 to 6.12. Couldn't update the kernel to 6.* earlier because it wouldn't boot, fortunately that issue has been fixed

Unfortunately wifi is broken with kernel 6.12, it can't find rtw88/rtw8703b_fw.bin and rtw88/rtw8703b_wow_fw.bin, boot with kernel 5.15 and wifi works again.

Since 5.15 works, does this mean I'd have to compile my own 6.12 with that firmware put in if I want to use 6.12?

edit: firmware-realtek was missing, apparently a dependency with 6.12.

While using my pbp, it displayed vertical wide grey and white bars covering the screen for a few seconds, display went black and it shut down. It had been pretty stable for quite a while.
Now when i power it on, green light on the keyboard comes on for maybe 10 seconds then goes out, the screen remains black. Anyone dealt with this? I hate to take it apart to blindly start seating cables or whatever since i understand this thing is easy to break and i am somewhat of a klutz. But i would like to get it working again, any suggestion is appreciated.

Hello everone!
I bought a pinecil v2 a few months ago, but I have only needed to use it once since I own it.
Yesterday I wanted to use it again, but I had to found out it don’t power on.
I tried with both barrel jack, and USB-C via 5-12-20V, also from two different cables.
While I hoped its firmware can be updated at least, from my PC, it doesn’t even recognised my device.
When I opened it up, everything looked normal, the joints were fine, nothing blown up.
Personally I’m a plain user not an engineer, though my assumption is that it is completely dead.

I would like to ask, what can I do in this case? Is there anything my attention passed on?
If it’s dead, I have any chance to repair?

Hello everyone,

first I want to phrase the question:
Is it possible to somehow reset the userpassword via setting a boot parameter in uboot to drop into a root shell (without disk encryption this should (?!) be possible in linux via the init=/bin/sh "trick"). I connected via UART and to my pinenote and tried some combinations, setting the bootcmd and others (see https://isc.sans.edu/forums/diary/Resett...ers/28564/).

now the why:

What was bugging me, since I have the pinenote for 2-3 weeks now, is that it crash-reboots at least once in a using session (no heavy actions done (?!): a bit browsing and configuring koreader, xournaling some pdfs, and stuff). I thought, this is because the system is not meant to be stable by now (as far as I understood what I read)  and wasn't yet able to investigate further

Now 2 days ago I apt-upgraded via terminal and the update seemed relatively big (but it was NOT my first time running the os update). The screen froze at 55% - no reaction. I was already fearful because it happened after the downloading/unpacking part and still I powercycled it after 1-2 hours. It didn't boot anymore (it showed a dark version of the image with the squares and it said "booting ...").

I connected UART (thanks so much for delivering the dongle with it!!) and was presented a login.
Ok, what was my root password again? I've set it up a week ago and used it some times. But although I'm 98% sure that I got it right, I was not able to log in.
Ok, I created another user with sudo permissions and because of the many reboots of the pinenote I had to put it in very frequently, so I'm 99,999% sure that I have it right (still there was a slight uncertainty, because the password is somehow bound to the layout of the on-screen-keyboard) - NO, not able to login.
Ok, what was the password of ther originals "user" ... yeah, I'm able to log in ... BUT ... as I created another user I removed sudo group from "user" -.-
Now I'm confused even more - I can see that the user I created really exists in /etc/passwd ... so once again my reality is questioned - why wasn't I able to login?
Did I tried to much and some new PAM restriction is active by default in Trixie? Seems not so. But I remembered the workaround of dropping to a root shell in grub, maybe/hopefully this also works here? But I'm not very proficient with uboot and UART yet.
Alternatively: can I copy the bootmenu file from the pine, change it and put it back?
Maybe there is an even easier option I didn't think of yet, before I have to flash it(?!)

I was looking at the chip in the Ox64 and I think it is kind of interesting that it can do video output. Anyone tried building a watch around it? I like the idea of having a little more hardware capabilities in a watch but I don't care for the "modern" watches. Right now I have a BangleJS 2 and it works ok but the software is unpolished and buggy. Also the battery life isn't great since Javascript adds a lot of overhead. I think it would be cool if there was a watch that could utilize something a little more mainstream like Linux to speed up development. Since the chip has Wifi you could control it via a web server and it could pull down apps and install updates.

This is really just a random thought I had the other day so it is probably flawed. However, I wish we had a watch with a open ecosystem.

is anyone successfully running postmarketOS on a Pine Note?
if yes, do you think i could run sxmo on it (sway, wayland?)