Hi everyone,

I have recently registered an account to join the forums and I received no confirmation email at first, I later found it in the spam folder of my gmail account.
The header says:

Quote:Why is this message in spam? It is in violation of Google's recommended email sender guidelines.

Hi Everyone,

I will update this post, which effectively serves as a log, when improvements are made to the default Debian with Mate build by @Mrfixit2001  for the Pinebook Pro. Perhaps this is obvious, but the development for this build is ongoing and continues despite the device not being shipped out yet (at the time of writing).

Please provide all feedback regarding this OS build, and ONLY this OS build, in this thread.

N.B. Once you get your unit make sure to use the update script on first boot [icon next to time/date] to download the new kernel, device tree and various other improvements.
N.B. ii. Perform the initial update on full battery charge. If the battery is partly drained, the update will temporarily cause a faulty battery calibration / software power read. This however is not a permanent issue, and does not cause damage to any components, but it may at take one charge/discharge cycle to correctly re-calibrate.  
[edit 25/11/2019]

Changing Username and Home Directory
Log into root (root/root) and open the termial. To change the username and home directory name type the following, replacing  NewUser with your desired username:

On thing I have been doing on my Linux computers at home for more than 8 years, is use ABEs, (aka Alternate Boot Environments).

Let's say you have a perfectly functional OS load. A few weeks later you want to update. Do you over-write the working OS load? (Even if you have backups...) Or would you prefer to keep your cake, (aka OS load), and eat it too, (update to an alternate location)?

Here is a description of the ABEs possible with Linux. I've actualy used 1, 3 & 4, and tested that 2 works.

 - Separate root partitions. Copy the existing one to the off-line one before update. Boot off the new copy to make sure it's botable, then update. Keep your home partition, (and anything else un-related to the OS), separate from root partition to reduce the amount of duplicated storage. Dis-advantage is that you have to have 2 full root partitions, (like 20GB per root).

 - Use Linux LVM with 2 root partitions. Same as above, but you can also perform R/O snapshots if you leave free space in the volume group.

 - Use BTRFS. Have a separate tree for root. Make R/W snapshots when updating. Still keep non-root / OS data out of the root / OS tree. Each extra BE takes up only as much as had been changed, (it's copy on write).

 - Use ZFS. Have separate tree for root. Make snapshot & clones when updating. Still keep non-root / OS data out of the root / OS tree. Each extra BE takes up only as much as had been changed, (it's copy on write).

This methodology is also good for a new kernel. You may have to update drivers and support software, which if it goes badly, that BE, (aka Boot environment), may become un-bootable. Having an ABE with the old funtional kernel can save you from headaches.

My Grub entries become a bit more complex. Basically at least 1 per BE, and 1 per kernel update. Plus, I have little incentive to delete too many. I generally keep perhaps 5 or 6 BEs. They also act as on-line backup.

If there is interest, I can describe them in more detail. I am most familar with 1 & 4. But have used 3, just not recently.

Does anyone know of any activity, between either (any) of the parties--Pine, MX-Linux, antiX--to get antiX or MX-Linux ported to the Pinebook Pro?
Both are full-featured, lightweight distributions, and both get outstanding reviews by users and tech writers.
MX-Linux has been #1 on Distrowatch for over one year, at one point having a ranking of over 6000, and has one of the highest Reader Rating of any distribution listed on Distrowatch. MX-Linux download size is ≈ 1400 MB, and antiX is ≈ 900 MB (for the largest version).
My personal opinion is that both of these would be an outstanding 'fit' for the PBP, based on their small size and full functionality.

https://mxlinux.org/

https://antixlinux.com/

https://distrowatch.com/table.php?distribution=mx

I wonder if we would be able to replace the included panel with a touch screen one?

Thanks

Hello!

Some time ago I bough A64+, then had a chance to buy Pinebook.
The plan was to run OpenBSD on both and get involved in driver development.

I maintain a few patches to OpenBSD (slowly trying them to be upstreamed).
But the code needs modified device tree, so my second repo is u-boot related (but also it's just an addition to OpenBSD's u-boot port).

Repositiories:
1. u-boot additions: https://github.com/elewarr/openbsd-ports-u-boot
2. OpenBSD src patches: https://github.com/elewarr/openbsd-arm64-src-dev

Please note, these repositories have instructions to help you get involved (with some scripts that are not very reliable but fulfil basic needs).

Status:
1. sxitemp, sxisid
  sxitemp driver relies on sxisid and uses calibration data, providing accurate temperature readings.
2. sxiuphy
  This driver (provided by Patrick Wildt) enables 2nd USB port is disabled by default for now because of unsolved issues on A64+, uncomment sxiuphy in GENERIC config to enable.
3. sxiccmu
  Enables dynamic CPU frequencies.
4. axppmic
  Supports more PMIC sensors. Current battery capacity, voltage, dis/charging current.


Work in progress:
1. sxipwm
  OpenBSD does not have PWM framework but this is needed for
2. pwmbl
  PWM backlight driverThe idea is to provide basic support for wsconsctl brightness property using PWN and generic PWM based backlight driver.Current status: brightness is set to max at boot.

I was eager to get my hands on Pinebook Pro but because of some technical issues I failed to get my voucher in time. Maybe I'll have more luck in the future. I'm aware this work (focused on Pinebook) may not be useful for Rockchip ICs but I want to learn something and this is a lot of fun!

I'd like to connect my rock64 to an old tv. I tried with an av to rca cable, but it's not flush. Attaching images:






Is this normal? I tried with android 9 stock and ubuntu bionic image. On hdmi it works fine.

Hi

I haven’t quite decided on it, but I’m considering purchasing a Rock64pro to replace the Pine64 I already have. However, configuring the right bundle was a bit difficult with the Pine64, but it seems even harder with the Rock64. Have you considered adding a guide or wizard to the store? You have an awful lot of options; offering base bundles with options to choose from would make the action of selecting what to get much easier. You guys obviously know much more than I do, when it comes to building a working system. Having the store software guarantee you’d end up with a working bundle would be quite helpful. Is this something you’ve considered?

Thanks!

(Feel free to move this elsewhere if I picked the wrong forum; I haven’t posted here before.)

Hi,

I have a Rock64 board and wanted to give it a try again.
I see new Android releases made for this but do not see git repos of kernel sources for the new release.
The last time I tried Android it was based on a 3.10 (? ) kernel. I think Rockchip has moved to 4.4 kernel.

Vasant

Is it just me or are the m.t pillars wrong?

Mine is approx 10mm tall! with a groove cut around the middle of the circumference.