Bug 498757 – mention lm_sensors changes

Bug 498757 - mention lm_sensors changes

Summary:	mention lm_sensors changes

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora Documentation
Classification:	Fedora
Component:	release-notes (Show other bugs)
Sub Component:
Version:	devel
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	John J. McDonough
QA Contact:	Karsten Wade
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-05-02 19:10 EDT by Tom Horsley
Modified:	2009-06-09 15:27 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-06-09 15:27:26 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tom Horsley 2009-05-02 19:10:03 EDT

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 15:27:26 EDT

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.