On Fri, Sep 24, 2021 at 12:19:35PM +0800, Kevin Lo wrote: > > On Fri, Sep 03, 2021 at 10:08:52PM +0000, Cord wrote: > > > > > > > > > > > > It looks like it is probably a Qualcomm-based device. It seems likely > > > > > > that as things are now, it will attach to umsm. I can't say for sure if > > > > > > it will work or not though I think there is a fairly good chance. > > > > > > But unless you are lucky and somebody already used the same device, > > > > > > you will need to buy one to find out for sure. > > > > > > If it does work, while attached to umsm there should be several com > > > > > > interfaces presented, one of which is likely to accept AT commands > > > > > > so you can find strength that way. For umsm, you will need to mess > > > > > > about with pppd to get it to connect to the internet. > > > > > > The device would probably support working with umb(4) but would need > > > > > > some extra work (maybe as simple as moving the vendor/product ID to > > > umb(4), > > > > > > but it may need more...so far I have a success rate of about 33% with umb > > > > > > devices, including some devices which are even listed in the manpage - > > > > > > the firmware on the device matters too, not just the chipset). > > > > > > There is no support for displaying signal strength directly via umb, > > > > > > and the other com ports are only available via umsm, so in that case you > > > > > > can't send AT commands to find it either.. > > > > > > This device is cat4 only (no MIMO, no channel aggregation) so speed won't > > > > > > be amazing. > > > > > > > > > Hello, thank you very much for your help. > > I bought the toy and it seems it works, but it stuck when I run fw_update > > at around 10% or 20%. In the log I found messages like: > > ppp0: bad fcs 59f8 > > ppp0: bad protocol 728a > > ppp0: packet too big > > ppp0: bad fcs baf0 > > ppp0: bad protocol debc > > ppp0: bad fcs and so on. > > > > The strange thing is that when I press ctrl+c to break the ppp connection I > > lose all the connections I have with box. I mean lan and serial connections. > > I don't know if the box is stucked or it's just the connection. But I find > > very strange that I lose the serial connection. Obviously the box is > > headless. It's just a simple > > raspberry. > > FCS stand for "Frame Check Sequence" and it seems a kind of ppp checksum. > > Maybe I'm in a spot where the signal is weak. I'll try to move the dongle. > > I got mine yesterday. As sthen@ pointed out, this device would support > working with umb(4). Using the following AT commands to switch into mbim > mode: > > AT+CUSBPIDSWITCH=9003,1,1 > AT+CLANMODE=1 > > You also need to apply the following diff, thanks.
Index: sys/dev/usb/if_umb.c =================================================================== RCS file: /cvs/src/sys/dev/usb/if_umb.c,v retrieving revision 1.46 diff -u -p -u -p -r1.46 if_umb.c --- sys/dev/usb/if_umb.c 4 Jul 2021 19:22:31 -0000 1.46 +++ sys/dev/usb/if_umb.c 24 Sep 2021 01:12:24 -0000 @@ -256,6 +256,12 @@ const struct umb_quirk umb_quirks[] = { 0, 0 }, + + { { USB_VENDOR_SIMCOM, USB_PRODUCT_SIMCOM_SIM7600 }, + 0, + 1, + UMATCH_VENDOR_PRODUCT + }, }; #define umb_lookup(vid, pid) \ Index: sys/dev/usb/usbdevs =================================================================== RCS file: /cvs/src/sys/dev/usb/usbdevs,v retrieving revision 1.741 diff -u -p -u -p -r1.741 usbdevs --- sys/dev/usb/usbdevs 31 Aug 2021 22:55:56 -0000 1.741 +++ sys/dev/usb/usbdevs 24 Sep 2021 01:12:24 -0000 @@ -4123,6 +4123,7 @@ product SILICONPORTALS YAPPHONE 0x0201 Y /* Simcom products */ product SIMCOM SIM7600E 0x9001 SIM7600E modem +product SIMCOM SIM7600 0x9003 SIM7600 LTE /* Sirius Technologies products */ product SIRIUS ROADSTER 0x0001 NetComm Roadster II 56