USB id 0af0:6911 should use hso and not 'option' driver

[Martijn vdS]

I have an Option iCON 7.2 USB UMTS/HSDPA device, with USB ID 0af0:6911.

It has new firmware (which also changed the USB id to the current one), doesn't work with the 'option' driver, but does work with the 'hso' driver (usb-add-option-hso-driver.patch in gregkh's linux-staging), so I think it would be right if the 'option' driver didn't try to manage the device.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Martijn vdS (martijn)]

The "option" module still gets loaded in 2.6.27-1, but only before the device switches (using the rezero tool, se my ppa) to "HSDPA modem"-mode.

usb-storage also gets loaded, which triggers the "rezero" udev rule.

[Martijn vdS (martijn)]

This is the only bug preventing 3G from working out-of-the-box for me.

[Martijn vdS (martijn)]

Confirmed this with another Option USB device on a different machine.

[Ville Valtasaari (vva-novision)]

I'm running Intrepid w. Array.org kernel + HSO Pharscape (http://www.pharscape.org/content/view/66/53/) + rezero (https://launchpad.net/~martijn/+archive) on an Asus eeepc 901. Network-manager didn't have a clue about my Option Icon 225 USB-modem, so I installed hso. The setup works.

I'm a newbie so I'm not sure this is relevant, but now what happens is that removing the modem while HSOConnect is running will hang Ubuntu (must forcibly power down) and create errors on both my SSD my disks. The disks are not properly repaired on boot, so I've had to reinstall (twice).

[Alexander Sack (asac)]

hso should be supported in intrepid. can you confirm that fixing the driver mapping helps?

[Ville Valtasaari (vva-novision)]

As I said, I'm fairly new to linux. How do I go about that?

[Alexander Sack (asac)]

please attach the output of lsmod for now.

[wabre (fancollo)]

i'm having the same problem, same device icon 225 on a HP TX2120us tablet with intrepid 8.10 32bit.

network manager does not recognize the modem at all, tried with a huawei 220 and that worked flawlessly in network manager.

lsmod and dmesg attached, other docs needed?

second newbie here

cheers

[wabre (fancollo)]

second attachement of course here

[Alexander Sack (asac)]

not a NM bug.

[Alexander Sack (asac)]

Pete, assigning to you to get kernel team attention. Dispatch to someone appropriate please.

[Alexander Sack (asac)]

On Wed, Dec 17, 2008 at 01:46:58AM -0000, Leann Ogasawara wrote:
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>

Leann, this sounds like rather a simple fix. Can you ensure that this
gets done during this cycle so users with that hardware dont get a
wrong driver?

 - Alexander

[Leann Ogasawara (leannogasawara)]

Hi Alexander,

I'll make sure we track this and try to get this resolved for Jaunty's release. Thanks.

[thoughtbox (th-ubuntu)]

Could you make sure this also is the case for the 6711 device id? The "option" driver does not work with this device; only the "hso" driver (albeit with its watchdog timeouts and crashes, by the looks of things -- see my bug report elsewhere).

Bus 005 Device 002: ID 0af0:6711 Option

AKA Option Globetrotter MAX "7.2 Ready"
AKA Option GX0201

Thanks!

[Andy Whitcroft (apw)]

@Martijn van de Streek, thoughtbox -- the current intrepid kernels have both the option and hso drivers, looking at the PCI ids you are reporting here they appear to only be supported by the hso driver. I would therefore expect only that driver to be loaded when they are detected.

So could you confirm that you still see this issue with the kernel in -proposed (the -11 kernel). Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

If the problem is still present with this release then could you attach the output of the following commands to this bug (all with the device inserted):

    dmesg
    lsusb -v
    lsmod

Either way report back here with the results of your testing. Thanks.

[Martijn vdS (martijn)]

Works for me in -11.

[Andy Whitcroft (apw)]

This looks to have been resolved during the stable updates.

[Ban (sven-waeyenbergh)]

i'm still having the 'hanging' problem on an updated 8.10 with a Option Icon 225 (GIO225)

I used the udev rule in combination with rezero to load the hso driver for this device, that works great.
i can use the connection in networkmanager, but as soon as the connection stops (for example because of signal loss),
the systems hangs completely and has to be forcibly powered off

uname reports 2.6.27-9-generic (32bit)
modinfo reports hso version is 1.2
deviceid is 0af0:6971

i'm getting no logging at all when the crash occurs, so i'm at a loss on how to provide more info.

[Ban (sven-waeyenbergh)]

update:
if i manually stop the 3g connection,
but the kernel module is still loaded, the hang does not occur.

i hope it's ok to log this here, please let me know if i need to open another bug report.

[Alexander Sack (asac)]

On Tue, Jan 20, 2009 at 01:49:20PM -0000, Ban wrote:
> i'm still having the 'hanging' problem on an updated 8.10 with a Option
> Icon 225 (GIO225)
>
> I used the udev rule in combination with rezero to load the hso driver for this device, that works great.
> i can use the connection in networkmanager, but as soon as the connection stops (for example because of signal loss),
> the systems hangs completely and has to be forcibly powered off

Could you check whether the jaunty kernel works for your without
rezero?

 - Alexander

[Martijn vdS (martijn)]

Without rezero, I get the ZeroCD CD drive, which doesn't switch into modem mode.

[Martijn vdS (martijn)]

Hm, but that might be an old kernel. Will retry later.

[Ban (sven-waeyenbergh)]

I tried with both 2.6.27-9 and 2.6.27-7 (the only ones my updated 8.10 has)

these came with zerocd udev rule (i'm guessing from a package ?)

do you want me to try the one from -proposed or the jaunty one (or is that the same one ?)
i can re-try tonight but i'm on umts right now.

[Alexander Sack (asac)]

On Wed, Jan 21, 2009 at 01:12:57PM -0000, Ban wrote:
> I tried with both 2.6.27-9 and 2.6.27-7 (the only ones my updated 8.10
> has)
>
> these came with zerocd udev rule (i'm guessing from a package ?)
>
> do you want me to try the one from -proposed or the jaunty one (or is that the same one ?)
> i can re-try tonight but i'm on umts right now.
>

The idea is that userspace stuff isnt needed to not open the storage
device; kernel fixes have flowed into 2.6.28 (jaunty) and now into
2.6.29; just wanted to check whether your device is already fixed or
if we need to look around for cherry-picks from 2.6.29 development
tree.

So please check whether it works with 2.6.28 kernel out-of-box.

 - Alexander

[Martijn vdS (martijn)]

Jaunty doesn't seem to have option_ms.[ch]yet:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=tree;f=drivers/usb/storage;h=eb55e5f0a0a86d3b67610b6da7ee02c48626aa7a;hb=7c88cff7e3a5e14d83287e3111a8131358b0091d

Also, the one in kernel HEAD (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/usb/storage/unusual_devs.h;h=a7f9513fa19d984eda4a627124c448ee5f67cad7;hb=HEAD) doesn't list my device (0af0:6911, "Option Icon 7.2") as one of the "unusual_devs" to switch to modem mode.

[Ban (sven-waeyenbergh)]

i had a try with the latest Jaunty alpha livecd with what seems like interesting results:
it seems like the device gets recognised as usb storage first,
only the usb storage scan takes a while and meanwhile the modem gets detected,
then the storage gets mounted and the modem seems not usable, or at least i cant find device nodes
and network manager does not allow me to make a connection as it does in 8.10 with the hso driver/userspace blob
a subsequent pull-out/stick-in of the stick seems to trigger only the storage driver

this is dmesg covering initial stick-in/pull-out/stick-in:
[ 429.316100] usb 3-1: new full speed USB device using uhci_hcd and address 2
[ 429.481624] usb 3-1: configuration #1 chosen from 1 choice
[ 433.413371] Initializing USB Mass Storage driver...
[ 433.416464] scsi2 : SCSI emulation for USB Mass Storage devices
[ 433.416999] usbcore: registered new interface driver usb-storage
[ 433.417007] USB Mass Storage support registered.
[ 433.418311] usb-storage: device found at 2
[ 433.418316] usb-storage: waiting for device to settle before scanning
[ 433.542594] hso: /build/buildd/linux-2.6.28/drivers/net/usb/hso.c: 1.2 Option Wireless
[ 433.542653] usbcore: registered new interface driver hso
[ 438.417519] usb-storage: device scan complete
[ 438.420501] scsi 2:0:0:0: CD-ROM ZCOPTION HSDPA Modem 3.00 PQ: 0 ANSI: 2
[ 438.459439] sr1: scsi-1 drive
[ 438.459607] sr 2:0:0:0: Attached scsi CD-ROM sr1
[ 438.459717] sr 2:0:0:0: Attached scsi generic sg2 type 5
[ 441.694558] ISO 9660 Extensions: Microsoft Joliet Level 1
[ 441.700592] ISOFS: changing to secondary root
[ 1178.416150] usb 3-1: USB disconnect, address 2
[ 1203.708066] usb 3-1: new full speed USB device using uhci_hcd and address 3
[ 1203.873607] usb 3-1: configuration #1 chosen from 1 choice
[ 1203.875440] scsi3 : SCSI emulation for USB Mass Storage devices
[ 1203.876914] usb-storage: device found at 3
[ 1203.876919] usb-storage: waiting for device to settle before scanning
[ 1208.877393] usb-storage: device scan complete
[ 1208.880509] scsi 3:0:0:0: CD-ROM ZCOPTION HSDPA Modem 3.00 PQ: 0 ANSI: 2
[ 1208.916297] sr1: scsi-1 drive
[ 1208.916468] sr 3:0:0:0: Attached scsi CD-ROM sr1
[ 1208.916582] sr 3:0:0:0: Attached scsi generic sg2 type 5
[ 1211.681415] ISO 9660 Extensions: Microsoft Joliet Level 1
[ 1211.690418] ISOFS: changing to secondary root

the device concerned has the following usbid:
Bus 003 Device 003: ID 0af0:6971 Option

the hso driver remains loaded until stick is pulled
no device nodes to be found: no /dev/*hs* or /dev/*HS*

[Alexander Sack (asac)]

On Thu, Jan 22, 2009 at 09:40:17PM -0000, Ban wrote:
> i had a try with the latest Jaunty alpha livecd with what seems like interesting results:
> it seems like the device gets recognised as usb storage first,
> only the usb storage scan takes a while and meanwhile the modem gets detected,
> then the storage gets mounted and the modem seems not usable, or at least i cant find device nodes

Well, the modem is not detected. its just that the scsi device has
"Modem" in its name. Have you tried to use hso vs. option driver? In
jaunty hso driver supposely will prevent the usb storage mount.

 - Alexander

[Ban (sven-waeyenbergh)]

Well, the modem is not detected. its just that the scsi device has
> "Modem" in its name. Have you tried to use hso vs. option driver? In
> jaunty hso driver supposely will prevent the usb storage mount.
>

i don't agree. it's true that the scsi driver gets loaded, and that the
usbstorage device name includes "modem" in its name,
but if you look closely at the first initialisation you'll see:

[ 433.542594] hso: /build/buildd/linux-2.6.28/drivers/net/usb/hso.c: 1.2
Option Wireless
[ 433.542653] usbcore: registered new interface driver hso

that is actually the hso driver getting loaded.
it remains in lsmod as it should, but no /dev entries are created for the
modem
i'm assuming that is because the device is already hijacked by the
usbstorage driver.

positive is that the hso driver is loaded for my device as it should (not
the option driver)
but the prevention of the usb storage driver is not working, or at least not
for my usbid.
the usb storage gets mounted. no hso dev entries anywhere.

Ban

[Alexander Sack (asac)]

On Thu, Feb 19, 2009 at 11:18:20AM -0000, Ban wrote:
> Well, the modem is not detected. its just that the scsi device has
> > "Modem" in its name. Have you tried to use hso vs. option driver? In
> > jaunty hso driver supposely will prevent the usb storage mount.
> >
>
> i don't agree. it's true that the scsi driver gets loaded, and that the
> usbstorage device name includes "modem" in its name,
> but if you look closely at the first initialisation you'll see:
>
> [ 433.542594] hso: /build/buildd/linux-2.6.28/drivers/net/usb/hso.c: 1.2
> Option Wireless
> [ 433.542653] usbcore: registered new interface driver hso
>
> that is actually the hso driver getting loaded.
> it remains in lsmod as it should, but no /dev entries are created for the
> modem
> i'm assuming that is because the device is already hijacked by the
> usbstorage driver.
>
> positive is that the hso driver is loaded for my device as it should (not
> the option driver)
> but the prevention of the usb storage driver is not working, or at least not
> for my usbid.
> the usb storage gets mounted. no hso dev entries anywhere.

please try to patch the kernel with the patches from below thread (3
patches) and maybe add your device to the unusual devices (as the 3/3
patch does)

 https://lists.one-eyed-alien.net/pipermail/usb-storage/2009-January/004499.html
 https://lists.one-eyed-alien.net/pipermail/usb-storage/2009-January/004556.html

 - Alexander

[Alexander Sack (asac)]

On Mon, Mar 02, 2009 at 11:21:28AM -0000, Alexander Sack wrote:
>
> please try to patch the kernel with the patches from below thread (3
> patches) and maybe add your device to the unusual devices (as the 3/3
> patch does)
>
> https://lists.one-eyed-alien.net/pipermail/usb-storage/2009-January/004499.html
> https://lists.one-eyed-alien.net/pipermail/usb-storage/2009-January/004556.html
>
Any luck with this?

 - Alexander

[Martijn vdS (martijn)]

Alexander, could you provide a pre-built kernel with those patches?

[Damian Melniczuk (quantumdamage)]

Hi.
I have unknown modem from polish GSM operator "Era BlueConnect" identified by lsusb as " 0af0:6971 Option". I use program HSOconnect v. 1.1.82 2008-05-23.
I can start using modem, but some time after initialization and using it, it completely hang system.
I'm using Ubuntu 8.10 with "2.6.27-14-generic" kernel.

[Timo Aaltonen (tjaalton)]

I've installed jaunty on a machine that comes with a Option 0af0:7011 device. It uses option by default, but forcing hso doesn't seem to work.

[Timo Aaltonen (tjaalton)]

sorry, mine didn't load option, it just defaulted to mass-storage -mode, and I'm trying to come up with a patch to fix it.

[Laurent GUERBY (laurent-guerby)]

jaunty beta does not fix the issue.

When the key is plugged in it is recognized as usb-storage.

I installed rezero from

http://ppa.launchpad.net/martijn/ppa/ubuntu/pool/main/r/rezero/rezero_0.1-3_i386.deb

And after that install the key is recognized as modem and I get to setup the connection in network manager.

Why isn't rezero installed on jaunty?

[StefanHuszics (stefan-huszics)]

This bug seems to be a bit confusing likely because people are reporting status/issues of (at least) 2 completely different USB-modems.

0af0:6971 Option (aka GlobalTrotter Icon 255 Model: GI0255)
Works out of the box with Jaunty.

0af0:6911 Option (aka GlobalTrotter Icon 7.2 Model: GI0201 with updated flash)
This one is a big hassel to get working as it is identified as a storage device. Still requires rezero and jumping through hoops to get working in Jaunty.

Since the title of this bug is USB ID :6911 could people please post issues with OTHER USB modems in another bug and leave this bug for fixing of the still currently broken :6911? Thanks :)

For the coders, is there any output you still need for fixing this thing? I'll be happy to attach it. :)