| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 171
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,718
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 264
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 119
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 217,067
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 219
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 303
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,091
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 940
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 606
|
|
|
| Keyboard keys rearrangable? |
|
Posted by: User 16030 - 01-11-2020, 02:17 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (6)
|
 |
I am considering getting a Pinebook Pro with ANSI keyboard. I am a Dvorak typist, so I would really want to move my keys to the Dvorak layout.
Can the Pinebook Pro's keys be removed and rearranged? Are all letter keys shaped identically so they fit in all places? This has been a problem on my Lenovo X200 for instance, as the keys around the TrackPoint are different, so I'm using blank keys (read: I sanded my keycaps) on there instead.
Note that the Dvorak layout only differs from QWERTY with letters and some other 'square' keys. Non-square keys like the spacebar, backspace, Shift, Ctrl and Tab are in the same place.
|
|
|
|
| Where can I learn to contribute? |
|
Posted by: goda90 - 01-11-2020, 12:35 PM - Forum: Linux on Pinebook Pro
- Replies (1)
|
 |
I just got my ANSI Pinebook Pro yesterday, and I'm already a fan. There are things I'd like to achieve and fix(for instance, running Android apps in Linux and properly hibernating), but, this being a young project, there aren't many tutorials, scripts etc. So I'd like to learn some skills and start working on things. I develop software professionally, but I've never done anything low level, or really even worked with Linux since college. Does anyone have some recommendations on resources for learning to work with the kernel and firmware, etc?
|
|
|
|
| Hibernate Manjaro -> NetworkManager doesn't start anymore |
|
Posted by: Gerhard - 01-11-2020, 12:19 PM - Forum: Linux on Pinebook Pro
- Replies (8)
|
 |
Hi,
today I pushed the button to hibernate the system but it didn' t wake up again. So I pushed the power button to restart the notebook.
Now sytemd can't start NetworkManager.service. There is a core-dump.
Is ist possible to make NetworkManager work again?
Code: [~]> systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service>
Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
└─NetworkManager-ovs.conf
Active: failed (Result: core-dump) since Sat 2020-01-11 18:15:>
Docs: man:NetworkManager(8)
Process: 835 ExecStart=/usr/bin/NetworkManager --no-daemon (cod>
Main PID: 835 (code=dumped, signal=ILL)
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Scheduled >
Jän 11 18:15:05 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Start requ>
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Failed wit>
Jän 11 18:15:05 b00k systemd[1]: Failed to start Network Manager.
#################
[~]> systemd-analyze critical-chain
The time when unit became active or started is printed after the "@>
The time the unit took to start is printed after the "+" character.
graphical.target @3min 32.222s
└─multi-user.target @3min 32.221s
└─smb.service @3min 31.895s +324ms
└─network-online.target @2min 1.625s
└─network.target @2.906s
└─NetworkManager.service @6.023s +352ms
└─dbus.service @2.598s
└─basic.target @2.588s
└─sockets.target @2.588s
└─dbus.socket @2.588s
└─sysinit.target @2.586s
└─systemd-timesyncd.service @2.222s +363ms
└─systemd-tmpfiles-setup.service @2.165s +51ms
└─local-fs.target @2.156s
└─run-user-1000-gvfs.mount @26.539s
└─run-user-1000.mount @22.150s
└─local-fs-pre.target @2.156s
└─lvm2-monitor.service @637ms +1.14>
└─lvm2-lvmetad.service @717ms
└─systemd-journald.socket @606ms
└─system.slice @328ms
└─-.slice @328ms
##################################
[~]> systemd-analyze blame
2min 57ms systemd-networkd-wait-online.service
1min 30.246s nmb.service
30.062s NetworkManager-wait-online.service
3.036s bootsplash-hide-when-booted.service
1.143s lvm2-monitor.service
898ms dev-mmcblk2p1.device
779ms systemd-logind.service
618ms systemd-random-seed.service
441ms systemd-udevd.service
389ms tlp.service
363ms systemd-timesyncd.service
353ms systemd-networkd.service
352ms NetworkManager.service
324ms smb.service
297ms systemd-journald.service
240ms user@1000.service
239ms polkit.service
184ms systemd-udev-trigger.service
138ms systemd-journal-flush.service
51ms systemd-tmpfiles-setup.service
39ms dev-hugepages.mount
39ms systemd-tmpfiles-setup-dev.service
35ms dev-mqueue.mount
34ms systemd-modules-load.service
33ms systemd-remount-fs.service
32ms sys-kernel-debug.mount
30ms systemd-sysctl.service
30ms systemd-rfkill.service
30ms tmp.mount
29ms systemd-backlight@backlight:edp-backlight.service
28ms user-runtime-dir@1000.service
27ms sys-fs-fuse-connections.mount
27ms systemd-update-utmp.service
27ms kmod-static-nodes.service
26ms systemd-user-sessions.service
##################################################
Jän 11 18:15:05 b00k systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
Jän 11 18:15:05 b00k systemd[1]: Dependency failed for Network Manager Wait Online.
Jän 11 18:15:05 b00k systemd[1]: Failed to start Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jän 11 18:15:05 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:05 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.
Jän 11 18:15:04 b00k systemd[1]: systemd-coredump@4-838-0.service: Succeeded.
Jän 11 18:15:04 b00k systemd-coredump[839]: Process 835 (NetworkManager) of user 0 dumped core.
Stack trace of thread 835:
#0 0x0000aaaae4aa8120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffa21674bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffa219e000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:04 b00k systemd[1]: Started Process Core Dump (PID 838/UID 0).
Jän 11 18:15:04 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4775] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4726] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:04 b00k NetworkManager[835]: <info> [1578762904.4725] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:04 b00k systemd[1]: Started Hide bootsplash after starting the system.
Jän 11 18:15:04 b00k systemd[1]: bootsplash-hide-when-booted.service: Succeeded.
Jän 11 18:15:04 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:04 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4.
Jän 11 18:15:04 b00k systemd[1]: systemd-coredump@3-828-0.service: Succeeded.
Jän 11 18:15:04 b00k systemd-coredump[829]: Process 825 (NetworkManager) of user 0 dumped core.
Stack trace of thread 825:
#0 0x0000aaaab078a120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffbdd794bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffbddb0000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:04 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:03 b00k systemd[1]: Started Process Core Dump (PID 828/UID 0).
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8540] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:03 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8492] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:03 b00k NetworkManager[825]: <info> [1578762903.8490] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:03 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:03 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 3.
Jän 11 18:15:03 b00k systemd[1]: systemd-coredump@2-819-0.service: Succeeded.
Jän 11 18:15:03 b00k systemd-coredump[820]: Process 816 (NetworkManager) of user 0 dumped core.
Stack trace of thread 816:
#0 0x0000aaaab3dbf120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffb61844bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffb61bb000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:03 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:03 b00k systemd[1]: Started Process Core Dump (PID 819/UID 0).
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0382] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jän 11 18:15:03 b00k systemd[1]: Started Network Manager.
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0315] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf)
Jän 11 18:15:03 b00k NetworkManager[816]: <info> [1578762903.0313] NetworkManager (version 1.22.4-1) is starting... (after a restart)
Jän 11 18:15:02 b00k systemd[1]: Starting Network Manager...
Jän 11 18:15:02 b00k systemd-logind[778]: Watching system buttons on /dev/input/event3 (HAILUCK CO.,LTD USB KEYBOARD System Control)
Jän 11 18:15:02 b00k systemd[1]: Stopped Network Manager.
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2.
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[477]: event1: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[472]: event5: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd[1]: systemd-coredump@1-799-0.service: Succeeded.
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[467]: event3: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd-coredump[801]: Process 796 (NetworkManager) of user 0 dumped core.
Stack trace of thread 796:
#0 0x0000aaaadbd66120 n/a (NetworkManager + 0x64120)
#1 0x0000ffffa0e654bc g_type_class_ref (libgobject-2.0.so.0 + 0x3d4bc)
#2 0x0000ffffa0e9c000 n/a (libgobject-2.0.so.0 + 0x74000)
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a6, and key code 225: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x700a5, and key code 224: Invalid argument
Jän 11 18:15:02 b00k systemd-udevd[473]: event4: Failed to call EVIOCSKEYCODE with scan code 0x70066, and key code 142: Invalid argument
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Failed with result 'core-dump'.
Jän 11 18:15:02 b00k systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=4/ILL
Jän 11 18:15:02 b00k systemd-udevd[464]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jän 11 18:15:02 b00k systemd-udevd[464]: Using default interface naming scheme 'v243'.
|
|
|
|
| How do I easily charge the watch? |
|
Posted by: Paranoid - 01-11-2020, 06:18 AM - Forum: General Discussion on PineTime
- Replies (18)
|
 |
Hi everybody,
my devkit recently arrived and I'd like to charge it.
This may come as a weird question to some, but how do I charge the watch? I need to hold the case closed with relatively much force for the contacts to remain securely closed. I've tried to put something more or less heavy on it while charging, but that didn't do the trick. Permanently closing the backplate with glue probably isn't a good idea either as I will need to flash it every now and then.
How are you guys doing that?
|
|
|
|
| Pebble/Rebble compat? |
|
Posted by: cscott - 01-10-2020, 11:47 PM - Forum: Development Discussion on PineTime
- Replies (3)
|
 |
Has anyone looked closely at the work the RebbleOS folks did in creating an open source version of the Pebble OS?
It seems to be based on FreeRTOS and the Pebble hardware is very similar, although presumably we'd only use the center 144x168 pixels of the display. https://github.com/PebbleA2/wiki/wiki/Watch-Comparison is a good summary of the pebble hardware. https://github.com/ginge/FreeRTOS-Pebble seems to be the main site for the pebble firmware reimplementation.
The main limitation seems to be that "the Pebble hardware is very similar", that is, PineTime doesn't have a lot of extra CPU, RAM, or Flash to play with. So the clone implementation can't cut corners, it would have to be at least as good as the original 2012 PebbleOS. And PineTime has a lot of features that Pebble doesn't...
Still, it would be really nice to be able to cross-compile some of the old pebble watchfaces and see them run on new hardware -- or better, upload a .pbw directly to the watch via bluetooth. https://developer.rebble.io/developer.pe...index.html documents the pebble APIs you'd need to reimplement. I looked but couldn't find any documentation on the PBW file format for watch faces. https://github.com/pebble-dev/neographics has a reimplementation of the pebble graphics APIs.
I'm interested in comparing notes with anyone who's thought hard about this.
|
|
|
|
Fn + F keys screwy for F9, F10, F11 and F12 |
|
Posted by: keithzg - 01-10-2020, 06:15 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (13)
|
 |
ANSI PBP, keyboard/touchpad firmware update applied. Using the Fn key with the keys on the top row, Esc through F8 seems fine:
Esc: Calls up the shutdown menu
F1: Brightness down
F2: Brightness up
F3: Seems to be the same as the Pine key? Presumably that's fine
F4: Mute
F5: Volume down
F6: Volume up
F7: Disables the trackpad
F8: Insert
However, F9 onwards seems wrong, both in what keycodes xev reports and in observed behaviour:
F9: Label says Print Screen, but instead Num_Lock
F10: Label says NumLK, but instead Scroll_Lock
F11: Label says ScrLK, but instead Pause
F12: Label says Pause Break, but instead Num_Lock
Other blue-label keys (ie. the numberpad keys, delete, home/end, page up/down) all seem to be mapped as expected.
|
|
|
|
| PBP ANSI Keyboard Mapping Issue |
|
Posted by: JaredT66 - 01-10-2020, 05:42 PM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
 |
All, just dropping a note. Just opened my PBP and everything looks good. Only issue I found was that while typing the double quote '"' and the at '@' were reversed. It appears that this is because the default keyboard mapping was set to English(UK) instead of English(US).
After changing it seems to be working as expected!
-Jared
|
|
|
|
|