<PNP0e01> failed to probe at port 0x3e0-0x3e1 on isa0

Sean Shapira <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
Hi.  I'm having some trouble getting a FreeBSD 6.0-RELEASE-p1 kernel to 
detect the PCMCIA controllers on a Pentium-based Compaq.  (One 
controller is in the laptop itself; one in the dock.)  The controllers 
are Cirrus Logic PD6720s, and the Plug-and-Play bios seems to know about 
them, i.e. at boot time I'm told:

PNP0e01: adding fixed io range 0x3e0-0x3e1, size=0x2, align=0x1
pnpbios: handle 12 device ID PNP0e01 (010ed041)
PNP0e01: adding fixed io range 0x3e2-0x3e3, size=0x2, align=0x1
pnpbios: handle 13 device ID PNP0e01 (010ed041)

In other (oldcard-based?) systems, the pcic driver would find these and 
report things like:
pcic0: <Cirrus Logic PD672X> at port 0x3e0 iomem 0xd0000 drq 0 on isa0
pcic0: Polling mode
pccard0: <PC Card bus -- kludge version> on pcic0
pccard1: <PC Card bus -- kludge version> on pcic0
pcic1: <Cirrus Logic PD672X> at port 0x3e2 iomem 0xd4000 irq 10 drq 0 on 
isa0
pcic1: management irq 10
pccard2: <PC Card bus -- kludge version> on pcic1
pccard3: <PC Card bus -- kludge version> on pcic1

With my 6.0 kernel I instead get:

unknown: <PNP0e01> failed to probe at port 0x3e0-0x3e1 on isa0
unknown: <PNP0e01> failed to probe at port 0x3e2-0x3e3 on isa0

I think the relevant lines enabling the driver(s) all appear in my 
kernel config file:

device          cbb             # cardbus (yenta) bridge
device          pccard          # PC Card (16-bit) bus
device          cardbus         # CardBus (32-bit) bus

Not to be too simplistic, but can anyone give me a hint about why this 
might be happening?

Thanks!

-- 
Sean Shapira    [email protected]
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.