Open arinc9 opened 2 months ago
How one of three possible working configurations is qualified as improper? In general you do not need modemmanager, native luci extensions suffice.
How one of three possible working configurations is qualified as improper?
Sorry, what does that mean? Where do you see that "one of three possible working configurations" do I claim is improper? I have clearly stated that the modem is not detected properly at boot.
In general you do not need modemmanager, native luci extensions suffice.
I disagree with your suggestion. I'd much rather prefer to have this issue fixed instead of using something else to evade the issue.
If this only happens at boot, it is usually because the modem is not yet ready to respond on the cdc_wdm interface. I suspect that it is not responding to the cdc_wdm interface during the probe phase of the ModemManager. The ModemManager then assumes that cdc_wdm (qmi/mbim) is not supported. As a workaround you could delay the start of ModemManager. But the cleanest solution would be that the ModemManager extends the probe phase and thus gives the modem more time to respond correctly during probing.
Will the modem be detected if you restart the ModemManager? This is definitely a timing thing.
I'm going to close this because I don't think we can do anything about it. If you disagree, feel free to reopen the ticket.
Will the modem be detected if you restart the ModemManager?
After running service modemmanager restart
and waiting for a minute to get past the error: couldn't find the ModemManager process in the bus
response, I see the same output I've mentioned in the issue report.
I'm going to close this because I don't think we can do anything about it. If you disagree, feel free to reopen the ticket.
As I've mentioned:
This issue is not there on Buildroot which utilises ModemManager 1.22.0 unmodified.
I think the problem stems from the modifications made to ModemManager for OpenWrt. Therefore, I believe that this issue report should remain open until the issue it reports is fixed. I see no option in this page to re-open the issue. I'm going to wait 48 hours for you to re-open it or provide me the means to do so on my own. Otherwise, I will open another issue with the same report.
Then you need to give us some more information.
Will the modem be detected if you restart the ModemManager?
After running
service modemmanager restart
and waiting for a minute to get past theerror: couldn't find the ModemManager process in the bus
response, I see the same output I've mentioned in the issue report.
Is the dbus service running?
Could use please execute the following command /etc/init.d/modemmanager restart
and past the log message from syslog?
Looks like hotplug script may need to be extended to notify MM about the addition of the cdc_mbim as well as mbim network device. And maybe PCIe MHI devices...
Maintainer: @feckert, @aleksander0m Environment: aarch64, Banana Pi BPI-R4, OpenWrt SNAPSHOT
Description:
This issue only happens for the modem on the M.2 socket. Modems on the mPCIe sockets are detected properly. This issue is not there on Buildroot which utilises ModemManager 1.22.0 unmodified.
At boot, the modem won't be detected properly. The cdc_mbim driver is missing from the drivers section.
Same modem on Buildroot is detected properly.
The modem is detected properly on OpenWrt after manually resetting the modem.
All modems seem to be brought up by the kernel properly on OpenWrt.