mirror of
https://github.com/iamromulan/quectel-rgmii-toolkit.git
synced 2026-04-25 06:35:52 +03:00
[GH-ISSUE #124] RM500U Does not support systemctl #45
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/quectel-rgmii-toolkit#45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RongshuoHe on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/iamromulan/quectel-rgmii-toolkit/issues/124
root@udx710-module:/ # opkg update && opkg install systemctl
Downloading http://bin.entware.net/armv7sf-k3.2/Packages.gz
Updated list of available packages in /opt/var/opkg-lists/entware
Unknown package 'systemctl'.
Collected errors:
root@udx710-module:/ # cat /etc/os-release
ID=unisoc-initgc
NAME="unisoc-initgc-distro"
VERSION="udx710-module+unisoc-initgc-1.0+W24.10.4:14.56.00+user+native (sumo)"
VERSION_ID=udx710-module-unisoc-initgc-1.0-w24.10.4:14.56.00-user-native
PRETTY_NAME="unisoc-initgc-distro udx710-module+unisoc-initgc-1.0+W24.10.4:14.56.00+user+native (sumo)"
DISTRO_CODENAME="sumo"
root@udx710-module:/ # uname -a
Linux udx710-module 4.14.98 #1 SMP PREEMPT Thu Mar 7 07:12:10 UTC 2024 aarch64 GNU/Linux
@dr-dolomite commented on GitHub (Feb 19, 2025):
I dont think that it supports Unisoc release modules?
@iamromulan commented on GitHub (Feb 19, 2025):
RM or RG?
Doesn't appear to be SDXLEMUR, SDXPRAIRIE, or SDXPINN which is what this repo supports.
Confirmed:
(*Assumed not tested)
SDXPRAIRIE:
RM500Q*, RM502
SDXLEMUR:
RM520/521/530*
SDXPINN:
RM550*, RM551
However, your goal seems to be to understand what handles services and/or system init. Could be systemd (
systemctl), could be systemV (like on OpenWRT; init.d [servicecommand] ), could even be BusyBox init. Just depends on how the system was built.The kernel log right after it's booted can be helpful
dmesgAlso understanding the mount points and storage allotment can also be helpful
df -h && mount@RongshuoHe commented on GitHub (Feb 20, 2025):
It should be a model issue, this module is not supported