Thank you for your helpful comments. I went ahead and returned the Pinephone to Ameridroid where I bought it, I had to rush because there was only a few more days before the end of 30 day warranty.
I hope they agree with my assessment that there is something defective with the Pinephone that is causing the problem, because they will charge me a lot of money if they conclude there is no hardware cause :-( I will report back in a few weeks when I find out more. Keith Ostertag On Mon, Jun 27, 2022, at 4:34 AM, Dylan Van Assche wrote: > Hey, > > On Mon, 2022-06-27 at 09:50 +0200, Aleksander Morgado wrote: >> Hey Keith, >> >> On Mon, Jun 27, 2022 at 5:05 AM Keith Ostertag <s...@card16.com> >> wrote: >> > >> > I am not a developer, it was suggested to me that people on this >> > list might be able to say with some authority whether my network >> > connection problem is due to a hardware problem or a >> > misconfiguration of modemmanger. >> > >> > Using a Pinephone (original convergence package) running >> > postmarketOS and sxmo. >> > >> > The modem appears to be cycling around, shutting down every 30 >> > seconds or so. >> > >> > Here is a partial log from partial /var/log/modemmanager.err: >> > https://dpaste.com/364H3K945 >> > >> >> It seems the modem disappears abruptly as per the following log: >> >> <<<<<< type = "New MT Message Indicator" (0x10) >> <<<<<< length = 1 >> <<<<<< value = 00 >> <<<<<< translated = [ report = 'no' ] >> [2101]: <debug> [1656296202.119915] [modem0/ttyUSB0/qcdm] unexpected >> port hangup! >> [2101]: <debug> [1656296202.120116] [modem0/ttyUSB0/qcdm] forced to >> close port >> [2101]: <debug> [1656296202.120188] [modem0/ttyUSB0/qcdm] device open >> count is 0 (close) >> [2101]: <debug> [1656296202.120270] [modem0/ttyUSB0/qcdm] closing >> serial port... >> [2101]: <debug> [1656296202.120460] [modem0/ttyUSB0/qcdm] serial port >> closed >> [2101]: <info> [1656296202.123279] [base-manager] port ttyUSB0 >> released by device '/sys/devices/platform/soc/1c1b000.usb/usb2/2-1' >> [2101]: <info> [1656296202.124985] [base-manager] port ttyUSB1 >> released by device '/sys/devices/platform/soc/1c1b000.usb/usb2/2-1' >> [2101]: <debug> [1656296202.125636] [modem0/ttyUSB2/at] unexpected >> port hangup! >> [2101]: <debug> [1656296202.125773] [modem0/ttyUSB2/at] forced to >> close port >> [2101]: <debug> [1656296202.125832] [modem0/ttyUSB2/at] device open >> count is 0 (close) >> [2101]: <debug> [1656296202.125911] [modem0/ttyUSB2/at] closing >> serial port... >> [2101]: <debug> [1656296202.126050] [modem0/ttyUSB2/at] serial port >> closed >> [2101]: <info> [1656296202.128020] [base-manager] port ttyUSB2 >> released by device '/sys/devices/platform/soc/1c1b000.usb/usb2/2-1' >> [2101]: <debug> [1656296202.128882] [modem0/ttyUSB3/at] unexpected >> port hangup! >> [2101]: <debug> [1656296202.129038] [modem0/ttyUSB3/at] forced to >> close port >> [2101]: <debug> [1656296202.129171] [modem0/ttyUSB3/at] device open >> count is 0 (close) >> [2101]: <debug> [1656296202.129252] [modem0/ttyUSB3/at] closing >> serial port... >> [2101]: <debug> [1656296202.129432] [modem0/ttyUSB3/at] serial port >> closed >> [2101]: <info> [1656296202.133747] [base-manager] port ttyUSB3 >> released by device '/sys/devices/platform/soc/1c1b000.usb/usb2/2-1' >> [2101]: Cannot read from istream: connection broken >> [2101]: [/dev/cdc-wdm0] QMI endpoint hangup: removed >> [2101]: <info> [1656296202.135888] [modem0] connection to qmi-proxy >> for /dev/cdc-wdm0 lost, reprobing >> [2101]: <debug> [1656296202.136234] [device >> /sys/devices/platform/soc/1c1b000.usb/usb2/2-1] unexported modem from >> path '/org/freedesktop/ModemManager1/Modem/0' >> >> >> But I'm not sure how that was triggered, because I also see >> ModemManager daemon stopping at that very same time: >> >> [2101]: <info> [1656296202.152536] ModemManager is shut down >> [2101]: <debug> [1656296202.153457] [sleep-monitor] singleton >> disposed >> [2101]: <debug> [1656296202.155021] [auth-provider] singleton >> disposed >> >> >> > and a partial log from /var/log/eg25-manager.err: >> > https://dpaste.com/DE6MZ4QKP >> > >> >> The eg25-manager seems to indicate, it's responsible for shutting >> down >> the modem? >> >> ** Message: 22:16:25.285: Request to quit... >> ** Message: 22:16:25.287: Powering down the modem... >> ** Message: 22:16:26.287: Executed power-on/off sequence >> ** Message: 22:16:26.288: Executed power-off sequence >> ** Message: 22:16:42.289: Modem down, quitting... >> >> > I am only wanting some confirmation that it seems to be a hardware >> > problem before I issue an RMA for the pinephone, because I would >> > not want to do so and later find out that the problem was a simple >> > configuration mistake. >> > >> >> Hopefully some eg25-manager developer can comment on these logs. > > Seems that the eg25-manager gets a request to quit that's weird. > Does the eg25-manager gets some kill signal or something? > > > Dylan -- Keith Ostertag s...@card16.com
