I have an Athlon system which isn't co-operating with the ACPI in -stable (I haven't tried -current yet). I notice that the general recommendation in -current is to provide the output of acpidump but none of the ACPI userland has been MFC'd. I just had a quick try and building the -current userland on -stable and found this is non-trivial because it appears that the APIs are different between the two versions - AcpiOs{Read,Write}{Port,Memory}() have different prototypes. Any suggestions on the way forward? Peter
On Fri, 5 Sep 2003, Peter Jeremy wrote:> I have an Athlon system which isn't co-operating with the ACPI in > -stable (I haven't tried -current yet). I notice that the general > recommendation in -current is to provide the output of acpidump but > none of the ACPI userland has been MFC'd.I'm sorry, I can't support acpi on -stable. Someone else may.> I just had a quick try and building the -current userland on -stable > and found this is non-trivial because it appears that the APIs are > different between the two versions - AcpiOs{Read,Write}{Port,Memory}() > have different prototypes. > > Any suggestions on the way forward?-stable has 0228, -current is 0619. You can manually import the tools by hacking the header files. A better approach would be to boot the 5.1 live filesystem image and use acpidump from there. -Nate
Possibly Parallel Threads
- 4.20.0-rc3 nouveau/Quadro P2000 Mobile: runpm causing ACPI errors, lockups
- 4.20.0-rc3 nouveau/Quadro P2000 Mobile: runpm causing ACPI errors, lockups
- Heads up: New if_xl committed
- [Bug 55948] New: [nvd9 optimus] drm/nouveau/bios: attempt to fetch entire acpi rom image in one shot breaks module load
- MFC of reentrant realpath.c