All Activity

I realized that, and connected the pi5 to the lan port on my wifi router but wasn't able to see it in the clients list on my router dashboard (192.168.1.1). Waited for 10-15 mins.

You normally connect ethernet to a switch or router not directly to a laptop. You need something providing dhcp addresses and routing traffic between connected devices. While is is possible to setup a laptop to at as a dhcp server and to route traffic that isn't normal and isn't easy to setup correctly. You just need to plug the board into your 'network' and plug you laptop into the same network.

Ok guys, it's almost a year after my last post and I'm finally back at the project 🙂 I've read some mail about upcoming new releases and I'm no here to ask what version I should try to use on an old (unsupported or "community supported") Cubieboard 2 with 1G of RAM, 100Mbits/s Ethernet and Allwinner A20. Is it possible to use the NAND flash in the meantime? My Goal ist to build some appliance for some smarthome things, including 3 pcs. PIP4048ms PV inverters (in 3 phase combination), accumulators (LiFePo with Daly BMS), MQTT, an SQL Database and so on. I'm still don't know what to use at as user frontend, "solaranzeige.de", homeassistant or whatever. I have 3 such cubieboard 2's and I have kits named DVK521 which contain an LCD with touchscreen, an breakout board and even an camera module, that's why I'm trying to use one of them, nice that they have an SATA connector so I can use spinning rust. power should be enough for the project, 1GByte RAM is ..so lala... Last time I've tried an Armbian Version that don't even read the the config files. So please, what version I should use actually? Which build environment? Kind regards, Holm

Dear Armbian Community, We are excited to announce that our new release is approaching quickly, with an estimated release date of May 25th. Our team is working actively on the final touches, focusing on stability and fine-tuning advanced features such as 3D and video acceleration. We’re utilizing the best available methods, as there are multiple options to consider. We are adjusting our build targets to include stable, rolling and application-specific builds. Stable Releases: For those who prefer a more reliable and tested environment. Rolling Releases: For the latest updates and experimental features. Applications: Optimized builds for specific applications. We will continue to support Jammy (old stable Ubuntu) while gradually introducing Noble as the latter has numerous bugs from upstream user space applications. Official Partnership with Radxa: We are thrilled to announce a new official partnership with Radxa. This collaboration will enhance support for their newly released RK3588 boards, bringing more robust and reliable options to our users. Community Engagement and Giveaways: One of our current giveaways is nearing its end, but don’t worry – a new one is here! Stay tuned for more exciting opportunities. Focus Areas: As we approach the release date, we ask for your help, especially in the areas of desktop acceleration and desktop environments. While we have covered base OS system features well, your contributions and feedback are invaluable. Community Poll Results: We recently conducted a poll to understand our community’s involvement in open-source projects. Here are the results: I’m an active contributor: 28.6% Contributed occasionally: 31.7% Not yet, but I’d like to: 28.6% No, why?: 11.1% These results are based on 63 votes and show a vibrant and engaged community, with a significant number of active and occasional contributors. For those who haven’t contributed yet but would like to, we encourage you to get involved. Your participation can make a significant difference! Thank you for your continued support and contributions. Together, we can make Armbian even better! Best regards, The Armbian Team The post New Release Approaching Fast! first appeared on Armbian. View the full article

I can't see my rpi5 installed with armbian cli on nmap / angry ip scanner, when I connect it via ethernet to my laptop. The getting started guide mentions it via serial or hdmi, do I need to enable ethernet somewhere??

Hi there. I have a Pine A64(+) board (https://pine64.org/documentation/Pine_A64/) I have been experiencing this issue since last year. I updated the SO (armbian version + kernel) several times and it didn't resolve the issue. It happens randomly. The CPU and storage are not overheated (30º C each) and I tested all physical components (board, ethernet wire, switch, ...) ambianmonitor -u -> https://paste.armbian.com/arozepuxen Things I tested for now: - Daily reboot. Sometimes eth0 is not wake up after boot and I have to physically power-toggle the board. - Stay on latest raspbian release (24.2.1) + latest kernel (6.6.16) + latest uboot. Same issue. - Stay on latest raspbian release (24.2.1) + legacy kernel (6.1.77) + latest uboot. Same issue. - Armbian 23.11.1 Jammy with Linux 6.1.63-current-sunxi64 was also some time the SO in the board. Same issue. - Also I set the segmentation and MTU as here but same issue: Notes: - CPU is "on demand". That's also why the temperature is OK. - Somehow is only 100Mbits available (the board has gigabit port). By the way, is not my concerning now. - https://github.com/jwrdegoede/rtl8189ES_linux/tree/rtl8189fs I saw this driver. Is this an option? Should I try? Any idea? Should I totally rebuild the microsd SO from zero with an ARMBIAN from 2021 or so? Any other suggestion? The board is totally unstable as it currently is and I guess is software related (driver maybe) Thank you.

I ask this question purely out of curiosity - why is the userpatches folder not in the build folder when it is first cloned

Hi, I am new here but been playing with the opi zero 2w for a bit with the zero 3 image. So happy to now see 2w images have appeared. I have the expansion board and was hoping to get the ethernet port working at some point. I mainly want to use this device to run headless and be able to shut it down when I push one of the buttons on the expansion board. Is this possible with any of the current images?

I had the same issue. Not able to see an hdmi output unless i used a usb-c to hdmi dongle. I was able to restore hdmi output using the instructions in this post: Could be an issue with cheap displays only? The display I'm using is a RCA tv so I'm not really sure.

Hi, sorry my english Did you got a working system? I can boot MiniArch-20231112-6.7.4-board-h313.x96_q_lpddr3-SD-Image but ethernet won't work and MiniArch-20231112-6.7.4-board-h616.tanix_tx6s_axp313-SD-Image won't boot.. I'm in hope to get Klipper work on this tvbox

I have this same issue. It is displaying 1920x1080 on my 1920x1200 old Dell LCD, when using the HDMI input. If I use an adapter to connect the RockPro64 to to a DVI-D input, I only get 1024x768, bleh.

Yes! I get a degraded x1 link, too, with a Samsung 980 Pro. I assumed it had never worked at x4, so it's interesting to hear that it is a regression.

I was having the same issue and used Colton's solution. Worked like a charm, thank you.

I've seen this question asked quite frequently here and all the posts end before there is a solution. I think it's time we had a crystal clear discussion on how it can be done. Not just for my curiosity, but for the people who've asked before and for the people who will ask in the future. The reason: Many hats/shields designed for RaspberryPi would otherwise be compatible with OrangePi if Armbian/u-boot didn't direct the debug output to UART0. UART0 is the most commonly used serial connection for hats/shields designed for RaspberryPi. OrangePi has multiple UART gpio so it would make sense for the O.S. (Armbian) to use the one that least impacts the users ability to actually use their hardware. Debug output is important but not so much so that the user cannot easily disable it.

- Update: Kernel 5.1 Wifi-K510: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.bin sudo reboot now nmcli dev wifi sudo rmmod brcmfmac_wcc brcmfmac brcmutil modprobe brcmfmac - Image: Updated K510 test image: https://drive.google.com/file/d/1ng0j7BhpMya7vOfQjhxmM0HipQ6_F8Ep/view?usp=sharing - BaseFiles: RK3566-H96-MAX-VENDOR-51-V3:https://drive.google.com/file/d/1_N5jQ6wp3rk5Y4xeZK3sEp-L_o5H6KJv/view?usp=drive_link edit Rockchip U-boot Legacy 4.19 DTS: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/arch/arm/dts/rk3566-h96.dts edit Rockchip U-boot Legacy 4.19 DEFCONFIG: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/configs/h96-rk3566_defconfig RK3566-H96-MAX-LEGACY-51-V3.zip

if your using the build system, you can call "add_packages_to_rootfs" with a simple list of packages (i.e. "add_packages_to_rootfs build-essential"), it will handle the references for you. you can also remove packages with "remove-packages" the same way

@primoitt thanks for those Infos, even if not strictly hardware related , they are usefull for building new distros Could be also interesting open a specific thread related ti repositories issues and leave this for hardware specific

hey @jock @SteeMan focal builded flawlessly! [🐳|🔨] sent 16.83M bytes received 2.18K bytes 33.67M bytes/sec [🐳|🔨] total size is 16.82M speedup is 1.00 [🐳|🔨] '/usr/bin/qemu-arm-static' -> '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/usr/bin/qemu-arm-static' [🐳|🌿] Updating initramfs... [ TMPDIR=/tmp update-initramfs -u -k 4.4.194-legacy-rk322x ] [🐳|🔨] update-initramfs: Generating /boot/initrd.img-4.4.194-legacy-rk322x [🐳|🔨] update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-4.4.194-legacy-rk322x [🐳|🔨] Image Name: uInitrd [🐳|🔨] Created: Mon May 20 18:33:54 2024 [🐳|🔨] Image Type: ARM Linux RAMDisk Image (gzip compressed) [🐳|🔨] Data Size: 5816136 Bytes = 5679.82 KiB = 5.55 MiB [🐳|🔨] Load Address: 00000000 [🐳|🔨] Entry Point: 00000000 [🐳|🔨] update-initramfs: Armbian: Symlinking /boot/uInitrd-4.4.194-legacy-rk322x to /boot/uInitrd [🐳|🔨] '/boot/uInitrd' -> 'uInitrd-4.4.194-legacy-rk322x' [🐳|🔨] update-initramfs: Armbian: done. [🐳|🌱] Updated initramfs. [ TMPDIR=/tmp update-initramfs -u -k 4.4.194-legacy-rk322x ] [🐳|🔨] '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/boot/initrd.img-4.4.194-legacy-rk322x' -> '/armbian/cache/initrd/initrd.img-4.4.194-legacy-rk322x-b45d4cabfa6aaf61a91db4025d6d89c8' [🐳|🔨] '/armbian/.tmp/work-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/initrd.img-4.4.194-legacy-rk322x.4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.manifest' -> '/armbian/cache/initrd/initrd.manifest-4.4.194-legacy-rk322x.last.manifest' [🐳|🌿] Re-enabling [ initramfs-tools hook for kernel ] [🐳|🔨] mode of '/etc/kernel/postinst.d/initramfs-tools' changed from 0644 (rw-r--r--) to 0755 (rwxr-xr-x) [🐳|🌱] Unmounting [ /armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e ] [🐳|🔨] removed '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/usr/bin/qemu-arm-static' [🐳|🌱] Free SD cache [🐳|🌱] Mount point [ 90% ] [🐳|🌱] Preparing u-boot bootloader [ LOOP=/dev/loop8 - /armbian/output/debs/linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb ] [🐳|🌱] Sourcing u-boot install functions [ /armbian/output/debs/linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb ] [🐳|🌱] Writing u-boot bootloader [ /dev/loop8 ] [🐳|🌿] Unmounting recursively [ MOUNT - be patient ] [🐳|🌿] Freeing loop device [ /dev/loop8 ] [🐳|🔨] renamed '/armbian/.tmp/rootfs-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.raw' -> '/armbian/.tmp/image-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img' [🐳|🌱] Done building [ Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img ] [🐳|🌱] SHA256 calculating [ Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img (860.00MiB) ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.sha (199.00B) ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.txt (19.30KiB) ] [🐳|🌿] Unmounting recursively [ SDCARD rootfs finished - be patient ] [🐳|🌿] Done building image [ rk322x-box ] [🐳|🌱] Runtime [ 152:09 min ] [🐳|✨] Repeat Build Options [ ./compile.sh BOARD=rk322x-box BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes INSTALL_HEADERS=yes KERNEL_CONFIGURE=yes KERNEL_KEEP_CONFIG=yes RELEASE=focal ] [🐳|🌱] Cleaning up [ please wait for cleanups to finish ] [🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.log.ans ] [🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.log.ans https://paste.armbian.com/log ] ls output/images/ -lah total 741M drwxr-xr-x 2 root root 4.0K May 20 18:34 . drwxr-xr-x 7 root root 4.0K May 20 17:48 .. -rw-rw-r-- 1 root root 860M May 20 18:33 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img -rw-rw-r-- 1 root root 199 May 20 18:34 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.sha -rw-rw-r-- 1 root root 20K May 20 18:33 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.txt But there's no linux-headers... 😔😔😔 /armbian/output/debs# ls -lah total 144M drwxr-xr-x 3 root root 4.0K May 20 18:06 . drwxr-xr-x 7 root root 4.0K May 20 17:48 .. -rw-rw-r-- 1 root root 1.6M May 20 18:06 armbian-bsp-cli-rk322x-box-legacy_24.2.0-trunk_armhf__1-PCf77f-V24e2-H68df-Be8be-Rf32b.deb -rw-rw-r-- 1 root root 87M May 20 18:06 armbian-firmware_24.2.0-trunk_all__1-SA6fae-B90f5-R448a.deb -rw-rw-r-- 1 root root 1.4K May 20 18:06 fake-ubuntu-advantage-tools_24.2.0-trunk_all__1-Bfcde-R448a.deb drwxrwxr-x 2 root root 4.0K May 20 18:06 focal -rw-rw-r-- 1 root root 4.9M May 20 18:06 linux-dtb-legacy-rk322x_24.2.0-trunk_armhf__4.4.194-Sf8f4-Dc654-Pb5a2-C999999Hfe66-HK01ba-V014b-B1743-R448a.deb -rw-rw-r-- 1 root root 51M May 20 18:06 linux-image-legacy-rk322x_24.2.0-trunk_armhf__4.4.194-Sf8f4-Dc654-Pb5a2-C999999Hfe66-HK01ba-V014b-B1743-R448a.deb -rw-rw-r-- 1 root root 439K May 20 16:02 linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb

This is community maintained software. I'm not aware of anyone else that has that specific box. So you are welcome to track down the issue and submit a PR for a fix.

Results of today: I found no image that would let me boot from EMMC without the micro SD, but when i edit the armbianEnv on the SD to point to the UUID of the EMMC partion with installed os it boots from the EMMC. So my conclusion is that i need to build my own U-Boot.bin to get around the poweron issue with the emmc.