I recently bought a replacement lcd screen for my Pinephone pro. But after connecting everything there is no image on the screen. The backlight turns on and I get feedback from the touchscreen. The LED indicator also briefly flashes green during boot up. When I put back the original display which is damaged it displays an image. What could cause the new display to not show an image? The flex cable does not appear to be damaged in any way.

Would it be possible for pine to develope an open source cable modem where we can have full access to the whole file system, except the speed file that tells you what you are provisioned for.

Would it be possible for pine to develope an open source cable modem where we can have full access to the whole file system, except the speed file that tells you what you are provisioned for.

I've been attempting to install Waydroid (with these instructions https://wiki.debian.org/Mobian/How-to#Ho...a_Waydroid, which links to: https://docs.waydro.id/usage/install-on-desktops). And for some reason it appears apt is attempting to use urls that just don't work (Failed to fetch...). After some URL exploring it looks like the last part of the url is wrong... And I have ran apt update & apt upgrade

Any ideas why this is happening and/or are there better directions out there?

Heres the command output of 'apt install' & 'cat /etc/os-release' for system version info.

sudo apt install waydroid
[sudo] password for mobian:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  apparmor arch-test bridge-utils busybox-static
  cloud-image-utils debootstrap distro-info
  distro-info-data fakechroot genisoimage
  ibverbs-providers libaio1 libboost-thread1.74.0
  libdistro-info-perl libfakechroot libfmt9
  libgbinder libgfapi0 libgfrpc0 libgfxdr0
  libglibutil libglusterfs0 libibverbs1 libiscsi7
  liblxc-common liblxc1 libpam-cgfs librados2
  librbd1 librdmacm1 libssh-4 libsubid4 liburing2
  lxc lxc-templates lxcfs mmdebstrap
  python3-gbinder qemu-block-extra qemu-utils
  uidmap uuid-runtime
Suggested packages:
  apparmor-profiles-extra apparmor-utils ifupdown
  mtools squid-deb-proxy-client
  ubuntu-archive-keyring shunit2 wodim cdrkit-doc
  btrfs-progs lvm2 python3-lxc qemu-user-static
  apt-transport-tor genext2fs perl-doc qemu-user
  squashfs-tools-ng
The following packages will be REMOVED:
  busybox
The following NEW packages will be installed:
  apparmor arch-test bridge-utils busybox-static
  cloud-image-utils debootstrap distro-info
  distro-info-data fakechroot genisoimage
  ibverbs-providers libaio1 libboost-thread1.74.0
  libdistro-info-perl libfakechroot libfmt9
  libgbinder libgfapi0 libgfrpc0 libgfxdr0
  libglibutil libglusterfs0 libibverbs1 libiscsi7
  liblxc-common liblxc1 libpam-cgfs librados2
  librbd1 librdmacm1 libssh-4 libsubid4 liburing2
  lxc lxc-templates lxcfs mmdebstrap
  python3-gbinder qemu-block-extra qemu-utils
  uidmap uuid-runtime waydroid
0 upgraded, 43 newly installed, 1 to remove and 0 not upgraded.
Need to get 5,445 kB/27.0 MB of archives.
After this operation, xxx MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://deb.debian.org/debian bookworm/main arm64 qemu-utils arm64 1:7.2+dfsg-7
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:2 http://deb.debian.org/debian bookworm/main arm64 debootstrap all 1.0.128+nmu2
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:3 http://deb.debian.org/debian bookworm/main arm64 distro-info-data all 0.58
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:4 http://deb.debian.org/debian bookworm/main arm64 distro-info arm64 1.5
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:5 http://deb.debian.org/debian bookworm/main arm64 liblxc1 arm64 1:5.0.2-1
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:6 http://deb.debian.org/debian bookworm/main arm64 liblxc-common arm64 1:5.0.2-1
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:7 http://deb.debian.org/debian bookworm/main arm64 libpam-cgfs arm64 1:5.0.2-1
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:8 http://deb.debian.org/debian bookworm/main arm64 lxc arm64 1:5.0.2-1
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:9 http://deb.debian.org/debian bookworm/main arm64 lxcfs arm64 5.0.3-1
  404  Not Found [IP: 2a04:4e42:44::644 80]
Err:10 http://deb.debian.org/debian bookworm/main arm64 qemu-block-extra arm64 1:7.2+dfsg-7
  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/q..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/d...u2_all.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/d...58_all.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/d..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/l..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/l..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/l..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]E: Failed to fetch http://deb.debian.org/debian/pool/main/l..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]


E: Failed to fetch http://deb.debian.org/debian/pool/main/l..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Failed to fetch http://deb.debian.org/debian/pool/main/q..._arm64.deb  404  Not Found [IP: 2a04:4e42:44::644 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

mobian@mobian:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Hey hey
I want an app that allows me to do continuous heart rate monitoring with the pine time. I'm interested in tracking my heart rate variability to see when I've slept well or not, etc. And also tracking my heart rate during exercise to see how it responds to sleep etc. I have been using " sleep as Android" with the pine time occasionally But I also want continuous heart rate tracking when I'm awake.

Since my last upgrade of the KDE danctnix software there is an issue when powering off the pinetab: a messsage "A stop job is running for Network Manager" appears, which suspends power off.The kernel is 6.8.0-danctnix1-1-pinetab2. Any recommendations to avoid this?

I'd like to verify the rating of some USB-C cables according to their E-Marker chips. Can the pencil power delivery debug menu be used to read this data from the chips?

Hi everybody,

I'm new to building Linux and related components for embedded systems. I found the work that @Fishwaldo has done with `meta-pine64`, however I'm having trouble visualising the entire process. I'd like an ELI5 for a few topics so I can try building my own images.

My questions are (as of now):

1. How did you figure out the U-boot partitions required? The U-boot documentation (https://docs.u-boot.org/en/latest/board/...l#flashing) uses 4KiB for the SPL and 8KiB for U-boot + OpenSBI. However, the JH7110 user-guide (https://doc-en.rvspace.org/VisionFive2/D...oot_UG.pdf) doesn't seem to mention this (or does it? Not sure if I missed something important). How did you know?

2. If I understand correctly, Fishwaldo patched the Linux Kernel tree in a new branch with the OEM drivers from StarFive? Then, he created the layer on top of Poky and the other base layers from Openembedded? Why is it that he is forced to use the Linux 5.1xx kernel instead of the new 6.1xx kernel? Did StarFive mention this limitation somewhere that I missed it?

Thanks for reading through! I really appreciate the help - I would like to be part of the effort to take RISC-V forward, and I want to be able to build my own images for the Star64 alongside the SOEdge module as a replacement for Coral.ai's TPUs.

Thanks!

Like many of you, I came across the work that @Fishwaldo did to get Linux working on the Star64.

I'm new to Yocto and the lower level of building Linux for embedded systems. I would love it if someone/Fishwaldo could do an ELI5 on what he did for the `meta-pine64` layer (btw, there seems to be a different `meta-pine64` layer mentioned on the openembedded page but that's specifically for ARM chips).

From what I understand:

1. He forked/branched off the Linux kernel.
2. Applied OEM drivers as patches from StarFive.
3. Used that in the new Yocto layer he built.

My questions (for now) are:

1. How did he/you guys find the U-boot partition map? I have seen the JH7110 Boot User Guide, but I haven't been able to figure out how U-boot mentions the partition sizes in their documentation.
2. I couldn't quite find where StarFive mentions that their drivers are not compatible with the newer 6.1xx Linux kernel, forcing @Fishwaldo to use the 5.1xx kernel. Ideally, one would be able to download the source tree and place the patches in the tree to compile it with bitbake in Yocto, yes?

Would greatly appreciate any replies to this thread! I'm very new to this, and I would like to be a part of the effort to take RISC-V forward, even if I'm only doing it for myself. I'm looking at the Star64 alongside the OSEdge as an alternative to Coral.ai's TPUs and would like to learn to build my images for both of them.

Thanks!

Hello!

I've been considering getting myself a Pinebook Pro, but I check again every year or so and the hardware hasn't been updated it seems. Are there any plans for 8GB RAM or a newer ARM CPU?

Cheers!