Re: Fibocom L850-GL / Intel XMM7360
On Mon, 2020-06-22 at 09:42 +0200, Aleksander Morgado wrote: > Hey, > > > > Anyway, FWIW, I'd explore the PCIe driver option first if I were > > > you. > > > That's the only mode tested by anyone, so it is more likely to > > > work. > > Is there anybody reading this willing and knowlegable enough to > > work on > > a kernel driver for inclusion in mainline? I'm able to provide > > funding > > and hardware for testing... > > > > If I'm not mistaken, Intel themselves are working on implementing the > PCIe driver for these XMM based modules, but I don't know how well > that is going, or when it's going to happen. I'll ask Fibocom to see > if they have updates. It exists, is for 7560 and later, and may be proposed soon. Not sure how hard it would be adapt to earlier devices, but that would probably require some community input. Dan > If switching the L850-GL to USB mode works, though, that would > probably work very well. The Dell DW5820e is a L850-GL in USB mode, > and I added a lot of support for that module in the past years. > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Fibocom L850-GL / Intel XMM7360
On Mon, 2020-06-22 at 10:45 +0200, Reinhard Speyerer wrote:
> On Mon, Jun 22, 2020 at 06:51:50AM +, Wassenberg, Dennis wrote:
> > Hi all,
> >
> > I tested the PCI approach.
> >
> > Unfortunately I had no luck. The kernel PCI driver at
> > https://github.com/xmm7360/xmm7360-pci can not initiale the modem
> > correctly. The modem stays at status=0xfeedb007. This seems to mean
> > that the modem is (still) booting. After 20 seconds
> > probing fails. The kernel driver gives up waiting for the device to
> > boot.
> >
> > So, both options: usb switch and native pci driver will not work.
> >
> > Are there any ideas how to continue?
> >
>
> Hi Dennis,
>
> some time ago Johannes Berg was working on a WWAN subsystem for the
> Linux
> kernel (
> https://lore.kernel.org/netdev/20200225100053.16385-1-johan...@sipsolutions.net/T/#t
> ) which also mentioned the 'upcoming Intel 4G modem driver ("iosm")'.
That effort is currently stalled. And the pci-based driver you mention
supports 7560 and later, not earlier devices. Not sure how hard it
would be to adapt to earlier devices though.
It does exist, but it's not quite ready for upstreaming yet.
Dan
> Perhaps it might help to ask him what the current status of this
> project is.
>
> Regards,
> Reinhard
>
> > Thank you & best regards,
> >
> > Dennis
> >
> >
> > On Thu, 2020-06-18 at 16:24 +0200, Dennis Wassenberg wrote:
> > > Hi Bjørn,
> > >
> > > thank you for your estimation.
> > >
> > > > Do you have any confirmation that it is actually possible to
> > > > switch this
> > > > firmware into USB mode? Are there other firmwares available
> > > > with
> > > > (possible) USB support?
> > > >
> > >
> > > I don't have a confirmation that the USB mode will really work,
> > > especially on the new models.
> > >
> > > Last year (Lenovo Thinkpad Whiskey Lake series) there was the
> > > possibility to choose between the slow modem (Fibocom
> > > L830-EB) and the faster option Fibocom L850-GL. This year the
> > > slow modem ist the fast modem of the last year and the
> > > fast modem is CAT16 Fibocom L860-GL.
> > >
> > > Regarding the Lenovo Thinkpad Whiskey Lake series models I found
> > > some threads where the USB mode switch worked:
> > >
> > > https://forums.lenovo.com/t5/Other-Linux-Discussions/WWAN-Fibocom-L850-GL-and-Linux-support/m-p/4318903?page=1#4327397
> > > https://gmt-24.net/archives/1461
> > >
> > > Thats why I assumed that this might work at newer Thinkpads as
> > > well.
> > >
> > > Especially https://gmt-24.net/archives/1461 shows that your
> > > assumption regarding the bootloader and application mode
> > > seems to be correct.
> > >
> > > This comes out directly after disabling the PCIe link and
> > > directly after that:
> > > [ 162.799214] usb 1-6: new high-speed USB device number 5 using
> > > xhci_hcd
> > > [ 162.940604] usb 1-6: New USB device found, idVendor=8087,
> > > idProduct=07f5, bcdDevice= 0.00
> > > [ 162.940612] usb 1-6: New USB device strings: Mfr=0, Product=0,
> > > SerialNumber=0
> > > [ 169.651754] usb 1-6: USB disconnect, device number 5
> > >
> > > Now bcdDevice changed to real device id.
> > >
> > > [ 175.462630] usb 1-6: new high-speed USB device number 6 using
> > > xhci_hcd
> > > [ 175.620153] usb 1-6: New USB device found, idVendor=2cb7,
> > > idProduct=0007, bcdDevice= 3.33
> > > [ 175.620162] usb 1-6: New USB device strings: Mfr=1, Product=2,
> > > SerialNumber=3
> > > [ 175.620167] usb 1-6: Product: L850-GL
> > > [ 175.620172] usb 1-6: Manufacturer: Fibocom Wireless Inc.
> > > [ 175.620176] usb 1-6: SerialNumber: 00499901064
> > >
> > >
> > > > Anyway, FWIW, I'd explore the PCIe driver option first if I
> > > > were you.
> > > > That's the only mode tested by anyone, so it is more likely to
> > > > work.
> > >
> > > Ok, I will try that approach and let you know my results.
> > >
> > > Thank you & best regards,
> > >
> > > Dennis
> > >
> > >
> > > On Thu, 2020-06-18 at 15:36 +0200, Bjørn Mork wrote:
> > > > "Wassenberg, Dennis" writes:
> > > >
> > > > > After that dmesg shows this:
> > > > > [ 930.843781] usb 1-7: new high-speed USB device number 16
> > > > > using xhci_hcd
> > > > > [ 930.996572] usb 1-7: New USB device found, idVendor=8087,
> > > > > idProduct=07f5, bcdDevice= 0.00
> > > > > [ 930.996577] usb 1-7: New USB device strings: Mfr=0,
> > > > > Product=0, SerialNumber=0
> > > > > [ 937.683939] usb 1-7: USB disconnect, device number 16
> > > > >
> > > > > So, in general I think there should be USB lines routed to
> > > > > the M.2 slot but I have no idea why the device leaves
> > > > > the
> > > > > bus. It is possible to run the script again and again but in
> > > > > the end it will always disconnect automatically.
> > > >
> > > > I know nothing about these modems, but my guess is that this is
> > > > a
> > > > bootloader mode. Mostly based on the assumption that there will
> > > > be one,
> > > > and that the vendor-id will be something non-Intel in
> > > >
Re: Reg Adding GPS NMEA & GPS RAW Capabilities to get GPS location using mmcli
Hi Aleksander, Thanks for the explanation.. Will try for GPGGA with antenna ... 1. Able to display nmea traces with *gps-nmea ..* mmcli -m 0 --location-status Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged | enabled: 3gpp-lac-ci, gps-raw, gps-nmea | signals: no GPS | refresh rate: 30 seconds root@tcs-imx6:~# mmcli -m 0 --location-get -- 3GPP | operator code: 404 | operator name: 49 | location area code: | tracking area code: C4E3 |cell id: 0DE0010B -- GPS | nmea: $GPGSA,A,1*32 | $GPRMC,,V,,N,V*29 | $GPGLL,,V,N*64 | $GPVTG,,T,,M,,N,,K,N*2C | $GPGGA,,0*66 2. For *gps-unmanaged * mmcli -m 0 --location-status Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged | enabled: 3gpp-lac-ci, gps-unmanaged | signals: no GPS | refresh rate: 30 seconds root@tcs-imx6:~# mmcli -m 0 --location-get -- 3GPP | operator code: 404 | operator name: 49 | location area code: | tracking area code: C4E3 |cell id: 0DE0010B 3. *For gps-raw : * mmcli -m 0 --location-status Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged | enabled: 3gpp-lac-ci, gps-raw | signals: no GPS | refresh rate: 30 seconds root@tcs-imx6:~# mmcli -m 0 --location-get -- 3GPP | operator code: 404 | operator name: 49 | location area code: | tracking area code: C4E3 |cell id: 0DE0010B Regards Ramu On Mon, Jun 22, 2020 at 1:06 PM Aleksander Morgado wrote: > Hey > > On Sat, Jun 20, 2020 at 3:39 PM Ramu wrote: > > > > I applied patches you mentioned for UDEV tags ... Seems to be working > now.. > > > > mmcli -m 0 --location-status > > > > Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged > >| enabled: 3gpp-lac-ci > >| signals: no > > > > GPS | refresh rate: 30 seconds > > > > Good! > > > ### Enabling GPS working fine ### > > > > root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-nmea > > successfully setup location gathering > > root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-raw > > successfully setup location gathering > > root@tcs-imx6:~# > > > > Ok. > > > ### Do we need get any location Data here ??? > > root@tcs-imx6:~# mmcli -m 0 --location-get-gps-raw > > error: no actions specified > > root@tcs-imx6:~# mmcli -m 0 --location-get-gps-nmea > > error: no actions specified > > > > The command you're looking for is --location-get. > > > But the GPS data is comign on the ttyUSB1 port .. I have not connected > any passive or active antenna for GPS as of now.. But seeing below data ... > > > > cat /dev/ttyUSB1 > > If you are using --location-enable-gps-nmea or > --location-enable-gps-raw you CANNOT touch the ttyUSB1 manually. You > cannot "cat" it or any other thing, because you would be hijacking the > data from ModemManager. If you need to cat or touch the ttyUSB1 > manually, you instead need to --location-enable-gps-unmanaged, so that > MM takes care of starting the GPS engine, but then ignores the tty > with the GPS data. > > > $GPVTG,,T,,M,,N,,K,N*2C > > $GPGSA,A,1*32 > > $GPGGA,,0*66 > > $GPRMC,,V,,N,V*29 > > $GPGLL,,V,N*64 > > $GPVTG,,T,,M,,N,,K,N*2C > > $GPGSA,A,1*32 > > $GPGGA,,0*66 > > $GPRMC,,V,,N,V*29 > > $GPGLL,,V,N*64 > > $GPVTG,,T,,M,,N,,K,N*2C > > $GPGSA,A,1*32 > > $GPGGA,,0*66 > > $GPRMC,,V,,N,V*29 > > $GPGLL,,V,N*64 > > > > Given that your GPGGA trace doesn't give any location yet, the output > of --location-get will not give you lat/long info, but it will still > give you the list of NMEA traces received and read by ModemManager (as > long as you don't hijack the tty as said above). > > Cheers! > > -- > Aleksander > https://aleksander.es > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Fibocom L850-GL / Intel XMM7360
"Wassenberg, Dennis" writes: > I tested the PCI approach. > > Unfortunately I had no luck. The kernel PCI driver at > https://github.com/xmm7360/xmm7360-pci can not initiale the modem > correctly. The modem stays at status=0xfeedb007. This seems to mean > that the modem is (still) booting. After 20 seconds probing fails. The > kernel driver gives up waiting for the device to boot. Strange. That sounds similar to the USB experience. Maybe the issue preventing it from booting up in USB mode isn't related to USB after all? Maybe there is a problem with the installed firmware? Did you confirm that this specific test device actually works? Or did you test multiple modems with the same behaviour? Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Fibocom L850-GL / Intel XMM7360
On Mon, Jun 22, 2020 at 06:51:50AM +, Wassenberg, Dennis wrote:
> Hi all,
>
> I tested the PCI approach.
>
> Unfortunately I had no luck. The kernel PCI driver at
> https://github.com/xmm7360/xmm7360-pci can not initiale the modem
> correctly. The modem stays at status=0xfeedb007. This seems to mean that the
> modem is (still) booting. After 20 seconds
> probing fails. The kernel driver gives up waiting for the device to boot.
>
> So, both options: usb switch and native pci driver will not work.
>
> Are there any ideas how to continue?
>
Hi Dennis,
some time ago Johannes Berg was working on a WWAN subsystem for the Linux
kernel (
https://lore.kernel.org/netdev/20200225100053.16385-1-johan...@sipsolutions.net/T/#t
) which also mentioned the 'upcoming Intel 4G modem driver ("iosm")'.
Perhaps it might help to ask him what the current status of this project is.
Regards,
Reinhard
> Thank you & best regards,
>
> Dennis
>
>
> On Thu, 2020-06-18 at 16:24 +0200, Dennis Wassenberg wrote:
> > Hi Bjørn,
> >
> > thank you for your estimation.
> >
> > > Do you have any confirmation that it is actually possible to switch this
> > > firmware into USB mode? Are there other firmwares available with
> > > (possible) USB support?
> > >
> >
> > I don't have a confirmation that the USB mode will really work, especially
> > on the new models.
> >
> > Last year (Lenovo Thinkpad Whiskey Lake series) there was the possibility
> > to choose between the slow modem (Fibocom
> > L830-EB) and the faster option Fibocom L850-GL. This year the slow modem
> > ist the fast modem of the last year and the
> > fast modem is CAT16 Fibocom L860-GL.
> >
> > Regarding the Lenovo Thinkpad Whiskey Lake series models I found some
> > threads where the USB mode switch worked:
> >
> > https://forums.lenovo.com/t5/Other-Linux-Discussions/WWAN-Fibocom-L850-GL-and-Linux-support/m-p/4318903?page=1#4327397
> > https://gmt-24.net/archives/1461
> >
> > Thats why I assumed that this might work at newer Thinkpads as well.
> >
> > Especially https://gmt-24.net/archives/1461 shows that your assumption
> > regarding the bootloader and application mode
> > seems to be correct.
> >
> > This comes out directly after disabling the PCIe link and directly after
> > that:
> > [ 162.799214] usb 1-6: new high-speed USB device number 5 using xhci_hcd
> > [ 162.940604] usb 1-6: New USB device found, idVendor=8087,
> > idProduct=07f5, bcdDevice= 0.00
> > [ 162.940612] usb 1-6: New USB device strings: Mfr=0, Product=0,
> > SerialNumber=0
> > [ 169.651754] usb 1-6: USB disconnect, device number 5
> >
> > Now bcdDevice changed to real device id.
> >
> > [ 175.462630] usb 1-6: new high-speed USB device number 6 using xhci_hcd
> > [ 175.620153] usb 1-6: New USB device found, idVendor=2cb7,
> > idProduct=0007, bcdDevice= 3.33
> > [ 175.620162] usb 1-6: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [ 175.620167] usb 1-6: Product: L850-GL
> > [ 175.620172] usb 1-6: Manufacturer: Fibocom Wireless Inc.
> > [ 175.620176] usb 1-6: SerialNumber: 00499901064
> >
> >
> > > Anyway, FWIW, I'd explore the PCIe driver option first if I were you.
> > > That's the only mode tested by anyone, so it is more likely to work.
> >
> > Ok, I will try that approach and let you know my results.
> >
> > Thank you & best regards,
> >
> > Dennis
> >
> >
> > On Thu, 2020-06-18 at 15:36 +0200, Bjørn Mork wrote:
> > > "Wassenberg, Dennis" writes:
> > >
> > > > After that dmesg shows this:
> > > > [ 930.843781] usb 1-7: new high-speed USB device number 16 using
> > > > xhci_hcd
> > > > [ 930.996572] usb 1-7: New USB device found, idVendor=8087,
> > > > idProduct=07f5, bcdDevice= 0.00
> > > > [ 930.996577] usb 1-7: New USB device strings: Mfr=0, Product=0,
> > > > SerialNumber=0
> > > > [ 937.683939] usb 1-7: USB disconnect, device number 16
> > > >
> > > > So, in general I think there should be USB lines routed to the M.2 slot
> > > > but I have no idea why the device leaves
> > > > the
> > > > bus. It is possible to run the script again and again but in the end it
> > > > will always disconnect automatically.
> > >
> > > I know nothing about these modems, but my guess is that this is a
> > > bootloader mode. Mostly based on the assumption that there will be one,
> > > and that the vendor-id will be something non-Intel in application mode.
> > >
> > > You can probably confirm this by capturing the full device descriptor,
> > > e.g by creating a udev rule to dump it or simply by snooping on the bus.
> > >
> > > If this assumption is correct, then the firmware was supposed to boot
> > > into an application mode and then reconnect to the USB bus with its real
> > > device ID and descriptors. This could be failing due to a firmware
> > > crash, maybe caused by this unexpected state. Or more likely: The
> > > firmware on this modem is built without support for the USB mode.
> > >
> > > Do you have any confirmation that it
Re: Fibocom L850-GL / Intel XMM7360
Hey, > > Anyway, FWIW, I'd explore the PCIe driver option first if I were you. > > That's the only mode tested by anyone, so it is more likely to work. > Is there anybody reading this willing and knowlegable enough to work on > a kernel driver for inclusion in mainline? I'm able to provide funding > and hardware for testing... > If I'm not mistaken, Intel themselves are working on implementing the PCIe driver for these XMM based modules, but I don't know how well that is going, or when it's going to happen. I'll ask Fibocom to see if they have updates. If switching the L850-GL to USB mode works, though, that would probably work very well. The Dell DW5820e is a L850-GL in USB mode, and I added a lot of support for that module in the past years. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Reg Adding GPS NMEA & GPS RAW Capabilities to get GPS location using mmcli
Hey On Sat, Jun 20, 2020 at 3:39 PM Ramu wrote: > > I applied patches you mentioned for UDEV tags ... Seems to be working now.. > > mmcli -m 0 --location-status > > Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged >| enabled: 3gpp-lac-ci >| signals: no > > GPS | refresh rate: 30 seconds > Good! > ### Enabling GPS working fine ### > > root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-nmea > successfully setup location gathering > root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-raw > successfully setup location gathering > root@tcs-imx6:~# > Ok. > ### Do we need get any location Data here ??? > root@tcs-imx6:~# mmcli -m 0 --location-get-gps-raw > error: no actions specified > root@tcs-imx6:~# mmcli -m 0 --location-get-gps-nmea > error: no actions specified > The command you're looking for is --location-get. > But the GPS data is comign on the ttyUSB1 port .. I have not connected any > passive or active antenna for GPS as of now.. But seeing below data ... > > cat /dev/ttyUSB1 If you are using --location-enable-gps-nmea or --location-enable-gps-raw you CANNOT touch the ttyUSB1 manually. You cannot "cat" it or any other thing, because you would be hijacking the data from ModemManager. If you need to cat or touch the ttyUSB1 manually, you instead need to --location-enable-gps-unmanaged, so that MM takes care of starting the GPS engine, but then ignores the tty with the GPS data. > $GPVTG,,T,,M,,N,,K,N*2C > $GPGSA,A,1*32 > $GPGGA,,0*66 > $GPRMC,,V,,N,V*29 > $GPGLL,,V,N*64 > $GPVTG,,T,,M,,N,,K,N*2C > $GPGSA,A,1*32 > $GPGGA,,0*66 > $GPRMC,,V,,N,V*29 > $GPGLL,,V,N*64 > $GPVTG,,T,,M,,N,,K,N*2C > $GPGSA,A,1*32 > $GPGGA,,0*66 > $GPRMC,,V,,N,V*29 > $GPGLL,,V,N*64 > Given that your GPGGA trace doesn't give any location yet, the output of --location-get will not give you lat/long info, but it will still give you the list of NMEA traces received and read by ModemManager (as long as you don't hijack the tty as said above). Cheers! -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Reg Adding GPS NMEA & GPS RAW Capabilities to get GPS location using mmcli
I applied patches you mentioned for UDEV tags ... Seems to be working now.. mmcli -m 0 --location-status Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, gps-unmanaged | enabled: 3gpp-lac-ci | signals: no GPS | refresh rate: 30 seconds ### *Enabling GPS working fine #*## root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-nmea successfully setup location gathering root@tcs-imx6:~# mmcli -m 0 --location-enable-gps-raw successfully setup location gathering root@tcs-imx6:~# ### *Do we need get any location Data here ??? * root@tcs-imx6:~# mmcli -m 0 --location-get-gps-raw error: no actions specified root@tcs-imx6:~# mmcli -m 0 --location-get-gps-nmea error: no actions specified But the GPS data is comign on the ttyUSB1 port .. I have not connected any passive or active antenna for GPS as of now.. But seeing below data ... cat /dev/ttyUSB1 $GPVTG,,T,,M,,N,,K,N*2C $GPGSA,A,1*32 $GPGGA,,0*66 $GPRMC,,V,,N,V*29 $GPGLL,,V,N*64 $GPVTG,,T,,M,,N,,K,N*2C $GPGSA,A,1*32 $GPGGA,,0*66 $GPRMC,,V,,N,V*29 $GPGLL,,V,N*64 $GPVTG,,T,,M,,N,,K,N*2C $GPGSA,A,1*32 $GPGGA,,0*66 $GPRMC,,V,,N,V*29 $GPGLL,,V,N*64 On Sat, Jun 20, 2020 at 2:45 PM Aleksander Morgado wrote: > Hey, > > > Yes, No GPS capabilities reporting by mmcli ... > > mmcli -m 0 --location-status > > > > Location | capabilities: 3gpp-lac-ci > >| enabled: 3gpp-lac-ci > >| signals: no > > > > > > mmcli -m 0 --location-enable-gps-nmea > > error: couldn't setup location gathering: > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot > enable unsupported location sources: 'gps-nmea'' > > > > Ok, the reason for this is that there are no udev tags flagging any > port as GPS data for the device with vid:pid 1bc7:1201. > > You're missing at least commits > 8b7bdea7e07ca12f787ede809471f413ba988697 and > 9c77fb8834cf8b666baa2778514f809f11e303f3 in your custom build. These > patches are already scheduled to be included in MM 1.12.12, whenever > that happens. > > -- > Aleksander > https://aleksander.es > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: Fibocom L850-GL / Intel XMM7360
Hi all, I tested the PCI approach. Unfortunately I had no luck. The kernel PCI driver at https://github.com/xmm7360/xmm7360-pci can not initiale the modem correctly. The modem stays at status=0xfeedb007. This seems to mean that the modem is (still) booting. After 20 seconds probing fails. The kernel driver gives up waiting for the device to boot. So, both options: usb switch and native pci driver will not work. Are there any ideas how to continue? Thank you & best regards, Dennis On Thu, 2020-06-18 at 16:24 +0200, Dennis Wassenberg wrote: > Hi Bjørn, > > thank you for your estimation. > > > Do you have any confirmation that it is actually possible to switch this > > firmware into USB mode? Are there other firmwares available with > > (possible) USB support? > > > > I don't have a confirmation that the USB mode will really work, especially on > the new models. > > Last year (Lenovo Thinkpad Whiskey Lake series) there was the possibility to > choose between the slow modem (Fibocom > L830-EB) and the faster option Fibocom L850-GL. This year the slow modem ist > the fast modem of the last year and the > fast modem is CAT16 Fibocom L860-GL. > > Regarding the Lenovo Thinkpad Whiskey Lake series models I found some threads > where the USB mode switch worked: > > https://forums.lenovo.com/t5/Other-Linux-Discussions/WWAN-Fibocom-L850-GL-and-Linux-support/m-p/4318903?page=1#4327397 > https://gmt-24.net/archives/1461 > > Thats why I assumed that this might work at newer Thinkpads as well. > > Especially https://gmt-24.net/archives/1461 shows that your assumption > regarding the bootloader and application mode > seems to be correct. > > This comes out directly after disabling the PCIe link and directly after that: > [ 162.799214] usb 1-6: new high-speed USB device number 5 using xhci_hcd > [ 162.940604] usb 1-6: New USB device found, idVendor=8087, idProduct=07f5, > bcdDevice= 0.00 > [ 162.940612] usb 1-6: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > [ 169.651754] usb 1-6: USB disconnect, device number 5 > > Now bcdDevice changed to real device id. > > [ 175.462630] usb 1-6: new high-speed USB device number 6 using xhci_hcd > [ 175.620153] usb 1-6: New USB device found, idVendor=2cb7, idProduct=0007, > bcdDevice= 3.33 > [ 175.620162] usb 1-6: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 175.620167] usb 1-6: Product: L850-GL > [ 175.620172] usb 1-6: Manufacturer: Fibocom Wireless Inc. > [ 175.620176] usb 1-6: SerialNumber: 00499901064 > > > > Anyway, FWIW, I'd explore the PCIe driver option first if I were you. > > That's the only mode tested by anyone, so it is more likely to work. > > Ok, I will try that approach and let you know my results. > > Thank you & best regards, > > Dennis > > > On Thu, 2020-06-18 at 15:36 +0200, Bjørn Mork wrote: > > "Wassenberg, Dennis" writes: > > > > > After that dmesg shows this: > > > [ 930.843781] usb 1-7: new high-speed USB device number 16 using xhci_hcd > > > [ 930.996572] usb 1-7: New USB device found, idVendor=8087, > > > idProduct=07f5, bcdDevice= 0.00 > > > [ 930.996577] usb 1-7: New USB device strings: Mfr=0, Product=0, > > > SerialNumber=0 > > > [ 937.683939] usb 1-7: USB disconnect, device number 16 > > > > > > So, in general I think there should be USB lines routed to the M.2 slot > > > but I have no idea why the device leaves > > > the > > > bus. It is possible to run the script again and again but in the end it > > > will always disconnect automatically. > > > > I know nothing about these modems, but my guess is that this is a > > bootloader mode. Mostly based on the assumption that there will be one, > > and that the vendor-id will be something non-Intel in application mode. > > > > You can probably confirm this by capturing the full device descriptor, > > e.g by creating a udev rule to dump it or simply by snooping on the bus. > > > > If this assumption is correct, then the firmware was supposed to boot > > into an application mode and then reconnect to the USB bus with its real > > device ID and descriptors. This could be failing due to a firmware > > crash, maybe caused by this unexpected state. Or more likely: The > > firmware on this modem is built without support for the USB mode. > > > > Do you have any confirmation that it is actually possible to switch this > > firmware into USB mode? Are there other firmwares available with > > (possible) USB support? > > > > > > Anyway, FWIW, I'd explore the PCIe driver option first if I were you. > > That's the only mode tested by anyone, so it is more likely to work. > > > > > > > > Bjørn > > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
