Unfortunately, running Waydroid suceeds with the first start only. After app exit or phone reboot - not anymore. I’m on manjaro-arm phosh on the PinePhone and still experience this issue after reflashing Manjaro. Any suggestions?
EDIT: It is working again with the following workaround.
Missing user permissions to r/w waydroid.log was the root of evil. For brief instructions, please see
https://githubmemory.com/repo/Anbox-halium/anbox-halium/issues/84
Well it happened again, Strit. This update killed my NVMe SSD boot, just like before.
Because the updated system will no longer boot from NVMe, I booted from an SD card and copied the NVMe boot partition files over to my eMMC memory and changed extlinux.conf and /etc/fstab to boot from eMMC. It now boots from eMMC (/ is on NVMe and /boot is on eMMC) but I’m frustrated that these Manjaro updates have twice broken my NVMe boot! The cause is still unknown but last time I had to fully install a new release image to get NVMe boot back.
From my /var/cache/pacman/pkg/ contents, it appears that I have successfully updated this system twice with new kernels:
linux-5.14.1-1-aarch64.pkg.tar.zst
linux-5.14.2-1-aarch64.pkg.tar.zst
linux-5.14.8-1-aarch64.pkg.tar.zst
but 5.14.8-1 seems to have created a problem with NVMe boot.
I’ll try regressing back to the 5.14.2-1 kernel and switch the files back to NVMe boot and see what happens but I might not have time to do it for a day or two.
Regression back to the 5.14.2-1 kernel did not restore NVMe boot that was previously working after installing a recent Manjaro XFCE release.
Booting the NVMe system (NVMe /) from eMMC (eMMC /boot) continues to work but when I move the /boot files from eMMC to NVMe and change /etc/fstab to mount /boot on NVMe, it still fails to boot after the regression.
I might try regressing to 5.14.1-1 next or I might just live with eMMC boot, though I’d like to remove my eMMC entirely, if NVMe boot ever becomes sufficiently reliably for me to risk flashing U-boot to SPI.
I’ve noticed that initramfs varies in size considerably between linux versions. Why?
8410175 Oct 2 09:56 initramfs-linux.img
30624256 Sep 8 02:43 Image
vs.
13213087 Aug 22 10:50 initramfs-linux.img
31205888 Aug 18 00:33 Image
Hello,
Sorry to comeback with that, but 3D slicers like Cura or PrusaSlicer still cannot launch. They used to work like a charm, but since about this summer, I tried what I could (not much) to fix it. I got the same problem as here described
[ray@pi4 ~]$ cura
Traceback (most recent call last):
File “/usr/bin/cura”, line 25, in
import pynest2d # @UnusedImport
ValueError: PyCapsule_GetPointer called with incorrect name
In
Any ideas?
Thank you
For some reason Arch Linux ARM does not seem to have been able to build the recent releases of both Cura and PrusaSlicer.
Their PKGBUILD is updated (because they get it directly from Arch x64, but the package is not in the repo, so I assume it is failing to be built.
Edit 1
Test building both Cura and Prusa-Slicer now.
Cura just built without issues. So will upload that to unstable branch later.
Prusa-Slicer was missing a dependency, since one of it’s dependencies dropped it recently. But it’s building after adding that. If/When it finishes, I will upload that to unstable branch as well.
Edit 2
Both packages built, just uploaded them to our unstable branch. No idea if they work or not, haven’t tested them. So if you can test them, @Ada, that would be awesome!
Do you have any problems with WiFi on Pinebook Pro after “cold” boot when the device was charged using USB-C (when the device was turned off)? By the “problems” I mean WiFi working extremely slow or not working at all. Turning off and on “fixes” it.