On Mon, 7 Dec 2009, Mikael Bak wrote:
Hi list,
Seems to me that this card isn't recognized at boot time (dmesg pasted
at the end of this email). It's a PCMCIA card. Instead of a wifi device
OpenBSD tries to allocate a serial port (com3).
I don't think it is necessarily related to the wi(4) driver. I experienced
very similar behaviour with an ne(4) PCMCIA card (D-Link DE-650).
Sometimes it got detected correctly as ne3, sometimes as a non-working
serial port (pccom?). The machine was a ThinkPad T42 and the following
part of the dmesg is from 4.2-current. ACPI was not configured. I haven't
used that card since then.
pccom3 at pcmcia0 function 0: can't allocate i/o space
pccom4 at pcmcia0 function 0: can't allocate i/o space
pccom5 at pcmcia0 function 0: can't allocate i/o space
ne3 at pcmcia1 function 0 "D-Link, DE-650, Ver 01.00" port 0xa000/32: where did
the card go?
ne3 detached
ne3 at pcmcia1 function 0 "D-Link, DE-650, Ver 01.00" port 0xa000/32: where did
the card go?
ne3 detached
ne3 at pcmcia1 function 0 "D-Link, DE-650, Ver 01.00" port 0xa000/32, address
00:80:c8:85:3e:57
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x3000031f
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x30000316
ne3 detached
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x30000710
cbb1: bad Vcc request. sock_ctrl 0x22, sock_status 0x30000710
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x30000719
ne3 at pcmcia1 function 0 "D-Link, DE-650, Ver 01.00"cbb1: bad Vcc request.
sock_ctrl 0x0, sock_status 0x30000710
cbb1: bad Vcc request. sock_ctrl 0x22, sock_status 0x30000710
port 0xa000/32: where did the card go?
cbb1: bad Vcc request. sock_ctrl 0x0, sock_status 0x30000719
Regards,
David
