Search the Community

Hi, I have "ARMBIAN Debian GNU/Linux 10 (buster) 4.6.5-sunxi" running on a BananPi R1 router. I used to have it set up such that while it booted off the SD card, it had its root FS on an SSD. Some time ago, I had to re-install as an upgrade went fatally wrong and now I cannot remember the exact steps to switch from the SD card to the SSD as the root FS. I changed the root= in /boot/boot.cmd and generated the /boot/boot-scr and also changed the /etc/fstab entry but findmnt -n -o SOURCE / still shows "/dev/mmcblk0p1". Can anyone tell me the steps to take in switching to a new root FS? Thanks and ... stay healthy! Josef

I know Lamobo-r1 has many problems and that the support ended, but it works fine for me. Everything works fine with kernel 4.14.84-sunxi, however, when I update the kernel, the b53 switch does not work anymore. I need to update the kernel to add another wifi usb dongle that seems to work only with newer kernels (https://github.com/aircrack-ng/rtl8812au/issues/272#issuecomment-467983704). Anybody experiencing the same problem? Any ideas for a workaround?

I have observed the same problem. My NanoPi-R1 - which interestingly identifies at a NEO on the boot UART console...... I do have a serial UART console. So have captured my findings. Albeit limited as verbosity isnt set high and the console log when booting the SD armbian image Armbian_23.5.2_Nanopi-r1_bookworm_current_6.1.30_minimal.img.xz SHA: ea10d9a0940a516be9f627f4a943caf39f3c2f3d1e80afafc95f78c65e4d2d10 Written to a 8G Sandisk SD. Put into the SD slot and powered the unit on. Console output gets to Starting Kernel ... and then the red LED light just blinks and blinks for a long time with no change. Unit has DHCPd and I am able to ssh into it with the root defaults. Establish my new root passwd and setup a user account and locale details etc. I then run the nand-sata-install Select the emmc and it takes about 2 minutes to copy over after all the warnings etc. Armbian for NanoPi R1 install script, https://www.armbian.com qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq lqqqqqqqqqqqqqqqqqqqqqqqqqqqeMMC installqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x x All done. Power off x x x tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu x <Power off> < Exit > x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj root@nanopi-r1:~# Then the unit reboots and the console comes alive and displays. U-Boot SPL 2022.07-armbian (Jun 06 2023 - 04:52:59 +0000) DRAM: 1024 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### https://paste.armbian.com/ivopizatot

Hello, I am in a project where I need to use armbian on an OrangePi R1 Plus, but I realized that it is not yet available on the site. Any prevision?

I have one of these boards: http://www.orangepi.org/Orange%20Pi%20R1%20Plus/ https://photos.app.goo.gl/1otMwG4totvNbGo88 It's kept cool with a heatsink, and fan (30-35c). Currently, I'm running the orange pi supplied version of openwrt. It's a snapshot version, so the kernel isn't compatible with some packages. My question then is, is there a script out there that can transform armbian into a router, with a firewall, web interface, and easy to use? I'd like to give it a try if such a thing exists. Sent from my Redmi Note 9S using Tapatalk

Hi, We've built a network experimentation system using NanoPi R1 modules, but when load testing the system with iperf3, we are seeing the on-board RTL8152 interface enter a state where it does not seem to be responding until the board is power cycled. The system consists of 32 NanoPi modules connected in a torus, with the 1Gig interface connected to its neighbour's 100Mbit interface. An additional USB Ethernet dongle functions as a control interface. The modules are powered from a Ubiquiti PoE switch, using this type of isolated PoE splitter. Eyeballing the switch UI, power consumption per node seems to hover between 2.3W-3.5W, depending on load. We're using the latest Ubuntu-based image, with kernel 5.4.28. Under light loads, the system works fine, but when performing load tests, we're seeing the RTL8152 entering some kind of lock-up state. As can be seen from the system logs, first the netdev watchdog triggers, then the kernel tries to reset the USB device, finally reporting that it is unable to enumerate the device. After encountering this problem, if the node is rebooted, the USB device can still not be enumerated, and will remain unresponsive until it is powercycled. The external USB Ethernet dongle stays working through all of this, so it seems that the USB host controller and subsystem works OK. We haven't seen any issues with the 1Gig interface. Searching the net, I have found reports with similar backtraces, but they seem to be either several years old, or related to the RTL8153 chip, which shares the same driver. In either case, none of them seem to offer any answers as to what's going on, or if there is any fix. Has anyone else seen this? Any ideas if it's a driver or hardware issue? Relevant bit from the kernel log: Full diagnostic dump:

What gives with the Armbian website links? Links to all previous versions Armbian for the OrangePi R1 Plus LTS have been removed. The links to SHA hash and PGP signature do nothing. I was hoping to use an image that was based on Debian Bullseye, but that link has been recently removed. It is possible to create my image, but I would spend my time working on my code, not wading through the options to create an image.

Having used YOCTO for a couple of years at work I assumed that creating my own Armbian image was going to be difficult. However to my suprise I was able to create a Bullseye image for the Orange Pi R1+ LTS in less than 1 hour. And, .... it actually runs correctly on the target board. That is pretty good.

http://paste.armbian.com/icedujiguw.yaml Hello everyone, trying to give new life to this old Orange Pi+ 2. Here is described what hapens when i try to boot up latest image. Can anyone help. Thanks in advance. Armbian 23.8 Bookworm Kernel 6.2.y, Size: 421Mb, Release date: Jun 3, 2023 SBC gets stuck after the request Sense .. and doesnt booy up, if i plug a device in usb ports, it bootloops .. see below using same sd-card and a diffrent image file works with no issues . hardware : grounded out pin 9 of the SD card slot (checked with multimeter and works) U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface9 eth0: ethernet@1c30000 starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... EHCI timed out on TD - token=0x80008c80 unable to get device descriptor (error=-1) 2 USB Device(s) found scanning bus usb@1c1d000 for devices... Device NOT ready Request Sense returned 02 3A 00 SBC gets stuck after the request Sense .. and doesnt booy up, if i plug a device in usb ports, it bootloops .. see below U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface9 eth0: ethernet@1c30000 starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... Device NOT ready Request Sense returned 02 3A 00 undefined instruction pc : [<bbf93980>] lr : [<bffa3391>] reloc pc : [<4600b980>] lr : [<4a01b391>] sp : bbf5e848 ip : 0000001c fp : bffde94a r10: bffe5c00 r9 : bbf67ec0 r8 : 00000000 r7 : 00000000 r6 : bbf93b18 r5 : a0000000 r4 : bbf93b80 r3 : bbf93980 r2 : 00000000 r1 : 00000000 r0 : bbf93b80 Flags: NzCv IRQs off FIQs off Mode SVC_32 Code: bbf68cc8 00000000 00000000 00000000 (ffffffff) Resetting CPU ... resetting ... U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1

I'm trying to load Armbian on my NanoPi R1, but it doesn't boot. I've been able to boot it successfully with https://www.friendlyarm.com/ official image, and also various (unsupported) DietPi images. I tried Armbian_21.02.3_Nanopi-r1_focal_current_5.10.21.img.xz using Balena Etcher to copy it to the SDCard on a Macbook laptop. Instead of seeing the uboot startup, the terminal remains completely empty. No idea where to start on debugging this. Please help! Thanks!

Description Mainline kernel 6.3 and above implements yt8531 driver. This pull request removes the legacy driver patch and fix the device tree for Orange Pi 4 LTS and other devices to use that driver. Note: this PR has a "dependency" upon this other PR (https://github.com/armbian/build/pull/5290) - these two PRs are unrelated, but the PR-5290 bug does not allow me to easily test without having conflicts later. This is just a note, everything should go on flawlessy once PR-5290 is merged. Jira reference number AR-1774 How Has This Been Tested? [x] Tested dtb on a live Orange Pi 4 LTS system [ ] Tested on Orange Pi R1 LTS (@schwar3kat) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Orangepi zero plus Images boot, network connection functions (iperf3). USB ports function. Orangepi R1 Images boot, both ethernet ports and wifi function as expected (iperf3).

I'm a newbie to Armbian, just a hobby user, no company behind me. While building Armbian for my Banana Pi R1 (aka Lamobo R1) [Allwinner A20, sunxi] the build system gave the following warnings originating from the U-Boot project. I think some maintainers and/or experienced users should take a look at the following. ===================== WARNING ====================== This board does not use CONFIG_DM_MMC. Please update the board to use CONFIG_DM_MMC before the v2019.04 release. Failure to update by the deadline may result in board removal. See doc/driver-model/MIGRATION.txt for more info. ==================================================== ===================== WARNING ====================== This board does not use CONFIG_DM_USB. Please update the board to use CONFIG_DM_USB before the v2019.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/MIGRATION.txt for more info. ==================================================== ===================== WARNING ====================== This board does not use CONFIG_DM_SCSI. Please update the storage controller to use CONFIG_DM_SCSI before the v2019.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/MIGRATION.txt for more info. ==================================================== ===================== WARNING ====================== This board does not use CONFIG_DM_VIDEO Please update the board to use CONFIG_DM_VIDEO before the v2019.07 release. Failure to update by the deadline may result in board removal. See doc/driver-model/MIGRATION.txt for more info. ==================================================== Here's also the full content of the file ./cache/sources/u-boot/v2019.01/doc/driver-model/MIGRATION.txt :

Orangepi R1 Plus LTS (RK3328) - networking issue AR-1747. Caused by one of the network interface logical names changing from eth0 to end0. I can can submit a PR to fix this with a rename in /etc/udev/rules.d/70-rename-lan.rules which is already created from a hook in the board config file (to rename the other network interface). Already tested and works as expected on current and edge, Ubuntu and Debian. Before I take this route, I'm just wondering if anyone knows a reason for this happening that could possibly lead to a better fix? I didn't find anything obvious in the PR's.

I use NANOPI R1 in one of my projects. Now I need to develop a board to make a physical watchdog from NANOPI R1 itself and an RTC (the NANOPI R1 RTC does not work). I have two possibilities: One is to use the already integrated UART, or use a USB - I2C converter. Using the UART I would communicate the NANOPI with a 328P microcontroller, and from there I would collect the RTC information (with i2c between 328P and RTC), in addition to sending the frequent information to the 328P to keep the watchdog active. Using the I2C, the RTC would be connected to the I2C BUS and I would do the direct query via NANOPI R1, as well as send the frequent information via I2C to the 328P or ATTINY85 (I can use this CI - it have I2C) to keep the watchdog active. I want an opinion: I would like to know how you would do that? Would it be using I2C or using UART? If they were going to use UART, I need the two ports available on NANOPI R1 (because I already use a Nextion HMI on a UART port). So can i use UART_DBG too? What problems can I face?

Hi forum, I want use my R1 board as a switch and if possible to run some services as the same if possible. Now when I look in /etc/network I do see a lot of different .conf files in that folder, but I do not really know how to use or them. Therefore my questions. 1. can I use my board as switch and can I run as the same services. 2. How do I use these config files and how do I interpret the results. Thx,blub4747

rockchip64/edge/6.3: rebase/rewrite patches against v6.3.1; do archeology for mbox-less patches; materialize overwrites After the work done by @amazingfate on #5140 it is now viable to rebase all rockchip64 edge patches. This "admits" all the overwrites (full replacement) as actual patches -- it does not change the contents. materialized overwrites: add-board-helios64.patch add-board-orangepi-r1-plus.patch add-driver-for-Motorcomm-YT85xx+PHYs.patch add-board-rk3328-roc-pc.patch Special attention: wifi-4003-uwe5622-adjust-for-rockchip.patch @paolosabatino this patch is done on top of the wifi drivers patches exclusively, and fails to apply on a pure mainline tree. we should probably consider moving this into the wifi drivers patch harness, not in the rockchip tree. tl;dr: this changes this: https://rpardini.github.io/linux/armbian-next-rockchip64-6.3-20230505.html kernel patching: 119 total patches; 119 applied; 95 with problems; 4 overwrites; 54 not_mbox; 73 needs_rebase into this: https://rpardini.github.io/linux/armbian-next-rockchip64-6.3-20230506.html kernel patching: 119 total patches; 119 applied; 0 with problems View the full article

I'm a newbie. Got the NanoPi R1 that sports a UART but no Video Output. Now when I want to read the output of the serial console I need a 3-wire cable and a converter, that much I know. But what is the baud rate? Where is this configured on the armbian NanoPiR1 image (on my raspberry Pi I just checked and found the file /boot/cmdline.txt with that settings, in my case it's 115200) Why is the baud rate nowhere documented? On the download page https://www.armbian.com/nanopi-r1/ it is stated that "serial console is enabled on UART1, which is exposed on chasis" , but no hint about which speed to use. There neither is any info about the baud rate on the friendlyelec site where they provide various OS images for download. Plenty of documentation on how to wire the serial cable though. Is there a kind of industry standard that everyone knows and therefore it is not necessary to include it in the how-to guides. Or are we supposed to try every rate from 9600 upward until we get readable output? Thanks. So far I couldn't get my NanoPi to work, it just blinks red, and I haven't seen anything on the console too. It's a brick, possible defective hardware.

Hi. I'm using "Orangepi-r1_focal_current_5.8.5" Armbian. I'm connected to it via Wifi. Everything working fine, but after few hours, I notice that it is no longer showing on my network. If I connect by cable I can ssh to it via ethernet without any issue and it stays available for several days without disconnecting. Any idea why this happens? when Wifi disconnects I will have to reboot to show it again. And I am not running any program on it. Is orange pi r1 wifi like orange pi zero wifi suffering from poor software support?

Hi, I have a few questions about the NanoPi R1 system. 1) The (USB > TTL) debug serial port is that 3.3v or 5v? I need to get the correct adapter. 2) Hooking up a serial debug cable is there enough room to close the front plate? 3) Can the system run from eMMc and get software upgraded from the SD-Card? 4) I could not not find clear procedures for this. Am not familiar with OpenWRT. 5) Can the Ethernet port be used to talk to a P.C. running Windows (putty) or would the micro-USB to P.C. be better? 6) I would eventually use WiFi for remote access and updates. 7) Can the NanoPi R1 run Apache WEB server? 8) Can this run Debian or Ubuntu? If so where would the downloads be found? Looks like a fine product. If it works out I may buy several. I do have experience with Linux (several flavors) and the Beaglebone. My history goes back to 1974 and Unix from Bell Labs.

Hello! My problem is with paying for OrangePi Plus 2 (not E), but I haven't found a suitable section. Dear administrators, please fix the split if I made a big mistake. I was installed image orangepiplus/Bullseye_current (Nov 30, 2022) in eMMC. All works is normal. In armbian-config I was run Firmware (Update all packages and firmware). Afeter this the board are not loading from eMMC or external CD with current image Armbian. The Ubuntu from site orangepi.org the loading is normal. In debug-uart I see a cyclical reboot with: <0xdd>!␊ ␊ <0xea><0xfc>q<0xb9><0xf6>Core: 65 devices, 18 uclasses, devicetree: separate␍␊ WDT: Not starting watchdog@1c20ca0␍␊ MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1␍␊ Loading Environment from FAT... Unable to use mmc 1:1...␍␊ In: serial@1c28000␍␊ Out: serial@1c28000␍␊ Err: serial@1c28000␍␊ Net: phy interface9␍␊ eth0: ethernet@1c30000␍␊ starting USB...␍␊ Bus usb@1c1b000: USB EHCI 1.00␍␊ Bus usb@1c1d000: USB EHCI 1.00␍␊ scanning bus usb@1c1b000 for devices... 2 USB Device(s) found␍␊ scanning bus usb@1c1d000 for devices... Device NOT ready␍␊ Request Sense returned 02 3A 00␍␊ prefetch abort␍␊ pc : [<fffffffa>]⇥ lr : [<bffaa4b3>]␍␊ reloc pc : [<8a077ffa>]⇥ lr : [<4a0224b3>]␍␊ sp : b8a99728 ip : bbf6c038⇥ fp : bffdec47␍␊ r10: ffffffff r9 : bbf67ec0⇥ r8 : b8a99780␍␊ r7 : 00000000 r6 : 00000001⇥ r5 : e59ff014 r4 : 00000000␍␊ r3 : b8a99780 r2 : 00000001⇥ r1 : 00000000 r0 : e59ff014␍␊ Flags: nzcv IRQs off FIQs off Mode SVC_32 (T)␍␊ Code: 0000 0000 0000 0000 (0000) 0000 ␍␊ Resetting CPU ...␍␊ ␍␊ resetting ...␍␊ The problem is that the board no longer wants to load with EXT4, and now it loads only with FAT32. Please tell me how to teach the board to boot from EXT4 again.

esd electronics CAN-PCIeMiniHS/402 is a half-size mini PCIe card with four CAN FD Interfaces designed for embedded systems with one model adding extended temperature range support from -40C to 85°C. The company also introduced the CAN-Mini/402-4-DSUB9-150mm adapter to more easily connect the four CAN network interfaces via DSUB9 connectors. It comes with four individual small adapter boards, each equipped with a DSUB9 plug and a jumper for selectable onboard CAN termination, as well as 150 mm long wires. CAN-PCIeMiniHS/402 highlights: 4x CAN FD interfaces according to ISO 11898-2, no galvanic isolation, bit rates from 10 Kbit/s up to 8 Mbit/s Bus mastering and local data management by FPGA (Intel Cyclone IV EP4CGX) PCIe Mini interface according to Mini Card Electromechanical Spec. R1.2 Supports MSI (Message Signaled Interrupts) HW-Timestamp capable Dimensions – 30 mm x 27 mm (Half-size mini PCIe form factor) Temperature Range Standard – 0°C … +75°C Extended range: [...] The post Half-size mini PCIe card adds up to 4 CAN FD interfaces to embedded systems appeared first on CNX Software - Embedded Systems News. View the full article

Description A user from the forum reports that a new rockchip rk3288-based board Tinkerboard S R2.0 has no wifi (see discussion here). After some talk, it seems that this board revision uses a Realtek rtl8723ds chip, whereas the R1.01 board uses rtl8723bs. This PR enabled the rtl8723ds wifi module that curiously was previously enabled in kernel 5.15 but somehow has been disabled in the advancement to 6.1. Current and edge kernel on rockchip family are both on 6.1 right now. The board actually is in a limbo where probably much of the design is shared with regular Tinkerboard/S, but other differences are unknown. Enabling a kernel module to let wifi work is a relatively straight and simple task that makes an user happy. Jira reference number AR-1619 How Has This Been Tested? [x] kernel deb packages have been complied with success Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

I have the same problem with my orange pi R1 plus LTS on armbian. Floating problem. In some cases pc rebooting normally, but in 3/4 of cases it stucks. Bullseye/jammy 22.04 UPDATE: Something info about this problem in my case. I had this problem, when ive been used concrete TF cards - Smartbuy 10 class 32 gib. When i changed TF to Mirex 10 class 8 gib - problem solved. So, in user manual was info about that - all tests passed with TF SanDisk. But who reads man before working. Therefore, this card working clearly with other platforms (OPI ZERO, OPI ZERO 2 e.x.).

Hello, I'm pretty new to configuring networks completely with /etc/network/interfaces and have my problems with understanding how to set up my ports adequately. What I want to do is: I want to run a DHCP-Server on all the LAN-Ports and want to use the wireless Connection as a Gateway (using NAT, no bridge). I found this to setup the Switchports as bridged.https://github.com/armbian/build/issues/511#issuecomment-262571252 But I don't know how to set the whole system up. I read lots of introduction but all people are using the WAN-Port as Gateway and setting the wireless as Access Point. That's not what I want to do. And I also wasn't able to adept there solution to get it running how I want. Hopefully someone may help a noob... Thanks for responses in Advance! MetallJ