-
Upcoming Events
-
-
Volunteering positions
-
Part time technical support
Position: Technical supportNumber of places: 12Applicants: 12
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
21
HDMI audio and analog audio do not work on Opi5Plus
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!! -
21
HDMI audio and analog audio do not work on Opi5Plus
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.1 -
12
What is purpose of /dev/mmcblk2boot devices?
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 -
21
HDMI audio and analog audio do not work on Opi5Plus
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>; -
12
What is purpose of /dev/mmcblk2boot devices?
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.
-
-
Member Statistics