Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kernel panic with voodoops2trackpad identify touchpad command failed, #12

Closed
racso25 opened this issue Dec 22, 2021 · 8 comments
Closed

Comments

@racso25
Copy link

racso25 commented Dec 22, 2021

Mornig, who can help me with kernel panic with voodoops2trackpad identify touchpad command failed, I have no idea what will be happend with this, I am used last EFI folder and I can not enter to my instalation of BigSur, pleasse help me.

The trackpad does not work in the installation. You have to plug in your mouse for installation. Chances are you didn't follow the bios settings and you have a kernel panic.

Bios settings? Phoenix settigs?

Originally posted by @daniyo27 in #10 (comment)

@racso25 racso25 changed the title > Mornig, who can help me with kernel panic with voodoops2trackpad identify touchpad command failed, I have no idea what will be happend with this, I am used last EFI folder and I can not enter to my instalation of BigSur, pleasse help me. kernel panic with voodoops2trackpad identify touchpad command failed, Dec 23, 2021
@daniyo27
Copy link

  1. BIOS Settings
    Hold F2 to enter BIOS on boot up
    Press CTRL-ALT-F7 to open Advanced Options
    Main - Boot Features - Quick Boot => Disabled
    Advanced - Intel Advanced Menu - CPU Configuration - Software Guard Extentsions (SGX) => Disabled
    Advanced - Intel Advanced Menu - Power & Performance - "CPU - Power Management Control" - CPU Lock Configuration - CFG Lock => Disabled and Overclocking Lock => Disabled
    Advanced - Intel Advanced Menu - System Agent (SA) Configuration - Graphics Configuration - DVMT Pre-Allocated => 64M
    Advanced - Intel Advanced Menu - PCH-IO Configuration - Security Configuration - Force unlock on all GPIO pads => Enabled (Thanks 1OldSWguy)
    Advanced - Intel Advanced Menu - Platform Settings - System Time and Alarm Source => Legacy RTC
    Exit - Exit Saving Changes

@racso25
Copy link
Author

racso25 commented Dec 24, 2021 via email

@daniyo27
Copy link

You keep saying you have kernel panic yet you don't even post screenshots? How are we supposed to know what exactly is wrong?

@racso25
Copy link
Author

racso25 commented Dec 25, 2021 via email

@racso25
Copy link
Author

racso25 commented Dec 25, 2021

Here my screenshot and video
IMG_20211225_230656
IMG_20211225_231120
IMG_20211225_231218
IMG_20211225_231318
IMG_20211225_231408
IMG_20211225_231504
IMG_20211225_231541
IMG_20211225_231611
IMG_20211225_231902
IMG_20211225_233411

@racso25 racso25 closed this as completed Dec 25, 2021
@racso25
Copy link
Author

racso25 commented Dec 25, 2021

Here you are my screenshot

@racso25
Copy link
Author

racso25 commented Dec 25, 2021

You keep saying you have kernel panic yet you don't even post screenshots? How are we supposed to know what exactly is wrong?

@racso25
Copy link
Author

racso25 commented Dec 25, 2021

You keep saying you have kernel panic yet you don't even post screenshots? How are we supposed to know what exactly is wrong?

#12 (comment)) take a look to my screenshot and if you can help me, do it please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants