| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Weatherproof case build
Forum: Enclosures
Last Post: ltorsini
10 hours ago
» Replies: 12
» Views: 38,460
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
Yesterday, 04:47 PM
» Replies: 16
» Views: 11,020
|
pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
Yesterday, 07:28 AM
» Replies: 0
» Views: 43
|
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 193
|
Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 103
|
Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,047
|
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 265
|
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 148
|
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,611
|
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,226
|
|
|
| DSI mainline branches |
|
Posted by: fpoussin - 08-28-2019, 11:07 AM - Forum: LCD and Touch Panel
- Replies (5)
|
 |
Hi,
I've been working on DSI to use my panel with the Sopine but I wanted a mainline kernel.
I've used the patches from the amarula fork (this) and rebased them on latest stable/rc versions, plus a few fixes. These are supposed to go upstream at some point.
![[Image: image0.jpg]](https://cdn.discordapp.com/attachments/463285150898192384/614614869257486340/image0.jpg)
You can find the 5.2.x code here
Let me know if that works with other panels.
|
|
|
|
| Help request - Twitter Banner / logo |
|
Posted by: Luke - 08-27-2019, 02:10 PM - Forum: Community and Events
- Replies (2)
|
 |
Its about time to change the Twitter banner and possibly spice up the log; the same banner has been up on the accound for quite some time (3 years?).
If you're handy with GIMP and would like to help out then I'd be very thankful.
Feel free to credit yourself on the banner (name / online handle -- whatever you feel like).
Paste submission in this thread. Cheers!
|
|
|
|
| Manjaro arm on pine64+ |
|
Posted by: roel - 08-27-2019, 08:27 AM - Forum: Linux on Pine A64(+)
- Replies (2)
|
 |
Hello,
I made a build of Manjaro arm for the pine64+. Everything works fine, only sound through hdmi with most recent kernels doesn't work. With kernel 4.2 hdmi sound works. Analogue sound works.
As it was just a few changes in the manjaro-arm-tools they added them in git -> https://gitlab.manjaro.org/manjaro-arm/a...-arm-tools
So probably with the next manjaro arm release there will be a image for the pine64+.
As I don't have the wifi and DAC board I couldn't test if they work, so don't expect them to work.
|
|
|
|
| Network problems (actually bad power supply) |
|
Posted by: Unkn0wn - 08-26-2019, 03:00 PM - Forum: Clusterboard
- Replies (14)
|
 |
But different from the problems I've read so far.
Using the latest version of Armbian Buster all the modules boot and are accessible. However after a couple of hours the modules become unreachable one by one. After ~1 week only 2 of the 7 modules are resolve-able over the network. All modules have a static IP natively, however I have tried with DHCP and a static IP on the gateway. Here a network ping to a "off-line" module:
Code: C:\WINDOWS\system32>ping 10.10.10.70
Pinging 10.10.10.70 with 32 bytes of data:
Reply from 169.254.1.1: Destination host unreachable.
Reply from 169.254.1.1: Destination host unreachable.
Reply from 169.254.1.1: Destination host unreachable.
Reply from 169.254.1.1: Destination host unreachable.
Ping statistics for 10.10.10.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\WINDOWS\system32>
I do not know whether the system is actually running. What kind of serial interface should I be using to debug this?
The extra software I am running on the modules is docker (18.06.3~ce~3-0~debian), containerd.io (latest) and kubernetes (1.15.2).
p.s.
the software date on some of the modules jumps randomly to october 2119 on the command date, but the hardware clock shows the correct time (hwclock). This is resolved after a reboot and is unkown whether this has something to do with the network, I just thought it was important enough to mention.
EDIT: After having physical access I think I've found the issue. I believe it is twofold:
1. Misconfigured switch and gateway. Couldn't prove this one, but I believe it caused a part of the issues I had.
2. Faulty PSU. I use the 5v 15A PSU from the Pine64 store, and on top of making poor contact between the AC cord and the adapter, it is faulty and not able to sustain all modules under a full load. I've asked for a replacement unit.
EDIT2: Ordered a ATX PSU, will see if that goes better.
EDIT3: With an ATX power supply the modules are working perfectly, even under heavy load and for sustained amounts of time. However I still have the time drifting issues.
|
|
|
|
|