Bug 511195 - cpuspeed doesn't work with GA-MA790XT-UD4P and latest bios
cpuspeed doesn't work with GA-MA790XT-UD4P and latest bios
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: cpuspeed (Show other bugs)
11
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Jarod Wilson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-14 02:41 EDT by Justin Newman
Modified: 2009-07-15 08:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-07-15 00:27:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Justin Newman 2009-07-14 02:41:10 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):
1.5-10.fc11

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
  
Actual results:
Nothing

Expected results:
cpuspeed daemon starts

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.
Comment 1 Jarod Wilson 2009-07-14 09:25:26 EDT
(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...
Comment 2 Justin Newman 2009-07-14 14:29:00 EDT
Yes, well, I asked in #fedora and was told to file a bug here. If somebody wants to move it upstream, feel free.
Comment 3 Jarod Wilson 2009-07-14 16:02:58 EDT
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.
Comment 4 Justin Newman 2009-07-15 00:26:51 EDT
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."
Comment 5 Jarod Wilson 2009-07-15 08:57:30 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.