Here is another solution that should work with a stock Asus EEEPC and its present Xandros disto. I have recompiled a couple of drivers and included scripts to make zte mf622 modem work with EEEPC without removing support of SD and usb mass storage. It is not elegant, but works. Improvements welcome.

Download:

http://anthrosciences.net/asus_eeepc/EEEPC_3gSerial.zip

Read the readme.txt file (follows and in distibution). Have included  the source files I modified from the current ASUS kernel source files. All I did is literally add a line to support the modem and recompile.

These changes make it possible to use the ZTE MF622 to the Asus. It is not a refined process. I got it working for me and am happy, and won't work further until it fails or someone else improves it. If you do improve it please let me know (m.d.fischer@kent.ac.uk) and I'll update the archives and give you credit.

I have recompiled two modules, usbserial.ko and airprime.ko. airprime is a much faster interface for 3g modems with larger buffers than usbserial. It also simplifies getting the modem recognised in the first place.

I have added two scripts to /etc/udev/rules.d. One is similar to the published solutions elsewhere, but checks specifically if the usb-mass storage device is the zte mf622 before removing support for usbstorage. Apparently either the storage devices are mounted later, or they remount themselves. But works for me.

The second script ejects the zte mf622 pseudo cd-drive, allowing the zte modem to appear. This process takes time! 30 seconds to a minute before the modem is available after plugging in the modem. Keep this in mind before trying to establish a ppp connection.

You will also need to configure ppp ... I direct you to a page on the web for that. Skip the first section on recognising the modem since what I have done is equivalent.

To install:
1) get a terminal up, cd to the directory where you unpacked the archives,
and type

bash bash_me_to_install.bash

You may be asked to give a password if you have set one since this
uses the sudo command to act as root for a couple of operations.

If you don't trust me, just look at the file and do what is inside yourself.

These changes just make it possible to connect the ZTE MF622 to the Asus.

2)
To connect to the UK Three network follow the second part of directions at

http://hillj.co.uk/2008/01/31/how-to-ge … ux-ubuntu/

beginning with text "Create a file called /etc/ppp/peers/three, and include:"

Do not do the first part, since what I have included here is the equivalent, without the side effect of losing USB mass storage (at least for me!)

Diagnostics:

sudo lsusb

You should see either 19d2 2000 or 19d2 0001 in the report
19d2 2000 is the fake cd, and you can't proceed with ppp until it is
19d2 0001. This can take some time (up to a minute from plugging in the modem)

sudo lsmod should include airprime in the list. It will have a zero following it until you make a ppp connection.

Dear jnm21 and others

Sorry if I've added to your pain. I made a rather gross error in the mdfischer posting in transferring a line to the 25-zte-mf622.rules file.

The lines

GROUP="dialout"
NAME="ttyUSB%n", SYMLINK+="usb/tts/%n", MODE="664" ,  GROUP="dialout"

should have been the single line

BUS=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="0001", KERNEL=="ttyUSB[0-9]*", NAME="ttyUSB%n", SYMLINK+="usb/tts/%n", MODE="0664", GROUP="dialout", RUN+="/sbin/modprobe airprime"

I had the correct line in another rules file that I had meant to delete, so it still worked for me.

Although I hope to find a way to do this without usb_modeswitch, at the moment my method doesn't work properly in some circumstances when other usb storage is already installed (seems to work with sd, but not with usb-sticks).

I will correct the archives. If jnm21 sends me the compiled usb_modeswitch programme (and source distribution) I will include this in the archives, and change the rules code to use this instead of rmmod.

You can get my email address off my website link above. (http://fischer.md)

Mike

Hi all, I just spent all of 10 mins getting this working on ubuntu on the eeepc, dunno if its as easy on Xandros

I used the info on the page to edit a .rules file and wvdial.conf.

I rebooted, ejected the cd icon manually and typed sudo wvdial and it all worked, seems much easier than some suggestions for compiling modules and switching of usb mass storage.

Page: http://ubuntuforums.org/archive/index.php/t-665332.html

JimmyI s post, 4th one down.

Hope this helps someone

P

Hi Pauliephonic
Sounds great
Could you please post the details i.e. which ubuntu, which modem, your wvdial,conf and /etc/udev/rules.d/XXXXXX.rules files. I have been trying to get my 3.co.uk  ZTE MF622 working with ubuntu-7.10 on my eee for a few days now, with no progress. Everything else is working the way I need on the eee. I am gobsmacked to see this amazing little gizmo boot a full blown ubuntu-7.10-desktop (not yes fully optimised) in 43 seconds flat to the login prompt with compiz extras.
Thank for your great efforts

Hi there, I won't post my files here as I used the files suggested in this page:

http://ubuntuforums.org/archive/index.php/t-665332.html

I am using the ZTE MF622 with ubuntu 7.10 on my eeepc, the instructions really are quite straightforward.

I would repeat that the easiest way to put the modem into Modem mode, as opposed to usb drive mode is to 'Eject' it from your desktop menu using the context menu (right-click)

A few seconds after you do this,  the command lsusb shows that the device now has id 19d2:0001

> lsusb
....
Bus 001 Device 004: ID 19d2:0001
....

when the device is in this mode the command

> sudo modprobe usbserial vendor=0x19d2 product=0x0001
(this is the command that should autoexecute by rules in /etc/udev/rules.d, try issuing it manually if the device is not getting picked up after ejecting)

will attach it so that wvdial can do it's magic (wvdials conf file is included in the link above)

Hope this helps

Paulie

One of my friends has bought an eeepc and one of these modems from '3' mobilr in the UK. The methods described about, and in the ubuntu post helped me work through getting it working, but with some minor issues that I worked around, which I will now document here.

The revised automount posted by mdfisher for the 25 rule needs to be modified before running the bash scritp. I could not get this to work correctly, no matter how I edited the udev rule 25. So I created a simple script in /usr/bin to force the insertion of the airprime module and the usbserial module. The other parts of the rules seem to work, and automatically unmount the false cd-rom mount. You will also have to create the three and three.chat files mentioned above, and also described below. So follow mdfishers instructions, modify the 25 udev rule, and then run the bash script, then complete below.

Script to start the modem once it has been inserted. - start-three.sh

#!/bin/bash
sudo modprobe airprime
sudo modprobe usbserial vendor=0x19d2 product=0x0001
sudo pppd call three
sleep 30
sudo cp /etc/resolv.conf-orig /etc/resolv.conf
exit

I found that the DNS was not working correctly, and I backed up the /etc/resolv.conf file and just put it back once I had called the pppd to start. You may not need to this, so check the contents of the file /etc/resolv.conf, and if it is empty, take the sleep command and the cp command out of the above script.So to make a backup copy of your /etc/resolv.conf , like so , sudo cp /etc/resolv.conf /etc/resolv.conf-orig. This simple just moves a known working DNS lookup file.

You will need to create this file as root - ie sudo /usr/bin/start-three.sh and once created you will need to do the following to make sure you can run this file from a terminal, like so 'sudo chmod +x /usr/bin/start-three.sh

I also created a simple script to stop it again once finished, using the methods described above called /usr/bin/stop-three.sh
#!/bin/bash
sudo killall pppd
exit

I also created another simple script to check that the modem had made a good connection, and that an IP address had been assigned, as without this, you won't be able to connect to anything: Again sudo chmod +x /usr/bin/three-diag.sh
/usr/bin/three-diag.sh

#!/bin/bash
/sbin/ifconfig | grep -A 1 ppp0


This would start, and once you could see ppp0 with the three-diag.sh script, you knew you could open firefox and surf.

We tested this several times, and it worked each time.

I hope this helps others trying to get this working.

Cod

For completeness, here are the other config files I created from the ubuntu install post.

/usr/ppp/peers/three
/dev/ttyUSB0
nobsdcomp
novj
nodeflate
ipcp-accept-local
ipcp-no-address
ipcp-no-addresses
ipcp-max-configure 20
user guest
password guest
crtscts
modem
noipdefault
replacedefaultroute
defaultroute
lock
noauth
connect '/usr/sbin/chat -f /etc/ppp/peers/three.chat'
ipcp-restart 8
ipcp-max-configure 50
ipcp-accept-local
ipcp-accept-remote
usepeerdns

/etc/ppp/peers/three.chat

ABORT BUSY
ABORT 'NO CARRIER'
ABORT VOICE
ABORT "NO DIALTONE"
"" ATZ
OK AT+CGDCONT=1,"IP","three.co.uk"
OK ATDT*99***1#
'CONNECT' '\c'
'TIMEOUT' '20'

Here's my version of a fix for a Eee 900, with the ZTE MF622 modem.  I arrived at this after a couple of hours of fiddling based on other posts in this thread.  The solution I have seems simpler than the others listed above, and worked fine for me, but your mileage may vary (as they say).  While I was testing, I was careful to undo one experiment before starting another, so this ought to work on a clean machine - but I make no promises.

1. Download and unpack the EEEPC_3gSerial.zip file from mdfischer (see the second post in this thread).  Only the two kernel module files from this package are needed.

2. Replace the Eee's two 'native' kernel modules with the modules from mdfischer's package, like this:
  a  Assuming you're working from another pc, copy the kernel modules usbserial.ko and airprime.ko to a usb memory stick...
  b  Insert the USB memory stick into the Eee
  c  Open a terminal window by pressing ctrl-alt-t
  d  Type the following to make backups of the original kernel modules...
          cd /lib/modules/2.6.21.4-eeepc/kernel/drivers/usb/serial
          sudo cp airprime.ko airprime.ko.orig
          sudo cp usbserial.ko usbserial.ko.orig
  d  Type the following to copy the new kernel modules over the native ones (assuming your USB memory stick is mounted at  /media/D: ) ...
          sudo  cp  /media/D:/airprime.ko  /lib/modules/2.6.21.4-eeepc/kernel/drivers/usb/serial
          sudo  cp  /media/D:/usbserial.ko  /lib/modules/2.6.21.4-eeepc/kernel/drivers/usb/serial

3. Now, make sure the airprime module gets loaded each time the eee boots (loading the airprime module also causes the usbserial module to load).  Do this by editing the /etc/modules file using the KDE text editor (kate)...
  a  Open the KDE text editor to work on the /etc/modules file...
          sudo kate /etc/modules
  b  Scroll to the bottom of this file, and add the word "airprime" to the list.  The end of the list should then look like...
          button
          asus_acpi
          fuse             
          airprime
  c  Save the file and close the text editor

4.  Restart the Eee.  (If you wish, confirm that the modules are loaded by opening a terminal window, and typing lsusb at the prompt.  You should see airprime and usbserial among the listed items)

5.  Plug in the ZTE modem.  At first, the ZTE modem light will be red, then a CD icon will appear in the task bar and the modem light will turn green.  After a minute or so, the icon will disappear (because the fake CD won't mount properly).  The ZTE modem's light will turn red, then green again.  The modem is now ready to be configured

6.  From the 'Internet' page, open the 'Network' icon to open the 'Network Connections' dialog, and click the 'Create...' button.  Follow the Connection Wizard using these settings (these are for 3 UK - other operators may use different default usernames ans passwords))...
  a  Connection type... select 'Dialup'  (the Eee will then take an age to search through the available hardware for a modem)
  b  Highlight the 'Serial - modem' item in the list of devices.  It should list /dev/tts/USB0 as its 'details'.  Click 'Next'
  c  Set the phone number to *99# then click 'Next'
  d  Set the user name as "guest", and the password to "guest" (ignoring my quotation marks)
  e  Give the connection an appropriate name, and click 'Next' (the Eee will now take an age configuring the connection)
  f  Click 'Finish'

Start the connection (using the 'Connection' button on the 'Network Connections' dialog - mine takes an age to connect).  Have fun.
 
As I've said, this works fine for me, but I make no promises.

===
Edit 19-5-2008:  corrected typo:  modules directory should be /lib/modules/2.6.21.4-eeepc/....

Last edited by lesway (2008-05-19 5:07:58 pm)

@ bounder... I think we're both guilty of typos   Glad it worked for you - I've updated the post to fix my errors.

XP Instalacion problem with ZTE MF622.Can be solved by using USB CABLE FOR NOKIA PHONE symbian.During the instalation skip restart of pc.And it work.For MAC you must find drivers on net.

niknik068

Hi dontpanic. The link you've said "2 - Install the patch found here[this link], and the additional scripts found here." doesn't work anymore. Do you have another link like that?

Thanks.

Sergio Gripp
Brazil

Michael

Followed your instructions on how to get the ZTE modem to work on a 900 - thanks.

It says it's connected but browsing results in a 'server not found' message.

Any ideas?

Tirc

hi

has anybody a new link to EEEPC_3gSerial.zip because the server is down

phil