Hello Dan,
I have tried running ModemManager with /dev/ttymxc2 port set to 57600 baud
rate. It looks like as I can see from ModemManager debug logging the QUECTEL
UC20 device is not recognized. I have looked into the ModemManager supported
devices website
Am Dienstag, 21. März 2017, 20:32:29 schrieb Aleksander Morgado:
> You can convince MM to use the WWAN with a udev rule like this:
>
> # Airtel branded E3372h-607, using huawei-cdc-ncm driver but with
> unresponsive cdc-wdm port
> ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
>
On Sat, 2017-03-11 at 13:00 +0100, Aleksander Morgado wrote:
> There are 2 main types of udev properties: device-specific and
> port-specific.
>
> The port-specific properties are set independently per port (e.g.
> port
> type hints set per interface number for a given vid:pid).
>
> The
On Sat, 2017-03-11 at 13:15 +0100, Aleksander Morgado wrote:
> A new 'ID_MM_TTY_BAUDRATE' per-port udev tag is introduced, which
> allows specifying the baudrate that will be used when opening a
> specific serial port.
>
> E.g.:
>
> ACTION!="add|change|move", GOTO="mm_my_modem_end"
>
Hey Jan,
On Tue, Mar 21, 2017 at 9:39 PM, Jan Graczyk wrote:
> How to set ModemManager baudrate?
See
https://lists.freedesktop.org/archives/modemmanager-devel/2017-March/004075.html
If you import that patch, you would be able to configure the default
baudrate that would be
Hello Aleksander,
How to set ModemManager baudrate?
Best Regards,
Jan Graczyk
This email message may contain confidential and privileged information. Any
unauthorized use is prohibited. If you are not the intended recipient, please
contact the sender by reply email and destroy all copies of
On Tue, Mar 21, 2017 at 9:18 PM, Jan Graczyk wrote:
> The baudrate of /dev/ttymxc2 is 115200.
That won't work, unless you instruct ModemManager to use that specific
baudrate on the TTY. Last week I sent a patch for review to allow that
with per-port udev rules, see:
Hello Aleksander,
The baudrate of /dev/ttymxc2 is 115200.
Best Regards,
Jan Graczyk
This email message may contain confidential and privileged information. Any
unauthorized use is prohibited. If you are not the intended recipient, please
contact the sender by reply email and destroy all
Hello Dan,
Yes, I am able to talk to this modem through command:
kermit -l /dev/ttymxc2 -b 115200
set flow none
set carrier-watch off
connect
AT
OK
at+cops=?
+COPS:
(1,"T-Mobile","T-Mobile","310260",2),(1,"AT","AT","310410",2),(1,"T-Mobile","T-Mobile","310260",0),,(0-4),(0-2)
OK
Best Regards,
On Tue, Mar 21, 2017 at 8:56 PM, Jan Graczyk wrote:
> ModemManager[1623]: [1490123698.126826] [mm-port-serial-at.c:440]
> debug_log(): (ttymxc2): --> 'AT'
> ModemManager[1623]: [1490123699.675043] [mm-plugin-manager.c:710]
> min_probing_timeout_cb(): (Plugin Manager)
>
Hello Dan,
Here is the ModemManager debug logging with my recent udev rule added:
root@linaro-alip:~# ModemManager --debug
ModemManager[1623]: [1490123697.480062] [main.c:140] main():
ModemManager (version 1.4.0) starting in system bus...
ModemManager[1623]: [1490123697.502634] [main.c:65]
Hi,
I reflashed a Telekom Speedstick V (E3372h) with the firmware from megafon.
Under Windows 10 this has the effect, that the stick is running dualstack.
This is also possible under linux, but only manually:
echo -ne '\r\nAT^NDISDUP=1,1,"internet.telekom"\r\n' > /dev/ttyUSB0
With
Hello Dan,
When I have applied that rule you have provided for me the target serial
console is printing garbage characters and I do not have access to target
serial console any more. I had to remove that rule to get the target serial
console back.
Best Regards,
Jan Graczyk
This email message
On Tue, 2017-03-21 at 16:59 +, Jan Graczyk wrote:
> Hello Aleksander,
>
> The Queltec UC20 modem is sitting on my development board PCIe bus.
> When I issue the command udevadm info /dev/ttymxc2 I am getting
> response:
We care more about the parents though, so could you:
udevadm info
Hello Aleksander,
The Queltec UC20 modem is sitting on my development board PCIe bus. When I
issue the command udevadm info /dev/ttymxc2 I am getting response:
root@linaro-alip:~# udevadm info /dev/ttymxc2
P: /devices/soc0/soc/210.aips-bus/21ec000.serial/tty/ttymxc2
N: ttymxc2
E:
Hello Aleksander,
Thank you for your response. I have actually stopped running Modem Manger and
then I have issued the command ModemManager --debug. This time the service name
was acquired. However I have got another problem. The mm-base-manager.c:314
reports error device added():
On Tue, Mar 21, 2017 at 5:04 PM, José wrote:
> ModemManager reports look like this:
>
> Status | lock: 'none'
> | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
> | state: 'connected'
> | power state: 'on'
> | access tech: 'hsdpa'
> | signal quality:
ModemManager reports look like this:
Status | lock: 'none'
| unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)'
| state: 'connected'
| power state: 'on'
| access tech: 'hsdpa'
| signal quality: '38' (recent)
I have some questinos about the signal quality quantity:
* Which
Thomas Lang writes:
> Coldstart:
>
> [ 481.884820] ehci-pci: EHCI PCI platform driver
> [ 481.885253] ehci-pci :00:13.0: EHCI Host Controller
> [ 481.885308] ehci-pci :00:13.0: new USB bus registered, assigned bus
> number 1
> [ 481.885326] ehci-pci
On Tue, Mar 21, 2017 at 12:55 AM, Jan Graczyk wrote:
>
> I have installed Quectel UC20 modem on my development board PCIe bus. The
> Linux modem device for Quectel UC20 modem is showing up as /dev/ttymxc2. When
> I try to run mmcli -L or ModemManager –debug the message “Could
Hey Colin,
On Mon, Mar 20, 2017 at 9:17 AM, Colin Helliwell
wrote:
>
>> On 17 March 2017 at 19:56 Aleksander Morgado
>> wrote:
>>
>> On Fri, Mar 17, 2017 at 6:40 PM, Dan Williams wrote:
>>
>> > I ended up with
Hi Dan,
Hmm..
Coldstart:
[ 10.071183] usbcore: registered new interface driver usbserial
[ 10.071266] usbcore: registered new interface driver usbserial_generic
[ 10.071315] usbserial: USB Serial support registered for generic
[ 10.102189] usbcore: registered new interface driver qcserial
On Mon, Mar 20, 2017 at 4:46 PM, Engel, Mike wrote:
> I have used the MM 1.7.0 that includes the UBlox plugin and the error that I
> saw with the previous version persist. It seems that the SIM is not detected.
>
> When I change the USB profile from (3 ("NETWORK, 1
23 matches
Mail list logo