Bug 490225
Created attachment 335170 [details]
The NetworkManager menù before connectiong the USB modem
Created attachment 335171 [details]
The NetworkManager menù after the USB modem has been connected
Created attachment 335172 [details]
Messages in /var/log/messages when I click on the "Auto Mobile Broadband (GSM) connection" voice in NetworkManager
This bug has been triaged. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Simone, are you comfortable with the terminal? I'll need to see some serial debugging logs here. If you are comfortable, can you do the following things from a 'root' terminal? 1) unplug your modem 2) serivce NetworkManager stop 3) NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon 4) plug your modem in 5) (as your user from the GUI) click on the 3G modem in the applet's menu 6) wait until the 3G connect attempt fails 7) Copy the NetworkManager output from the terminal, and attach it to this bug report Looks like the modem doesn't like any of the AT init strings NM is sending. If you happen to know one that works (for example, if you've ever been able to get the modem to work with wvdial) that would help me a lot. Otherwise we can continue to narrow down the issue with some trial & error. Also, something else useful would be the output of: /sbin/udevadm info --export-db so I can see what serial ports on the ZTE device actually accept AT commands. Created attachment 336184 [details]
NetworkManager output for serial debugging
Here's the output.
A couple of things to note:
1. When I issued the command:
NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon
a SELinux AVC error appeared on the systray (the yellow star icon)
The error is:
SELinux is preventing dhclient (dhcpc_t) "read" to ./nm-dhclient-eth1.conf (var_run_t).
When NetworkManager is used like a service there's no problem.
2. Now there are 2 voices in the NetworkManager menù for the USB modem (see next attachment
Created attachment 336185 [details]
NetworkManager menù after the USB modem has been connected (2 voices)
Created attachment 336186 [details]
Output of "/sbin/udevadm info --export-db"
Can I also get "lshal" output when the device is plugged in? Created attachment 336478 [details]
Output of lshal
Can you try this build? http://koji.fedoraproject.org/koji/buildinfo?buildID=96639 It has some fixes for odd modems like the ZTEs and the Huaweis. Tried the build requested in comment #12: NetworkManager 1:0.7.0.100-1.fc10 NetworkManager-glib 1:0.7.0.100-1.fc10 NetworkManager-gnome 1:0.7.0.100-1.fc10 but the situation is more or less the same. Maybe there's a slight improvement: when I click on the modem option now it shows the 2 green circles with the "comet" spinning for a while (I'm not sure but the previous version didn't show these...). But after that the modem still doesn't work. I'll post the messages in /var/log/messages both for modem connection and detection and when I select the modem option. Created attachment 339838 [details]
Messages in /var/log/messages when connecting the modem
Created attachment 339839 [details]
Messages in /var/log/messages when I click on the "Auto Mobile Broadband (GSM) connection" voice in NetworkManager
(In reply to comment #15) > Created an attachment (id=339839) [details] > Messages in /var/log/messages when I click on the "Auto Mobile Broadband (GSM) > connection" voice in NetworkManager I read in somewhere that networkmanger don't (yet) support 3g , you have to make a dial for you connection , im my case , after arrive to this . to unlock SIM # COMGTPIN=9999 /usr/bin/comgt PIN -d /dev/ttyUSB0 /usr/bin/wvdial tmn where /etc/wvdial.conf is : Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = Analog Modem ; Phone = ISDN = 0 ; Username = Init1 = ATZ ; Password = Modem = /dev/ttyUSB0 Baud = 460800 [Dialer tmn] Init2 = ATZ Init3 = AT+CGDCONT=1,"ip","internet" Stupid Mode = 1 ISDN = 0 Phone = *99***1# Ask Password = 0 Modem = /dev/ttyUSB0 Username = tmn Dial Command = ATD Password = tmn Baud = 460800 I think I'm seeing a similar behavior happening in Fedora 11 with my ZTE MF626 (driver: option) HSDPA modem. After a lot of debugging while reading /var/log/messages, I saw that NetworkManager is not consistent in detecting at what interface the modem (AT command interface) really is. In the great majority of times, NM recognizes my modem in ttyUSB1, and initialization always fails. There are times when NM uses ttyUSB0 or even ttyUSB3. There are some situations, though, that NM (correctly) identifies the modem at ttyUSB2 (see attachment for the 'correct_behavior;' log) I'm unable to check if this is a driver (option module) issue or a NM issue, since often times I see log items such as: Jun 17 13:07:25 klausk NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties and thus ttyUSB2 ends up discarded (note that it's still more common to see NM selecting ttyUSB0 without any 'ignoring due to lack of capabilities' messages). This bug is annoying.. please let me know how I can help in further debugging. Thanks, -Klaus Created attachment 348293 [details]
NM log for the correct behavior
This is rare when using the ZTE MF 626, but it (naturally) happens from time to time - yeah, wonder if it's a timing issue
Created attachment 348300 [details]
A sample of when NM doesn't use NM
I spent a bunch of time back in August making ZTE devices (including the MF626) work better upstream; so this should get quite a bit better with NM 0.7.2 snapshots that I'll build for F10. IN the mean time, could you provide the 'lsusb' output when the device is plugged in and recognized by NetworkManager? I'd like to make sure your device is handled properly by the ID matching that NM has to do. Model MF622
to work I have to add /etc/udev/rules.d/70-persistent-cd.rules
ACTION=="add", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2000", RUN+="/usr/bin/usb_modeswitch"
lsusb -s 004 -v
Bus 002 Device 004: ID 19d2:0001 ONDA Communication S.p.A.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x19d2 ONDA Communication S.p.A.
idProduct 0x0001
bcdDevice 0.00
iManufacturer 1 Qualcomm, Incorporated
iProduct 2 ZTE CDMA Technologies MSM
Oct 15 18:53:55 segulix kernel: usb 2-1: new full speed USB device using uhci_hcd and address 6
Oct 15 18:53:55 segulix kernel: usb 2-1: New USB device found, idVendor=19d2, idProduct=0001
Oct 15 18:53:55 segulix kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 15 18:53:55 segulix kernel: usb 2-1: Product: ZTE CDMA Technologies MSM
Oct 15 18:53:55 segulix kernel: usb 2-1: Manufacturer: Qualcomm, Incorporated
Oct 15 18:53:55 segulix kernel: usb 2-1: configuration #1 chosen from 1 choice
Oct 15 18:53:55 segulix kernel: option 2-1:1.0: GSM modem (1-port) converter detected
Oct 15 18:53:55 segulix kernel: usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
Oct 15 18:53:55 segulix kernel: option 2-1:1.1: GSM modem (1-port) converter detected
Oct 15 18:53:55 segulix kernel: usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
Oct 15 18:53:55 segulix kernel: option 2-1:1.2: GSM modem (1-port) converter detected
Oct 15 18:53:55 segulix kernel: usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
Oct 15 18:54:02 segulix NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:CDMA)
Oct 15 18:54:02 segulix NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Oct 15 18:54:04 segulix NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Oct 15 18:54:05 segulix NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
https://admin.fedoraproject.org/updates/NetworkManager-0.7.1.997-1.fc10,mobile-broadband-provider-info-1.20090918-1.fc10?_csrf_token=4a9d08a8e7454b749cd8a0339c3cab4de1699810 Please try the NetworkManager packages listed there; they have specific fixes for ZTE/Onda devices. Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Oct 17 02:37:04 segulix NetworkOct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabiltiesManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Oct 17 02:37:04 segulix NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Rebooting haldaemon with various combinations :
still need :
ACTION=="add", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2000", RUN+="/usr/bin/usb_modeswitch"
--- /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi.orig 2009-03-16 13:02:14.000000000 +0000
+++ /usr/share/hal/fdi/information/10freedesktop/10-modem.fdi 2009-03-16 13:06:10.000000000 +0000
@@ -299,13 +299,13 @@
<match key="@info.parent:usb.vendor_id" int="0x19d2">
<!-- Qualcomm: Telstra/NextG CDMA , ZTE CDMA Tech -->
- <match key="@info.parent:usb.product_id" int_outof="0x0001;0xfffe">
+ <match key="@info.parent:usb.product_id" int_outof="0xfffe">
<match key="@info.parent:usb.interface.number" int="0">
<append key="modem.command_sets" type="strlist">IS-707-A</append>
</match>
</match>
<!-- ZTE MF626 HSDPA USB dongle -->
- <match key="@info.parent:usb.product_id" int="0x2000">
+ <match key="@info.parent:usb.product_id" int="0x0001;0x2000">
<match key="@info.parent:usb.interface.number" int="0">
<append key="modem.command_sets" type="strlist">GSM-07.07</append>
<append key="modem.command_sets" type="strlist">GSM-07.05</append>
and NetworkManager don't recognize any device has mobile broadband ,
has CDMA or has GSM .
Sometime in past NetworkManager at least allow try dial some connection and did it , if before, I unblock PIN with comgt ,
# COMGTPIN=1111 /usr/bin/comgt PIN -d /dev/ttyUSB0
(In reply to comment #20) > I spent a bunch of time back in August making ZTE devices (including the MF626) > work better upstream; so this should get quite a bit better with NM 0.7.2 > snapshots that I'll build for F10. IN the mean time, could you provide the > 'lsusb' output when the device is plugged in and recognized by NetworkManager? > I'd like to make sure your device is handled properly by the ID matching that > NM has to do. Hi Dan, I'm not using F10 anymore but F11. It's fully updated (NetworkManager 1:0.7.1-8.git20090708.fc11), but when I plug the Onda MT505UP is not anymore recognized by NetworkManager. Here's the /var/log/messages output: Oct 26 08:40:43 penguin kernel: usb 5-1: new full speed USB device using uhci_hcd and address 2 Oct 26 08:40:43 penguin kernel: usb 5-1: New USB device found, idVendor=19d2, idProduct=2000 Oct 26 08:40:43 penguin kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 26 08:40:43 penguin kernel: usb 5-1: Product: USB ONDA Storage Oct 26 08:40:43 penguin kernel: usb 5-1: Manufacturer: Qualcomm, Incorporated Oct 26 08:40:43 penguin kernel: usb 5-1: configuration #1 chosen from 1 choice Oct 26 08:40:43 penguin kernel: Initializing USB Mass Storage driver... Oct 26 08:40:43 penguin kernel: scsi4 : SCSI emulation for USB Mass Storage devices Oct 26 08:40:43 penguin kernel: usbcore: registered new interface driver usb-storage Oct 26 08:40:43 penguin kernel: USB Mass Storage support registered. Oct 26 08:40:43 penguin kernel: usbcore: registered new interface driver usbserial Oct 26 08:40:43 penguin kernel: USB Serial support registered for generic Oct 26 08:40:43 penguin kernel: usbcore: registered new interface driver usbserial_generic Oct 26 08:40:43 penguin kernel: usbserial: USB Serial Driver core Oct 26 08:40:43 penguin kernel: USB Serial support registered for GSM modem (1-port) Oct 26 08:40:43 penguin kernel: usbcore: registered new interface driver option Oct 26 08:40:43 penguin kernel: option: v0.7.2:USB Driver for GSM modems Oct 26 08:40:48 penguin kernel: scsi 4:0:0:0: CD-ROM ONDA USB Storage 2.31 PQ: 0 ANSI: 2 Oct 26 08:40:48 penguin kernel: sr1: scsi-1 drive Oct 26 08:40:48 penguin kernel: sr 4:0:0:0: Attached scsi generic sg2 type 5 Oct 26 08:40:49 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:40:49 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:40:49 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:40:50 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:40:50 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:40:50 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:40:53 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:40:53 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:40:53 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:40:53 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 Oct 26 08:40:53 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 Oct 26 08:40:53 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 However, here's the lsusb output: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 19d2:2000 ONDA Communication S.p.A. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c521 Logitech, Inc. MX620 Laser Cordless Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub (In reply to comment #22) > https://admin.fedoraproject.org/updates/NetworkManager-0.7.1.997-1.fc10,mobile-broadband-provider-info-1.20090918-1.fc10?_csrf_token=4a9d08a8e7454b749cd8a0339c3cab4de1699810 > > Please try the NetworkManager packages listed there; they have specific fixes > for ZTE/Onda devices. Tried the package for F11 (1:0.7.1.997-1.fc11), but the problem is the same: the modem is not recognized by NetworkManager: Oct 26 08:59:17 penguin kernel: usb 5-1: new full speed USB device using uhci_hcd and address 2 Oct 26 08:59:17 penguin kernel: usb 5-1: New USB device found, idVendor=19d2, idProduct=2000 Oct 26 08:59:17 penguin kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 26 08:59:17 penguin kernel: usb 5-1: Product: USB ONDA Storage Oct 26 08:59:17 penguin kernel: usb 5-1: Manufacturer: Qualcomm, Incorporated Oct 26 08:59:17 penguin kernel: usb 5-1: configuration #1 chosen from 1 choice Oct 26 08:59:17 penguin kernel: Initializing USB Mass Storage driver... Oct 26 08:59:17 penguin kernel: scsi4 : SCSI emulation for USB Mass Storage devices Oct 26 08:59:17 penguin kernel: usbcore: registered new interface driver usb-storage Oct 26 08:59:17 penguin kernel: USB Mass Storage support registered. Oct 26 08:59:17 penguin kernel: usbcore: registered new interface driver usbserial Oct 26 08:59:17 penguin kernel: USB Serial support registered for generic Oct 26 08:59:17 penguin kernel: usbcore: registered new interface driver usbserial_generic Oct 26 08:59:17 penguin kernel: usbserial: USB Serial Driver core Oct 26 08:59:17 penguin kernel: USB Serial support registered for GSM modem (1-port) Oct 26 08:59:17 penguin kernel: usbcore: registered new interface driver option Oct 26 08:59:17 penguin kernel: option: v0.7.2:USB Driver for GSM modems Oct 26 08:59:22 penguin kernel: scsi 4:0:0:0: CD-ROM ONDA USB Storage 2.31 PQ: 0 ANSI: 2 Oct 26 08:59:22 penguin kernel: sr1: scsi-1 drive Oct 26 08:59:22 penguin kernel: sr 4:0:0:0: Attached scsi generic sg2 type 5 Oct 26 08:59:22 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:59:22 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:59:22 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:59:23 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:59:23 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:59:23 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:59:26 penguin kernel: sr1: CDROM (ioctl) error, command: Get configuration 46 00 00 00 00 00 00 00 20 00 Oct 26 08:59:26 penguin kernel: sr: Sense Key : No Sense [current] Oct 26 08:59:26 penguin kernel: sr: Add. Sense: No additional sense information Oct 26 08:59:26 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 Oct 26 08:59:26 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 Oct 26 08:59:26 penguin kernel: usb 5-1: reset full speed USB device using uhci_hcd and address 2 Maybe with something like usb_switch it should work (see comments 21 and 23). Simone: yes, you'll likely need to install usb_modeswitch to make the device eject the CDROM and become a modem. That's not something NM does or should do, as there are already tools like usb_modeswitch out there that do this. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. (In reply to comment #22) > https://admin.fedoraproject.org/updates/NetworkManager-0.7.1.997-1.fc10,mobile-broadband-provider-info-1.20090918-1.fc10?_csrf_token=4a9d08a8e7454b749cd8a0339c3cab4de1699810 > > Please try the NetworkManager packages listed there; they have specific fixes > for ZTE/Onda devices. https://bugzilla.redhat.com/show_bug.cgi?id=547513#c4, I found how I debug modem-manager and found that doesn't work because the SIM is locked, once I unblock 3G card with PIN, NetworkManager (I'm trying last one ModemManager-0.2.997-4.git20091218) seems to works great. Any tip for unlock SIMS with a PIN, before try probe the modem ? :~#modem-manager --debug ** Message: Loaded plugin Huawei ** Message: Loaded plugin Gobi ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin MotoC ** Message: Loaded plugin Generic ** Message: Loaded plugin Ericsson MBM ** Message: Loaded plugin ZTE ** Message: Loaded plugin Nokia ** Message: Loaded plugin Option ** Message: Loaded plugin Novatel ** Message: Loaded plugin Sierra ** Message: (ttyUSB2) opening serial device... ** (modem-manager:29453): DEBUG: (ttyUSB2): probe requested by plugin 'ZTE' ** Message: (ttyUSB1) opening serial device... ** (modem-manager:29453): DEBUG: (ttyUSB1): probe requested by plugin 'ZTE' ** Message: (ttyUSB0) opening serial device... ** (modem-manager:29453): DEBUG: (ttyUSB0): probe requested by plugin 'ZTE' ** (modem-manager:29453): DEBUG: (ttyUSB2): --> 'ATE0+CPMS?<CR>' ** (modem-manager:29453): DEBUG: (ttyUSB2): <-- 'ATE0+CPMS?<CR><CR><LF>ERROR<CR><LF>' ** (modem-manager:29453): DEBUG: Got failure code 100: Unknown error ** (modem-manager:29453): DEBUG: (ttyUSB2): --> 'ATE0+CPMS?<CR>' ** (modem-manager:29453): DEBUG: (ttyUSB1): --> 'ATE0+CPMS?<CR>' ** (modem-manager:29453): DEBUG: (ttyUSB0): --> 'ATE0+CPMS?<CR>' ** (modem-manager:29453): DEBUG: (ttyUSB2): <-- 'ATE0+CPMS?<CR><CR><LF>ERROR<CR><LF><CR><LF>+ZDONR: "Not Found"<CR><LF><CR><LF>+ZPASR: "Limited Service"<CR><LF><CR><LF>+ZDONR: "Not Found"<CR><LF><CR><LF>+ZPASR: "Limited Service"<CR><LF><CR><LF>+ZDONR: "Not Found"<CR><LF><CR><LF>+ZPASR: "Limited Service"<CR><LF>' ** (modem-manager:29453): DEBUG: Got failure code 100: Unknown error |
Created attachment 335169 [details] Messages in /var/log/messages when connecting the modem Description of problem: If I plug the Onda MT505UP to the USB port, the modem is recognized but it doesn't work. Tried on a Acer Travelmate 4002WLMi and on a IBM Thinkpad and in both cases the result is the same. My OS is Fedora 10 fully updated (13/3/2009) Version-Release number of selected component (if applicable): NetworkManager-0.7.0.99-3.fc10.i386 How reproducible: Always Steps to Reproduce: 1. Connect the Onda MT505UP to the USB port 2. Wait about 30 seconds 3. Clicking on the NetworkManager icon there's the additional voice for the UMTS modem, but if I click on it gives an error Actual results: The modem doesn't work Expected results: Clicking on the NetworkManager icon and selecting the relative voice the modem should work Additional info: The MT505UP is a composite device: - GPRS/EDGE/UMTS/HSDPA/HSUPA modem - USB storage device 1GB When plugged the OS detect the USB storage device, then immediately ignore it. After about 20 seconds it detects the modem and configures it correctly, except for a couple of errors (and the fact that it doesn't work).