![]() * Then the modem disappears, and reappears in ethernet mode (product 14db)! Abort" just after it finds the device (I set EnableLogging=1 to see this, full logs below). * But usb_modeswitch always crashes with the error "Error opening the device. * Our setup correctly identifies our custom rule to switch them into serial mode (product 155e) and runs usb_modeswitch with the appropriate arguments. * The new modems initially appear with the same vendor and product id as the old ones: 12d1:1f01 (as seen in journalctl). ![]() This has been working perfectly well with older modems for around 6 months now, but recently we got a new batch of modems which mysteriously switched into ethernet mode instead. ![]() ![]() We have a setup which switches our E3372 modems into serial mode. I had some problems with getting an E3372h-320 into serial (or "option") mode and wanted to share my findings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |