Jump to content

Hervé

Administrators
  • Posts

    10013
  • Joined

  • Last visited

  • Days Won

    560

Everything posted by Hervé

  1. Hervé

    App Store

    This has been mentioned over and over on the forum: make sure your Ethernet/LAN port is 1st in the list of interface. Check that out through Terminal command ifconfig. If it's not the 1st interface in the list, remove all interfaces from your Network Preference panel, reboot then add the interfaces manually after reboot, starting with the Ethernet. Do think of using the search facility on the forum.
  2. Last Edited: 08 Mar 2020 - - - - - - - - - - - - - - - - - - Updated with info re: installation and operation in Mojave and Catalina I decided to look at that card I got from good old Tonton Leon some time last year... It's an HSPA+ model with data rates given at 21Mbps download and 5.76Mbps upload. This WWAN module works OOB under OS X (SL/L/ML/Mav/Yos/EC) as a dial-up USB 3G modem. In fact, the module appears listed as 3 different USB modems in the Network Preferences panel. They are visible as follows when clicking on the "+" icon when looking to add an interface manually: As many people know, the option to display the modem in the menu bar provides a useful shortcut to connect and disconnect the module to and from the 3G network: This thread details the procedure to follow in order to get the module recognized and operational as a proper WWAN module under OS X. There's no real difference between WWAN mode and USB modem mode in terms of 3G connection, but the WWAN mode provides the added benefit of the signal monitoring icon in the menu bar as opposed to a dial-up modem icon. The module I actually possess is the HP-branded one (for the infamous HP BIOS whitelist purposes), although it's exactly as pictured above with the black "Ericsson F5521gw" label across the card. The PCI ids are as follows (Vendor id/Product id in Hex): Ericsson F5521gw: 0x0bdb/0x1911 (or 3035/6417 in decimal) HP hs2340 HSPA+: 0x03f0/0x3a1d (or 1008/14877 in decimal) Dell DW5550: 0x413c/0x818d (or 16700/33165 in decimal) To configure the module as a WWAN under SL, Lion, ML and Mavericks myHack-based installations, proceed as follows: Remove the 3 WWAN modems listed in Network Preferences Make a copy of CellPhoneHelper.kext from /S/L/E to your desktop Open up the kext copied to your desktop and browse through to the Contents folder to patch the Info plist as detailed below Once your plist has been updated, move the patched kext from your Desktop to /E/E Run myHack->myFix (quick) and reboot For non myHack-based SL/L/ML/Mav installations, Yosemite, El Capitan, Sierra, High Sierra, Mojave and Catalina, proceed as follows: Remove the 3 WWAN modems listed in Network Preferences Use one of the 2 following methods: a.1. Make a backup of vanilla CellPhoneHelper kext found in /S/L/E a.2. Make a copy of CellPhoneHelper.kext from /S/L/E to your desktop a.3. Open up the kext copied to your desktop and browse through to the Contents folder to patch the Info plist as detailed below a.4. Once your plist has been updated, move the patched kext from your Desktop to /S/L/E and replace the original kext or b.1. Copy your FakeSMC kext to your desktop and browse through to the Contents folder to patch the Info plist as detailed below b.2. Once your plist has been updated, move the revised FakeSMC kext from your Desktop to its original folder (/S/L/E or /L/E or other) 3. Repair permissions, rebuild cache and reboot The patch basically consists of a pasted copy of the Sony Ericsson W350 entry, modified with the Ericsson FF5521gw, HP hs2340 or Dell DW5550 PCI device ids (entered in decimal values) and the Sony Ericsson reference for Device Vendor. For instance, to patch the CellphoneHelper kext in Mavericks or Yosemite, open up its Info.plist file with your preferred text editor, locate the Sony Ericsson W350 entry, copy/paste it right underneath and modify the pasted entry as indicated below: <key>0x03F0/0x3A1D HP hs2340</key> /* Edited reference for new entry */ <dict> <key>CFBundleIdentifier</key> [...] [...] [...] <key>DeviceModemOverrides</key> <dict> [...] [...] [...] <key>DeviceVendor</key> <string>Sony Ericsson</string> /* Edited DeviceVendor reference */ </dict> [...] [...] [...] <key>idProduct</key> <integer>14877</integer> /* Edited Product id (in decimal) */ <key>idVendor</key> <integer>1008</integer> /* Edited Vendor id (in decimal */ </dict> NB: in the Device Vendor section, the Sony Ericsson reference can be replaced by Generic as per the following code: <key>DeviceVendor</key> <string>Sony Ericsson</string> suitable alternative: <key>DeviceVendor</key> <string>Generic</string> ` The patch code above applies to the HP hs2340 HSPA+ module, so make sure to use the F5521gw PCI ids if you actually have the Ericsson-branded model or the DW5550 PCI ids if you have the Dell-branded one and change the name of the entry too to something appropriate like: <key>0x0BDB/0x1911 Sony/Ericsson F5521gw</key> or <key>0x413c/0x818d Dell DW5550</key> ` On reboot, the system should pop up an alert about new interfaces being available. Open up your Network Preferences and manually add the new WWAN interfaces as listed in the available interfaces menu if they're not automatically added. The WWAN icon can then be displayed in the menu bar to provide a shortcut to connect/disconnect the WWAN module to/from the 3G network. The icon provides signal strength monitoring just as on a cellular phone. On top of the USB entry in the System Profiler, a new WWAN entry will now be available with full details of the module. In the WWAN menu bar icon, unique information about the WWAN module can also be obtained through the About menu item. The module was tested successfully on D430, D630 and E6220 Dell Latitude laptops under Snow Leopard, Lion, Mountain Lion, Mavericks, Yosemite, El Capitan, Sierra, High Sierra, Mojave and Catalina: SL 10.6.8 -> patched CellPhoneHelper v1.2 from /S/L/E Lion 10.7.5 -> patched CellPhoneHelper v1.2.6 from /S/L/E ML 10.8.5 -> patched CellPhoneHelper v1.2.6 from /S/L/E MLPF 10.8.4/10.8.5 -> patched CellPhoneHelper v1.2.4 from /S/L/E Mav 10.9.2-10.9.5 -> patched CellPhoneHelper v1.3.2 from /S/L/E Yos 10.10-10.10.5 -> patched CellPhoneHelper v1.3.2 from /S/L/E EC 10.11.2-10.11.6 -> patched CellPhoneHelper v1.4.0 from /S/L/E Sie 10.12-10.12.6 -> patched CellPhoneHelper v1.4.0 from /S/L/E HiSie 10.13-10.13.6 -> patched CellPhoneHelper v1.4.0 from /S/L/E Moj 10.14-10.14.6 -> patched CellPhoneHelper v1.4.0 from /S/L/E Cat 10.15-10.15.3 -> patched CellPhoneHelper v1.4.0 from /S/L/E Performance wise, I've noticed data rates ranging from 3.5 to 14Mbps download and from 0.6 to 3.5Mbps upload. NB: As mentioned above, this patch can also be injected into FakeSMC Info.plist rather than patch /S/L/E/CellPhoneHelper or use a patched copy of the kext. I recommend this. Just make sure to inject the patch according to your current version of OS X and current version of CellPhoneHelper as the contents of the Info plist can differ between versions. In other words, re-using the patch of OS X/macOS version n in version n+1 is unlikely to work. Re-apply the patch to n+1's CellPhonerHelper contents.
  3. Can you post your system specs and the SMBIOS profile you're using?
  4. How about starting with a compatible bluetooth module?
  5. Yes. But you should have everything in the Extra you got there, i.e. no need of EDP.
  6. I think you're confusing disk partitioning and partitions formatting... Your disk is either GPT or MBR, it can't be both at the same time.
  7. kext = Kernel EXTension, it's another name for drivers, i.e. it's part of the OS, not Chameleon which is "just" a boot loader (although it does help to inject parameters to the OS). Chameleon would not prevent a LAN or WLAN kext to load. You can check your hardware specs with Terminal command lspci -nn and post us the output. In addition, list us the kext you have in /Extra/Extensions folder. Yes, you can simply install/re-install Chameleon through myHack; it should still allow you to boot Win and, in theory, Linux (TMX bootloader is just a copy of Chameleon afterwards). You would normally find myHack in Applications folder, there's no need to reboot from your USB installer.
  8. What wireless card do you have? I'm surprised Grub would have any effect on that... There's no problem running/installing Win7 on a GPT partitioned disk. Simply format the target partition as FAT from OS X and you'll be able to see it and reformat it NTFS afterwards during Win7 installation. Linux, can't remember, haven't bothered with it for many many years now, but I'm pretty sure I had a successful triple boot with Chameleon before.
  9. Guys, this is a post about Ethernet! Please use a separate thread for graphics! @Durga: is 10BaseT (legacy 10Mbps Ethernet) the only working choice? How about 100Mbps full-duplex?
  10. Check your screen res in the BIOS setup! Getting to know one's computer specs is the primary thing to do for Hackintoshing...
  11. Use this on HiRes/WXGA+ 1440x900 X3100 model: D630_X3100_HiRes_Extra.zip
  12. Did you read my last input?
  13. Ok, nothing specific for Sleep/Wake on the D620 nVidia. It's just running on native CPU power management with MBP5,1 settings (SMBIOS + SMC keys) Can you list the kexts you have in /E/E and the version you use for FakeSMC? Is there a string of characters in your Chameleon boot plist Properties field?
  14. There should not be any sleep/hibernation/wake issues. The D620 nVidia was known for its unrecoverable dark gray screen after screen sleep, but that could be recovered by putting the computer to sleep and then wake it; screen would then return to life. I'll go and check what I have on my D620 NV for sleep&wake; can't remember if it's using the SleepEnabler kext or not.
  15. Do you have the lspcidrv kext in /E/E? It normally comes with recent version of myHack unless I'm mistaken. Which version of myHack are you using by the way?
  16. can you post the output of Terminal command lspci -nn?
  17. Look it up in your BIOS (press F2 at Dell logo when you switch on/reset the laptop). WXGA+ is normally 1440x900. The DSDT table is different and using the wrong one will give you a black screen.
  18. Well... come back when you've sussed it out, because it's critical!
  19. Go to driver's details and get the info about PCI Vendor id + Product id (VID/PID). Eg: You can then compare with the info published in the supported/unsupported wireless cards thread that you'll find in R&D forum section.
  20. Post your model specs (eg: D620 Intel HiRes, D630 nVidia LoRes, etc.) and I'll send you a complete /Extra pack.
  21. Post us the output of Terminal command lspci -nn (needs lspcidrv kext in /E/E, normally installed with myHack). In Windows, look under Device Properties. Failing that, open up your laptop and look for the card. Dell have instruction manuals on their web site for opening up the laptop.
  22. I think I noticed a kext called X3100 in the pack; try to remove it to see if the machine can boot using vanilla graphics kexts.
  23. No issue, that's the place to do it.
×
×
  • Create New...