tonio92 Posted November 16, 2016 Share Posted November 16, 2016 SInce a few days and without success, i try to install a 4G module DW5570 on OSX SIERRA in my computer /hackintosh dell E5440 According All , few problems could be encountered during installation : - bad configuration in the USB boards since OSX el capitan --> need to define a kext "USBinjectAll" to redefine the USB2/USB3 and internal port -modification in kext "CellPhoneHelper.kext " or utilisation legacy_sierra_QMI.kext to define the module DW5570 I have now this configuration without possibility to switch on the module with a cmd AT Please help me to understand where is the problem to find a solution. Module is identified as a usb device and a wwan module SMbios choosen for E5440 : Macbook pro 6.1 Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 16, 2016 Administrators Share Posted November 16, 2016 https://osxlatitude.com/index.php?/topic/8006-sierra-wireless-qmi-modules-mcem73xx8805-dell-dw557058085809/ You can rule out a USB port issue, your module is clearly listed in SysProfiler, i.e. detected and correctly reported in IOReg. So, it's more to do with CellPhoneHelper patch (if it's supported on this 4G module) or the QMI kext posted by Skvo. You have to base the patch on Sierra's vanilla kext, not an older version such as Yosemite's because Apple tends to modify these kexts from one OS X version to another (like they also like to do for Bluethooth kexts). For instance Skvo's patch made references to Yosemite's AppleUSBMergeNub kext as per CellPhoneHelper kext whereas, in Sierra, that kext does not exist and was replaced by AppleUSBHostMergeProperties. Try the following patch in Sierra which you can simply add to FakeSMC's Info.plist through any text editor: <key>0x413C Dell Wireless (based on Sierra QMI) modules</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBHostMergeProperties</string> <key>IOClass</key> <string>AppleUSBHostMergeProperties</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>IOProviderMergeProperties</key> <dict> <key>DeviceModemOverrides</key> <dict> <key>AccessPointName</key> <string>Obtain From Service Provider</string> <key>ConnectionPersonality</key> <string>Sierra GSM Personality</string> <key>ConnectionScript</key> <string>WWAN.ccl</string> <key>DeviceContextID</key> <string>1</string> <key>DeviceModel</key> <string>GSM</string> <key>DeviceVendor</key> <string>Sierra Wireless</string> </dict> <key>DevicePPPOverrides</key> <dict> <key>LCPMTU</key> <integer>1450</integer> </dict> <key>InfoCommands</key> <dict> <key>ATCommands</key> <dict> <key>DirectoryNumber</key> <string>+cnum</string> <key>IMEI</key> <string>+cgsn</string> <key>IMSI</key> <string>+cimi</string> <key>Manufacturer</key> <string>+cgmi</string> <key>Model</key> <string>+cgmm</string> <key>ModemSW</key> <string>+cgmr</string> <key>Serial#</key> <string>+gsn</string> </dict> <key>HiddenProperties</key> <dict> <key>CommandPortBaseName</key> <string>wwan</string> <key>ControlPortBaseName</key> <string>wwan</string> <key>DataPortBaseName</key> <string>wwan</string> <key>StatusType</key> <string>CellPhoneGSM</string> </dict> </dict> <key>Initializing</key> <true/> <key>InterfaceMapping</key> <dict> <key>0</key> <string>wwanDM</string> <key>2</key> <string>wwanGPS</string> <key>3</key> <string>wwan</string> </dict> <key>WWAN</key> <true/> </dict> <key>bcdDevice</key> <integer>6</integer> <key>idProduct</key> <string>*</string> <key>idVendor</key> <integer>16700</integer> </dict> - Link to comment Share on other sites More sharing options...
tonio92 Posted November 16, 2016 Author Share Posted November 16, 2016 Thank you Hervé for this response and your analyse. Legacy_sierra_qmi.kext and CellPhoneHelper.kext are some command identified AT to communicate with the module For example : <key>ATCommands</key> <dict> <key>DirectoryNumber</key> <string>$nwmdn</string> <key>ESN</key> <string>+gsn</string> <key>Manufacturer</key> <string>+gmi</string> <key>Model</key> <string>+gmm</string> <key>ModemSW</key> <string>+gmr</string> It is not possible for me to have a response with a console and you see the same pb in the pictures : no response with logiciel model ..... Have you a solution to activate the ATcommands thank you for your reply best regards Link to comment Share on other sites More sharing options...
tonio92 Posted November 18, 2016 Author Share Posted November 18, 2016 I have tested two configurations without success : -First config : Legacy_sierra_qmi.kext posted by SKvo and CellPhoneHelper.kext Sierra : module is detected as WWAN --> with the command ls -la /dev/tty.* only two devices identifed (see pictures 1) -Second config : Legacy_sierra_qmi.kext deleted and a CellPhoneHelper.kext Sierra modified : module is detected as WWAN --> with the command ls -la /dev/tty.* only three devices identifed (see pictures 2) a new device tty.wwan but impossible to communicate with it : why ? is it my module wwan ? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted November 18, 2016 Administrators Share Posted November 18, 2016 1st of all, note that you obviously must not use the Legacy_sierra_qmi kext posted by Skvo under macOS Sierra because it's based on Yosemite's CellPhoneHelper kext. This kext is not compatible with Sierra and won't work under macOS 10.12. This extends naturally to any patch built on it. Secondly, you must not use Legacy_sierra_qmi kext AND patched CellPhoneHelper kext. You may use either/or but not both. Did you try the patch I detailed above? It was just a basic and rapid adaptation of Skvo's posted patch for macOS Sierra. I might have missed something in my code of course. Lastly, please note that, SIM inserted, if the reported WWAN module does not list software version and network name, it's simply not operating properly. 1st thing to do is get your module fully recognised. Skvo wasn't exactly thorough or generous with details in his thread so, not owning this particular WWAN module myself, I'm not in a position to undertake any tests and cannot be of much further help on this. I can only offer you to send me your module to try and get it working. Link to comment Share on other sites More sharing options...
tonio92 Posted November 28, 2016 Author Share Posted November 28, 2016 Hi, It seem that modem Sierra DW5570 (MC8805) is stucked in low power mode (see attached bug report : https://bugzilla.kernel.org/show_bug.cgi?id=78851 The solution is to install a library : "Dell-branded Sierra Wireless modems need the "FCC Auth" command (QMI DMS service, 0x555F) before they can be brought online; supported in libqmi and ModemManager already." is it possible to install this library on OS X ? Best regards Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now