All Activity

@Cancer Why you need to drop ifconfig for ip: https://opensource.com/article/21/1/ifconfig-ip-linux If you’re still using ifconfig, you’re living in the past https://ubuntu.com/blog/if-youre-still-using-ifconfig-youre-living-in-the-past there are certain things in this article that can be done in ip command that takes more than just ifconfig to do the same. Introduction to Linux interfaces for virtual networking https://developers.redhat.com/blog/2018/10/22/introduction-to-linux-interfaces-for-virtual-networking#vlan

accordingly, one can remove Netplan if one don't like it https://www.baeldung.com/linux/etc-network-interfaces-netplan-switch and that actually even with Netplan one can configure a different renderer, e.g. Network-Manager https://docs.armbian.com/User-Guide_Networking/ or for that matter, I think it is feasible to remove Netplan altogether and just use Network Manager, if one prefers that or even for that matter switch back to the raw lowest level /etc/network/interfaces as described in the 1st link In addition show the detailed sequence of events and provide details that: if you cannot show this in detail, then what is your basis of saying that it happens? Note that normally, there is a sequence of events, the interfaces need to be setup first hand, then that the firewall (e.g. iptables) is configured after that. What you need to proof in addition, is that Netplan or NetworkManager *revoke or change* your iptables / firewall setup if they are configured after Netplan / NetworkManager setup the interfaces. i.e. that it is potentially malicious if all that you mention can be rigiously proven then that perhaps we can file that with mitre and have the world cybersecurity issue a major CVE about it. https://attack.mitre.org/ https://www.cve.org/

Additional Info: The "Current" Kernel I found the equivalent code in the Current kernel. It is a clearly a different version of the file, but it looks like the same error is present. I have not tested it. Snippet Source: ./build/cache/sources/linux-kernel-worktree/6.12__rockchip64__arm64/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>; // This line here: Change GPIO_ACTIVE_LOW to GPIO_ACTIVE_HIGH simple-audio-card,widgets = "Microphone", "Onboard Microphone", "Microphone", "Microphone Jack", "Speaker", "Speaker", "Headphone", "Headphones"; The "Vendor" Kernel I found the equivalent code in the Vendor kernel's devicetree. It is also a clearly different version of the file from the other two kernel trees. But it looks like this particular coding error (for the audio) is not present here. The headphone detection level is set to GPIO_ACTIVE_HIGH. Source: ./build/cache/sources/linux-kernel-worktree/6.1__rk35xx__arm64/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts However in my experience (tested again just now with version 28.5.1), the Vendor kernel seems a bit crippled: No GPU or video acceleration, and no ES8388 analog audio whatsoever (not even at the ultra-low volume I was getting with the Edge kernel). At least the screen, keyboard, mouse, and ethernet works, but with no video acceleration the video is slow and clumsy (in gnome). I suspect that the best place to look for the audio issue with the Vendor kernel is not to focus on the audio, so much as to focus on what broke on an apparently deeper level.

Thanks, i will tear it down and see what axp chip mine is using

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! The kernel.org audio patch 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",

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"