Getting usb invalid interface number with EM060K-GL USB in ubuntu 22.04 and 20.10

Dear,

we getting below with boot messages.
We can dial-up using quectel-CM and connect internet.

references :

Getting usb invalid interface number with EM060K-GL PCIE in Openwrt

we question :

  1. how to fix invalid messages in the cold boot or reboot.
    usb 1-3: config 1 has an invalid interface number: 8 but max is 6
    usb 1-3: config 1 has an invalid interface number: 9 but max is 6
    usb 1-3: config 1 has an invalid interface number: 9 but max is 6
    usb 1-3: config 1 has an invalid interface number: 12 but max is 6
    usb 1-3: config 1 has no interface number 4
    usb 1-3: config 1 has no interface number 5
    usb 1-3: config 1 has no interface number 6

  2. Or is there documentation to prove that it does not affect function?

  3. Is this message related to the FW of EM060K-GL?
    (Because RM500Q, EM06, EG25, EC25, EM05…etc don’t have this message)

boot messages:
[ 38.572040] usb 1-3: new high-speed USB device number 4 using xhci_hcd
[ 38.724727] usb 1-3: config 1 has an invalid interface number: 8 but max is 6
[ 38.731862] usb 1-3: config 1 has an invalid interface number: 9 but max is 6
[ 38.739006] usb 1-3: config 1 has an invalid interface number: 9 but max is 6
[ 38.746143] usb 1-3: config 1 has an invalid interface number: 12 but max is 6
[ 38.753361] usb 1-3: config 1 has no interface number 4
[ 38.758586] usb 1-3: config 1 has no interface number 5
[ 38.763813] usb 1-3: config 1 has no interface number 6
[ 38.770061] usb 1-3: New USB device found, idVendor=2c7c, idProduct=030b
[ 38.776771] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 38.783903] usb 1-3: Product: EM060K-GL
[ 38.787742] usb 1-3: Manufacturer: Quectel
[ 38.791842] usb 1-3: SerialNumber: d3d5633b
[ 38.823519] usbcore: registered new interface driver cdc_ncm
[ 38.832522] usbcore: registered new interface driver cdc_wdm
[ 39.300681] cdc_mbim 1-3:1.8: setting rx_max = 16384
[ 39.306190] cdc_mbim 1-3:1.8: cdc-wdm0: USB WDM device
[ 39.312086] cdc_mbim 1-3:1.8 wwan0: register ‘cdc_mbim’ at usb-0000:00:15.0-3, CDC MBIM, ae:96:f0:39:e4:29
[ 39.321853] usbcore: registered new interface driver cdc_mbim
[ 39.329419] cdc_mbim 1-3:1.8 wwp0s21u3i8: renamed from wwan0

Dear Justin,

Could you show the result of :slight_smile:

cat /sys/kernel/debug/usb/devices

and

lsusb -t

it seems like warnings because you didn’t install the tty serail driver.

Dear Bean.Wang-Q :

thank for you reply.

“it seems like warnings because you didn’t install the tty serail driver.”
=> you mean “usbserial” driver ??

cat /sys/kernel/debug/usb/devices
message =>
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=2c7c ProdID=030b Rev= 5.04
S: Manufacturer=Quectel
S: Product=EM060K-GL
S: SerialNumber=d3d5633b
C:* #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=500mA
A: FirstIf#= 8 IfCount= 2 Cls=02(comm.) Sub=0e Prot=00
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=40 Driver=(none)
E: Ad=83(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=(none)
E: Ad=85(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=40 Driver=(none)
E: Ad=87(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 8 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0e Prot=00 Driver=cdc_mbim
E: Ad=88(I) Atr=03(Int.) MxPS= 64 Ivl=32ms
I: If#= 9 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I:* If#= 9 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
E: Ad=8e(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=0f(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#=12 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=70 Driver=(none)
E: Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

lsusb -t
message =>
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 3, If 3, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 3, If 8, Class=Communications, Driver=cdc_mbim, 480M
|__ Port 3: Dev 3, If 9, Class=CDC Data, Driver=cdc_mbim, 480M
|__ Port 3: Dev 3, If 12, Class=Vendor Specific Class, Driver=, 480M

Thanks.

What I mean:

image

the option driver show match the usb interface.

Dear Bean.Wang-Q :
I know insmod “option.ko” driver.
“lsusb -t” message =>
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 3, If 1, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 3, If 2, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 3, If 3, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 3: Dev 3, If 8, Class=Communications, Driver=cdc_mbim, 480M
|__ Port 3: Dev 3, If 9, Class=CDC Data, Driver=cdc_mbim, 480M
|__ Port 3: Dev 3, If 12, Class=Vendor Specific Class, Driver=option, 480M

AT command is work. (“option” may only affect tty serial)
But, I want to know “how to fix invalid messages in the cold boot or reboot.”

my question :
I have update driver (usb_wwan, qcserial, option, qmi_wwan_q) to kernel.
But boot or reboot still have “invalid” message.

I thought so it was “If” not sorting!!!
ex: EM060K-GL => 0,1,2,3,8,9,12
I think => 0,1,2,3,4,5,6
Below is EM06-E message:
EM06-E

yes. It should be in order.
But till now, it is like this.
Maybe it will be fixed in next version.

OK~, I see.
FW will be fixed in next version.
Is there plan time?
So, “invalid message” doesn’t affect function?
How do explain it to our customers?

Thanks.

The interface like 4\5\6\7 might be used for other purpose, such as UAC and adb.

Yes it’s really a very bad experience for customers. I will write letters to the related software engineers and software project manager to fix it.

If I have any feedback I will inform you.

yes. It is warnnings and don’t affect the funtions.

thanks for your help.
If you get any response, please inform me.

Thanks.

Hi Justin,

Could you tell me which version of the firmware do you use?

Dear Bean.Wang-Q :
I has no EM060K-GL AT command manual.
Could you provide me?
below message , reference RM500Q’s AT manual
FW_version

Thanks.

Sorry Till now there is no AT command manual for EM060K.
You can use the manual for RM500Q.

RD don’t think it need be fixed. It is just warnnings.

Dear Bean.Wang-Q :

OK, 
I know, but you(Quectel) could provide any documentation,
explain it is "No plan to fix".
let us provide to customers.
Can't just let us say "Quectel no plan to fix it".

Thanks.

I cannot provide any document on the forums.
You can email to me: bean.wang@quectel.com.

Dear Bean.Wang-Q :

OK, thanks.
has sent mail.

Thanks.