njbhvgfcd

Audio is back now, thank you. Since the display now sleeps fine with the lid open, I think this is okay. Thank you! If you do find a solution for the hanging after opening the lid, let me know, but I don't really need that to work.

The sound output device is gone now, by the way (it worked out of the box before). ACPIPoller.kext is installed in /Library/Extensions/ACPIPoller.kext and active, according to kextstat (com.rehabman.driver.ACPIPoller (0.8.1)). I didn't install it myself, it came with your tutorial etc. (I guess you wanted to make sure that it's actually on, or should I remove the kext?) I can confirm now that this only happens when the lid is closed and at least 30 10-30 seconds have passed, then it will reliably happen. I am not able to make it hang when turning off the screen and leaving the lid open. As long as I can have my sound back, I am happy to leave the lid open when it's turned on... since I can now put the display to sleep just fine.

With the files from the updated zip archive the laptop boots just fine, but the problem with closing the lid and Sierra hanging occurs again, there is a 50:50 chance that it crashes upon opening the lid. I couldn't make it crash from display sleep with the lid open though.

I put those files into the 'patched' folder and replaced the existing ones (I think this was the right folder?). After a reboot it doesn't start up anymore, shows the forbidden sign. Verbose mode says 'waiting on boot-uuid-media' and eventually 'Still waiting for root device.'

Here is the origin folder. Now that I have a 4k capable displayport cable I noticed that video playback is very limited, both 1080p x264 and 4k videos are stuttering a lot. But that might be a limitation of the laptop, not indicating a problem with the Sierra. (When I read that the cpu is capable of 4k playback I assumed that refers to playing 4k material on a 4k screen...) I'll test this with linux/windows perhaps, just to make sure. Otherwise I am happy to see that even a 4k screen is supported out of the box, at 60Hz. origin.zip

It's running the latest BIOS, A14, that it came with. To make sure it's not an issue with the lock screen, I disabled that so that I end up on the desktop upon turning on the display. And that works, except that I too get the spinning ball there and it hangs forever. What exactly can I do? A pointer in the right direction would be more than enough, but I am not sure what exporting raw files means. Thanks!

Now I discovered a new issue: When I turn off the screen or close the lid and wait for at least two minutes, when I try to use it again the screen will turn on but remain blank, or after a while show the login window and hang with the spinning ball of death while the hdd led is going crazy. After resetting the laptop I find the same log entry over and over again: "com.apple.xpc.launchd.domain.user: Service sets EnableTransactions=false and EnablePressuredExit=true, which makes no sense. Enabling Transactions." I can reproduce this about every second time I turn off the screen. I turned off any hibernation/standby and even installed the SleepLess utility to prevent sleep with lid closed, and I verified that I can still ping the laptop with the lid closed. (Power light stays on too of course.) So it's not a standby issue. Forget the smart card reader, that's a luxury. But turning the screen off is a bare minimum to work with a laptop... thanks!

I got everything working other than the integrated Broadcom 5880 smartcard reader - there even is a driver included in macOS Sierra, but it is not showing up in the USB device tree to begin with and the driver reports no hardware found. Is this a hardware issue? I wouldn't need the wireless RFID function, just the smartcard slot. (If only I could find an antiglare+fullhd+IPS screen for this nice e7250, instead of the bad panel installed now, that's bothering me more than the smartcard reader.)

It worked! Thank you

So much for working perfectly: I checked the values in windows, they were as expected 0x15b and 0x15c. Then I changed them to 0x3 which worked as well. Now when I double-check the changes by entering setup_var 0x15b (I rebooted first to make sure the changes were actually saved) I receive: successfully obtained "setup" variable from VSS expected a differentt size of the setup variable. continue with care... offset 0x15b is: 003 So the change was done in BIOS, but the "dedicated video memory" entry in Windows remains at 128MB and in BIOS it keeps showing 64MB, macOS Sierra still panics. It all looks the same. I followed the guide to the latter (because obviously I didn't want to damage the BIOS), so I don't know what I am supposed to do next...

I see. I am wondering if the DVMT change will actually work, since the patch method I used should have worked as well and it did not. There is something in the firewolf instruction that I probably should double check: Then open your DSDT, find Device (GFX0) or Device (IGPU) or Name (_ADR, 0x00020000) and add the Device-Specific Method. Not sure if that is already applied.

That did not work. I patched the file /System/Library/Extensions/AppleIntelBDWGraphicsFramebuffer.kext/Contents/MacOS/AppleIntelBDWGraphicsFramebuffer with Find: 89 45 C8 39 C7 76 4F Replace: 89 45 C8 39 C7 eb 4F but the same kernel panic occurs on startup. Maybe I patched the wrong file, or I patched it with the wrong values? My ig-platform-id in the config.plist is 0x16260006, that is unchanged from the files you provided. Perhaps that's not the right hex value to inject? I'll keep reading, thanks for the assistance, I appreciate it!

I am just a bit worried about damaging this laptop, so I'd prefer not to modify the BIOS if I can avoid it. I will try to patch the AppleIntelBDWGraphicsFramebuffer file according to the firewolf guide.

Oh god. It actually does work, the disk is showing up now. Using those old E7x50_Clover files led to the whole issue. I'll try installing it now. Thank you so much, you have no idea how glad I am... /edit: It booted successfully. There is no kext loaded for graphics yet, but hopefully with the information in this thread I'll be able to make it work.

I have the intel i5-5300U, it says in this thread somewhere that it does not have to be modified to 96MB, the default of 64MB ("video memory" in the bios) is fine. Does the mod still have to be done? As somebody else in this thread had the issue with a kernel panic, removing the ig-platform-id is the only way for the setup to not panic and actually start. I changed it back to the sierra files, I will check now if it works...

I did. I dropped the ACPI and kexts folder into the EFI/CLOVER directory, as well as the config.plist. But it wouldn't boot (kernel panic), I added this to the folder (DSDT.aml, ssdt.aml and new config.plist) to make it go to the setup (attachment E7x50_Clover.zip): https://osxlatitude.com/index.php?/topic/7844-e7250/page-2&do=findComment&comment=49828 Finally it would kernel panic because of the graphics card, so I removed those two lines from the config.plist: ig-platform-id 0x16160002 Sorry - i should have mentioned that. I wonder if there might be an issue with the fact that your files are for e7450 and i have a e7250, for example the boot argument nv_disable=1 makes no sense when my laptop does not have any nvidia graphics, right? I don't know too much about this, I admit.

Thank you, but that's exactly what I did. I just received this laptop today, reset the BIOS, installed opensuse linux just to make sure the hardware works (it sees the ssd and installs/boots from it), Legacy rom + UEFI is enabled by default, so I just switch from RAID to AHCI. As I said, I followed your instructions (for El Capitan, but you wrote that the same instructions work for macOS Sierra) exactly line by line and really did not miss any steps. Thanks for the quick reply, hopefully there is something I can check, a log file perhaps? Or maybe there is a special sata kext that I should check for?

Hello everyone, My e7250 sadly does not recognize the internal ssd (it is the regular 128GB Samsung one from Dell) when starting the macOS Sierra installation. It shows up neither in Terminal with diskutil list nor in the Disk Utility with the GUI. Is there any way to proceed? I set the mode to AHCI of course and followed all other instructions exactly. Thanks!