FS#56825 - [linux]usb_modeswitch / udev stopped working with my USB 3G modem
Attached to Project:
Arch Linux
Opened by Razvan Cojocaru (rc) - Friday, 22 December 2017, 21:30 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 March 2022, 13:15 GMT
Opened by Razvan Cojocaru (rc) - Friday, 22 December 2017, 21:30 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 March 2022, 13:15 GMT
|
Details
I used to be able to just plug my USB 3G modem in and start
using it, but I haven't used it in a while and with an
up-to-date Arch Linux as of today, it doesn't work in a
plug-and-play manner anymore.
It works manually, by doing: usb_modeswitch -v 0x12d1 -p 1f1e -W -c /usr/share/usb_modeswitch/12d1\:1f1e But when I plug it in, by default this is what dmesg says: [ 41.507081] usb 1-1: new high-speed USB device number 6 using xhci_hcd [ 41.742244] usb-storage 1-1:1.0: USB Mass Storage device detected [ 41.742477] scsi host2: usb-storage 1-1:1.0 [ 41.742572] usbcore: registered new interface driver usb-storage [ 41.744630] usbcore: registered new interface driver uas [ 42.753253] scsi 2:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 42.754278] scsi 2:0:0:0: Attached scsi generic sg1 type 5 [ 42.768257] sr 2:0:0:0: [sr0] scsi-1 drive [ 42.768260] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 42.768426] sr 2:0:0:0: Attached scsi CD-ROM sr0 [ 47.003952] sr 2:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [ 47.003954] sr 2:0:0:0: [sr0] tag#0 Sense Key : 0x3 [current] [ 47.003955] sr 2:0:0:0: [sr0] tag#0 ASC=0x11 ASCQ=0x0 [ 47.003957] sr 2:0:0:0: [sr0] tag#0 CDB: opcode=0x28 28 00 00 00 63 fc 00 00 02 00 [ 47.003958] print_req_error: critical medium error, dev sr0, sector 102384 [ 47.003966] attempt to access beyond end of device The thing is then promptly being automounted (by Gnome, I assume), and that's the end of it (until I manually usb_modeswitch, at which point it starts working - although even then it show "Ethernet connected" in Gnome's GUI - it used to say "Mobile connection" or something of that sort). I'm running kernel 4.14.7-1-ARCH and usb_modeswitch 2.5.1-1. There's this, however. ● ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2017-12-22 22:18:53 EET; 1h 7min ago Main PID: 428 (ModemManager) Tasks: 3 (limit: 4915) CGroup: /system.slice/ModemManager.service └─428 /usr/bin/ModemManager Dec 22 22:18:53 t460 systemd[1]: Starting Modem Manager... Dec 22 22:18:53 t460 ModemManager[428]: <info> ModemManager (version 1.6.10) starting in system bus... Dec 22 22:18:53 t460 systemd[1]: Started Modem Manager. Dec 22 22:18:55 t460 ModemManager[428]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0': not supported by any plugin Dec 22 22:18:55 t460 ModemManager[428]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin Dec 22 22:21:24 t460 ModemManager[428]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin Dec 22 22:27:37 t460 ModemManager[428]: <info> (net/enp0s20f0u1): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1 Dec 22 23:03:49 t460 ModemManager[428]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2': not supported by any plugin Dec 22 23:07:38 t460 ModemManager[428]: <info> (net/enp0s20f0u2): released by modem /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2 Dec 22 23:09:59 t460 ModemManager[428]: <info> Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin NetworkManager is enabled and seems to be running fine. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Thursday, 03 March 2022, 13:15 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-02-27: A task closure has been requested. Reason for request: No response in years. Assuming fixed upstream.
Thursday, 03 March 2022, 13:15 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-02-27: A task closure has been requested. Reason for request: No response in years. Assuming fixed upstream.
Comment by Andreas Radke (AndyRTR) -
Tuesday, 10 December 2019, 10:17 GMT
Is this still an issue?