Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 53232 - why is CONFIG_PNPBIOS disabled ?
why is CONFIG_PNPBIOS disabled ?
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-09-05 05:41 EDT by Fabrice Bellet
Modified: 2007-04-18 12:36 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-05 05:41:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fabrice Bellet 2001-09-05 05:41:55 EDT
Description of Problem:
CONFIG_PNPBIOS has been disabled from kernel configuration since 
kernel version > 2.4.6-2.

This feature is valuable for thinkpad users for example.
When combined with the setpnp tool from the pcmcia package,
it allows us to change some hardware resources, without 
the dos-only PS2.EXE tool provided by IBM. So my wish is
to re-enable this feature, and to add setpnp in the
kernel-pcmcia package too. (bug #50486).

Comment 1 Arjan van de Ven 2001-09-05 05:54:59 EDT
The problem with this feature is that a LOT of machines have a defective bios
that made the 2.4.6 kernels which had PNPBIOS oops. a LOT. Until there is a
reliable way to catch such oopses in the kernel and THEN disable PNPBIOS at
runtime, we have no choice other than to disable it. (Windows uses this method;
but that has the sideeffect of bios writers not noticing their bios is buggy, or
at least not having it as critical bug, hence the large number of broken

Alan is working on getting the "catch" part working, but so far it doesn't; as
soon as it does I'll enable the option.

I'm closing this as "deferred" as I do agree it should be enabled, but only once
it has become actually usable.

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