Jump to content

Lenovo ThinkPad T420 with UEFI Only

K0gen

By K0gen,
in Installation Guides

 Share
5,282 posts in this topic

Recommended Posts

tluck
tluck
Posted
Posted

@Somez - what screen saver gizmo are you using? - perhaps try a different one like "Message". if you are not getting BRSYNC etc that is a step in the right direction.

 

@rollitab - if HS is not working well, go with Sierra, It was rock solid. 

Link to comment
Share on other sites
Somez
Somez
Posted
Posted (edited)

@Somez - what screen saver gizmo are you using? - perhaps try a different one like "Message". if you are not getting BRSYNC etc that is a step in the right direction.

 

@rollitab - if HS is not working well, go with Sierra, It was rock solid. 

 

I turned the screensaver off (didn't know it was enabled), but still got the freeze after my LCD turned off after a few minutes. And after rebooting I also see the BRSYNC log entries. On top of that when I uncheck the EDID injection in Clover boot menu, it goes back into checked state after every reboot so I have to turn it off again :)

It's not like it help at all.

 

Just to clarify, I can trigger the system freeze by puting the display into sleep. It's easy because I set the bottom-left corner of the screen as a hot corner and it sends the display to sleep when I move the cursor over there. So it shouldn't be the screensaver.

Edited by Somez
Link to comment
Share on other sites
Somez
Somez
Posted
Posted (edited)

Alright, here is the log:

 

2018-02-07 18:37:02.479789+0100 0x722e     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

 

I put the display to sleep at 19:37, before that I have not seen any log entries for BRSYNC as you can see on the above timestamp.

 

2018-02-07 19:42:11.546209+0100 0x5c65     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:16.550633+0100 0x533      Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:21.553513+0100 0x5c65     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:41.586502+0100 0xd60      Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:46.588793+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:51.599523+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:42:56.623764+0100 0xd60      Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:01.645886+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:06.659507+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:11.661547+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:16.688964+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:21.694100+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:26.708359+0100 0x5eb5     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

2018-02-07 19:43:27.970631+0100 0x5d09     Default     0x0                  0      0    kernel: (AppleIntelHD3000Graphics)     BRSYNC: (0x22040) = 0x0

 
So this confirms that I can trigger the issue with putting the display into sleep mode. I'll set the display sleep to "never" now to see if I can freeze the system if I don't touch the computer but the screen is turned on.
 
Update #1: System hang even though display remained on. I forgot to disable the EDID injection in Clover options though. However no new BRSYNC entries have been written into the log.
Edited by Somez
Link to comment
Share on other sites
tluck
tluck
Posted
Posted

@somez - if you startup without the custom EDID run this to capture the native EDID - i would like to what your native is

... also i will put my new LG EDID into a config.plist for you to test if you like.

ioreg -l | grep -i yedid

and post the results

Link to comment
Share on other sites
Somez
Somez
Posted
Posted

@somez - if you startup without the custom EDID run this to capture the native EDID - i would like to what your native is

... also i will put my new LG EDID into a config.plist for you to test if you like.

ioreg -l | grep -i yedid

and post the results

 

Here it is

 

Tamass-MacBook-Pro:~ somez$ ioreg -l | grep -i yedid

    | |   | | |       "IODisplayEDID" = <00ffffffffffff0030e4e2020000000001140103801f1178e233859956559127175054000000010101010101010101010101010101018025408060841a303020350036ae10000018000000000000000000000000000000000000000000fe004c656e6f766f0a202020202020000000fe0031363030783930300a2020202000ad>

Link to comment
Share on other sites
Somez
Somez
Posted
Posted

tluck, I'm not sure if this is really an EDID issue. I mean, I've had these freezes in the past occasionally. Under Sierra I've had none of them. And I've never changed anything on the default way of installing your package. Now that I'm on High sierra (and a different Clover verison) I get the freezes. I'm just saying to ensure we are not walking into a dead end with this EDID thing :)

Link to comment
Share on other sites
SuperReaper
SuperReaper
Posted
Posted

log show --style syslog | fgrep "Wake reason"

2018-02-11 03:13:12.392199+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 03:13:12.392200+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 05:13:58.057572+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 05:13:58.057573+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 07:14:46.616861+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 07:14:46.616862+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: RTC EH02 (Alarm)
2018-02-11 09:15:33.175068+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: SLPB LID EH02

2018-02-11 09:15:33.175070+0700  localhost kernel[0]: (AppleACPIPlatform) Wake reason: SLPB LID EH02

I don't know why sometimes when the lid is just already closed, my laptop is wake for wake reason like RTC EH02 (Alarm)?

Link to comment
Share on other sites
rolitab
rolitab
Posted
Posted

Maybe it's still too early to get to a conclusion, but I've seen a hint on a Reddit thread to change the memory frequency in the BIOS from AUTO to 1333 mhz. Since then I haven't had any freezes.

 

Where did you find this option in your BIOS? I don't have it in mine (v 1.46).

Link to comment
Share on other sites
rolitab
rolitab
Posted
Posted

@somez - i just posted a new zip/release

 

- key item is a new EDID in the 1600x900 config.

- the old one is in the .alt. files.

 

perhaps try this one?

 

@tluck, thanks for new package. As I have same problem as @somez, so I will also give a feedback on it. I tried both 1600x900 plists. With new one I got freeze in the first minute from booting, also I could notice that display brightness buttons were not working. I also tried alt one (old) and got freeze in 5 minutes.

I found some solution which lets me use my laptop while I'm thinking where to go next. It only freezes when laptop is idle, when I'm using it's almost fine. I have blinking and artifacts from time to time, but at least it doesn't freeze when I'm using it. If I leave laptop idle it freezes in about 1 hour. So what I did - I changed edid in config.plist to the following:

				AP///////wAw5OICAAAAAAEUAQOAHxF46jOFmVZVkScXUFQAAAABAQEBAQEB
				AQEBAQEBAQEBgCVAgGCEGjAwIDUANq4QAAAYQB9AgGCEGjAwIDUANq4QAAAY
				AAAA/gBMZW5vdm8KICAgICAgAAAA/gAxNjAweDkwMAogICAgAMc=
Link to comment
Share on other sites
Somez
Somez
Posted
Posted

@somez - i just posted a new zip/release

 

- key item is a new EDID in the 1600x900 config.

- the old one is in the .alt. files.

 

perhaps try this one?

 

Thanks tluck, I've just installed the latest package by following the instructions as usual. Hope there were no special steps I should've known about.

I've also installed the kexts to /Library/Extensions eventhough the guide says it's now an optional steps. I was afraid that by not installing them the system would load the older (existing) version of the kexts located there. Is that right?

 

I'll report back about the freezes.

 

Thanks.

Link to comment
Share on other sites
Somez
Somez
Posted
Posted

Thanks tluck, I've just installed the latest package by following the instructions as usual. Hope there were no special steps I should've known about.

I've also installed the kexts to /Library/Extensions eventhough the guide says it's now an optional steps. I was afraid that by not installing them the system would load the older (existing) version of the kexts located there. Is that right?

 

I'll report back about the freezes.

 

Thanks.

 

Just got a sudden freeze :(

What I've noticed is that after a while I start to se visual artifacts (characters in Safari are looking differently for some accented letters, I see lines on images/youtube videos, etc.) and then the freeze happens soon.

I've none of these issues in Sierra. Do we have any clue what's changed?

Link to comment
Share on other sites
tluck
tluck
Posted
Posted

I have no idea why High Sierra is glitchy. my mini-mac-hack is a HD3000 and I am getting speckles and lines on that box now - after 3 years (and OS versions) without issue. My son's T420 is getting BRSYNC on occasion too.

 

@rolitab - the current zip supports sierra and high sierra. my t420 boots Sierra and High Sierra from the same disk.

Link to comment
Share on other sites
Somez
Somez
Posted
Posted

I have no idea why High Sierra is glitchy. my mini-mac-hack is a HD3000 and I am getting speckles and lines on that box now - after 3 years (and OS versions) without issue. My son's T420 is getting BRSYNC on occasion too.

 

@rolitab - the current zip supports sierra and high sierra. my t420 boots Sierra and High Sierra from the same disk.

 

Well, I guess this is the downside of using a hackintosh. I could live with the glitches but these freezes are killing me.

Maybe next macOS/Clover version will be better...

Link to comment
Share on other sites
goodguess
goodguess
Posted
Posted

Hi,

just wanted to say thank you so much to tluck and all others making Release v2018.02.11 happen!

The new EFI runs very well with my Sierra T420, minor graphic glitches with Firefox are gone too.

 

I´m not upgrading to HS as long as possible.

HS won´t talk to my vintage DSL router any more due to Apple´s new security policy.

A pity no being able to use APFS with my SSD therefore.

  • Like 1
Link to comment
Share on other sites
149113
149113
Posted
Posted

My T520 Hack has performed great for the last 3 years. But like all things it's time to upgrade the 5 year old machine to a T570. Lenovo is running a deal right now and I am thinking about getting the NVIDIA GeForce 940MX version of the T570. Question... will this card work with High Sierra?

Link to comment
Share on other sites
trifero
trifero
Posted
Posted

My T520 Hack has performed great for the last 3 years. But like all things it's time to upgrade the 5 year old machine to a T570. Lenovo is running a deal right now and I am thinking about getting the NVIDIA GeForce 940MX version of the T570. Question... will this card work with High Sierra?

 

Meanwhile...what about a CPU upgrade?

Link to comment
Share on other sites
goodguess
goodguess
Posted
Posted

I´m getting occasional KP the last weeks, I never saw that frequent before with Hackintosh.

This is the backtrace:

 

*** Panic Report ***
panic(cpu 1 caller 0xffffff80003ff085): Kernel trap at 0xffffff8000836a6f, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0xffffff81dc581000, CR3: 0x000000000390a000, CR4: 0x00000000000626e0
RAX: 0x0000000000000015, RBX: 0x0000000000000015, RCX: 0xffffff801efd5480, RDX: 0x0000000000000000
RSP: 0xffffff81e68c3c00, RBP: 0xffffff81e68c3c40, RSI: 0xffffff8000c09570, RDI: 0xffffff801effe8c0
R8:  0x0000000000000000, R9:  0xffffff801effe880, R10: 0xffffff801effe8a0, R11: 0x0000000000000000
R12: 0xffffff801effe880, R13: 0xffffff801effe840, R14: 0x447373616c436174, R15: 0xffffff8000c09570
RFL: 0x0000000000010206, RIP: 0xffffff8000836a6f, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff81dc581000, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 0
 
Backtrace (CPU 1), Frame : Return Address
0xffffff800014bc50 : 0xffffff80002e950c 
0xffffff800014bcd0 : 0xffffff80003ff085 
0xffffff800014beb0 : 0xffffff800029a543 
0xffffff800014bed0 : 0xffffff8000836a6f 
0xffffff81e68c3c40 : 0xffffff7f82a9b58d 
0xffffff81e68c3c80 : 0xffffff7f82a9c72a 
0xffffff81e68c3ca0 : 0xffffff7f82a9ca6b 
0xffffff81e68c3d30 : 0xffffff7f82a9cbfa 
0xffffff81e68c3d80 : 0xffffff7f82b90326 
0xffffff81e68c3e00 : 0xffffff7f82b90af0 
0xffffff81e68c3e40 : 0xffffff800089793d 
0xffffff81e68c3e80 : 0xffffff800089768e 
0xffffff81e68c3f10 : 0xffffff8000896c46 
0xffffff81e68c3f60 : 0xffffff800089865e 
0xffffff81e68c3fb0 : 0xffffff80002998f7 
      Kernel Extensions in backtrace:
         org.netkas.driver.FakeSMC(1443.0)[F4D6719F-5FF2-3417-8F1B-7CA64314D941]@0xffffff7f82a99000->0xffffff7f82ab1fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80e1b000
         org.hwsensors.driver.ACPISensors(1443.0)[FC0EE82A-1514-3891-A0AF-6A7947B7EFDF]@0xffffff7f82b8f000->0xffffff7f82b9cfff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xffffff7f80e1b000
            dependency: org.netkas.driver.FakeSMC(1443)[F4D6719F-5FF2-3417-8F1B-7CA64314D941]@0xffffff7f82a99000
 
BSD process name corresponding to current thread: kernel_task

 

Boot args: slide=0 kext-dev-mode=1 rootless=0 

 

 

Does anybody have similar issues with a T420 Sierra recently?

I´ll try with my other T420, which usually has W10 installed, to rule out a hardware error, but I don´t think its the hardware.

 

Off topic:

Did any of you hear from René Trost maybe?

Many will know Rene as one of the kind admins over at OSX86.com / kexts.com or from other hackintosh forums. ;)

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...