| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,954
» Latest member: parker888
» Forum threads: 16,335
» Forum posts: 117,437
Full Statistics
|
| Latest Threads |
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
Yesterday, 08:37 AM
» Replies: 106
» Views: 215,024
|
Ibotta Referral Program [...
Forum: Pinebook Pro Hardware and Accessories
Last Post: rex9090k
Yesterday, 05:24 AM
» Replies: 0
» Views: 53
|
Ibotta Deal for New Users...
Forum: Android on Pinebook Pro
Last Post: rex9090k
Yesterday, 05:23 AM
» Replies: 0
» Views: 44
|
Ibotta Promo Code Today [...
Forum: Getting Started
Last Post: rex9090k
Yesterday, 05:23 AM
» Replies: 0
» Views: 44
|
Ibotta Invite Offer [ZVFT...
Forum: PineNote Hardware
Last Post: rex9090k
Yesterday, 05:22 AM
» Replies: 0
» Views: 42
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 58
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 126
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
03-28-2026, 01:01 PM
» Replies: 17
» Views: 8,405
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 1,987
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 879
|
|
|
| using on-board sensors |
|
Posted by: Mentaluproar - 07-17-2020, 12:00 AM - Forum: Linux on Rock64
- No Replies
|
 |
Is there a way to access the hardware sensors for temperatures and voltages through the sensors command? Has anyone mapped things to a /etc/sensors.d/rockpro64 file? I can rename the virtual adaptor temps but power management reads out all zeros.
|
|
|
|
| We need more power, Scotty! |
|
Posted by: mtnygard - 07-16-2020, 06:52 PM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
 |
I've got the power adapter plugged in, but the battery still heads toward zero.
Admittedly, I'm compiling Haskell, so it's not a typical workload.
But still, it'd be nice to power up enough to keep from going to sleep mid-compile.
Any recommendations? I've already fiddled with NVMe settings and turned the brightness down. Can the PBP accept more power from an after-market adapter?
|
|
|
|
| sudden ethernet failure |
|
Posted by: Paraplegic Racehorse - 07-16-2020, 04:12 PM - Forum: Armbian
- Replies (16)
|
 |
Hardware: Pine64 A64 512MB
OS: Armbian Buster 20.02.1 (kernel 5.4)
After months of running steady through multiple reboots and sudden power failures, all my boards suddenly lost eth0; all simultaneously; all while powered on and otherwise running without issue. No, I was not logged in and doing things with the system at the time. My router alerted me when the connections dropped out.
Things I tried (and failed): - different ports on ethernet switch
- power cycling (hard reboot)
- hook up monitor and keyboard and investigate
Investigation discovered no eth0 device. dmesg reports no driver.
lshw is not present on system so I cannot probe hardware and maybe get driver working with modprobe.
So I reflashed the OS and ... no network. dmesg reports no driver.
So I flashed a differnt OS -- Armbian Bionic 20.05.2 (kernel 5.4) -- and ... no network. dmesg output below.
Code: dwmac-sun8i 1c30000.ethernet: IRQ eth_wake_irq not found
dwmac-sun8i 1c30000.ethernet: IRQ eth_lpi not found
dwmac-sun8i 1c30000.ethernet: PTP uses main clock
dwmac-sun8i 1c30000.ethernet: 1c30000.ethernet supply phy-io not found, using dummy regulator
dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 2001 (expect 0)
dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
dwmac-sun8i 1c30000.ethernet: COE Type 2
dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
dwmac-sun8i 1c30000.ethernet: Normal descriptors
dwmac-sun8i 1c30000.ethernet: Chain mode enabled
...
dwmac-sun8i 1c30000.ethernet: EMAC reset timeout
dwmac-sun8i 1c30000.ethernet eth0: stmmac_dvr_remove: removing driver
dwmac-sun8i: probe of 1c30000.ethernet failed with error -14
Any ideas or assistance appreciated.
|
|
|
|
| Screen freezes and alternates two frames? Look here! |
|
Posted by: Djhg2000 - 07-16-2020, 02:55 PM - Forum: Mobian on PinePhone
- Replies (1)
|
 |
First of all a disclaimer; I haven't had a chance to test this on the latest version of Mobian yet.
This will be a quick post about an issue I've discovered but I don't have the time to investigate it (I'll be quite busy in the next few days). Hopefully my research still helps someone.
I managed to capture this in dmesg when it happened (I got lucky and had an SSH session going):
Code: [ 7251.715549] [drm:lima_sched_timedout_job] *ERROR* lima job timeout
[ 7252.962247] lima 1c40000.gpu: fail to save task state from phoc pid 1663: error task list is full
[ 7252.971463] lima 1c40000.gpu: gp task error int_state=0 status=0
Searching various bug trackers I found this open but stagnant bug report:
https://gitlab.freedesktop.org/lima/linux/-/issues/33
So it looks like the GPU either stalls or falls out of sync with the lima driver for whatever reason. I do suspect it has something to do with power delivery because the same issue won't happen if I do this:
Code: echo powersave | sudo tee /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
The most reliable way I've found to trigger the bug on my phone is do start downloading something big over LTE with wget. After somewhere between a few hundred MB and a GB you will notice the scrolling test going back and forth and you stop being able to interact with the phone through the touch screen.
At first I thought it was a hard crash and the power button only kept working through some weird quirk of interrupts offloaded from the main CPU, but as it turns out the rest of the system is fully functional. You can even recover most of the system (GUI tasks will be killed) by issuing this command:
Code: sudo systemctl restart phosh.service
This should bring back the lock screen as if the system was freshly booted, but any non-GUI tasks are still running as if nothing happened.
That's about as far as I've been able to work things out so far. I think the appropriate thing to do here is to test the hack from the lima issue tracker (raising the scheduling error threshold above 1) and see if it helps the driver towards a successful recover. I'd try it myself if I had a build environment set up. Since this is an upstream issue I didn't post this on the Mobian issue tracker, but in retrospect I probably should've done that as well.
|
|
|
|
| Manjaro XFCE: Vastly improved experience with Picom (Compton) compositor |
|
Posted by: jichu4n - 07-16-2020, 02:13 PM - Forum: Linux on Pinebook Pro
- Replies (2)
|
 |
TL;DR: Switched to Picom compositor instead of XFCE's built-in compositing, and everything feels MUCH smoother.
Currently running a vanilla Manjaro ARM XFCE install on my Pinebook Pro. While everything mostly works fine, I've been bugged by how the experience somehow just feels a bit sluggish. In particular, scrolling in Chromium and Firefox is visibly laggy even for fairly lightweight websites.
I would've assumed it's just how the hardware is, but I've seen some videos of Manjaro ARM KDE on the Pinebook Pro that seem to suggest otherwise. Additionally, I happen to have a Chromebook with the same Rockchip RK3399 SoC (ASUS Chromebook Flip C101PA) and browsing and scrolling around on the Chromebook feels much much smoother in comparison.
After some digging around, I started to suspect the lag / sluggishness was related to a lack of OpenGL acceleration in the XFCE desktop. So long story short, I tried switching out XFCE's built-in compositing for the Picom compositor (apparent successor to Compton), and was blown away by how much it improved the experience. Scrolling in Chromium and Firefox felt much smoother, and navigating around apps end menus just felt much snappier.
So really wanted to share this result, and curious to know if switching to Picom may help other Manjaro ARM XFCE users as well.
Steps I used to set up Picom:
1. pacman -Sy picom
2. XFCE Settings -> "Window Manager Tweaks" -> "Compositor" -> uncheck "Enable display compositing"
3. XFCE Settings -> "Session and Startup" -> "Application Autostart" -> add item with the command "picom"
4. Start in current session with "picom -b".
The default settings seemed to work fine for me, so I haven't found the need to create a config file to tweak settings yet.
My setup: manjaro-release 20.07-1 (upgraded from 20.04 install), kernel linux-pinebookpro 5.7.0-3, mesa 20.1.3-1, xfwm4 4.14.2-1
References:
- Using Compton for a tear-free experience in Xfce in Manjaro Wiki
- Picom in Arch Linux Wiki
|
|
|
|
| USB-C Dock and HDMI, revison 1.2 (Modded) |
|
Posted by: Ersatz - 07-16-2020, 01:06 PM - Forum: Mobian on PinePhone
- Replies (5)
|
 |
*Edit* Please see https://wiki.mobian-project.org/doku.php?id=mods
Update ANX chip firmware https://xnux.eu/devices/feature/anx7688.html
Note: this should be run as root user and not through sudo
*This line is important. Note 2: Clone the repository rather than directly downloading the .bin file. For some reason, directly downloading it does not give you the correct image and errors on the “echo” command.
*Original Post*
I have been testing out a USB-C dock for a couple days now. USB device work (mouse, flash drives), SD-card reader, and power deliver all work. However, I can not get a monitor to detect the HDMI signal, dmesg shows when HDMI is plugged in an detected. Has anyone successfully used display out on Mobian? I am hitting a wall troubleshooting this, and have ruled out the dock itself.
Unplugged HDMI: anx7688 0-0028: dp state changed to 0x00
Plugged in HDMI: anx7688 0-0028: dp state changed to 0x03
Note to anyone wondering my phone is hardware modded (switches removed)
|
|
|
|
| Pine Store should accept Zip+4 |
|
Posted by: Mark53 - 07-16-2020, 12:03 PM - Forum: General
- Replies (1)
|
 |
I ordered a Pinephone yesterday and used my zip code with the extra 4 digits (the USPS calls this ZIP+4). Zip+4 codes have 5 digits for the regular zip code, followed by a hyphen, then a 4 digit extension. When I entered my zip code in the pattern 12345-6789, the hyphen was removed in the backend and my confirmation email showed a zip code with a pattern of 123456789.
Fortunately sales@pine64.org took care of this very quickly and fixed the zip code, but it should be a simple fix to allow hyphens in this field so we can use a more specific address. Is there any reason not to allow this character?
|
|
|
|
| I/O errors from SD card slot? (Manjaro, kernel 5.7) |
|
Posted by: zackw - 07-16-2020, 07:31 AM - Forum: General Discussion on Pinebook Pro
- Replies (5)
|
 |
I'm getting I/O errors from some, but not all, attempts to use the SD card slot in my PBP. `badblocks -w /dev/mmcblk1` completes without error, and `fdisk` is also happy, but when I attempt to run `mkfs.ext4` or `cryptsetup luksFormat` on the (single, whole-disk) partition, the operation fails and I see errors like this in dmesg:
Code: blk_update_request: I/O error, dev mmcblk1, sector 2120 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2128 op 0x1:(WRITE) flags 0x8800 phys_seg 254 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2117 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 2127 op 0x1:(WRITE) flags 0x8800 phys_seg 255 prio class 0
(Only one error occurred per attempt to format the partition.)
I put the card into a different computer and was able to create a filesystem successfully, so I don't think the card itself is at fault. However, when I put the formatted card back into the PBP and tried to mount the filesystem or to run e2fsck on it, I got more of the same errors, just with different sector numbers and flags:
Code: blk_update_request: I/O error, dev mmcblk1, sector 8301 op 0x1:(WRITE) flags 0x8800 phys_seg 251 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 40960 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
blk_update_request: I/O error, dev mmcblk1, sector 59023360 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
This is a 2019-batch PBP, so it shipped with MrFixit's modified Debian, and the card slot was working fine with that kernel; I only started seeing problems after I reflashed the internal storage with Manjaro. So right now I'm inclined to suspect a kernel bug. Anyone else seeing similar problems? Workarounds? Debugging advice?
|
|
|
|
|