void-linux / void-linux/void-docs

Add Pinephone Documentation to the Void Docs

Open
#518 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
217
Forks
212
Avg merge
2d 21h
Merged PRs (30d)
1

Description

I got void linux working on my pinephone is a slightly hacky way. I talked a bit with the maker of u-boot and p-boot that made an image with 13 distros to try out stuff on the pinephone.

The article I followed was here: https://xnux.eu/howtos/install-arch-linux-arm.html

However, this did not work as the author changed up the repos somewhat for newer stuff to be accomplished.
When I talked with him, we decided to flash the void linux aarch64 ROOTFS over one of the distros in the multi boot image ( I booted over maemo), and it does successfully boot, although I am taking the the void linux terminal login which I am not sure what I can do not (will probably attach my keyboard and trying building plasma mobile from scratch)

I think void linux would be a good distro for the pinephone as it has both musl and glibc and is rolling release.

I talked with someone else and they said they did void working by using void-mklive, but it is not clear how the general user would use that versus some of these premade images.
If we could get some step by step guide for getting void on the pinephone or a prebuilt image, that would be super sweet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Arch Linux ARM article and the Void mklive approach described in the issue, then determine which PinePhone installation method is supportable. Done means providing a tested step-by-step guide or a clearly supported prebuilt image path for general users.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.