Search the Community

Showing results for tags 'solved'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 108 results

  1. Hello, I'm running a OPI Lite with debian jessie, All works fine until i have to reboot, and that happens quiet often while testing software. AFTER the boot i'm not able to reach the OPI via SSH, because the eth0 is activated ...and has a 169.x.x.x ip adress... On the OPI Lite i can ONLY discover WIFI and no eth0 connector...So i go into the "nmtui" tool and "disactivate" the eth0... Than i have access again via the wifi to my OPI lite. How can i completely disable the eth0, that only WIFI connects to my network? I didn't find about this behavior on the web, anyone else have that problem? Kind regards from Hans F4VSJ
  2. sonic2023

    Beelink X2 Boot Problem

    I use a Beelink X2 Android TV box with Armbian Stretch mainline kernel 4.19.y Image on a SD Card. If I plug in my SD Card and then the power supply, the LED is purple and after some seconds blue. No picture over hdmi but the num-lock on the keyboard works. The box also don't get an IP over DHCP. No matter how long (1h+) I wait, nothing happens... When I plug in the power supply without the SD Card, the LED is red. The normal standby mode of the box. I can now plug in the SD Card and then power the system on. The LED switches to purple and after sone seconds to blue and Armbian is running fine, no problems. If the system reboots it will run into the boot problem described above. Armbian is great but as long as I can't find a solution it sucks to plug out/in the SD Card all the time the system starts... Tryed different SD-Cards, Etcher and Rufus, other power supply - allways the same problem. The Image SHA256 hash is ok. I wanna boot direct from the SD Card and leave the android on the onboard emmc as it is. I hope someone can give me some hints, but be kind - I have only some basic knowledge of linux. ^^ Thanks
  3. Hi Guys ! I bought a new WD Blue 3D NAND SSD (1TB). It is not detected by the USB 3.0 port but by the USB 2.0 port (tested with lsblk). What can I do to be recognized on the fast 3.0 port? I am using Armbian_5.73.190128_Rockpi-4b_Debian_stretch_dev_4.20.0 Best thanks in advance ... !
  4. Hi, Recently I have installed "Armbian_5.75_Orangepizero_Debian_stretch_next_4.19.20" on my OrangePi Zero . I configured both Ethernet and wifi connection but I had a problem with the wifi, my board does have an IP address but I can not connect through ssh nor pinging that IP. The connection is Ok and I can get access to internet but I can not ping from any other devices on the network (error Destination host unreachable), But I noticed that if I ping (from the orangepi board ) the host machine then I will be able to connect through ssh to that IP. I dont know if its a problem with arp last thing that I tried was to disable the network manager but I still have the same issue.
  5. Dear Armbian friends, I have question about add DS18B20 temp sensor at RPi-Monitor (web based interface). Can somebody paste working config of this sensor? On internet I found many tutorials but with DHT sensors. On this page (Xavier is an author of RPi-Monitor I think) is described DS18B20 but in status "Working in progress". I tried this but without luck. https://xavierberger.github.io/RPi-Monitor-docs/32_sensors.html?highlight=ds18b20 Cheers, Lucas
  6. hello everyone my Orange Pi A20 does not detect any USB device with the current versions of Stretch or Bionic, but works fine with Wheezy I had try with a printer, a scanner, or USB stick. When something is connected, nothing appears in dmesg or lsusb. Yes...yes...I've been reading the troubleshooting FAQs and Google it for an answer. Change power supply and SD card, etc. But a printer or scanner doesn't consume too much power from the USB, does it? in a last effort I went back to the old Debian Wheezy (downloaded from orangepi.org) and everything works fine. Any help with that? Could it be a kernel parameter or module?
  7. Requirements: https://github.com/lthiery/SPI-Py https://github.com/mxgxw/MFRC522-python (for Raspberry Pi) https://github.com/kwanxian/OrangePiPC/tree/master/SPI/RC522 (for Orange Pi PC) sudo armbian-config System --> Hardware --> select "spi-spidev" --> Confirm --> reboot when reboot finish: sudo vim /boot/armbianEnv.txt under "overlays=spi-spidev",add this: "param_spidev_spi_bus=0" save & reboot again. then you can see spi enable in "/dev/spidev0.0". cd ./SPI_Python sudo python3 setup.py install cd ../RC522 sudo python3 Read.py you can test IC card like this: Welcome to the MFRC522 data read example Press Ctrl-C to stop. Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] Card detected Card read UID: 53,101,232,169 Size: 8 Sector 8 [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
  8. I installed Armbian_5.75_Orangepizeroplus2-h3_Debian_stretch_next_4.19.20. But it can't boot up. These image can boot up. Armbian_5.65_Orangepizeroplus2-h3_Debian_stretch_next_4.14.78 Armbian_5.69_Orangepizeroplus2-h3_Debian_stretch_next_4.19.13
  9. Hi, I am running Debian Strech on a headless server with armbian (since 2014 on wheezy), on a Cubox-i 4 Pro. My system is on /dev/sda1 After an upgrade, few minutes ago, my device is no more reachable by ssh neither answering to ping. It seems to boot the kernel but I am not even sure of that (as nothing appears in the console after "booting the kernel"). Here is the full console log: U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 2 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: vga Err: vga Net: FEC [PRIME] (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found Hit any key to stop autoboot: 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 1816 bytes read in 127 ms (13.7 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 ** File not found .next ** 48 bytes read in 114 ms (0 Bytes/s) 36853 bytes read in 826 ms (43 KiB/s) 4636514 bytes read in 411 ms (10.8 MiB/s) 5839840 bytes read in 482 ms (11.6 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x591be0 ] ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4636450 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800bff4 Starting kernel ... Uncompressing Linux... done, booting the kernel. Files located in /boot on the SDCard (same files list in sda/boot): -rw-r--r-- 1 root root 48 janv. 30 18:28 armbianEnv.txt -rw-r--r-- 1 root root 79 janv. 30 18:28 armbianEnv.txte -rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.cmd -rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.scr -rw-r--r-- 1 root root 360 déc. 27 2015 boot.txt -rw-r--r-- 1 root root 160K févr. 8 09:33 config-4.14.98-cubox -rw-r--r-- 1 root root 162K févr. 8 09:38 config-4.19.20-cubox lrwxrwxrwx 1 root root 17 févr. 16 17:47 dtb -> dtb-4.19.20-cubox drwxr-xr-x 2 root root 12K févr. 16 17:42 dtb-4.14.98-cubox drwxr-xr-x 2 root root 12K févr. 16 17:31 dtb-4.19.20-cubox -rw-r--r-- 1 root root 4,2M févr. 16 17:09 initrd.img-4.14.98-cubox -rw-r--r-- 1 root root 4,5M févr. 16 17:09 initrd.img-4.19.20-cubox -rw-r--r-- 1 root root 2,5M févr. 8 09:33 System.map-4.14.98-cubox -rw-r--r-- 1 root root 2,6M févr. 8 09:38 System.map-4.19.20-cubox lrwxrwxrwx 1 root root 21 févr. 16 17:47 uInitrd -> uInitrd-4.19.20-cubox -rw-r--r-- 1 root root 4,2M févr. 16 17:09 uInitrd-4.14.98-cubox -rw-r--r-- 1 root root 4,5M févr. 16 17:09 uInitrd-4.19.20-cubox -rwxr-xr-x 1 root root 5,4M févr. 8 09:33 vmlinuz-4.14.98-cubox -rwxr-xr-x 1 root root 5,6M févr. 8 09:38 vmlinuz-4.19.20-cubox lrwxrwxrwx 1 root root 21 févr. 16 17:48 zImage -> vmlinuz-4.19.20-cubox $ more boot.txt setenv bootargs root=/dev/sda1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt .global_cursor_default=0 quiet ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file} ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 $ more armbianEnv.txt verbosity=1 rootdev=/dev/sda1 usbstoragequirks= What else could I provide as information to get help? Thanks a lot to anybody that could give me some support...
  10. Hello, since I upraded from Armbian Strech 5.60 (kernel 4.14.84-sunxi) to Armbian Stretch 5.70 (kernel 4.19.13-sunxi), I can't get hostapd to work on my Cubietruck. When I modprobe the brcmfmac module, I get the following lines with dmesg: [134591.243266] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 [134591.523515] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 [134591.523658] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43362-sdio.clm_blob failed with error -2 [134591.523665] brcmfmac mmc1:0001:1: Falling back to syfs fallback for: brcm/brcmfmac43362-sdio.clm_blob [134591.532943] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-11), device may have limited channels available [134591.535517] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43362/1 wl0: Oct 23 2017 10:33:17 version 5.90.240 FWID 01-0 Also, the result of "ip a" returns "state DOWN" for interface wlan0. Did I miss something ? Thanks in advance for your suggestions, Romain
  11. Dear Armbian Friends, My temperature sensor is not detected by board. Can somebody give me some advice what should I chceck / change / test now? Cheers! Lucas I tried: - another sample of DHT11 - changed cables to different ones - changed - both tested sensors were connected with 4.7k resistor between positive and data cable - tried different system versions like bionic, stretch and now jessie - tried to load modules via /etc/modules-load.d/modules.conf g_serial w1-sunxi w1-gpio w1-therm - or with /boot/armbianEnv.txt (disabling loading with modules.conf) wverbosity=1 logo=disabled console=serial disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 w1-gpio param_w1_pin=PA10 param_w1_pin_int_pullup=1 rootdev=UUID=9cecf84e-027e-40ad-b711-ae5d323d9043 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u - tried to change data pin from GPIO10 (number 26) to GPIO 15 MOSI (number 19) Below some info about my system. sysadm@orangepizero:~$ ls /sys/bus/w1/devices/ w1_bus_master1 sysadm@orangepizero:~$ cat /sys/devices/w1_bus_master1/w1_master_slave_count 0 sysadm@orangepizero:~$ dmesg | grep wire [ 7.802453] Driver for 1-wire Dallas network protocol. [ 7.807173] gpio-10 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file sysadm@orangepizero:~$ sudo cat /sys/kernel/debug/gpio [sudo] password for sysadm: gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-10 ( |onewire@0 ) in lo gpio-17 ( |orangepi:red:status ) out lo gpio-20 ( |vcc-wifi ) out hi gpio-166 ( |cd ) in lo gpio-204 ( |usb0_id_det ) in hi IRQ gpiochip1: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-358 ( |vdd-cpux ) out hi gpio-359 ( |reset ) out hi gpio-362 ( |orangepi:green:pwr ) out hi sysadm@orangepizero:~$ uname -a Linux orangepizero 4.19.17-sunxi #5.73 SMP Mon Jan 28 21:06:40 CET 2019 armv7l GNU/Linux sysadm@orangepizero:~$ cat /etc/issue Debian GNU/Linux 9
  12. Hey there, uploading armbianmonitor failed, due to the connection issues, so i pasted it somwhere else: https://nopaste.xyz/?40aa3fcbb5834d1c#a9goEaQrtfCzF+MAAhWDb4+Gbfq6UMa2smyGL+ShbME= password is armbian My problem is, that there is no working outgoing IPv4 Traffic, i cant even ping a v4 adress. But on adresses, that get a AAA-Response from DNS it works fine. Had pihole installed, removed it for testing but this didn't make an difference. No firewall in use, iptables is empty at the moment. Every v4-Request ends up in a !N or No route to Host. While using pihole, i saw that the request went throug to pihole and was forwarded by it, also the resolving to an ip worked fine. So it's hard to find some information about this scenario, therefore i decided to start a thread in here. In the same network i can easily ssh into the pi with the v4 it gets from DHCP, DHCP is done by the router (was also done by the router while pihole was installed). In var/log/messages i can see the buildup of Connection with no errors, if needed i can paste this, too. (as well as the ping reply for v4/v6 or everything else you might want to see) Yeah, not sure what this is all about…grateful for all sort of ideas also @ freenode in #armbian, in case of someone is idling there and reading here Edit: Just pasting the strange Ping-situation immediatly, in case of someone thinks i may just be too stupid to ping root@bananapi:~# ping google.de PING google.de(fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003)) 56 data bytes 64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=1 ttl=57 time=14.7 ms 64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=2 ttl=57 time=14.3 ms 64 bytes from fra16s13-in-x03.1e100.net (2a00:1450:4001:819::2003): icmp_seq=3 ttl=57 time=14.0 ms ^C --- google.de ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 14.059/14.392/14.766/0.290 ms root@bananapi:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.100.40 icmp_seq=1 Destination Host Unreachable From 192.168.100.40 icmp_seq=2 Destination Host Unreachable From 192.168.100.40 icmp_seq=3 Destination Host Unreachable ^C --- 8.8.8.8 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3078ms pipe 4 also the output of ifconfig, even though its also part of the above pasted armbianmonitor: bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST> mtu 1500 ether 36:f9:0d:f7:d8:b7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500 inet6 fe80:<censored>:9e04:34c7 prefixlen 64 scopeid 0x20<link> ether d2:ac:0a:b8:d9:b5 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1239 bytes 489405 (477.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.100.40 netmask 255.255.255.0 broadcast 192.168.100.255 inet6 2003:<censored>:ee4f:61f8:564a:b35f prefixlen 64 scopeid 0x0<global> inet6 2003:<censored>:e24b:6a84:ce4:1fa5 prefixlen 64 scopeid 0x0<global> inet6 fe80::<censored>:9784:b673 prefixlen 64 scopeid 0x20<link> ether 02:10:08:42:d2:8c txqueuelen 1000 (Ethernet) RX packets 601750 bytes 48435497 (46.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2033153 bytes 2954998671 (2.7 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 60 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 5450 bytes 489081 (477.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5450 bytes 489081 (477.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 aand the var/log/messages part of the buildup: Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0508] manager: NetworkManager state is now CONNECTING Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0564] device (eth0): state change: prepare -> config (reason 'none') [40 50 0] Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.0965] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0] Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.1089] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.1781] dhcp4 (eth0): dhclient started with pid 1113 Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4654] dhcp4 (eth0): address 192.168.100.40 Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4687] dhcp4 (eth0): plen 24 (255.255.255.0) Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4690] dhcp4 (eth0): gateway 192.168.100.1 Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4691] dhcp4 (eth0): server identifier 192.168.100.1 Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4692] dhcp4 (eth0): lease time 864000 Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4694] dhcp4 (eth0): nameserver '192.168.100.1' Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4695] dhcp4 (eth0): domain name 'fritz.box' Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.4698] dhcp4 (eth0): state changed unknown -> bound Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5425] device (eth0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5757] device (eth0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5871] device (eth0): state change: secondaries -> activated (reason 'none') [90 100 0] Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.5901] manager: NetworkManager state is now CONNECTED_LOCAL Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.6569] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 12 10:17:57 localhost NetworkManager[654]: <info> [1549966677.6584] policy: set 'Armbian ethernet' (eth0) as default for IPv4 routing and DNS Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.0054] device (eth0): Activation: successful, device activated. Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.8260] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds) Feb 12 10:17:58 localhost NetworkManager[654]: <warn> [1549966678.8265] dhcp6 (eth0): hostname is not a FQDN, it will be ignored Feb 12 10:17:58 localhost NetworkManager[654]: <info> [1549966678.8693] dhcp6 (eth0): dhclient started with pid 1178 Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966678.9849] policy: set 'Armbian ethernet' (eth0) as default for IPv6 routing and DNS Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.0645] device (eth0): ipv6: duplicate address check failed for the 2003:<censored>:8447:32d7:aacf/64 lft 7199sec pref 1097sec lifetime 13$ Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8293] dhcp6 (eth0): nameserver 'fd00::9ec7:a6ff:feec:bebd' Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8296] dhcp6 (eth0): state changed unknown -> bound Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8950] dhcp6 (eth0): client pid 1178 exited with status 0 Feb 12 10:17:59 localhost NetworkManager[654]: <info> [1549966679.8952] dhcp6 (eth0): state changed bound -> done but when asking ip route, it says: default via 192.168.178.1 dev eth0 src 192.168.100.40 metric 203 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.40 metric 203 192.168.178.1 dev eth0 scope link src 192.168.100.40 metric 203 hmm, where does the wronge gateway come from? Grepping through config dirs i found it, a double-config in /etc/dhcpcd.conf # Generate Stable Private IPv6 Addresses instead of hardware based ones slaac private interface eth0 static ip_address=192.168.178.40/24 static routers=192.168.178.1 static domain_name_servers=127.0.0.1 interface eth0 static ip_address=192.168.100.40/24 static routers=192.168.100.1 static domain_name_servers=127.0.0.1 Not sure how this could come, but as there is a dns-bind to localhost i assume pihole gifted me with this error. Unsure why it would do that, but commented the first block out and everything was fine:) Biggest thanks to wysiwtf in #armbian, solution was his work So this is solved…if someone knows about the source of this would be glad for the info, though this shouldn't happen no matter what one does…
  13. Vuckovic Milos

    Orange Pi One monitor mode?

    Hello, I'm new to the Pi computers and all that, and I'm planning on doing a project, so I was wondering if the Opi One H3 would support packet injection and monitor mode on Armbian with the onboard wifi? Thanks in advance.
  14. Hi, unfortunately many times the support for XFS filesystem is just forgotton. At the moment I just run the last update for the cubietruck this morning which includes the new kernel version 4.19 and my system, which is used as an NAS device with XFS filessystem, didn't start again. I found out that this filesystem is not supported anymore (see 'cat /proc/filesystems') and no module is available. Could you plaese take care of this to fix this issue in the future? And/Or tell me please how I can get back to the older version of the kernel which supports XFS. The reason why I say this way is because I cannot spend every time hours or day's first to figure out the problem and than rebuild the system by my self and may the next update will cause the same issue again. The result is the lost of trust in Armbian and the way to use it in professional enviroments... So please tell me a quick and reliable solution. ;-) Thanks in advance...
  15. Hello everyone. I'm new to Armbian. If I do not restart or turn off by command (correctly) all the files generated or transferred since it was turned on are deleted immediately. Why? Is it normal in Armbian? I use Orange Pi Win Plus 2, how do I deactivate that functionality? I use it as a remote server.
  16. cibomato

    Touch display for cubietruck?

    Hi all, I'd like to use a touch display together with my cubietruck. Research shows displays for all other boards but not for cubietruck :-( Isn't there any touch display out there which works with cubietruck? Do I really have to change system to raspberry or something else? Thanks for your help and best regards, cibomato
  17. Hi! Periodically, time in two-three days, sharply increases CPU utilization, the system becomes disfunctional. SD card and power supply maybe not the best, but they working fine in other systems and I'm tried others. SSH hangs on login while this problem is actual, but i have a serial connection, so can investigate in real time. Please, advise, what to look when this situation came again? top - 03:02:15 up 24855 days, 3:14, 1 user, load average: 1.75, 1.77, 1.93 Tasks: 125 total, 3 running, 70 sleeping, 0 stopped, 8 zombie %Cpu(s): 17.4 us, 26.6 sy, 0.0 ni, 56.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 505152 total, 9724 free, 144028 used, 351400 buff/cache KiB Swap: 1301132 total, 1299340 free, 1792 used. 343236 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 26012 3040 1304 R 100.0 0.6 46:55.28 systemd 851 root 20 0 6128 1368 948 R 75.2 0.3 34:13.74 systemd-lo+ 8668 root 20 0 7044 2608 2136 R 1.3 0.5 0:00.15 top 7 root 20 0 0 0 0 S 0.3 0.0 14:28.83 ksoftirqd/0 8 root 20 0 0 0 0 I 0.3 0.0 1:21.03 rcu_sched 2 root 20 0 0 0 0 S 0.0 0.0 0:00.05 kthreadd root@pione:/media/data/log# systemctl reboot Failed to set wall message, ignoring: Connection timed out Failed to reboot system via logind: Connection timed out Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. root@pione:/media/data/log# root@pione:/media/data/log# systemctl status reboot.target Failed to get properties: Connection timed out root@pione:/media/data/log# root@pione:/media/data/log# reboot root@pione:/media/data/log# root@pione:/media/data/log# reboot -f Failed to read reboot parameter file: No such file or directory Rebooting. [141846.733884] reboot: Restarting system ▒▒▒▒▒▒ U-Boot SPL 2018.05-armbian (Aug 19 2018 - 17:07:52 +0200) DRAM: 512 MiB Trying to boot from MMC1 System log:
  18. Hi all! I am running a nextcloud server on an odroid HC2 and a 4 TB WD red HDD. So far, so good (thanks again @Igor for the quick help with the kernel downgrade!). And since I have bought the sbc recently, I do not seem to have the older firmware version with the HDD "emergency power down" bug, i.e. I haven't heard clacking sound from the HC2. Today, I set HDD spindown to 1 hour via hdparm (wd red does not support apm) because the HDD would spin down after about three minutes on its own. The HDD does not seem to apply these settings, so I installed smartmontools to check the HDD in general. Only to find that: smartctl -a /dev/sdb1 gives this: === START OF INFORMATION SECTION === Vendor: JMicron Product: Revision: 3101 Compliance: SPC-4 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Logical block size: 512 bytes Physical block size: 4096 bytes LU is fully provisioned Logical Unit id: 0x3042000000000132 Serial number: DB00000000013B Device type: disk Local Time is: Tue Jan 29 11:03:47 2019 UTC SMART support is: Unavailable - device lacks SMART capability. To seems, it seems the JMicron USB-SATA Bridge prohibits armbian from seeing the actual HDD. Any way to fix this? Thanks!
  19. Hellow, I would like to report an issue with Orange Pi PC+ I tried to run the board with a manually built image (with kernel version 'next' and 5.71). While in the past I was able to create Wifi hotspots without any issues, with a new image I encountered weird issues where the hotspot was listed from Wifi clients, but trying to connect triggered some scarry traceback such as this one : Having no idea what I was doing, after trying a few other things, I tried downgrading the kernel to 5.70 (using apt.armbian.org) - this did not solve the issue - and then to 5.67 for which it was working as expected ! I don't know if this is something that can be solved upstream somehow ... Naively it sounds related to the 8189fs module (driver for the Wifi chip ?) but not really sure as I don't understand so much all the driver and kernel stuffs
  20. Hi, Please, i am seeking for some help. Today i just did an apt-get dist-upgrade and my banana pi updated the kernel to 4.19.13. There wasnt any error messages but then i wasnt able to boot. I get messages like "/boot/zImage file not found" so i checked my sdcard (wich cointains the boot folder) and i saw that zImage was symlink to the previous kernel image (wich no longer existed). I corrected it cause in fact there was a vmlinuz-4.19.13-sunxi but there are some more symlinks broken in boot foolder. UInitrd is also broken and i dont have the appropiate file to make a new symlink, script.bin symlink is also broken (it pointed to /boot/bin/bananapi.bin wich dont exists anymore on my system) Can i repair the boot folder in any way? Can somebody with the same board provide me that files? Basically all the boot folder with kernel 4.19.13-sunxi or if anyone can explain me a way to boot again...
  21. Hi! recently bought a HC2 from hardkernel to migrate my nextcloud from a raspberry pi 3b. HDD is a WD red 4 TB. armbian stretch with the 4.19 kernel, downloaded from armbian.com (Armbian_5.69_Odroidxu4_Debian_stretch_next_4.19.14). My problem: after boot (sudo reboot now or sudo shutdown -r), no possibility to login, i.e. angryip scanner doesn't show the hc2, putty times out when trying to connect. All LEDs are lit or pulsate respectively. I have to physically disconnect the power supply and reboot, then I can easily login. This is probably not very healthy for the hdd (or the sd card..., although with the ro option and zram, not much is being written to the boot section anyway, right?) I speculated that the hc2 has a problem with the 4tb hdd when booting and added the nofail option to /etc/fstab, but this doesn't do the trick. Any help is greatly appreciated. I really like the hc2 formfactor and after having used nextcloud on the raspberry pi for 12 months now, I'd like to upgrade to a more powerful board, but this problem seems like a dealbreaker if I can't fix it. EDIT: I corrected the used image, I actually had the 4.19 installed!
  22. I just got a Nanopi NEO2 512MB, installed Armbian Ubuntu Bionic. It works fine, except for the DVB-T/C stick. It is affected by Kernel 4.10+ problems. I wonder if I can downgrade to an older kernel, like 4.4.0 for example, where everything works perfectly? If yes, how? There is a patch that perhaps would resolve the problem, how could I apply this patch to an of the available releases of Armbian? This patch Please, help me with this. Many thanks!
  23. Hello, I set up an Odroid-HC1 running Armbian which works fine so far. But today I recognized htop only shows 8 CPUs of type .LITTLE running at a max of 1300Mhz while 4 of them were shown as .BIG CPUs with higher frequency before. The output of cat /proc/cpuinfo is: processor : 0 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 3 processor : 1 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 3 processor : 2 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 3 processor : 3 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 3 processor : 4 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc0f CPU revision : 3 processor : 5 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc0f CPU revision : 3 processor : 6 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc0f CPU revision : 3 processor : 7 model name : ARMv7 Processor rev 3 (v7l) BogoMIPS : 36.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc0f CPU revision : 3 Hardware : SAMSUNG EXYNOS (Flattened Device Tree) Revision : 0000 Serial : 0000000000000000 Any idea on how to make the system detect the CPU cores correctly? Update: Kernel version is 4.19.5-odroidxu4 #5.67 SMP PREEMPT Fri Nov 30 03:15:28 UTC 2018 armv7l GNU/Linux Update: armbianmonitor shows the correct CPU information: ### Current system health: Time big.LITTLE load %cpu %sys %usr %nice %io %irq CPU C.St. 00:13:18: 1800/ 600MHz 0.06 1% 0% 0% 0% 0% 0% 39.0°C 0/11 00:13:19: 1800/ 600MHz 0.06 4% 3% 0% 0% 0% 0% 38.0°C 0/11 00:13:19: 1800/ 600MHz 0.06 3% 2% 0% 0% 0% 0% 37.0°C 0/11 00:13:20: 600/ 600MHz 0.06 4% 4% 0% 0% 0% 0% 36.0°C 0/11 00:13:20: 600/ 600MHz 0.06 5% 4% 0% 0% 0% 0% 36.0°C 0/11 00:13:24: 1800/1300MHz 0.13 1% 0% 0% 0% 0% 0% 49.0°C 0/11 00:13:24: 1800/1300MHz 0.13 3% 2% 0% 0% 0% 0% 44.0°C 0/11 00:13:24: 1800/1300MHz 0.13 3% 2% 0% 0% 0% 0% 42.0°C 0/11 00:13:25: 1800/1300MHz 0.13 2% 2% 0% 0% 0% 0% 41.0°C 0/11 00:13:25: 1800/1300MHz 0.13 3% 2% 0% 0% 0% 0% 41.0°C 0/11 Thanks in advance, Letterus
  24. Hi, After building a DEV Pine64 image successfully, I wanted to build a Dev BananaPI image to update 2 banana pis. Unfortunately I have this error (using this commit id : e7aeffb1) : Setting up nplan (0.36.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up gnupg (2.2.4-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:216 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:60 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated I'm trying to generate a new image. It's only the second image I'm trying to build, so maybe I forgot some cleanup somewhere. Thanks in advance.
  25. Today I did build the image for stretch (for M2 Ultra) - but it was a bit strange - because it ended up in a 1.1GB .image file, but the compressed size was only 1.5MB OK, before building the image I got only 6GB free on my virtual HDD - by the last images this did work.... Now I will reinstall my build-system with the double size (60GB against 30GB before) and then I will firstly try to create a xenial image (not stretch which give me the compressed 1.50MB image whcih doesnt boot )