Lucid: hotplugging Huawei E220 doesn't load 'option' module

[Pedro Francisco]

On Lucid Lynx, if I hotplug my Huawei E220 only the usbstorage module is loaded. I need to modprobe option manually for it to work.
If I plug it before booting Linux it works fine out-of-the-box.

NOTE: the initial bug message mentioned harddisk failing to mount, which was caused by https://bugs.launchpad.net/oem-priority/+bug/548513 , which is now fixed.

[Sebastian Bator (eremit7)]

The same for my Huawei E220, works if plugged in before boot, but not hotpluged. This is a regression after karmic.

[Sebastian Bator (eremit7)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 1317 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,104382a1,00100101'
   Controls : 13
   Simple ctrls : 8
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 ppp0 no wireless extensions.
MachineType: ASUSTeK Computer INC. 701
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=caa48be3-4fb5-4873-a114-07710157c454 ro splash
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: eeepc-wlan: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: lucid ubuntu-une regression-potential needs-upstream-testing
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/03/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0910
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 701
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 701
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[Sebastian Bator (eremit7)]

apport information

[jpr (jprouffy)]

Hi, I have the same problem ( plug in just before boot) but with another problem :
When I have an mass storage (HD or usb) and I want unmount the mass storage with right click "unmount"
the icon of my connection and the connection disappear and I can no more connect I mus restart the computer.

[Pedro Francisco (pedrogfrancisco)]

Can someone confirm this has been fixed?

@jpr I'm sorry, can't tell you what's wrong, try the forums and if no-one replies nor can't solve it, open _another_ bug.

[Sebastian Bator (eremit7)]

No, it's still an issue for me.

[Timo Jyrinki (timo-jyrinki)]

What about now? I borrowed one E220 and it's working fluently for me in 10.04 LTS, with and without usb-modeswitch being installed (reboot in between). It also connected both when attached after boot or before boot (before boot only tested without usb-modeswitch).

In each case, option module seems to be loaded automatically. Can people confirm the fix? ...and maybe someone found out where something was changed so this got fixed?

USB id is 12d1:1003. I wonder if there are multiple Huawei E220 revisions around or something else that would explain this.

[Pedro Francisco (pedrogfrancisco)]

The problem only occurs if you plug-in the dongle after boot. Plugging before works as intended.
I though it had been fixed but for me it isn't as well.

$ lsmod |grep -i option
(none)

$ dmesg
[ 138.004084] usb 5-2: new full speed USB device using uhci_hcd and address 2
[ 138.163216] usb 5-2: configuration #1 chosen from 1 choice
[ 138.245183] Initializing USB Mass Storage driver...
[ 138.256039] scsi5 : SCSI emulation for USB Mass Storage devices
[ 138.256196] usbcore: registered new interface driver usb-storage
[ 138.256200] USB Mass Storage support registered.
[ 138.283620] usb-storage: device found at 2
[ 138.283624] usb-storage: waiting for device to settle before scanning
[ 138.288085] usb 5-2: USB disconnect, address 2
[ 139.024072] usb 5-2: new full speed USB device using uhci_hcd and address 3
[ 139.187302] usb 5-2: configuration #1 chosen from 1 choice
[ 139.206161] scsi8 : SCSI emulation for USB Mass Storage devices
[ 139.206405] usb-storage: device found at 3
[ 139.206409] usb-storage: waiting for device to settle before scanning
[ 144.206302] usb-storage: device scan complete
[ 144.209223] scsi 8:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2
[ 144.234298] sr1: scsi-1 drive
[ 144.235409] sr 8:0:0:0: Attached scsi CD-ROM sr1
[ 144.238269] sr 8:0:0:0: Attached scsi generic sg2 type 5

$ lsusb
Bus 005 Device 003: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem

NO modeswitch here.

[Ivan (freeazy)]

hello, I had the same problem on my E220, and then I update E220 firmware to v11117100399 (via windows) and the problem disappeared! I freely plug/unplug every time and still can connect without rebooting first.

[Christian González (droetker)]

Anyone hints how to fix this?

[Christian González (droetker)]

ivan90112, could you tell us how you upgraded the modem? I was not able to do this - the device was not found by the upgrade installer in Windows.
Where did you get the upgrade from?

[Filippo Argiolas (fargiolas)]

Just for the sake of completeness, I have this very same dongle and networkmanager doesn't seem to see it neither in 9.10 nor 10.04 but the same dongle works flawlessly on Fedora 13.
So the issue is not in the firmware, it's either in some ubuntu specific patch or some (mis)configuration (well fedora could also have some downstream patch that fixes the same issue too).

[^rooker (rooker)]

Is there any update on this issue?

[Seth Forshee (sforshee)]

@Pedro: The apport information you attached shows that the option module is loaded. Could you collect the information after plugging in the dongle when the option module does not get loaded? Please run 'apport-collect 565058' to add the data to this bug report.

Can you verify that you have the usb-modeswitch and usb-modeswitch-data packages installed? If not, please install these packages and see if they fix your issue.

If things still don't work, it would help if you could also do the following. These instructions apply to lucid; things are a little different in maverick.

Edit /lib/udev/usb_modeswitch and change the line

  set logging 0

to

  set logging 1

Capture the output of 'udevadm monitor --property' while you plug in the dongle. After the dongle is plugged in, capture output of 'lsusb -v' with the dongle plugged in. Please provide the output of these commands along with any /var/log/usb_modeswitch_* files that are present.

[Pedro Francisco (pedrogfrancisco)]

I'm on 10.10 now which doesn't have the problem anymore. Unmarking "this bug affects me".

[Seth Forshee (sforshee)]

Anyone else affected by this problem able to test?

My primary interest at this point is whether not having the usb-modeswitch and usb-modeswitch-data packages installed are behind this problem. I performed a clean lucid install and found that these packages are not installed by default.

[Bartosz Kosiorek (gang65)]

I have also affected by this bug:
When I have plugged my E220 modem during Ubuntu startup it is OK.
When I try to hotplug Huawei E220 it doesn't connect. Sometimes it need several E220 disconnect/connect to start working.

I have also very poor signal quality. Thats why it disconnect frequently. After that I cannot connect to network. If I disconnect/connect E220 it starts works again.

?field.comment=I have also affected by this bug:
When I have plugged my E220 modem during Ubuntu startup it is OK.
When I try to hotplug Huawei E220 it doesn't connect. Sometimes it need several E220 disconnect/connect to start working.

I have also very poor signal quality. Thats why it disconnect frequently. After that I cannot connect to network. If I disconnect/connect E220 it starts works again.

[Bartosz Kosiorek (gang65)]

I cannot do "apport-collect 565058" after plugin because I haven't got internet access.

I have already installed the usb-modeswitch and usb-modeswitch-data packages.

[Seth Forshee (sforshee)]

@Bartosz, thanks for the data, it is extremely helpful.

The mode switch is happening, but the ttyUSB* devices don't seem to be appearing. I can't tell why they aren't appearing though. Can you run the following commands and attach all the .log files produced? Please run them when the modem is plugged in but not working.

$ uname -a > uname-a.log
$ cat /proc/version_signature > version.log
$ dmesg > dmesg.log
$ lsmod > lsmod.log
$ grep 'usb:v12D1p1003' /lib/modules/`uname -r`/modules.alias > modules-alias.log

Thanks again for your help.

[Seth Forshee (sforshee)]

@Bartosz:

With the above, could you also do the following?

$ sudo udevadm control --log-priority=debug
$ tail -f /var/log/syslog | grep udev | tee syslog-udev.log
$ # Plug in modem, wait for output to stop, then exit with ctrl-C
$ sudo udevadm control --log-priority=err

Then attach syslog-udev.log.

[Seth Forshee (sforshee)]

@Bartosz:

Are all of the latest batch of logs captured from the same modem insertion? From looking at syslog-udev.log it would appear that everything worked correctly, but lsmod.log does shows that the option or usbserial modules aren't loaded.

If you captured them from different instances of inserting the modem, please capture another syslog-udev.log when the modem does not work.

Could you also provide the output of '/sbin/modprobe --show-depends usb:v12D1p1003d0000dc00dsc00dp00icFFiscFFipFF'?

Thanks!

[Bartosz Kosiorek (gang65)]

It's start working :-(
I couldn't reproduce it (I checked five times and every time it connects to network).
Maybe couse is the signal strength (in night it is stronger), and that's why it working. I will check tommorow and let you know.

[Seth Forshee (sforshee)]

@Bartosz, I wouldn't be surprised to find that if it works once it will continue working as long as the computer isn't rebooted, since the option and usbserial modules will remain loaded. You can use 'sudo modprobe -r option usbserial' to remove the modules without rebooting.

[Manfred Hampl (m-hampl)]

I am on Ubuntu 10.10 using a Huawei E160 USB modem and experience the same bug. (Note that in lsusb the E160 is shown as 12d1:1003 and is named E220/E270, so apparently it is technically identical to the E220.)

If I have my device plugged in when booting, it shows up in the network manager applet ready for use.
If I plug it in only after booting, I have to manually issue the 'modprobe option' command to get it working.

I have both usb-modeswitch and usb-modeswitch-data installed, but I did not see any effect on said behavior with manually running usb-modeswitch.

What I have found out respectively can confirm so far:
If I have the device plugged in at boot time, among others the modules usb_storage, option, usb_wwan and usbserial are loaded.
If I plug in the device later, only the usb_storage module gets loaded, any only with the command "modprobe option" the other three modules (option, usb_wwan and usbserial) get loaded, to achieve the same list of loaded modules as when booting with the device already connected.

If it helps I can attach all data similar to those Bartosz has sent or any other system output if requested.

uname -a:
Linux burkhard-desktop 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:48 UTC 2011 i686 GNU/Linux

cat /proc/version_signature:
Ubuntu 2.6.35-25.44-generic 2.6.35.10

lsb_release -a:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick

[Andy Whitcroft (apw)]

Could you capture the output of udevadm monitor while inserting the stick after boot please. You can do that by running the command below in a terminal window, and attaching the UDEV-TRACE file to this bug. Thanks.

    udevadm monitor >UDEV-TRACE

You will need to run the command before insertion, insert the device, wait 30s or so for everything to occur, then hit control-C.

[Manfred Hampl (m-hampl)]

Attached the output of
udevadm monitor
udevadm monitor --property
dmesg
from one session where I plugged in the device some minutes after booting. The logs contain also the effects of issuing 'sudo modprobe option' about a minute later - manually separated by a string of ++++++++++++.

If there is anything I can provide in addition to this please feel free to ask.

[Seth Forshee (sforshee)]

@Manfred, thank you for the traces. They show that the modeswitch completes successfully, the modem device appears, and udev receives events for the modem, but the option module still isn't loaded for some reason. I can't tell why it isn't loaded however. To help determine the cause, can you perform the same steps as before (only the output of 'udevadm monitory --property' is needed) and also include the syslog-udev.log file from the following commands.

$ sudo udevadm control --log-priority=debug
$ tail -f /var/log/syslog | grep udev | tee syslog-udev.log

Plug in modem, wait for the output to stop, then exit with ctrl-C and run

$ sudo udevadm control --log-priority=err

Make sure that the logs are from an instance where the options module is not loaded (you will probably either need to reboot or manually unload the options module). Also make sure both logs are from the same event, as this will allow us to correlate the events from the two logs together.

Thanks!

[Manfred Hampl (m-hampl)]

@Seth: Very strange thing. It feels like "until yesterday it has always failed, and today when I want it to fail, it works."
I wanted to create the trace files as asked for, but out of a sudden whenever I plug my USB device in now, the option module gets loaded. Whatever I do, plugging in the device after booting works now, and I have rebooted already five times, I have manually unloaded option module etc.etc. I will try again tomorrow and hope that it will fail again at least once.

[Seth Forshee (sforshee)]

@Manfred:

Okay, thanks for testing. The commands I gave you enable some extra logging in udev, making me suspicious that this is somehow timing-related, as Bartosz seemed to have similar results. If you don't try to collect syslog-udev.log, does it start failing? (The command 'sudo udevadm control --log-priority=debug' enables the extra logging, and --log-priority=err resets it back to the default, so if you want to you could play around with those and see if they affect the results)

[Bartosz Kosiorek (gang65)]

To reproduce this problem again turn off debug login 'sudo udevadm control --log-priority=debug', turn off the computer and wait couple of hours.

Simply turn off/turn on computer, could be not unsufficient (Don't ask me why).

[Seth Forshee (sforshee)]

@Bartosz, am I to understand that you're never able to get the module load to fail with --log-priority=err?

[Bartosz Kosiorek (gang65)]

@Seth, Yes. It seems it is starts working only after set "--log-priority=debug"

@Manfred: Do you have the same issues?

[Manfred Hampl (m-hampl)]

Current status on my machine:
In the past two days I was not able to see the error any more, i.e. when plugging in the device after boot the option module did always load. No difference with and without extended logging. I will try more during the coming weekend.

One remark: Just compared the log files from Feb 14 above (not loading) with what I think I remember seeing on screen yesterday: when manually issuing the "modprobe option" command there was only ttyUSB0 and ttyUSB1; when it works automatically I get ttyUSB0, ttyUSB1, ttyUSB2 and ttyUSB3? I will try to dig into that the coming days and promise to come back.

[Sebastian Bator (eremit7)]

Apparently this bug does occur no longer.

Feel free to reopen.