All Activity

Well that's one thing that confuses me with Linux source code - is having so many different versions of the same file, how to tell which one: location, version type, and especially which repository. Thanks so much for acting right away to get this fix into the Armbian!!

Thank you for having a look and catching my mistake. I have marked the PR as still work-in-progress for now while I look into where to patch this correctly in Armbian itself.

Using included in image armbian-config script as many times for other boards before. I have no idea what was there and I didn't care because Script formats emmc before transfer (with "Warning! All data will be destroyed - proceed?") So there is no chance to leave any trails of anything rested on emmc before

Awesome! Thanks so much!! You're welcome! @laibsch I looked at this, and while I'm not intimately familiar with this project, it looks like leggewie has committed an entirely different (and possibly dangerous) patch, a patch to the way a voltage regular works? ...and to the wrong version of the devicetree file. I do not have an account on GitHub, so I'm reporting this here. From my local copy of the source code (Release 28.5.1) with the Edge kernel cached, the file appears exactly twice: ./build-25.8.1/patch/u-boot/legacy/u-boot-radxa-rk35xx/dt/rk3588-orangepi-5-plus.dts ./build-25.8.1/cache/sources/linux-kernel-worktree/6.16__rockchip64__arm64/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts From examining both files, it looks to me like the first one may be the original version from Rockchip for the vendor kernel. The audio section to be patched doesn't even appear in that one. The second one appears current and is the one targeted by the kernel.org patch. The kernel.org audio patch (the correct one) by Maud Spierings is as follows: Source: https://patchwork.kernel.org/project/linux-rockchip/patch/20250823-orangepi5-v1-1-ae77dd0e06d7@hotmail.com/ ./arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts &analog_sound { pinctrl-names = "default"; pinctrl-0 = <&hp_detect>; simple-audio-card,aux-devs = <&speaker_amp>, <&headphone_amp>; - simple-audio-card,hp-det-gpios = <&gpio1 RK_PD3 GPIO_ACTIVE_LOW>; + simple-audio-card,hp-det-gpios = <&gpio1 RK_PD3 GPIO_ACTIVE_HIGH>; simple-audio-card,widgets = "Microphone", "Onboard Microphone", "Microphone", "Microphone Jack", The new GitHub voltage regulator Commit by leggewie is as follows: Source: https://github.com/armbian/build/pull/8568/commits/a44ae297ec5a24d3217793fa4128177709b06e44 ./patch/u-boot/legacy/u-boot-radxa-rk35xx/dt/rk3588-orangepi-5-plus.dts vcc3v3_pcie_eth: vcc3v3-pcie-eth-regulator { u-boot,dm-pre-reloc; compatible = "regulator-fixed"; gpios = <&gpio3 RK_PB4 GPIO_ACTIVE_LOW>; gpios = <&gpio3 RK_PB4 GPIO_ACTIVE_HIGH>; regulator-name = "vcc3v3_pcie_eth"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>;

How was this transfered? What was on the eMMC before the transfer? Was the eMMC wiped before the transfer? My guess is that your eMMC has Android loaded on it, you didn't wipe it and now you have partitions left over from the Android install.

still on windows , but microsoft suggests 11 so looking for linux 11

I didn't mention, sorry, probably it matters somehow - my bookworm is already transferred to emmc, so system boots and runs from there, not from SD-card

WSL might be easier if you're on windows

" Either of those," i'm one step closer OK, i 'll get Ubunto on vm and will look deeper. Thanks for now

Not joking at all. 1st point Supported Architectures: x86_64, aarch64, riscv64 board is armhf Next 3 points from this readme: System: VM, container, or bare-metal with: ≥ 8GB RAM (less with KERNEL_BTF=no) ~50GB disk space Operating System: Armbian / Ubuntu 24.04 (Noble) for native builds Any Docker-capable Linux for containerized setup Windows: Windows 10/11 with WSL2 running Armbian / Ubuntu 24.04 Are they alternate to each other

Either of those, I personally used Ubuntu running in ESXi VM

Are you joking? Open readme.md in GitHub repo, read it and explore links therein

Thanks for answering. Couple things: "As per documentation, run on a compatible host". Which documentation? can you provide link you define by this word? Define pls compatible host as it is very unclear in comparison to what i was reading ( it was unclear too) , or it is defined in docs you mentioned... banana pi pro is not supported as I understood. Igor Pecovnik was supporting this device for years. Maybe he can deliver more info in this subject. 2 points in reqs: - Armbian / Ubuntu Noble 24.04.x for native building or any Docker capable Linux for containerised - Windows 10/11 with WSL2 subsystem running Armbian / Ubuntu Noble 24.04.x Both required?

Thank you for your report, @DanflashX So, your audio is working out of the box and the change in https://github.com/armbian/build/pull/8568 is not necessary for the Opi 5 Pro?

Anybody here with the Opi 5 Pro? Does it need the same change? https://github.com/armbian/build/pull/8568

I just wanted to interject that I ran into the same (non?)-issue on the 25.8.1 trixie minimal image using a rpi400. armbianmonitor -u

I have only ever seen mmcblk?boot? Partitions on media that was setup for Android as the A/B is part of how Android installs updates and can fall back to the previous version. I've never seen them on an Armbian created media.

Wow, I didn't know those command and mechanism even exist... Thank you for your tip! Any ideas regarding main (mmcblk2boot) topic question, perhaps?

It's worth noting that you don't have to necessarily change anything in the build process. As long as you plan to not insert partitions in the middle, you can: write the image to the card with parted, resize the root partition to whatever you want make a new partition If you want to have more than 4 partitions total, this works best with GPT partition table, but legacy msdos works too with a little more effort `fsck.ext4 -f /dev/foo` where foo is the root partition `resize2fs /dev/foo` after you have the machine booted, you can then mkfs the new partition [you could probably do it in advance of booting the system too] I do this regularly, b/c I typically only partition about 1/2 or 1/4 of the SD card to leave the rest for wear-leveling. Are you trying to do this as a one-off or are you trying to do it for a dozen or more SBCs of the same type?

not everything is mounted, at least not in the way you expect it. check "swapon -s"

As per documentation, run on a compatible host: git clone https://github.com/armbian/build cd build ./compile.sh Follow screen menus. Build system will download necessary toolchain, sources, patches, etc and build an image. Whether or not it will work depends on whether sources/patches for a particular board deviated from the hardware due to time or bugs. If someone is regularly testing then image likely will be ok, if not then image might work or not. If the board has community maintained status, then it is up to its users to test/develop/send patches in GitHub. If necessary, it is possible to play with sources, configs, develop and place extra patches, etc. At times it looks not that straightforward, so there will be a learning curve.

If I have not researched incorrectly, the Rock Pi S0 has microSD, USB, and Ethernet to access external storage, but you have not provided any information about which options are available in your specific case.

I guess they are free to spend that time to develop own samba implementation

I don't think I can condone changing a very, very security-relevant part of your setup without fully understanding its implications. So, it's good you ask here. I can't answer it off the top of my hat, but maybe somebody else can chime in. I don't think I would bother for the sake of 5 seconds. Are you logging in and out all the time? By the way, PAM is short for pluggable authentication module, so you are disabling an authentication mechanism.