| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,966
» Latest member: Sergio Gus
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 104
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,607
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 179
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 90
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 216,595
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 162
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 240
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,047
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 912
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 591
|
|
|
Power indicator LED flashing alternating colours |
|
Posted by: K4rolis - 05-29-2020, 01:27 PM - Forum: General Discussion on Pinebook Pro
- Replies (3)
|
 |
Hi,
I've been messing around with my brand-new Pinebook Pro. I had an issue where KDE appeared to have died, so I force shutdown the laptop. After that, I could no longer log in - my password would get accepted, but it would hang on the progress bar after the password.
To try and work out what's going on, I dropped into tty2 (Ctrl + Alt + F2), but then I realised that things are seriously wrong - I would get segfaults running man. I force shut down the laptop again, and now I'm getting the power LED flashing.
I am fully aware that this is my fault (well, except the initial KDE blackout which I probably should have debugged more), however, does this mean that eMMC is now corrupted and the only solution is a reinstall?
Also, I don't know what the colours of the power LED are as I'm colourblind, but I'm certain people in the know understand what I'm talking about. I think the error codes should also possibly be on the wiki - I'm happy to add those there when I get a reply here.
|
|
|
|
| Clock Time wrong |
|
Posted by: VMMainFrame - 05-29-2020, 10:35 AM - Forum: PineTime Hardware and Accessories
- No Replies
|
 |
I am running Danielt's wasp-os on my Pinetime. Yesterday in the afternoon I set the correct year, month, day and time on the Pinetime.
Last night at about 11:30 pm I checked the Pinetime and the date and time were correct, and the battery icon was yellow.
This morning I checked the Pinetime and the date (year, month and day) were correct but the time was wrong. It said 08:48 and the actual time was 11:00 am. The battery icon showed red.
I can understand the clock resetting if the battery gets too low, but I can't understand why the time would be wrong but the date is correct.
Any ideas?
Hugh
|
|
|
|
| operating time? |
|
Posted by: mindwave - 05-29-2020, 09:10 AM - Forum: General Discussion on PineTab
- Replies (9)
|
 |
i know that few if any have had their hands on one, but has there been any indication of what the actual operating time should be?
As I tell my son on a regular basis, if we had focused a fraction of our time on battery life that we have on doubling cpu numbers we'd charge our cars for 1 hour 1 day a year and drive wherever we wanted.....
I just bought a Chuwi Hi10x and he operating time is good but not great
|
|
|
|
| Manjaro SD card boot issue |
|
Posted by: aeastw - 05-29-2020, 02:38 AM - Forum: Linux on Pinebook Pro
- Replies (8)
|
 |
Hi,
I received my new PineBook Pro yesterday, and can't wait to get stuck in and put it to work. Apologies if this question has been answered somewhere already, I did have a look around and couldn't find a definite answer.
The new PineBook has Manjaro 20.04 installed by default on the EMMC. This works great. The issue comes when I try and boot from SD card. Every image that I've attempted to boot from SD so far has resulted in a black screen, although I'm fairly certain that the system has booted as on some images I hear the startup sound/chime, so it looks like a display/graphics issue. I've tried different SD cards, including ones that I know work on other SBCs. And I've tried several images so far:
- aryufans bionic and focal images
- armbian
- Manjaro 20.04
The only image that I've had working from SD card is the Manjaro image.
After having a dig around I found some references to the issue which looks like it could be an issue with Manjaros uboot and a post here but the proposed work around doesn't seem to work. I'm guessing quite a few people will come across this as the new PineBook Pros arrive with people.
Any help would be greatly appreciated!
|
|
|
|
| SD won't boot |
|
Posted by: dgkPBP - 05-28-2020, 09:20 PM - Forum: General Discussion on Pinebook Pro
- Replies (9)
|
 |
I'm new to the Pinebook Pro. I bought a used one a few days ago. I decided to update to Manjaro; no problem. Now I'd like to re-install using
Manjaro-ARM-kde-plasma-pbpro-20.04-emmc-installer-20.04.img
When I insert the SD and power cycle, it wouldn't boot. I thought that maybe I needed to install the original software and then try. I couldn't boot the original SD.
Any ideas?
Thanks.
|
|
|
|
| Built-in Webcam Not Working |
|
Posted by: fozzedout - 05-28-2020, 06:35 PM - Forum: General Discussion on Pinebook Pro
- Replies (36)
|
 |
I received my PBP today, and just trying out all the features, but for some reason I can't get the built-in webcam to work.
I've tried Kamoso and Cheese - cheese outputs this "cheese-application.vala:214: Error during camera setup: No device found"
Under the /dev/ there is /dev/video0, /dev/video1, /dev/video2. Using that, I've tried smplayer /dev/video0 as well as video1 and video2, but nothing shows.
I've also checked that the webcam is enabled (double flash from [Pine]+[F12]).
Can someone help me diagnose this please?
|
|
|
|
| Next SBC? |
|
Posted by: Rocker - 05-28-2020, 04:29 PM - Forum: General
- Replies (1)
|
 |
So...just curious, anyone have details on the next SBC?
With the new 8GB RP I figured Pine would follow up?
|
|
|
|
| Get volume keys working |
|
Posted by: Boern - 05-28-2020, 03:54 PM - Forum: Mobian on PinePhone
- Replies (3)
|
 |
I was fed up with the volume keys not working in Phosh, so I set up actkbd to control them.
1. Download the source code of actkbd http://users.softlab.ntua.gr/~thkala/pro....8.tar.bz2
2. Untar the downloaded file
Code: tar xjf actkbd-0.2.8.tar.bz2
3. Install build-essential so that you can compile programs
Code: sudo apt install build-essential
4. Enter the untarred directory and compile actkbd
Code: cd actkbd-0.2.8 ; make
5. Copy the resulting actkbd binary somewhere sensible. I chose ~/.local/bin/
6. Create a config file somewhere sensible. I chose ~/.config/actkbd.conf. The default is /etc/actkbd.conf. If you use the default location you don't have to specify it when launching actkbd.
7. Add the following to the config file
Code: 114:key::pactl set-sink-volume @DEFAULT_SINK@ -5%
115:key::pactl set-sink-volume @DEFAULT_SINK@ +5%
8.Setup actkbd to autostart by creating the file ~/.config/systemd/user/actkbd.service with the contents:
Code: [Unit]
Description=actkbd keyboard shortcut daemon
[Service]
Type=simple
ExecStart=/home/mobian/.local/bin/actkbd -c /home/mobian/.config/actkbd.conf -d /dev/input/by-path/platform-1c21800.lradc-event
Restart=always
RestartSec=5s
[Install]
WantedBy=default.target
9. Reload systemd
Code: systemctl --user daemon-reload
10. Enable actkbd to autostart
Code: systemctl --user enable actkbd
11. Start actkbd
Code: systemctl --user start actkbd
|
|
|
|
Help: Pinebook Pro will not enter sleep [Manjaro 20.04] |
|
Posted by: EverythingIsInput - 05-28-2020, 02:41 PM - Forum: Linux on Pinebook Pro
- Replies (49)
|
 |
Hello, I just received my Pinebook Pro yesterday which is the latest Manjaro branded version using the most current Manjaro ARM KDE 20.04 release. I finally finished installing & configuring all of my software/settings and thought I would test the machine - everything seems to work fine except SLEEP! (I also have a thread open about this issue on Manjaro forums since I'm not sure which would be the better place)
I have researched online and see a few others have encountered similar issues, but I wasn't able to find a fix that worked for me. Also, I haven't made any configuration changes or messed with suspend modes - I am fine with using s2idle, just want the screen to shut off and sleep when I close the laptop lid!
The crux of the issue is that the laptop starts to go to sleep, then it wakes immediately after - whether closing the lid, pressing the power button and choosing "sleep", or typing into terminal: "systemctl suspend". Long story short, it appears that either the dwmmc_rockchip [fe310000.mmc: pre_suspend failed for non-removable host: -38], or Device ff9a0000.gpu [failed to suspend: error -16] are causing the machine to abort going to sleep. Attached are the full logs:
Code: May 28 12:15:59 feather polkitd[1013]: Registered Authentication Agent for unix-process:4179:71609 (system bus name :1.193 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale eaHello, I just received my Pinebook Pro yesterday which is the latest Manjaro branded version using the latest Manjaro ARM KDE 20.04 release. n_US.UTF-8)
May 28 12:15:59 feather ksmserver[1216]: lock called
May 28 12:15:59 feather kded5[1188]: bluedevil: About to suspend
May 28 12:15:59 feather NetworkManager[881]: <info> [1590693359.2819] manager: sleep: sleep requested (sleeping: no enabled: yes)
May 28 12:15:59 feather NetworkManager[881]: <info> [1590693359.2822] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 28 12:15:59 feather NetworkManager[881]: <info> [1590693359.2842] manager: NetworkManager state is now ASLEEP
May 28 12:15:59 feather ksmserver[1216]: Lock window Id: 20971562
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 20971562
May 28 12:15:59 feather polkitd[1013]: Unregistered Authentication Agent for unix-process:4179:71609 (system bus name :1.193, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 28 12:15:59 feather org_kde_powerdevil[1269]: powerdevil: Pausing all media players before sleep
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525956
May 28 12:15:59 feather kscreenlocker_greet[4185]: Qt: Session management error: networkIdsList argument is NULL
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525960
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525972
May 28 12:15:59 feather ksmserver[1216]: CreateNotify: 54525981
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: kf5.kpackage: No metadata file in the package, expected it at: "/usr/share/wallpapers/Breath2/contents/images/"
May 28 12:16:00 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList
May 28 12:16:00 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525983
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525985
May 28 12:16:00 feather ksmserver[1216]: MapNotify: 54525983
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 41947667
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54525987
May 28 12:16:00 feather ksmserver[1216]: MapNotify: 20971562
May 28 12:16:00 feather systemd[1]: Reached target Sleep.
May 28 12:16:00 feather systemd[1]: Starting Suspend...
May 28 12:16:00 feather kscreenlocker_greet[4185]: UdevQt: unable to create udev monitor connection
May 28 12:16:00 feather ksmserver[1216]: CreateNotify: 54526000
May 28 12:16:00 feather kscreenlocker_greet[4185]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
May 28 12:16:01 feather kscreenlocker_greet[4185]: file:///usr/share/plasma/look-and-feel/org.kde.breath2.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
May 28 12:16:01 feather ksmserver[1216]: CreateNotify: 54526011
May 28 12:16:01 feather systemd-sleep[4193]: Suspending system...
May 28 12:16:01 feather kernel: PM: suspend entry (s2idle)
May 28 12:16:02 feather kernel: Filesystems sync: 0.060 seconds
May 28 12:16:02 feather kernel: dwmmc_rockchip fe310000.mmc: pre_suspend failed for non-removable host: -38
May 28 12:16:02 feather kernel: Freezing user space processes ... (elapsed 0.004 seconds) done.
May 28 12:16:02 feather kernel: OOM killer disabled.
May 28 12:16:02 feather kernel: Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
May 28 12:16:02 feather kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 28 12:16:02 feather kernel: PM: dpm_run_callback(): pm_runtime_force_suspend+0x0/0xd8 returns -16
May 28 12:16:02 feather kernel: PM: Device ff9a0000.gpu failed to suspend: error -16
May 28 12:16:02 feather kernel: PM: Some devices failed to suspend, or early wake event detected
May 28 12:16:02 feather kernel: OOM killer enabled.
May 28 12:16:02 feather kernel: Restarting tasks ... done.
May 28 12:16:02 feather kernel: PM: suspend exit
May 28 12:16:02 feather wpa_supplicant[923]: wlan0: CTRL-EVENT-DISCONNECTED bssid=38:94:ed:c5:0b:17 reason=3 locally_generated=1
May 28 12:16:02 feather systemd-networkd[518]: wlan0: Lost carrier
May 28 12:16:02 feather wpa_supplicant[923]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 28 12:16:02 feather systemd-sleep[4193]: Failed to suspend system. System resumed again: Device or resource busy
May 28 12:16:03 feather systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
May 28 12:16:03 feather systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
May 28 12:16:03 feather systemd[1]: Failed to start Suspend.
May 28 12:16:03 feather systemd[1]: Dependency failed for Suspend.
May 28 12:16:03 feather systemd-logind[886]: Operation 'sleep' finished.
This suspend issue is happening on my eMMC main installation, but also happens on a fresh SD card install of Manjaro ARM KDE 20.04 as well with the same error messages as above. Also, interesting to note that this Pinebook Pro also has actually successfully entered sleep state before - it will randomly work maybe 5% of the time, which hopefully is a good sign this is a software issue that can be fixed.
Loving this little machine other than this issue - Any help is greatly appreciated, thank you!
|
|
|
|
|