Failed to start modem daemons
Describe your issue
What's the expected behaviour?
Modems daemons start when phone boots.
What's the current behaviour?
"We failed to start the modem daemons. We may need a hard reboot." Error message appears in sxmo when system boots and cannot send or receive phone calls or texts
How to reproduce your issue?
What I did was flash latest image of postmarketos edge with sxmo wayland (December 22 I believe) to the Pinephone Braveheart emmc from an sd card running manjaro phosh with a dd command. Tried it twice with same behavior. Modem was running fine in latest sxmo (not wayland) on latest postmarket stable, and still running fine in Manjaro Phosh (to rule out possibility of broken phone)
What device are you using?
Pinephone-Braveheart
On what postmarketOS version did you encounter the issue?
-
edge (
masterbranch) -
v21.06 -
v21.12
On what environment did you encounter the issue?
Phone environments
- Phosh
- Plasma Mobile
- Sxmo (Wayland/Sway)
Other
- No environment
- GNOME
- KDE Plasma
- Kodi
- MATE
- Shelli
- Sway
- Weston
- Xfce4
- fbkeyboard
- i3wm
- Sxmo (Xorg/Dwm)
How did you get postmarketOS image?
- from https://images.postmarketos.org
- I built it using pmbootstrap
- It was preinstalled on my device
What's the build date of the image? (in yyyy-mm-dd format)
20211222-0725-postmarketOS-edge-sxmo-de-sway-1.6.0-pine64-pinephone.img
Additional information
wiki seemed to recommend turning on logging for eg25manager and I pulled the following from the log:
** (eg25manager:3535): ERROR **: 03:26:26.825: Unable to get config for input GPIO 'status'
** Message: 03:26:26.862: Opening config file: /usr/share/eg25-manager/pine64,pinephone-1.1.toml
(I confirmed the file in question exists and contains content, beyond my present understanding to assess the accuracy of that content)
This may be unrelated...The sxmo status bar was also failing to populate and instead reporting an error as well sometimes and it occurs to me now that may be what the error message refers to.
Activity
link to sxmo mailing list thread
By hal9yo on 2021-12-29T01:02:49
added category::device device-pine64-pinephone ui-sxmo labels
removed category::device label
added category::ui label
-
I think this a bug in eg25-manager effecting braveheart devices. I'm guessing it was introduced by https://gitlab.com/mobian1/devices/eg25-manager/-/commit/abf60b793a70f202f8fbefea59d82577ca575078, which changes that from a warning to an error.
If this is the case this issue shouldn't happen with eg25-manager versions before 0.4.2. Unfortunately I'm not a postmarket user, so I don't know what the best way to test that would be.
By ArenM on 2022-01-01T00:00:32
-
I get the same error. If I try running eg25manager manually, I get this:
** Message: 07:21:35.960: Opening config file: /usr/share/eg25-manager/pine64,pinephone-1.1.toml
** (eg25manager:19930): CRITICAL **: 07:21:35.962: Unable to configure /dev/ttyS2
** (eg25manager:19930): ERROR **: 07:21:35.963: Unable to find GPIO chip '1c20800.pinctrl'
edit: sorry, that was running as user. if I run as root I get only the same error as originally posted here.
By sam bowlby on 2022-01-01T13:27:13
Edited by Administrator -
I copied the the
status = { chip = 0, line = 233 }line from pine64,pinephone-1.2.toml to pine64,pinephone-1.1.toml and everything seems to work fine now.By sam bowlby on 2022-01-01T20:52:50
Edited by Ghost User -
That's a bad idea. IIUC that line isn't included in the config for braveheart devices, because it's not connected in hardware. eg25-manager is supposed to do some magic behind the scenes to check the status of the modem if the pin isn't available.
You should open a bug in the eg25-manager repository, and downgrade eg25-manager to 0.4.1 until they fix this.
By ArenM on 2022-01-01T20:52:50