iwi not loaded by OS

[leonardz]

I have an AMD64 laptop with an Intel PRO/Wireless 2200BG wireless card. It works under linux but I cannot get it to work under OpenBSD (using -current).

Config sees the device driver but dmesg.boot shows it cannot load the driver (see below). So there are is no iwi0 device. What do I need to do to have OpenBSD see the device.

As an asside: I could not get iwi-firmware-3.0.tgz to load as aq package (it complained that it only will load on 1386. So I untarred it into /etc/firmware and rebooted..

grep iwi dmesg.boot
iwi0 at pci0 dev 5 function 0 "Intel PRO/Wireless 2200BG" rev 0x05: could not map memory space
root@genetraveller run 503>>config -e /bsd
OpenBSD 4.3-current (GENERIC) #1448: Sat May 31 12:18:34 MDT 2008
deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
warning: no output file specified
Enter 'help' for information
ukc> find iwi
131 iwi* at pci* dev -1 function -1 flags 0x0
ukc> quit

[jggimi]

Make sure your firmware was unpacked correctly. In the tarball is a +CONTENTS file, a +DESC file, and an etc/ folder containing the firmware and related files. If you untarred directly into /etc, the firmware will be in /etc/etc/firmware, which would be in error.

Your dmesg fragment status, "could not map memory space" is disconcerting. If you have confirmed the firmware is in the right spot, then this error should be reported to the OpenBSD project. Use sendbug if you have a working NIC. I recommend this because the HCL lists the iwi driver and the 2200 BG as supported on the amd64 architecture.

Yeah, I note that the +CONTENTS say "@arch i386" -- but the man page for amd64 and i386 point to the same package.

As a circumvention, you could install i386 and see if the NIC works there.

[ocicat]

Originally Posted by jggimi

MUse sendbug if you have a working NIC.

For more information on submitting PR's, see the following:

http://openbsd.org/report.html

[BSDfan666]

There are some config flags for pcibios(4) that can fix possible PCI configuration problems... another option is to disable pcibios and enable acpi for acpiprt(4) support.

Note: A message was sent into @tech that may fix some systems, http://marc.info/?t=121235482300003&r=1&w=2

If this doesn't work, try using GENERIC.MP, even on non-MP systems the introduction of ioapic(4) may be beneficial.

Good luck & Take care.