dimaxus
-
Posts
16 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by dimaxus
-
-
The most interesting thing is that everything works fine for joshua-riek Ubuntu 24.04 with the 6.1 kernel
https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html -
good day everyone. The situation with bluetooth was repeated again after the last update. Only now the service file is called not rk3399-bluetooth.service, but bluetooth.service and the content is different there. Please help fix the problem.
-
piter75 thanks a lot, now it works as it should.
Be sure to ask the developer to fix this in the following distributions.
Do you know how to get the standard audio output to work?
Aplay -l command output:
**** List of PLAYBACK Hardware Devices **** card 0: Dummy [Dummy], device 0: Dummy PCM [Dummy PCM] Subdevices: 7/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 7/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 2: realtekrt5651co [realtek,rt5651-codec], device 0: ff880000.i2s-rt5651-aif1 rt5651-aif1-0 [ff880000.i2s-rt5651-aif1 rt5651-aif1-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 3: rockchiphdmi [rockchip,hdmi], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 4: ROCKCHIPSPDIF [ROCKCHIP,SPDIF], device 0: ff870000.spdif-dit-hifi dit-hifi-0 [ff870000.spdif-dit-hifi dit-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 -
16 hours ago, piter75 said:
You can fix your current installation by running:
sudo sed -i s/Type=exec/Type=simple/g /lib/systemd/system/rk3399-bluetooth.servicefollowed by a reboot.
Bluetooth in legacy Bionic images will be fixed when they are built next time.
I did, but the Bluetooth Adapters application still does not start, of course there is no way to add Bluetooth devices, what else can you try?
Boot log output:3.019909] of_get_named_gpiod_flags: parsed 'uart_rts_gpios' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.019927] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 83.
[ 3.019952] of_get_named_gpiod_flags: can't parse 'BT,power_gpio' property of node '/wireless-bluetooth[0]'
[ 3.020002] of_get_named_gpiod_flags: parsed 'BT,reset_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.020018] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 9.
[ 3.020067] of_get_named_gpiod_flags: parsed 'BT,wake_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.020082] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 90.
[ 3.020131] of_get_named_gpiod_flags: parsed 'BT,wake_host_irq' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.020146] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 4.
[ 3.020702] [BT_RFKILL]: Request irq for bt wakeup host
[ 3.020800] [BT_RFKILL]: ** disable irq
[ 3.021030] [BT_RFKILL]: bt shut off power
[ 3.043187] [BT_RFKILL]: bt_default device registered.[ 7.296310] systemd[1]: /lib/systemd/system/rk3399-bluetooth.service:11: Support for option SysVStartPriority= has been removed and it is ignored
-
and here are some more lines:
[ 3.025330] of_get_named_gpiod_flags: parsed 'uart_rts_gpios' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.025346] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 83.
[ 3.025377] of_get_named_gpiod_flags: can't parse 'BT,power_gpio' property of node '/wireless-bluetooth[0]'
[ 3.025427] of_get_named_gpiod_flags: parsed 'BT,reset_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.025441] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 9.
[ 3.025488] of_get_named_gpiod_flags: parsed 'BT,wake_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.025502] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 90.
[ 3.025548] of_get_named_gpiod_flags: parsed 'BT,wake_host_irq' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.025562] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 4.
[ 3.026068] [BT_RFKILL]: Request irq for bt wakeup host
[ 3.026159] [BT_RFKILL]: ** disable irq
can anyone know how to defeat this? -
6.388066] systemd[1]: /lib/systemd/system/rk3399-bluetooth.service:6: Failed to parse service type, ignoring: exec
[ 6.388184] systemd[1]: /lib/systemd/system/rk3399-bluetooth.service:11: Support for option SysVStartPriority= has been removed and it is ignoredlines from boot log, command armbianmonitor -u dumps log to remote server http://ix.io/2N9v - is this ok?
-
Good day to all. In the latest builds of the system, bluetooth does not work, maybe someone knows how this is treated, help ...
-
One more question . What version of Debian is the Armbian Buster based on?
-
Thanks to everyone. I figured it out myself.
-
Armbian is already installed in eMMC, so I'm trying to figure out which button on the keyboard stops U-Boot and at what point, because I can’t do it at all.
-
stop booting from UART console
Is it to press some key on the keyboard or close TP50265 and GND?
-
So how to boot from a flash drive after installing Armbian in eMMC. If possible in detail, step by step. Sorry inexperienced user.
-
"once you have Armbian booting from eMMC, you can boot SD card in more simple manner: stop booting from UART console and execute those commands: setenv devnum 1 followed by run mmc_boot"
Good day to all.
A question also to experts. And you can explain everything in more detail, in steps, for beginners. How to stop which keys to press, something I can’t do in any way. -
Thanks for the quick response
-
Good day to all.
Question to experts. How to change the resolution of the HDMI output in Armbian. Which file to make changes to: boot.cmd or armbianEnv.txt?
If you can a couple of specific examples.

HDMI audio and analog audio do not work on Opi5Plus
in Orange Pi 5 Plus
Posted
If you can solve the problem, please share it with the community.