| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,982
» Latest member: rbpatrick
» Forum threads: 16,335
» Forum posts: 117,444
Full Statistics
|
| Latest Threads |
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,655
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 89
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,021
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,053
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,306
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 242
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,035
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 345
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 149
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 218,371
|
|
|
| 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.
|
|
|
|
|