Mobile Internet Key

joenew · 04-13-2015, 08:23 AM

I'm trying to make this 3G mobile internet key work.

Under a Debian Jessie system seems to be automatically switched to modem mode by usb-modeswitch.

The device is seen as a zero-cd (storage mode) as i plug it in.

lsusb says:

Code:

2020:0002

The chip is recognized as Mediatek MT6225.

After half a second usb-modeswith converts it to a modem device and lsusb now says:

Code:

2020:4000

Ok, so it's all right.
But we need a last step:

Ususally theese device recognized as modems are linked to serial devices files under /dev, for example:

Code:

/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2
/dev/ttyUSB3

For this secific dongle seems that linux doesn't know which kernel module load to generate that files.
I've seen for example, many cell phones working with cdc-acm, or with usbserial and now I have an other dongle working out of the box with "option" module.

It's a Huawei-E353:
I plug it in.
wait a few seconds
and I'm ready to use one of the serial device, /dev/ttyUSB0 for example, as a modem.

In that case the module option is automagically loaded and it take under its control the dongle, creating alse the /dev/ttyUSB* files

Now I'm asking myself why Huawei dongle is able to be automatically working with option module whereas the Olicard doesn't let the kernel to load any module at all...

Can anybody explain how that mechanism works exactly?

I can use olicard key manually loading a module to manage it, for example:

Code:

modprobe usbserial vendor=0x2020 product=0x4000

This command generate some /dev/ttyUSB* files to be used in PPP config...
But I can also use the option module to obtain the same files:

Code:

# modprobe option
# echo "2020 4000" > /sys/bus/usb-serial/drivers/new_id

Now I can use internet connection via pppd and successfully use the dongle to be online.

But I'd like to understand why the huawei key managment is automatic whereas the olicard needs some manual commands more.
Is there a databse anywhere? Which contains a list of devices automatically recognize with a particoular module?

Thanks in advance!
An sorry for my bad english.

PS.
I know a bit of udev and its rules. But in this topic I prefer to begin with some infos about "how kernel thinks to manages" theese devices.

Soadyheid · 04-13-2015, 09:20 AM

I'm not sure if I can really help but I managed to get a Vodafone Dongle working using drivers I got from the Betavine project. I was running Ubuntu 10.04 on my netbook and we're talking quite a while ago now.

Anyway... The main thing I can remember is that I had to download a particular Firmware file which provided the low level access to the 3G dongle hardware. (I had to google about for it, see below for identification!)

Running

Code:

dmesg

after plugging the dongle in showed the manufacturer (Huawei)and model (Cant remember) plus the Firmware file it needed to load. It latterly said it was loaded once I'd found it and installed it.
I think it should be put in /lib/firmware somewhere but I'm not sure.

You also need some sort of connection manager which is where Betavine came in. It happens to be particular to Vodafone though, so you may need to see if some kind person has written a Linux connection manager for your 3G provider. If you find one there would hopefully be instructions about installing the Firmware file.

I'm sorry I can't be more helpful, your English is fine by the way.

Play Bonny!

joenew · 05-03-2015, 04:52 PM

Just an update:
you can find more info about my progress with this mobile internet dongle at following link:
http://www.draisberghof.de/usb_modes...php?f=3&t=2273

Finnally I've tried to edit option.c source of option module to let it attach to right usb device interfaces..
It seems to work properly after my editing/rebuilding.
I'm not a developer nor a C progammer, but I'll try to submit a patch to "option" kernel module maintainers.
This is usb-device output after option patch:

Code:

T:  Bus=02 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 10 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=2020 ProdID=4000 Rev=03.00
S:  Manufacturer=Network Connect
S:  Product=MT6225 
C:  #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I:  If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I:  If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option
I:  If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I:  If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I:  If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I:  If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

PS.
Anyway I still can't make it totally working using mbim... It Seems wwan interfaces can't obtain an IP via DHCP after mbim connection succeded.
I've read DHCP could be not supported for this mbim interface, but I still not understand how to get IP address (provided by my ISP) just using some mbim feature.
You can find my progress updates in the right thread of this forum:
http://www.linuxquestions.org/questi...pp-4175537653/