Jump to content

[GUIDE] OS X Lion on ThinkPad W520


gothic860
 Share

107 posts in this topic

Recommended Posts

@nukedeath:

 

In my experience, speedstepping has a lot to do with your choice of the SMBios. Which are you using? Before generating my custom SSDT, MSRDumper-Readings were all over the place when switching SMBioses.

You could try to find out which MacBookPro-SMBios matches your configuration closest (for me it was MacBookPro8,3, make the processor a priority when comparing!) or try to generate your SSDT with the script by RevoGirl.

 

Using the right SMBios, at least for me more states showed up, even before generating my own SSDT. One more trick: When using the MacBookPro-SMBios, the Info.plist within AppleGraphicsPowerManagement.kext needs to be updated for proper GState-Management when using the NVidia Card. I did overwrite the first Entry under MacBookPro(8,3) with the corresponding one from MacPro(5,1) (with the edited device and vendor-id, plus the custom GStates) and left the second entry as is, hoping it would have to do with integrated graphics. Turns out that it worked, and now I don't have the stuttering GUI problem when using NVIDIA+MacBookPro SMBios. When trying to get Intel HD3000 graphics to work, it is also mandatory (in my knowledge at least) to use the MacBookPro SandyBridge-SMBios (or MacMini, although I am not quite sure on that one). Still on 10.7.3, so maybe there are other problems prohibiting the speedstepping from working.

 

Also: Are you using the Legacy AppleACPIPlatform.kext (Version 1.3.5)? For me, it was the only way of getting sleep to work correctly, without having dead USB 2.0 ports after waking up.

 

There is another issue i am facing: I am using this kext for Battery, which was originally suggested by gothic 860: http://www.insanelym...dpost&p=1772114

Using it, when the battery reaches 0%, the system does not do the emergency sleep, it shuts down, as if i was to pull the plug. Because this is not a really healthy behaviour, I have created an Applescript which starts at boot and polls the battery, initiating sleep manually when the battery is nearly empty. But the more elegant solution of course would be for the OS to recognize it in the first place.

 

So, to all who have the battery indicator working: Does your system go to sleep if the battery reaches 0%? Or does it behave like mine? How could we fix this in a better way?

  • Like 1
Link to comment
Share on other sites

@Kupolski:

 

Hello!

I am using MacPro5.1, tried changing to MacBookPro8,3 with no luck. Have tried generating an SSDT but seems like it didnt change anything. Going to try more later tonight, i wont dare do anything right now in case it kernel panics when im not at home ^^.

 

Sleep does not work with my W520 yet, but really I don't need it. It boots up quite fast using SSD so i will try to fix speedstepping first.

 

EDIT: After trying hard, speedstepping on 10.7.4 is too hard :/

 

EDIT2: 10.7.3 with this patch AICPMPatch by el coniglio (olarila site) and SMBIOS for macbook pro 8,3 worked quite well, now i get more than two states: 11.07.12 22:59:44,000 kernel: MSRDumper PStatesReached: 8 24 32 34 35

 

EDIT3:

Also: Are you using the Legacy AppleACPIPlatform.kext (Version 1.3.5)? For me, it was the only way of getting sleep to work correctly, without having dead USB 2.0 ports after waking up.

No, its my USB3 ports that are dying, the combo/sata port works fine.

Link to comment
Share on other sites

  • 3 weeks later...

@nukedeath:

 

 

 

Hello,

 

what did you do to install 10.7.4? If I use the combo updater and patch the relevant extensions, but when booting it just hangs after loading the extensions, the last one being VoodooBattery (If I remove that, the result is the same, and the last message is about the wireless interface). Any clue?

 

Regards,

 

EDIT: I fixed it just repeating the expected steps, it seems that I've not patchet de RTC kext in the right way, and that was blocking the boot process. No everything is working with 10.7.4. So now I have a W520 triple booting without problems, but I've ordered a Retina Macbook Pro... need to try the real thing :-D

Link to comment
Share on other sites

  • 3 weeks later...

Hi Guys.

I have a dual boot Windows 7 and Lion 10.7.4. Everything is working except the sound. I have been trying to make sound work for quite some time now but to no avail. SystemInfo.app shows i have a 1c20 Audio Controller.

 

i have an Intel HD audio Controller, an HDMI (Intel HD3000 Graphics) and in Windows Device Manager i can see Conexant (14f1 5069). Also in Windows Device Manager i can see Intel Display® Audio (2805 8606) which is different from what i see in Mac SystemInfo.app (Downloaded from this forum) which is 1c20. I am confused.

 

None of it is working. Speaker on Menu bar is enabled after installing VoodooHDA-v2.7.2 (1c20x8086 already mentioned in info.plist) but no sound at all. I tried alot of kexts but nothing is working.

 

Any suggestions in this regard will be highly appreciable.

 

Thanks

Link to comment
Share on other sites

  • 4 weeks later...

Hi, I'm very new to OSx86 so I'm very sory about any silly questions in advance... but I'm been looking for a solution for quite some time and finally decided to ask here as I'm not getting anywhere :-(

 

I've installed Mountain Lion 10.8.1 using ###### on my W520 and now I'm trying to sort out HW using the guide here but my W520 always get stuck after the reboot.

 

I know this guide is for Lion distro... but I believe some steps may be the same - so I've been trying to follow this guide.

 

I started with the chameleon and made org.chameleon.Boot.plist and SMBios.plist files and placed them in /Extra, than I run ###### 5.0.2 looking slightly different - screenshot enclosed. After reboot my OSX is stuck. I also tried to install VoodooHDA-2.7.3 but during OSX start I got a lot of terminal text and OSX got stack as well (both installations gone throught no problem, also tried them separately - in all three cases the same result)

 

Anybody any idea what I'm doing wrong? Any help will be very appreciated....

 

Tomas

post-1076506-0-20528400-1347218139_thumb.jpg

Link to comment
Share on other sites

  • 2 weeks later...

Hi,

Following this thread and Joshh's I got my ThinkBook Pro W520 working perfectly on Mountain Lion 10.8.2. Thank you all very much for all the info.

 

At this point, I'm trying to fix a couple of quirks left on my machine and would need some precisions on the kexts and DSDT edits I need to fix it.

 

1- Battery Indicator: I've tried VoodooBattery and a couple of patched AppleSmartBatteryManager kexts without success. At the moment I have what I think is the latest VoodooBattery.kext and no ASBM.kext, but the system's battery indicator shows No batteries available and power source: Battery all the time. I have not edited my DSDT as I wasn't clear on what parts needed to be modified. Also, I'm not sure which ACPIPlatform.kext I'm using.

 

2- AGPM: I'm using the MacBookPro8,2 SMBios and am getting great results with speedstepper and TurboBoost using a custom SSDT generated from RevoGirl's script. But the MBP8,2 section of AGPM is very different from the MacPro5,1.

 

@Kupolski: could you upload your AGPM kext so I could see what you did to have it working? I'm not sure at what line I need to copy the Cards entry from MacPro5,1. I'd also like to know if you or anyone else know the best custom thresholds for the Quadro 1000m.

 

3- Quadro 1000m DSDT injection. I'm completely lost here as I can't seem to figure out what I need to change from Gothic860's guide to make it work with the 1000m.

 

4- Thermal Zones: I tried wrapping my head around it, but whenever I tried to apply what Gothic860 had, my DSDT would not compile without errors. Maybe one of you can explain it better or show me how to do it properly. I don't mind a bit of fan noise if it's gonna keep the temperatures down.

 

Apart from that, everything works like a charm (sleep, SD Card Reader, sound, etc). Mountain Lion is a real improvement over Lion for my machine and is the better performing OS on it surpassing both Windows 7 and Ubuntu 12.04.

 

I've attached my DSDT if someone is able to help me -> http://dl.dropbox.co...XStuff/dsdt.aml

Thanks a lot.

Link to comment
Share on other sites

Hi Simon,

 

Would you be please so kind and summarize what you've done? I have exactly the same W520 like you.. but get all sort of troubles running 10.8.1 on it. Did you manage to make the original intel wifi work? What kexts did you use for the soundcard? Card reader? None if mentioned work for me....

 

Thank you,

 

Tomas

Link to comment
Share on other sites

@xxxhonyy

For sound I followed joshhh guide. I'm using the patched AppleHDA.kext that I had in 10.8.0 and the DSDT edit he mentionned in this thread in the post right above mine. For the SD card reader, I use VoodooSDHC kext. I've attached both kexts.

 

EDIT: The WiFi cards provided by Lenovo are not compatible with OSX. I don't have WiFi for now, but I'm looking to get a usb WiFi adapter that works with OSX. The one I'm looking at is the Asus USB-N10. When I get confirmation that it works in ML, I'm buying it and will finally have all the features of my computer in order.

AppleHDA.kext-cx20590.zip

VoodooSDHC.kext.zip

Link to comment
Share on other sites

Hi Simon, I'm really sorry to trouble you again with this but my osx86 ended up belly up and i cant start it up and restoring again :( would you do me a massive favour and explain me a bit more in details how you have done it, what tools did you use? I'm trying to apply what you say on Gothic's guide.. but i've probably misunderstood something and so i keep breaking my system over and over. Did you use ##### at all? (what setting?) how did you get your smbios.info and the othe info file to the system?

 

I'm sure you know this but you can get a replacement for your internal wifi card that's suppose to work (one with atheros chipset listed here / ebay - 5$)

 

Is your USB3.0 working as well? The webcamera?

 

Tom

Link to comment
Share on other sites

  • 6 months later...

You have to patch you apple hda with following command

 

sudo perl -pi -e 's|\x84\x19\xd4\x11|\x6E\x50\xf1\x14|g' /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA

 

And yes I use older ACPI Platform to get working battery detection

 

Last - your pin configuration from windows may not be working solution at all, mine config from win 7 wasn't right and I changed it a lot to get speakers and mic working

 

If you have linux codec dumps or voodoohda dumps we can try to make applehda config for cx20590 together

 

ps. T510/510i has cx20585 codec

 

If T510/510i is CX20585, why not try AppleHDA.kext for T410? As T410 is CX20585 too.

Link to comment
Share on other sites

  • 1 year later...

what's up guys? haven't been here in a minute. did a fresh install of mavericks 10.9.2, following the previous procedures, but only getting a score of 4.12 in Cinebench (v11.5) as opposed to Gothic's 5.31

 

10.9.2 / i7-2720QM / 16gb / quadro 1000

Link to comment
Share on other sites

  • 6 months later...
  • 3 weeks later...

Hi there,

I have managed to get my W520 running Yosemite 10.10.1 with Intel Graphic,

I have never managed to enable the NVIida Quadro 1000m. I need help. Can you please advise where can I start?

I'm using Clover, I've tried to inject NVIdia to enable the original kexts, but that never worked.

 

Please help.

Link to comment
Share on other sites

  • 3 weeks later...

Hi there,

I have managed to get my W520 running Yosemite 10.10.1 with Intel Graphic,

I have never managed to enable the NVIida Quadro 1000m. I need help. Can you please advise where can I start?

I'm using Clover, I've tried to inject NVIdia to enable the original kexts, but that never worked.

 

Please help.

I confess I've yet to get anywhere with Yosemite and Clover, but I was having constant issues getting the 1000m in my W520 working on any version of Mavericks past 10.9.1 until I updated Chameleon to r2516 and changed my smbios so that I'm now a MacPro5,1. At that point it Mysteriously Just Worked. :)

 

I also long ago patched my DSDT to inject graphics info, which might make a difference; on the off chance it helps, here's the DSM I have for Device VID:

                    Method (_DSM, 4, NotSerialized)
                    {
                        Store (Package (0x22)
                            {
                                "AAPL,backlight-control", 
                                Buffer (0x04)
                                {
                                    0x01, 0x00, 0x00, 0x00
                                }, 

                                "@0,backlight-control", 
                                Buffer (0x04)
                                {
                                    0x01, 0x00, 0x00, 0x00
                                }, 

                                "AAPL,slot-name", 
                                Buffer (0x09)
                                {
                                    "Build In"
                                }, 

                                "@0,built-in", 
                                Buffer (Zero) {}, 
                                "@0,pwm-info", 
                                Buffer (0x14)
                                {
                                    /* 0000 */    0x01, 0x14, 0x00, 0x64, 0xA8, 0x61, 0x00, 0x00, 
                                    /* 0008 */    0x1C, 0x02, 0x00, 0x00, 0x64, 0x00, 0x00, 0x00, 
                                    /* 0010 */    0x00, 0x04, 0x00, 0x00
                                }, 

                                "@0,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 

                                "@0,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 

                                "@0,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-A"
                                }, 

                                "@1,compatible", 
                                Buffer (0x0B)
                                {
                                    "NVDA,NVMac"
                                }, 

                                "@1,device_type", 
                                Buffer (0x08)
                                {
                                    "display"
                                }, 

                                "@1,name", 
                                Buffer (0x0F)
                                {
                                    "NVDA,Display-B"
                                }, 

                                "NVCAP", 
                                Buffer (0x18)
                                {
                                    /* 0000 */    0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 
                                    /* 0008 */    0x3E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, 
                                    /* 0010 */    0x00, 0x00, 0x00, 0x00
                                }, 

                                "NVPM", 
                                Buffer (0x20)
                                {
                                    /* 0000 */    0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
                                    /* 0008 */    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
                                    /* 0010 */    0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 
                                    /* 0018 */    0x00, 0x00, 0x00, 0x00
                                }, 

                                "VRAM,totalsize", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x80
                                }, 

                                "device_type", 
                                Buffer (0x0C)
                                {
                                    "NVDA,Parent"
                                }, 

                                "model", 
                                Buffer (0x15)
                                {
                                    "NVIDIA Quadro 1000M"
                                }, 

                                "rom-revision", 
                                Buffer (0x0F)
                                {
                                    "70.18.87.00.00"
                                }
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }
  • Like 1
Link to comment
Share on other sites

  • 2 months later...
  • 5 months later...

I have successfully made my W520 works like a charm with HD3000 under 10.10.5, thanks everyone this forum!

 

Still little problem, I can't fix Nvidia 2000m, when I adapt every fix/patch and update the bios setting, and boot into 10.10, it' black screen.

My W520 still works, I can login by teamviewer, and do some modifies, change edid, change DSDT (it should work already, cause I use gothic860's version), modify AppleGraphicsPowerManagement.kext (and update permission).

I will try NVCAP later, to see if it works. 

Link to comment
Share on other sites

  • 4 months later...
  • 1 month later...

My W520 is working mostly great under Yosemite 10.10.5.  Mine is a Quadro 1000m, 1080p, 8gb ram, and i7 2720qm.

 

Problems I'm having:  

 

Quadro 1000m:  The DSDT I'm using is from someone else's laptop with a 2000m, but the laptop works on Intel graphics only.  It's ok with me, as I only use the Quadro when I boot into Windows.

 

Trackpoint:  about 75% of the time, the Trackpoint does not work.  Touchpad always works, just not the nub.  No idea why.

 

I've uploaded the kexts and DSDT I'm using.  I'm running Clover R3292 - install that first, then put the kexts where they need to go (which should be noted in the zip).  This should hopefully help someone get their machine working, but also help someone perhaps let me know what I'm missing for the Trackpoint issue.

 

In addition, if anyone knows how to enable the Trackpoint WITHOUT the touchpad and still have middle button click and scroll, I will love them forever.

W520 Yosemite Squid 1.0.zip

Link to comment
Share on other sites

  • 8 months later...

After successful installation of my macOS Sierra on my W520 and Nvidia 1000m, I received first kernel panic. Any clues?

 

*** Panic Report ***

panic(cpu 2 caller 0xffffff8000409f4a): Kernel trap at 0xffffff7f827dde5e, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000344df515e, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0xffffff819e1fc1e0, RCX: 0xffffff802924b000, RDX: 0xffffff80208f0330
RSP: 0xffffff9204fc3880, RBP: 0xffffff9204fc38a0, RSI: 0x000000000000702b, RDI: 0xffffff80208f0330
R8:  0xffffff9204fc34c0, R9:  0xffffff9204fc34b8, R10: 0x0000000000000000, R11: 0xffffff81dcac6058
R12: 0xffffff802131c000, R13: 0x0000000000040000, R14: 0xffffff819e1fe058, R15: 0xffffff819e1fb000
RFL: 0x0000000000010246, RIP: 0xffffff7f827dde5e, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0
 
Backtrace (CPU 2), Frame : Return Address
0xffffff9204fc3510 : 0xffffff80002f748c 
0xffffff9204fc3590 : 0xffffff8000409f4a 
0xffffff9204fc3770 : 0xffffff80002a9743 
0xffffff9204fc3790 : 0xffffff7f827dde5e 
0xffffff9204fc38a0 : 0xffffff7f827bec1c 
0xffffff9204fc3900 : 0xffffff7f827be4c3 
0xffffff9204fc3960 : 0xffffff7f826fab93 
0xffffff9204fc3990 : 0xffffff7f827008e7 
0xffffff9204fc39e0 : 0xffffff7f827bf5cb 
0xffffff9204fc3a30 : 0xffffff7f826f87fc 
0xffffff9204fc3ac0 : 0xffffff80008e7d39 
0xffffff9204fc3b20 : 0xffffff80008e5d62 
0xffffff9204fc3b80 : 0xffffff80008eed31 
0xffffff9204fc3cc0 : 0xffffff80003c9968 
0xffffff9204fc3dd0 : 0xffffff80002fc23c 
0xffffff9204fc3e30 : 0xffffff80002d9b51 
0xffffff9204fc3e80 : 0xffffff80002ed6e7 
0xffffff9204fc3f10 : 0xffffff80003f600e 
0xffffff9204fc3fb0 : 0xffffff80002a9f66 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f826f3000->0xffffff7f82792fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80bd1000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f8127c000
         com.apple.GeForce(10.1.2)[FC349F8C-5043-3B46-A796-6CC097BFB1B2]@0xffffff7f82793000->0xffffff7f82836fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80bd1000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[C1544DFB-9066-340F-AD0A-9302DC3E6841]@0xffffff7f81455000
            dependency: com.apple.nvidia.driver.NVDAResman(10.1.2)[5DD89348-73FE-38C1-87A2-FE664001CBAA]@0xffffff7f81683000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f8127c000
            dependency: com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f826f3000
Link to comment
Share on other sites

 

After successful installation of my macOS Sierra on my W520 and Nvidia 1000m, I received first kernel panic. Any clues?

 

*** Panic Report ***

panic(cpu 2 caller 0xffffff8000409f4a): Kernel trap at 0xffffff7f827dde5e, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000344df515e, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0xffffff819e1fc1e0, RCX: 0xffffff802924b000, RDX: 0xffffff80208f0330
RSP: 0xffffff9204fc3880, RBP: 0xffffff9204fc38a0, RSI: 0x000000000000702b, RDI: 0xffffff80208f0330
R8:  0xffffff9204fc34c0, R9:  0xffffff9204fc34b8, R10: 0x0000000000000000, R11: 0xffffff81dcac6058
R12: 0xffffff802131c000, R13: 0x0000000000040000, R14: 0xffffff819e1fe058, R15: 0xffffff819e1fb000
RFL: 0x0000000000010246, RIP: 0xffffff7f827dde5e, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0
 
Backtrace (CPU 2), Frame : Return Address
0xffffff9204fc3510 : 0xffffff80002f748c 
0xffffff9204fc3590 : 0xffffff8000409f4a 
0xffffff9204fc3770 : 0xffffff80002a9743 
0xffffff9204fc3790 : 0xffffff7f827dde5e 
0xffffff9204fc38a0 : 0xffffff7f827bec1c 
0xffffff9204fc3900 : 0xffffff7f827be4c3 
0xffffff9204fc3960 : 0xffffff7f826fab93 
0xffffff9204fc3990 : 0xffffff7f827008e7 
0xffffff9204fc39e0 : 0xffffff7f827bf5cb 
0xffffff9204fc3a30 : 0xffffff7f826f87fc 
0xffffff9204fc3ac0 : 0xffffff80008e7d39 
0xffffff9204fc3b20 : 0xffffff80008e5d62 
0xffffff9204fc3b80 : 0xffffff80008eed31 
0xffffff9204fc3cc0 : 0xffffff80003c9968 
0xffffff9204fc3dd0 : 0xffffff80002fc23c 
0xffffff9204fc3e30 : 0xffffff80002d9b51 
0xffffff9204fc3e80 : 0xffffff80002ed6e7 
0xffffff9204fc3f10 : 0xffffff80003f600e 
0xffffff9204fc3fb0 : 0xffffff80002a9f66 
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f826f3000->0xffffff7f82792fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80bd1000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f8127c000
         com.apple.GeForce(10.1.2)[FC349F8C-5043-3B46-A796-6CC097BFB1B2]@0xffffff7f82793000->0xffffff7f82836fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[731443D8-78D5-30C8-939A-1ED3E857CA22]@0xffffff7f80bd1000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[C1544DFB-9066-340F-AD0A-9302DC3E6841]@0xffffff7f81455000
            dependency: com.apple.nvidia.driver.NVDAResman(10.1.2)[5DD89348-73FE-38C1-87A2-FE664001CBAA]@0xffffff7f81683000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[377FAA09-C02F-3FF4-A5DE-C0F2E711C8B0]@0xffffff7f8127c000
            dependency: com.apple.iokit.IOAcceleratorFamily2(288.13)[27E0AFCE-E36A-35F5-A008-BB1EB3A2C7B9]@0xffffff7f826f3000

 

strange thing...i run sierra on w520 smoothly....

Link to comment
Share on other sites

strange thing...i run sierra on w520 smoothly....

Is your Airplay working on W520? Can you get the airplay mirroring icon to the menu bar? I think it's possible only when running Intel graphics, with Nvidia it's not possible, I suppose.

Link to comment
Share on other sites

 Share

×
×
  • Create New...