Jump to content

abrellm

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by abrellm

  1. Tried with GenericUSBXHCI kext above and updating the info.plist but still didn't work. It seems AppleUSBEHCI.kext is always loaded as the USB Controller. I've also tried removing AppleUSBEHCI.kext from the plugins inside IOUSBFamily.kext (to try to force it to use the GenericUSBXHCI,kext) but that stopped all the Bluetooth and USB related devices as well and running kextstat does not indicate that GenericUSBXHCI is loaded. Appreciate any more ideas/things I can try to make this work....
  2. Ok. So I've found that the issue was with that model of docking station that I was using with. I've tried with a smaller docking station (which only has 1 DVI, 1 DP, 1 VGA port) and it works perfect with the DP port.
  3. Thanks Herve. I am already on A13. But its still Hi-Speed only. Are you getting Super-Speed on your E6440?
  4. I tried that but it doesn't detect any additional displays when docked. My docking station is one that has 2 DVI outputs and a VGA output. I've tried with both the DVI outputs and both are not detected. I'm looking at the AppleIntelFramebufferAzul kext and here's what they look like. 0000 0800 0200 0000 3000 0000 0105 1200 0008 0000 8700 0000 0204 0900 0004 0000 8700 0000 FF00 0000 0100 0000 4000 0000 If I understand this right, the red coloured 12 and 08 were patched from 09 and 04 respectively from the info provided by Jake Lo - which enabled the HDMI out....... I was just looking at Pike's post on the AppleIntelFramebufferAzul kext and am I right to say that the value was changed to 08 (from 04) so that it references the HDMI connector-type? Pike's post provided the list of values for each connector-type and HDMI is 00 08 00 00 If so, may I know what is the value change from 09 to 12 for? Would patching the 0004 0000 on the 3rd line to 0400 0000 make it so that the 3rd connector-type is DVI thus enabling the DVI port on the docking station? I do apologise if I am not making sense here.. but I really am interested to learn and understand the logic behind these changes. Thank you in advance.
  5. Herve, I've setup 10.10.5 with my Dell E6440 but can;t seem to get the display output to DVI when docked. As you mentioned, pressing Fn-F8 will result in corrupted screen (which is fixed by closing the lid and reopening it). I've got 2 DVI and 1 VGA port on the docking station but none of them worked. I'm currently using the DSDT that you posted on your guide to install Mavericks/Yosemite on the E6440 and the patched AppleIntelFramebufferAzul and AppleIntelHD5000 kexts which got the HDMI port on the back of the laptop working. Did you do anything extra to get your E6440 to work with the docking station?
  6. Does anyone here have USB 3.0 (Super speed) working? Or is Hi-Speed the best we can get?
  7. Hi everyone, I've got 10.10.5 installed successfully on my Dell E6440 Core i7-4600M following Herve's excellent thread for setting up Mavericks and Yosemite on the Dell E6440. However, it seems that I am only getting USB 2.0 working... I've tried: 1. Running System Report shows that my USB is "USB Hi-Speed" which as I understand it to be USB 2.0. See attached screenshot. 2. I've also connected an external HDD which runs with blue led when its USB 3.0 and white when its USB 2.0. When I connect it to my Dell, I am only seeing a white led... I've checked around the internet and it seems so far people are getting USB 3.0 (USB Super Speed) by using the GenericUSBXCHI.kext which I have been using as well. Can anyone let me know if they have got USB Hi-Speed or USB Super-Speed on their System Report? And if you have Super-Speed, can you let me know if there was anything special you did to get that working? Thank you in advance.
  8. Hi, I've been encountering random PM issues with my 10.10.5 Dell E6440 setup. Basically sometimes when I startup, after the initial Clover boot loader loads, the screens turn dark and if I leave it running, the system will startup and automatically goes in sleep mode. I then press the Power button and the system comes back to the login screen. When this happens, I notice that the battery status indicator on the menu is gone and when I go to System Preferences->Energy Saver and try to check the "Show battery status in menu bar" checkbox, it will check and then 1 second later uncheck itself. Energy Saver will also report a 0% battery charge. It is as if OS X is not seeing the battery at all. Has anyone encountered the same issue?
  9. Hi Jake or Forum Admin, I discovered that the 10.10.5_AppleIntelFramebufferAzul.kext shared in the following locked thread was not fully patched hence giving some issues when hot plugging the HDMI. https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemite/ I've patched it completely and put it here. Since the thread is locked, could you update the locked thread with this updated kext? I found that thread tremendously useful and have guided me to successfully setup Yosemite on my Dell E6440. I am sure it would be a great help to anyone who wants to setup Yosemite on their Dell E6440. I also included my SSDT that works with the Core i7-4600M CPU that's on my laptop. The one on the thread was for the Core i5. Thanks SSDT.zip AppleIntelFramebufferAzul.kext.zip
  10. Thank you Jake. I didn't manage to test the patch you made but I decided to re-setup with Yosemite and the kexts in the post did the trick. I can now hot plug and unplug HDMI. The issue now is when I plug in the HDMI cable, the display is only shown on the TV and my notebook display will be blank. Opening up Displays preferences only shows the TV panel with no options to mirror or extend desktop. The system will also not boot up if the HDMI is connected. Is this the expected behaviour?
  11. Hi Jake, Thank you for the response. I patched it but the issue still remains. I am not sure if I patched it correctly though. I patched it by using 0xED via finding and replacing as well as using the perl method. I attach both the original AppleIntelFramebufferAzul.kext and the patched one with this post. Some additional info... I have deployed the patched version using multiple ways.... 1. Just copy and paste the patched file over the original file in S/L/E 2. Did step 1 and then run myFix 3. Copied the patched file into the Extra/Extensions folder and then using myHack to Install Extra into the system. I'm not sure which is the best way to deploy the patch. Appreciate your guidance as well. Thank you again! patched.zip original.zip
  12. Hi everyone, I've just managed to setup Mavericks 10.9.4 (and then upgraded to 10.9.5) following this guide: https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemite/ All is working well (Intel HD 4600M with QE/CI) and I have used the DSDT in the post together with SSDT that was generated for my i7. However unlike the author of the post (Herves), I can't manage to connect a HDMI output to my e6440. The moment I connect the HDMI, the computer freezes up. And if I reboot with the HDMI connected, I will not be able to reboot successfully. The post above mentions something about a patched Azul frame buffer - and I have gone to https://github.com/Piker-Alpha/AppleIntelFramebufferAzul.shand ran the patch against my AppleIntelFramebufferAzul.kext by running... sudo ~/AppleIntelFramebufferAzul,sh 0x0a260006 show and then selected Patch to patch it. Rebooted but the issue still remains. I've tried searching for other posts about this issue and it always seem to suggest that the Framebuffer needs to be patched. Would appreciate any guidance at all on this matter. Thank you!
×
×
  • Create New...