PHARscape

gtournier · Joined: 14 Jun 2008 Posts: 4

Hello,
I have been struggling for over two months trying to install my Option GlobeTrotter iCon 7.2 USB modem into Ubuntu 8.04.
Most of the information related to how to make this 3G+ USB modem work under Linux, I have found here (along with all the HSO stuff needed and the Option Rezero App).
I found it very hard to install all the needed components - being new to Linux, I really had to struggle with the lack of clear installation instructions. The only clear "How to" related to the whole process is the Fedora one - obviously some of the commands are not the same for Ubuntu and also some stuff needs to be placed in different directories - this information is described nowhere and is not clear to me.
Up to now, I understand I have to install at least 4 components :
- the HSO 1.2 drivers
- the HSOLink (which version I'm not sure...)
- the rezero App in order to disable the ZeroCD mounting of the device
- the HSOConnect (which I installed the latest version .83)

In trying to understand how to install each module, I ran into a lot of problems that beginner users don't even know about : such as the lack of some packages needed for compiling the packages, very little understanding of the Unix command shell, hardly no knowledge of where the different parts of the OS are or should be...But I did solve some of these issues until I was able to finally successfully install all the required modules to make this modem work...But (of course!) it does not work, and I really don't have a clue as to why or what is missing or which element is not placed where it should be, or what final configuration needs to be done...
The easiest module to install was the HSOConnect app - no need to even go into terminal mode for this. And it works (at least I can launch the app and have a window displayed).
The HSO drivers I did install first (as show inside the Fedora "How To") - to my knowledge the install went ok and there were no error messages. So I'm assuming this got properly installed.
I then installed the HSOLink package - and this was way more difficult than for the two other modules - but I think I finally could install this properly.
I had the hardest time with the rezero utility - I can tell it installs properly - I can even see all the required files where they should be - but this does not work and when I plug the modem into the USB I get the ZeroCD to mount! Whichever way I tried I couldn't get the ZeroCD feature to be disabled and have access to the modem itself - even if I plug the modem before starting Ubuntu or after I have a session opened : nothing changes and this damn modem is being seen as a mass medium hard disk...It is very frustrating and I am now stuck - due to my lack of knowledge of Linux.

Could you possibly create a "How To" for Ubuntu - a detailled procedure listing all what one has to do, in which order, and what the result of the commands should look like?

Could you also confirm that :
- at least one person was able to make this iCon 7.2 USB device work under Ubuntu 8.04 by installing these four packages
- that I am using the correct versions that all work together and also work with Ubuntu 8.04 and Python 2.5
-that there should be nothing more to do in terminal mode after "sudo make" and "sudo make install" for all the stuff to be at the proper place to work and with all the proper permissions...

Thank you for helping me - I have put an enormous amount of time into this - but also this was a learning process as well, and an interesting one - somehow, I am quite convinced that I am very close to make it all work and that I am just missing one little stupid detail...

Regards.

Gilles Tournier

Paul · Posted: Sun Jun 15, 2008 11:35 am Post subject:

Hi,
I have written a howto here:
http://www.pharscape.org/content/view/66/53/

gtournier · Joined: 14 Jun 2008 Posts: 4

Hello Paul,
Thank you for your help! Very Happy

Reading your new "How To" for Ubuntu and following all your instructions, I was able to solve some of the problems...but not all of them Confused

It is still not working, but I could resolve the issue with the Option rezero utility : the rule did not properly recognize my modem (as a mass storage device at first when plugged in) - because the manufacturer name is not the same...the udev rule expects "ZCOPTION" and my device shows "GT".
I assume this package was built for another Option device...Anyway, I was able to edit the rule and replace "ZCOPTION" by "GT" - and miracle! Now the rezero utility IS functioning and the ZeroCD drive is not mounted anymore!
But...it does its job to reset the device and activate the modem - and then the modem is not properly recognized for what it is now.
Follows a console output of what happens when I plug the modem in :

[ 89.389810] usb 5-1: new full speed USB device using uhci_hcd and address 2

[ 89.552857] usb 5-1: configuration #1 chosen from 1 choice

[ 89.729615] usbcore: registered new interface driver libusual

[ 89.770692] Initializing USB Mass Storage driver...

[ 89.771313] scsi5 : SCSI emulation for USB Mass Storage devices

[ 89.772027] usbcore: registered new interface driver usb-storage

[ 89.772033] USB Mass Storage support registered.

[ 89.773245] usb-storage: device found at 2

[ 89.773249] usb-storage: waiting for device to settle before scanning
[ 94.766772] usb-storage: device scan complete

[ 94.769764] scsi 5:0:0:0: CD-ROM GT HSDPA Modem 3.00 PQ: 0 ANSI: 2

[ 94.802664] sr1: scsi-1 drive

[ 94.802776] sr 5:0:0:0: Attached scsi CD-ROM sr1

[ 94.802856] sr 5:0:0:0: Attached scsi generic sg2 type 5

[ 95.029169] usb 5-1: USB disconnect, address 2

[ 96.495114] usb 5-1: new full speed USB device using uhci_hcd and address 3

[ 96.658367] usb 5-1: configuration #1 chosen from 1 choice

[ 96.851747] usbcore: registered new interface driver usbserial

[ 96.852436] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic

[ 96.853366] usbcore: registered new interface driver usbserial_generic

[ 96.853372] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial Driver core

[ 96.867739] /build/buildd/linux-2.6.24/drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port)
[ 96.867781] option 5-1:1.0: GSM modem (1-port) converter detected

[ 96.867931] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB0

[ 96.867947] option 5-1:1.1: GSM modem (1-port) converter detected

[ 96.868023] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB1

[ 96.868035] option 5-1:1.2: GSM modem (1-port) converter detected

[ 96.868111] usb 5-1: GSM modem (1-port) converter now attached to ttyUSB2

[ 96.868124] usbcore: registered new interface driver option

[ 96.868127] /build/buildd/linux-2.6.24/drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1

gilles@gilles-laptop:~$

To me, it seems that it is identified as a GSM modem and NOT as a Direct Access HSDPA network card. I do not see that it loads the HSO 1.2 drivers for this device, although they DID install properly...

Another problem is :
I do not have any ttyHS* files inside /dev/ - hence I could not check the permissions as you refer to inside your "How To".
Inside this directory, there are all sorts of tty* files but not the ttyHS0 --> HS2.
I am not sure the hso 1.2 drivers were installed properly - or maybe they are not where they should be...what do you think?
Is it the reason why the HSO drivers are not used when the modem mounts?

Thank you very much for your help, anyway Smile

Cordially

Paul · Posted: Sun Jun 15, 2008 9:37 pm Post subject:

Hi Gilles,

Thank you for the information on the ZeroCD name difference. It was a fact I had forgotten and answers some issues that other people have had with rezero not working.

Here is something we should have checked...

gtournier · Joined: 14 Jun 2008 Posts: 4

Hello again Smile

Thank you for your message. I will work around your idea that an unappropriate option driver grabs the device when it is plugged in, thus preventing the hso driver to load.
In the meantime, I also had the idea of having a more detailed info on what the usb port "sees" when the device is plugged in and I did find this lsusb command looking into the docs. And here is a copy of what it reported for the concerned usb port :

gilles@gilles-laptop:~$ sudo lsusb -v | more
[sudo] password for gilles:

Bus 007 Device 003: ID 0af0:6901 Option
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0af0 Option
idProduct 0x6901
bcdDevice 0.00
iManufacturer 1 Option N.V.
iProduct 2 Globetrotter HSDPA Modem
iSerial 4 Serial Number
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 88
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 128
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
INTERFACE CLASS: 03 24 0e
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 3 Data Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

Does this printout confirm what you expected? (idProduct 0x6901 )
Is there anything else in there that would be of interest for solving my problem?

Cheers Laughing

I feel that we are getting real close to making it work...
Gilles

Paul · Posted: Mon Jun 16, 2008 12:13 am Post subject:

The device ID "6901" is perfect for the HSO driver Wink

The blacklisting of the option module should get things working.

Cheers,
Paul

gtournier · Joined: 14 Jun 2008 Posts: 4

Hello,

Unfortunately, the blacklisting of the older option driver did not solve the problem. It seems to me that now no driver loads for this device anymore Sad

As you can see below :

[ 94.385347] usb 6-2: new full speed USB device using uhci_hcd and address 2
[ 94.553357] usb 6-2: configuration #1 chosen from 1 choice
[ 94.667493] usbcore: registered new interface driver libusual
[ 94.688335] Initializing USB Mass Storage driver...
[ 94.688836] scsi5 : SCSI emulation for USB Mass Storage devices
[ 94.689378] usbcore: registered new interface driver usb-storage
[ 94.689383] USB Mass Storage support registered.
[ 94.690342] usb-storage: device found at 2
[ 94.690345] usb-storage: waiting for device to settle before scanning
[ 99.685387] usb-storage: device scan complete
[ 99.688368] scsi 5:0:0:0: CD-ROM GT HSDPA Modem 3.00 PQ: 0 ANSI: 2
[ 99.720306] sr1: scsi-1 drive
[ 99.720418] sr 5:0:0:0: Attached scsi CD-ROM sr1
[ 99.720496] sr 5:0:0:0: Attached scsi generic sg2 type 5
[ 99.954071] usb 6-2: USB disconnect, address 2
[ 99.954334] sg_cmd_done: device detached
[ 99.954891] sr1: Hmm, seems the drive doesn't support multisession CD's
[ 101.523947] usb 6-2: new full speed USB device using uhci_hcd and address 3
[ 101.687854] usb 6-2: configuration #1 chosen from 1 choice
gilles@gilles-laptop:~$ lsmod
Module Size Used by
usb_storage 73664 1
libusual 19108 1 usb_storage
ipv6 267780 10
i915 32512 2
drm 82580 3 i915
rfcomm 41744 2
l2cap 25728 13 rfcomm
bluetooth 61156 4 rfcomm,l2cap
ppdev 10372 0
acpi_cpufreq 10796 2
cpufreq_powersave 2688 0
cpufreq_userspace 5284 0
cpufreq_ondemand 9740 1
cpufreq_conservative 8712 0
cpufreq_stats 7104 0
freq_table 5536 3 acpi_cpufreq,cpufreq_ondemand,cpufreq_stats
container 5632 0
sbs 15112 0
dock 11280 0
sbshc 7680 1 sbs
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
parport_pc 36260 0
lp 12324 0
parport 37832 3 ppdev,parport_pc,lp
joydev 13120 0
evdev 13056 6
serio_raw 7940 0
sr_mod 17956 0
cdrom 37408 1 sr_mod
psmouse 40336 0
pcspkr 4224 0
usbhid 31872 0
ata_generic 8324 0
hid 38784 1 usbhid
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
ath_pci 101024 0
wlan 207728 1 ath_pci
ath_hal 192592 1 ath_pci
battery 14212 0
ac 6916 0
snd_hda_intel 344728 3
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
video 19856 0
snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
snd_hwdep 10500 1 snd_hda_intel
output 4736 1 video
snd_seq_dummy 4868 0
wmi_acer 9644 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
snd_rawmidi 25760 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
button 9232 0
snd 56996 17 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
shpchp 34452 0
pci_hotplug 30880 1 shpchp
intel_agp 25492 1
agpgart 34760 3 drm,intel_agp
soundcore 8800 1 snd
ext3 136712 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36880 0
sd_mod 30720 3
ata_piix 19588 0
ahci 28420 2
pata_acpi 8320 0
libata 159344 4 ata_generic,ata_piix,ahci,pata_acpi
scsi_mod 151436 5 usb_storage,sr_mod,sg,sd_mod,libata
ehci_hcd 37900 0
r8169 32900 0
uhci_hcd 27024 0
usbcore 146028 6 usb_storage,libusual,usbhid,ehci_hcd,uhci_hcd
thermal 16796 0
processor 36872 4 acpi_cpufreq,thermal
fan 5636 0
fbcon 42912 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 3
gilles@gilles-laptop:~$

The lsmod command confirms that the hso module did not load...
I also tried to load it manually using modprobe, but it loads and registers without linking to the HSDPA device.

Any idea from here on?

Regards
Gilles

Paul · Posted: Mon Jun 16, 2008 9:44 am Post subject:

I have to apologise, I gave you incorrect information.

Icon 7.2 with device ID 6911 supports the HSO driver. The device you have with ID 6901 supports the PPP interface and is correctly supported by the option driver.

HSOconnect does not support PPP - but UMTSmon does.

Your choices are:

Use UMTSmon or kppp or wvdial

or

Try to upgrade the firmware. Check with your hardware supplier for an update. You can also check at http://www.option.com/support/login.shtml to see if there is a firmware update direct from Option.

Sorry, again, for the confusion.

Paul

Paul · Posted: Mon Jun 16, 2008 9:53 am Post subject:

In addition.... Just upgrading the firmware is not everything.

The PPP interface you currently have is supported by what are known as Revision 3 Windows drivers.

The HSO interface is supported by Revision 4 Windows drivers.

Not all Firmware upgrades supplied by Network Operators switch the device over to the new Rev. 4 driver set.

If the firmware update does not switch the device ID over to 6911 then the switch to the HSO interface (Rev 4 interface) is not supported by your Operator's firmware update.

Cheers,
Paul