Help needed with Huawei E220

Thought I should just report,

My just purchased E220 (MTN) is working very good.. :)

I'm on Fedora Core 6 though.. uname -r:
Linux Hogwarts 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 athlon i386 GNU/Linux
Click to expand...

I'm certain there should be a newer kernel for Ubuntu.. 2.6.15 is older than mine.. which is also not the latest.. latest stable is 2.6.20 I think..

Anyways for me, I had to do nothing special, just follow Tazz_Tux's steps.. in fact I it's a bit easier for me.. after I "rmmod usb_storage" and then "modprobe usbserial ..." I do not need to unplug and replug the dongle.. it just works from there on.. :D
I also do not have any problems when suspending my system.. after wake up it works the same.. :) (Unless I left it connected to the net.. then the suspend does mess it around a bit).

Only other point is there's definetly something up with the speed .. the absolute max I can get is 500Kbps.. I (ugh!) tried it on a Windows system and managed to get 650Kbps ... so I recon it must need some further tweaking..

Btw.. skywatcher do you have SeLinux enabled on your system? For me it's always proved a huge pain in the neck when trying to get connected.. dunno if it's got something to do with it.. but well.. you never know. :)


A question from me: anyone know how to prevent a module from "autoloading" ? :confused:
It would make things simpler if I could just prevent usb_storage from loading in the first place.. I hardly ever use flashdrives anyway so it wouldn't bother me if I have to manually load it once in a while... thanks.
 
Last edited:
redarrow said:
I also do not have any problems when suspending my system.. after wake up it works the same.. :) (Unless I left it connected to the net.. then the suspend does mess it around a bit).
Click to expand...
OK.. correction this is not totally accurate...

On my laptop I have no problems with suspending..
On my desktop I need to plug it out and then back in to get it to work.. - must be a issue on my desktop's BIOS or something..
 
I have now successfully installed the latest stable kernel 2.6.20.3, but my problem hasn't gone away. Please can someone look at the following terminal dump to see if they can spot a likely cause of the problem (note how it repeats after --> Using interface ppp0):

Code: 
chris@chris-laptop:~$ sudo modprobe usbserial vendor=0x12d1 product=0x1003
chris@chris-laptop:~$ sudo ls -la /dev/ttyU*
crw-rw---- 1 root dialout 188, 0 2007-03-14 16:56 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 2007-03-14 16:54 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 2007-03-14 16:54 /dev/ttyUSB2
chris@chris-laptop:~$ wvdial huawei_e620 && sleep 5 && internet 3gonly 384k
--> WvDial: Internet dialer version 1.55
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
CONNECT
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Wed Mar 14 16:57:25 2007
--> Pid of pppd: 9751
--> Using interface ppp0
--> Disconnecting at Wed Mar 14 16:57:30 2007
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 5 seconds
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
CONNECT
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Wed Mar 14 16:57:35 2007
--> Pid of pppd: 9762
--> Using interface ppp0

The wvdial.conf file is identical to that in Tazz_Tux's How To, and also significant is the fact that I have exactly the same problem on two different machines, both running Dapper. The E220 works on Windows.

Sorry for being a nuisance with this.
 
Hmm.. your command line looks incorrect to me:
Code: 
chris@chris-laptop:~$ wvdial huawei_e620 && sleep 5 && internet 3gonly 384k

Whats with the && sleep 5 && ? This is not going to work.. Why do you want a delay here? :confused:

The delay will only occur after the first command has completed.. and even then you're just throwing "internet 3gonly 384k" straight at the command line... These are parameters not individual commands...

Try running it straight as:
Code: 
wvdial huawei_e620 internet 3gonly 384k
 
redarrow said:
Hmm.. your command line looks incorrect to me:
Whats with the && sleep 5 && ? This is not going to work.. Why do you want a delay here? :confused:
Click to expand...

The delay is an unquestioned carry-over from trouble I had with getting the E620 going. I inserted it on the suggestion of Tazz_Tux, because the E620 would not respond to the ATZ command without it. I find that the E220 has the same problem -- it too won't respond with OK to the ATZ command unless the delay is there. But I think you might be onto something, but not at the point where the 5 s delay is inserted. Couldn't it be that one or more delays are required further down the line?

I discovered by chance that if I plug in the modem and go and do something else like make a cup of coffee, when I get back I can run the sudo ls -la /dev/ttyU* commands and immediately get the ttyUSB0,1,2 response. It seems like the (my ?) modem is very slow for some reason.
 
skywatcher said:
The delay is an unquestioned carry-over from trouble I had with getting the E620 going. I inserted it on the suggestion of Tazz_Tux, because the E620 would not respond to the ATZ command without it. I find that the E220 has the same problem -- it too won't respond with OK to the ATZ command unless the delay is there. But I think you might be onto something, but not at the point where the 5 s delay is inserted. Couldn't it be that one or more delays are required further down the line?

I discovered by chance that if I plug in the modem and go and do something else like make a cup of coffee, when I get back I can run the sudo ls -la /dev/ttyU* commands and immediately get the ttyUSB0,1,2 response. It seems like the (my ?) modem is very slow for some reason.
Click to expand...
The thing is, if that command ever could work at all then I'm truly :confused:

Have a look at your output, you will see that the last three parameters to the wvdial command never get executed.. if they did you should see them.. for example:
The "internet" param should show up like:
Code: 
--> Sending: AT+CGDCONT=1,"IP","internet"
AT+CGDCONT=1,"IP","internet"
OK

In your output that you posted this is not happening... nor can it logically. (unless I'm smoking something weird here :eek: )

I guess if you say it worked for your E620 .. well then it must .. or maybe it was some sort of weird coincidence...

Basically you are putting a delay between a command and its parameters... there's no way that additional command line parameters can be passed to a program that's busy running... if you need a delay it should technically be somewhere in the wvdial program itself.. perhaps in the config.. but I don't know if it's syntax supports that..

Well... I stand under correction with what I've said.. but I really don't believe I have made an error... :eek: (maybe I am smoking something.. :eek: )

The whole thing confuses me.. :confused:
 
Hey Guys,

The reason I put those delays in place is because the PIN command renders the modem "useless" for a couple of seconds, if you don't need a PIN, drop the delay. Redarrow might be right, and you do need "another" huawei_e620 - so your command should look like:

wvdial huawei_e620 internet 3gonly 384k

Try it and let us know - also look under /var/log/messages or /var/log/all.log for anything that ppp might dump at you while connecting. If you see nothing, post back and I will show you how to enable debugging :)

Laterz !

redarrow said:
The thing is, if that command ever could work at all then I'm truly :confused:

Have a look at your output, you will see that the last three parameters to the wvdial command never get executed.. if they did you should see them.. for example:
The "internet" param should show up like:
Code: 
--> Sending: AT+CGDCONT=1,"IP","internet"
AT+CGDCONT=1,"IP","internet"
OK

In your output that you posted this is not happening... nor can it logically. (unless I'm smoking something weird here :eek: )

I guess if you say it worked for your E620 .. well then it must .. or maybe it was some sort of weird coincidence...

Basically you are putting a delay between a command and its parameters... there's no way that additional command line parameters can be passed to a program that's busy running... if you need a delay it should technically be somewhere in the wvdial program itself.. perhaps in the config.. but I don't know if it's syntax supports that..

Well... I stand under correction with what I've said.. but I really don't believe I have made an error... :eek: (maybe I am smoking something.. :eek: )

The whole thing confuses me.. :confused:
Click to expand...
 
OK guys, if you're prepared to help me battle this one out, great! :)

What I'm going to do, is post the output from the connection sessions of both modems for comparison. I'll do that tonight.

By the way, maybe I'm confusing the issue with the 'huawei_e620' in the command line instead of 'huawei_e220'. It's just that the code in the wvdial.conf file is exactly the same for the two modems.
 
Hi guys

Here is the latest feedback. First, just a comment about the delay in the command line when using the E620:
Code: 
wvdial huawei_e620 && sleep 5 && internet 3gonly 384k

It does not work when I remove the delay -- I have to use it as shown above (PIN is disabled). Can you explain that?

Now, for the E220. I finally got it to connect by not using the delay, as you suggested. ??

But my problems aren't over. The connection is EXTREMELY slow < 100 B/s. I can see that there is some activity on gkrellm, but when I open the browser or try to read e-mail, nothing happens. If I can fix this problem, I'm home and dry. I tried this

Code: 
sudo setserial -a /dev/ttyUSB0 low_latency spd_warp

but I get this message

Code: 
sudo: setserial: command not found
 
skywatcher said:
Hi guys

Here is the latest feedback. First, just a comment about the delay in the command line when using the E620:
Code: 
wvdial huawei_e620 && sleep 5 && internet 3gonly 384k

It does not work when I remove the delay -- I have to use it as shown above (PIN is disabled). Can you explain that?
Click to expand...
I always thought I knew bash... you're making me doubt myself.. :eek: :(

What happens if you simply run:
Code: 
wvdial huawei_e620
My understanding of bash is that this is infact what you actually are running..
But now I don't know anymore.. :(

skywatcher said:
Now, for the E220. I finally got it to connect by not using the delay, as you suggested. ??

But my problems aren't over. The connection is EXTREMELY slow < 100 B/s. I can see that there is some activity on gkrellm, but when I open the browser or try to read e-mail, nothing happens. If I can fix this problem, I'm home and dry. I tried this

Code: 
sudo setserial -a /dev/ttyUSB0 low_latency spd_warp

but I get this message

Code: 
sudo: setserial: command not found
Click to expand...
Looks like you don't have the setserial binary? :confused:
It should come standard with your distro.. weird.. :confused:
Dunno.. maybe see it it's installed somewhere else.. /sbin/setserial perhaps..
Or ask the Ubuntu guys..
 
elton!! said:
Something I've noticed with my modem is that it doesn't always come up right (despite my having killed my usb-storage module). If it creates only a /dev/tttyUSB0 and not through to ttyUSB2, then it will usually get it right after a reboot or two? Heh.........??
Click to expand...

Hi :)

I had same experience as above with my e220 on Ubuntu Linux.
 
Hi guys

I finally have it going! I followed redarrow's advice and removed the extra parameters when calling wvdial, i.e. I use this:

Code: 
wvdial huawei_e220

I find it doesn't always work first time. Sometimes the system retries once or twice, then it connects. Anyway, I discovered some other tricks. The first time I plug in the modem, the LED flashes green a few times, then it changes to blue. If I now try

Code: 
find /dev/ | grep ttyUSB

I only get ttyUSB0. At this point I remove the modem briefly, then plug it in again. Then I wait for the LED to flash blue again. If I now try

Code: 
find /dev/ | grep ttyUSB

I get ttyUSB0, 1, 2. Then I can run wvdial ...

Note that this 'new' behaviour (no mass-storage device, no modprobe) started after I installed kernel version 2.6.20.3. I still don't understand the inconsistencies, but as long as it works, who cares?

Thanks for all your help, everyone! It is much appreciated.
 
skywatcher said:
Hi guys

I finally have it going! I followed redarrow's advice and removed the extra parameters when calling wvdial, i.e. I use this:

Code: 
wvdial huawei_e220
Click to expand...
Did you ever try that command on your e620?

I'd be curious to know how it works...

Btw.. I do think that the "internet" param should always be there at least... I wonder if it'd make any difference in your case?
 
@skywalker
as i mentioned here, connect the modem before you boot. for me (kernel 2.6.18) this worked.
 
I'm running SUSE 10.1, kernel version 2.6.16.13-4. I bought a 3G Huawei E220 modem for my wife to use on her Windose machine. The idea was to share it, but I can't seem to get it to work. Got hold of your Howto through a google seach. Tried - no luck. Posted a query on a SUSE forum - got refered back to your Howto. Printed it and read through the parts that seemed relevant.

Here's my problem and what happens. I'd really appreciate it if you could browse over it and have a look where I'm missing something. I would be really cool if you could get this thing to work for me.

plug in the E220 Huawei modem into the usb socket

Celeborn:~ # tail -f /var/log/messages
...
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new device found, idVendor=12d1, idProduct=1003
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0
Mar 24 09:00:52 Celeborn kernel: usb 2-1: Product: HUAWEI Mobile
Mar 24 09:00:52 Celeborn kernel: usb 2-1: Manufacturer: HUAWEI Technologies
Mar 24 09:00:52 Celeborn kernel: usb 2-1: configuration #1 chosen from 1 choice
Mar 24 09:00:52 Celeborn kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Mar 24 09:00:52 Celeborn kernel: usb-storage: device found at 2
Mar 24 09:00:52 Celeborn kernel: usb-storage: waiting for device to settle before scanning
Mar 24 09:00:57 Celeborn kernel: Vendor: HUAWEI Model: Mass Storage Rev: 2.31
Mar 24 09:00:57 Celeborn kernel: Type: CD-ROM ANSI SCSI revision: 02
Mar 24 09:00:57 Celeborn kernel: 3:0:0:0: Attached scsi generic sg2 type 5
Mar 24 09:00:57 Celeborn kernel: usb-storage: device scan complete
Mar 24 09:00:57 Celeborn kernel: sr0: scsi-1 drive
Mar 24 09:00:57 Celeborn kernel: sr 3:0:0:0: Attached scsi CD-ROM sr0

unplug modem

Celeborn:~ # rmmod usb-storage
Mar 24 09:11:01 Celeborn kernel: usbcore: deregistering driver usb-storage

Celeborn:~ # modprobe usbserial vendor=0x12d1 product=0x1003

Mar 24 09:02:53 Celeborn kernel: usbcore: registered new driver usbserial
Mar 24 09:02:53 Celeborn kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Mar 24 09:02:53 Celeborn kernel: usbcore: registered new driver usbserial_generic
Mar 24 09:02:53 Celeborn kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core

re-insert into usb socket

Mar 24 09:12:22 Celeborn kernel: usb 2-1: new full speed USB device using uhci_hcd and address 5
Mar 24 09:12:22 Celeborn kernel: usb 2-1: new device found, idVendor=12d1, idProduct=1003
Mar 24 09:12:22 Celeborn kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0
Mar 24 09:12:22 Celeborn kernel: usb 2-1: Product: HUAWEI Mobile
Mar 24 09:12:22 Celeborn kernel: usb 2-1: Manufacturer: HUAWEI Technologies
Mar 24 09:12:22 Celeborn kernel: usb 2-1: configuration #1 chosen from 1 choice
Mar 24 09:12:22 Celeborn kernel: usbserial_generic 2-1:1.0: generic converter detected
Mar 24 09:12:22 Celeborn kernel: usb 2-1: generic converter now attached to ttyUSB0

make sure /dev/ttsUSB0 exists
Celeborn:~ # find /dev/ |grep USB
/dev/ttyUSB0

downloaded your wvdial.conf and saved to /etc
I understand that there may still be an issue regarding the pin when logging onto the internet, but at this stage I just want to make contact with the modem first.

Celeborn:~ # wvdial huewai_e220
--> WvDial: Internet dialer version 1.54.0
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding

using kppp
Celeborn:~ # kppp &
choosing /dev/ttsUSB0
choosing query modem
error message: cannot open modem
on Konsole the following messages:
Opener: received OpenLock
Opener: received OpenDevice
error opening modem device !
Opener: received RemoveLock
Cannot open client
akode: Guessed format: xiph

It seems as if the modem has been recognised, the device /dev/ttsUSB0 has been created but for some reason I can't communicate with the device.
 
der_pinguin said:
I'm running SUSE 10.1, kernel version 2.6.16.13-4. I bought a 3G Huawei E220 modem for my wife to use on her Windose machine. The idea was to share it, but I can't seem to get it to work. Got hold of your Howto through a google seach. Tried - no luck. Posted a query on a SUSE forum - got refered back to your Howto. Printed it and read through the parts that seemed relevant.

Here's my problem and what happens. I'd really appreciate it if you could browse over it and have a look where I'm missing something. I would be really cool if you could get this thing to work for me.

plug in the E220 Huawei modem into the usb socket

Celeborn:~ # tail -f /var/log/messages
...
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new device found, idVendor=12d1, idProduct=1003
Mar 24 09:00:52 Celeborn kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0
Mar 24 09:00:52 Celeborn kernel: usb 2-1: Product: HUAWEI Mobile
Mar 24 09:00:52 Celeborn kernel: usb 2-1: Manufacturer: HUAWEI Technologies
Mar 24 09:00:52 Celeborn kernel: usb 2-1: configuration #1 chosen from 1 choice
Mar 24 09:00:52 Celeborn kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Mar 24 09:00:52 Celeborn kernel: usb-storage: device found at 2
Mar 24 09:00:52 Celeborn kernel: usb-storage: waiting for device to settle before scanning
Mar 24 09:00:57 Celeborn kernel: Vendor: HUAWEI Model: Mass Storage Rev: 2.31
Mar 24 09:00:57 Celeborn kernel: Type: CD-ROM ANSI SCSI revision: 02
Mar 24 09:00:57 Celeborn kernel: 3:0:0:0: Attached scsi generic sg2 type 5
Mar 24 09:00:57 Celeborn kernel: usb-storage: device scan complete
Mar 24 09:00:57 Celeborn kernel: sr0: scsi-1 drive
Mar 24 09:00:57 Celeborn kernel: sr 3:0:0:0: Attached scsi CD-ROM sr0

unplug modem

Celeborn:~ # rmmod usb-storage
Mar 24 09:11:01 Celeborn kernel: usbcore: deregistering driver usb-storage

Celeborn:~ # modprobe usbserial vendor=0x12d1 product=0x1003

Mar 24 09:02:53 Celeborn kernel: usbcore: registered new driver usbserial
Mar 24 09:02:53 Celeborn kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
Mar 24 09:02:53 Celeborn kernel: usbcore: registered new driver usbserial_generic
Mar 24 09:02:53 Celeborn kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core

re-insert into usb socket

Mar 24 09:12:22 Celeborn kernel: usb 2-1: new full speed USB device using uhci_hcd and address 5
Mar 24 09:12:22 Celeborn kernel: usb 2-1: new device found, idVendor=12d1, idProduct=1003
Mar 24 09:12:22 Celeborn kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0
Mar 24 09:12:22 Celeborn kernel: usb 2-1: Product: HUAWEI Mobile
Mar 24 09:12:22 Celeborn kernel: usb 2-1: Manufacturer: HUAWEI Technologies
Mar 24 09:12:22 Celeborn kernel: usb 2-1: configuration #1 chosen from 1 choice
Mar 24 09:12:22 Celeborn kernel: usbserial_generic 2-1:1.0: generic converter detected
Mar 24 09:12:22 Celeborn kernel: usb 2-1: generic converter now attached to ttyUSB0

make sure /dev/ttsUSB0 exists
Celeborn:~ # find /dev/ |grep USB
/dev/ttyUSB0

downloaded your wvdial.conf and saved to /etc
I understand that there may still be an issue regarding the pin when logging onto the internet, but at this stage I just want to make contact with the modem first.

Celeborn:~ # wvdial huewai_e220
--> WvDial: Internet dialer version 1.54.0
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
--> Re-Sending: ATZ
--> Modem not responding

using kppp
Celeborn:~ # kppp &
choosing /dev/ttsUSB0
choosing query modem
error message: cannot open modem
on Konsole the following messages:
Opener: received OpenLock
Opener: received OpenDevice
error opening modem device !
Opener: received RemoveLock
Cannot open client
akode: Guessed format: xiph

It seems as if the modem has been recognised, the device /dev/ttsUSB0 has been created but for some reason I can't communicate with the device.
Click to expand...
You seem to have mixed up the order in which to do the various steps...

After you've plugged it in for the first time, you must first do:
Code: 
rmmod usb-storage
modprobe usbserial vendor=0x12d1 product=0x1003
These commands must be run before you do the unplug and replug routine.. (if you need to do it at all.. I find that I don't need to)

The clue that it's been initialised correctly is when the system output reports three "generic convertors" .. my own sys output:
Code: 
usbserial_generic 3-1:1.0: generic converter detected
usb 3-1: generic converter now attached to ttyUSB0
usbserial_generic 3-1:1.1: generic converter detected
usb 3-1: generic converter now attached to ttyUSB1
usbserial_generic 3-1:1.2: generic converter detected
usb 3-1: generic converter now attached to ttyUSB2

Hope this helps..
 
Hi redarrow

You were wondering about sending only this to the E620:

Code: 
wvdial huawei_e620

Unlike the E220, it doesn't work. It needs all the other garbage in the command string.

But as far as the E220 is concerned, I'm really happy with @wescht's solution to plug in the modem BEFORE booting. :) Maybe @der_pinguin should try that?

Cheers!
 
Last edited:
redarrow said:
You seem to have mixed up the order in which to do the various steps...

After you've plugged it in for the first time, you must first do:
Code: 
rmmod usb-storage
modprobe usbserial vendor=0x12d1 product=0x1003
These commands must be run before you do the unplug and replug routine.. (if you need to do it at all.. I find that I don't need to)

The clue that it's been initialised correctly is when the system output reports three "generic convertors" .. my own sys output:
Code: 
usbserial_generic 3-1:1.0: generic converter detected
usb 3-1: generic converter now attached to ttyUSB0
usbserial_generic 3-1:1.1: generic converter detected
usb 3-1: generic converter now attached to ttyUSB1
usbserial_generic 3-1:1.2: generic converter detected
usb 3-1: generic converter now attached to ttyUSB2

Hope this helps..
Click to expand...
Thanks redarrow! That did the trick - I'm sending this message from my linux box!
I had assumed that everything is ok since /dev/ttyUSB0 was present. Well, we all know about assumptions...
 
skywatcher said:
Hi redarrow

You were wondering about sending only this to the E620:

Code: 
wvdial huawei_e620

Unlike the E220, it doesn't work. It needs all the other garbage in the command string.

But as far as the E220 is concerned, I'm really happy with @wescht's solution to plug in the modem BEFORE booting. :) Maybe @der_pinguin should try that?

Cheers!
Click to expand...
Ta! Thanks for trying it... it's really weird.. I still can't understand how it works.. :confused: .. oh well.. some things just can't be explained I guess.. ;)

der_pinguin said:
Thanks redarrow! That did the trick - I'm sending this message from my linux box!
I had assumed that everything is ok since /dev/ttyUSB0 was present. Well, we all know about assumptions...
Click to expand...
Glad to hear it's working.. :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X