Long-time lurker, first time poster. I have been doing some work with my Pine64 2GB and came across the kernel-update.sh script and as I was having issues (and was hoping some missing kernel modules would be in the later release), I ran the script which determined that there was an update and it duly installed it.
Upon rebooting the Pine, everything came back but the network! It doesn't appear to see the NIC at all now.
I had been previously forcing eth0 to 100MB F/D due to the gigabit issues, so I don't think it's related as even with the network connected, it doesn't even flash the connectivity LED any more to acknowledge a cable connected.
Is this a known problem?
I'll try again with a new memory card and the original image to rule out a hardware issue, but is there a way I can wind back the new kernel to the one which I was previously running before the script? Does it back up the original kernel folder?
It's difficult to use the Pine via the HDMI as it oversizes so badly that you can't read what you are typing at the bottom of the screen, so I've only done limited investigation at this stage so I'm not even sure exactly which version of kernel it has installed (whatever the latest is as of today I guess)
I have Pine64 running under Debian with a Wifi module installed that came with the board.
However, I can access the network only by plugging a Wifi adapter into one of the USB
connectors.
Without Wifi adapter the terminal command "ip link" shows no Wifi just
a link called "sit0" and another "dummy0". Is one of those the Wifi module?
How can a get the module active and how can I find its MAC address?
I've installed ubbuntu on my board and ran the resize_rootfs.sh script. I tried to install MATE with:
sudo /usr/local/sbin/install_mate_desktop.sh
I get two errors"
E: Could not get lock /vat/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists
There is any alternative LCD with touch panel that will be work with Android? Lcd from Pine64 store has terrible viewing angle... If lcd has hdmi with usb touch, it will be ok too.
As many of you have surely noticed, the forum have seen an increase in spam over the past few weeks. More than one person asked me directly or via PM to 'clean up' the forums; and I'm sure this is also true for other mods. Let me start by saying that I think that we are getting rid of spammers quickly as is, but you can speed up the process by reporting spam to us.
Reading one of those requests today, it just occurred to me that some of you may not know how to report spam (or other undesirable activity), and hence this post.
Having entered a thread, you will notice that under each comment there is a bar with a variety of options. On the right hand side of the bar, there is a 'report' button (with a red flag) which will look something like this.
Clicking 'Report' will give you a drop down menu with a number of options - select the relevant one. Completing a 'Report' alerts mods to spam or other wrong-doings as soon as they log on.
We are working on getting other systems in place to prevent excessive spam. However, it appears that some of the spamming is done by actual humans, which is much harder to prevent. So its important that you report spam when you encounter it.
Thank you so much for your help, we greatly appreciate it!
I am trying to assign static IPs to two pines and be able for them to ping each other(for future ssh).
I have edited /etc/network/interfaces:
Code:
interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
# source-directory /etc/network/interfaces.d
# commented out, so it doesnt conflict with this config
# Disable wlan1 by default (8723bs has two intefaces)
iface wlan1 inet manual
similarly the second one with the IP: 192.168.1.101, left everything else the same.
I also set managed=true /etc/NetworkManager/NetworkManager.conf so it uses the data from /etc/network/interfaces
Code:
[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq
[ifupdown]
managed=true
After a restart I can see in the network manager that both of them are corretly configured, but if I try to ping them with(from 192.168.1.101):
ping 192.168.1.100
it doesnt work.
but if I try to ping the address of my switch: 192.168.1.1, it works on both of them.
The switch in configured with the same gateway and IP: 192.168.1.1
I used longsleeps 10160528 desktop build.
I also cant go on the internet, which is connected to the switch. But between them is a router. Do I have to find out the IP of the router and set it the gateway address of the switch?
I tried using diffrent addresses for the switch(like 192.168.1.2) and use this as a gateway address in /etc/network/interfaces, but still nothing.
Any suggestions on how to make this work?
Also keep in mind, that I am a linux beginner and never did any real networking, so if you can, answer with detailed explanations and forgive my noobism.
I bought the pine64 2GB version, than I burn the 'Debian Linux Jessie with Mate GUI Image' on the SD card according to the wiki page.
After powering the board, there is nothing on PC monitor, no action, no output. The system boots fine, serial console by EXP connector works, SSH by 'Putty' works.
Please can you advice me what's wrong? My monitor doesn't have HDMI but have DVI. To connect it I use HDMI-DVI adaptor like this: http://www.officeworks.com.au/shop/offic...-cohddviad
I used to use this adaptor with same PC monitor and with Raspberry PI and it was working.
When I use it with pine64 and plug and unplug the monitor cable I get message (on serial console) like this:
[ 55.600051] hdmi_clk_disable_prepare()L176
[ 62.557231] hdmi_clk_enable_prepare()L161
Also startx doesn't work:
debian@pine64:~$ sudo startx
[sudo] password for debian:
X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-arm64 aarch64 Debian
Current Operating System: Linux pine64 3.10.102-0-pine64-longsleep #7 SMP PREEMP T Fri Jun 17 21:30:48 CEST 2016 aarch64
Kernel command line: console=tty0 console=ttyS0,115200n8 no_console_suspend disp .screen0_output_mode=720p60 earlycon=uart,mmio32,0x01c28000 mac_addr=36:c9:e3:f1 :b8:05 root=/dev/mmcblk0p2 ro rootwait
Build Date: 11 February 2015 01:19:23AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sat Nov 12 14:40:10 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module g2d_23 not found.
modprobe: FATAL: Module mali_drm not found.
modprobe: FATAL: Module sunxi_cedar_mod not found.
SunxiMaliDRI2_Init: drmOpen failed!
What is the correct value of the maximium MIPI-DSI display resolution for Allwinner A64 SoC and I quess same for PINE64+? In the Allwinner A64 SoC User Manual V1.0 (Official Release Version) on page 497 it states 1366x768@60fps. While in almost all other places it states 1920x1080@60fps. Did smbd manage to light up the 1920x1080 MIPI-DSI 24bpp color display on PINE64+ as advertised? And does it support the 24 bpp color depth or some decreased depth at maximum resolution? The question is only about MIPI-DSI and not about other possible display interfaces (HDMI, LVDS, bridges and etc).
SET failed on device wlan0 ; Operation not permitted.
Any help on how to get this connected to my secured network?
I can connect via my network currently with the pine plugged in and have access to http://openhab:8080 but havent seen wifi configuration tool in web interface. I'm new to both openhab and commandline operations...
I just received my first two Pine boards (2GB ram models). My dream is to network these together for use as a Docker Swarm cluster that would host various applications that I develop -- sort of a home-grown replacement for AWS or Docker Cloud. Although I am pretty familiar with Docker, I am rather new at devices like Pine boards. Would anyone be able to help me understand what I need to do to get a reasonably performant cluster that can scale as I purchase more Pine boards?
Here are some questions/thoughts I have:
1) OS
I was thinking Debian base here.
2) Shared Storage
I want shared storage to store docker volumes so that every board in the cluster can mount the volumes into containers.
My first thought was to buy a 1 or 2 TB external hard drive, but:
a) How do i connect all the boards to the drive? Do I need to have the drive connected to one board and then share the mount over the network?
b) What can I expect for IO latency? I want to be able to run postgres database containers against the volumes on the external drive. How will that perform?
3) microSD storage per board
This hits a limit on my docker knowledge -- i'm not sure if i need to have internal storage for all the images that I want my swarm to run, or whether the images can be stored on the shared storage from 1) and just loaded into memory when i instantiate containers. If the images must be kept on the microsd, I guess i would need 32 or 64 GB. But if the images can be kept on shared storage, then i imagine i would only need a microsd large enough for the OS and whatever disk space the docker daemon needs to do its job.
4) Accessing over the internet via SSH
I was thinking instead of buying a static IP, which would require business class from my cable company, to use a service like http://www.noip.com/. I want to be able to SSH into this cluster via the domain name, and of course be able to hit web applications over HTTP.
This is as far as I have gotten so far. I am sure there are gaps in my understanding above. Also please point out to me anything I am NOT thinking of that is crucial to my goal of a personal docker swarm cluster -- any help is appreciated!!!
