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

  • Technical support
    • Getting started
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Amlogic S905(x)
    • Armada A388, A3700
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
    • Common issues
  • Community forums
    • Peer to peer technical support
    • TV boxes
    • General chit chat
  • 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 90 results

  1. 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
  2. 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...
  3. 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!
  4. 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...
  5. 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
  6. 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.
  7. 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 )
  8. Hello Everyone, I would like to share my experience about how to boot Orange Pi almost silently in console mode (eliminate a lot of kernel messages on startup) without desktop and remove cursor blinking that can cause black rectangle appearing over white background, when painting to framebuffer. Many options that proposed as being able to reduce kernel messages on boot didn't work for me. So based on Armbian documentation I started to experience with armbianEnv.txt file in the /boot folder. The extraargs setting was not part of the default armbianEnv.txt file, but appeared in BOOT.CMD file. The setting extraargs=vt.global_cursor_default=0 quiet solved both above problems. Hope this will be helpful for somebody else.
  9. Hi, is it possible to have the serial/UART on the Olimex LIME2 to work as a serial console on Armbian Jessie (kernel version 4.5.2)? The UART is already working during early boot, but once kernel is loaded it becomes inactive. /boot/boot.cmd contains: setenv bootargs "console=tty1 root=/dev/sda1 rootwait rootfstype=ext4 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" Thanks
  10. Hello all, I am iterating the build process, debugging some user build scripts and it would be nice to be able to avoid recompiling the kernel and generating its debs every time, in order to be able to iterate faster and make faster progress. I didn't see a way of doing this in the documentation. Any suggestions? Thanks
  11. Armbian provides its own hostapd. Why? This is relevant because of the recent WPA2 bug. Upstream hostapd has been patched: https://packages.debian.org/jessie/hostapd I don't understand the precise relation between Debian and Armbian. Will this patch percolate down? Thanks
  12. Hi everyone, since upgrading to the new stable build DKMS refuses to compile any driver package for the 8812au Wifi chip I could find on github: make ARCH= CROSS_COMPILE= -C M=/root/rtl8812AU modules make[1]: *** M=/root/rtl8812AU: No such file or directory. Stop. Makefile:1576: recipe for target 'modules' failed make: *** [modules] Error 2 I did change the makefile to reflect compiling for ARM. This procedure worked on the old stable kernel. Is there a way to modify the Makefile or kernel sources to accept the new kernel...or is something borked with my system? The error message does not point me to a direction to check for a fix. Cheers FIX: I think I found a fix in editing the makefile, created a pullrequest with a more famous rtl8812au repo: https://github.com/diederikdehaas/rtl8812AU/pull/62
  13. Is it possible to shut down power to a particular USB port? I have a sensor that is using USB also to power itself. I don't need it running all the time - hence - I'd like to turn it off.
  14. Hi, I'm trying to boot from SATA the original OrangePI: Using the Jessie "Linux orangepi 4.9.12-sunxi #4 SMP Thu Feb 23 19:46:51 CET 2017 armv7l GNU/Linux" Followed this thread: https://forum.armbian.com/index.php/topic/329-moving-linux-to-sata-or-external-drive/ - copied to /dev/sda1 - edited /boot/boot.cmd and changed to /dev/sda1 - edited the mounted sda1 fstab and changed / to SATA drive UUID - compiled: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Rebooted but Orange Pi still boots from mSD card and does not use SATA drive. Question: Should I use UUID of the SATA drive in /boot/boot.cmd?
  15. For anyone stumbling accross CVE-2017-6074 and thinking about whether Armbian installations are affected or not: we're most probably not since CONFIG_IP_DCCP is enabled as module only on some kernels: root@armbian:/var/git/Armbian/lib/config/kernel # grep 'CONFIG_IP_DCCP=' * linux-cubox-default.config:CONFIG_IP_DCCP=m linux-cubox-dev.config:CONFIG_IP_DCCP=m linux-mvebu-default.config:CONFIG_IP_DCCP=m linux-mvebu-next.config:CONFIG_IP_DCCP=m linux-sun8i-dev.config:CONFIG_IP_DCCP=m linux-sunxi-dev.config:CONFIG_IP_DCCP=m linux-sunxi-next.config:CONFIG_IP_DCCP=m root@armbian:/var/git/Armbian/lib/config/kernel # Details about this local root exploit: http://seclists.org/oss-sec/2017/q1/471
  16. First of all forgive my English, I do not speak the language and certainly make mistakes. use google translator to write;-) I have the Orange Pi + 2e and I installed "Debian Jessie," but I can not run the wifi that is integrated, I am new to linux, so everything costs me more. According to the specifications https://linux-sunxi.org/Orange_Pi_Plus_2E the wifi chip is Realtek RTL8189FTV Would appreciate some help, thank you very much.
  17. Hi, No real problem, just a question. I'm using latest Armbian Jessie 5.25 with my good old Banana Pi. root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 144000 312000 528000 720000 864000 912000 960000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 480000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 960000 Please notice that 480MHz (the min freq) is not in the available frequencies. So that gives the following output with cpufreq-info : root@marvin:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367) Should I set /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq to 528000 or is there a problem with 480MHz not being in available frequencies ? IIRC I had the same problem with the previous kernel (Armbian 5.24), I do not remember if it happened before.
  18. I have Armbian_4.5_Cubietruck_Debian_jessie_3.4.109 running from NAND on my Cubietruck. Boot, reboot and shutdown are very slow. I assume that this is caused by this bug: As I do not need WIFI and Bluetooth ... Is it possible to remove WIFI and Bluetooth completely? How? Would that help with the mentioned problem? Is it ensured, that the WIFI and Bluetooth hardware modules are shutoff / power save when disabled? P.S.: great work Igor
  19. Hello, I received a few weeks ago some new Lime2 boards. Using compiled Armbian kernel leads to a network problem: no IP is set and network does not work I have messages when connecting Ethernet cable: sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx Link is Up - 100/Full The ip a command gives: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 02:02:02:cc:cc:cc brd ff:ff:ff:ff:ff:ff inet6 fefe::fe:xxx:xxx:9307/64 scope link valid_lft forever preferred_lft forever I think the problem is related to the new revision of the board as described here : Ethernet PHY is changed to RTL8211E replacing the obsolete RTL8211CL no need for kernel patches But searching through the kernel options did not give me any clue, and nothing works. What is to be done to make network up again ? Is there something to reconfigure on an existing armbian installation ? Are there some files to modify ?
  20. Hello, I'm running a freshly installed armbian with mainline kernel 4.9.5 on my cubietruck. Between u-boot messages and login prompt I don't get any output while booting. I've tried several values for the "console" parameter in the armbianEnv.txt and recompiled the /boot/boot.scr file without success. I've tested both VGA and HDMI (with an HDMI to VGA adapter) outputs without success too. What should I do to get things to work please ? Thanks for your time and your great work on armbian.
  21. Hi all, thank you for creating and maintaining Armbian. Makes live much more easier. I installed Armbian 4.5 (Cubietruck Jessie 4.2.3) via UART0. I'm now trying to access at least two further UART Devices (I need serial to an Arduino and to a GPS shield). I understood as Armbian uses the mainline Kernel script.bin is now obsolete and no longer used. Thus I don't know the pinouts for the other UARTs. Is there any documentation? Furthermore I'm not sure if the other UARTs are properly enabled in the Kernel configuration. Linux serial console seem to be on ttyS0 which is working fine: [ 0.000893] console [tty1] enabled Furthermore dmesg shows ttyS0: [ 1.901838] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 41, base_baud = 1500000) is a U6_16550A Additionally the Kernel seem to find more serials on the SoC: /proc/device-tree/soc@01c00000/serial@01c28000 /proc/device-tree/soc@01c00000/serial@01c28400 /proc/device-tree/soc@01c00000/serial@01c28800 /proc/device-tree/soc@01c00000/serial@01c28c00 /proc/device-tree/soc@01c00000/serial@01c29000 /proc/device-tree/soc@01c00000/serial@01c29400 /proc/device-tree/soc@01c00000/serial@01c29800 /proc/device-tree/soc@01c00000/serial@01c29c00 Which probably result in the devices /dev/ttyS0 to /dev/ttyS7? Which steps are nessecary to configure this devices in Linux and how can I find out the pinouts for each device. Any hints or pointers are welcome. Thank you very much for your help in advance.
  22. Having trouble getting the modem to show up in the /dev/ folder. I have a HL8548 Sierra Wireless mini pci-e connected to my Clearfog-Pro. Currently using Armbian 3.10.104 "jessie". I've tried using a stock image, going through the kernel config menu to turn on PPP and looking for any settings related which I can turn on (Can't seem to find anything device driver related). My understanding is it's part of the stock Kernel and should show up as a USB device (gone back to the supplier to check the AT command was sent to have the modem in the right mode). If anyone has experience getting a mini pci-e cellular modem going in Armbian I'd appreciate any advice. Also tried using the dev and next branches but couldn't get them to install on my clearfog (freezes during boot at the decompressing part, not sure why).
  23. Hi everyone, So I am a real beginner with networking so I though I would buy this board for learning and messing about. But I cant get the switched 6 port Ethernet to work. It shows up with ip link: root@armada:~#ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 0a:b2:e1:6c:82:2e brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 532 link/ether 00:50:43:25:fb:84 brd ff:ff:ff:ff:ff:ff 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 532 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 5: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 532 link/ether 00:50:43:0d:19:18 brd ff:ff:ff:ff:ff:ff 6: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1 link/ipip 0.0.0.0 brd 0.0.0.0 7: lan1@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 8: lan2@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 9: lan3@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 10: lan4@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 11: lan5@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff 12: lan6@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:50:43:84:25:2f brd ff:ff:ff:ff:ff:ff I also can a assign an IP to eth1 and ping it, but i cant ping any thing connected with eth1. I am running the latest vanilla version of armbian for the Clearfog Pro. Help would be much appreciated.
  24. I know is a hard-work, maybe due to the "avalanche" of new boards. But I find a little mess in the filter to select boards in the Donwload page based on the availability of OS images. For example Orange Pi One http://www.armbian.com/orange-pi-one/ doesn't have Mainline OS but it's appear in the filtered list. Thanks in advance.
  25. petrmaje

    Solved GMAC TX status: VLAN frame

    Hi, after pure installation Armbian_4.5_Lamobo-r1_Debian_wheezy_3.4.109.zip, the log is full of GMAC messages: [43099.518189] GMAC TX status: VLAN frame [43099.521192] GMAC TX status: VLAN frame [43099.524646] GMAC TX status: VLAN frame [43111.775611] GMAC TX status: VLAN frame [43112.963963] GMAC TX status: VLAN frame [43112.980989] GMAC TX status: VLAN frame [43112.986370] GMAC TX status: VLAN frame [43112.989681] GMAC TX status: VLAN frame [43112.992410] GMAC TX status: VLAN frame [43112.996184] GMAC TX status: VLAN frame [43113.002038] GMAC TX status: VLAN frame [43113.973308] GMAC TX status: VLAN frame [43113.976078] GMAC TX status: VLAN frame [43114.143583] GMAC TX status: VLAN frame [43114.487643] GMAC TX status: VLAN frame [43114.700444] GMAC TX status: VLAN frame [43115.015755] GMAC TX status: VLAN frame [43115.188027] GMAC TX status: VLAN frame Bug? Or I configured something wrong? PM