1. 33
  1.  

  2. 11

    See also: Pinebook Pro review—a $200 FOSS-to-the-hilt magnesium-chassis laptop at Ars Technica (not really worth posting a new story for, so I’ll just drop it here)

    1. 1

      Thanks for sharing!

    2. 5

      Have you experienced any issues specific to the ARM architecture? I occasionally hears that Linux still has issues with ARM workstations/laptops, but it’s hard to evaluate from outside.

      1. 8

        I don’t (yet) own a PineBook Pro, but do own a PinePhone and a brace of Raspberry Pis (3 x Pi3s, 1 x Pi).

        The only issues I’ve experienced are with proprietary software like games and media players that don’t offer ARM binaries. Otherwise it’s been plain sailing for me, and that includes laying the groundwork for a Common Lisp based dev stack for the PinePhone.

        1. 1

          zge - I actually have’nt. I wanted a daily driver that consumer very little power and cheap. I have no real issues actually. I only use it as “ssh+browser” system, since the stuff I do is almost 100% in the terminal anyway :)

        2. 6

          I have a Pinebook Pro, and most things work great. The main problem is that some GUI apps don’t have official binaries, and casually compiling them yourself is often too difficult. As a result, you have to go hunt down unofficial binaries, which may or may not displease you. Some unofficial binaries I use:

          I’m using the current default Manjaro KDE, so I’m compiling a lot of stuff using AUR, and rarely run into problems. Sometimes it will warn you that “The following packages are not compatible with your architecture” but so long as it doesn’t include binaries, most terminal-based software will compile just fine despite the warning, and some GUI apps compile as well (takes some trial and error to figure out which).

          1. 2

            What issues with compiling by yourself did you experience? The “usual” as in I’m not sure what build libraries are required or something else?

            1. 4

              I just mean that if I try to compile something, and the build fails, I generally don’t know enough to even start trying to fix it. I’m a noob. If a build fails I usually just give up and try something else.

              On a few occasions I’ve tracked down the source of the problem and “fixed” it. For instance, Alacritty won’t compile on the PBP because the PBP doesn’t support gles3 by default yet, but I found a branch that compiles for me with gles2: https://github.com/nuumio/alacritty/tree/cyclopsian-gles2-nuumio

            2. 1

              Yes, I totally understand! That is “the price” people for being on a pretty new architecture. I do assume that everyone single one that has bought one is aware of it. I am thinking about having a dedicate “build-machine” like a RockPro64 from Pine that takes care of the compiling

          2. 4

            I got my pinebook a week or so ago and mostly it feels really good but it has a problem with screen flickering that makes it practically unusable unless plugged into electricity (apparently the problem has to do with the battery not being able to supply a stable current).

            This turns my plan for having it be a super-mobile and replace-able laptop into null and void.

            1. 3

              Have you tried different power bricks?

              1. 1

                I only have the charger that came with it if that’s what you mean, but I’ve tried plenty of different power outlets.

              2. 3

                May well be a manufacturing defect, mine doesn’t have this issue. I would talk to their support and see if you can get a replacement. According to the Ars Technica article they’ve been having quality control issues since restarting manufacturing post-pandemic.

                1. 1

                  Thanks, I’ll try that.