Bug 531916

Does booting with 

acpi.power_nocheck=1

on the kernel parameter line in grub help?

That last patch from http://bugzilla.kernel.org/show_bug.cgi?id=11000#c38 (commit eab4b645769fa2f8703f5a3cb0cc4ac090d347af) has been reverted in 2.6.32 and in Fedora 12 because it causes complete failure to boot on some systems.

chuck: aha, interesting, chuck. thanks.

I'm still waiting for the forum reporter to answer my relayed request for the info mjg needs (comment #1)...

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Leaving this flagged needinfo until then

Reporter says:

"The acpidump gave me no such file or directory.I did not expect it but the acpi.power_nocheck=1 seem to be working fine.Fedora 12 may be the only one accepting this option because it didnt work with ubuntu,debian,arch,gentoo,centos.I just hope to not have problem with the next kernels.Thanks for giving attention to my problem and report this bug.If i can help by giving information for that problem i am waiting.."

So acpi.power_nocheck=1 does help. I forgot to tell him to install pmtools before running acpidump, sorry, my bad. I have sent him further instructions and will post back once we've got his BIOS info.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Created attachment 367186 [details]
The output of acpidump

Hello.Thanks adam for helping me with this bug,and everyone else ofcourse.I have attach the output of acpidump.

excellent, thank you John.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Can you test with the kernel build from http://koji.fedoraproject.org/koji/taskinfo?taskID=1788372 and see if this helps?

I could if there was an explanation or a guide for this testing.I downloaded f12 beta again.I cant make install,same problem i had with f11 see bugs 498457 or 484276.Also having problems after updating system with the latest kernel.Screen goes black if i open a window or start a program.When booting with previous kernel firefox doesnt start.

john: are you on 32-bit or 64-bit fedora? tell me that and I can give you exact commands for testing.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

32-bit

OK, try this then:

go to http://koji.fedoraproject.org/koji/taskinfo?taskID=1788377 and get kernel-2.6.31.5-118.fc12.i686.rpm and kernel-devel-2.6.31.5-118.fc12.i686.rpm . Open a console and go to the directory where you downloaded the files. Use 'su' to become root, then run:

rpm -ivh kernel-2.6.31.5-118.fc12.i686.rpm kernel-devel-2.6.31.5-118.fc12.i686.rpm

if it complains about the versions of kernel-firmware and kernel-headers , get kernel-headers-2.6.31.5-118.fc12.i686.rpm from the same page and kernel-firmware-2.6.31.5-118.fc12.noarch.rpm from http://koji.fedoraproject.org/koji/taskinfo?taskID=1788375 , go to the directory, do 'su', and run:

rpm -Uvh kernel-headers-2.6.31.5-118.fc12.i686.rpm kernel-firmware-2.6.31.5-118.fc12.noarch.rpm

then try the first rpm command again. let us know if you get stuck. good luck!

after all that, reboot and see how it works.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

[root@machine Downloads]# ls
kernel-2.6.31.5-118.fc12.i686.rpm
kernel-devel-2.6.31.5-118.fc12.i686.rpm
kernel-firmware-2.6.31.5-118.fc12.noarch.rpm
kernel-headers-2.6.31.5-118.fc12.i686.rpm
[root@machine Downloads]# rpm -Uvh kernel-headers-2.6.31.5-118.fc12.i686.rpm
Preparing...                ########################################### [100%]
   1:kernel-headers         ########################################### [100%]
[root@machine Downloads]# rpm -Uvh kernel-firmware-2.6.31.5-118.fc12.noarch.rpm
Preparing...                ########################################### [100%]
   1:kernel-firmware        ########################################### [100%]
[root@machine Downloads]# rpm -ivh kernel-2.6.31.5-118.fc12.i686.rpm
Preparing...                ########################################### [100%]
   1:kernel                 ########################################### [100%]

W: Possible missing firmware aic94xx-seq.fw for module aic94xx.ko
W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko
W: Possible missing firmware ql2400_fw.bin for module qla2xxx.ko
W: Possible missing firmware ql2322_fw.bin for module qla2xxx.ko
W: Possible missing firmware ql2300_fw.bin for module qla2xxx.ko
W: Possible missing firmware ql2200_fw.bin for module qla2xxx.ko
W: Possible missing firmware ql2100_fw.bin for module qla2xxx.ko

 
[root@machine Downloads]# rpm -ivh kernel-devel-2.6.31.5-118.fc12.i686.rpm
Preparing...                ########################################### [100%]
   1:kernel-devel           ########################################### [100%]
[root@machine Downloads]#

Also after restarting,the system frezze at password prompt with the screen corupted or black and cannot login.At this point(login) it seems that the fan works properly.

Thanks - just to make sure, this is using the updated kernel and *not* using acpi_power.nocheck, right?

Yes.Even with the acpi.power_nocheck=1 option i have the same results.

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Is there any reason why temperature limits are locked?

FYI,
commit 0c99c5288eb9b1bbc9684b0ec0fd7efc578749b3
Author: Zhang Rui <rui.zhang>
Date:   Thu Dec 17 16:02:08 2009 +0800

    ACPI: Disable explicit power state retrieval on fans
    
    If the ACPI power state can be got both directly and indirectly,
    we prefer to get it indirectly.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=531916 describes a
    system with a _PSC method for the fan that always returns "on".
    There's no benefit in us always requesting the state of the fan
    when performing transitions - we want to do everything we can
    to ensure that the fan turns on when it should do, not risk
    hardware damage by believing the hardware when it tells us the
    fan is already on. Given that the Leading Other OS(tm) works fine
    on this machine, it seems likely that it behaves in much this way.
    
    inspired-by: Matthew Garrett <mjg>
    Signed-off-by: Zhang Rui <rui.zhang>
    Signed-off-by: Len Brown <len.brown>


shipped in upstream linux-2.6.34-rc2

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

not my bug, but john's. still seeing this, john?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.