[SOLVED] Setup and Configuration of Ericsson F3507g WWAN Card

[sog]

Has anyone managed to successfully configured and used an Ericsson F3507g HSPA card?

My Thinkpad X301 came issued with one, and I confirmed the card as working under Windows before installing Ubuntu Hardy (subsequently upgraded to Intrepid).

While Intrepid can see the card [1], it will not connect to the AT&T network. I've updated the settings (username = WAP@CINGULARGPRS.COM and password = cingular1) in NetworkManager with those from scripts that have worked in the past, and these do not work.

lsusb reveals the following:

sog@apone:~$ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 08ff:2810 AuthenTec, Inc. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 17ef:4807 Lenovo 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

According to the Ericsson datasheet [2], there is a Linux driver available for the card, but Lenovo does not make it available and inquiries to Ericsson have returned with a recommendation to talk to Lenovo. Nor can I find a driver in kernel - modinfo ericsson returns nothing.

Is there any way to make this device work? Can, for example, ndiswrapper be employed on WWAN cards like this one, or is it wifi only?

Any and all help, suggestions, tips appreciated.

[1] http://www.flickr.com/photos/sog/2895856979/
[2] http://www.ericsson.com/solutions/mo...heet_print.pdf

[nixscripter]

Looking around, several people are in the same predicament. Google doesn't give any obvious answers.

If you have the windows XP driver (Vista won't work), I would suggest just trying ndiswrapper. It seems a lot of people would like to know if it works.

[guhl]

Hi !

I also got a X301 and this is my standing:

1. I am using a self compiled 2.6.27_rc8 kernel (be careful nor to compile or use the e1000e module for you LAN card as it could damage your cards eeprom, see http://lkml.org/lkml/2008/10/1/368 and the additional information about this)

2. I used the patch that you can find here http://www.spinics.net/lists/linux-usb/msg10344.html that makes the card visible to the option kernel module.

3. the result is that after loading the option module i have 4 new tty's.
(see output from my syslog)

Oct  3 10:50:52 myx301 usbcore: registered new interface driver usbserial
Oct  3 10:50:52 myx301 usbserial: USB Serial support registered for generic
Oct  3 10:50:52 myx301 usbcore: registered new interface driver usbserial_generic
Oct  3 10:50:52 myx301 usbserial: USB Serial Driver core
Oct  3 10:50:52 myx301 usbserial: USB Serial support registered for GSM modem (1-port)
Oct  3 10:50:52 myx301 option 2-4:1.0: GSM modem (1-port) converter detected
Oct  3 10:50:52 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0
Oct  3 10:50:52 myx301 option 2-4:1.5: GSM modem (1-port) converter detected
Oct  3 10:50:52 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1
Oct  3 10:50:52 myx301 option 2-4:1.6: GSM modem (1-port) converter detected
Oct  3 10:50:52 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB2
Oct  3 10:50:52 myx301 option 2-4:1.7: GSM modem (1-port) converter detected
Oct  3 10:50:52 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB3
Oct  3 10:50:52 myx301 option 2-4:1.8: GSM modem (1-port) converter detected
Oct  3 10:50:52 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB4
Oct  3 10:50:52 myx301 usbcore: registered new interface driver option
Oct  3 10:50:52 myx301 option: USB Driver for GSM modems: v0.7.2

Now its time to start playing around with the ttys and find out how to communicate with the modem.

[guhl]

New Standing [SOLVED for the UMTS part]:

The device for communication with the Modem is not one of the ttyUSBx ports but ttyACM0 provided by the cdc_acm module!

Oct  3 10:31:58 myx301 usb 2-4: new high speed USB device using ehci_hcd and address 3
Oct  3 10:31:58 myx301 usb 2-4: configuration #1 chosen from 2 choices
Oct  3 10:31:58 myx301 option 2-4:1.0: GSM modem (1-port) converter detected
Oct  3 10:31:58 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB0
Oct  3 10:31:58 myx301 cdc_acm 2-4:1.1: ttyACM0: USB ACM device
Oct  3 10:31:58 myx301 cdc_acm 2-4:1.3: ttyACM1: USB ACM device
Oct  3 10:31:58 myx301 option 2-4:1.5: GSM modem (1-port) converter detected
Oct  3 10:31:58 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB1
Oct  3 10:31:58 myx301 option 2-4:1.6: GSM modem (1-port) converter detected
Oct  3 10:31:58 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB2
Oct  3 10:31:58 myx301 option 2-4:1.7: GSM modem (1-port) converter detected
Oct  3 10:31:58 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB3
Oct  3 10:31:58 myx301 option 2-4:1.8: GSM modem (1-port) converter detected
Oct  3 10:31:58 myx301 usb 2-4: GSM modem (1-port) converter now attached to ttyUSB4
Oct  3 10:31:58 myx301 cdc_acm 2-4:1.9: ttyACM2: USB ACM device

Then i used cu to connect to the port:

cu -l /dev/ttyACM0

And then i started to communicate with the modem:

AT+CFUN=1
OK
AT+CPIN="4310"
OK

*ESTKSMENU: A1-Dienste,0,6
254,News
253,Freizeit & Fun
252,B-FREE
251,TOOLBOX
250,Service
249,Hotlines


*EMWI: 1,0

+PACSP0

*ESTKDISP: 1,0,0,SIM Card PRO

AT+CGDCONT=1,"IP","A1.net"
OK

ATDT*99***1#
CONNECT

The important thing is that the GSM-Module has to be turned on by the AT+CFUN=1 command because it will not respond to any other commend without this. You can use AT+CFUN=0 to turn it off and save energy.
So put this in the init settings of the software that you use to connect.

Have fun !

And now the next quest: How to use the GSM part of the module ?

[sog]

@guhl: fantastic! thanks for documenting your work. i'm debating whether to roll my own kernel or simply wait for that diff to trickle down into mainline. should i go the former, i'll definitely follow your lead here. outstanding.

[nixscripter]

Great. Please mark the thread as solved (under the thread tools menu).

[sog]

anybody else try that patch and have success? i just tried to apply it to the 2.6.27 source and got the following:

patching file drivers/usb/serial/option.c
patch: **** malformed patch at line 6: *tty, struct usb_serial_port *po

if anyone's got a fix, i'm all ears.

[guhl]

anybody else try that patch and have success? i just tried to apply it to the 2.6.27 source and got the following:

patching file drivers/usb/serial/option.c
patch: **** malformed patch at line 6: *tty, struct usb_serial_port *po

if anyone's got a fix, i'm all ears.

Hi !

I think that you made a mistake when copying the patch source.
You can download my version of the patch from http://www.thinkthinkdo.com/linux/option_F3507g.patch (right click and save to)
Save it somewhere and then do the following:

cd /usr/src/linux-2.6.27 (your kernel source directory)
cat <path_to_patch>/option_F3507g.patch | patch -p1

Then you should be able to build the option module.

Remark:
The option module is not necessary to use the modem.
You can use the modem without the option module via device /dev/ttyACM0 that is created by the cdc_acm module (Kernel option -> Device Drivers -> USB support -> USB Modem (CDC ACM) support)

The option module adds another 5 tty's (/dev/ttyUSB0 - /dev/ttyUSB4) but i did not find out how and what fore they can be used yet.

good luck !

[sog]

Remark:
The option module is not necessary to use the modem.
You can use the modem without the option module via device /dev/ttyACM0 that is created by the cdc_acm module (Kernel option -> Device Drivers -> USB support -> USB Modem (CDC ACM) support)

Fascinating. I did a make menuconfig on /usr/src/linux, and that CDC ACM was actually already present as a module, so I did a:

cu -l /dev/ttyACM0

And sure enough, it connected, and the LED symbol for the modem lit up for the first time.

Unfortunately, the:

AT+CPIN="4310"

Generated an error. Nor did any of the three listings in NetworkManager successfully connect to AT&T's service.

But still, this is progress! Thanks much for answering my earlier question.

[guhl]

Unfortunately, the:

AT+CPIN="4310"

Generated an error. Nor did any of the three listings in NetworkManager successfully connect to AT&T's service.

BE CAREFUL (and i am sorry that i thought this was obvious)!

4310 is the PIN-Code of my SIM-Card !!!
If you entered your SIM-Card and sent the PIN 4310 (which is probably not the PIN of your SIM-Card) more the 3 times then your SIM-Card is very likely locked now!
You will have to put the SIM-Card in a cell phone and unlock the SIM using your PUK-Code. (At least this is how this would work her in Austria).

Of course you also could put the SIM-Card into a phone and use the phone to disable the PIN-request for your SIM than you do not have to send the
AT+CPIN='xxxx' (where xxxx is your PIN ) at all!

And just another remark:
The command AT+CGDCONT=1,"IP","A1.net" is for my carrier (Mobilkom Austria aka as A1) where the "A1.net" is the APN for my carrier. You will have to use the APN for AT&T (whatever that is).
The command ATDT*99***1# is the code to dial in. The number *99***1# could differ for AT&T.

I hope this helps!