Dies ist in gewisser Weise die Fortsetzung meiner früheren Beiträge
https://forum.ubuntuusers.de/topic/unerkanntes-xinxun-modem/
und
https://forum.ubuntuusers.de/topic/netzwek-zugang-mit-qualcomm-modem/
aber unter neuen Gesichtspunkten. Ich habe inzwischen weiter gesucht im Internet und es gibt da ein weit verbreitetes Problem mit Modems, die von skrupellosen Händlern vom Hersteller (Qualcomm) gekauft werden und dann eigentlich bei der USB Organisation mit einer vemdor ID registriert werden müssten. Das kostet Geld und darum verhökern diese Händler das ohne diese Registrierung und damit findet das auch keine Aufnahme in die Linux Daten Basis. Die haben einen Windows Treiber eingebaut, und das war es dann auch. Es gibt eine ausführliche Diskussion darüber hier:
Das Problem liegt vor allem darin, dass der modeswitch zwar durchgeführt wird, aber das System weiß dann nicht weiter. Sehr viele verschiedene chipsets laufen unter der vendor ID 6000. Es gibt dafür keine allgemein gültige Lösung.
Nach dem Debakel in den oben genannten Beiträgen habe ich zwangsläufig noch so ein Modem kaufen müssen, mit dem gleichen Problem, es gibt hier nichts anderes. Aber es scheint ein anderer chipset zu sein. Es nennt sich LTE 4G USB.
Dann habe ich entdeckt, in der usb_modeswitch.conf Konfigurationsdatei kann man
EnableLogging=1
aktivieren. Dadurch kann man den modeswitch Prozess verfolgen in der Ausgabedateien:
"usb_modeswitch_1-2":
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 | USB_ModeSwitch log from Tue Nov 08 09:31:49 EAT 2022 Raw parameters: --switch-mode 1-2 Use global config file: /etc/usb_modeswitch.conf Use global config file: /etc/usb_modeswitch.conf Use top device dir /sys/bus/usb/devices/1-2 Check class of first interface ... Interface class is 08. ---------------- USB values from sysfs: manufacturer Qualcomm, Incorporated product Qualcomm CDMA Technologies MSM serial 1234567890ABCDEF ---------------- bNumConfigurations is 1 - don't check for active configuration Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz ConfigList: pack/05c6:f000 pack/ SCSI attributes not needed, move on Check config: pack/05c6:f000 ! matched. Read config data Extract config 05c6:f000 from collection /usr/share/usb_modeswitch/configPack.tar.gz Note: Using generic manufacturer configuration for "linux" Command line: usb_modeswitch -W -D -u -1 -b 1 -g 39 -v 05c6 -p f000 -f $flags(config) Verbose debug output of usb_modeswitch and libusb follows (Note that some USB errors are to be expected in the process) -------------------------------- Read long config from command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.6.1 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0xf000 TargetVendor= 0x05c6 TargetProductList="0016,6000,9000" StandardEject=1 MessageContent="5553424308306384c000000080000671030000000000000000000000000000" System integration mode enabled Use given bus/device number: 001/039 ... Look for default devices ... bus/device number matched found USB ID 05c6:f000 vendor ID matched product ID matched Found devices in default mode (1) Get the current device configuration ... Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) ------------------------- Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: 1234567890ABCDEF ------------------------- Sending standard EJECT sequence Looking for active drivers ... OK, driver detached Set up interface 0 Use endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Read the response to message 1 (CSW) ... Response successfully read (13 bytes), status 0 Trying to send message 2 to endpoint 0x01 ... OK, message successfully sent Read the response to message 2 (CSW) ... Response successfully read (13 bytes), status 0 Trying to send message 3 to endpoint 0x01 ... OK, message successfully sent Read the response to message 3 (CSW) ... Response successfully read (13 bytes), status 1 Trying to send message 4 to endpoint 0x01 ... OK, message successfully sent Read the response to message 4 (CSW) ... Response successfully read (13 bytes), status 1 Trying to send message 5 to endpoint 0x01 ... OK, message successfully sent Read the response to message 5 (CSW) ... Response successfully read (13 bytes), status 0 Reset response endpoint 0x81 Reset message endpoint 0x01 Device is gone, skip any further commands ok:busdev -------------------------------- (end of usb_modeswitch output) Check success of mode switch for max. 20 seconds ... Read attributes ... All attributes matched Mode switching was successful, found 05c6:6000 (Qualcomm, Incorporated: Qualcomm CDMA Technologies MSM) Logger is /usr/bin/logger Serial USB driver bound to interface 0 will try to guess and symlink modem port on next connect Check for AVOID_RESET_QUIRK kernel attribute AVOID_RESET_QUIRK activated All done, exit |
und auch in
"usb_modeswitch_ttyUSB_1-2:1.0"
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | USB_ModeSwitch log from Tue Nov 08 09:31:51 EAT 2022 Raw parameters: --symlink-name /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0 Use global config file: /etc/usb_modeswitch.conf Use global config file: /etc/usb_modeswitch.conf My name is ttyUSB0 Check my endpoints ... in /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0 check ep_81 ... ep_81 has interrupt transfer type --> I am an interrupt port --> No interrupt interface below me Return symlink name "gsmmodem3" and exit |
Das läuft nach dem Einstecken des Modems ab und am Ende kommt eine Meldung:
Qualcomm CDMA Technologies MSM konnte nicht eingehängt werden MTP-Gerät "001,039" kann nicht geöffnet werden
Das läßt bei mir die Vermutung aufkommen, es könnte sich um ein Problem mit der Zugangsberechtigung handeln. Ist es für eine Modem normal als MTP Gerät eingehängt zu werden?
Hier noch ein paar weitere Abfragen:
1 2 3 4 5 6 7 8 9 | yx@yx-HP:~$ lsusb Bus 002 Device 002: ID 152d:1337 JMicron Technology Corp. / JMicron USA Technology Corp. jmicron Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 013: ID 05c6:6000 Qualcomm, Inc. Siemens SG75 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub yx@yx-HP:~$ |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 | yx@yx-HP:~$ usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 7 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.15 S: Manufacturer=Linux 5.15.0-25-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=0000:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 13 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=05c6 ProdID=6000 Rev=00.00 S: Manufacturer=Qualcomm, Incorporated S: Product=Qualcomm CDMA Technologies MSM S: SerialNumber=1234567890ABCDEF C: #Ifs= 5 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=2ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms E: Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 4 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 6 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=05.15 S: Manufacturer=Linux 5.15.0-25-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=0000:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0 D: Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1 P: Vendor=152d ProdID=1337 Rev=05.08 S: Manufacturer=jmicron S: Product=jmicron S: SerialNumber=7F833EEF5DC0 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=896mA I: If#= 0 Alt= 1 #EPs= 4 Cls=08(stor.) Sub=06 Prot=62 Driver=uas E: Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms yx@yx-HP:~$ |
1 2 3 4 5 6 7 8 9 10 11 12 | yx@yx-HP:~$ lsblk -lf /dev/sd? NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda sda1 vfat FAT32 FF97-4E77 505,8M 1% /boot/efi sda2 ext4 1.0 a23ae266-1f69-4916-a7be-b711e9cd3bbd sdb sdb1 ext4 1.0 dasi 9ec1982e-9d9a-4320-ac54-8ae8716680e5 125,5G 40% /media/yx/dasi sdb2 sdb5 vfat FAT32 963B-AE64 46,3M 0% /media/yx/963B-AE64 sdb6 ext4 1.0 52dae4af-7c56-4115-a7c2-b42971f9d6f5 113,9G 45% / sdc yx@yx-HP:~$ |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | yx@yx-HP:~$ lsmod | grep -e option -e usb btusb 57344 0 option 61440 0 btrtl 24576 1 btusb usb_wwan 24576 1 option btbcm 20480 1 btusb btintel 40960 1 btusb usbserial 57344 2 usb_wwan,option bluetooth 688128 43 btrtl,btintel,btbcm,bnep,btusb,rfcomm intel_xhci_usb_role_switch 16384 0 usbhid 65536 0 hid 147456 2 usbhid,hid_generic usb_storage 77824 1 uas yx@yx-HP:~$ |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 | yx@yx-HP:~$ sudo dmesg | grep -i -e option -e usb [sudo] Passwort für yx: [ 0.290693] ACPI: PM: Power Resource [USBC] [ 0.373867] ACPI: bus type USB registered [ 0.373867] usbcore: registered new interface driver usbfs [ 0.373867] usbcore: registered new interface driver hub [ 0.373867] usbcore: registered new device driver usb [ 0.552876] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.552982] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.553065] uhci_hcd: USB Universal Host Controller Interface driver [ 3.057821] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 [ 3.070653] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [ 3.072558] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.074493] usb usb1: Product: xHCI Host Controller [ 3.076336] usb usb1: Manufacturer: Linux 5.15.0-25-generic xhci-hcd [ 3.078180] usb usb1: SerialNumber: 0000:00:14.0 [ 3.093948] hub 1-0:1.0: USB hub found [ 3.123512] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 3.125255] xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed [ 3.138144] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15 [ 3.139922] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.141651] usb usb2: Product: xHCI Host Controller [ 3.141656] usb usb2: Manufacturer: Linux 5.15.0-25-generic xhci-hcd [ 3.141658] usb usb2: SerialNumber: 0000:00:14.0 [ 3.145731] hub 2-0:1.0: USB hub found [ 3.449660] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 3.635162] usb 1-1: New USB device found, idVendor=05c6, idProduct=6000, bcdDevice= 0.00 [ 3.645154] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4 [ 3.653505] usb 1-1: Product: Qualcomm CDMA Technologies MSM [ 3.659958] usb 1-1: Manufacturer: Qualcomm, Incorporated [ 3.666349] usb 1-1: SerialNumber: 1234567890ABCDEF [ 3.760134] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd [ 3.803183] usb 2-2: New USB device found, idVendor=152d, idProduct=1337, bcdDevice= 5.08 [ 3.805619] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.807951] usb 2-2: Product: jmicron [ 3.810257] usb 2-2: Manufacturer: jmicron [ 3.812506] usb 2-2: SerialNumber: 7F833EEF5DC0 [ 3.929581] usb 1-3: new low-speed USB device number 3 using xhci_hcd [ 4.081623] usb 1-3: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00 [ 4.081646] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.081653] usb 1-3: Product: USB Optical Mouse [ 4.081658] usb 1-3: Manufacturer: Logitech [ 4.209689] usb 1-5: new high-speed USB device number 4 using xhci_hcd [ 4.368222] usb 1-5: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=88.32 [ 4.368231] usb 1-5: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 4.368234] usb 1-5: Product: USB2.0 Hub [ 4.370147] hub 1-5:1.0: USB hub found [ 4.390143] usb-storage 1-1:1.4: USB Mass Storage device detected [ 4.390490] scsi host2: usb-storage 1-1:1.4 [ 4.390709] usbcore: registered new interface driver usb-storage [ 4.404782] usbcore: registered new interface driver uas [ 4.661920] usb 1-5.3: new full-speed USB device number 5 using xhci_hcd [ 4.765169] usb 1-5.3: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [ 4.765203] usb 1-5.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.653064] usbcore: registered new interface driver usbhid [ 5.657939] usbhid: USB HID core driver [ 5.681059] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C077.0001/input/input6 [ 5.690921] hid-generic 0003:046D:C077.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-3/input0 [ 33.551355] usbcore: registered new interface driver usbserial_generic [ 33.551635] usbserial: USB Serial support registered for generic [ 33.699813] usbcore: registered new interface driver option [ 33.706588] usbserial: USB Serial support registered for GSM modem (1-port) [ 33.706669] option 1-1:1.0: GSM modem (1-port) converter detected [ 33.709410] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 [ 33.709522] option 1-1:1.1: GSM modem (1-port) converter detected [ 33.709779] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 [ 33.709858] option 1-1:1.2: GSM modem (1-port) converter detected [ 33.710488] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 [ 33.710584] option 1-1:1.3: GSM modem (1-port) converter detected [ 33.711009] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3 [ 33.779283] usbcore: registered new interface driver btusb yx@yx-HP:~$ |
1 2 3 | yx@yx-HP:~$ mmcli -L /org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] 0 yx@yx-HP:~$ |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | yx@yx-HP:~$ mmcli -m 0 ----------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: db8611bf327807af3e19db1895ce77e328fd5b27 ----------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MDM9K-QXWL-U-3M_LTE_V12.1 1 [Jan 19 2012 21:00:00] | supported: gsm-umts | current: gsm-umts | equipment id: 861179036479053 ----------------------------- System | device: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1 | drivers: option | plugin: generic | primary port: ttyUSB0 | ports: ttyUSB0 (at), ttyUSB1 (at), ttyUSB3 (qcdm) ----------------------------- Status | state: failed | failed reason: sim-missing | power state: on | signal quality: 0% (cached) ----------------------------- Modes | supported: allowed: any; preferred: none | current: allowed: any; preferred: none yx@yx-HP:~$ |
Hier ist interessant, es wird offensichtlich als Modem erkannt, der "option" Treiber wird zugeordnet und unter "Status" wird "sim-missing" angezeigt, dies sowohl mit als auch ohne eingelegte SIM. Auch GUI-modemmanager zeigt nun das Qualcomm Modem an, aber mit dem Hinweis :
"Das Modem ist nicht betriebsbereit. Bitte warten Sie, während das Modem vorbereitet wird..."
Ich habe den Eindruck, das Problem ist lösbar, aber wie, ist es eine Frage der Zugangsberechtigung?
