Red Hat Bugzilla – Bug 511195
cpuspeed doesn't work with GA-MA790XT-UD4P and latest bios
Last modified: 2009-07-15 08:57:30 EDT
Description of problem:
cpuspeed daemon won't start with a GA-MA790XT-UD4P motherboard using the F5 BIOS. Worked with F3 and earlier BIOS (not sure about F4)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora 11 on above mentioned system
2. Try to start cpuspeed with /etc/init.d/cpuspeed start
3. Check /var/log/messages for error output
cpuspeed daemon starts
Error in /var/log/messages:
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor.
(In reply to comment #0)
> Additional info:
> Error in /var/log/messages:
> [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a
> way that Linux understands. Please report this to the Linux ACPI maintainers
> and complain to your BIOS vendor.
Um... bugzilla.redhat.com is neither the Linux ACPI maintainers nor your BIOS vendor...
Yes, well, I asked in #fedora and was told to file a bug here. If somebody wants to move it upstream, feel free.
Probably better to stop by #fedora-kernel for an issue like this, rather than rely on #fedora... If anything, this would best be filed at bugzilla.kernel.org under acpi, but given that a prior bios worked fine, I'm inclined to believe there's nothing they could do there either, as its probably a bios bug.
Please also note that there's no "move it upstream" switch, someone has to file a bug upstream, and it really doesn't make sense for anyone but the person w/the actual affected hardware to file the bug. Proxying on something like this is just a grossly inefficient waste of everyone's time.
You know what's a grossly inefficient waste of *my* time? Bothering to file a bug report at all when the response is just going to be, "Not my problem. Don't waste my time."
Only so many hours in the day, can't fix everything. Sorry. If this issue were reported *as the log message instructed*, you might have better luck. But again, most likely a bios bug. I don't have the source code to your bios, let alone your motherboard, so there's really not much I could do to begin with. I've given you all the help I reasonably can.