In message <[EMAIL PROTECTED]> Alex writes:
: Many thanks for your explanation. The question is why PNPBIOS tries to
: attach and assign resources to devices that have already been attached
: (things like AT DMA controller, keyboard controller, math coprocessor,
: printer port, etc.) Is it not
Dear Warner,
Many thanks for your explanation. The question is why PNPBIOS tries to
attach and assign resources to devices that have already been attached
(things like AT DMA controller, keyboard controller, math coprocessor,
printer port, etc.) Is it not smart enough to figure it out?And
In message <[EMAIL PROTECTED]> Alex writes:
: # pnpinfo
: Checking for Plug-n-Play devices...
: No Plug-n-Play devices were found
Makes sense because this looks for PnP ISA addin cards.
OK, taking the lead from
http://members.hyperlink.net.au/~chart/pnpid.txt, lets have a crack at
these things:
OK, the bad news is that reverting to pcm of Dec 5 doesn't fix my
problem. The good news is that "options PNPBIOS" does fix it. Now if
only someone could explain all this junk:
# pnpinfo
Checking for Plug-n-Play devices...
No Plug-n-Play devices were found
# dmesg
...
pcm0: at port 0x530-0x
PCM has been broken for me since December 1999. I would very much
appreciate if someone could help me fix it before the code freeze (cg,
dfr and tanimura CC'd).
I have an unknown MSS-compatible non-PnP ISA sound card, which
identifies itself as a CS4231. Unknown, because it's inside a
laptop.
