PnP OS와 D3-cold 문제?
http://scyld.com/ 를 돌아다니다가 다음과 같은 구문을 봤습니다.
좀 자세하게 이것에 관련해서 정보를 얻고 싶은데요.. 아시는분 첨언좀 부탁 드리겠습니다.
Problems and Solutions
What if the card is detected with a ff:ff:ff:ff:ff:ff station address?
There are three known causes of this problem.
Warm-booting from Win95 OSR2.1 or Win98 (power-managed cards only)
"PnP OS" is set in the PCI BIOS setup.
Broken PCI BIOSes (reportedly version "AI78" is broken).
The "D3-cold" problem
Quick summary: restore operation by unplugging the machine after running an OS that disables the card. Merely using the "soft-off" pushbutton on a ATX case is not sufficient.
Many modern PCI chips have ACPI power management capability. Some include a mode known as "D3-cold", where the chip can power itself off. When in this mode the chip uses only the tiny amount of stand-by power always available when an ATX power supply is plugged in. In the D3-cold mode the chip can be turned on only by writing a PCI configuration space register. This works great if you have a ACPI-aware BIOS that knows how to re-enable the chip on a warm boot, but older BIOS don't know that the chip cannot retain configuration information. When the machine is warm booted the chip has only invalid configuration information.
The PnP OS problem occurs because Microsoft has convinced BIOS makers to modify their PCI device configuration from the previous rational standard, to one that works well only with Microsoft operating systems. Where previously the BIOS allocated resources for and enabled the PCI device by default, it now does so only for boot devices and audio devices. (Why are audio devices specifically an exception? Because MS-Windows can't handle the resource allocation for them!)
The solution is to either update to the latest driver, (the drivers are being re-worked to enable the devices) or to disable the "PnP OS" setting in the machine's BIOS setup.
The reason Microsoft had to have this change implemented for them was that MS-Windows still handles some devices with "real-mode" drivers, and this change makes it easier to mix real-mode and protected-mode device drivers. This is an excellent example of Microsoft using its dominant position in the software industry force a technical change that is detrimental to other operating systems.