Wpi intel 3945 wireless

batGnat

I am building a system using 2.0 snapshot. Toshiba M100, with 3945.

It detects the 3945, but has a cant load firmware error on the ipw module.

Any know how to get this working?

batGnat

more info:

I am replacing a Asus 500g Premium, running OpenWRT on my home network. It has a panic when transfer rates hit around 12Mbit per second.

Friend gave me a M100 (dual core 1.6ghz, 2.5gb ram) with broken screen. With 100mbit connection on the way in Australia, the old one needs replacing.

I have access to 3 miniPCI cards, 3945, broadcom 47xx, and a TI something from older router.

Was hoping to run an 802.11a network, if I could get the 3945 working.

mrguitar

I'm about to purchase an alix board and I've got an Intel 3945 lying around. I would love to use it if it will work. Anyone else know if it's possible?

Thanks,

mrguitar

Opps. It looks like mini pci express isnt' really an option at this time.

cmb

You have to set something to acknowledge the license for ipw. Check the system log after booting for details.

batGnat

I have set the options in loader.conf

FreeBSD 8.1 supports it, so it should work. Is it a compile option that needs to be set? pfSense recogizes card

Is the firmware a separate file, or is it actually in the kernel? according to a openBSD reference (http://damien.bergamini.free.fr/packages/openbsd/) the firmware is available as a binary, but even if it would work by copying the file onto system (dont know??), there are no details of where to put it.

wpi0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        ether 00:21:6a:a6:6d:4e
        inet6 fe80::213:2ff:fe80:df15%wpi0_wlan0 prefixlen 64 scopeid 0x9
        inet 10.2.2.3 netmask 0xff000000 broadcast 10.255.255.255
        nd6 options=3 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
        status: no carrier
        ssid batTest channel 1 (2412 MHz 11g)
        regdomain ROW country AU indoor authmode WPA1+WPA2/802.11i privacy ON
        deftxkey UNDEF txpower 30 bmiss 7 scanvalid 60 protmode OFF
        roaming MANUAL</performnud,accept_rtadv></up,broadcast,running,simplex,multicast>

wpi0: flags=8803 <up,broadcast,simplex,multicast>metric 0 mtu 2290
ether 00:13:02:80:df:15
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated</up,broadcast,simplex,multicast>

[2.0-BETA4][admin@pfsense.localdomain]/root(5): dmesg | grep wpi0
wpi0: <intel(r) pro="" wireless="" 3945abg=""> mem 0xd6000000-0xd6000fff irq 17 at device 0.0 on pci3
wpi0: Driver Revision 20071127
wpi0: Hardware Revision (0x1)
wpi0: Regulatory Domain: MoW1
wpi0: Hardware Type: B
wpi0: Hardware Revision: ?
wpi0: SKU does support 802.11a
wpi0: [ITHREAD]
wpi0: need multicast update callback
wpi0: need multicast update callback
wpi0: need multicast update callback
wpi0: need multicast update callback
wpi0: timeout resetting Tx ring 1
wpi0: timeout resetting Tx ring 3
wpi0: timeout resetting Tx ring 4
wpi0: could not load firmware image 'wpifw'
wpi0: A problem occurred loading the firmware to the driver
wpi0: could not load firmware image 'wpifw'
wpi0: A problem occurred loading the firmware to the driver
wpi0: need multicast update callback
wpi0: could not load firmware image 'wpifw'
wpi0: A problem occurred loading the firmware to the driver
wpi0: could not load firmware image 'wpifw'
wpi0: A problem occurred loading the firmware to the driver</intel(r)>

jimp

wpifw should be in our kernels. Though it may be like runfw where it behaves better as a KLD

digitalrefuse

I have this same card in a machine I'm trying to set up, and ran into the same problem. When I took a look at dmesg.boot, I noticed that there are a couple of errors telling me I had to accept the license file

You have to change the loader.conf and add the following lines:

legal.intel_ipw.license_ack=1
legal.intel_wpi.license_ack=1

There was a bug filed on this (http://redmine.pfsense.org/issues/1233) but it looks like it was rejected.

I was able to get past those errors by adding the above lines to my loader.conf, but now I'm getting some sort of memory allocation errors - maybe you'll be luckier.

wallabybob

@digitalrefuse:

I was able to get past those errors by adding the above lines to my loader.conf, but now I'm getting some sort of memory allocation errors

It would be better to add those lines to loader.conf.local since loader.conf can get overwritten in a firmware upgrade.

Please provide details of the memory allocation errors.