usb 3G dongle not working in opensuse 12.2

English Hardware
1

Hi !

I have acquired an Archos USB dongle for an Internet tablet it is supposed to work on different OSes (Windows, linux etc…) .
From time to time I would like to use this dongle on my Desktop PC with opensuse 12.2 , so I just plug it in my Desktop but nothing happens in Networkmanager. The dongle is not broken , it works perfectly under Android.

So what is missing ?


output in /var/log/messages

Jan 29 14:47:37 machinux kernel:   842.406814] usb 1-3: new high-speed USB device number 8 using ehci_hcd
Jan 29 14:47:37 machinux kernel:   842.524595] usb 1-3: New USB device found, idVendor=1bbb, idProduct=f000
Jan 29 14:47:37 machinux kernel:   842.524602] usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Jan 29 14:47:37 machinux kernel:   842.524606] usb 1-3: Product: HSPA Data Card
Jan 29 14:47:37 machinux kernel:   842.524609] usb 1-3: Manufacturer: USBModem
Jan 29 14:47:37 machinux kernel:   842.524612] usb 1-3: SerialNumber: 1234567890ABCDEF
Jan 29 14:47:37 machinux kernel:   842.526971] scsi9 : usb-storage 1-3:1.0
Jan 29 14:47:37 machinux mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
Jan 29 14:47:37 machinux mtp-probe: bus: 1, device: 8 was not an MTP device
Jan 29 14:47:37 machinux dbus-daemon[659]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/host9/scsi_host/host9
Jan 29 14:47:37 machinux dbus-daemon[659]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/host9/scsi_host/host9
Jan 29 14:47:38 machinux usb_modeswitch: switching device 1bbb:f000 on 001/008
Jan 29 14:47:38 machinux dbus-daemon[659]: **** scsi_host IGNORING REMOVE /sys/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/host9/scsi_host/host9
Jan 29 14:47:38 machinux kernel:   843.297276] usb 1-3: USB disconnect, device number 8
Jan 29 14:47:39 machinux kernel:   843.606912] usb 1-3: new high-speed USB device number 9 using ehci_hcd
Jan 29 14:47:39 machinux kernel:   843.723808] usb 1-3: New USB device found, idVendor=1bbb, idProduct=00b7
Jan 29 14:47:39 machinux kernel:   843.723815] usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Jan 29 14:47:39 machinux kernel:   843.723820] usb 1-3: Product: HSPA Data Card
Jan 29 14:47:39 machinux kernel:   843.723823] usb 1-3: Manufacturer: USBModem
Jan 29 14:47:39 machinux mtp-probe: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
Jan 29 14:47:39 machinux mtp-probe: bus: 1, device: 9 was not an MTP device

no Modems appear in /dev/tty*

Any help is welcome!

2

From this thread (discussing similar model), perhaps ‘usb_modeswitch’ is required to activate the modem interface. Check that you have it installed with

rpm -qa |grep usb_modeswitch

and install if necessary

zypper in usb_modeswitch

Then plug in your 3G device and examine the dmesg output again.

3

After a quick look at my /lib/udev/rules.d/40-usb_modeswitch.rules, (openSUSE 12.2,usb_modeswitch-1.2.3-2.5.1), I don’t see any matching udev rules for your chipset.

A little more searching online turned up this post:

xda-developers - View Single Post - Archos G9 3G Stick usb dongle

which gives some hope for support using the usbserial module, and no mode switching required.

With the device plugged in, do this (with root privileges):

modprobe usbserial vendor=0x1bbb product=0x00b7

If /dev/ttyUSB* is created, then you can proceed with configuring via the network manager, and to get the device supported on a more permanent basis, you can create a udev rule as described in that post.

(BTW, for regular user access to the /dev/ttyUSB[0,1,2…] device nodes, you need to need to be a member of the ‘dialout’ group.)

Let us know how you get on.

4

hi

usb_modeswitch is installed

rpm -qa |grep usb_modeswitch
usb_modeswitch-1.2.3-2.5.1.x86_64
usb_modeswitch-data-1.2.3-2.5.1.noarch
5

Hi

after giving the command modprobe usbserial vendor=0x1bbb product=0x00b7 , nothing happens

there are no ttyUSB decices created , I have one ttyUSB0 running a fixed GPS receiver should I unplug it first ?

thanks

6

No, there should be no need to remove any other devices. I’m not sure what else to suggest. Might be a good idea to make sure that it’s not still in the wrong mode.

For storage devices, it is usual to see /dev/sr* device nodes present (ignore any associated with cdrom/dvd hardware)

ls -l /dev/sr*

and confirm that no ttyUSB* nodes exist (other than your GPS)

ls -l /dev/ttyUSB*

Some other potentially useful threads:

Enabling UMTS on Archos G9 in Plasma Active | ruedigergad

[SOLVED] Can access but not dial from my TCT Mobile One Touch X200S 3G USM Modem [Archive] - Ubuntu Forums]([SOLVED] Can access but not dial from my TCT Mobile One Touch X200S 3G USM Modem [Archive] - Ubuntu Forums)

The latter concerns a different model 3G device, but good diagnostic info.

7

Hi

I was aware of the link you gave for ruedigergad (he describes the setup for plasma desktop which does not come with modeswitch installed I think), the other link is also interesting but very technical for me.

After a lot of hacking and trials until late tonight I have been able to get this dongle work in opensuse 12.2,
even with networkmanager I could connect and surf with UMTS and disconnect to reconnect to the UMTS and surf very easy the Internet.
I also did not need to cancel PIN on the SIM Card since networkmanager asked for this, everything worked fine for a test period of about half an hour late in the night as I said above.
But things got worse after unplugging the dongle.
The big problem now is I don’t know/remember exactly the steps to reproduce the correct setup for this dongle since I have tried a lot of the suggested stuff in the links you posted.

After your suggestion to check for DVD/CD I typed

eject /dev/sr0

and suddenly the networkmanager asked for the PIN and I could connect to the internet.

As you suggest there is a modeswitch problem. Here is what I have tried now.
I have deinstalled usb_modeswitch and rebooted the machine . When I plug in the Archos dongle I get those messages in syslog:

#lsusb
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 002: ID 1bbb:f000 T & A Mobile Phones 
Bus 004 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. 
Bus 007 Device 002: ID 03eb:0902 Atmel Corp. 4-Port Hub

then I reinstalled usb_modeswitch from the opensuse repo and changed the file

/etc/usb_modeswitch.conf

verbosity to yes

EnableLogging=1

and got this in my syslog :

USB_ModeSwitch log from Wed Jan 30 03:25:54 CET 2013

Raw args from udev: /2-5:1.0

Using global config file: /etc/usb_modeswitch.conf
Using top device dir /sys/bus/usb/devices/2-5
----------------
USB values from sysfs:
  manufacturer    USBModem
  product    HSPA Data Card
  serial    1234567890ABCDEF
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /usr/share/usb_modeswitch/1bbb:f000
! matched. Reading config data
config: TargetVendor set to 1bbb
config: TargetProductList set to 0000,0017
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 14 -v 1bbb -p f000 -f $configBuffer

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.2.3 (C) Josua Dietze 2012
 * Based on libusb0 (0.1.12 and above)

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x1bbb
DefaultProduct= 0xf000
TargetVendor=   0x1bbb
TargetProduct=  not set
TargetClass=    not set
TargetProductList="0000,0017"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint=  not set
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled


Use given bus/device number: 002/014 ...
Looking for default devices ...
 bus/device number matched
  searching devices, found USB ID 1bbb:f000
   found matching vendor ID
   found matching product ID
   adding device
 Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: USBModem
     Product: HSPA Data Card
  Serial No.: 1234567890ABCDEF
-------------------------
Looking for active driver ...
 OK, driver found; name unknown, limitation of libusb1
 OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
 Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...
 Reading attributes ...

Target config not matching - current values are
    2-5:1.0/bInterfaceClass:   ff
    bConfigurationValue:       1
    bNumConfigurations:        1
    busnum:                    2
    devnum:                    15
    idProduct:                 00b7
    idVendor:                  1bbb
    manufacturer:              USBModem
    product:                   HSPA Data Card
    serial:                    

Mode switching may have failed. Exiting

any idea how I can bring it back to work ? a need a step by step help because I am not familiar with this modeswitching tool.

Thanks, :expressionless:

8

Since you successfully managed to expose the modem interface by manually ejecting the storage device, you could try creating a rule (eg /etc/udev/rules.d/10-modem.rules) that automates this process

ATTRS{idVendor}=="1bbb", ATTRS{idProduct}=="f000", RUN+="/usr/bin/eject %k", OPTIONS="last_rule"

Does that help?

9

Well as I told you I am not even sure that this eject command unblocked the situation or may a

modprobe -r usbstorage

, because today I tried again with no success.

What I noticed is that I had unplugged the GPS because it had created a ttyUSB0 device.
As the modem was activated and used by Networkmanager there were ttyUSB0, ttyUSB1,ttyUSB2,ttyUSB3,ttyUSB4 devices created One of them was ttyUSB4 was shown in networkmanager.

where does the value TargetidProduct=0x00b7 come from during the modeswitch ?

I have changed the file

/etc/usb_modeswitch like this :

# Disable automatic mode switching globally (e.g. to access the original
# install storage)

DisableSwitching=1


# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_<interface-name>" and probably others

EnableLogging=1

and want to retry with step by step from there !

so gave the command


usb_modeswitch -s 3 -v 0x1bbb -p 0xf000 -V 0x1bbb -P 0x00b7 -M 5553424308a05984c000000080000606f50402527000000000000000000000

as in Enabling UMTS on Archos G9 in Plasma Active | ruedigergad
doing lsusb after that


Bus 002 Device 004: ID 1bbb:00b7 T & A Mobile Phones

then


modprobe usbserial vendor=0x1bbb product=0x00b7

as explained by ruedigergad, but no ttyUSB devices are created , and now I am stuck there !

thanks for your help

10

The message string that is sent effectively sets the new state. The ‘TargetidProduct=’ entry in relevant config file (located in the /usr/share/usb_modeswitch/ directory) is only used for checking against. You can read the ‘usb_modeswitch’ man pages for more info on this. I’m not sure that 0x00b7 is the correct state. Some of the sources mention 0x0000 (as the modeswitch file itself suggests). When you had the modem active, it would have been good to observe the lsusb output (to see whether a different product ID was reported).

Maybe the state changing takes a little time, so the delay between steps may be important here. This is going to be a process of trial and error I’m afraid. The dmesg output is useful for providing clues about what the kernel has detected, and what the next step might be. Try plugging the device again, and try to retrace your steps. For example, invoke

modprobe -r usb-storage

then check

lsusb

dmesg|tail
11

Your modeswitch log suggest that the mode switching is failing, so I’d be surprised if it was involved in activating the modem. When you had success, was it after you had removed it? You could try removing it for now, and then try the eject command or removing the usb-storage module…

12

Hi

luckily there is the /var/log/message file

from what I remember the targetproduct id was 1x00b7 as I did not really changed it myself but who knows !
here is a snapshot of the first connection last night as found in /var/log/message


Jan 30 00:44:56 machinux kernel:   108.901625] usb 2-5: new high-speed USB device number 2 using ehci_hcd
Jan 30 00:44:56 machinux kernel:   109.019399] usb 2-5: New USB device found, idVendor=1bbb, idProduct=f000
Jan 30 00:44:56 machinux kernel:   109.019406] usb 2-5: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Jan 30 00:44:56 machinux kernel:   109.019411] usb 2-5: Product: HSPA Data Card
Jan 30 00:44:56 machinux kernel:   109.019414] usb 2-5: Manufacturer: USBModem
Jan 30 00:44:56 machinux kernel:   109.019417] usb 2-5: SerialNumber: 1234567890ABCDEF
Jan 30 00:44:56 machinux kernel:   109.021528] scsi8 : usb-storage 2-5:1.0
Jan 30 00:44:56 machinux mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:13.2/usb2/2-5"
Jan 30 00:44:56 machinux mtp-probe: bus: 2, device: 2 was not an MTP device
Jan 30 00:44:56 machinux dbus-daemon[608]: **** scsi_host ADDING /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0/host8/scsi_host/host8
Jan 30 00:44:56 machinux dbus-daemon[608]: **** scsi_host IGNORING ADD /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0/host8/scsi_host/host8
Jan 30 00:44:57 machinux usb_modeswitch: switching device 1bbb:f000 on 002/002
Jan 30 00:44:57 machinux dbus-daemon[608]: **** scsi_host IGNORING REMOVE /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0/host8/scsi_host/host8
Jan 30 00:44:57 machinux kernel:   109.790428] usb 2-5: USB disconnect, device number 2
Jan 30 00:44:57 machinux kernel:   110.099778] usb 2-5: new high-speed USB device number 3 using ehci_hcd
Jan 30 00:44:57 machinux kernel:   110.246828] usb 2-5: New USB device found, idVendor=1bbb, idProduct=00b7
Jan 30 00:44:57 machinux kernel:   110.246835] usb 2-5: New USB device strings: Mfr=3, Product=2, SerialNumber=0
Jan 30 00:44:57 machinux kernel:   110.246840] usb 2-5: Product: HSPA Data Card
Jan 30 00:44:57 machinux kernel:   110.246843] usb 2-5: Manufacturer: USBModem
Jan 30 00:44:57 machinux mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:13.2/usb2/2-5"
Jan 30 00:44:57 machinux mtp-probe: bus: 2, device: 3 was not an MTP device
Jan 30 00:45:21 machinux su: (to root) metehyi on /dev/pts/2
Jan 30 00:49:11 machinux kernel:   363.671219] usbcore: registered new interface driver usbserial
Jan 30 00:49:11 machinux kernel:   363.671256] usbcore: registered new interface driver usbserial_generic
Jan 30 00:49:11 machinux kernel:   363.671700] USB Serial support registered for generic
Jan 30 00:49:11 machinux kernel:   363.671752] usbserial_generic 2-5:1.0: generic converter detected
Jan 30 00:49:11 machinux kernel:   363.672175] usb 2-5: generic converter now attached to ttyUSB0
Jan 30 00:49:11 machinux kernel:   363.672191] usbserial_generic 2-5:1.1: generic converter detected
Jan 30 00:49:11 machinux kernel:   363.672264] usb 2-5: generic converter now attached to ttyUSB1
Jan 30 00:49:11 machinux kernel:   363.672277] usbserial_generic 2-5:1.2: generic converter detected
Jan 30 00:49:11 machinux kernel:   363.672629] usb 2-5: generic converter now attached to ttyUSB2
Jan 30 00:49:11 machinux kernel:   363.672647] usbserial_generic 2-5:1.3: generic converter detected
Jan 30 00:49:11 machinux kernel:   363.673118] usb 2-5: generic converter now attached to ttyUSB3
Jan 30 00:49:11 machinux kernel:   363.673134] usbserial_generic 2-5:1.4: generic converter detected
Jan 30 00:49:11 machinux kernel:   363.673183] usb 2-5: generic converter now attached to ttyUSB4
Jan 30 00:49:11 machinux kernel:   363.673187] usbserial: USB Serial Driver core
Jan 30 00:49:11 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) opening serial port...
Jan 30 00:49:11 machinux modem-manager[664]: <info>  (ttyUSB1) opening serial port...
Jan 30 00:49:11 machinux modem-manager[664]: <info>  (ttyUSB2) opening serial port...
Jan 30 00:49:11 machinux modem-manager[664]: <info>  (ttyUSB0) opening serial port...
Jan 30 00:49:11 machinux modem-manager[664]: <info>  (ttyUSB3) opening serial port...
Jan 30 00:49:11 machinux modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:49:11 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) opening serial port...
Jan 30 00:49:11 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) opening serial port...
Jan 30 00:49:11 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB3) opening serial port...
Jan 30 00:49:11 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5 claimed port ttyUSB4
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (ttyUSB3) closing serial port...
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (ttyUSB3) serial port closed
Jan 30 00:49:13 machinux modem-manager[664]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5 claimed port ttyUSB3
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5 claimed port ttyUSB4
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB3) closing serial port...
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB3) serial port closed
Jan 30 00:49:13 machinux dbus-daemon[608]: modem-manager[664]: <info>  (Generic): GSM modem /sys/devices/pci0000:00/0000:00:13.2/usb2/2-5 claimed port ttyUSB3
Jan 30 00:49:14 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:49:14 machinux modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:49:14 machinux modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:49:14 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:49:22 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) closing serial port...
Jan 30 00:49:22 machinux modem-manager[664]: <info>  (ttyUSB1) closing serial port...
Jan 30 00:49:42 machinux dbus-daemon[608]: dbus[608]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jan 30 00:49:42 machinux dbus[608]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Jan 30 00:49:42 machinux dbus-daemon[608]: dbus[608]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jan 30 00:49:42 machinux dbus[608]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) serial port closed
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB1) serial port closed
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB1) opening serial port...
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB2) closing serial port...
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB2) serial port closed
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB2) opening serial port...
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB0) closing serial port...
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB0) serial port closed
Jan 30 00:49:52 machinux modem-manager[664]: <info>  (ttyUSB0) opening serial port...
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) opening serial port...
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) closing serial port...
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) serial port closed
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) opening serial port...
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) closing serial port...
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) serial port closed
Jan 30 00:49:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) opening serial port...
Jan 30 00:49:58 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) closing serial port...
Jan 30 00:49:58 machinux modem-manager[664]: <info>  (ttyUSB1) closing serial port...
Jan 30 00:50:28 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB1) serial port closed
Jan 30 00:50:28 machinux modem-manager[664]: <info>  (ttyUSB1) serial port closed
Jan 30 00:50:28 machinux modem-manager[664]: <info>  (ttyUSB2) closing serial port...
Jan 30 00:50:28 machinux modem-manager[664]: <info>  (ttyUSB2) serial port closed
Jan 30 00:50:28 machinux modem-manager[664]: <info>  (ttyUSB0) closing serial port...
Jan 30 00:50:28 machinux modem-manager[664]: <info>  (ttyUSB0) serial port closed
Jan 30 00:50:28 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) closing serial port...
Jan 30 00:50:28 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB2) serial port closed
Jan 30 00:50:28 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) closing serial port...
Jan 30 00:50:28 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB0) serial port closed
Jan 30 00:53:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:53:52 machinux modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:53:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required
Jan 30 00:53:52 machinux modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: unlock no longer required
Jan 30 00:53:52 machinux modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: # unlock retries is 0
Jan 30 00:53:52 machinux dbus-daemon[608]: modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: # unlock retries is 0
Jan 30 00:53:54 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:53:54 machinux modem-manager[664]: <info>  (ttyUSB4) closing serial port...
Jan 30 00:53:54 machinux modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:53:54 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) serial port closed
Jan 30 00:53:58 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:53:58 machinux dbus-daemon[608]: modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
Jan 30 00:53:58 machinux modem-manager[664]: <info>  (ttyUSB4) opening serial port...
Jan 30 00:53:58 machinux modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (disabled -> enabling)
Jan 30 00:53:59 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB3) opening serial port...
Jan 30 00:53:59 machinux modem-manager[664]: <info>  (ttyUSB3) opening serial port...
Jan 30 00:53:59 machinux dbus-daemon[608]: modem-manager[664]: <info>  (ttyUSB4): using text mode for SMS
Jan 30 00:53:59 machinux modem-manager[664]: <info>  (ttyUSB4): using text mode for SMS
Jan 30 00:53:59 machinux dbus-daemon[608]: modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (enabling -> enabled)
Jan 30 00:54:00 machinux dbus-daemon[608]: modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
Jan 30 00:54:00 machinux modem-manager[664]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (connecting -> connected)
Jan 30 00:54:00 machinux pppd[2822]: Plugin /usr/lib64/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jan 30 00:54:00 machinux kernel:   652.424983] PPP generic driver version 2.4.2
Jan 30 00:54:00 machinux pppd[2822]: pppd 2.4.5 started by root, uid 0
Jan 30 00:54:00 machinux pppd[2822]: Using interface ppp0
Jan 30 00:54:00 machinux pppd[2822]: Connect: ppp0 <--> /dev/ttyUSB4
Jan 30 00:54:00 machinux pppd[2822]: CHAP authentication succeeded
Jan 30 00:54:00 machinux pppd[2822]: CHAP authentication succeeded
Jan 30 00:54:00 machinux kernel:   652.449406] PPP BSD Compression module registered
Jan 30 00:54:00 machinux kernel:   652.454988] PPP Deflate Compression module registered
Jan 30 00:54:01 machinux pppd[2822]: Could not determine remote IP address: defaulting to 10.64.64.64
Jan 30 00:54:01 machinux pppd[2822]: local  IP address 10.215.95.121
Jan 30 00:54:01 machinux pppd[2822]: remote IP address 10.64.64.64
Jan 30 00:54:01 machinux pppd[2822]: primary   DNS address 212.23.115.132
Jan 30 00:54:01 machinux pppd[2822]: secondary DNS address 212.23.115.148
Jan 30 00:54:01 machinux SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 30 00:54:01 machinux SuSEfirewall2: using default zone 'ext' for interface ppp0
Jan 30 00:54:02 machinux SuSEfirewall2: Firewall rules successfully set
Jan 30 00:54:02 machinux pppd[2822]: Script /etc/ppp/ip-up finished (pid 2833), status = 0x0
Jan 30 00:54:02 machinux dbus[608]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 30 00:54:02 machinux dbus-daemon[608]: dbus[608]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 30 00:54:02 machinux dbus-daemon[608]: dbus[608]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 30 00:54:02 machinux dbus[608]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'

I kept this internet connection for nearly 30-60 minutes , then I unplugged the dongle to test again but nothing was as before.

13

Hi

I have two DVD drives , one burner and one player , they are mounted on /dev/sr0 and sr1 , so the eject command I gave last night just opened the trays for the dvds . The USB 3g Dongle is shown as /dev/sr2 which I did not eject and It was not there last night.

cheers

14

Then, that had nothing to do with your success

The USB 3g Dongle is shown as /dev/sr2 which I did not eject and It was not there last night.

So, what happens when you do

eject /dev/sr2

then examine dmesg and/or lsusb?

15

I notice a lengthy gap here (between black/red output):


.
.
Jan 30 00:44:57 machinux kernel:   110.246840] usb 2-5: Product: HSPA Data Card
Jan 30 00:44:57 machinux kernel:   110.246843] usb 2-5: Manufacturer: USBModem
Jan 30 00:44:57 machinux mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:13.2/usb2/2-5"
Jan 30 00:44:57 machinux mtp-probe: bus: 2, device: 3 was not an MTP device
Jan 30 00:45:21 machinux su: (to root) metehyi on /dev/pts/2
Jan 30 00:49:11 machinux kernel:   363.671219] usbcore: registered new interface driver usbserial
Jan 30 00:49:11 machinux kernel:   363.671256] usbcore: registered new interface driver usbserial_generic
Jan 30 00:49:11 machinux kernel:   363.671700] USB Serial support registered for generic
Jan 30 00:49:11 machinux kernel:   363.671752] usbserial_generic 2-5:1.0: generic converter detected
.
.

Did you do anything special, because suddenly the /dev/ttyUSB* device nodes appear.

16

I had to cut some irrelevant lines because i cannot submit huge data , but this is my problem I do not recall what command I gave , sorry …

17

Well, start over by making sure usb_modeswitch is installed. Then plug in your device and wait. It is crucial that the ttyUSB nodes appear. If you prefer, leave the GPS device disconnected too, (although I don’t believe that should make a difference). If you don’t see the modem device appear, then proceed on to removing the ‘usb-storage’ module. We need to determine what caused the modem to kick in.

18

Hi

after rebooting and disabling automatic usb_modswitch I get

lsusb
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 003: ID 1bbb:f000 T & A Mobile Phones 
Bus 004 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. 
Bus 007 Device 002: ID 03eb:0902 Atmel Corp. 4-Port Hub
Bus 008 Device 002: ID 03f0:4305 Hewlett-Packard ScanJet G3110
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
Bus 007 Device 004: ID 1c6b:a222 Philips & Lite-ON Digital Solutions Corporation 
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

thereafter I typed

# usb_modeswitch -s 3 -v 0x1bbb -p 0xf000 -V 0x1bbb -P 0x0000 -M "55534243123456788000000080000606f50402527000000000000000000000"  
Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
   found matching product ID
   adding device
 Found device in default mode, class or configuration (1)
Accessing device 002 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found; name unknown, limitation of libusb1
 OK, driver "unkown" detached

SCSI inquiry data (for identification)
-------------------------
  Vendor String: ALCATEL 
   Model String: Mass Storage    
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: USBModem
     Product: HSPA Data Card
  Serial No.: 1234567890ABCDEF
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
 Device is gone, skipping any further commands

Checking for mode switch (max. 3 times, once per second) ...
 Searching for target devices ...
 Searching for target devices ...
 Searching for target devices ...
 No new devices in target mode or class found

Mode switch has failed. Bye.

should not the option driver or usbserial appear ?
again

 # lsusb
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 003: ID 1bbb:00b7 T & A Mobile Phones 
Bus 004 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. 
.....

why does it switch to

Bus 002 Device 003: ID 1bbb:00b7 T & A Mobile Phones

and not to

Bus 002 Device 003: ID 1bbb:0000 T & A Mobile Phones

as requested in my usb_modswich command ?

this is my puzzle for now ! any idea ?

Cheers

19

[QUOTE=metehyi;2523346]Hi

after rebooting and disabling automatic usb_modswitch I get

lsusb
Bus 002 Device 003: ID 1bbb:f000 T & A Mobile Phones

As expected. The device state is at default.

thereafter I typed

# usb_modeswitch -s 3 -v 0x1bbb -p 0xf000 -V 0x1bbb -P 0x0000 -M "55534243123456788000000080000606f50402527000000000000000000000"  

 # lsusb
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 002 Device 003: ID 1bbb:00b7 T & A Mobile Phones 
Bus 004 Device 002: ID 0603:00f2 Novatek Microelectronics Corp. 
.....

why does it switch to

Bus 002 Device 003: ID 1bbb:00b7 T & A Mobile Phones

and not to

Bus 002 Device 003: ID 1bbb:0000 T & A Mobile Phones

as requested in my usb_modswich command ?

this is my puzzle for now ! any idea ?

Cheers

The target ID does not influence the device mode switching, only the string sent. I explained that before. Read

man usb_modeswitch

-V --target-vendor NUM
Target vendor ID. When given will be searched for and
detected initially for information purposes. If success
checking (option -s) is active, providing target IDs (ven-
dor/product) or target class is recommended

20

Ok here is a step by step method to bring this hardware to connect to the Internet with PIN Code request , but it connects for one time , if I unplug/plug-in the Archos usb dongle for second time no connection is possible, provided are also dmesg…

  • first removed my USB GPS Receiver from the USB in my PC it was using /dev/ttyUSB0 and stopped gpsd (also in /etc/sysconfig/gpsd set GPSD_STARTBYUDEV=“no”)
  • changed DisableSwitching=0 in the file /etc/usb_modeswitch.conf
  • reboot
  • plugged the Archos usb 2g dongle
  • lsusb shows
# lsusb
Bus 002 Device 005: ID 1bbb:00b7 T & A Mobile Phones
  • rmmod usb_storage
# ls -lrt /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 3 Jan 31 18:30 /dev/ttyUSB3
crw-rw---- 1 root dialout 188, 2 Jan 31 18:31 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 1 Jan 31 18:31 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 0 Jan 31 18:31 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 4 Jan 31 18:43 /dev/ttyUSB4
  • now in network manager the Broadband Mobile activation is possible
  • click on a provider established Internet Connection to my prefered 3g provider and asked for my PIN stored in Kwallet
  • everything fine with surfing for a while blinking yellow diode on usb stick goes blue
  • unplugged the usb dongle
  • ls -l /devttyUSB* shows nothing as expected
ls -l /dev/ttyUSB*
ls: cannot access /dev/ttyUSB*: No such file or directory
  • typed dmesg -c
 2759.666752] usb 2-5: USB disconnect, device number 5
 2759.666949] generic ttyUSB0: generic converter now disconnected from ttyUSB0
 2759.666972] usbserial_generic 2-5:1.0: device disconnected
 2759.667172] generic ttyUSB1: generic converter now disconnected from ttyUSB1
 2759.667192] usbserial_generic 2-5:1.1: device disconnected
 2759.667339] generic ttyUSB2: generic converter now disconnected from ttyUSB2
 2759.667359] usbserial_generic 2-5:1.2: device disconnected
 2759.668709] generic ttyUSB3: generic converter now disconnected from ttyUSB3
 2759.668738] usbserial_generic 2-5:1.3: device disconnected
 2759.669865] generic ttyUSB4: generic converter now disconnected from ttyUSB4
 2759.669898] usbserial_generic 2-5:1.4: device disconnected
  • plugged again the usb 3g dongle
# dmesg 
 2900.392536] usb 2-5: new high-speed USB device number 6 using ehci_hcd
 2900.510189] usb 2-5: New USB device found, idVendor=1bbb, idProduct=f000
 2900.510195] usb 2-5: New USB device strings: Mfr=3, Product=2, SerialNumber=4
 2900.510200] usb 2-5: Product: HSPA Data Card
 2900.510203] usb 2-5: Manufacturer: USBModem
 2900.510206] usb 2-5: SerialNumber: 1234567890ABCDEF
 2900.516444] Initializing USB Mass Storage driver...
 2900.516538] scsi12 : usb-storage 1-4:1.0
 2900.516674] scsi13 : usb-storage 7-2.4:1.0
 2900.516780] scsi14 : usb-storage 2-5:1.0
 2900.516821] usbcore: registered new interface driver usb-storage
 2900.516823] USB Mass Storage support registered.
 2901.273410] usb 2-5: USB disconnect, device number 6
 2901.518493] scsi 12:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 0
 2901.518778] sd 12:0:0:0: Attached scsi generic sg4 type 0
 2901.519886] scsi 12:0:0:1: Direct-Access     Generic- Compact Flash    1.01 PQ: 0 ANSI: 0
 2901.520228] sd 12:0:0:1: Attached scsi generic sg5 type 0
 2901.521647] scsi 12:0:0:2: Direct-Access     Generic- SM/xD-Picture    1.02 PQ: 0 ANSI: 0
 2901.522073] sd 12:0:0:2: Attached scsi generic sg6 type 0
 2901.522627] sd 12:0:0:0: [sdd] Attached SCSI removable disk
 2901.523346] sd 12:0:0:1: [sde] Attached SCSI removable disk
 2901.524178] scsi 13:0:0:0: CD-ROM            slimtype  eTDU108   1     SL46 PQ: 0 ANSI: 0
 2901.524599] scsi 12:0:0:3: Direct-Access     Generic- MS/MS-Pro        1.03 PQ: 0 ANSI: 0 CCS
 2901.525740] sd 12:0:0:3: Attached scsi generic sg7 type 0
 2901.525971] sd 12:0:0:2: [sdf] Attached SCSI removable disk
 2901.528969] sd 12:0:0:3: [sdg] Attached SCSI removable disk
 2901.544146] sr1: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda pop-up
 2901.544242] sr 13:0:0:0: Attached scsi CD-ROM sr1
 2901.544317] sr 13:0:0:0: Attached scsi generic sg8 type 5
 2901.582581] usb 2-5: new high-speed USB device number 7 using ehci_hcd
 2901.700024] usb 2-5: New USB device found, idVendor=1bbb, idProduct=00b7
 2901.700028] usb 2-5: New USB device strings: Mfr=3, Product=2, SerialNumber=0
 2901.700030] usb 2-5: Product: HSPA Data Card
 2901.700031] usb 2-5: Manufacturer: USBModem
 2901.701989] usbserial_generic 2-5:1.0: generic converter detected
 2901.702041] usb 2-5: generic converter now attached to ttyUSB0
 2901.702078] usbserial_generic 2-5:1.1: generic converter detected
 2901.702116] usb 2-5: generic converter now attached to ttyUSB1
 2901.702148] usbserial_generic 2-5:1.2: generic converter detected
 2901.702188] usb 2-5: generic converter now attached to ttyUSB2
 2901.702220] usbserial_generic 2-5:1.3: generic converter detected
 2901.702258] usb 2-5: generic converter now attached to ttyUSB3
 2901.702289] usbserial_generic 2-5:1.4: generic converter detected
 2901.702328] usb 2-5: generic converter now attached to ttyUSB4

lsmod | grep storage
usb_storage            57741  0

# rmmod  -v usb_storage
rmmod usb_storage, wait=no

ls -lrt /dev/ttyUSB*

crw-rw---- 1 root dialout 188, 3 Jan 31 19:06 /dev/ttyUSB3
crw-rw---- 1 root dialout 188, 2 Jan 31 19:07 /dev/ttyUSB2
crw-rw---- 1 root dialout 188, 1 Jan 31 19:07 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 0 Jan 31 19:07 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 4 Jan 31 19:08 /dev/ttyUSB4

  • in networkmanager tried to establish a new 3g connection to my provider with no succes !
  • dmes shows nothing
tail -f /var/log/message 
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB4) opening serial port...
Jan 31 19:11:26 machinux modem-manager[709]: <info>  Modem /org/freedesktop/ModemManager/Modems/2: state changed (disabled -> enabling)
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB4) opening serial port...
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  Modem /org/freedesktop/ModemManager/Modems/2: state changed (disabled -> enabling)
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB3) opening serial port...
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB3) opening serial port...
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <warn>  (ttyUSB4): failed to query SMS mode, assuming text mode
Jan 31 19:11:26 machinux modem-manager[709]: <warn>  (ttyUSB4): failed to query SMS mode, assuming text mode
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <warn>  (ttyUSB4): failed to enable USSD notifications.
Jan 31 19:11:26 machinux modem-manager[709]: <warn>  (ttyUSB4): failed to enable USSD notifications.
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  Modem /org/freedesktop/ModemManager/Modems/2: state changed (enabling -> disabled)
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB4) closing serial port...
Jan 31 19:11:26 machinux modem-manager[709]: <info>  Modem /org/freedesktop/ModemManager/Modems/2: state changed (enabling -> disabled)
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB4) closing serial port...
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB4) serial port closed
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB3) closing serial port...
Jan 31 19:11:26 machinux modem-manager[709]: <info>  (ttyUSB3) serial port closed
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB4) serial port closed
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB3) closing serial port...
Jan 31 19:11:26 machinux dbus-daemon[632]: modem-manager[709]: <info>  (ttyUSB3) serial port closed
  • impossible to reestablish internet connection although /dev/ttyUSB* still available

any ideas ?