Jump to content
3390 posts in this topic

Recommended Posts

22 hours ago, iCanaro said:

 

create an SSDT for the custom PM for your CPU

https://github.com/Piker-Alpha/ssdtPRGen.sh

tried. but I don't think this change anything...

I remove the prebuilt ssdt, reboot, run the script, generate the file, rename in ssdt-plug, copy in the ACPI folder, enable via OpenCore configurator and reboot. This is the result1881206220_Schermata2020-07-28alle18_15_34.thumb.png.092b94d8e16f50b3f134c0cc19984a6b.png

Edited by Sbrillo
3 hours ago, MorenoAv said:

Hi guys,

Today I'm at work, and as you remember I had 2 updates for my Mac mini 2018, today I installed it again... and now I have the installation appear although I already made it... and the one in system preferences satay there. BS weirdness strikes again, how do I remove the update from system preferences and the reminder that I have one update in about this Mac?

If you feel that this post is off topic feel free to move it elsewhere...

Thanks

Captura de ecrã 2020-07-28, às 13.59.19.png

 

 

Delete the items under AttentionPrefBundleIDs then log out.

1225086985_ScreenShot2020-07-28at9_50_59AM.thumb.png.5a1b6581d64391cb1482f050c1990bd5.png

Edited by AppleBreak
  • Thanks 2
1 hour ago, eSaF said:

@dvil - Although I've posted about this bug a few times, can I ask if your Clover finding is just with Windows and BS alone connected, because I found BS will only be present if and when another OS X disk is connected. If it is easy for you to do can you just boot your system with just BS and Windows Disk connected and check the result in System Preferences/Startup Disk please.

 

Still working fine in Clover just with BS and Windows.

 

Cheers.

 

Spoiler

1145750031_CloverBS-Winonly.png.e2e3d2b84ef1a5c8d0dff4207dacd29b.png

 

Hi guys,

Currently I have Catalina 10.15.6 and Big Sur Beta 2. I tried to update to beta 3 and it created a Preboot entry in OC, but every time I try to boot it, it results in the kernel panic from the attached picture. I tried it with the latest Clover v2020 and with a compiled OC from today - it results in the same error. Both bootloaders are booting successfully Catalina and BigSur Beta 2. I even downloaded and created a usb installer for beta 3. But unfortunately, it also resulted in the same error (both in Clover and OC).

 

Please if you have encountered this error before and know how to fix it, help me! 

Many thanks!!!

IMG_8711.JPG

19 minutes ago, mvitanov said:

Hi guys,

Currently I have Catalina 10.15.6 and Big Sur Beta 2. I tried to update to beta 3 and it created a Preboot entry in OC, but every time I try to boot it, it results in the kernel panic from the attached picture. I tried it with the latest Clover v2020 and with a compiled OC from today - it results in the same error. Both bootloaders are booting successfully Catalina and BigSur Beta 2. I even downloaded and created a usb installer for beta 3. But unfortunately, it also resulted in the same error (both in Clover and OC).

 

Please if you have encountered this error before and know how to fix it, help me! 

Many thanks!!!

IMG_8711.JPG

I could be wrong but it looks like you don't have a ssd-tpl0 or what ever your device is called to identify the touch hub in order for Big Sur to move on mark it present and go on booting I posted my ssd-tpl0 for any one to get compiled but so far no takers

Edited by markl18
7 minutes ago, markl18 said:

I could be wrong but it looks like you don't have a ssd-tpl0 or what ever your device is called to identify the touch hub in order for Big Sur to move on mark it present and go on booting

 

I use Samsung 970 EVO SSD - NVMe m.2; I haven't had any problems so far with it (using it since High Sierra). And the other betas of Big Sur were not making this problem, so I assume apple changed sth yet again related to that.

14 minutes ago, mvitanov said:

 

I use Samsung 970 EVO SSD - NVMe m.2; I haven't had any problems so far with it (using it since High Sierra). And the other betas of Big Sur were not making this problem, so I assume apple changed sth yet again related to that.

you are missing the point your computer has a touchscreen according to the screen you posted and there is no corresponding driver for that hub to take care off, so installation dies because of unidentified device you could take of the problem by posting a notch kext which tells make no to busy with this device to make it its own and use its own drivers

Edited by markl18
3 minutes ago, markl18 said:

you are missing the point your computer has a touchscreen according to the screen you posted and there is no corresponding driver for that hub to take care off, so installation dies because of unidentified device

My computer does not have a touchscreen (lenovo 700 - 15isk with Skylake i7). How did you infer that? I see only touchpad related stuff in the boot logs.

3 minutes ago, mvitanov said:

My computer does not have a touchscreen (lenovo 700 - 15isk with Skylake i7). How did you infer that? I see only touchpad related stuff in the boot logs.

u vac napisano eto vconze bashei loga kotorgo vi postali pochitai ego vnimatelno i vi uvidete sami look at the end of your log it says all about your touchscreen device elan which probably needs a voodooCElan.kext andvoodoogpio.kext and a ssd-tplo or tpd0 or what ever your DSDT says

3 hours ago, markl18 said:

hi mr @Cyberdevs as per your suggestion trying to install from new betta 3 why I am getting can't mount errors

Does it reach the installer to it just hangs with the errors?

32 minutes ago, markl18 said:

u vac napisano eto vconze bashei loga kotorgo vi postali pochitai ego vnimatelno i vi uvidete sami look at the end of your log it says all about your touchscreen device elan which probably needs a voodooCElan.kext andvoodoogpio.kext and a ssd-tplo or tpd0 or what ever your DSDT says

This is not the problem. I turned off the kext for my touchpad and this line disappears. It gets stuck on AppleNVMe assert failed and the 2 virtual IOReturn IONVMeController lines 

5 minutes ago, markl18 said:

I don't know what ever the picture says I think I tries to mount something and than expand the dmg file into it but doesn't succeed in mounting

If you want to boot the installer you need to remove these boot-args:

 

Spoiler

Untitled.jpg.1bbaa91e06aed9f4293935b4804b5fca.jpg

 

4 minutes ago, Toilet said:

Add vsmcgen=1 to boot-args for beta 3

it's already using it

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<string> -v debug=0x100 keepsyms=1 alcid=5 vsmcgen=1</string>
</plist>
 

Edited by markl18
10 minutes ago, markl18 said:

it's already using it

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<string> -v debug=0x100 keepsyms=1 alcid=5 vsmcgen=1</string>
</plist>
 

Please update your kexts to the latest ones 

54 minutes ago, markl18 said:

 

I think it is the same exact error do you think it is integrity of the file should I download it again but doesn't it check for check some errors it is tcp/ip the whole 7 layer stack

 

Untitled.heic

Edited by markl18
On 7/10/2020 at 2:20 PM, mnfesq said:

 

Thanks but it did not work.  I kept getting a KP due to VoodooInput.kext.  I tried adjusting the settings but could not get the EFI to boot even though it is mostly identical to mine.

Hi, is your HP Envy with the touchscreen? Did you use I2C kext?

Also, in DSDT do you have GPI0 device? Cause in my HP Envy this device is missing.

8 minutes ago, valeryimm said:

I know nothing about this table, what is it intended for?

in order to get the touch hub to work there are two ways ether pinning or gpio and that why you need i2c app to generate you ssddt-tbl0.tbl file which doesn't exactly compile. 

ps you have find out if it is a elan device and do you want to use pinning and the name of the actual device like tpd0 or tpl0 or what ever it is in your DSDT under i2c section also Valerii okuda ti

Edited by markl18
1 minute ago, markl18 said:

in order to get the touch hub to work there are two ways ether pinning or gpio and that why you need i2c app to generate you ssddt-tbl0.tbl file which doesn't exactly compile

Ok, understand. I will return to this very soon. Now I need to get mi wifi working with DW 1560, BCM94532Z, something like that
 

Guest
This topic is now closed to further replies.
×
×
  • Create New...