Red Hat Bugzilla – Bug 202304
Kernel do not understand all BIOS functions
Last modified: 2007-11-30 17:11:40 EST
Description of problem:
I have a MSI K8NGM2 motherboard powered by AMI BIOS (v02.59) and AMD Athlon 64
processor. But I am running FC4 32-bit edition (i686). The kernel
(2.6.17-1.2142_FC4) cannot detect all the bios features.
In Windows the power button (start button) in my cabinet shuts down my computer
normally. But FC4 cannot trap this. As a result the computer shuts down
immediately (abnormally). I want a solution for this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
[This comment added as part of a mass-update to all open FC4 kernel bugs]
FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel. As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
Please retest with Fedora Core 5.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.