[lkml]   [2001]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux should not set the "PnP OS" boot flag
Thomas Hood <> writes:

> My problem was: After running a recent 2.4.x kernel, on a subsequent
> boot of Linux, all configurable devices (internal modem, audio chip,
> parallel, serial and IR ports) were disabled. This would causes
> oopses in my sound device drivers.
> My workarounds were:
> (1) to reinitialize the BIOS prior to booting, or,
> (2) to run "setpnp on" on all the configurable devices early in
> the boot sequence.
> I just now figured out what was going on. When the PnP BIOS is
> going to boot a non-PnP OS, it configures all configurable devices
> itself. When the PnP BIOS is going to boot a PnP OS (which it
> tells from a "boot flag") it leaves configurable devices, other
> than those needed to boot the OS, unconfigured. Recent Linux
> kernels have set the "boot flag" indicating that the OS being booted
> is a PnP OS.
> Unfortunately, Linux isn't really a "PnP OS". The kernel alone
> doesn't configure the devices. One has to use setpnp to do that.

Hmm. Linux isn't quite a "PnP OS". I agree that in the short
term we should not set the boot flag. But we should also investigate
what needs to added so that setpnp does not need to be called.

In the normal case the pci subsystem gets this correct, and we need
the logic to get this correct to support hot plug devices.

Do you have any insite into what needs to be done so that the kernel
will automatically configure isa pnp devices?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:04    [W:0.034 / U:1.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site