lanefu

Okay new discovery.. seem's to be a drive-specific issue.... Experiencing Issue with no init on boot issue on -- Samsung SSD 860 PRO 256GB I have another device working fine on boot.. no issue. -- Samsung SSD 860 EVO 500GB even tried moving both drives around different slots. Behavior was consistent

Another me too Drives don't initialize on boot.. ATA ports show down... if i hot plug a drive, it comes right up. Observed issue on fresh kernel builds of 6.1.62 6.6.1 Tried fresh uboot from edge as well.

Make sure you're building with EXPERT=yes The rk3588 edge kernel is already 6.6 rc1 https://github.com/armbian/build/blob/dd5fb3e3f8659e2a502808a7e10b5aeed8ffb18f/config/boards/orangepi5.conf#L3 https://github.com/armbian/build/blob/main/config/sources/families/rockchip-rk3588.conf#L32

here's an unsupported, unofficial build. Mainline kernel, Mainline Uboot. https://refuge.armsurvivors.icu/lanefu/lanefu_23.08.0-trunk_Nanopi-r5s_bookworm_edge_6.5.3/

nanopi-r5s has been added in a community support configuration. It is available via the EXPERT mode of the builder. It requires EDGE kernel, but mainline support is good https://github.com/armbian/build/blob/main/config/boards/nanopi-r5s.csc I'm using as a router on debian sid via the clammy-ng router framework

When was your PBP made? Is it from one of the newer production runs from past year? Mines from 2nd gen. (Pre covid era) I remember seeing Kali had a few extra patches for the newer PBPs

Yep writing image directly to emmc should be fine. Has been the case historically for me.

I downloaded xfce for PBP from armbian website, flashed to sdcard with etcher and booted successfully. Caveat I don't have emmc chip installed and nothing on SPI. So yeah could easily be manjaro uboot allergies to trying to pivot to armbian to boot. If possible just wipe emmc

The quickest fix for the user will be to use armbian-config to select a mirror. The redirector dev may be able to add some exceptions but geoiop data will never be 100% accurate

Don't confuse current circumstance with an overt decision. What have you done to troubleshoot and participate in diagnosing and solving the problem? Also look-up maintainer https://docs.armbian.com/Release_Board-Maintainers/

The Armbian images shrink the filesystem down to a minimal footprint that then expand to the max of the sdcard on first boot. You're cloning the image after it's been expanded from first boot stage You'll want to shrink the root file system and the partition before imagine. Rather than making a golden image, using the Armbian build tool and the customize image hooks to install your packages would be a more appropriate solution

thank you! merged!

Or I guess Balbes support is free and easy. Note this is balbes and not official support status

for current use `AUFS=no` and it should build.. ran into that yesterday

Hi Judy, There's a lot of work involved in adding a device to Armbian. In your case, a new product without mainline linux support, it's an enormous amount of labor. It's unlikely there will be any community members willing to do the engineering required for free. Are you looking for a paid engagement? Are there kernel source code and device tree source code published and available for this product? https://docs.armbian.com/User-Guide_FAQ/#where-do-i-ship-a-board-so-that-armbian-will-add-support