Modem vanishes randomly #185
Comments
|
Got dmesg? It's possible that the OS inside the modem crashed, which firmware do you use? |
|
Tomas Oqvist reported the same problem on Telegram, the user claimed that most of the modem vanishing caused while the phone is charging. There seems to be no sign of USB EMI when the modem is lost. Once the modem is lost, eg25-manager daemon tries to reboot the modem but failed to do so. A few seconds later, a mysterious USB device appears on the bus which ModemManager doesn't know how to use it. I personally think that there is something wrong with the software running on the modem as I have never seen this strange behavior before and I have no way to reproduce the issue on my end. Modem software version: |
|
Hello, I might update to Biktorgj's latest firmware version and check. |
|
Attached is a dmseg log from a reboot that ended with the modem vanishing after the screen timed out once. I'm running |
|
Had the same problem. Downgrading eg25-manager to 0.3.0+2+g64145ac fixed the issue for me. |
|
I had the same issue on a fresh install of the 6/28 build. Cell modem would disappear every couple of hours. Disabling the wifi/bluetooth via the physical kill-switch helped delay the issue, but did not fix it. I enabled the wifi/bluetooth toggle and then I tried downgrading eg25-manager as suggested by @Michasze. It also helped keep the modem connected longer, but the modem would still disappear after awhile. Running pacman -Syu last night pulled a new kernel (5.12.14-1) and I haven't had any issues since. I am still using eg25-manager version 0.3.0+2+g64145ac from the 6/13 build. |
Looks like ModemManager knows how to handle the reconnecting modem after all... But it will not continue resetting the modem on every failure. At some point, it will not add another modem. No further output (into the journal) happens. And this is when we see the modem never come back from vanishing (and wwan, telephony being completely unavailable). So, the modem is disappearing more often than we think it is, but ModemManager and eg25-manager seem to be recovering a lot. However, when we restart, we see the following output: At that point, the modem comes back and becomes usable again, as indicated by the cellular icon in the (in my case) Phosh statusbar.
|
|
I have had the same problem with the modem disappearing for the past month. I also had phosh login screen control issues. I religiously pacman -Syu daily. As of two days ago the problems stopped occurring. Other than the pacman updates the only thing I changed was my power options in Settings. Previous settings were 10 minutes display, 15 minute suspend on battery. No suspend on power. For two days the phone has been 100% reliable. No modem drops, no login screen issues |
|
I flashed the 01.002.07 modem firmware (which still shows up as 01.002.01.002, go figure). Apparently, that breaks GPS, but my modem has never gone away since. Same as Dave before me: YMMV. |
|
According to biktor, the only single /dev/ttyUSB device showing up after losing cellular is the modem crashed to EDL/Sahara mode.
Sometimes, the modem successfully rebooted back to the OS and work again, then crashed sometime later. There's also reports on Pine64 forum as well: https://forum.pine64.org/showthread.php?tid=13885 |
|
I would like to add that the permanent vanishing seems to occur with modem firmwares 01.002.01.002 and 01.003.01.003, but I've flashed 01.002.07 (which still reports as 01.002.01.002 for some reason), and ever since, the modem still vanishes occasionally ("Lost modem, resetting..."), but always comes back within 10 seconds by itself, and never disappears permanently. Also, the vanishing occurs much less frequently. (I don't suggest flashing that modem firmware though, it seems to be broken in a number of other ways) |
|
@kescherCode could you elaborate on some of the other ways the |
|
@Jab2870 well, AT+QGPS=1 returning +CME ERROR=504, for instance. And its version string is still returning 01.002.01.002. Allegedly, there are more things that are broken in comparison to 01.002.01.002, but I don't really notice as the PinePhone isn't my daily driver. |
|
IMHO the modem software revision is not a significant factor. eg25-manager-dbgsym/unstable 0.3.0-1 arm64 csn@mobian:~$ uname -a Arch started with 20210713 version and is: My vote would be something in the kernel compilation options (I think arch is more-megi and mobian is less-megi?) but I really am pretty damn ignorant so feel free to laugh at that suggestion. (And I have no axe to grind with megi, I use his p-boot for my dual boot!) PS (2 days later) |
|
Is there anything (logs etc) I can provide to help with this. This is the only reason I can't use Arch on my pinephone as my Daily driver. |
|
As mentioned before I have been experiencing the modem dropping problem. Last week it started happening every 30 minutes and the modem/phone would get wery hot. Shortly after the modem was not always detected on boot. Now it is never detected on boot. [cone@pine ~]$ dmesg|grep odem [cone@pine ~]$ journalctl -b -u eg25-manager -- Journal begins at Mon 2021-08-02 11:59:28 MDT, ends at Fri 2021-08-13 12:13:30 MDT. -- I have not opened the phone to check the traces, yet... :( |
|
This happens to me as well recently @1001111github .I've found it happens more often if the phone is hot, so even if you restart it fails. You have to shut down the phone first, wait for the phone to cool down enough, then power on the phone again. |
I am in the same situtation, but I have been using pinephone with Arch as daily device for several months. |
|
Might be anecdotal at best, but I upgraded my Modem FW to the open-source Biktorgj 0.3.0 and it seems to have improved the situation tremendously. I had the modem vanish twice on the first day (last Sunday) and could not get it to work by simply restarting the eg25-manager service (I had to reboot), but it has not vanished on me a single time since. Or if it has, it recovered before I had a chance to notice. Keeping my fingers crossed that its a long term solution, as I am using this phone as my daily driver and really need the reliability. Edit (27 Aug 21): The modem still vanishes 1-2 a day with heavy use, but it is nowhere near as bad as it used to be. Baby steps, I guess... |
|
It seems like the discussion has died down, I haven't heard of anyone's modem resetting for months now. Closing. |
|
Can we reopen? This is definitely not fixed and has happened at least twice today! |
|
@rothn Are you using the official firmware? If so, try switching to Biktorgj's firmware. It's much better and doesn't crash all the time. Yep, the modem's official firmware seems to be at fault with this. |
|
I have been using Biktorgj's firmware without any issues since your comment until today, when the modem disappeared and did not reappear. Rebooting did not fix it. I ultimately had to take the battery out, wait 10 seconds, and put it back in before the modem started working again. Still, 2 months uptime sure beats it dropping (and not coming back) multiple times per day. |
I am running the Phosh build on a 3GB PinePhone 1.2a modded to 1.2b.
Several other maintainers are troubleshooting issues with the modem disappearing (ex: https://invent.kde.org/teams/plasma-mobile/issues/-/issues/3). When the phone sleeps, the modem may or may not work when the phone wakes up, and restarting eg25-manager or resetting the usb port usually fixed it for most, but that's just a bad hack.
I've had this problem intermittently for months, but the last few weeks the phone doesn't even need to deep sleep for the modem to randomly disappear, plugged in or not. Restarting eg25-manager does not "fix" anything, and to get anything through the modem again I have to reboot the phone.
Here is something else I noticed. I just rebooted. Here is the output of
ls /dev/ttyUSB*andlsusb:And about 2 minutes later after the modem vanished:
The modem is a different device number now, in addition to the serial ports missing. If you want anything else let me know what you want and how to get it. If this is better addressed upstream, please point me in the right direction, and I'll go there. Thanks!
The text was updated successfully, but these errors were encountered: