Bug 498757 - mention lm_sensors changes
Summary: mention lm_sensors changes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: release-notes
Version: devel
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: John J. McDonough
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-02 23:10 UTC by Tom Horsley
Modified: 2009-06-09 19:27 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-06-09 19:27:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Tom Horsley 2009-05-02 23:10:03 UTC
Description of problem:

I was quite confused by the kernel changes that had the side effect
of disabling almost all the lm_sensors info. Bug 496355 shows my
confusion and the kernel changes which caused it as well as the
kernel boot parameter that can be used to get old behavior.
Seems like this would be good info to go in the release notes
somewhere (if it is already there, I couldn't find it).

The acpi_enforce_resources=lax boot parameter got back my sensor
data, and copying the /etc/sensors3.conf file from fedora 10 got
back my interpretation of that data.

Comment 1 John J. McDonough 2009-06-09 19:27:26 UTC
Added to zero-day release notes.  Basically, the release notes entry points to 496355, better to admonish people of the risks.


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