Re: Does not Debian support mobile broadband anymore?
Yes, this is expected. As I said: 1199:9078 is a booloader mode. This mode is
normally only visible in two situations:
1) when upgrading firmware
2) when the firmware fails to boot
Your case is numer 2. The booloader will try to boot the modem firmware
a few times (seen as multiple connect+disconnect events) and then enter
a failsafe/debug mode. There is only a single USB interface available
in this mode, as you can see from your lsusb output. This is a serial
function which is handled by the same driver that will handle the normal
modem serial function, making it appear to the system as typically
/dev/ttyUSB0. But there is *no modem* related function there. Only a
Qualcomm or Sierra Wireless bootloader debug function, speaking the
SAHARA protocol.
As I said: Please verify that the modem works on any other OS if you
can. Downgrade your Debian install if you believe that will help. If it
doesn't, then you should assume that the firmware or NVRAM on this modem
is damaged. This is most likely a warranty repair since this is a rather
new laptop. You should therefore contact Lenovo support.
Bjørn
wglxy@china.com writes:
> Sometimes, the device Sierra Wireless EM7455 is connected success, and run lsusb, mmcli -L, their output is below. No any modem is found.
>
> lsusb -v
> ************************************************************************
> Bus 001 Device 009: ID 1199:9078 Sierra Wireless, Inc.
> Couldn't open device, some information will be missing
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x1199 Sierra Wireless, Inc.
> idProduct 0x9078
> bcdDevice 0.00
> iManufacturer 1
> iProduct 2
> iSerial 3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 32
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 2mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 2
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01 EP 1 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> *****************************************************************************
>
> mmcli -L
> ************************************
> No modems were found
> ************************************
>
>
>> -----原始邮件-----
>> 发件人: "Bjørn Mork" <bjorn@mork.no>
>> 发送时间: 2017-11-23 16:38:25 (星期四)
>> 收件人: wglxy@china.com
>> 抄送: debian-laptop@lists.debian.org
>> 主题: Re: Does not Debian support mobile broadband anymore?
>>
>> wglxy@china.com writes:
>>
>> > I use dmesg to view the system message, and get these informations as below,
>> >
>> > [ 1535.372130] usb 1-6: new high-speed USB device number 8 using xhci_hcd
>> > [ 1535.378889] thinkpad_acpi: unknown possible thermal alarm or keyboard event received
>> > [ 1535.378893] thinkpad_acpi: unhandled HKEY event 0x60b0
>> > [ 1535.378894] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net
>> > [ 1535.513304] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
>> > [ 1535.513308] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> > [ 1535.513310] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
>> > [ 1535.513312] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
>> > [ 1535.513313] usb 1-6: SerialNumber: LF72567821041020
>> > [ 1535.513996] qcserial 1-6:1.0: Qualcomm USB modem converter detected
>> > [ 1535.514212] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB0
>> > [ 1535.515015] usb 1-6: USB disconnect, device number 8
>> > [ 1535.515330] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
>> > [ 1535.515356] qcserial 1-6:1.0: device disconnected
>> > [ 1536.014626] thinkpad_acpi: unknown possible thermal alarm or keyboard event received
>> > [ 1536.014628] thinkpad_acpi: unhandled HKEY event 0x60b1
>> > [ 1536.014629] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net
>> > [ 1536.524163] usb 1-6: new high-speed USB device number 9 using xhci_hcd
>> > [ 1536.665054] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
>> > [ 1536.665058] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
>> > [ 1536.665988] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
>> > [ 1536.665992] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> > [ 1536.665994] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
>> > [ 1536.665996] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
>> > [ 1536.665998] usb 1-6: SerialNumber: LF72567821041020
>> > [ 1536.666822] usb 1-6: USB disconnect, device number 9
>> > [ 1544.686163] thinkpad_acpi: unknown possible thermal alarm or keyboard event received
>> > [ 1544.686167] thinkpad_acpi: unhandled HKEY event 0x60b0
>> > [ 1544.686168] thinkpad_acpi: please report the conditions when this event happened to ibm-acpi-devel@lists.sourceforge.net
>> > [ 1553.785361] usb 1-6: new high-speed USB device number 11 using xhci_hcd
>> > [ 1553.926371] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
>> > [ 1553.926390] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> > [ 1553.926392] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
>> > [ 1553.926394] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
>> > [ 1553.926395] usb 1-6: SerialNumber: LF72567821041020
>> > [ 1553.926986] qcserial 1-6:1.0: Qualcomm USB modem converter detected
>> > [ 1553.927112] usb 1-6: Qualcomm USB modem converter now attached to ttyUSB0
>> > [ 1553.928024] usb 1-6: USB disconnect, device number 11
>> > [ 1553.928258] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
>> > [ 1553.928275] qcserial 1-6:1.0: device disconnected
>> > [ 1554.937425] usb 1-6: new high-speed USB device number 12 using xhci_hcd
>> > [ 1555.078351] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
>> > [ 1555.078354] usb 1-6: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
>> > [ 1555.079241] usb 1-6: New USB device found, idVendor=1199, idProduct=9078
>> > [ 1555.079245] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> > [ 1555.079247] usb 1-6: Product: Sierra Wireless EM7455 Qualcomm
>> > [ 1555.079249] usb 1-6: Manufacturer: Sierra Wireless, Incorporated
>> > [ 1555.079250] usb 1-6: SerialNumber: LF72567821041020
>> > [ 1555.080269] usb 1-6: USB disconnect, device number 12
>> >
>> >
>> > That is to say, the device Sierra Wireless EM7455 is connected and disconnected frequently. It should be a problem of something. But I do not known what it is. This device worked fine before Oct 29.
>>
>> This is the problem, but I don't it is related to Debian versions in any
>> way.
>>
>> The modem seems to be constantly resetting. I expect it eventually
>> settles when the (modem) bootloader failsafe mode kicks in. But it will
>> then probably be in a debug mode.
>>
>> Notice that the device ID is 1199:9078 all the way. This is the
>> bootloader ID. The application ID is 1199:9079. If you have older logs
>> from when the modem worked, then I am pretty sure you'll see that ID
>> instead.
>>
>> I'm afraid there is little which can be done about this on an OS level,
>> unless the root cause is some platform (Lenovo) specific issue which
>> triggers the modem boot failure. My advice would be to test this with
>> another OS, if possible, and then contact Lenovo support if it fails
>> there as well.
>>
>>
>>
>> Bjørn
Reply to: