Jump to content

Semaj

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Semaj

  • Rank
    Private First Class
  1. The stock Dell bluetooth module is supported and is separate form the wifi card. check which card you have now, you can pick up a 2.4/5ghz Broadcom 43xx card for little and that will work with kexts and if you feeling adventurous rebrand the card to stock Dell. It is not that hard, just don't make any mistakes without a backup of the original 'firmware' file. Other than that it's a matter of booting into a live Linux, downloading some tools, loading the right modules (rmmod wl && mod probe b43) and extract the firmware from the card, then change the vendor/device id in the file and copy the file back to the card. Save the original firmware on external storage before rebooting so you can always restore it. This guide is great, the pictures are broken but it should be enough. In my case after rebranding I also had to change the code (country) and regulatory so it would see my 5ghz channels, but that was also pretty easy. Let me know what you have in your laptop now and we'll see! I picked up quite a few 43xx Broadcom cards from eBay for very little. Once rebranded they will always work without any modifications.
  2. I'm happy to hear you got it working. As for what went wrong for you, I can't really tell from the screenshot. There's some errors about the GPU, was the pic taken at the point it didn't continue anymore? If so then it most likely due to the graphics not being configured properly in your Clover config. If you have Intel graphics your Clover config was not injecting anything Intel and was set to inject both ATI and Nvidia. I have it set to only inject Intel and also changed the platform id to 0x01660003. My guess is that if you had set the graphics properly you would've made it into the installer just fine. Though it might have needed some kexts still.
  3. Successfully running 10.14.2 for a few weeks on my little e6330 now and it's perfectly stable. Using it every day. This setup is perfectly suitable for daily usage. I'm happy with it and excited, want to share my success and process with you all. First off, a very big thank you to Jake Lo for creating the initial bootpack for the e6330 that did pretty much everything already. I merely tested and tweaked it over the past few weeks. My process is fairly simple, tested the steps out a few times on two different e6330's, seems to work fine every time. BIOS settings are the usual for E series found in this forum. I've disabled legacy booting and legacy loading of roms for a "pure" UEFI boot config. This is not needed, I just prefer it. 1: Create a new installer using the createinstallmedia script inside the macOS Installer app and install Clover to it, deselect everything except for the first two options (UEFI boot only and ESP install). Don't unmount the EFI folder after the Clover installation is complete. Make sure you select the right destination. I've installed Clover on my Mac by accident too many times, lol. 2: Delete the EFI folder on the EFI partition mounted by the Clover installer, empty the trash and copy over the EFI folder from the attached zip file. 3: Copy the attached zip file to the installer itself too, you need it after macOS is installed. 4: Boot from the installer and do a clean install. When the system reboots make sure you boot from the installer and select the macOS disk to boot from. On my machines this usually went fine without me paying any attention to it. If you happen to get some error simply reboot and select the internal disk from the Clover menu. It should resume installing. 5: Once installation is complete you should be able to boot into the freshly installed macOS from the Clover menu using the installer for a final time. 6: Go trough the first time setup screens and once on the desktop copy over the attached zip from the installer and unpack it on the desktop. 7: Install Clover like above, make sure you select the internal disk as destination. Leave the EFI partition mounted and delete the EFI folder and copy over the EFI folder from the attached zip file to the mounted EFI partition like above. Don't make a mess and empty the trash. 8: In case you have the Dell bluetooth module, copy the files from the LE folder to /Library/Extensions and rebuild permissions with Kext Utility (included in zip file). If your wifi is not working and you've got a Broadcom chipset, copy the kexts inside the Broadcom-fix folder to the Clover kext folder on the EFI partition that is still mounted. 9: Generate your own SSDT. Download and run this script to generate one and replace the one currently in the /EFI/Clover/ACPI/patched folder on the EFI partition. For the lazy run the command below to generate the SSDT; curl -o ./ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh && chmod +x ./ssdtPRGen.sh && ./ssdtPRGen.sh 10: With your own SSDT in place, the kexts in place and Clover installed to the internal disk it's time to reboot once more. Eject the installer and remove it then reboot the machine and hope for the best! If all went well you now have a pretty much fully working macOS. There are few more things to tidy up and do, let's finish up! Make sure we're not going to hibernate. Open up the terminal app and run the following commands: sudo pmset -a hibernatemode 0 sudo rm /var/vm/sleepimage sudo mkdir /var/vm/sleepimage sudo pmset -a standby 0 sudo pmset -a autopoweroff 0 Check if TRIM is enabled if you're using an ssd, run "sudo trimforce" if it's disabled. Check for TRIM support under SATA in the System Information app. Thats pretty much it. The rest are optional steps, but felt like sharing them too. Unenroll from the beta program. Somehow I was in there a few times, open system preference -> software update and click on details on the left side underneath the icon. You can reset the defaults there. Alternatively you can run "sudo softwareupdate --clear-catalog" in a terminal. Disable spotlight indexing, seems to improve performance and I personally don't use it: sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist Disable gatekeeper (I find the thing annoying): sudo spctl --master-disable Disable sudden motion sensor (use only if you have an ssd): sudo pmset -a sms 0 - Add a decent content blocker to Safari: Open this url; https://safari-extensions.apple.com/?q=ublock (Don't forget to configure regional lists in uBlock settings.) - Change keybindings in System Preferences -> Keyboard -> Modifier keys. Out of the box its ALT = Apple key, Windows key = macOS alt key. Personally I install Karabiner-elements for this, mainly because of the additional options and also because installing it makes F4 and the likes work for launchpad and brightness, just like on Apple keyboards. - You can use Clover Configurator and generate some new IDs and serial numbers in the SMBIOS and System Parameters sections in config.plist inside the Clover folder of the EFI partition. I'm using the RehabMan port of Clover but feel free to install the latest Clover if you wish, they work fine but I prefer to stick with the port. Other stuff you might want to install: - HWSensors: https://bitbucket.org/kozlek/hwsensors/downloads/ - lspci: https://osxlatitude.com/forums/topic/9488-lspci-package/ - homebrew: for lsusb and other a lot of other stuff I use personally: https://brew.sh - iasl https://bitbucket.org/RehabMan/acpica/downloads/ - MaciASL https://bitbucket.org/RehabMan/os-x-maciasl-patchmatic/downloads/ - OnyX https://www.titanium-software.fr/en/release_onyx.html No kexts are needed in /S/L/E. That should make minor macOS (10.14.x) updates install fine and not break much, if anything at all. Oh, if you have a cpu with a turboboost mode you might want to compile and place this kext in /Library/Extensions and rebuild permissions again to prevent turboboost being used whilst on battery. If you get "the internet appears offline" anywhere during installation and find yourself back at the beginning of the installer just disable wifi and try again. This happened to me only once. So what works? Sleep, sound (internal speakers, headphone out and build-in mic), wireless, hdmi output including clamshell mode, lan, sd card, e-sata, graphical h/w acceleration, bluetooth, dvd, battery, sensors, etc, etc. WWAN is untested but there are some kexts for it from what I gathered on this forum. PC Express is also untested. I have no cards for it. What doesn't work? Nothing big really, minor glitches here and there. Nothing more than I have on my MacBooks. Some of them might as well be macOS related bugs. When shutting down there's some graphical glitches happening. Most other stuff has to do with input: - Capslock light doesn't tuns off (double tap also doesn't turn the light off), caps lock itself does turn off. When using an Apple bluetooth keyboard I have the reverse. Capslock never lights up but works fine. Fixed now. It was a bug in Karabiner. - There is a short delay before touchpad works after using keyboard, hard to explain but easy to replicate; hold down a key and move the cursor with touchpad or move the cursor with touchpad and press a key to make the moving stop. This could have something to do with the ALPS kext. Not an issue for me. - Moving icons sometimes produces a weird effect where the icon travels its own trajectory instead of where I'm dragging it. Hard to explain again. Happens very rarely too. Can't seem to reproduce it. - Waking up from sleep can only be done by opening the lid or pressing power button. Bluetooth and usb devices can't wake it up, no problem unless you want to wake the machine while its sleeping in clamshell mode. Another very minor thing is that the Fn+arrow keys to control the brightness sometimes 'fight' with the macOS ones. To get around this use the brightness slider or install the Karabiner app mentioned earlier so you can use F1 and F2 to change the brightness. Maybe there's a way to make them stop 'fighting' but it doesn't bother me and I'm already used to using F1/F2 keys to control the brightness. Personally nothing in there that stops me form enjoying this little laptop for what it is; a great little monster running macOS smoothly. Hope this little guide will help others getting Mojave to run smoothly on their e6330. Resources/kexts/apps used: This forum! RehabMan: https://bitbucket.org/RehabMan/ Lilu: https://github.com/acidanthera/Lilu/releases AppleALC: https://github.com/acidanthera/AppleALC/releases WhateverGreen: https://github.com/acidanthera/WhateverGreen/releases Alps: https://osxlatitude.com/forums/topic/8285-refined-alps-touchpad-driver/ Disclaimer: I have probably made silly mistakes or loaded kexts that aren't really needed. Please point them out to me if you wish, I like to stay minimalistic and only use what's needed. As it stands now this configuration is very workable for me. I'm using the Dell just like my MacBooks. Very happy with it! e6330-osxlatitude.zip
  4. I know fan control is tricky on Dell laptops, but it is possible. I've successfully tested the Windows method on my e6330. The fan noise difference is day and night. Under Windows I've setup a custom profile where the fan won't come on until the Cpu is 75c. This results in a much quieter laptop. I would've opted for a constant low rpm fan speed but the e6330 fan only has 3 speeds, off, 2500-3000 and give or take 5000. Both Linux and Windows use the same technique to take control; disable Dell bios fan control (EC?) via SMM. I haven't tested the Linux apps yet but I assume they work fine. My skills are not that good and I was wondering if it would be possible to do this under macOS as well. It would be awesome to setup my own fan curves like in Windows. Windows: Used a driver and an app (precompiled can be found here) to disable EC and then used HWiNFO to setup a custom fan profile. It works great, downside is that Windows has to run in signing-test mode. Linux: Not tested (yet) but there are a few routes (see this thread (1/2)) to disable the EC and create custom fan profiles. I guess on paper it should be possible to create some kext that will disable EC and then we could use a tool like SMC fan control to setup our own curves. But I have no idea if this is feasible. It would be great to get my macOS as quiet as my Windows on this machine. (PS: I wasn't quite sure where to post this, so I'm sticking to the e6xxx forums, but this should apply to all Dell machines that lack the EC/thermal menu you could make appear with some key combination on the D series.)
  5. Those are some great suggestions again, thanks. I did check the brackets and they seem to seat it properly, I will try the others too. It only takes a tiny bit of force to the module work. A piece of cardboard in between them also works, but it's not stable enough. Tried that. Ran some benchmarks to see if dual channel is faster in Geekbench. Only got about 400 points more with dual channel. Ran the benchmarks a few times to make sure. The speed difference (at least in Geekbench) is not that much.
  6. Thats some very interesting stuff to read, thanks for that! Very educational. I'm surprised Dell put 3 slots in this little laptop. Still not too sure what to do with the top one next to the BT module. Would be fun to put something useful there but no clue as to what The PATA SSD looks very cool by the way, but a bit too slow to put in the machine. Maybe if I can get one really cheap for just storage. I replaced the slow SSD with an old Samsung 840 EVO and it's pretty darn fast. Getting about 400mb/s write and 530mb/s reads depending on the benchmark. Slightly slower write speeds after a while with Blackmagic.
  7. They don't exist? I didn't look for it but read some discussions on the Dell forums about this. Some people think that if it has a controller it will work. I found lot of other fun things to put in those 1/2 size slots like sd card reader or a tiny usb slot to put a wireless mouse/keyboard receiver or something thats fine with usb 2 only. Fun stuff!
  8. Good tip, thanks. Running the latest bios on it, but I will try to downgrade and see if it helps. Update: Downgraded to A08 and then upgrade to A15 but none of them makes the bottom ram slot work so I'm back at A20. I wonder if there's a way to get details about the exact "error" the laptop sees. The blinking pattern means there was ram detected but I have no clue how to get details like some (debug) log. But maybe the slot is just dodgy or broken after all. Update2: The ram slot works if I push down the module a bit while turning it on. So it's dodgy and can work. Guess I need to dust off my soldering iron or place something between the two sticks so the bottom one gets pushed down enough. Progress lol.
  9. Thanks for the reply. Makes sense! So Dell has shipped these laptops with those drives that have firmware updates listed with those disks fitted in the optical bay maybe? Just makes little sense to me that they would offer these firmware upgrades on the e6330 support page if they weren't an option at some point. I'm still tempted to try a disk with build-in SATA controller in it but they're hard to find. Most specs don't list if they have build-in controller or not. Either way, for now I won't be spending any more money on it until I figure out the ram issue. I'll contact Dell tomorrow to see what they can do. It's out of warranty but not for a long time. Maybe 4 months. I also wonder what Dell designed the 3rd 1/2 size slot for that doesn't have any antennas... Intel turbo memory perhaps?
  10. I'm sorry for making another topic. I just think there's a lot of knowledge regarding Dell here and despite my experience in ICT I don't understand this at all. Currently the laptop has 1x 4GB, it came like that from Dell. I wanted to place 2x 2GB as dual channel might improve performance. Somehow the bottom slot isn't working at all. - 1x 4GB in top slot: laptop boots - 1x 4GB in bottom slot: laptop gives me 2 solid and one blinking led which according to the manual means "the memory modules are detected but has encountered an error" - 1x 2GB in top slot: laptop boots - 1x 2GB in bottom slot same blinking error code as above - 2x 2GB occupying both slots, same error code - no ram at all, different error code indicating no ram was found If it was just the ram slot being broken it shouldn't give me the memory models detected error code right? It should give me the no memory installed error instead. Yet with any combination of ram sticks the laptop won't boot as soon as the bottom slot is used. How is this even possible? And if the slot is actually broken it means Dell has never even tested the 2nd slot cuz it has never been used since it was bought. I hope the speed gain running dual channel vs. single channel isn't that much cuz I also have some 8GB sticks laying about. 16GB dual channel would be so nice but impossible as of now. I can't run 2 sticks of ram at all in this laptop. Anyone have a clue what's happening and how to sort this out? I did check the pins of the slot and they all seem fine. I also cleaned it with some alcohol but to no avail. Update: Took the whole laptop apart to check the motherboard, all seems fine and nothing indicating the slot itself is broken, yet my ram modules are all just fine too. Guess I got a lemon where the 2nd ram slot is broken, never worked and never tested by Dell. Kind of annoying but nothing I can do other than buying a new motherboard for it which isn't worth the time or money.
  11. Apparently Dell has sold the e6330 with mSATA disks in what I assume is the WWAN slot. There's a bunch of firmware updates for supported drives and they all seem full sized mPCI cards (see image). I'm guessing they used the WWAN slot as theres only 1 full size slot which is also used by the WWAN card. Now I'm wondering if the e6330 has the WWAN slot (or any of the two smaller ones) connected to SATA directly or does it need a mSATA disk with build-in SATA controller? I can't find much about the specs of the disks listed, so I have no idea if they all have a build-in controller or not. I've found some mSATA disks that should fit but not sure if they will work. Maybe only the Dell "approved" ones will work? On the Dell forums the Dell staff flat out says the e6330 doesn't support mSATA but if thats true then why are there firmware updates for them? Surely they're mistaken and at the time it was possible to buy the e6330 with an mSATA disk. Hopefully someone here can help me out. I will try to find one of the disks listed on the Dell website used on eBay, if they're not too expensive I'll grab one to test. But I can't find them brand new for a reasonable price.
  12. Semaj

    [SUCCESS] Latitude E6330 Mojave Upgrade with Clover

    Thanks for the enlightening reply. You're right that the SSDT-PNLF.aml file wasn't added to the sort order and also right that it fixed sleep, the brightness slider doesn't work though but really a non-issue. So essentially the DSDT you posted doesn't need any extra patches and all my hard work patching was merely educational Thanks for answering my usb question as well. Unless you say there's some big advantage to patching my own DTST I'll just keep using the one you posted as it works perfectly. Edit: the brightness slider is working now. Not sure what did that. Maybe fixing permissions did the trick.
  13. Semaj

    [SUCCESS] Latitude E6330 Mojave Upgrade with Clover

    Joined to say thank you for making and sharing the bootpack, with it I now have macOS Mojave 10.14.2 running in near perfection on my e6330 with A20 bios. I was working on my own DSDT and everything worked fine except for the usb port on the back, I think Rehabman's series 7 usb patch wasn't enabling all the ports. I just couldn't get it to work. Got tired of trying and rebooting and I tried your bootpack and to my surprise all usb ports worked. In fact everything seemed to work just fine! All the basics like audio, graphics, networking and even the sd card! The only things that didn't work are near nitpicking level for a hackingtosh build. But I share them anyways and also also share the fix, if I managed to fix it. When closing the lid the screen stayed on and going into sleep manually was a shallow sleep only. This was fixed by applying _WAK Arg0 v2 and HD4000 brightness fix patch from Rehabman's repo. The laptop now sleeps when closing the lid or entering sleep manually. The power led pulsates. This was really the biggest issue. I consider working sleep an extra for hackingtosh builds, not an essential at all. Very happy this works on top of everything else. I've also experienced some weird dragging behaviour, from time to usually when dragging icons upwards the icon itself changes position, it's hard to explain and happens very rarely and is really not an issue. Sometimes after selecting stuff the selection line stays on and it keeps selecting stuff until cancel is pressed. I had this happen on very old D series builds as well from time to time. I think this was an issue with PS2 kext or something. There's also some graphical glitches when shutting down and the bootup logo has a dark background instead of light. No clue how to fix those. Really not much to complain about to be honest. I'm more bummed out I couldn't get the usb on the back work in my own DTSD, I'm not even sure if it matters much to use my own extracted DTSD or the one you built. Everything works just as well as what I made and it made the usb on the back work Since I wasn't sure which patches were done in the bootpack I applied Rehabman's recommended patches as well. These were: HPET, SMBUS, IRQ, RTC, OS Check fixes and the Mutex with non-zero SyncLevel fix. They might already been applied by you or fixed in another way but I had them applied in the one I was working on. Not sure if any of them are needed for sleep but I really don't wanna try one by one to see which ones are needed for working sleep I did also apply the HD4000 Low Resolution patch hoping it would make brightness control show up in display control panel or fix the garbled display on shutdown and weird dragging behaviour but I don't think this one is needed. The brightness controls didn't show up and graphics were working just fine without this patch applied. For good measure I've attached my DTSD that I extracted and patched up myself and the modified version of the one you posted. Been using it for a few days with great results. I am really curious what in mine would cause the usb port on the back not to work, just for educational purposes haha. I've also attached a compiled version of the modified one from the bootpack just in case someone else with an e6330 wants to give it a try without the need to compile it. To make the e6330 purr all someone needs to do is follow the instructions in your post and replace the DSDT with the one from my post. Thanks again for sharing! Oh yeah, this was needed to stop the panics when booting up. Not sure if all e6330 need to uncheck it but mine did. PS: The e6330 might be old but it runs Mojave like a champ and it only has an older slow ssd, the i3 and 4gb of ram. Very pleased with the performance of this little monster. DSDT.aml.zip DSDT-origin-broken-usb-on-back.dsl.zip DSDT-bootpack-modified.dsl.zip
×