You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the boot up of my Orange Pi 5 Plus with Ubuntu 24.04 LTS I noticed that the pd-mapper.service failed to start. In my unterstanding this service is for Qualcomm cpu's only and can be disabled by default on Rockchip cpu's.
One option is to disable it by hand with the following command: sudo systemctl disable pd-mapper.service
Even though it would be much nicer to not activate it at all by default.
Thoughts: I'm not sure if I understand the project structure here correctly. My assumption is that one possibility would be to add it i.e. in the script /ubuntu-rockchip/config/boards/orangepi-5-plus.sh. Thought about adding the following: chroot "${rootfs}" systemctl disable pd-mapper.service However I'm unsure if this would work. Furthermore this would just solve the issue for an Orange Pi 5 Plus and not all the other boards. Therefore one would have to possibly add it to every script in /ubuntu-rockchip/config/boards/. However because of the lack of my understanding of the project structure I'm unsure if there is a more general way to add it for every board. If "my solution" with adding it to every script in /ubuntu-rockchip/config/boards/ would work in your opinion, I would try to do a pull request for it (last time I did one GitHub was 2014).
Kernel version
6.1.0-1025-rockchip
SBC model
Orange Pi 5 Plus
What operating system are you seeing this problem on?
Ubuntu 24.04 LTS (Noble Nombat)
Relevant logs
sudo systemctl status pd-mapper.service
× pd-mapper.service - Qualcomm PD mapper service
Loaded: loaded (/usr/lib/systemd/system/pd-mapper.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-11-27 12:01:03 CET; 1min 9s ago
Duration: 33ms
Main PID: 840 (code=exited, status=1/FAILURE)
CPU: 30ms
Nov 27 12:01:03 OrangePi systemd[1]: pd-mapper.service: Scheduled restart job, restart counter is at 5.
Nov 27 12:01:03 OrangePi systemd[1]: pd-mapper.service: Start request repeated too quickly.
Nov 27 12:01:03 OrangePi systemd[1]: pd-mapper.service: Failed with result 'exit-code'.
Nov 27 12:01:03 OrangePi systemd[1]: Failed to start pd-mapper.service - Qualcomm PD mapper service.
The text was updated successfully, but these errors were encountered:
I finally managed to get the image build process somehow up and running. I'm building an image for Orange Pi 5 Plus to try out my assumption with adapting the /ubuntu-rockchip/config/boards/orangepi-5-plus.sh script.
There are two ways this could be addressed, either through the ubuntu-rockchip-settings package or when the rootfs is created, which is done in livecd-rootfs.
What happened?
During the boot up of my Orange Pi 5 Plus with Ubuntu 24.04 LTS I noticed that the pd-mapper.service failed to start. In my unterstanding this service is for Qualcomm cpu's only and can be disabled by default on Rockchip cpu's.
One option is to disable it by hand with the following command:
sudo systemctl disable pd-mapper.service
Even though it would be much nicer to not activate it at all by default.
Thoughts: I'm not sure if I understand the project structure here correctly. My assumption is that one possibility would be to add it i.e. in the script /ubuntu-rockchip/config/boards/orangepi-5-plus.sh. Thought about adding the following:
chroot "${rootfs}" systemctl disable pd-mapper.service
However I'm unsure if this would work. Furthermore this would just solve the issue for an Orange Pi 5 Plus and not all the other boards. Therefore one would have to possibly add it to every script in /ubuntu-rockchip/config/boards/. However because of the lack of my understanding of the project structure I'm unsure if there is a more general way to add it for every board. If "my solution" with adding it to every script in /ubuntu-rockchip/config/boards/ would work in your opinion, I would try to do a pull request for it (last time I did one GitHub was 2014).Kernel version
6.1.0-1025-rockchip
SBC model
Orange Pi 5 Plus
What operating system are you seeing this problem on?
Ubuntu 24.04 LTS (Noble Nombat)
Relevant logs
The text was updated successfully, but these errors were encountered: