I had a similar problem with an IBM T43p with an Intel card.
The output of prtpci with an updated pci id file:
4/0x2/0 8086,4224 (8086,1010) rev 0x5
slot name: Slot 1, Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter
class 2/80/0: Network controller/Network controller
BAR[0]: 32-bit memory 0xa8401000 0x1000
Therefore I added the following line to the end of /etc/driver_aliases:
iwi "pci8086,4224"
I then did a reconfiguration reboot. No joy.
Turns out that for some reason the e1000g driver binds to the wireless
hardware due to the 8086,1010 line for e1000g in driver_aliases.
I deleted that line in the file and did another reconfiguration reboot.
After that I could plumb the interface and inetmenu gives me the
choice of the iwi interface. It even works - I'm on a trip and in a
coffee shop with free wifi access :-)
[t43p:/]# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
iwi0: flags=1005843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,DHCP,IPv4> mtu
1500 index 4
inet 192.168.1.112 netmask ffffff00 broadcast 192.168.1.255
ether 0:12:f0:5b:8f:32
[t43p:/]#
Thanks for the work getting this going. Now I'd like to see support for
802.11a added to the b/g and also WPA and WPA/2 encryption (I know
that works with the adapter as I use WPA in windows XP).
Stuart
This message posted from opensolaris.org
