I have used the script install-wifi-firmwares.sh to download and install the drivers. My wifi controller was not showing up in the Network Preferences, so I ran listdev and PRO/Wireless 2200BG (Calexico2) showed up. I checked the …/firmware/ folder and found the /iprowifi2200/ folder. It contains ipw2200-fw-3.1.tgz. But, of course, I cannot expand it to a read-only folder.
Frankly, I’m not certain that this is the correct driver. If it is, how do I expand the gz file to install it?
Thanks.
listdev … ?
ifconfig …?
/boot/system/add-ons/kernel/drivers/bin
ipw2100 supporting Intel Pro Wireless 2100
iprowifi2200 supporting
Intel Pro Wireless 2200BG
Intel Pro Wireless 2225BG
Intel Pro Wireless 2915ABG
iprowifi3945 supporting Intel Pro Wireless 3945
iprowifi4965 supporting Intel Pro Wireless 4965 http://www.haiku-os.org/guides/daily-tasks/wireless
http://www.haiku-os.org/docs/userguide/en/workshop-wlan.html
Only PCI, PCI-X, PCI-Express, Mini PCI, and Mini PCI-Express devices are expected to work. PCMCIA, CardBus, ExpressCard, USB and ISA devices do not have the needed glue code to operate at this time.!!!
Hi Tyro65,
if your listdev shows the same id, the driver should work, see here.
The firmware tgz should already been unpacked. Compare it’s contents with the folder it’s in,
Is there anything under /dev/net/ ?
What does “ifconfig” say?
Does “listimage | grep ipro” find the driver?
Regards,
Humdinger
In /dev/net/ there is a driver for iprowifi2200.
I get nothing when I issue this command “listimage | grep ipro”
~> ifconfig
loop Hardware type: Local Loopback, Address: none
inet addr: 127.0.0.1, Mask: 255.0.0.0
inet6 addr: ::1, Prefix Length: 128
MTU: 16384, Metric: 0, up loopback link
Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
Collisions: 0
/dev/net/broadcom570x/0
Hardware type: Ethernet, Address: 00:14:22:cf:2a:87
Media type: 1 GBit, 1000BASE-T
inet addr: 192.168.0.10, Bcast: 192.168.0.255, Mask: 255.255.255.0
MTU: 1500, Metric: 0, up broadcast link auto-configured
Receive: 744 packets, 0 errors, 51125 bytes, 0 mcasts, 0 dropped
Transmit: 7 packets, 0 errors, 1914 bytes, 0 mcasts, 0 dropped
Collisions: 0
Darn. I’m almost certain that this NIC was working with one of the other nightlies. I wish I could remember which one.
listdev ???
Supporting
{ 0x8086, 0x4220, “Intel® PRO/Wireless 2200BG” },
{ 0x8086, 0x4221, “Intel® PRO/Wireless 2225BG” },
{ 0x8086, 0x4223, “Intel® PRO/Wireless 2915ABG” },
{ 0x8086, 0x4224, “Intel® PRO/Wireless 2915ABG” },
listimage ???
~> listdev
device Multimedia controller (Multimedia audio controller) [4|1|0]
vendor 8086: Intel Corporation
device 24c5: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC’97 Audio Controller
device Mass storage controller (IDE interface) [1|1|8a]
vendor 8086: Intel Corporation
device 24ca: 82801DBM (ICH4-M) IDE Controller
device Bridge (ISA bridge) [6|1|0]
vendor 8086: Intel Corporation
device 24cc: 82801DBM (ICH4-M) LPC Interface Bridge
device Network controller [2|80|0]
vendor 8086: Intel Corporation
device 4220: PRO/Wireless 2200BG [Calexico2] Network Connection
device Bridge (CardBus bridge) [6|7|0]
vendor 1217: O2 Micro, Inc.
device 7113: OZ711EC1 SmartCardBus Controller
device Bridge (CardBus bridge) [6|7|0]
vendor 1217: O2 Micro, Inc.
device 7113: OZ711EC1 SmartCardBus Controller
device Network controller (Ethernet controller) [2|0|0]
vendor 14e4: Broadcom Corporation
device 165d: NetXtreme BCM5705M Gigabit Ethernet
device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 2448: 82801 Mobile PCI Bridge
device Serial bus controller (USB controller, EHCI) [c|3|20]
vendor 8086: Intel Corporation
device 24cd: 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller
device Serial bus controller (USB controller, UHCI) [c|3|0]
vendor 8086: Intel Corporation
device 24c7: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3
device Serial bus controller (USB controller, UHCI) [c|3|0]
vendor 8086: Intel Corporation
device 24c4: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2
device Serial bus controller (USB controller, UHCI) [c|3|0]
vendor 8086: Intel Corporation
device 24c2: 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1
device Display controller (VGA compatible controller, VGA controller) [3|0|0]
vendor 1002: Advanced Micro Devices, Inc. [AMD/ATI]
device 4c66: RV250/M9 GL [Mobility FireGL 9000/Radeon 9000]
device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 3341: 82855PM Processor to AGP Controller
device Bridge (Host bridge) [6|0|0]
vendor 8086: Intel Corporation
device 3340: 82855PM Processor to I/O Controller
~>
Hi Tyro65,
So, the driver and firmware is there, but isn’t loaded (=doesn’t appear in “listimage”). I guess you’ll have to file a ticket at the bugtracker…
Put in all the info you gained, listdev, listimage and also add your syslog.
Regards, Humdinger
Okay. Thanks for trying.
Wifi is alive and well when I run r1/alpha4.
Hi!
You could pinpoint the release that has caused the issue with a binary search in the nightly images, i.e. go half-way between the alpha4 release and the latest nightly. If it still works, go have way between that working nightly and the latest nightly, and so on. Until you find the (more or less) exact commit that has caused your wifi to fail.
Regards, Humdinger
I just used a f1/alpha4 live CD to expand ipw2200-fw-3.1.tgz and move the files to /boot/system/data/firmware/iprowifi200/
I rebooted and now my wifi is working.
Maybe we need to post this workaround somewhere.
It would be better to file this issue where it belongs, on the bug tracker – http://dev.haiku-os.org The proper fix is to find out why install-wifi-firmwares.sh is not working as it should. Unfortunately, I don’t have access to one of the wifi cards, which makes testing impossible.
My Dell Latitude D600 has a mind of its own. I’m baffled, but happy. As Humdinger suggested, I’ve tried to find the first nightly that stopped installing the iprowifi2200 driver. I’ve installed 46368, 46516, 46467, 46602, 46618, 46626, 46629, 46632 and finally 46638, which was the only one that didn’t load the wifi driver. All the others loaded the driver properly. I must have a hardware problem with that NIC, because it seems to me that some of the nightlies that didn’t work when I tried them before, worked today. And it seems to me that it would work and, at times, not work with various Linux distros. I blamed the not-working on the kernels not having the correct driver module.