Active threads

Oh damn, wish I would have read this before I tried to install (26.2 with vendor kernel build on the 9th) from SD to Nvme... How can I reflash MTD if I only have a MacBook available?

This week’s Armbian development saw a wide range of improvements and fixes across the project’s build framework, kernel support, and device compatibility. Notable changes include the transition from POSIX to Bash syntax for enhanced script reliability, expanded support for new hardware such as the Norco-EMB-3531 board, and the addition of Vulkan and improved 3D package descriptions. Several device-specific updates were made, including kernel enhancements for sm8250, mainline support for SpacemiT, and fixes for wireless and HDMI functionality on various boards. The team also introduced new features like a cache manager modal in the imager and improved marking for container-based software. Multiple bug fixes addressed issues with OS image duplication, patch timestamps, and device quirks. Security was bolstered with hardened GitHub Actions, ensuring a more robust development pipeline. Changes(#9400 P1a) Replace POSIX [ ] with bash [[ ]] across build framework. by @iav in armbian/build#9462Add manual execution and daily cron schedule for MOTD generation. by @igorpecovnik in armbian/armbian.github.io#249Add norco-emb-3531 board and norco vendor image. by @retro98boy in armbian/armbian.github.io#244add Vulkan support and expand 3D package descriptions. by @igorpecovnik in armbian/build#9494Added config improvements and fixes to ayn odin2. by @Squishy123 in armbian/build#9316bump 7.0 to rc2. by @EvilOlaf in armbian/build#9475dwc2: explicitly force host mode for USB_DR_MODE_HOST. by @igorpecovnik in armbian/build#9486feat: add cache manager modal with per-image management. by @SuperKali in armbian/imager#109feat: mark container-based software in menu and docs. by @igorpecovnik in armbian/configng#761fix(gitignore): ignore pycache at all depths (#7863). by @iav in armbian/build#9490fix(images): adapt module to new armbian-images.json structure. by @igorpecovnik in armbian/configng#756fix(manage_zsh): abort shell change if zsh package install fails. by @ajorpheus in armbian/configng#759fix: resolve OS image list duplication when switching filters. by @SuperKali in armbian/imager#110Fix: SakuraPi RK3308B WLAN broken. by @TheSnowfield in armbian/build#9478i915: fix Dell XPS 13 7390 device ID in quirk patches. by @igorpecovnik in armbian/build#9485Improve sm8250 6.19 edge kernel. by @retro98boy in armbian/build#9434meson64: bump edge to 7.0-rc1. by @EvilOlaf in armbian/build#9459meson: freeze current kernel at 6.12.28 and fix HDMI PHY frequency limit. by @igorpecovnik in armbian/build#9465nanopi-zero2: enable mainline kernel support and PCIe for M.2 WiFi. by @rubycomm in armbian/build#9453OrangePi 3B: Add device tree overlays for OrangePi 3B with I2C, PWM, SPI support. by @kskshaf in armbian/build#9460OrangePi-RV2: Fix wireless access point mode by using the correct FW. by @sven-ola in armbian/build#9504orangepi5: rewrite uboot patches against v2026.04-rc3. by @EvilOlaf in armbian/build#9457patching: fix #9028 timestamp when multiple patches touch same file. by @iav in armbian/build#9489pkg_install/pkg_remove: properly propagate apt-get exit codes. by @igorpecovnik in armbian/configng#760Removed un-needed patch for SM8550-6.18; patch has already been updat…. by @Squishy123 in armbian/build#9487rk3568: add 51.2MHz PLL rate for HDMI. by @skorobkov in armbian/build#9477rock-5b-plus: add current kernel to build targets. by @igorpecovnik in armbian/build#9464rock-5t: add current kernel to build targets. by @igorpecovnik in armbian/build#9463Rockchip64 fix patches due to upstream changes in 6.19.6 and 6.18.16. by @EvilOlaf in armbian/build#9483rockchip: Disable specific patches in 6.19 series. by @igorpecovnik in armbian/build#9493rockchip: Enable Wireguard/TUN module in vendor kernel. by @vidplace7 in armbian/build#9492Spacemit legacy loadpatch. by @sven-ola in armbian/build#9496SpacemiT: Add linux-7.0.y "mainline" support. by @pyavitz in armbian/build#9458spacemit: remove old and unused patch set. by @sven-ola in armbian/build#9497unset QEMU_CPU for aml_image_packer. by @QwaSeeK in armbian/build#9417Update odroidxu4-current to 6.6.128. by @belegdol in armbian/build#9491[StepSecurity] ci: Harden GitHub Actions. by @step-security-bot in armbian/build#9356View the full article

Hi all, I kinda set myself in a corner: Last year in October I installed the UEFI image in SPI on my OrangePi5 Plus, then I installed the uefi armbian image on the Nvme ssd. I did all of that after a system failure during my 3 month absence from where I've got that OPi5 setup. As I couldn't get it back to work I went and tried with the Uefi Image... But it seems that this was a major mistake: I could never get my frigate container back to running as there's no NPU's detected! Just now I took the leap of faith and reinstalled uboot into the SPI and flashed a freshly loaded "Armbian_25.11.1_Orangepi5-plus_trixie_current_6.12.58_minimal.img.xz"... And still there's no NPU: I can't see a thing about a NPU: mircsicz@orangepi5-plus:~$ sudo dmesg|grep rocket mircsicz@orangepi5-plus:~$ sudo dmesg|grep NPU mircsicz@orangepi5-plus:~$ sudo dmesg|grep GPU mircsicz@orangepi5-plus:~$ sudo dmesg|grep gpu [ 6.133753] panthor fb000000.gpu: [drm] clock rate = 198000000 [ 6.136216] panthor fb000000.gpu: [drm] Mali-G610 id 0xa867 major 0x0 minor 0x0 status 0x5 [ 6.136222] panthor fb000000.gpu: [drm] Features: L2:0x7120306 Tiler:0x809 Mem:0x301 MMU:0x2830 AS:0xff [ 6.136226] panthor fb000000.gpu: [drm] shader_present=0x50005 l2_present=0x1 tiler_present=0x1 [ 6.160653] panthor fb000000.gpu: [drm] Firmware protected mode entry not be supported, ignoring [ 6.160711] panthor fb000000.gpu: [drm] Firmware git sha: 814b47b551159067b67a37c4e9adda458ad9d852 [ 6.160868] panthor fb000000.gpu: [drm] CSF FW using interface v1.1.0, Features 0x0 Instrumentation features 0x71 [ 6.161137] [drm] Initialized panthor 1.5.0 for fb000000.gpu on minor 1 mircsicz@orangepi5-plus:~$ uname -a Linux orangepi5-plus 6.18.0-rc6-edge-rockchip64 #1 SMP PREEMPT Sun Nov 16 22:25:38 UTC 2025 aarch64 GNU/Linux Nor with the npu-probe.sh script: # Auto-generated NPU detection record # Generated at: Mon Mar 9 07:32:45 PM EST 2026 [platform] comatible="xunlong,orangepi-5-plus,rockchip,rk3588," model="Xunlong Orange Pi 5 Plus," family="unknown" soc_id="unknown" arch="aarch64" kernel="6.18.0-rc6-edge-rockchip64" [modules] rknpu="" rocket="" [devices] no_detected_npu=1 devices_not_support=[ "/dev/dri/renderD128", # Driver: panthor ] [libraries] no_delegate=1 vendor_libs=[] So I came here hoping one of you guys will be able to gi'me a hint... After flashing a recent dev build of v26.2 with vendor Kernel to another SD I finally can see the NPU again: # Auto-generated NPU detection record # Generated at: Mon Mar 9 08:20:56 PM EST 2026 [platform] comatible="rockchip,rk3588-orangepi-5-plus,rockchip,rk3588," model="Orange Pi 5 Plus," family="unknown" soc_id="unknown" arch="aarch64" kernel="6.1.115-vendor-rk35xx" [modules] rknpu="/sys/module/rknpu" rocket="" [devices] npu_device="/dev/dri/renderD129" # Driver: RKNPU devices_not_support=[ "/dev/dri/renderD128", # Driver: rockchip-drm ] [libraries] no_delegate=1 vendor_libs=[] Also added my entry to the Github mentioned above 😉 So now I need to ask @usual user what specific kernel are you running? It seems to me that with the kernels available on the repo's only 6.1.115 allows me to use the NPU...

Update — Working fix available I've got eMMC detection working on my Radxa Zero 3W with Armbian Trixie (vendor kernel 6.1.115, SD card boot). The fix uses a device tree overlay to inject the missing voltage regulators, pinctrl references, and eMMC capabilities into the base DTB, combined with a small systemd service that rebinds the SDHCI driver to work around a deferred probe timing issue. After applying, the eMMC is detected as expected: mmc0: new HS200 MMC card at address 0001 mmcblk0: mmc0:0001 8GTF4R 7.28 GiB armbian-install works normally after that to migrate to eMMC boot. The rebind service is conditionally skipped when booting from eMMC so it doesn't interfere. I've attached a zip with all the files. The README.md inside has the full details — root cause analysis, what was tried and failed (including full DTB recompile), how the fix works, installation/verification/revert steps, and known limitations (the pinctrl phandle values are specific to this kernel build). I still working on a version that does not need the rebind service for sd cards. but for now you need the rebind on the sd card to get it to find the EMMC so you can install. emmc-fix.zip

Hi folks, I was looking to activate the NPU on my beagley-AI chip, running armbian, and I couldn't find how. This chip as a NPU (AM67A) on the SOC from TexasInstruments (https://api.pageplace.de/preview/DT0400.9783895766572_A50990365/preview-9783895766572_A50990365.pdf). The loading of the NPU seems to have failed: mesg | grep remoteproc [ 8.461511] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode [ 8.461728] remoteproc remoteproc0: 7e000000.dsp is available [ 8.461868] k3-dsp-rproc 7e000000.dsp: register pm nitifiers in remoteproc mode [ 8.464448] k3-dsp-rproc 7e200000.dsp: configured DSP for remoteproc mode [ 8.465124] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2 [ 8.465164] remoteproc remoteproc0: powering up 7e000000.dsp [ 8.465271] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2 [ 8.465285] remoteproc remoteproc0: request_firmware failed: -2 [ 8.480524] remoteproc remoteproc1: 7e200000.dsp is available [ 8.480658] k3-dsp-rproc 7e200000.dsp: register pm nitifiers in remoteproc mode [ 8.482329] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2 [ 8.482375] remoteproc remoteproc1: powering up 7e200000.dsp [ 8.482488] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2 [ 8.482501] remoteproc remoteproc1: request_firmware failed: -2 [ 8.964763] platform 79000000.r5f: configured R5F for remoteproc mode [ 9.047514] remoteproc remoteproc2: 79000000.r5f is available [ 9.048055] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2 [ 9.048099] remoteproc remoteproc2: powering up 79000000.r5f [ 9.048222] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2 [ 9.048241] remoteproc remoteproc2: request_firmware failed: -2 [ 9.234391] remoteproc remoteproc3: 78000000.r5f is available [ 9.234578] remoteproc remoteproc3: attaching to 78000000.r5f [ 9.402138] remoteproc remoteproc3: remote processor 78000000.r5f is now attached [ 9.505240] platform 78400000.r5f: configured R5F for remoteproc mode [ 9.547946] remoteproc remoteproc4: 78400000.r5f is available [ 9.548359] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2 [ 9.548400] remoteproc remoteproc4: powering up 78400000.r5f [ 9.548505] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2 [ 9.548521] remoteproc remoteproc4: request_firmware failed: -2 [ 15.281722] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink [ 15.285991] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink The usual lspci doesn't contain much: lspci 00:00.0 PCI bridge: Texas Instruments Device b010 How should I proceed to make it work? Thanks!

I also saw that both apt and beta repo's do not contain recent rockchip64 kernels at the moment. There is only a recent generic arm64 one. So it is not only my rock3a, also my nanopi-r6c would be affected, but I use own/other/vendor kernels as well, so specific 6.18.8 is not an issue for me. I use extlinux or grub to select a certain kernel (6.19 flavor on nanopi-r6c for example). For my rock3a, I need vendor kernel, but if you use mainline based, you could use standard Debian backports kernel: https://packages.debian.org/trixie-backports/linux-image-arm64 You need to get the .dtb manually and I just assume most features are supported when the rock3a has mainline U-Boot in SPI. You need of course add that to sources.list and specifically select it. You could also use Armbian build framwork to build a 6.18.x yourself, you will also get a header files package then. For Debian14 I see there is: /usr/lib/linux-image-6.18.15+deb14-arm64/rockchip/rk3568-rock-3a.dtb But as indicated, this is total DIY, I have not tested it. I only know that on rock5b I could run standard distro since quite some months, but use 6.1.115 vendor one as I need all RK3588 HW to work.

Ok, after doing more tests the issue was the boot switch on the board. It must be switched to boot from SD/eMMC and not SPI (BIOS). Then reboot works fine.

ha extension is not a part of the framework. Copy from here https://github.com/armbian/os/tree/main/userpatches/extensions

If you’re thinking about running Armbian on the OnePlus 8T, basic functionality like calls, SMS, and mobile data will really depend on how well the device drivers are supported in the current build. From what most community discussions suggest, Wi-Fi and some hardware features may work, but cellular, camera, and other components can still be hit-or-miss compared to more mature options like Sailfish OS or Ubuntu Touch on officially supported devices. It’s a good idea to check active developer threads and user reports before installing.

Hi @maxsub, two annotations. Firstly, it's not the Wifi driver but the firmware. Thus echo "options bcmdhd firmware_path=brcm/ nvram_path=brcm/" > /etc/modprobe.d/orangepirv2.conf will get you going. And secondly no, there is no GPU change currently. GPU not working in "current" but may work with dirty tricks using "legacy". That's why it may pay to do some maintenance on the ancient 6.6 kernel.

Ah I didn't know about that. I just created a systemd service that runs cpupower at boot.

@Morales Morales

Read post on October 27 2024 Worked for me but with a couple extra steps burn .iso cfcard boot into device dd mmblk to nvme edit UUID for nvme -- Request new UUID for NVME (when dd I had the same UUID for cf card and nvme) edit orangpiEnv.txt in the armbian-config /System/Kernel/Edit Boot Env and apply the new UUID to the rootdev="New UUID" Edit fstab to add this line: /dev/mmcblk1p1 /boot vfat defaults 0 2 itd

Issues for the actual image (no UI): no HDMI; Ethernet got address with DHCP, but cannot connect with SSH, even ping (ICMP) is not stable. Wifi works fine. The board is OK - tested with official debian image.

i also added a hp now: https://langerma.github.io/dumpstore/

I am extremely excited! This really worked! Successfully booted into the system from NVMe! Thx!!!! 😘😘

UPDATE I was able to figure out what was happening. The board initially boots with the LEDs enabled. Because of this, applying the device tree overlay alone did not seem to disable them, even across reboots. However, after manually turning the LEDs off once using: echo 0 | tee /sys/class/leds/blue_led/brightness echo 0 | tee /sys/class/leds/green_led/brightness and then enabling the overlay, the LEDs remained disabled, and the overlay appeared to work as expected. So it seems the LEDs needed to be turned off once manually before the overlay behaviour became consistent. Everything now works as intended. It appears that when overlay_prefix is either not defined or is empty, the system behaves unexpectedly during overlay lookup. In such cases, the loader seems to attempt resolving overlays starting with -, rather than correctly resolving the overlay name.

Related to Again, you are using the wrong image. You cannot assume an image for the opi5+ works for the opi5b. Those are different boards.

wrong image. you cannot simply use an image for board X and assume it works on board Y

Can someone pull request this to have it working myself as well please?

I managed to disable heartbeat. I am running HA based on debian trixie and my it was only led i could change to off echo 0 | sudo tee /sys/class/leds/state-led/brightness

I can't install mpd on Armbian v26.2 rolling for NanoPi Air running Armbian Linux 6.12.76-current-sunxi Packages: Ubuntu stable (noble) user@nanopiair:~$ sudo apt install mpd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mpd : Depends: libavcodec61 (>= 7:7.0) but it is not installable Depends: libavfilter10 (>= 7:7.0) but it is not installable Depends: libavformat61 (>= 7:7.0) but it is not installable Depends: libavutil59 (>= 7:7.0) but it is not installable Depends: libflac14 (>= 1.5.0) but it is not installable Depends: libfmt10 (>= 10.1.1+ds1) but it is not installable Depends: libicu76 (>= 76.1-1~) but it is not installable Depends: libiso9660-12 (>= 2.2.0) but it is not installable Depends: libsidplayfp6 (>= 2.12.0) but it is not going to be installed Depends: libjs-sphinxdoc (>= 8.1) but it is not going to be installed Depends: sphinx-rtd-theme-common (>= 3.0.2+dfsg) but it is not going to be installed E: Unable to correct problems, you have held broken packages. What is the issue with missing packages ? Edit: Solved by adding trixie repositories.

Continuing to dig into this. Updated the Armbian images - available via the same links above (md5sum mismatch): How to add the module to an already working system (so you don't have to reinstall from scratch): 1. Download the archive ws2801-1.0.tar.gz with the dkms source code for the ws2801 module. 2. Extract the source folder to /usr/src/ : sudo tar -xzvf ~/ws2801-1.0.tar.gz -C /usr/src/ (here ~/ is the /home directory of my user) 3. Install the module step-by-step via dkms: sudo dkms add ws2801/1.0 sudo dkms build ws2801/1.0 sudo dkms install ws2801/1.0 4. To avoid rebooting, you can load the module immediately: sudo modprobe ws2801 By default, Red should start blinking as a "heartbeat" trigger. Description of dts and demo:

A long time ago, that I started the question, but a few days ago, I started again to solve it. And with the help of several AI, I found a working solution. This is the working overlay: /dts-v1/; /plugin/; /* * NanoPI Neo2 H5 - OTG USB with switchable VBUS * Allows SD-Card as USB device on OTG port with GPIO-controlled power * * Key points: * - fragment 0: dr_mode "otg" enables dual-role (host+device detection) * - fragment 1: Removing usb0_id_det-gpios prevents "External vbus detected" error * - fragment 2: Removing gpio property from regulator keeps GPIO 354 (PR2) free for manual control * - fragment 3: GPIO 354 is controlled via usb.sh script (echo 1/0 to /sys/class/gpio/gpio354/value) * * GPIO 354 (PR2) state: * 1 = VBUS ON (USB device recognized) * 0 = VBUS OFF (USB device disconnected) */ / { compatible = "allwinner,sun50i-h5"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "otg"; status = "okay"; }; }; fragment@1 { target = <&usbphy>; __overlay__ { usb0_id_det-gpios; }; }; fragment@2 { target-path = "/usb0-vbus"; __overlay__ { gpio; status = "okay"; }; }; fragment@3 { target = <&r_pio>; __overlay__ { usb0_vbus_pin: usb0_vbus_pin { pins = "PR2"; function = "gpio_out"; output-high; }; }; }; }; This allows the standard GPIO controls using sysfs in /sys/class/gpio. I'm using the kernel Linux nanopineo2 6.6.75-current-sunxi64 on Armbian 25.11.2 bookworm (32 bit userland). Hope this helps everybody trying to achive the same 😉

I'm having a problem with my Raspberry Pi 5, which I describe below. I have a DVR connected to it via Ethernet. If I connect both at the same time, dmesg reports a failure and I can't ping the DVR to establish a connection; I have to run `ifconfig eth0 down` and `ifconfig eth0 up`. Can anyone help or know if there's a bug in the kernel version? I'm using Ubuntu 22.04. jammy root:~# dmesg | grep eth0 [ 1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a) [ 3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0. [ 3.453483] systemd[1]: Started ifup for eth0. [ 3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 11.560707] macb 1f00100000.ethernet eth0: Link is Down [ 13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off root:~# ping 192.168.200.201 PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data. ^C --- 192.168.200.201 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 13305ms root:~# ifconfig eth0 down root:~# ifconfig eth0 up root:~# dmesg | grep eth0 [ 1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a) [ 3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0. [ 3.453483] systemd[1]: Started ifup for eth0. [ 3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 11.560707] macb 1f00100000.ethernet eth0: Link is Down [ 13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 147.034711] macb 1f00100000.ethernet eth0: Link is Down [ 151.855860] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 151.855871] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 152.869842] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off root:~# ping 192.168.200.201 PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data. 64 bytes from 192.168.200.201: icmp_seq=1 ttl=64 time=1.01 ms 64 bytes from 192.168.200.201: icmp_seq=2 ttl=64 time=1.01 ms ^C --- 192.168.200.201 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.007/1.007/1.007/0.000 ms