USB Broadband ZTE HSUPA Dongle MF637 doesn't connect

Bug #369311 reported by Fazl
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Please bear with me as I am a n00b at Xubuntu (Xubuntu 8.10 Intrepid as far as I can tell) running an XFCE desktop.

I have a ZTE MF637 Broadband dongle which I cannot connect to the internet with. I see that there have been problems with the older MF622, MF626, MF628 and MF632 but I don't see anything about the MF637. I've been trying to get mine working using the same solutions but have come to a dead end where i don't see what the modification for (gedit /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi) file which was reported in bug #305968. On top of that, I tried to do the modification for what IS in the file and I don't seem to have permissions to do it and I don't know how to give myself those permissions. What I am hoping is that these bugs are already resolved, but if they are, I don't understand how they still exist since I only downloaded and installed my Xubuntu 8.10 Intrepid about 18 days ago.

A little background on my problem: I bought the USB dongle to connect to the internet faster than what I have now. Currently I am connecting through a Motorola C380 and using it as a modem via USB. It is only getting about 10kps at max so I bought this dongle hoping it would work just as easily but unfortunately not the case. I went online to try to see if there were any packages i could install via Synaptic Package Manager that might help. I've installed a few which managed to make the Dongle's light go blue (3G operational) instead of the steady red (communication error). With this, i thought I was making some progress but no luck after that. I've downloaded a few other packages but none seem to help. They were "3G managing" packages for 3G dongles.

Originally I thought the issue was that my computer was not even recognizing the dongle because when i went to Terminal and punched in LSUSB, or DMESG, i never got any change. The other thing is that I am using a PCMCIA to USB adapter card for my USB devices. These devices all work fine but when I plug in the dongle, the PCMCIA card freezes up and I lose communication from it. I have to remove the dongle and reset my PCMCIA card and then the devices work again.

I think thats all the information I can tell. I don't know of anything else to do.

-----------------------------

Here is a bit of an update as I have been trying to get this to work. It turns out that part of the problem is the dongle's interface with my Nexxtec PCMCIA card. When the dongle is plugged into it, it freezes the card up so it does not show up on the LSUSB commanded device list.

I plugged the dongle into my replicator USB port (I am using an IBM T43 with a replicator dock) and I got a device id --- Bus 002 Device 006: ID 19d2:2000. Now checking this against my 10-modem.fdi file, this vendor ID is correct as it comes up with ZTE or ONDA, but the device ID is wrong as it should be 0002. I tried a couple of different things including modifying the 10-modem.fdi file but to no avail. The computer does not recognize the device as anything other than the "Bus 002 Device 006: ID 19d2:2000" identification.

Next, I did some research with a lot of help from another fellow Linux user and came across USB_modeswitch. I already had the file installed but had to change the conf file. This is the part I changed (or de-commented):

########################################################
# ZTE MF628
#
# Captured with "usbmon". Has a micro SD slot which can be
# activated alternatively
#
# Contributor: Alvaro Lopes <alvieboy at alvie dot com>

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

# To modem mode:

TargetVendor= 0x19d2
TargetProduct= 0x0015

MessageEndpoint=0x08
MessageContent="5553424312345678000000000000061b000000030000000000000000000000"

# To SD slot mode:

;TargetVendor= 0x05c6
;TargetProduct= 0x2001

;MessageEndpoint=0x08
;MessageContent="55534243123456782000000080000a86010101180101010101000000000000"

;ResponseEndpoint=7

########################################################

With that done, I believe that I should have been able to enact the usb_modeswitch to engage the Broadband part of the dongle and disengage the ZeroCD (false pendrive) portion. Unfortunately that did not work either so the next step was to Blacklist the usb-storage by (sudo gedit /etc/modprobe.d/blacklist). I did that hoping that it would bring the USB storage back to the default but that didn't work either. After trying that and retrying the usb_modeswitch, i keep getting the notorious (-2) error which states that the device cannot unlock or communicate. This is the error.

sudo usb_modeswitch

 * usb_modeswitch: tool for controlling "flip flop" mode USB devices
 * Version 0.9.6 (C) Josua Dietze 2009
 * Works with libusb 0.1.12 and probably other versions

Looking for target devices
 No target device found
Looking for default devices
 Found default devices (1)
Prepare switching, accessing latest device
Looking for active default driver to detach it
 No driver found. Device probably not initialized. Trying to continue ...
Setting up communication with device
Trying to send the message
 Sending the message returned error -2, trying to continue ...
-> See /proc/bus/usb/devices (or call lsusb) for changes. Bye

Can anyone help me here? I know there is a way to get this working, I just need to find it.

-----------------------------------------------------

Second update here....

Here is a bit more of an update on my problem. I continued on troubleshooting and came across this set of commands in one of the forums and tried it out. This is what I did.

sudo gedit /etc/udev/rules.d/ZTEMF622.rules

With that, I created a rules file for the ZTEMF637 even though the name was 622, I didn't see it to matter much since the product and vendor Ids are identical. Next, I filed in the file with...

ACTION!="add", GOTO="ZTE_End"

# Is this the ZeroCD device?
SUBSYSTEM=="usb", SYSFS{idProduct}=="2000",
SYSFS{idVendor}=="19d2", GOTO="ZTE_ZeroCD"

# Is this the actual modem?
SUBSYSTEM=="usb", SYSFS{idProduct}=="0001",
SYSFS{idVendor}=="19d2", GOTO="ZTE_Modem"

LABEL="ZTE_ZeroCD"
# This is the ZeroCD part of the card, remove
# the usb_storage kernel module so
# it does not get treated like a storage device
RUN+="/usr/src/usb_modeswitch-0.9.2/usb_modeswitch -d 1 -v 0x19d2 -p 0x2000 -V 0x19d2 -P 0x0001"

LABEL="ZTE_Modem"
# This is the Modem part of the card, let's
# load usbserial with the correct vendor
# and product ID's so we get our usb serial devices
RUN+="/sbin/modprobe usbserial vendor=0x19d2 product=0x0001",
# Make users belonging to the dialout group
# able to use the usb serial devices.
MODE="660", GROUP="dialout"

LABEL="ZTE_End"

And then I saved this file in the location I made it in ( etc/udev/rules.d/ZTEMF622.rules )

Next, I did this

sudo gedit /etc/wvdial.conf

[Dialer Defaults]

Init2 = ATZ

Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

Stupid Mode = 1

Modem Type = Analog Modem

ISDN = 0

Phone = *99#

Modem = /dev/ttyUSB0

Username = user

Dial Command = ATDT

Password = pass

Baud = 460800

I saved the file and closed it. Then I shut my computer down and rebooted and tried the sudo wvdial command and I got

--> WvDial: Internet dialer version 1.60
--> Cannot open /dev/ttyUSB0: No such file or directory
--> Cannot open /dev/ttyUSB0: No such file or directory
--> Cannot open /dev/ttyUSB0: No such file or directory

Now this is where I stand now although I HAVE noticed some interesting changes. I no longer have the same issue with my PCMCIA card interfacing with the dongle. If I reboot the system with the dongle in the PCMCIA card, the card functions fine AND the dongle shows up on the LSUSB commanded device list. The only problem is if I pull the dongle out, everything freezes up and my entire system becomes unstable which is odd.

Also, I noticed in DMESG that the usb-storage is now ignored for this device just as I wanted, but the same problem seems to be occurring. The device's ZeroCD sector is being shut down, but the dongle is still unable to unmount so it can be modeswitched as demanded in the Rules file. This has me a bit confused as to how to overcome this issue. I think it could be that OR that it DID modeswitch but it just can't find this /dev/ttyUSB0 file which gives it the direction to activate the broadband dongle for communication.

If anyone has any suggestions, please feel free to tell me.

It still never shows up in Network Manager if anyone is curious about that part.

---------------------------------------------------------------

Ok so whats the update for today. I guess that I have to create the ttyUSB0 file so I did that with the :

sudo mknod /dev/ttyUSB0 c 188 0

Command. Not sure if that is right, but it made the ttyUSB0. Now, instead of getting the “directory or file not found error”, I now get...

fazl@fazl-laptop:~$ sudo wvdial

--> WvDial: Internet dialer version 1.60

--> Cannot open /dev/ttyUSB0: No such device

--> Cannot open /dev/ttyUSB0: No such device

--> Cannot open /dev/ttyUSB0: No such device

Wonderful. I've exchanged one ignorance of my device for another. Nonetheless, this made me wonder a few things. One, I was wondering if all the commands were linking together properly like the rules knowing the right location of the modprobe and the mode-switch so I checked those out. Turns out that the modprobe was not in the location that the Rules file was looking in so I changed that to match. Next, I am not sure if this is right, but all the information I am looking at says that product ID for the dongle in broadband mode should be 0x0001. I checked my 10-modem.fdi file and noticed that the 0x0001 was in there and so was the 0x2000 so I took out the 2000. Its the ZeroCD anyway and shouldn't need to be there. Then I checked the modeswitch.conf file and it looked like I was changing the device ID to 0x0015 instead of 0x0001 so I changed that also.

I'm just trying to get things lined up but after a hard days work, my brain isn't firing on all cylinders. I hit the command

Wvdialconf

just to see what happens and I got this:

       fazl@fazl-laptop:~$ wvdialconf

       Editing `/etc/wvdial.conf'.

       Scanning your serial ports for a modem.

        WvModem<*1>: Cannot set information for serial port.

        ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud

        ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud

        ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

        Modem Port Scan<*1>: S1 S2 S3

        ttyACM0<Info>: Device or resource busy

        Modem Port Scan<*1>: ACM0 USB0

         Sorry, no modem was detected! Is it in use by another program?

         Did you configure it properly with setserial?

         Please read the FAQ at http://open.nit.ca/wiki/?WvDial

         If you still have problems, send mail to <email address hidden>.

So I guess tomorrow is another day. I will have to continue my troubleshooting. Hopefully I will have a clearer head to make some more headway but I don't think I made much today. BTW, the ACM0 device source is my mobile phone.

--------------------------------------------------------------------

Finally... SUCCESS!!!! I followed these instructions and wiped out all the other instructions. This set worked perfectly for my ZTE MF637 dongle. This is not MY information. I copied it from another guy on one of the forums. His posting name was "jfernyhough" so he gets the credit. Thanks man, your method worked better than a charm! Here it is for people who haven't come across it...

jfernyhough 's method

 Howto: Connect ZTE MF627 3G modem with NM0.7
I recently bought a 3G mobile broadband modem and then realised I'd bought the wrong model - instead of getting a Huawei E160 or E169 that reportedly work OOTB with Intrepid I got a ZTE MF627 for which no information exists. On the plus side, it has a built-in MicroSD reader...

I initially raised a bug here but in the meantime have got it working. So here is a how-to.

1) Download and install usb_modeswitch
Go here and download the deb file. A direct link is here. Then install it.

This provides a way of switching the USB modem from its initial useless mode to its correct, functional modes. It will need configuring to apply to the modem.

2) Edit /etc/usb_modeswitch.conf to apply to the MF628+

Either comment the first modem configuration out, then find and uncomment the section for the MF628+, or (more easily) replace the content of the file with:

Code:

########################################################
# ZTE MF628+ (tested version from Telia / Sweden)
#
# Contributor: Joakim Wennergren
#
# Also applies to MF627 (Tested 3 UK) JF

DefaultVendor= 0x19d2
DefaultProduct= 0x2000

TargetVendor= 0x19d2
TargetProduct= 0x0031

MessageEndpoint=0x01
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

Save it.

3) Create a udev rule to automatically run usb_modeswitch when the modem is plugged in

Create a new file called 999-zte-rules:
gksudo gedit /etc/udev/rules.d/999-zte.rules

Its content should be as follows:
Code:

SUBSYSTEM=="usb", SYSFS{idProduct}=="2000", SYSFS{idVendor}=="19d2", RUN+="/usr/sbin/usb_modeswitch"

This will trigger usb_modeswitch every time you plug in the modem. Which is useful if you want it to work automatically.

4) Add device information to HAL so network-manager recognises the device as a modem

Finally, in order for Network Manager to recognise the modem information has to be added to HAL.

Create a new file:
gksudo gedit /usr/share/hal/fdi/information/20thirdparty/20-zte-mf627.fdi

Its content should be as follows:
Code:

<!-- -*- SGML -*- -->
<deviceinfo version="0.2">
  <device>
      <!-- ZTE MF627 HSDPA USB dongle -->
      <match <email address hidden>:usb.vendor_id" int="0x19d2">
        <match <email address hidden>:usb.product_id" int="0x0031">
          <match <email address hidden>:usb.interface.number" int="3">
            <append key="modem.command_sets" type="strlist">GSM-07.07</append>
            <append key="modem.command_sets" type="strlist">GSM-07.05</append>
            <append key="info.capabilities" type="strlist">modem</append>
          </match>
        </match>
      </match>
  </device>
</deviceinfo>

Save it.

5) Plug in the modem
Make sure the SIM card is in the modem (and if you're using 3 UK make sure you're in a 3G area. otherwise it won't work) and plug it into your PC.

After several seconds the LED should light red as it powers up, then switch to blue when it finds a network. You can check it's working by checking dmesg: you should see entries for GSM modem, USB drive and CD drive. Once modeswitch has been triggered and the modem reboots you will be presented with the ZeroCD device (e.g. containing the 3connect software), a USB MicroSD card reader, and if everything has gone correctly, Network Manager will detect a new mobile broadband modem.

Feel free to ignore the ZeroCD device and unmount it from the desktop.

If everything has gone well dmesg should read something like:
Code:

[52022.169361] usb 5-1: new high speed USB device using ehci_hcd and address 31
[52022.169362] usb 5-1: configuration #1 chosen from 1 choice
[52022.172724] usb-storage: device ignored
[52079.232398] usb 5-1: USB disconnect, address 31
[52189.029694] usb 5-1: new high speed USB device using ehci_hcd and address 32
[52189.177064] usb 5-1: configuration #1 chosen from 1 choice
[52189.192061] usb-storage: device ignored
[52194.546308] usb 5-1: USB disconnect, address 32
[52200.032140] usb 5-1: new high speed USB device using ehci_hcd and address 33
[52200.183440] usb 5-1: configuration #1 chosen from 1 choice
[52200.184979] option 5-1:1.0: GSM modem (1-port) converter detected
[52200.185184] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB0
[52200.185453] option 5-1:1.1: GSM modem (1-port) converter detected
[52200.185592] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB1
[52200.200858] scsi28 : SCSI emulation for USB Mass Storage devices
[52200.204904] usb-storage: device found at 33
[52200.204909] usb-storage: waiting for device to settle before scanning
[52200.205113] option 5-1:1.3: GSM modem (1-port) converter detected
[52200.205304] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB2
[52205.205580] usb-storage: device scan complete
[52205.207696] scsi 28:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
[52205.210603] scsi 28:0:0:1: CD-ROM ZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 2
[52205.226669] sd 28:0:0:0: [sdb] Attached SCSI removable disk
[52205.228914] sd 28:0:0:0: Attached scsi generic sg2 type 0
[52205.345654] sr1: scsi-1 drive
[52205.345837] sr 28:0:0:1: Attached scsi CD-ROM sr1
[52205.346023] sr 28:0:0:1: Attached scsi generic sg3 type 5
[52218.692468] ISO 9660 Extensions: Microsoft Joliet Level 1
[52218.699732] ISOFS: changing to secondary root

(I initially tried to post this in Tips and Tricks but it hasn't appeared yet. I'm posting it here so I at least have it as a record somewhere.)

********END OF QUOTE*********

Well, I am done. I hope everyone learns what a mission it can be to get oddball equipment working on Linux but once it gets done, its satisfying. Happy computing to everyone!!

Fazl (alphamale18)
description: updated
summary: - USB Broadband HSDPA Dongle ZTE MF637 doesn't connect
+ USB Broadband ZTE HSUPA Dongle MF637 doesn't connect
Fazl (alphamale18)
description: updated
Fazl (alphamale18)
description: updated
Fazl (alphamale18)
description: updated
Revision history for this message
Sergiu Bivol (sergiu-bivol) wrote :

I have the same problem. ZTE MF637 from Orange Moldova.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Fazl (alphamale18) wrote :

Sergiu

Try JFernyhough's method. Its stated in the last entry. This IS a bug that should be fixed but hopefully that method will make it work for you while the wonderful Xubuntu linux team get the bug taken care of! Cheers! - Fazl

Revision history for this message
Sergiu Bivol (sergiu-bivol) wrote :

OK, I got mine working:

1. Install latest version of "usb_modeswitch" from
http://azrael.raboud.homelinux.org/~didier/Debian/packages/usb_modeswitch/
2. Edit /etc/usb_modeswitch.conf and uncomment the ZTE MF628+ configuration
3. sudo usb_modeswitch

I also had to configure the connection through NetworkManager and enter the PIN.

Revision history for this message
CuleaViorel (culeaviorel) wrote :

Poate sa ma ajute cineva sa instalez modemul USB Broadband HSDPA Dongle ZTE MF637 in Mandriva,
Daca se poate sa imi dati mai multe detalii,
Multumesc

Revision history for this message
moorris (ullrrich) wrote :

Sergiu Bivol
thats all u did?
I got virgin fresh Install of Ubuntu 8.10
So I Install usb_modeswutch
 uncomment ZTE MF628 ? ( I got ZTE MF 637 )
and sudo usb_modeswitch ?
Thats really all we need to do to make ZTE MF 637 working with Ubuntu ?
 and what do I do next ?how do I dial to Orange network ?

Revision history for this message
matagou (matagou) wrote :

Hi

I have followed up the Fazl's guide but without success.

here is the output:

[code]
Sep 8 18:44:29 am-nb kernel: [14416.012391] usb 4-3: new high speed USB device using ehci_hcd and address 17
Sep 8 18:44:30 am-nb kernel: [14416.157471] usb 4-3: configuration #1 chosen from 1 choice
Sep 8 18:44:30 am-nb kernel: [14416.168371] usb-storage: device ignored
Sep 8 18:44:30 am-nb kernel: [14416.168702] usbserial_generic 4-3:1.0: generic converter detected
Sep 8 18:44:30 am-nb kernel: [14416.168834] usb 4-3: generic converter now attached to ttyUSB0
Sep 8 18:44:30 am-nb kernel: [14416.169115] usb 4-3: New USB device found, idVendor=19d2, idProduct=2000
Sep 8 18:44:30 am-nb kernel: [14416.169124] usb 4-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Sep 8 18:44:30 am-nb kernel: [14416.169132] usb 4-3: Product: ZTE CDMA Technologies MSM
Sep 8 18:44:30 am-nb kernel: [14416.169138] usb 4-3: Manufacturer: ZTE,Incorporated
Sep 8 18:44:30 am-nb kernel: [14416.169144] usb 4-3: SerialNumber: MDAP673A3CDROMMS
Sep 8 18:44:30 am-nb kernel: [14416.308319] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Sep 8 18:44:30 am-nb kernel: [14416.308342] usbserial_generic 4-3:1.0: device disconnected
Sep 8 18:44:30 am-nb kernel: [14416.432711] usb 4-3: USB disconnect, address 17
Sep 8 18:44:35 am-nb kernel: [14422.020057] usb 4-3: new high speed USB device using ehci_hcd and address 18
Sep 8 18:44:36 am-nb kernel: [14422.155280] usb 4-3: configuration #1 chosen from 1 choice
Sep 8 18:44:36 am-nb kernel: [14422.157760] scsi14 : SCSI emulation for USB Mass Storage devices
Sep 8 18:44:36 am-nb kernel: [14422.163758] usb 4-3: New USB device found, idVendor=19d2, idProduct=0031
Sep 8 18:44:36 am-nb kernel: [14422.163773] usb 4-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Sep 8 18:44:36 am-nb kernel: [14422.163781] usb 4-3: Product: ZTE CDMA Technologies MSM
Sep 8 18:44:36 am-nb kernel: [14422.163787] usb 4-3: Manufacturer: ZTE,Incorporated
Sep 8 18:44:36 am-nb kernel: [14422.163794] usb 4-3: SerialNumber: 1234567890ABCDEF
Sep 8 18:44:41 am-nb kernel: [14427.165851] scsi 14:0:0:0: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 2
Sep 8 18:44:41 am-nb kernel: [14427.212552] sd 14:0:0:0: [sda] Attached SCSI removable disk
[code]

The model is ZTE MF637, connected to Orange Moldova 3G network.
OS is Debian Lenny

[code]
am@am-nb:~$ uname -a
Linux am-nb 2.6.26-2-686 #1 SMP Wed Aug 19 06:06:52 UTC 2009 i686 GNU/Linux
[code]

Revision history for this message
Susannah Burrows (susannah-burrows) wrote :

It works perfectly for me in the current testing version Ubuntu Karmic (all updates installed). Thanks!

I believe this is the original forum post: http://ubuntuforums.org/showpost.php?p=6410693&postcount=1

(My system: Linux 2.6.31-9-generic #29-Ubuntu SMP i686 GNU/Linux)

Revision history for this message
Victor Vargas (kamus) wrote :

could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Peter (peter-fjelstrup) wrote :

Running updated Karmic 9.10, Huawei mf 637 doesnt show in setting up a mobile broadband connection.
It is show in Places - Computer, and it is turning into the colour, it should have when connected.
Orange Moldova OK, APN = internet, but <any device> instead of the name.

Peter

Revision history for this message
Peter (peter-fjelstrup) wrote :

I didnt really understand step 2?
My Ubuntu only has usb_modeswitch.d in folder etc.
And its only readable.

Where and how exactly do I edit modeswitch?

help
Peter

1. Install latest version of "usb_modeswitch" from
http://azrael.raboud.homelinux.org/~didier/Debian/packages/usb_modeswitch/
2. Edit /etc/usb_modeswitch.conf and uncomment the ZTE MF628+ configuration
3. sudo usb_modeswitch

Revision history for this message
guill (gillblu) wrote :

Guys, I have a solution. Works for me.
Using ZTE MF 637
Ubuntu 9.10

1. Add a Mobile Broadband network in Network Manager, configure the number, APN and PIN. In some cases username and password are required.
2. Give it a name you'd recognize.
3. IPv4 settings method should be "Automatic (PPP) addresses only.
4. Add DNS servers (Google's are 8.8.8.8 and 8.8.4.4) and apply

5. sudo aptitude install udev-extras (credit: volaer)
6. sudo update-usbids.sh (credit: Sergiu Bivol)
7. lsusb should show: 19d2:0031 ONDA Communication S.p.A. ZTE MF636
8. Plug in the mdoem to a usb port and wait for the modem icon on the desktop
9. right click and eject the drive and unplug it
10. replug the drive. The 4GB drive should appear.
11. Wait one minute. Broadband network should appear
12. try opening https://72.14.221.99 (google.com)
13. If the DNS in the broadband network config is OK, you will be able to use normal urls.

Enjoy.
Guill

Revision history for this message
madbiologist (me-again) wrote :

I have some good news. These modems are now included in usb-modeswitch-data (20100221-1) upstream:

From the changelog:

* New upstream release.
    + New devices
      [12d1:101e] Huawei U7510 / U7517
      [198f:bccd] Beceem BCSM250
      [19d2:2000] ZTE MF626 and others

Now we just have to wait for this to be included in Ubuntu. Keep an eye on bug #564695 for that.

Also, in Ubuntu 10.04 "Lucid Lynx" HAL has been deprecated in favour of udev, which should simplify things.

Revision history for this message
kmtigent (kmtigent) wrote :

From: guill wrote on 2010-03-12:
...
9. right click and eject the drive and unplug it
10. replug the drive. The 4GB drive should appear.
11. Wait one minute. Broadband network should appear
....
Dear all:
    I'm successful access the internet when follow the steps1 to12 which suggested from guill, But there have a problem from step 10 to 11, I always need to wait more than 20 min for the network manager to show the broadband network connection. Is there have any methods can minimize the waiting time?

Revision history for this message
penalvch (penalvch) wrote :

Fazl, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: intrepid needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.