| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,699
» Latest member: bigyoshi
» Forum threads: 16,260
» Forum posts: 117,188
Full Statistics
|
| Latest Threads |
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Today, 02:02 AM
» Replies: 8
» Views: 15,507
|
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
Yesterday, 08:25 PM
» Replies: 1
» Views: 205
|
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
11-21-2025, 08:45 PM
» Replies: 1
» Views: 126
|
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 105
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 603
|
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 168
|
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 475
|
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,166
|
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 101
|
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 102
|
|
|
| Connected to 4k (3840x2160) monitor but I can only select upto 1920x1080 resolution |
|
Posted by: NigelT - 01-11-2020, 10:49 PM - Forum: Linux on Pinebook Pro
- Replies (4)
|
 |
Hello all,
I'm a new Pinebook Pro owner, new to this forum and this is my first post.
My PBP is connected to an LG 32UD89-W monitor via USB-C cable.
The cable goes direct from the PBP's USB-C port to the monitors USB-C port. The USB-C cable is new and came included with the monitor.
It works but I'm limited to 1920x1080 resolution and unable to select the monitor's native 4k resolution.
This LG monitor is the only monitor I have that has a USB-C input (as well as HDMI inputs), and the PBP is the only device I have with a USB-C output. My other devices (PCs and a Raspberry PI) have HDMI outputs and run this monitor OK at 4k.
The monitor is:
https://www.lg.com/us/monitors/lg-32UD89...ed-monitor
The PBP is running the default Debian OS plus MrFixit's updates as of 10 Jan 2019.
During boot the open sesame splash screen is mirrored on both the built-in panel and the external monitor, and so also is the login/ greeter screen that appears a couple of seconds later.
Once logged into the desktop the monitor resolution is only 1920x1080, not the native 4k/3840x2160.
Control Center->Displays, and xrandr report the resolution as 1920x1080, but do not offer any higher options.
I have turned the built-in panel off so the only output is the external monitor.
I can change resolutions of the monitor from a maximum of 1920x1080, though 1280x720 and 1024x768 to a minimum of 720x480.
However the resolution I want to use, 4k (3840x2160), is not available as an option.
xrandr shows the same mode options as the "Control Center" UI
Code: rock@Debian-Desktop:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
1920x1080 59.99 +
1024x768 60.00
800x600 60.32 56.25
848x480 60.00
640x480 59.94
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
1920x1080 60.00*+
1280x720 60.00
1024x768 60.00
720x480 59.94
rock@Debian-Desktop:~$
And this also agrees with
Code: root@Debian-Desktop:~# cat /sys/devices/platform/display-subsystem/drm/card0/card0-DP-1/modes
1920x1080p60
1280x720p60
1024x768p60
720x480p60
root@Debian-Desktop:~#
If I connect the same LG monitor to my other PC (via HMDI) or my Raspberry PI4B (via HDMI), it shows more modes (including 3840x2160), and I can select and use 4k resolution on these devices, just not the PBP.
Modes when plugged into a PI4B
Code: root@raspberrypi:~# cat /sys/devices/platform/soc/soc:gpu/drm/card1/card1-HDMI-A-1/modes
3840x2160
2560x1440
1920x1080
1600x900
1280x1024
1280x800
1152x864
1280x720
1024x768
800x600
720x480
640x480
Something I've noticed on the PBP, but don't know if it is related, is the speeds below in dmesg, is this a negotiated USB-C speed? I wonder if my setup is negotiating a speed too slow for 4k? (I know very little about about USB-C so am guessing at this)
Code: root@Debian-Desktop:~# dmesg | grep -i mbps
[ 4.274459] cdn-dp fec00000.dp: 1620Mbps x 4lanes
[ 32.651935] cdn-dp fec00000.dp: 1620Mbps x 4lanes
[ 342.594439] cdn-dp fec00000.dp: 1620Mbps x 4lanes
[ 3255.050333] cdn-dp fec00000.dp: 1620Mbps x 4lanes
[ 3261.161106] cdn-dp fec00000.dp: 1620Mbps x 4lanes
[ 3327.898880] cdn-dp fec00000.dp: 5400Mbps x 4lanes <==== Note this is 5400 and the rest are 1620
[ 3359.093808] cdn-dp fec00000.dp: 1620Mbps x 4lanes
root@Debian-Desktop:~#
Another thing I've noticed, but again do not know if it is related. This monitor's EDID as returned to the PBP via USB-C is an EDID version 1.4 with a preferred mode of 6, whereas the EDID from the same monitor as returned to a Pi4 via HDMI is an EDID version 1.3 with a preferred mode of 10.
EDID as seen by PI4B over HDMI cable
Code: root@raspberrypi:~# parse-edid < /sys/devices/platform/soc/soc:gpu/drm/card1/card1-HDMI-A-1/edid
Checksum Correct
Section "Monitor"
Identifier "LG Ultra HD"
ModelName "LG Ultra HD"
VendorName "GSM"
# Monitor Manufactured week 7 of 2018
# EDID version 1.3
# Digital Display
DisplaySize 600 340
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-135
VertRefresh 48-61
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1152x864, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1280x800, 60Hz
#Extension block found. Parsing...
#WARNING: I may have missed a mode (CEA mode 97)
#WARNING: I may have missed a mode (CEA mode 96)
#WARNING: I may have missed a mode (CEA mode 93)
#WARNING: I may have missed a mode (CEA mode 94)
#WARNING: I may have missed a mode (CEA mode 95)
Modeline "Mode 10" +hsync -vsync
Modeline "Mode 0" +hsync +vsync
Modeline "Mode 1" +hsync -vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 11" +hsync -vsync
Option "PreferredMode" "Mode 10"
EndSection
root@raspberrypi:~#
Whereas EDID as seen by PBP over USB-C
Code: root@Debian-Desktop:~# parse-edid < /sys/devices/platform/display-subsystem/drm/card0/card0-DP-1/edid
Checksum Correct
Section "Monitor"
Identifier "LG Ultra HD"
ModelName "LG Ultra HD"
VendorName "GSM"
# Monitor Manufactured week 7 of 2018
# EDID version 1.4
# Digital Display
DisplaySize 600 340
Gamma 2.20
Option "DPMS" "true"
Horizsync 30-135
VertRefresh 56-61
# Maximum pixel clock is 560MHz
#Not giving standard mode: 1152x864, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1280x800, 60Hz
#Extension block found. Parsing...
Modeline "Mode 6" +hsync +vsync
Modeline "Mode 0" +hsync -vsync
Modeline "Mode 1" +hsync -vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 7" +hsync -vsync
Option "PreferredMode" "Mode 6"
EndSection
Is there something extra I need to do to enable 4k / 3840x2160 resolution via USB-C on an external monitor ?
In the meantime I'm going to purchase a USB-C to HDMI adapter and see if that makes a difference.
|
|
|
|
| Brand new system locked up after ~1hr |
|
Posted by: peetee - 01-11-2020, 08:00 PM - Forum: General Discussion on Pinebook Pro
- Replies (5)
|
 |
Hi everyone,
After waiting patiently for a few months, I opened my (ANSI) PBP and ran through the routine of updating it and patching the trackpad. No problems. Then I was cloning a github repo and the UI desktop locked up... no responsiveness at all. The mouse stopped moving, no keypresses were recognized. I long-pressed the power button to shut it off, and put it on the charger.
I came back to the system about an hour later and tried to power it on. The green LED on the keyboard lights up, but there is no sign of life on the monitor... it appears to be completely dead. I've tried several more times (eight to ten), there is no change. The keyboard LED lights up when I press the power button, but the screen is 100% black, with no flicker of activity whatsoever.
Please let me know what my next steps are.
|
|
|
|
| (almost) upstream uboot/atf |
|
Posted by: User 15997 - 01-11-2020, 04:21 PM - Forum: Pinebook Pro Tutorials
- Replies (27)
|
 |
for anyone wishing to use upstream uboot/atf, here's a guide on how to do that: https://eno.space/blog/2020/01/pbp-uboot.
behaviour of this version should be similar to the BSP uboot, no changes to the boot.txt files are necessary.
for the curious:
- boot order is SD, USB, eMMC
- atf and uboot used were very recent at the date of posting
- baudrate is 1500000, like BSP uboot
- LEDs light as soon as uboot starts running
|
|
|
|
| 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?
|
|
|
|
|