| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,200
» Latest member: luka
» Forum threads: 16,382
» Forum posts: 117,593
Full Statistics
|
| Latest Threads |
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
Yesterday, 01:32 AM
» Replies: 1
» Views: 12,749
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 75
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 145
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,527
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 342
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,005
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 151
|
Default password
Forum: PineTab Hardware
Last Post: dissimilar_goose
08-20-2026, 05:02 AM
» Replies: 0
» Views: 208
|
New SlateOS features
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:47 PM
» Replies: 0
» Views: 239
|
SlateOS for PineTime
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:33 PM
» Replies: 2
» Views: 520
|
|
|
| No WIFI network discovery in any manjaro installation (but works on fedora) |
|
Posted by: pineitup - 01-25-2021, 07:16 PM - Forum: General Discussion on Pinebook Pro
- Replies (1)
|
 |
Does anybody have an advice about activating the wifi network discovery on fresh manjaro installation (or when running from SD card)?
When I got the PBP the wifi worked on manjaro but soon after started to show no networks and failure in activating the wifi network interface. I reinstalled manjaro and separately ran from SD card and it's all the same. I also made sure the wifi hardware switch is not activated. When running fedora on an SD card the network discovery works fine.
What can I do to resolve this?
Thanks
|
|
|
|
| Pinephone on Cricket Wireless (USA) no service |
|
Posted by: acm006 - 01-25-2021, 05:26 PM - Forum: General Discussion on PinePhone
- Replies (44)
|
|
This morning, I woke up to a text from Cricket saying:
Quote:This device is not eligible for activation on the Cricket network. Cricket's High-Definition Voice network requires use of a compatible device...
Things were working fine yesterday when I went to bed. Clicking the link in the text takes one here, regarding their 3G network shutdown https://www.cricketwireless.com/support/...=3G_Sunset
Entering my IMEI says that the device is not compatible with network.
I checked my VoLTE settings, and it looked like I was using "VoLTE-ATT", which makes sense since it's an MNVO
The wiki states "Cricket wireless is a MVNO that uses AT&T's network. VoLTE is fully supported and the PinePhone is considered a compatible device in the US by the carrier."
]I just joined Cricket last month when my phone arrived, and I'd prefer to not have to switch networks again.
I'm at a loss, so any help would be appreciated.
|
|
|
|
| Found Potential Fix For Pinephone/Verizon |
|
Posted by: syrinx - 01-25-2021, 05:07 PM - Forum: PostmarketOS on PinePhone
- Replies (2)
|
|
While I was on the phone with Verizon tech support, I was throwing AT commands at the modem just for kicks. Through dumb luck, I managed to get calling, texting and data working. This took me from calls never going through and occasionally crashing the dialer to them being as smooth as I could hope for on experimental software. The only difference between a base pmOS phosh install and mine is that I have nano and minicom installed. Here are my steps:
List VoLTE configs:
# echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
Select proper config, in my case Verizon:
# echo 'AT+QMBNCFG="select","hVoLTE-Verizon"' | atinout - /dev/EG25.AT -
Restart modem:
# echo 'AT+QCFG="ims",1' | atinout - /dev/EG25.AT -
Restart phone.
After that, everything worked
|
|
|
|
| Power LED flashing red/green... |
|
Posted by: appelgriebsch - 01-25-2021, 11:17 AM - Forum: Linux on Pinebook Pro
- Replies (3)
|
 |
During a compile job today the Power LED on my Pinebook Pro running ManjaroARM, Kernel 5.10.7 was starting to flash in red-green sequence and I noticed the OS got stuck.
Have had to do a hard reset (power off / on) to get it up and running again.
Already checked the wiki, but didn't find a hint what a flashing red/green Power LED means, so maybe someone can give me an advise please?
Note: I run the OS from an internal Intel SSD and just started experimenting with the newer kernel in ManjaroARM yesterday with different results. I switched back to the linux-pinebookpro kernel on ManjaroARM (5.7.9) after the system came up again, and the compile job was running without any hiccups... so might be a kernel issue eventually...
|
|
|
|
| 502 Bad Gateway |
|
Posted by: doelf - 01-25-2021, 03:48 AM - Forum: General
- Replies (2)
|
|
Hello Pine64-Admins,
starting 2021 I have problems trying to access threads in the forum. Either an empty page is displayed or I get an "502 Bad Gateway - nginx/1.14.2" error. Only a few threads work fine.
examples:
https://forum.pine64.org/showthread.php?tid=12864 => 502 Bad Gateway
https://forum.pine64.org/showthread.php?tid=9683 => empty page
https://forum.pine64.org/announcements.php?aid=25 => works fine
When reloading these pages including cache reset their status does not change.
I can reproduce the error with Firefox 84 and 85 on Windows 10 Pro 64 Bit v20H2 with the latest patches while Microsoft Edge works just fine.
In Firefox the problem only occurs when accessing the forum as a guest. After I logged in the problem is gone.
This might be a problem with your nginx configuration or a bug in Firefox or some problem with the forum software and the cookies it uses.
Hope this helps
Michael
|
|
|
|
| phone doesn't begin charging until awoken |
|
Posted by: hiimtye - 01-25-2021, 02:30 AM - Forum: Sxmo on PinePhone
- Replies (2)
|
 |
If you plug in the Pinephone while in deep sleep it doesn't recognize that it's plugged in and continues discharging.
I keep forgetting this, leave the phone charging for hours and come back to a still almost dead battery.
I've reenabled RTC wake in my xinitrc to see if it'll help, but I don't like leaving it enabled as it causes unnecessary battery drain.
|
|
|
|
| How to reinstall a broken OS on Pinephone's internal storage? |
|
Posted by: danimations - 01-24-2021, 09:07 PM - Forum: General Discussion on PinePhone
- Replies (1)
|
 |
Hi, I've been Pinephoning since November and things got a bit wonky recently. I kept getting annoying on-screen phone shell alerts, and noticed that connectivity seemed to be dropping out when the phone went to sleep, and I was also concerned that I may have missed calls.
More recently I discovered that the phone could no longer retrieve and install updates, which left me wondering how to overwrite the internally stored OS from scratch.
So I went to Manjaro and downloaded the ARM Beta 5 Phosh version, flashed a microSD and booted my Pinephone from that.
I had hoped that it would present me with an option to install the OS to the internal storage, but keep my phone contacts in the process. It didn't, and I can't find a prompt anywhere to achieve that.
Could someone point me in the right direction please? 
Thanks in advance.
|
|
|
|
| Rock64: MAC Address is NOT Unique! |
|
Posted by: PDXpi - 01-24-2021, 08:19 PM - Forum: Ethernet Port
- Replies (3)
|
|
I have two Rock64 boards:
- One is Version 2 (4GB).
- One is Version 3 (4GB).
I've installed DietPi 6.34.3 on both boards. But I'm not able to connect both to the same broadcast domain at the same time because each has board has the same MAC address (86:e0:c0:ea:fa:a9)!
So I started digging around. And I found that...
I'm not able to find the first 3 octets (86:e0:c0) in any OUI databases. But the kernel ring buffer had these entries...
Code: e1000e: Intel(R) PRO/1000 Network Driver
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
igb: Intel(R) Gigabit Ethernet Network Driver
igb: Copyright (c) 2007-2014 Intel Corporation.
igbvf: Intel(R) Gigabit Virtual Function Network Driver
...and...
Code: RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
RTL8211F Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
To state the obvious:
- The first one appears to be related to an Intel PRO/1000 NIC.
- The second one appears to be a Realtek RTL8211 NIC.
I've read a few of Mark's posts on the subject. And I know/believe that...
- When setting the MAC address: It should begin with 00:06:dc (i.e., The OUI of Syabas Technology [Amquest]). [ Reference ]
- The accepted solution is to specify the MAC address manually in /etc/uEnv.txt using the macaddr= and/or the eth_addr= settings. I may be wrong - But I believe that these settings are now located in /boot/armbianEnv.txt. [ Reference ]
But specifying either one or both has no affect on the MAC address (86:e0:c0:ea:fa:a9)! e.g., Neither setting appears in the Kernel command-line:
Code: dietpi@DietPi:~$ grep addr /boot/armbianEnv.txt
ethaddr=00:06:dc:00:00:01
mac_addr=00:06:dc:00:00:01
dietpi@DietPi:~$ ip add | grep ether | awk '{ print $2 }'
86:e0:c0:ea:fa:a9
dietpi@DietPi:~$ cat /proc/cmdline
root=UUID=1542112e-4bd9-4f4a-9660-e9405c792736 rootwait rootfstype=ext4 consoleblank=0 loglevel=4 ubootpart=72193746-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u
dietpi@DietPi:~$ sudo dmesg | grep 'Kernel command line' | sed 's/\[.*\] //'
Kernel command line: root=UUID=1542112e-4bd9-4f4a-9660-e9405c792736 rootwait rootfstype=ext4 consoleblank=0 loglevel=4 ubootpart=72193746-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u
- Have I overlooked something besides the solution proposed on the Wiki page? i.e., WNpctool.exe
- Is there a solution for folks that don't have MS Windows in their environment? e.g., Linux "purists"
TIA!
|
|
|
|
|
