Today, a new version of postmarketos-mkinitfs tried to install when I ran apk upgrade.
However, the trigger script errored out, so it couldn't install the upgrade. I ran apk fix to try and redo the installation, but it failed again.
Code:
pinephone:~$ sudo apk fix
(1/1) Reinstalling postmarketos-mkinitfs (0.12.1-r1)
Executing busybox-1.31.1-r20.trigger
Executing postmarketos-mkinitfs-0.12.1-r1.trigger
==> initramfs: creating /boot/initramfs-postmarketos-allwinner
Scanning kernel module dependencies...
NOTE: ** modprobe warnings below can be ignored ** if your device does not run the
mainline kernel yet (most devices!) or if the related kernel options are enabled
with 'y' instead of 'm' (module).
- deviceinfo: sun6i_mipi_dsi sun4i_drm pwm_sun4i sun8i_mixer
- 00-default.modules: dm_crypt ext4 usb_f_rndis
==> kernel: device-tree blob operations
==> kernel: copying dtb allwinner/sun50i-a64-pinephone-1.1 to boot partition
==> initramfs: creating uInitrd
Image Name: uInitrd
Created: Sun Jun 14 23:09:53 2020
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 1427565 Bytes = 1394.11 KiB = 1.36 MiB
Load Address: 00000000
Entry Point: 00000000
==> kernel: creating uImage
mkimage: Can't open /boot/vmlinuz-postmarketos-allwinner: No such file or directory
ERROR: postmarketos-mkinitfs-0.12.1-r1.trigger: script exited with error 1
Executing postmarketos-base-3-r34.trigger
Configuring a getty on port ttyS0 with baud rate 115200
OK: 1420 MiB in 583 packages
pinephone:~$ ls /boot/
initramfs-postmarketos-allwinner uImage-postmarketos-allwinner
sun50i-a64-pinephone-1.1.dtb uInitrd-postmarketos-allwinner
Running apk fix, it gets picked up as improperly installed again.
The file it is looking for does not exist, there is an ls output at the bottom.
Any ideas? It'd be much appreciated.
I've had it for a few weeks and was using it today. Installing QT5 so that I could eventually flash the new 20.6 i3 that strit just put out.
I heard a tiny "pop", screen went blank, and now, it won't boot. Battery was charging with 5V3A charger, had it hooked up to Auzai external monitor, and installing QT5. Battery was a little warm under the bottom, but not red hot.
I think I now have a brick. Any recommendations?
OK, good news, D-0 is back (yes, I have my PBP themed for a Star Wars droid, complete with ogg sound-clips and custom wallpaper).
After he cooled off for about an hour, I plugged in the power adapter and was then able to boot the machine.
I'm wondering if this is a thermal failsafe? Does the board or batteries shut off with high temp?
The battery life of my PBP is really good, I get 8+ hours with my usage (browsing, bit of vnc, paying attention to brightness levels).
However, I have some problems with suspend to ram.
First, it wasn't always going into suspend to ram, though since some updates yesterday, this seems to have been fixed.
Second, when suspending to ram, after 2.5 hrs the battery still lost about 13% (82% to 69%), so that's barely better than keeping it running.
Is that normal?
The reason I ask: I have a Huawei tablet (M5 Lite) which runs seemingly forever, but also when just leaving it, it does fetch update information (so at some point wifi and other stuff is somewhat active), but otherwise it will lose about 20% in a week or more. I unplugged it this morning and it just sat idle all day, and just now it still has 100% charge...
Then another question: is it possible to do a suspend to disk? Or are there special reasons why that isn't recommended?
On my commute, there's a crap data connection, so I'd like to load a bunch of webpages at home or at work, then read on the go. With suspend to ram consuming a lot of battery, esp. when forgetting about it at work, I'll be stuck with a dead battery...
Any thoughts?
[Edit 2020-06-21 after getting proper suspend to ram working]
I got my Pinebook Pro in May 2020, these fixes are therefore for an ootb Manjaro 19 PBP.
With the guidance in this thread below I managed to get to where I'm at now.
My PBP is up to date in terms of software updates, so it already runs kernel 5.7.0-1-MANJARO-ARM. Kernel 5.6+ is one of the prerequisites for proper suspend to ram.
With dmesg and journalctl -f I could figure out that the sleep mode (closing the lid or Fn+ESC = Zz) was indeed not really suspend to ram.
I modified /etc/systemd/sleep.conf
#SuspendState=freeze
SuspendState=mem
and disallowed any Hibernate lines, not sure if that would be necessary, so just in case.
I installed bsp uboot, package name and version: uboot-pinebookpro-bsp (1.5-7), which tells me this at the end of the installation:
A new U-Boot version needs to be flashed our install drive. Please use lsblk to determine your drive, before proceeding.
You can do this by running:
# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblkX seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblkX seek=24576 conv=notrunc
Transaction successfully finished.
lsblk outputs this:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk2 179:0 0 58.2G 0 disk
├─mmcblk2p1 179:1 0 213.6M 0 part /boot
└─mmcblk2p2 179:2 0 58G 0 part /
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
zram0 252:0 0 5.6G 0 disk [SWAP]
So then I had to do this:
# dd if=/boot/idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc
after which a reboot got me to functional suspend to ram - I can see that the CPUs are put to sleep with journalctl, and overnight, the battery lost less than 3%.
Posted by: Quim - 06-14-2020, 02:02 PM - Forum: Getting Started
- No Replies
Hi everybody,
I am starting to learn how to program with the nRF52 and I have decided to start with the PineTime64.
I would like to know which ID is better to start developing with the device and with the software that comes with the smartwatch (if possible). I have a Segger JLINK programmer, will it be a good option the Segger Embedded studio to modify this repository and make my modifications?
Hi
I compile software using freepascal and fpgui for customers on Windows, Linux, MacOS and Raspian.
I am currently using my Pi as a WiFi router so I was sort of tempted to buy a Pi4 to replace it. But Pi's are such a faff with cables and SD cards and maybe I would just be better to get a Pinebook Pro.
Can I essentially treat a Pinebook Pro as a Pi laptop? It seems to use a similar processor as a Pi 4.
Would I be able to run 32 bit Raspbian binaries on it?
and I can install freepascal and Lazarus-IDE on it right?
If I buy one then I'll be most likely using Debian.
A laptop with a long battery life and a proper UART would be kind of cool.
thanks, DNJ
1) One of the pictures I saw of the internals of the PineTab showed a SSD installed, but I did not see that adapter in the store.
IS it or will it be available ?
2) Will it be possible to add a phone/data modem ?
3) Can the 64gb eMMC be upgraded to a 128gb, or perhaps larger ?
The speaker placement in the picture, kinda wish they were forward pointing instead of rear pointing.
It looks like the sides of the screen bezel would support forward facing speakers.
I just got my PBP two weeks ago. My trackpad is a bit cumbersome.
First and foremost, it seems not to be properly seated. Please see the photo.
I'm not quite sure if it is an assembly problem that I can fix, or if they "just are like that". Any idea?
Next, I have trouble to get a three finger tap to be recognized (middle mouse button), so I have configured Manjaro/KDE to take a right top and left top corner tap as middle button. According to xev (xorg-xev package) no three finger tap ever gets detected. The two finger tap for right mouse button is also not registered half the time.
I don't think that my device was made in 2019, should I do the keyboard firmware update? Or how can I tell if mine is from last year or this one?
Hello friends... I have received my first few batches of Pine hardware, specifically a USA version of the PineBook Pro, the PineTime developer kit, a clusterboard, and 7 modules. I have a PinePhone on order but no information on expected arrival.
I would like to start learning to program the PineTime but all the forum postings I have read so far refer to programming the watch using an Android phone, which I don't happen to own. So I have some easy questions, in no particular order...
Can I develop firmware for the PineTime using my PineBook Pro?
Can I do any of this before I receive my PinePhone or am I out of business until then?
Is my iPhone 7Plus of any value in this matrix in the mean time?
I have a j-link mini (edu) and a j-link edu. Can either of these be used to program the PineTime using OpenOCD?
Or do I need to buy something else specifically? If so what?
I am really looking forward to getting started :-)
I couldn't find anything on what to put where on the SD card for a successful SD boot (other than looking at existing OS images to see where they put stuff), or how to install a new u-boot (and particularly testing it without bricking the device), etc.
Is any such information available?
