miha
-
Joined
-
Last visited
Posts posted by miha
-
-
-
-
Added following line to /etc/rc.local, just above the exit 0:
nmcli dev wifi connect "mySSID" password "mypwd"
And device connects to wifi automatically after reboot. More elegant solution is needed but this is good for now. I need to figure out also how to connect two different wifi's, depending on location home/work automatically. Plan is to use nanopi with batteries as movable air quality measuring station. Thank Igor for you help!
-
New power (2.4A), new sdcard (Sandisk Ultra 32GB) and arduino (reset connected to gnd) acting as USB2UART, providing connection for OSX-software Serial.
And Arduino connected to Debug UART-ports on nanopi neo air. TX/RX/GND. Speed 115200, Data bits 8, Parity None, Stop bits 1
Attached output. Proves that my nanopi neo air is not completely dead.
-
-
Well, still no success. Added to /etc/cron.d/armbian-updates line
@reboot root /root/script.sh
And script has permissions 755 and content:
#!/bin/bash
touch /root/file
df >> /root/file
ifconfig -a >> /root/file
ls -R / >>/root/file
cat /proc/cpuinfo >>/root/file
cat /proc/meminfo >>/root/file
lsusb -vvv >>/root/fileBooted nanopi up with sdcard and I let nanopi running hours before switching power off. The file is not created.
is it so that crond is not enabled on 1st boot? I'll need to check this. I may need to test with another sdcard although I think that it's not the problem because opi+2 and raspi3 boots up w/o issues on that card.
EDIT:
Changed script to:
#!/bin/bash
/bin/touch /root/file
/bin/df >> /root/file
/sbin/ifconfig -a >> /root/file
/bin/ls -R / >>/root/file
/bin/cat /proc/cpuinfo >>/root/file
/bin/cat /proc/meminfo >>/root/file
/usr/bin/lsusb -vvv >>/root/file -
I have problem, I am not able to get console working to access my nanopi neo air. PSU is not issue, opi+2 runs with same power w/o issues. Sdcard is not problem either. Tested with more than one image and based on how onboard leds behaves, i believe that system boots up ok. Now the question: How to modify image on sdcard so that it connects to my WIFi (WPA2-PSK) on boot automatically making ssh to nano working? Or should I mount image, before writing to sdcard, and do the needed changes inside mounted image? What and how? Thanks!
-
Hi,
I wrote Armbian_5.25_Cubietruck_Ubuntu_xenial_default_3.4.113.img to sd-card and booted my cubietruck from the card. ssh in and user creation followed by reboot (rootfs resize) After that i performed apt get update&upgrade and started nand-sata-install.
I have SSD hooked to CubieTruck and my goal is boot system from onboard memory (with 3.4-kernel nand is available but not with 4.9...) and roots to /dev/sda1. This was how previous setup was. sd-card slot is broken, I need to use tape to keep card on the reader, another reason why boot from nand would be nice.
However, when i start and-sata-install, following is displayed on console:
[ 112.701170] Dev Sunxi softw311 nand magic does not match for MBR 1: softw411 [ 112.710146] Dev Sunxi softw311 nand magic does not match for MBR 2: [ 112.719450] Dev Sunxi softw311 nand magic does not match for MBR 3: [ 112.725528] Dev Sunxi softw311 nand magic does not match for MBR 4: [ 112.733262] Dev Sunxi softw311 nand header bad for all MBR copies, MBR corrupted or not present. [ 112.743553] Dev Sunxi softw411 nand: part 1, start 65536, size 65536 [ 112.749216] Dev Sunxi softw411 nand: part 2, start 131072, size 14909440 [ 112.751266] nand: nand1 nand2 [ 112.764254] Dev Sunxi softw311 nand magic does not match for MBR 1: softw411 [ 112.770268] Dev Sunxi softw311 nand magic does not match for MBR 2: [ 112.776448] Dev Sunxi softw311 nand magic does not match for MBR 3: [ 112.782522] Dev Sunxi softw311 nand magic does not match for MBR 4: [ 112.790258] Dev Sunxi softw311 nand header bad for all MBR copies, MBR corrupted or not present. [ 112.800339] Dev Sunxi softw411 nand: part 1, start 65536, size 65536 [ 112.806096] Dev Sunxi softw411 nand: part 2, start 131072, size 14909440 [ 112.808112] nand: nand1 nand2It's clear that my CubieTruck fails to boot from nand. I have searched around the web and conclusion is that i should install old ubuntu-server and flash with LiveSuite (which is not working with my MacOSsierra...)
Is there any other possibilities to get system booting from /den/nand?
Br
miha
Configuring WiFi ready before 1st boot?
in Beginners
Installed Welcome to ARMBIAN 5.37.180110 nightly Debian GNU/Linux 9 (stretch) 4.14.13-sunxi
Now trying to get bluetooth working, have two RuuviTags to connect
root@nanopiair:~# systemctl status ap6212-bluetooth
● ap6212-bluetooth.service - LSB: Patch firmware for ap6212 adapter
Loaded: loaded (/etc/init.d/ap6212-bluetooth; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-01-11 16:31:55 UTC; 7min ago
Docs: man:systemd-sysv-generator(8)
Process: 464 ExecStart=/etc/init.d/ap6212-bluetooth start (code=exited, status=1/FAILURE)
Jan 11 16:31:55 nanopiair systemd[1]: Starting LSB: Patch firmware for ap6212 adapter...
Jan 11 16:31:55 nanopiair ap6212-bluetooth[464]: sh: echo: I/O error
Jan 11 16:31:55 nanopiair ap6212-bluetooth[464]: Can't get port settings: Input/output error
Jan 11 16:31:55 nanopiair ap6212-bluetooth[464]: Can't initialize device: Input/output error
Jan 11 16:31:55 nanopiair ap6212-bluetooth[464]: Can't get device info: No such device
Jan 11 16:31:55 nanopiair systemd[1]: ap6212-bluetooth.service: Control process exited, code=exited status=1
Jan 11 16:31:55 nanopiair systemd[1]: Failed to start LSB: Patch firmware for ap6212 adapter.
Jan 11 16:31:55 nanopiair systemd[1]: ap6212-bluetooth.service: Unit entered failed state.
Jan 11 16:31:55 nanopiair systemd[1]: ap6212-bluetooth.service: Failed with result 'exit-code'.