Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PP Pro support #12

Open
fbmoose48 opened this issue Dec 16, 2021 · 6 comments · May be fixed by #14
Open

PP Pro support #12

fbmoose48 opened this issue Dec 16, 2021 · 6 comments · May be fixed by #14
Labels
enhancement New feature or request

Comments

@fbmoose48
Copy link

Can this be updated to include PinePhone Pro as an option?

@Danct12 Danct12 added the enhancement New feature or request label Dec 26, 2021
@Danct12
Copy link
Member

Danct12 commented Dec 26, 2021

Yes. So far the squash rootfs needs to be built, and the partition table needs to be changed too.

@alien2003
Copy link

I'm also interested in PPP support. It would be also nice to have keyboard-compatible DEs available

@fbmoose48
Copy link
Author

Can https://github.com/dreemurrs-embedded/arch-pine64-build build the squash rootfs? What needs to be changed regarding partition table?

@Danct12
Copy link
Member

Danct12 commented Feb 11, 2022

Yes, there is an option --osk-sdl which does it. There's nothing much need to be changed in this script except don't use the first 32MB on Rockchip platform.

@crispy-landslide
Copy link

I attempted to modify the script, but it does not appear to be working. I just used the pinephone-pro sqfs from DOWNLOAD_SERVER.

  1. I added the option to set DEVICE to pinephone-pro
select OPTION in "PinePhone" "PinePhone Pro" "PineTab"; do
    case $OPTION in
        "PinePhone" ) DEVICE="pinephone"; break;;
        "PinePhone Pro" ) DEVICE="pinephone-pro"; break;;
        "PineTab" ) DEVICE="pinetab"; break;;
    esac
done
  1. I changed the partitions if using pinephone-pro so that the boot partition starts at 32MB, otherwise it starts at 0%
sudo parted -a optimal ${DISK_IMAGE} mklabel msdos --script
if [ $DEVICE == "pinephone-pro" ]; then
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary fat32 32MB 256MB --script
else 
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary fat32 '0%' 256MB --script
fi
sudo parted -a optimal ${DISK_IMAGE} mkpart primary ext4 256MB 100% --script
sudo parted ${DISK_IMAGE} set 1 boot on --script
  1. Finally, I changed the dd commands if using pinephone-pro
if [ $DEVICE == "pinephone-pro" ]; then
  sudo dd if=${TMPMOUNT}/boot/idbloader.img of=${DISK_IMAGE} seek=64 conv=notrunc,fsync
  sudo dd if=${TMPMOUNT}/boot/u-boot.itb of=${DISK_IMAGE} seek=16384 conv=notrunc,fsync
else 
  sudo dd if=${TMPMOUNT}/boot/u-boot-sunxi-with-spl-${DEVICE}-552.bin of=${DISK_IMAGE} bs=8k seek=1
fi

I get no errors when flashing an SD card with these changes to the script. When I try to start the phone, it hangs on the splash screen and does not go further.

Am I on the right track here?

@crispy-landslide
Copy link

I get the following error when trying to boot after installing with this modified script.

cdn-dp fec00000.dp: Direct firmware load for rockchip/dptx.bin failed with error -2

I'm not sure what needs to be modified to make this script work.

I've also tried changing the partitions based on sectors, but I get the same result.

sudo parted -a optimal ${DISK_IMAGE} mklabel msdos --script
if [ $DEVICE == "pinephone-pro" ]; then
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary fat32 65536s 589823s --script
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary ext4 589824s 100% --script
else 
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary fat32 '0%' 256MB --script
  sudo parted -a optimal ${DISK_IMAGE} mkpart primary ext4 256MB 100% --script
fi
sudo parted ${DISK_IMAGE} set 1 boot on --script

@crispy-landslide crispy-landslide linked a pull request Mar 6, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants