All Activity

Any idea about this → sudo dmesg | grep tty [ 0.471034] console [tty0] enabled [ 633.797008] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 [ 1159.103497] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 2713.702725] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 3812.350749] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.351220] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.447580] cp210x ttyUSB0: failed set request 0x12 status: -19 [ 3812.447593] cp210x ttyUSB0: failed set request 0x0 status: -19 [ 3812.447923] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 4077.235990] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 4098.361943] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 GNU/Linux sudo screen /dev/ttyUSB0 115200. [screen is terminating]

Sorry for the late reply to your request. I still have the image; let me know where to upload it if you're still interested.

Hi, eselarm. i did not have time to delete the topic. Somehow it started working. Thank you for your time.

https://github.com/armbian/linux-rockchip/pull/448 Was able to reproduce this issue and get it fixed.

in the root of the rootfs do: find . -name platform_install.sh find . -name u-boot-sunxi-with-spl.bin essentially construct correct dd arguments somethings else might be wrong though, so make sure you have a serial console/debug able with loglevel=7

@shexplorer I am in the same situation with my x88pro13 box not booting and I do not manage to go in Maskrom mode. Any progress on your side ?

Hello everyone, I am new to Armbian and need some help. I tried to install Armbian 26.2.0-trunk (https://www.armbian.com/nanopi-neo/#collapse-widget-5-0-0-0) on a NanoPi NEO Core SBC. I used Armbian Imager and wrote the latest official image (the only one available) to the SD card. After writing the image, I see only one partition on the SD card named armbi_root. When I insert the card into the device and power it on, nothing happens — there are no boot messages or logs. I think the image is missing a bootloader. So my questions are: 1) If I’m right that the bootloader is missing, how can I add a bootloader to the image? 2) How can I apply OverlayFS to this setup? 3) Do you have a link to a good article or tutorial on these topics? Thanks in advance!

Unless they have changed something very recently, you can login as root via ssh on first-run. I double checked /etc/ssh/sshd_config on an armbian install image I had downloaded, and: # Authentication: #LoginGraceTime 2m PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 PubkeyAuthentication yes <snip> # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no And inside /etc/shadow (default 1234 passwd): root:$y$j9T$SAPCtO/l2ZIj6A2frqTza/$.Z8dP41gzqRHoIS8PvXFn9fghf9rgkGqAWgXVRW4dg6:20234:0:99999:7::: So that should not be an issue here. (and there are keys inside /etc/ssh that I assume can be used at first login, I have never tried) Sounds more like a faulty sd-card that gets mounted read-only, that can cause stuff like this happening. (as mentioned earlier by Igor) Try with a different sd-card (and use armbian-imager instead of balena) and see if the same happens on another card.

I managed to do it thanks

Hello averyone I'm trying to download the multitool.img.xz can someone please help me find it or share a valide link?

The paste armbian URL displays nothing (anymore?) so without any (new) info from you, no-one can help you. AFAIR, 4K via HDMI connector is only recently available (on RK3588, not sure about RK3399), so make sure you can manage various combinations of U-Boot, kernel, rootfs. So sort of act like a developer, als make sure you have a serial console (debug) cable, else you cannot get any step further. Use a 26.2 based U-Boot and 6.19 rockchip64 kernel I would say, then see what happens.

@ag123 thank you for your response. I donated to the project in the past (search my messages, peytote was an awesome guy that helped with some specific SPI issue i had many years ago on a Orange PI i think), i am donating to few open source projects (Like FreeCAD) , will make recurring donations to Armbian for sure. Yeah i am not using any OrangePi with their original OS, no way. I need a more powerful board than OPi Zero 3, will look into the maintained and supported ones here on Armbian. Thanks for your reply.

If I understand you correctly: root via ssh is not allowed by default I usually setup (new) SBC's in a different way, but last time testing 2 of my boards with 26.2 minimal/IoT fresh image was via serial console, have not used ssh and certainly not putty. If no (serial) console, you might also have sme networking firewall issues somewhere in Windows or so, although would be vary rare. Have you setup a normal user first via (serial) console first?

I'll add my 2 cents with my more recent findings. Mind that I am using an Orange PI 5 Plus, your mileage might vary with other models. I started booting the official Orange PI (Arch) distro to clear the SPI bootloader, as suggested by @Igor sudo pacman -Syy sudo pacman -S mtd-utils sudo flash_erase /dev/mtd0 I've tried multiple flavours of the available downloads for Armbian, but I've found that all versions with kernel 6.12.58 would fail to load (the LED stays red, instead of flashing red & blue). This includes both Debian trixie and Ubuntu noble, with their desktop and minimal editions. Back in December 20204 @Igor V described similar boot issues that got resolved with kernel 6.1.75, the one that was highlighted in green at the time. So that led me to try with kernel 6.1.115 instead, and that has worked just fine. Not sure if this is an issue introduced with the newer kernel, or whether it's to be expected as it has not been officially stabilised yet. Anyway, I thought I'd share in case this can help others in the future.

having the same issiue , would like to improve the situation since most of the monitor that i use come in 16:10 format, and those resolution seem not easily available. also read here on a site it should be capable of 4k output. https://www.electromaker.io/blog/article/pine64-rockpro64-review-a-beefy-single-board-computer

I tried it with a desktop PC, but couldn't select a resolution higher than 1024x768. I read that there's a bug in newer kernel versions that's already been fixed. However, I couldn't find out if the fix is included in the downloaded image. Then I tried an older imager with kernel 4.4, and with that one, I was able to select higher resolutions. @jock I only tested it with Wi-Fi. You could also try a version with an older kernel.

If you want to add new board with its own device tree, this is a good example: https://github.com/armbian/build/pull/9423 Remember to add pictures - this way https://github.com/armbian/armbian.github.io/pull/236

Tried your image on an SD card but tried several way to get it to boot from SD was unsuccessful. I tried the toothpick on the button inside the 3.5 mm port. I tired ADB reboot update and ADB reboot recovery. But all those times, I just receive the android recovery menu when failed to boot SD. Is there any thing special I need to do to get this box to boot from SD? I will solder some dupont pins soon so I can get a better reading what is happening with serial console. But for now, do you know why it is so difficult to boot from SD. I never had this much issue with an AMLogic S9xx before.

Trouble with SSH client or failed SD card could explain this. We didn't change anything in this regard. SSH settings are Debian / Ubuntu defaults. We are not altering this. I tested latest image on XU4 and - it worked.

Auto generated images: https://dl.armbian.com/nightly/orangepirv2/Forky_current_minimal https://dl.armbian.com/nightly/orangepirv2/Noble_current_xfce

that is why i am confused, I used the one image from here (armbian.com) https://www.armbian.com/odroid-xu4/ edit: what happens if the SBC starts the first time and you cut the power before hooking up with ssh - does it fall back to other credentials? P.P.S: did a new install and 1234 just got me a "access denied" on the first attempt directly after boot

Why are you expecting this to work?

Moved to amlogic TV ox forum

@kisgezenguz you're welcome. You can check the UART RX/TX paths with the multimeter in diode/continuity mode and checking the continuity against RX (or TX) and the various SMD components. But anyway, if you read 3.3v on all the UART pins, I can guess there are three other hypothesis: * the UART RX/TX pins are correctly connected, but not to the usual debug UART. rk3399 has several uarts, so perhaps that exposed UART is not the same configured in software to be used to log the debug. * MCU_D makes me think that UART is used for the little MCU embedded into rk3399. rk3399 has two small Cortex-M0 cores for very low power tasks. So again that UART is not what you are looking for. * the RX/TX pins are just shorted to high voltage level/pulled ups on purpose (improbable) edit: I just paid attention to the schematic you posted, but it looks it does not match what you've discovered: the schematic says you should read 5.0v on the VCC pin, instead you read 3.3v. Perhaps that MCU_D connector it's definitely not the one you are looking for.

Armbian default login and password is always root and 1234. If this does not work, the image is not genuine.