Andro

I am unable to see how to setup the Pimoroni NVME base for the Raspberry PI 5 with Armbian 23.11.3. Are there published instructions? Is this supported?

Fresh install of Armbian 22 XFCE as at today and exact same issue. This does not appear to be fixed? W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Failed to fetch http://cli.github.com/packages/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059

I think the vendor has fixed the ethernet problem in their release build. Has this fix made it into armbian yet or not? Sorry, it's not clear to me from reading this thread whether that is a definite yes or no.

Hello All, I have been away from this board for a while. Apologies for the very basic question, but how can I obtain or build an image for the Potato with the fixes described here? I read something about Armbian nightly builds no longer being made available (and, even more basic, I don't know where they are. Just the head of the git repo?)

Thanks @Igor. Just asking!

The supported Armbian build environment is Ubuntu 16.04 LTS I know. Is there any strong reason why one should not build now on Ubuntu 17.10?

Hi @TonyMac32 and @Da Xue, How does one obtain this patched image?

Hi Da Xue, Any progress?

I built the latest 5.34 Armbian image for the Le Potato and it still locks up after about an hour or so of ethernet traffic (using turbovnc), rendering this very nice little board unusable. I see others confirming the problem, but are there any people able to run this board successfully? A bit of a puzzle.

I saw references on the site to a countdown in days to a major new release, but that has now disappeared, and I also see various mentions of version 5.34 but I do not know where to obtain this. The highest release in github seems to be 5.24. How does one find this? Apologies if this appears to be a stupid question - I looked everywhere.

Hi @TonyMac32 now confirming that I can indeed confirm that a constant stream of inbound traffic causes the ethernet to lock up after 15 minutes to an hour or so. This test is repeatable and reliable. As to how to provide logs or any further detail, I don't really know.

I have the Libre Le Potato, running the Armbian Ubuntu image [Ubunutu desktop - mainline kernel] from the download page. 2GB model, exactly as the OP has above. I see the same issue - ethernet connectivity reliably just stops after about 15 minutes or so of use, just running turbovncserver and one remote session, nothing too strenuous. Apart from that, it's a wonderful little board and Armbian on it is really excellent. So, just adding more weight to this observation by others.

Builduing any Armbian image, headless or desktop, for any of the Orange Pi series results in a blank orange screen on boot and no futher action. The UART outputs nothing. However, the downloadable prebuilt Armbian image does work. As to the UART problem, I am beginning to suspect a board hardware problem. As to the non-booting issue, I have no idea. I did observe that I could find the IP address and ssh into the machine despite this lack of display output. Are there logs I could find to help diagnose this issue?

No matter what I do, when I use an Armbian image built with compile.sh I get a blank orange screen on the OPi Plus 2. The downloadable pre-built image from Armbian for the board works fine. Wanting to debug this, I have an Adafruit UART serial cable adapter, known functioning and working. If I attach this to the UART pins on the small header near the power socket I get no output (and I have swapped RX and TX to no avail). How does one enable this UART? Am I using a wrong approach? I have console=both in armbianEnv.txt.

Reading the above thread, is there any support for the Videostrong 6 core RK3399 board? Can Armbian run on that system?

SOLVED - I am using a combined 5V and SATA cable sold for use with the pcDuino. I checked the polarity of the 5V connector, and sure enough, it is reversed on the Orange Pi Plus 2 compared to the pcDuino. Swapping the pins to give the correct polarity on the Orange Pi completely solves the problem. There was no software configuration required. This may be useful for others to know in the future. As to the orange screen and no response from builds with compile.sh, that matter still remains. Any clues, anybody?

OK, so I downloaded images for the Orange Pi Plus, and the Orange Pi Plus 2. Both boot nicely, but neither can see the SATA drive, a known working unit. I am using the officially supplied 5V 3A power supply. I have successfull built many images for the pcDuino 3. But using compile.sh to build a user image for the Orange Pi Plus 2, or the plain Plus, the system will not boot in either case and simply presents a blank screen, filled with orange, and no text. What is the explanation for this? Why can't the system see its SATA drive? How does one debug this? There is not a single mention in the system log via journalctl or dmesg referrging to anything other than the eMMC storage.

Does Armbian run on the Orange Pi Plus 2, and support its SATA interface? I was unable to find this exact board model in the compile.sh menu list.

Hello Igor, Thanks for helping out this newbie to embedded Linux. Indeed, setting the CONFIG_GMAC_TX_DELAY to 3 for the pcDuino 3 makes the ethernet spring into life and function perfectly. I am sure others must have encountered this also, so I will learn how to make a patch properly and correctly and give it a good soak test and then push this fix back to the community. The pcDuino 3 is turning out for my purposes to be a surprisingly capable little board, and the price has suddenly dropped substantially here in Australia making it very affordable and excellent value, especially with the onboard SATA which works just great. Armbian on the pcDuino is so much superior to the poor system that is installed on the board at purchase that I am quite overwhelmed. Once more, thanks!

More information on this problem, confirmed by experiment. The GMAC delay is certainly the issue. Using the pcDuino Nano image works fine. If I do a diff between the two u-boot.cfg files for the pcDuino3 and the pcDuino3 Nano, we have the following: 120c120 < #define CONFIG_GMAC_TX_DELAY 0 --- > #define CONFIG_GMAC_TX_DELAY 3 204c204 < #define CONFIG_USB1_VBUS_PIN "PH6" --- > #define CONFIG_USB1_VBUS_PIN "PH11" 241a242 > #define CONFIG_RGMII 1 334c335 < #define CONFIG_DEFAULT_DEVICE_TREE "sun7i-a20-pcduino3" --- > #define CONFIG_DEFAULT_DEVICE_TREE "sun7i-a20-pcduino3-nano" It's clear the delay of 3 in the Nano config makes the ethernet work. So now my question becomes, as a newbie, how do I make this modification to u-boot.cfg in the build process? I am unclear as to what modifications need to be made to compile.sh or elsewhere to achieve this. All assistance gratefully received.

Sorry - this should be posted under A20.

Using the Ubuntu Armbian image for pcDuino 3 I am unable to get the ethernet device eth1 to work. Wireless works fine, but trying to get an IP address for eth1 fails consistently. I have read various indications that this may be an issue with GMAC TX delays or similar, but as a newbie to pcDuino and embedded Linux I do not know how to alter or adjust this, or if this is even the problem. Has anybody else experienced this with the pcDuino3 and is there a solution? As a long time UNIX developer I am reasonably confident this is not merely a UNIX configuration issue, as I have configured the pcDuino 3 Ubuntu identically to my other reference Ubuntu servers which work fine. This is the exact image file I built: Armbian_5.32_Pcduino3_Ubuntu_xenial_default_3.4.113_desktop.img