On Tue, Apr 05, 2016 at 06:35:36PM +0200, Yegor Yefremov wrote: > On Tue, Apr 5, 2016 at 4:09 PM, Bin Liu <b-liu@xxxxxx> wrote: > > Yegor, > > > > On Tue, Apr 05, 2016 at 08:16:27AM +0200, Yegor Yefremov wrote: > >> >> > > >> >> > Could you post output from: > >> >> > > >> >> > mmcli -m 0 > >> >> > >> >> root@debian:~# mmcli -m 0 > >> >> error: couldn't get bus: Could not connect: No such file or directory > >> >> > >> >> root@debian:~# mmcli -L > >> >> error: couldn't get bus: Could not connect: No such file or directory > >> >> > >> >> Seems like I miss something in my rootfs? > >> >> > >> > > >> > Ok, missing 'dbus' package. I am able to see the issue now. Does your > >> > modem still functional after the fifo flush issue? I am not familiar > >> > with modem. > >> > >> Can Modemmanager find your SIM card? mmcli -m 0 | grep SIM > >> > >> SIM | path: '/org/freedesktop/ModemManager1/SIM/0' > >> > >> My Huawei E353 has no problems with finding it, but MA260. So I cannot > >> really try it. AT interface is still functioning, but I can't check, > >> if qmi one is working. > > > > Here is what I found with two modems including MA260. Right after booted > > the board and connected the modem, tx fifo flush problem happens, but > > 'mmcli -m 0' _can_ find the SIM card. > > I think I have physical problem with my SIM card. It is a micro SIM in > a plastic adapter. I think it is a little bit higher, than in the > original adapter, that is now broken. E353 seems to have better > contacts. > > > Now remove the modem then plug it again, fifo flush problem does not > > happen at this time, but 'mmcli -m 0' is unable to find the SIM card > > anymore, with the following error. > > > > error: couldn't find modem at '/org/freedesktop/ModemManager1/Modem/0' > > ModemManager counts modem high, so that after you replug it you'll have it at 1 > > mmcli -m 1 > > You can check the number via > > mmcli -L Thanks for the tip. Yes, mmcli can aleays find the SIM card. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
