1. Please describe the problem: HP lt4132 (rebranded Huawei ME906s-158) doesn't work after update to 5.9 kernels. Observed on 5.9.8, 5.9.9, 5.9.10. Issue also exists on Fedora 32. Modem works on 5.8 kernels. Similar issue was created for ModemManager: https://bugzilla.redhat.com/show_bug.cgi?id=1901630 2. What is the Version-Release number of the kernel: 5.9.10-200.fc33.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes, it worked with 5.8 series kernels. I've confirmed it by installing and booting 5.8.18-300.fc33 kernel. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Use 5.9 series kernels. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Not tested. 6. Are you running any modules that not shipped with directly Fedora's kernel?: Virtualbox modules. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. [ 2.588316] usb 4-1.2: new high-speed USB device number 6 using xhci_hcd [ 2.671237] usb 4-1.2: New USB device found, idVendor=03f0, idProduct=a31d, bcdDevice= 1.02 [ 2.671239] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.671240] usb 4-1.2: Product: HP lt4132 LTE/HSPA+ 4G Module [ 2.671241] usb 4-1.2: Manufacturer: HP Inc. [ 2.671242] usb 4-1.2: SerialNumber: 0123456789ABCDEF [ 50.809515] usbserial: USB Serial support registered for GSM modem (1-port) [ 50.809536] snd_hda_intel 0000:04:00.6: enabling device (0000 -> 0002) [ 50.809665] option 4-1.2:2.2: GSM modem (1-port) converter detected [ 50.809766] usb 4-1.2: GSM modem (1-port) converter now attached to ttyUSB0 [ 50.809829] option 4-1.2:2.3: GSM modem (1-port) converter detected [ 50.809890] usb 4-1.2: GSM modem (1-port) converter now attached to ttyUSB1 [ 50.810866] option 4-1.2:2.4: GSM modem (1-port) converter detected [ 50.810942] usb 4-1.2: GSM modem (1-port) converter now attached to ttyUSB2 [ 50.812019] EDAC amd64: F17h_M10h detected (node 0). [ 50.812111] EDAC amd64: Node 0: DRAM ECC disabled. [ 50.812301] option 4-1.2:2.5: GSM modem (1-port) converter detected [ 50.812373] usb 4-1.2: GSM modem (1-port) converter now attached to ttyUSB3 [ 50.812431] option 4-1.2:2.6: GSM modem (1-port) converter detected [ 50.812482] usb 4-1.2: GSM modem (1-port) converter now attached to ttyUSB4 [ 51.857174] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 51.857211] option 4-1.2:2.2: device disconnected [ 51.858990] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [ 51.859009] option 4-1.2:2.3: device disconnected [ 51.859417] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [ 51.859431] option 4-1.2:2.4: device disconnected [ 51.859753] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [ 51.859767] option 4-1.2:2.5: device disconnected [ 51.860232] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4 [ 51.860247] option 4-1.2:2.6: device disconnected
works on 5.8.x doesn't work on 5.9.x (might work maybe 1 boot out of 20) works again on 5.10.0-0.rc4.20201119gitc2e7554e1b85.81.fc34.x86_64
still KO on 5.9.11-200.fc33.x86_64
still KO on kernel-core-5.9.12-200.fc33.x86_64
Sadly, still KO with 5.9.13-200.fc33.x86_64
Great news, it works with 5.9.14-200.fc33.x86_64 !
Still doesn't work for me (on 5.9.14-200.fc33.x86_64).
Yes sorry it was the 1 boot out of 20 that works. Still ko most of the time :-(
I've added this 3 lines ACTION=="add|change", SUBSYSTEM=="usb", ATTR{idVendor}=="03f0", ATTR{idProduct}=="a31d", ATTR{bConfigurationValue}!="3", ATTR{bConfigurationValue}:="0" ACTION=="add|change", SUBSYSTEM=="usb", ATTR{idVendor}=="03f0", ATTR{idProduct}=="a31d", ATTR{bConfigurationValue}!="3", RUN+="/bin/sh -c 'sleep 1; echo 3 > %S%p/bConfigurationValue'" ACTION=="add|change", SUBSYSTEM=="net", ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="a31d", ATTR{cdc_ncm/ndp_to_end}=="N", ATTR{cdc_ncm/ndp_to_end}:="Y" in /etc/udev/rules.d/hp-lt4132.rules and now it seems to work at every reboot (at least on 5.9.14-200.fc33.x86_64) source: https://toreanderson.github.io/2017/07/31/huawei-me906s-hp-lt4132-linux-ipv6.html
Still doesn't work with 5.10.6-200.fc33.x86_64.
Still doesn't work on 5.11 kernels.
*** Bug 1901630 has been marked as a duplicate of this bug. ***
Still doesn't work on 5.12 kernel.
Still doesn't work on 5.13 kernel.
And the above work around does not work for you?
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.