Search results

Unfortunately, you and I have encountered the same problem. I used to set up to turn off Above 4G MMIO. As a result, the black screen of the computer could not be restored, so I had to change the motherboard. I also thought that it might be the confusion of PCI distribution, turning off Above 4G...

I have seen that computers with the same USB controller 1022:1639 can start and recognize USB without any obstacles. I have checked many websites, and the problems all point to EC,RTC and HPET. However, I have checked many times, compared with other DSDT, and tried to modify but failed

Can be start without GenericUSBXHCI.But it's hard to get start. once the system is restarted, it needs to be rebooted many times to be successful, Using GenericUSBXHCI.kext is for 100% boot success

I think the USB controller can be identified, but I don't know why, as long as the USB controller is identified, it will be stuck near the loading PCI, which may be IRQ conflict, and it is possible to enter the system only after continuous restart. This is the IOREg I saved in the Big Sur system...

Still stuck, can't do without GenericusBxHCI. kext

It's nice to have someone willing to help with maintenance

In these days of use found that the system is not stable, a few minutes after successful boot easy to collapse restart

Install 12.6 system, but the installation is difficult, USB problem has not been solved, you need to cancel GenericusBxHCI. kext when installing, select it after the installation

Yes, the order of using the kext in EFI is correct, and renaming XHC has been tried, but that's not the problem.

What we need to solve is USBToolBox: XHC0: waitForMatchingService failed or timed out. Does anyone know why?

Thanks again for your help，Use USBToolBox will be stuck in USBToolBox: XHC0: waitForMatchingService failed or timed out Use USBPorts.kext to customize the correct port will be stuck in AppleNVME Assert failed Using GenericUSBXHCI.kext can enter the system normally even if it is restarted, but...

I successfully installed it, but it is very difficult to start the installation. It is very likely to be stuck in AppleNVME Assert failed, and I need to restart repeatedly and it will always succeed once. I restart more than 20 times before successful installation, I have tried to leave only...

A breakthrough! The patch worked and successfully resolved the kernel panic, thank you guys very much

I saw this guy say this way can skip MSR_IA32_TSC_ADJUST. May be different hardware TscSyncTimeout data is not the same, found the whole network did not find the specific setting value, but this can skip AppleACPIPlatform caused by kernel panic, this computer can not install may be really caused...

There are two critical issues with Legion 5 that have yet to be solved and will probably never be solved. It takes a very professional person to understand the problem, Significant changes to DSDT or BIOS may be required. 1. When BigSur is installed, it will be randomly stuck in IONVME and...

I compared @cr4700 FACP.aml again, and found that his is 0x800, is the correct AMDCPU parameters, my FACP.aml is 0X400, this website says that 0X400 is the old Intel, which I think is strange, this is AMD's FACP.aml, how to use Intel CPU parameters

I am using the latest version of BIOS, the main identifier of ACPI table is Length ID,SSDT-XXX is the compilation process order, the name is rearranged, this should be no problem

Okay, I posted that earlier

Still can't get rid of cpus=1, according to @ccr4700, I checked APIC.aml, his EFI APIC.aml and my original APIC.aml processor ID and Local Apic ID are both 00 starting, the difference is that I have multiple Local APIC NMI descriptions, I changed it to the same only one, I also tried to put the...

Thank you for sharing, my Legion 5 has been stuck on cpus=1 for several months, it is not clear why, do you encounter kernel Panic when Monterey is booted by 8 core cpus? I saw that you said to replace BigSur's Vanilla iopcifamily. kext/appleacpiplata. kext to Monterey, and I have also...