Am Mittwoch 16 Mai 2007 schrieb Joshua Hoblitt: > Hello, > > Below is a one line patch to possibly fix this bug: > > http://bugs.gentoo.org/show_bug.cgi?id=178585 > http://bugzilla.kernel.org/show_bug.cgi?id=8075 > > If the kernel is configured with: > > CONFIG_X86_POWERNOW_K8=y > CONFIG_X86_ACPI_CPUFREQ=m > > Which is currently an allowed configuration, the powernow-k8 driver on > an SMP system will fail with a warning like: NAK. I have an Athlon X2 and it works for me w/o the P states driver compiled in. YOu probably should ask the vendor to fix the bios or simply compile in the p states driver additionally w/o forcing the user to do it. Maybe you want to give a hint in the p states driver help text? -- (°= =°) //\ Prakash Punnoor /\\ V_/ \_V
Attachment:
signature.asc
Description: This is a digitally signed message part.
- Follow-Ups:
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: "Duane Griffin" <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- References:
- [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Joshua Hoblitt <[email protected]>
- [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Prev by Date: Re: BUG in kcryptd?
- Next by Date: Re: mkfs.ext2 triggered softlockup
- Previous by thread: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Next by thread: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Index(es):