Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,927
» Latest member: 1services
» Forum threads: 16,330
» Forum posts: 117,424

Full Statistics

Latest Threads
A/V output enable
Forum: Linux on Rock64
Last Post: 8lall0
2 hours ago
» Replies: 0
» Views: 1
If your USB-C port is fla...
Forum: PinePhone Pro Hardware
Last Post: Zebulon Walton
4 hours ago
» Replies: 0
» Views: 20
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-18-2026, 08:58 AM
» Replies: 2
» Views: 4,615
Pine a64+ power supply
Forum: General Discussion on PINE A64(+)
Last Post: davidspencer
03-18-2026, 01:02 AM
» Replies: 0
» Views: 135
Private / self-hosted "Cl...
Forum: General Discussion on PinePhone
Last Post: cyberb123
03-17-2026, 11:57 AM
» Replies: 8
» Views: 7,157
Automatic screen rotation
Forum: PineTab Software
Last Post: Raik
03-17-2026, 01:49 AM
» Replies: 32
» Views: 29,838
Prohibit Pinecil from goi...
Forum: Pinecil Software
Last Post: snorkel
03-13-2026, 01:56 AM
» Replies: 2
» Views: 217
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-12-2026, 04:49 AM
» Replies: 2
» Views: 610
Looking for PineTime user...
Forum: General
Last Post: Mitrax
03-11-2026, 02:50 PM
» Replies: 2
» Views: 394
reset wifi hardware/drive...
Forum: Mobian on PinePhone
Last Post: baptx
03-10-2026, 04:43 PM
» Replies: 5
» Views: 5,069

 
  Best way to avoid SMP internal errors when building RAID?
Posted by: kuleszdl - 02-26-2021, 05:11 PM - Forum: Linux on RockPro64 - Replies (1)

Hi,

as some of you might know there is a known issue with handling of PCIe errors on the RP64 as discussed here:

https://forum.pine64.org/showthread.php?tid=8374
https://forum.pine64.org/showthread.php?tid=6329

I am getting this error when I try to build/rebuild my RAID for the first time. Sometimes I am lucky and it works, but most of the time it does not and I don't have much confidence in putting my backup on a machine with a malfunctioning PCIe interface. If it happens, I see entries like these in the logs:

Code:
kernel:[  658.490457] Internal error: synchronous external abort: 96000210 [#1] SMP
Message from syslogd@debian at Feb 26 23:35:03 ...
kernel:[  658.518345] Code: b8615881 340001c1 8b21c061 8b010001 (b9400021)
Message from syslogd@debian at Feb 26 23:35:03 ...
kernel:[  658.490457] Internal error: synchronous external abort: 96000210 [#1] SMP
Message from syslogd@debian at Feb 26 23:35:03 ...
kernel:[  658.518345] Code: b8615881 340001c1 8b21c061 8b010001 (b9400021)

As I am still encountering these issues when running the latest Debian unstable kernel, I fear that this issue won't be fixed in the upcoming Debian stable either (because it's a hardware issue and not Debian's fault). Now, I wonder what the best workaround could be. Recompiling the kernel with the hack discussed in said thread seems to work, but it's not a longterm solution if we want to get regular security updates for our kernel without the need for manual patching and recompiling...

Is there any workaround we could apply in software to avoid these issues? I would be happy with anything, even at the cost of performance like disabling all but one CPU core etc.

Thank you!

I tried the most radical approach and completely disabled SMP by adding the following kernel command line parameter:

Code:
nosmp

As a result, my RP64 now runs with only one cortex a53 core. Yet, the performance seems to be enough to build the RAID:

Code:
%Cpu(s):  0.7 us, 44.6 sy,  0.0 ni, 49.4 id,  0.0 wa,  0.0 hi,  5.2 si,  0.0 st

At least, I didn't get any SMP error yet, so I am optimistic this will work...

Suggestions for less drastic and more performant workarounds (e.g. enabling one of the A72 cores) welcome!

Bad news and correction - I encountered the same issue now even with SMP disabled :-(

Code:
kernel:[  922.683235] Internal error: synchronous external abort: 96000210 [#1] SMP

Message from syslogd@debian at Feb 27 00:32:22 ...
kernel:[  922.711924] Code: b8615881 340001c1 8b21c061 8b010001 (b9400021)
Message from syslogd@debian at Feb 27 00:32:22 ...
kernel:[  922.683235] Internal error: synchronous external abort: 96000210 [#1] SMP

Message from syslogd@debian at Feb 27 00:32:22 ...
kernel:[  922.711924] Code: b8615881 340001c1 8b21c061 8b010001 (b9400021)

Details in dmesg:

Code:
[  922.696664] CPU: 0 PID: 171 Comm: scsi_eh_1 Not tainted 5.10.0-3-arm64 #1 Debian 5.10.13-
1                                                                                          
[  922.697415] Hardware name: Pine64 RockPro64 v2.1 (DT)                                  
[  922.697888] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)                        
[  922.698456] pc : ahci_scr_read+0x50/0x90 [libahci]                                      
[  922.698935] lr : sata_scr_read+0x7c/0xa0 [libata]                                      
[  922.699371] sp : ffff8000120cbab0      
[  922.699684] x29: ffff8000120cbab0 x28: ffff0000f0e50000                                
[  922.700185] x27: ffff0000f0e52368 x26: ffff0000f0e523e0                                  
[  922.700686] x25: 0000000000000000 x24: 0000000000000000                                  
[  922.701187] x23: 0000000000000001 x22: ffff0000f0e539b8                
[  922.700686] x25: 0000000000000000 x24: 0000000000000000                          [0/1980]
[  922.701187] x23: 0000000000000001 x22: ffff0000f0e539b8                                  
[  922.701688] x21: ffff0000f0e523e0 x20: ffff0000f0e52040                                  
[  922.702189] x19: ffff0000f0e52440 x18: 0000000000000000                                  
[  922.702689] x17: 0000000000000000 x16: 0000000000000000                                  
[  922.703189] x15: 0000000000000000 x14: 0000000000000000                                  
[  922.703689] x13: 0000000000000000 x12: 0000000000000000                                  
[  922.704189] x11: 0000000000000000 x10: 0000000000000000                                  
[  922.704690] x9 : ffff800008ea46fc x8 : 0000000000000000                                  
[  922.705191] x7 : ffff0000f0e52040 x6 : ffff8000120cbb44                                
[  922.705691] x5 : 0000000000000001 x4 : ffff800008e30078                                  
[  922.706191] x3 : 0000000000000180 x2 : ffff8000120cbb44                                  
[  922.706692] x1 : ffff800011e5d1b0 x0 : ffff800011e5d000                                  
[  922.707192] Call trace:                                                                  
[  922.707440]  ahci_scr_read+0x50/0x90 [libahci]                                          
[  922.707881]  ata_eh_link_autopsy+0x8c/0xb4c [libata]                                    
[  922.708368]  ata_eh_autopsy+0x40/0x144 [libata]                                          
[  922.708817]  sata_pmp_error_handler+0x48/0x930 [libata]                                
[  922.709308]  ahci_error_handler+0x4c/0x90 [libahci]                                    
[  922.709786]  ata_scsi_port_error_handler+0x2a4/0x744 [libata]                          
[  922.710343]  ata_scsi_error+0xa4/0xec [libata]                                          
[  922.710786]  scsi_error_handler+0xc0/0x5d0 [scsi_mod]                                  
[  922.711261]  kthread+0x130/0x134        
[  922.711574]  ret_from_fork+0x10/0x38                                                    
[  922.711924] Code: b8615881 340001c1 8b21c061 8b010001 (b9400021)                        
[  922.712486] ---[ end trace 687bc2ded22b1d30 ]---


  Finding and adding new programs/apps
Posted by: James Good - 02-26-2021, 04:16 PM - Forum: General Discussion on Pinebook Pro - Replies (3)

After what has seemed like a very long time with little to show for the efforts, I burned a new download of Manjaro to a micro USB card and put it in the PBP.  Powered it on and Manjaro got installed.  Seems to be working as it should.  Minor problem; can't seem to find or install an email program/app where I could send and receive email on the laptop.  The WiFi works and has connected to the home network.  Ultimate goal would be to use the laptop for portable and travel operations.  Any suggestions would be welcomed.
James Good


  What Now for Google Users?
Posted by: jc1685 - 02-26-2021, 04:12 PM - Forum: General Discussion on Pinebook Pro - Replies (8)

Hi,

Since the Chromium browser will be losing the ability to sync with Google, and Pinebook Pro users cannot install Chrome, what is the next step for Google users on Pinebook Pro? I've used Google for years and I have an Android phone, so being able to sync my bookmarks and history is important to me. I'm unaware of any solutions that exist; and using another browser ecosystem, like Firefox, isn't really a solution to the problem, since it's an entirely different browser ecosystem.

Anybody have any ideas?


  What OS and Software Are You Running On Your PineTab?
Posted by: ImmyChan - 02-26-2021, 04:06 PM - Forum: General Discussion on PineTab - Replies (3)

I just got my PineTab yesterday and I'm slightly at ends with what to run on it, what are you all running on yours?


  Latest updates
Posted by: bvbfan - 02-26-2021, 12:37 PM - Forum: Manjaro on PinePhone - Replies (3)

I install latest update and there is login issue, i change PIN to 12 then change kde password to `kde` (via passwd) then i can't unlock the device. Should i reflash? I try ssh but unfortunately it's not enable, root / root refused. Any suggestions?


  Warning, 5.5mm barrel-style power cables
Posted by: biketool - 02-26-2021, 02:26 AM - Forum: General Discussion on Pinecil - Replies (6)

I let someone look at my pinecil, they grabbed a standard 5.5mm 12v barrel-style power cable for the bench power supply assuming the pinecil used that standard and did the old push&twist to force it in.
After a few seconds of effort my associate had a stupid look on their face holding the connector cable but the center pin from the pinecil was jammed tight into the barrel connector.
Fortunately I was able to re-insert the pin and solder the broken power line back together, though certainly not as strong against a similar attack it works again over USB C (obviously) and the repaired barrel power port too so all is good.


  PINEBOOK Pro USB-C Docking Deck on FreeBSD
Posted by: S199pWa1k9r - 02-26-2021, 02:07 AM - Forum: BSD on Pinebook Pro - Replies (2)

Hi!

Has anyone tried the PINEBOOK Pro USB-C Docking Deck under FreeBSD.
Ethernet is not detected on me.
What chipset is used in the PINEBOOK Pro USB-C Docking Deck?


  Installing and tweaking Chromium on Mobian and Arch
Posted by: C0ffeeFreak - 02-25-2021, 07:54 PM - Forum: Mobian on PinePhone - Replies (19)

This will walk you through installing Chromium on Mobian and Arch Linux. Chromium won't run yet on Manjaro or Postmarket OS. I think after you make these tweaks and use Chromium you will see it has quite a few advantages over Firefox.

Positives: Faster, seems to be better optimized. Scales better. Works excellent with full window Web apps with desktop shortcuts. Pretty much as good as real apps. You can use a lot of extensions, my VPN has one and it works very well.

Negatives: Keyboard has to be manually throttled up and down through the keyboard icon in the bottom right corner. Some keys on the touch keyboard don't seem to work like capital  C, and the @ symbol. No idea why. Work fine on the keyboard docked.

Here is a step by step walk through for installing and tweaking it.
It has to be installed through Flatpak, The Chromium apps in the Mobian and Arch software repository don't seem to work. I suspect it's a Wayland or X11 problem.

Add flatpak to Mobian from the terminal:

Code:
apt install gnome-software-plugin-flatpak

Code:
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo


Close and restart your terminal.


Add flatpak to Arch from the terminal:

Code:
sudo pacman -S flatpak

Close and restart your terminal.

Install Chromium:
Code:
flatpak install flathub org.chromium.Chromium

Code:
scale-to-fit Chromium on

Code:
flatpak run org.chromium.Chromium


It's very important that you do this before you do anything with the browser. If you don't your browser user agent will leak and if your service provider identifies your device that way it may blacklist you and deactivate your account! AT&T has been doing this. For what it's worth, Mobian Firefox ESR is the only browser with a working Android user agent right now out of the box. User agent extensions alone will leak through Java. All the other distros are leaking after recent browser updates.

After Chromium opens type chrome://flags in the address bar and hit enter. After it opens search for Freeze User-Agent request header and enable it then close the browser.

Open Chromium go to settings-more tools-extensions search for and install Use-Agent Switcher and Manager.

Open the extension and choose Chrome and Android in the drop down. Then select Chrome 87.0.4290.101  Android 10  and at the bottom left select Apply (all windows)

Close the browser and relaunch. Your browser should launch in mobile now. Do a leak test by searching What is my browser? look on several of the result sites that show up and look at your User Agent string. There should be no hint of Arch64 or desktop in any of them or it's leaking. Congratulations! Your now running Chromium Mobile.

On another note this will not work for Ungoogled Chromium. The settings and extensions were removed. 


  KDE Manjaro CE
Posted by: submariner - 02-25-2021, 12:10 PM - Forum: General Discussion on PinePhone - Replies (1)

While on this 2GB cheaper version with KDE Manjaro CE edition (I havent manage to buy 3GB version in time) KDE Manjaro seems very sluggish out of the box, after an upgrade it became nearly as fluid as any fdriod, but it still feels a little bit overweight for 2GB ram as it would be on any other computer running KDE while having as much ram.

As I've never used manjaro itself and I've only used KDE on computers that at least has 4GB ram which is only not sluggish when its 8GB ram I was just thinking maybe someone has some tips for tweaking it ? Or could share their experiences


  battery and charging
Posted by: submariner - 02-25-2021, 12:04 PM - Forum: General Discussion on PinePhone - Replies (4)

Si it might be only my ignorance that I expected some charger to be packed with phone. ofc I've ordered in a separate package battery charger itself, but getting to the point

upon first boot battery showed something like 30%
plugging it with that USB-C red cable to an ultrabook instantly shows it to be 40 or 50% something
unplugging it after few seconds shows like 47% percent which after a while resets to some other number

So I was just wondering if its just me not having a proper charger has such issues, maybe a battery is bad ?

I'm not refunding or whatever, but given such limited supply of components for phone in a package itself (talking of 2GB version) its a bit worrying. in a week or so I should get a package with more cables and docker and such, but this battery % status on KDE Manjaro UI is a bit worrying.