| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
8 hours ago
» Replies: 1
» Views: 431
|
How can I record video on...
Forum: General Discussion on PinePhone
Last Post: baptx
8 hours ago
» Replies: 23
» Views: 18,312
|
u-boot rk356х (rockchip r...
Forum: Quartz64 Tutorials
Last Post: hamsterbacke
11 hours ago
» Replies: 18
» Views: 33,965
|
A/V output enable
Forum: Linux on Rock64
Last Post: 8lall0
Yesterday, 04:45 PM
» Replies: 0
» Views: 43
|
If your USB-C port is fla...
Forum: PinePhone Pro Hardware
Last Post: Zebulon Walton
Yesterday, 02:25 PM
» Replies: 0
» Views: 57
|
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-18-2026, 08:58 AM
» Replies: 2
» Views: 4,637
|
Pine a64+ power supply
Forum: General Discussion on PINE A64(+)
Last Post: davidspencer
03-18-2026, 01:02 AM
» Replies: 0
» Views: 148
|
Private / self-hosted "Cl...
Forum: General Discussion on PinePhone
Last Post: cyberb123
03-17-2026, 11:57 AM
» Replies: 8
» Views: 7,188
|
Automatic screen rotation
Forum: PineTab Software
Last Post: Raik
03-17-2026, 01:49 AM
» Replies: 32
» Views: 29,919
|
Prohibit Pinecil from goi...
Forum: Pinecil Software
Last Post: snorkel
03-13-2026, 01:56 AM
» Replies: 2
» Views: 228
|
|
|
| Verizon call/text fix |
|
Posted by: syrinx - 01-21-2021, 03:01 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
According to https://wiki.pine64.org/index.php?title=...rt#Verizon "Some Verizon users have had calls and and text stop working after around 2 weeks of use. This can be resolved by contacting Verizon support." Has anybody managed do do this successfully? If so, what should I tell support. After the massive headache of getting them to send me a sim, I am not in the mood for spending all day on the phone trying to explain to them what a pinephone is
|
|
|
|
| Kernel oops after big-ish writes |
|
Posted by: gaeb - 01-21-2021, 01:05 PM - Forum: Linux on RockPro64
- Replies (1)
|
 |
I've been trying to set up a rockpro64 for the purposes of a home server for backups; I have flashed the SPI so as to be able to boot off a USB. I had a Debian official installation on an SD with encrypted root going back in December when I noticed that any write operations larger than a few MB would give me a kernel oops (using tools like scp and rsync), and when I left it up for the holidays for a couple weeks, the machine crashed on its own. This problem seems to be independent of which OS I use; I've been trying to switch to Manjaro by flashing a USB stick and then rsyncing the contents of the root partition to a luks volume on an sd card, and I get a similar oops.
It seemed very similar to the problem described in this thread, but the solution offered here (compiling my own device tree blobs with trusted firmware) didn't yield any different behavior; although the thread leads me to suspect that it may have something to do with my having flashed the SPI partition, and there's firmware from when the rockpro64 booted off SPI still running that the kernel bumps into? However, I've used ayufan's as well as sigmaris' latest releases (sigmaris seems to be using atf for the dtb), and I continue to get kernel crashes.
What follows are the kernel messages from the most recent crash. I'm fairly new to dealing with things like this, so please let me know if I'm missing information that would be helpful.
Code: #### lots of rsync to sd happening before this, when suddenly... ####
[ 283.352255] Unable to handle kernel paging request at virtual address 000000000000b200
3,797 100% 14.[ 283.353084] Mem abort info:
60kB/s 0:00:00 (xfr#7615, ir-chk=1015/10770)
rsync: connecti[ 283.353853] ESR = 0x96000004
on unexpectedly closed (478578 bytes received so far) [generator[ 283.354546] EC = 0x25: DABT (current EL), IL = 32 bits
]
rsync error: error in rsync protocol data stream (code 12) at[ 283.355484] SET = 0, FnV = 0
io.c(228) [generator=v3.2.3]
[ 283.356229] EA = 0, S1PTW = 0
[ 283.356735] Data abort info:
[ 283.356994] ISV = 0, ISS = 0x00000004
[ 283.357335] CM = 0, WnR = 0
[ 283.357603] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000f5a93000
[ 283.358171] [000000000000b200] pgd=0000000000000000, p4d=0000000000000000
[ 283.358775] Internal error: Oops: 96000004 [#2] SMP
[ 283.359207] Modules linked in: btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq dm_crypt zram des_generic libdes cfg80211 8021q md4 garp mrp stp llc realtek rc_cec hci_uart snd_soc_simple_card dw_hdmi_cec snd_soc_audio_graph_card snd_soc_simple_card_utils btqca pwm_fan btrtl btbcm dw_hdmi_i2s_audio panfrost btintel dwmac_rk gpu_sched stmmac_platform bluetooth rockchip_rga hantro_vpu(C) stmmac rockchip_vdec(C) videobuf2_dma_sg ecdh_generic v4l2_h264 v4l2_mem2mem snd_soc_rockchip_i2s ecc snd_soc_rockchip_pcm videobuf2_vmalloc rfkill dw_wdt mdio_xpcs videobuf2_dma_contig videobuf2_memops phylink videobuf2_v4l2 videobuf2_common snd_soc_es8316 rtc_rk808 rockchip_saradc snd_soc_hdmi_codec rockchip_thermal gpio_keys rockchipdrm analogix_dp dw_hdmi cec rc_core dw_mipi_dsi drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm drm_panel_orientation_quirks
[ 283.366001] CPU: 1 PID: 690 Comm: rsync Tainted: G D C 5.9.13-1-MANJARO-ARM #1
[ 283.366735] Hardware name: Pine64 RockPro64 v2.1 (DT)
[ 283.367185] pstate: 60000005 (nZCv daif -PAN -UAO BTYPE=--)
[ 283.367688] pc : fsnotify_destroy_marks+0x1f4/0x420
[ 283.368124] lr : fsnotify_grab_connector+0x28/0xf0
[ 283.368548] sp : ffff800010c03d60
[ 283.368843] x29: ffff800010c03d60 x28: ffff0000f6f51c80
[ 283.369315] x27: 0000000000000000 x26: 0000000000000000
[ 283.369786] x25: 0000000000000000 x24: 0000000000000000
[ 283.370258] x23: ffff800012daa000 x22: ffff800012daa0c8
[ 283.370730] x21: 0000000000000000 x20: ffff800013004020
[ 283.371201] x19: 000000000000b200 x18: 0000000000000000
[ 283.371673] x17: 0000000000000000 x16: 0000000000000000
[ 283.372143] x15: 0000000000000000 x14: 0000000000000000
[ 283.372614] x13: 0000000000000000 x12: 0000000000000000
[ 283.373085] x11: 0000000000000000 x10: 0000000000000000
[ 283.373555] x9 : 0000000000000000 x8 : 0000000000000000
[ 283.374027] x7 : 000000000000003f x6 : ffff0000e0cd5600
[ 283.374498] x5 : 0000000000000305 x4 : 0000000000000000
[ 283.374970] x3 : 0000000000000001 x2 : 0000000000000001
[ 283.375440] x1 : 0000000000000000 x0 : 0000000000000000
[ 283.375912] Call trace:
[ 283.376137] fsnotify_destroy_marks+0x1f4/0x420
[ 283.376540] fsnotify_find_mark+0x1c/0xa4
[ 283.376899] dnotify_flush+0x58/0x180
[ 283.377229] filp_close+0x50/0x90
[ 283.377528] __close_fd+0x24/0x40
[ 283.377826] __arm64_sys_close+0x24/0x60
[ 283.378178] el0_svc_common.constprop.0+0x6c/0x170
[ 283.378605] do_el0_svc+0x24/0x90
[ 283.378905] el0_sync_handler+0x90/0x19c
[ 283.379256] el0_sync+0x158/0x180
[ 283.379559] Code: 88037c82 35ffff83 17fffaba f9800271 (885ffe60)
[ 283.380100] ---[ end trace 051f29ebb0bb4ed4 ]---
[ 330.448063] kauditd_printk_skb: 9 callbacks suppressed
Violación de segmento
|
|
|
|
| Wifi very slow on PBP Manjaro? |
|
Posted by: WeaseleyRon - 01-21-2021, 05:40 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
 |
My pbp is 1 month old running default Manjaro it came with.
I am able to connect to wifi but I am only gettting 0.33, and up to 1,5 Mbits/s. On the same connection my phone get 12+ Mbits/s.
What are some tips for me to debug this? I'm not even sure how to do the proper updates.
So far I've done all the updates in the software center, in whatever the UI system is on Manjaro (separate question: what is the UI/GUI called on Manjaro), and ran pamac update && paman upgrade and this did some stuff.
|
|
|
|
| Pinebook Pro has become dead, no lights? |
|
Posted by: JohnKarpenter - 01-21-2021, 05:37 AM - Forum: General
- Replies (3)
|
 |
Hi people
I've had a PBP working successfully for a month or so. But now it's dead.
It's sat in an inmoving position, connected to the mains with the barrel charger which I switch on from time to time to top up the battery. It's mostly used for flashing to my pinephone so it's not been used heavily, I also have tried a few OS's so it has been booting from multiple SD cards and the emmc (from original Manjaro) successfully.
Yesterday I flashed opensuse to the emmc (booted and rebooted a few times) and decided it wasn't for me so I flashed Manjaro again but after I tried to reboot it crashed so I had to force shutdown with 10s hold on power button. After that it failed to start up (no lights on front but charger is lit red when plugged in).
After leaving it for an hour or so it started, but after a reboot it went back to dead. And next day that's how it still is.
As it's not been moving it's unlikely to be a loose cable inside so I hesitate to take the back cover off.
Are there any known issues that may help me? Could repeated plugging of mains/SD/USB cause this?VidMate Mobdro
|
|
|
|
| Possibility of a future board revision |
|
Posted by: novhack - 01-21-2021, 03:31 AM - Forum: PinePhone Hardware
- Replies (3)
|
 |
Hey,
I have currently got sucked into the Pinephone world and I love the whole idea. I know that the plan is to support the current version of the phone for a very long time but I still cannot help it to speculate about a possible revision with a "better" SOC. I researched Allwinner products and the A50 chip looks very nice. Very similar package but using 28nm instead of 40nm, higher clock (1.8GHz), up to 4GB of DDR4 RAM.
I guess my question to other users is: Do you think that it's more probable that in the future there will be a board revision with better specs or a straight up completely new phone design?
|
|
|
|
| Random crash + network loss |
|
Posted by: r7s3TgmyQv2R3z - 01-21-2021, 02:28 AM - Forum: SailfishOS on PinePhone
- Replies (1)
|
 |
Hello,
The following situation is occurring on SF 3.4.0.24
First of all after some minutes of inactivity, the wifi network is lost and can only be enabled again by turning wifi off and on.
I get quite often a crash of the OS when I put the phone away for a couple of minutes.
=> When trying to unlock the phone, the phone doesn't react anymore (sometimes the led is blue/green but not red).
It can only be solved by a hard power off and then a normal boot.
Anyone knows what the issue might be or how to solve it?
Thanks.
Br
|
|
|
|
| Dead PinePhone 64 - does not power on at all |
|
Posted by: thatent - 01-21-2021, 12:36 AM - Forum: PinePhone Hardware
- Replies (9)
|
 |
I have used my PinePhone Pine64 Manjaro Community Edition for four days. I was having an awesome time with it, trying out different distros and UIs. Everything worked beautifully at first and I'm well impressed with the current status of usability of the phone.
Now, the phone is dead - absolutely dead: no LED action, no screen (not even backlight), nothing happens anymore.
How it started:
The problem started when I had the phone running Mobian+Phosh.
I had it docked on USB keyboard/mouse, HDMI and power (although the battery did not really seem to charge, it was losing charge %).
I had updated some packages and installed some new ones.
In the terminal I gave the command: sudo reboot.
At this point the charge on the battery was probably down to a single digit (5% maybe?)
I left it in the dock.
The phone started to reboot and even power on again. On the external monitor, a very hazy version of the Mobian logo appeared (so it started to boot).
Then all went black and the phone has been dead since.
Current situation
Nothing works.
I tried the reset pin, multiple times for over 15 seconds. Removed and replaced the battery a couple of times. Held the power button multiple times for over 10/15secs.
There is no indication that anything at all is still going on in the phone.
I left the phone charging overnight (the whole night), and still no luck this morning.
The only thing that is still happening is that the phone draws power (when I connect it, I can hear coil whine starting on my cheap charging station, and when I connect it to my power bank it shows dots indicating something is sucking power from it - both charging methods were used without any issues during the first four days).
I am at a complete loss as to what's going on and I don't know what to do next... it would be a real shame if this was it and the device is now dead.
I hope anyone can help. If you have any suggestions as to what I could try or do next, please let me know!
Cheers.
|
|
|
|
PinePhone WIFI: PineCone user installable? |
|
Posted by: PineUser-1337331 - 01-20-2021, 02:28 PM - Forum: PinePhone Hardware
- Replies (2)
|
 |
Hey folks,
I hope you are all healthy and well.
Since the wifi on the pinephone requires non-free drivers (realtek iirc), I obviously would rather wait for the version with the pinecone included.
But since I am impatient and want to start developing apps (and get rid of my android), I am wondering:
can I, once it has reached usability, change the wifi card? I couldn't find out how the wifi card is connected to the mainboard.
I don't have any skill in soldering, so that's out of the question.
Thank you all for your time!
1337331
|
|
|
|
|