Trying with the same card, NM version 0.7~~svn20081018t105859-0ubuntu1.

Using modified version of fdi, as I saw that the device that works is
always the "first" one (ttyS0, serial.port==0).

Enabled NM_SERIAL_DEBUG, and this is what I get:

Dec 15 12:12:46 fiol-laptop NetworkManager: <info>  Activation (ttyS0) starting 
connection 'Movistar' 
Dec 15 12:12:46 fiol-laptop NetworkManager: <info>  (ttyS0): device state 
change: 3 -> 4 
Dec 15 12:12:46 fiol-laptop NetworkManager: <info>  Activation (ttyS0) Stage 1 
of 5 (Device Prepare) scheduled... 
Dec 15 12:12:46 fiol-laptop NetworkManager: <info>  Activation (ttyS0) Stage 1 
of 5 (Device Prepare) started... 
Dec 15 12:12:46 fiol-laptop NetworkManager: <debug> [1229339566.192868] 
nm_serial_device_open(): (ttyS0) opening device... 
Dec 15 12:12:46 fiol-laptop NetworkManager: <info>  Activation (ttyS0) Stage 1 
of 5 (Device Prepare) complete. 
Dec 15 12:12:46 fiol-laptop NetworkManager: <debug> [1229339566.298240] 
nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' 
Dec 15 12:12:46 fiol-laptop NetworkManager: <debug> [1229339566.328303] 
nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=' 
Dec 15 12:12:46 fiol-laptop NetworkManager: <debug> [1229339566.330317] 
nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0   ERROR  ' 
Dec 15 12:12:46 fiol-laptop NetworkManager: <WARN>  init_done(): Modem 
initialization failed 

Trying with wvdial, I have seen that this device returns an error to
most anything (including ATZ) if the PIN has not been entered yet.

So this wvdial sequence works...
Init1 = AT
Init2 = AT+CPIN=0000           <--- Obviously with the right PIN
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

But this one does not:
Init1 = ATZ                      <<<---- Only change is the Z
Init2 = AT+CPIN=0000
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

How can I trick NM to enter the PIN first? Maybe some HAL-set property?
I am pretty new to this stuff (not to GSM commands, but to NM and HAL)

-- 
UMTS PCMCIA modem not picked up
https://bugs.launchpad.net/bugs/248630
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to