# Mc74xx chip is not detecting in kernel 5.10 but its get detected in 4.9

**URL:** <https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249>\
**Category:** IoT Modules\
**Created:** [November 2, 2022, 6:39am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249 "2022-11-02T06:39:27Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Murugan.SathishRam](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Murugan.SathishRam](https://forum.sierrawireless.com/u/Murugan.SathishRam)\
**Post date:** [November 2, 2022, 6:39am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/1 "2022-11-02T06:39:27Z")

</div>

We are trying to update kernel version in out IOT product from 4.9 to 5.10.9. Sierra modem wireless works fine in kernel 4.9 however in kernel 5.10, its not detecting.

New kernel output  
xxx:~# lsusb  
Bus 002 Device 002: ID 0424:3503 Microchip Technology, Inc. (formerly SMSC)  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub.

old kernel ouptut:  
lsusb  
Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc.  
Bus 003 Device 002: ID 0424:3503 Standard Microsystems Corp.  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I enabled desired configs for sierra modem wireless with kernel menuconfig (  
CONFIG\_USB\_SERIAL=m,  
CONFIG\_USB\_SERIAL\_GENERIC=y,  
CONFIG\_USB\_SERIAL\_CONSOLE=y  
CONFIG\_USB\_NET\_QMI\_WWAN=m  
CONFIG\_USB\_SIERRA\_NET=m

Thanks and regards  
Sathish Ram

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 2, 2022, 6:41am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/2 "2022-11-02T06:41:57Z")

</div>

Here says no problem is found for kernel 5.15:

> [@EM9190 not being detected in Linux Ubuntu 20.04.5 EM9191 EM7690 5G dev kit](https://forum.sierrawireless.com/t/em9190-not-being-detected-in-linux-ubuntu-20-04-5-em9191-em7690-5g-dev-kit/28161):
>
> EM9190 not being detected in Linux Ubuntu 20.04.5 EM9191 EM7690 EM9190 DEV KIT BOARD 5304831\_REV\_4 $ lsusb command in terminal doesn’t detect the EM9190 [Item: 6001349] Sierra Wireless 5G Development Kit. I have installed MBPL\_DRIVERS\_R28\_ENG1-usb-src.tar suggested in [Mobile Broadband Package for Linux (SDK, Drivers, Documentation)](https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/) Please Help. Thank you

Are you using the latest MBPL USB driver?

[https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/](https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/)

How about using MBIM interface? Does it work?

> [@EM7455 not enabled by default under Windows 10](https://forum.sierrawireless.com/t/em7455-not-enabled-by-default-under-windows-10/28064/17):
>
> Skylight uninstalled, same result. And I have updated the latest Verizon firmware, also does not help. And after I issue the !RMARESET=1 command, the firmware seems roll back to the previous one by itself.

---

<div class="post-metadata">

**Author:** ![Murugan.SathishRam](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Murugan.SathishRam](https://forum.sierrawireless.com/u/Murugan.SathishRam)\
**Post date:** [November 2, 2022, 6:53am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/3 "2022-11-02T06:53:38Z")

</div>

I think that its not related to hardware issue or modem software issue, Since same modem works with kernel version 4.9 with same hardware but not working in kernel 5.10. In our product, we are using yocto buildsystem to build customized kernels. I am not sure whether I am missing out configuration parameters or patches

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 2, 2022, 6:54am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/4 "2022-11-02T06:54:16Z")

</div>

have you tried with Ubuntu PC first?

Do you see anything in dmesg when connecting the USB cable of MC74xx?

---

<div class="post-metadata">

**Author:** ![Murugan.SathishRam](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Murugan.SathishRam](https://forum.sierrawireless.com/u/Murugan.SathishRam)\
**Post date:** [November 2, 2022, 7:02am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/5 "2022-11-02T07:02:27Z")

</div>

yeah, its working with ubuntu and also kernel version of 4.9 with same hardware and same modem. In dmesg, i will get output like this  
[4.476443] usbcore: registered new interface driver usbserial  
[4.489477] usbcore: registered new interface driver cdc\_wdm  
[4.496928] qmi\_wwan 3-1.3:1.8: cdc-wdm0: USB WDM device  
[4.509625] qmi\_wwan 3-1.3:1.8 wwan0: register ‘qmi\_wwan’ at usb-ci\_hdrc.2-1.3, WWAN/QMI device, be:ec:77:b4:bc:5c  
[4.512611] qmi\_wwan 3-1.3:1.10: cdc-wdm1: USB WDM device  
[4.520874] qmi\_wwan 3-1.3:1.10 wwan1: register ‘qmi\_wwan’ at usb-ci\_hdrc.2-1.3, WWAN/QMI device, be:ec:77:b4:bc:5c  
[4.520994] usbcore: registered new interface driver qmi\_wwan  
[4.755502] usbcore: registered new interface driver usbserial\_generic  
[4.837276] usbserial: USB Serial support registered for generic  
[4.896511] usbcore: registered new interface driver qcserial  
[4.935527] usbserial: USB Serial support registered for Qualcomm USB modem  
[4.992732] qcserial 3-1.3:1.0: Qualcomm USB modem converter detected  
[5.007310] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB0  
[5.045642] qcserial 3-1.3:1.2: Qualcomm USB modem converter detected  
[5.061652] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB1  
[5.082401] qcserial 3-1.3:1.3: Qualcomm USB modem converter detected  
[5.100424] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB2

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 2, 2022, 7:03am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/6 "2022-11-02T07:03:22Z")

</div>

I mean the dmesg in kernel 5.10 for the NOK case.

---

<div class="post-metadata">

**Author:** ![Murugan.SathishRam](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Murugan.SathishRam](https://forum.sierrawireless.com/u/Murugan.SathishRam)\
**Post date:** [November 2, 2022, 7:16am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/7 "2022-11-02T07:16:53Z")

</div>

dmesg logs for kernel 5.10  
[dmesg.txt](https://forum.sierrawireless.com/uploads/short-url/33iMa2GKNi4kOSuIoJdQ4fHEfhX.txt) (50.3 KB)

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [November 2, 2022, 7:25am UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/8 "2022-11-02T07:25:25Z")

</div>

you should at least see something like this even there is no driver:

```auto
usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
usb 2-2: config 1 has an invalid interface number: 4 but max is 3
usb 2-2: config 1 has no interface number 2
usb 2-2: New USB device found, idVendor=1199, idProduct=90d3, bcdDevice= 0.06
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: Sierra Wireless EM9191
usb 2-2: Manufacturer: Sierra Wireless, Incorporated

```

could it be a hardware issue?

---

<div class="post-metadata">

**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\
**Post date:** [November 4, 2022, 6:37pm UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/9 "2022-11-04T18:37:19Z")

</div>

> [@jyijyi](#):
>
> could it be a hardware issue?

or maybe a missing platform driver? minicard pin 20 control? slot power control?

Like @jyijyi says: the modem will show up on the USB bus whether or not there is a driver for it. So when it doesn’t show up, then it’s either physically disconnected, powered down or held in reset. This is managed by the host platform. If it works on one kernel version but not on another running on the same hardware, then you should look for a driver issue. But it won’t be the usb/modem drivers… It will be the drivers controlling the minicard slot on the host platform.

---

<div class="post-metadata">

**Author:** ![Murugan.SathishRam](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Murugan.SathishRam](https://forum.sierrawireless.com/u/Murugan.SathishRam)\
**Post date:** [November 6, 2022, 4:52pm UTC](https://forum.sierrawireless.com/t/mc74xx-chip-is-not-detecting-in-kernel-5-10-but-its-get-detected-in-4-9/28249/10 "2022-11-06T16:52:36Z")

</div>

Thanks a lot for the answers. yeah its driver configuration issue. I figured it out two of usb ports and mini pci slot where the modem is connected is not detecting anything. Its not issue in modem software
