nm 0.7 tries to talk to MC8780 via /dev/ttyUSB0, should be ttyUSB2

[Gerd Bavendiek]

Binary package hint: network-manager

Hi,

running nm-applet 0.7 on Hardy I tried to use my Sierra MC8780. Unfortunately NetworkManager tries to talk to /dev/ttyUSB0. This fails. AFAIK MC8780 can be used via ttyUSB2 only (I checked with minicom, ttyUSB2 works, ttyUSB0 _not_).

Looking at lshal output, I see

modem.command_sets = {'GSM-07.07', 'GSM-07.05'} (string list)

tied to the UDI with ttyUSB0.

I then changed my /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi to read

  <match <email address hidden>:usb.product_id" int_outof="0x6802;0x6804;0x6803;0x6812;0x6813;0x6820;0x6
    <match <email address hidden>:usb.interface.number" int="0">
      <match key="serial.port" int="2">
        <append key="info.capabilities" type="strlist">modem</append>
        <append key="modem.command_sets" type="strlist">GSM-07.07</append>
        <append key="modem.command_sets" type="strlist">GSM-07.05</append>
      </match>
    </match>
  </match>

(serial.port from 0 to 2)

After reboot I finally found:

root@lulu:~# ls /dev/ttyUSB*
/dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 /dev/ttyUSB3 /dev/ttyUSB4 /dev/ttyUSB5

So this obviously was no good idea.

Any hints how to configure this properly ?

BTW, this is exactly the same in Intrepid Ibex.

[Gerd Bavendiek (gerd-bavendiek)]

Please forgive me - I was talking nonsense. There is no point in changing serial.port from 0 to 2.
I finally found that evrything is working fine IF I SIMPLY DEACTIVATE MY PIN.

So after I ran minicom and issued

AT+CLCK="SC",0,"XXXX"

(My PIN instead of XXXX of course).

After that I got a connection. Works in Hardy and in Intrepid now.

[Alexander Sack (asac)]

thanks. deactiviting pin will be a feature at some point (0.7.1) .... most likely when we have a good modemmanager ... but not for now.

[Tim Hume (tim-hume)]

I installed Intrepid last night on a Lenovo Thinkpad X301 with Sierra Wireless MC8780 Mini PCI-E card installed.

All packages were updated.

After a wait Network Manager detects the mobile broadband but when I create a connection for "3" with an apn of 3netaccess and try and connect, it disconnects instantly.

(also, I am asked for the password, which I gather is the same as the connection password ?)

Can anyone else shed any light on this ?

Also, I have seen multiple comments on which port to issue AT commands on.... is it ttyusb0 or ttyusb2 ?

Thanks

Tim