pikatchum Posted December 18, 2017 Share Posted December 18, 2017 Hi, something quite unbelievable is happening to me. I have installed High Sierra on my SSD partition, converted automatically to apfs, and all is well, working for days without a hickup with my old GT740 graphics card handling 3 monitors. Honestly it works better and faster than before, but it's still a GT740. I purchased the Rx Vega 56, it worked straight out of the box, but I could only have 1 monitor for some reason. I looked around, made a few changes, added a few kexts, rebooted, and bang kernel panic right off the start. I thought it was due to my new config.plist or kexts, so I plugged the GT740 back in, removed the Rx Vega, rebooted using the config.plist for the GT740, and bang, same problem again. So, this is the issue now. Same hardware as before, same config, I even replaced the EFI with a saved backup of 5 days ago, and I still have the same kernel panic at the start. The verbose output is sooo fast, I can't take pictures of it, it's just a blur, and it ends with a long list of parameters to report to apple that push what caused the panic out of the screen ... I can't begin to understand how the same hardware, no BIOS changes, the same EFI folder as 5 days ago, don't boot like 5 days ago. I have a cloned copy of the apfs partition on another HFS disk and it does the same thing. So why is this computer behaving differently when it starts with a working EFI is beyond me? The thing is, with Sierra, it's become impossible to get the boot or crash logs. Very smart move from Apple I must say. I have looked around, I can't find anything that looks like what was on my screen (see attachments). And apple wants us to report it to them... How? By taking a picture of the screen? And the website they recommend (panic.apple.com) does not even exist !!! Seriously? So, my question is. How can I read the kernel crash log, FROM ANOTHER SYSTEM on top of it. I'm currently using a 10.10 system I keep for safety reasons, and I can't log back into 10.13.2 if I can't figure out what causes the crash. Any idea? PS: from one of my pictures, it seems like rehabman PS2 kext was causing the problem, I removed it, and I still had the same problem... I just need to KNOW what caused the problem Quote Link to comment Share on other sites More sharing options...
foskvs Posted December 18, 2017 Share Posted December 18, 2017 You are using VoodooPS2 1.8.11 (2014). Update it. Quote Link to comment Share on other sites More sharing options...
pikatchum Posted December 18, 2017 Author Share Posted December 18, 2017 You are using VoodooPS2 1.8.11 (2014). Update it. Hi, Thx for your quick reply... I'm going to try to simply remove it since I have no PS2 mouse or kbd. But the question remains: why the same config does not behave the same way? And where can I find that goddam log so I can read it properly? I don't even know how you could pinpoint that voodooPs2 file honestly, it's all a blur. Thx again Quote Link to comment Share on other sites More sharing options...
foskvs Posted December 18, 2017 Share Posted December 18, 2017 I don't even know how you could pinpoint that voodooPs2 file honestly, it's all a blur. Experience... The first kext in the backtrace is VoodooPS2Controller. You have to remove it from where you placed it. 1 Quote Link to comment Share on other sites More sharing options...
pikatchum Posted December 18, 2017 Author Share Posted December 18, 2017 Experience... Schermata 2017-12-18 alle 10.57.50.png The first kext in the backtrace is VoodooPS2Controller. You have to remove it from where you placed it. turns out, you were right, I'm now running from 10.13.2, simply by removing the voodooPS2 kext from another partition... I don't get why it has never been a problem before, and I still don't know how to access the kernel crash report... so now, I'm back with my single monitor issue with the Rx Vega ... but at least I can focus on that instead of a stupid boot problem... thx a lot, grazie mille 1 Quote Link to comment Share on other sites More sharing options...
foskvs Posted December 18, 2017 Share Posted December 18, 2017 I don't get why it has never been a problem before, Old versions cause KP since Sierra. and I still don't know how to access the kernel crash report... You can see the report after you log in. 1 Quote Link to comment Share on other sites More sharing options...
pikatchum Posted December 18, 2017 Author Share Posted December 18, 2017 Old versions cause KP since Sierra. You can see the report after you log in. Thx Deity... the problem is that I could not log in, because it crashed before I could log in... I still don't understand why the voodooPS2 that was there from the beginning suddenly crashed the system during boot... anyway, I have removed it from SLE and now it works perfectly Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.