[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#634916: marked as done (Linux modeswitches some 3G dongles in kernelland (duplicates userland functionality))

Your message dated Thu, 1 May 2025 13:30:52 +0200
with message-id <[🔎] aBNbbFQ_nBxZGoUC@eldamar.lan>
and subject line Re: Bug#634916: usb-modeswitch: seems to have no effect on Huawei E169
has caused the Debian Bug report #634916,
regarding Linux modeswitches some 3G dongles in kernelland (duplicates userland functionality)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
634916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634916
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: usb-modeswitch
Version: 1.1.8-1
Severity: normal

Hello!

I installed usb-modeswitch in order to prevent my USB HSDPA modem to be
seen as a storage device.
My modem is a Huawei E169, which has apparently the same vendor and
product IDs as the Huawei E620:

  $ lsusb | grep Huawei
  Bus 006 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

It seems to me that this device is known to usb-modeswitch-data:

  $ grep -A 1 E169 /lib/udev/rules.d/40-usb_modeswitch.rules
  # Huawei E169
  ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="usb_modeswitch '%b/%k'"

Well, if I plug the USB modem into a USB port, I get the following
relevant /var/log/syslog lines:

  kernel: [48971.464031] usb 6-1: new full speed USB device number 2 using uhci_hcd
  kernel: [48971.626112] usb 6-1: New USB device found, idVendor=12d1, idProduct=1001
  kernel: [48971.626115] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=1
  kernel: [48971.626117] usb 6-1: Product: HUAWEI Mobile
  kernel: [48971.626119] usb 6-1: Manufacturer: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
  kernel: [48971.626121] usb 6-1: SerialNumber: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
  udevd[28725]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1 6 2': No such file or directory
  kernel: [48972.175513] usbcore: registered new interface driver uas
  kernel: [48972.204572] Initializing USB Mass Storage driver...
  kernel: [48972.207123] scsi4 : usb-storage 6-1:1.0
  kernel: [48972.207285] usbcore: registered new interface driver usb-storage
  kernel: [48972.207287] USB Mass Storage support registered.
  kernel: [48972.216084] usb 6-1: USB disconnect, device number 2
  kernel: [48972.952054] usb 6-1: new full speed USB device number 3 using uhci_hcd
  kernel: [48973.116093] usb 6-1: New USB device found, idVendor=12d1, idProduct=1001
  kernel: [48973.116096] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=1
  kernel: [48973.116099] usb 6-1: Product: HUAWEI Mobile
  kernel: [48973.116101] usb 6-1: Manufacturer: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
  kernel: [48973.116103] usb 6-1: SerialNumber: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
  udevd[28744]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1 6 3': No such file or directory
  kernel: [48973.127105] scsi8 : usb-storage 6-1:1.3
  kernel: [48973.166893] usbcore: registered new interface driver usbserial
  kernel: [48973.167822] USB Serial support registered for generic
  kernel: [48973.168839] usbcore: registered new interface driver usbserial_generic
  kernel: [48973.168842] usbserial: USB Serial Driver core
  kernel: [48973.194559] USB Serial support registered for GSM modem (1-port)
  kernel: [48973.195691] option 6-1:1.0: GSM modem (1-port) converter detected
  kernel: [48973.196452] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB0
  kernel: [48973.196469] option 6-1:1.1: GSM modem (1-port) converter detected
  kernel: [48973.200295] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB1
  kernel: [48973.200320] option 6-1:1.2: GSM modem (1-port) converter detected
  kernel: [48973.200572] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB2
  kernel: [48973.201001] usbcore: registered new interface driver option
  kernel: [48973.201004] option: v0.7.2:USB Driver for GSM modems
  kernel: [48974.131117] scsi 8:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
  kernel: [48974.134133] scsi 8:0:0:1: Direct-Access     HUAWEI   SD Storage       2.31 PQ: 0 ANSI: 2
  kernel: [48974.147102] sr1: scsi-1 drive
  kernel: [48974.147238] sr 8:0:0:0: Attached scsi CD-ROM sr1
  kernel: [48974.147317] sr 8:0:0:0: Attached scsi generic sg2 type 5
  kernel: [48974.147460] sd 8:0:0:1: Attached scsi generic sg3 type 0
  kernel: [48974.189119] sd 8:0:0:1: [sdb] Attached SCSI removable disk

This seems to mean that the device is seen as both a USB modem and
a USB mass storage / CD-ROM device.

Indeed:

  $ ls -altrF /dev/ttyU* /dev/sg[23] /dev/sdb* /dev/sr1 /dev/scd1 /dev/cdrom4
  crw-rw---- 1 root dialout 188,  1 Jul 20 22:44 /dev/ttyUSB1
  crw-rw---- 1 root dialout 188,  2 Jul 20 22:44 /dev/ttyUSB2
  crw-rw---- 1 root dialout 188,  0 Jul 20 22:44 /dev/ttyUSB0
  crw-rw---- 1 root cdrom    21,  2 Jul 20 22:44 /dev/sg2
  crw------- 1 root root     21,  3 Jul 20 22:44 /dev/sg3
  brw-rw---- 1 root floppy    8, 16 Jul 20 22:44 /dev/sdb
  brw-rw---- 1 root cdrom    11,  1 Jul 20 22:45 /dev/sr1
  lrwxrwxrwx 1 root root          3 Jul 20 22:45 /dev/scd1 -> sr1
  lrwxrwxrwx 1 root root          3 Jul 20 22:45 /dev/cdrom4 -> sr1

exactly as when I tried *before* installing usb-modeswitch !

I expected to only see /dev/ttyUSB* files.

What's wrong?
What did I fail to understand?

Please help and/or clarify and/or fix the issue.
Thanks for your time!


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages usb-modeswitch depends on:
ii  dpkg                         1.16.0.3    Debian package management system
ii  libc6                        2.13-7      Embedded GNU C Library: Shared lib
ii  libusb-0.1-4                 2:0.1.12-17 userspace USB programming library
ii  tcl                          8.5.0-2     The Tool Command Language (default
ii  tcl8.5 [tclsh]               8.5.10-1    Tcl (the Tool Command Language) v8
ii  usb-modeswitch-data          20110619-1  mode switching data for usb-modesw

usb-modeswitch recommends no packages.

Versions of packages usb-modeswitch suggests:
pn  comgt                         <none>     (no description available)
pn  wvdial                        <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

On Thu, Aug 11, 2011 at 10:57:24AM +0200, Didier Raboud wrote:
> reassign 634916 src:linux-2.6 3.0.0-1
> retitle 634916 Linux modeswitches some 3G dongles in kernelland (duplicates userland functionality)
> thanks
> 
> Dear linux-2.6 maintainers, 
> 
> I'm hereby re-assigning the #634916 bug to the Linux kernel, as per the
> discussion held with Josua Dietze, the usb-modeswitch upstream developer.
> 
> In summary: the Linux kernel "modeswitches" some 3G dongles where
> usb-modeswitch is supposed to be the userland tool doing this. Having this
> behaviour hardcoded in Linux implies less flexibility and duplicates
> a functionality already present in userland _today_.
> 
> Please ask if you need more information, cheers, 

I have re-read the full bug today to do some BTS clean-up for
src:linux and given there was not further action to "address" this in
upstream I think it's time to close the bug.

AFAIU, in kernel mode switching is deprecated years ago, so I do not
expect development in that part of the code anymore and that devices
falling in this class will fade out as well.

Federico, I'm sorry you had to wait that long. If you feel strong
about the issue I suggest to re-forward it to the upstream list
including Josua, and see if there is still some interest in adressing
this misbehaviour.

My udnerstanding is that there is as well not major harm caused by
this.

I will thus close the bug with this explanation, keeping Josua as well
in the loop in case he now disagrees.

Regards,
Salvatore

--- End Message ---
Reply to: