From the previous section (2.1.3. Variations in ARM CPU designs and support complexity) "At the beginning of the ARM support in the Linux kernel, the hardware variety resulted in the requirement of having a separate kernel for each ARM system in contrast to the “one-fits-all” kernel for PC systems. As this approach does not scale to a large number of different systems,work was done to allow booting with a single ARM kernel that can run on different ARM systems. Support for newer ARM systems is now implemented in a way that allows the use of such a multiplatform kernel, but for several older systems a separate specific kernel is still required. Because of this, the standard Debian distribution only supports installation on a selected number of such older ARM systems, alongside the newer systems which are supported by the ARM multiplatform kernels (called “armmp”) in Debian/armhf."
It seems to me to be a better solution than a separate custom kernel, not tested/released by Debian.
I was "upgraded" to a 1080p display on my Pinebook, but that actually made it nearly unusable for me. The text is so damn small I can't read it unless my nose is pressed up against the display.
I looked in the Accessibility settings, but didn't see a way to scale the display to 150% or larger.
@tllim started the PBP wiki a few days ago and I have contributed to it somewhat today. But it will ultimately be up to you guys to maintain it so its up-to-date and useful to others.
Anyone with 3 moderated posts on the forum can use their forum credentials and edit the page.
Especially you guys in the first 3 batches, please contribute. If you're in doubt where to start, please ping @zaius .
As for excuses for not contibuting:
Don't have much time? no problem - do a FAQ
Not technical? no problem - correct spelling
Not a native speaker? no problem - upload pictures
Don't have a camera? no problem - edit layout
Don't know how to edit wiki? no problem - here are simple instructions
Well, it's finally here. And, it was well worth the wait.
I received notification via SMS on yesterday morning that DHL had a package for me that was going to require a signature. Every few hours I would receive an update on its current status as it made its way through customs and to my local DHL office. It was delivered today just before noon, no signature required... and no customs fees. ( I'm in the US )
The laptop was packaged inside a foam sleeve, inside a cardboard box, inside another cardboard box, inside a padded envelope, inside a DHL plastic bag. None of it was branded Pine64 in any way. The only thing included besides the laptop itself is a small wall-wart style AC adapter with a barrel plug for power. I have not yet tried charging via USB-C.
The laptop feels sturdy, has clean lines, and the keyboard feels great; aside from it being ISO.
The screen is crisp and easy to read, with no dead pixels or faults of any kind.
My initial opinion of the software was a little concerning, as I couldn't get audio to work and the key mappings seemed to be wrong. Both of these issues were corrected once I used the rock/rock credentials instead of root/root. The root/root user has a base MATE configuration, while the rock/rock user has been customized somewhat in ways that I personally find preferable. For example, the panel has been moved to the bottom and it includes a launcher which works with the Pine64 branded super key.
I've been using the laptop off and on for the last 6 hours on WiFi, and I'm currently sitting at 56% battery. It came to me at 100%.
Video playback is smooth, and the audio isn't bad for such a small/inexpensive device. One thing that really stands out to me is the keyboard. The keys feel just firm enough with no sponginess. It really is a pleasure to type on. Though, I might have to give in and buy the ANSI keyboard once it becomes available.
I didn't purchase the SSD adapter, as I assumed that I would be getting the ANSI keyboard at a later date anyhow. Even with the EMMC, the boot times are better than other laptops I have which contain SSDs. The stock image is consuming just under 5GB.
I'm happy to answer any questions, and will continue to provide updates as time goes by. So far, it's worth every penny of that $199.
K
UPDATE: I've had the PBP for a couple evenings now. It's at the tail-end of its second battery cycle. Overall the experience has been pleasurable. Simple web browsing and code editing work just fine for me. Firefox does seem to crash every once in a while. I've been getting more used to the keyboard. It's only an issue when I need to use the left-shift or the @ symbol.
I have been struggling to get another build to boot using the MicroSD slot. The chromium build resulted in nothing but a black screen, and the ubuntu MATE build doesn't seem to be recognized, as the laptop just boots up normally. Luke asked me to connect via UART, but I didn't realize until removing the back cover that the UART connection is done via the 3.5mm headphone jack. I do not have a cable for that yet, so I'll have to make one.
One thing I would like to share in hopes of saving someone else headache and potential damage. The tolerances on the back panel are very tight. So tight, in fact, that it was really difficult getting it back on. There are 4 spacers which need to be lined up with the screw holes. Two in the corners near the screen hinge, and two on the left and right edges halfway between the back and front of the laptop. Make sure those four spacers are lined up before trying to position the back panel. Secondly for me, the back panel would not sit flush on the left and right edges. After much trial and error, the answer to this was to get one side to sit flush. Put in the middle screw for that side. Then, apply gentle pressure to the other side while using a non-marring spudge tool to lift up on the middle of the panel next to this screen hinge. This gave the panel just enough clearance to sit down flush inside the bezel and allow the screws to be put in place.
K
UPDATE:
I have noticed that when sitting idle, the screen will quickly flicker off and then back on. I haven't yet found the time to dig deeper.
I may think that I'm in the right place for my question:
I have a big problem that makes me wonder if I should've done the good hardware. I've bought a Rockpro64 SBC with one WD Red HDD running on last Ayufan OMV version. I have a synology DS213+ (well an old thing). I've made copy of my movies from the DS213+ to the Rockpro64. Everything was almost fine but it's not the problem. I have a Mi Box for watching movies with Kodi.
I tried to watch movies and some work some don't: - Plex say that my connection it too slow or that an error came with transcoding. - I tried the Plex DLNA from my TV too. It worked only once. The other times, it frose or I had no movies on my list. - It doesn't work from Kodi and my TV (DLNA). - The same movies work well from the DS213+ (DLNA). - The same movies work well from my MacBook Pro.
So, is my SBC's not made for that or is there something I forgot to do ?
The PBP is listed as having 128 MB of SPI flash - I assume this is where UBoot lives, but perhaps it could also be used for e.g. storing crypto keys and the like? Does anyone know if Linux has a good way to do this safely?
I've been using Rock64 boards for about a year now and am overall pleased with them. I'm having NO stability or reliability issues, etc.
However, there has been one issue I've not been able to overcome---Ethernet latency. This is seen directly with ping performance, where ping round-trip times to/from a neighbor on the same LAN will be 650+ uS (microseconds). I've tried a LOT of tests and poked a lot of parameters, no solution found. For comparison, other (non-Rock64) hosts on the same LAN show round-trip latency under 150uS.
I've also tried different kernels, from recent Armbian (kernel: 4.4.182-rockchip64) to my preferred platform, archlinuxarm aarch64, including 4.18.2-1-ARCH
(my early builds from last year) up thru very recent, 5.x kernels.
I'm evaluating these boards for routing/firewall/VPN applications. I've not yet tried to evaluate what impact the network latency might have on performance. Typical routing performance I'm seeing, including VLANs and bridging, will end up with thru-put latency of over 1.6mS....That's a long time !
