Home - BeBytes Info - Submit App - Your Account - Links - Contact Us

  Intel ipw2100 wifi
Version 1.0.1
Contact Publisher
Version History
Other Reviews
Send Updates
  Submitted by: Wildman

Date Posted:
Last Updated:
Page Views:
User Rating:
awaiting votes..  

About Intel ipw2100 wifi:

This is the readme file of the ipw2100 wireless driver for BeOS/HAIKU. The driver supports Intel(R) PRO/Wireless 2100 adapters found in many first generation Centrino laptops.

Supported Devices
This driver only supports Intel(R) PRO/Wireless 2100 devices. The only vendor id supported is 0x8086 (Intel) and the only device id supported is 0x1043.

Supported Functions
The driver supports unencrypted wireless connections as well as WEP with 64 or 128 bits. The device can be operated in IBSS (ad-hoc), BSS (infrastructure), and monitoring mode. The authentication modes supported are Open System and Shared Key.

To install this driver just hit the install.sh shell script. It will put the binaries and links to the right location. You will be asked whether you want to edit the settings file at the end of the installation. You can do the configuration right from there or you can later naviagte to "/boot/home/config/settings/kernel/drivers" and edit the settings file "ipw2100". The settings file is heavily commented to explain all its options.

Not getting connected using this driver can have many different reasons:

1) You didn't switch wireless networking on
All wireless devices have a so called "RF kill switch". This switch or button enables the user to switch of any radio wave emitting device. If the RF kill is active you will not get connected. You can verify that the RF kill is active when you enable syslog output in the kernel settings file and check for the "IPW2100: rf kill switch enabled". If you cannot get this message away, it is most probable that you have a software RF kill switch. This is unfortunate, because the driver cannot override this. You need to find a driver for your RF kill switch first before you can use this driver.

2) The driver cannot start because of a wrong interrupt line
It is possible that the system provided interrupt line number is not correct. In this case the hardware triggers interrupts on an interrupt line, where there is no handler for them. This means that the driver doesn't get noticed by the hardware. An indicator for this problem are syslog entries like "KERN 'idle thread 1'[1]: disable irq 5" and "KERN 'idle thread 1'[1]: irq 5 reenabled (handled by 0x600e4f60)". In this case the hardware probably uses interrupt line 5 while the driver waits on some other interrupt line. You can force the driver to use a specific interrupt line (5 in this case) by changing the "interrupt" setting in the settings file to the desired number.

3) The driver cannot start / does not work
In this case please contact me with a detailed problem description at the contact information below. If you can, also include relevant syslog output and information about your specific setup (hardware, network components and such).

If you have questions or suggestions please don't hesitate to contact me at mmlr@mlotz.ch.

Latest Version

Details about this version:
(no information provided)

Intel (BeOS5, Haiku)     (273.2K)

Most Popular
1. BeAIM - 3288
2. BePDF - 3125
3. Paladin - 3108
4. OpenTracker - 2989
5. AMD PCnet32 - 2988
6. nVidia Driver - 2892
7. nVidia 3D Driver - 2879
8. VMWare PCnet/PCI - 2859
9. SPICE - 2808
10. Firefox - 2758
11. ATI Radeon - 2742
12. Duke Nukem 3D - 2741
13. Sequitur - 2727
14. Basilisk II - 2726
15. Traker.Newfs - 2708
16. AbiWord - 2641

Account Status
  You are not logged in.