I have a Pine64 with ZWave module, installed domotizc on it.
I installed open zwave for domoticz.
For it to work, it was needed to create a symlink from /dev/ttyACM0 -> /dev/ttyS2 as domoticz expects to find the open zwave module on /dev/ttyACM0
Now I also have a RFlink, which is connected to the serial port.
And guess what, when I remove the device and symlink, then I see the RFlink getting created as /dev/ttyACM0
Same way, if I keep the symlink, and connect the RFlink, in the log of domoticz I see it complaining about the ZWave device not properly reponding.
I.e. when I connect the RFLink, it will come as /dev/ttyACM0 even if there is already such a device (ore a symlink to it)
I have the pine64 2gb board with the touch LCD running armbian. everything with the LCD and touchscreen works. I am working on trying to get the display manager to work. When you boot it up, it does the autologin to the desktop for the user created on first run. Armbian uses the nodm (no display manager) by default. I removed that and installed lightdm as suggested on the getting started section on the armbian site. After rebooting I am presented with terminal only. I can login as what ever user I want and then run startx to get to the desktop but I still can't log out, or switch users or at any point get presented with a graphical login screen. If I remove lightdm and reinstall nodm it goes back to doing the autologin to the desktop.
I just got my Pinea64 2gb a few days ago and have been trying to get android TV to boot on it. I was able to get the official Ubuntu mate image to work so I know the board isn't bad. I have tried android tv 5.1.1, 6.0, and 7.0. All that happens when I plug it in and turn it on is the screen I'm using (both 1080p one is a large TV and one is a computer monitor, both are using straight HDMI) turns orange and after 10-15 seconds goes black and comes back as orange for 3 minutes before restarting again. Any ideas?
I would like to make an car amplifier extension board. Can anyone suggest me about the following topics:
- Volume adjustment (volume can be adjusted over I2C, what is the best way, adjusting volume of analog output of pine64 or tas524C)
- Audio input, there are four channels, pine64 has only 2 ch output. How can I do it?
- Fault, Mute, standby, clip_otw, is it necessary to use these pins with Pine?
Would it be possible for a 3rd party to create a better module?
I believe with the SDIO interface, it should be possible to implement a Broadcom BCM4356 (which supports SDIO v3.0 for WiFi and GPIO for BT4.0), and achieve WiFi speeds up to 867Mbps (not to mention this chip has a built-in FM receiver, which could also be used).
Also I understand that this would raise prices for such a wireless module, but for many, it would be a better choice (especially as there's no PCIe or USB3.0 port onboard). I just feel like 150Mbps is quite limited for such a versatile device.
Hi there,
I get it installed and up running with Debian. It was continuously on for several days, with some pauses when I shut it down. Then I moved with it to our second home and there i did not get it up anymore. I noted that it did something and got through some initial steps, but then it shut down itself. Now does not even show any signs of activity. When plugged in the red led is on, but no signs of activity. I checked the micro SD card and it seems OK as far as I can see. Any ideas where to start looking for a solution.
Regards Björn
The microsd card and my Pine A64 2GB becomes corrupted after a reboot, shutdown or power outage, which in turn leads to various bugs or renders the system unbootable, even after repairing the card using fsck.
Could anyone please tell me if this could be related to the microsd card brand(it is a fast Kingston model) or if it means my Pine A64 is defective and good to go to the trash can.
This problem occurs on all Pine A64 images I've tried: ubuntu, android and debian.
