ndis with Intel 2915 wireless, getting "NDIS ERROR" messages and
deattach on boot
Darren Pilgrim
dmp at bitfreak.org
Mon May 2 02:01:20 PDT 2005
I'm trying to get my wireless NIC working using the ndis driver, but during
boot I get an attach, a stream of what appear to be errors, followed by
"device_attach: ndis0 attach returned 6". The basic specs for the
configuration are:
FreeBSD src: RELENG_5 as of 2005/04/30, about 4pm PDT (-0700)
Machine: Dell Inspiron 6000
NIC: Intel PRO/Wireless 2915ABG miniPCI (Dell PCI ID)
NDIS drivers:
Windows 2000 (NDIS 5.0), driver file is "w29n50.sys"
Windows XP (NDIS 5.1), driver file is "w29n51.sys"
I could not find non-NT drivers for this NIC.
Both drivers produce the following output during boot:
ndis0: <Intel(R) PRO/Wireless 2915ABG Network Connection> mem
0xdfcfd000-0xdfcfdfff irq 5 at device 3.0 on pci3
ndis0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfcfd000
ndis0: [MPSAFE]
ndis0: NDIS API version: <Either "5.0" or "5.1" depending on driver used>
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x2fb
ndis0: NDIS ERROR: c00013a7 (unknown error)
ndis0: NDIS NUMERRORS: 2
ndis0: argptr: 0x4e4f4c41
ndis0: argptr: 0x191
ndis0: NDIS ERROR: c000138d (unknown error)
ndis0: NDIS NUMERRORS: 0
ndis0: init handler failed
device_attach: ndis0 attach returned 6
Subsequent boots appear to produce identical data. The dmesg outputs for
each driver and the driver files themselves are available upon request.
Is this fixed in -current?
More information about the freebsd-stable
mailing list