ThinkWiki - User contributions [en]

Madwifi

2006-01-08T01:41:30Z

Tvon: Remove obsolete CVS reference. Update location do daily snapshots. Rename 'CVS'/'SVN' sections to 'Source'. Move daily snapshots link from 'packages' to 'source'.

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)

=== Packages ===
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}

=== Source ===

Detailed instructions can be found [http://madwifi.org/wiki/UserDocs/GettingMadwifi on the MadWiFi Wiki].

* Daily snapshots: http://snapshots.madwifi.org/
* madwifi-ng:
:{{cmduser|svn checkout http://svn.madwifi.org/trunk madwifi-ng}}
* madwifi-old:
:{{cmduser|svn checkout http://svn.madwifi.org/branches/madwifi-old madwifi-old}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://www.madwifi.org/wiki MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]
* [http://www.ath-driver.org/ OpenSource Atheros driver for Linux]

[[Category:Drivers]]

How to enable integrated fingerprint reader with BioAPI

2006-01-08T00:12:51Z

Tvon: Things that can lock you out of your system without root access deserve a {{WARN}}

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page describes the process of getting the [[Integrated Fingerprint Reader|integrated fingerprint reader]] to work under Linux. It is based on experiences in {{Ubuntu}} on a T43. The same works on {{Fedora}} 4, SuSE 9.3, SuSE 10, and {{Gentoo}}.
|}

==Basic installation==
===Installing the bioapi framework===
====Automated installation script====
The [[Script for enabling the fingerprint reader]] automates the installation of most components (bioapi framework, driver, pam_bioapi, pam setup, device permissions, pamtester and enrolling), for some Linux distributions.

====Binary packages====
=====Debian=====
*If you're using {{Debian}} Sid (the unstable branch) you can try the packages from Michael R. Crusoe's site, either [http://www.qrivy.net/~michael/temp/ version 1.2.3] (recommended) or [http://www.qrivy.net/~michael/debs/unstable/ older versions] which might not work with the steps in this howto.
*This seems to work for {{Ubuntu}} Breezy/Dapper too, so save yourself some trouble and grab it.
=====Gentoo=====
You can either grab the [http://www.qrivy.net/~michael/blua/bioapi/bioapi-1.2.2.ebuild.tar.bz2 ebuild], or use the source-install procedure below.

Also see [http://toe.ch/~tsa/ibm-fingerprint/ http://toe.ch/~tsa/ibm-fingerprint/] for alternative documentation on installing on Gentoo including ebuilds for all the packages used.

====Installing from source====
*Get the bioapi source:
:{{cmduser|wget http://www.qrivy.net/~michael/blua/bioapi/bioapi-latest.tar.bz2}}
*I could not compile bioapi with the graphical Qt tools. To do it manually, do the following:
:{{cmduser|tar xjf bioapi-latest.tar.bz2}}
:{{cmduser|cd bioapi-1.2.2}}
:{{cmduser|1=./configure --with-Qt-dir=no}}
:{{cmduser|make}}
:and then as root
:{{cmdroot|make install}}
:If make install fails, be sure you're root and then:
:{{cmdroot|1=export LD_LIBRARY_PATH=/usr/local/lib}}
:{{cmdroot|make install}}
:and if you want to compile pam_bioapi for auth later
:{{cmdroot|cp include/bioapi_util.h include/installdefs.h imports/cdsa/v2_0/inc/cssmtype.h /usr/include}}
:Be aware that checkinstall will not work!
:(I got through configure with Qt, but got a cryptic build error. It all worked fine with Qt disabled as above)
:buzz: This is due to a wrong qt include path, set it manually in configure and everything should work.
* By default, bioapi will install numerous files in {{path|/usr/local/<nowiki>{</nowiki>bin,lib,include<nowiki>}</nowiki>}}, including files with "self-explanatory" names such as {{path|/usr/local/bin/Sample}}. To prevent this pollution:
:Create a dedicated directory, for example {{path|/opt/bioapi}} .
:Append <tt>--prefix=/opt/bioapi</tt> to the above <tt>./configure</tt> command.
:Append {{path|/opt/bioapi/bin}} to <tt>$PATH</tt> and {{path|/opt/bioapi/lib}} to <tt>$LD_LIBRARY_PATH</tt>.
:When installing the driver (below), tell it the new install path: {{cmdroot|sh install.sh /opt/bioapi/lib}}

===Installing and configuring the driver===
====Installing the driver====
*Download {{path|TFMESS_BSP_LIN_1.0.zip}} from the [http://www.upek.com/support/dl_linux_bsp.asp UPEK support site] and unzip it into a seperate folder, as it will not create one.
*Change to that folder and do as root:
:{{cmdroot|sh install.sh}}
:If you're running Gentoo, use
:{{cmdroot|sh install.sh /usr/lib}}
:If that fails, it may be that make install failed up above -- try setting LD_LIBRARY_PATH, do the make install again, and come back here and try this again. You also need {{cmd|mod_install|}} from bioapi in your PATH.
====Configuring permissions for non-root use====
If you want to use PAM-aware applications like xscreensaver that are NOT running with root permissions (as opposed to login, gdm or other authentication mechanisms), you may need to do all or at least some of the things in this section. More details on what is necessary on which distributions would be greately appreciated.
*Create two groups, one for access to BioAPI files and the other for access to the usb files. (This is done for full generality; i.e., you may have other USB devices which you want accessable to other users, without exposing your BioAPI configuration to them). Add your normal user (the one you wish to use PAM-aware applications with) to both of these groups. On Debian this is done with
:{{cmdroot|addgroup --system bioapi}}
:{{cmdroot|addgroup --system usbfs}}
:{{cmdroot|adduser yournormaluser bioapi}}
:{{cmdroot|adduser yournormaluser usbfs}}
:(where {{cmd|yournormaluser|}} is your normal user name). You will need to log out and log back in for this to take effect.
*Set permissions on the BioAPI config/registry directory:
:{{cmdroot|chown -R root:bioapi /usr/local/var/bioapi/}}
:{{cmdroot|chmod -R 770 /usr/local/var/bioapi/}}
:(change this path if you used an alternate BioAPI install directory above)
*Set permissions on the files in {{path|/proc/bus/usb}}:
:{{cmdroot|chown -R root:usbfs /proc/bus/usb}}
:{{cmdroot|chmod -R g+X /proc/bus/usb}}
:{{cmdroot|chown root:usbfs /proc/bus/usb/`lsusb <nowiki>|</nowiki> sed -ne "/0483:2016/s/Bus\ $.*$\ Device\ $.*$:\ .*/\1\/\2/p"`}}
:{{cmdroot|chmod 660 /proc/bus/usb/`lsusb <nowiki>|</nowiki> sed -ne "/0483:2016/s/Bus\ $.*$\ Device\ $.*$:\ .*/\1\/\2/p"`}}
:You may need to replace {{cmd|lsusb|}} with its full path, which is something like {{cmd|/sbin/lsusb|}} or {{cmd|/usr/bin/lsusb|}} depending on your distro. It might be necessary to put these lines into a script which is run at startup and resume from suspend/hibernate.
*As an alternative to the {{cmd|chown|}}/{{cmd|chmod|}} commands above, you can set mount options for usbfs with a line in {{path|/etc/fstab|}}; an example would be
none /proc/bus/usb usbfs defaults,devgid=108,devmode=0660,busgid=108,busmode=0770,listgid=108,listmode=0660 0 0
:where 108 is replaced with the numerical group ID of the usbfs group (you can determine this with something like {{cmd|cat /etc/group <nowiki>|</nowiki> grep usbfs <nowiki>|</nowiki> cut -d':' -f 3|}}). Make sure you only have one {{path|/proc/bus/usb}} entry in {{path|/etc/fstab}}. See the {{cmd|mount(8)|}} manpage for more information on these options. This is "cleaner" but seems to have a few weird issues -- see the talk page for details.
*You may also have files in {{path|/dev/bus/usb}}, which the driver will try before {{path|/proc/bus/usb}}. If this is another usbfs mount point ({{cmd|mount|}} shows a line containing {{cmdresult|/dev/bus/usb type usbfs}}), then simply follow the above instructions with {{path|/dev/bus/usb}} rather than {{path|/proc/bus/usb}}. Otherwise, you may be running a new kernel (i.e. 2.6.15) that makes usbfs-like files available through {{path|/dev/bus/usb}}. On systems running udev these files are dynamically created; you can configure their permissions by editing a udev config file. On Debian this is done by changing the <tt>usb_device</tt> line of {{path|/etc/udev/permissions.rules}} to read
SUBSYSTEM=="usb_device", MODE="0660", GROUP="usbfs"
*For the beta versions only, there is a logfile, which needs to exist with the proper permissions:
:{{cmdroot|touch /var/log/BSP.log && chown root:bioapi /var/log/BSP.log && chmod 660 /var/log/BSP.log}}
====Miscellaneous configuration====
* To increase the security level (minimize false accept rate), set this in {{path|/etc/tfmessbsp.cfg}}:
security-level="5"

===Testing the driver and enrolling a fingerprint===
To test the driver and generate the file containing your fingerprint information, you need a sample program included with the driver. The compilation steps below were discovered by trial and error; if they don't work for you, try the binary {{cmd|Sample|}} utility that came with the beta versions of the driver (i.e., {{path|TFMESS_BSP_LIN_1.0beta2.zip}} as mentioned above).
Go to the folder where you extracted {{path|TFMESS_BSP_LIN_1.0.zip}} and do:
:{{cmdroot|cd NonGUI_Sample}}
:Edit {{path|main.c|}} and remove (or comment out) the line
#include "port/bioapi_port.h"
:{{cmdroot|gcc -o Sample main.c -L/usr/local/lib -lbioapi100 -DUNIX -DLITTLE_ENDIAN}}
:{{cmdroot|./Sample}}
:Note that Sample may only run as root, unless you've already configured the usbfs file permissions.
:You can try to "e"nroll (to record a fingerprint for an account) and then "v"erify (to test a fingerprint against the one it expects for an account).
:You'll save a step later if you use your own login username as the username to enroll here.

==Login via pam_bioapi==

The following explains how to add fingerprint authentiation to programs that use the PAM (Pluggable Authentication Modules) framework, such as Gnome's GDM and KDE's KDM and screensaver.

===Getting required libs & tools===
====Installing pam_bioapi====
*Prerequisites
:On SuSE 10, I needed to install the pam-devel RPM
:In general, you will need pam itself (standard for most distros) as well as the pam development files (probably an optional package for your distro).
*Get and compile the pam_bioapi module.
:{{cmduser|wget http://www.qrivy.net/~michael/blua/pam_bioapi/pam_bioapi-latest.tar.bz2}}
:{{cmduser|tar xjf pam_bioapi-latest.tar.bz2}}
:{{cmduser|cd pam_bioapi-0.2.1}}
:{{cmduser|wget http://badcode.de/downloads/fingerprint.patch}}
:{{cmduser|patch -p0 < fingerprint.patch}}
:If you want to, review the patch. In general you should review all code you download and compile, if possible. The patch comes from [http://linuxbiometrics.com/modules/newbb/viewtopic.php?viewmode=flat&topic_id=80&forum=1 this thread].
:{{cmduser|./configure && make}}
:and as root
:{{cmdroot| make install}}
:{{cmdroot| cp /usr/local/lib/security/* /lib/security/}}
{{NOTE|If you get a 'rpl_malloc' error in /var/log/auth.log when trying to use the fingerprint reader, redo these steps and remove the related term from Makefile after running ./configure. (FC3, Debian etch)}}
*Use the sample tool from the fingerprint reader to create {{path|<username>.bir}} (<tt><username></tt> '''must''' be the username you want to login with. gdm will probably break for any login name that has no .bir file).
*As root do:
:{{cmdroot|SERIAL<nowiki>=`BioAPITest | sed -ne "/Fingerprint/{n;n;s/^.*: $.\{9\}$$.\{4\}$$.\{4\}$$.\{4\}$$.*$/\1-\2-\3-\4-\5/gp}"` </nowiki>}}
:{{cmdroot|echo $SERIAL}} should print something like {{cmdresult|<nowiki>{5550454b-2054-464d-2f45-535320425350}</nowiki>}} now.
:If it does, do:
:{{cmdroot|mkdir -p /etc/bioapi/pam/$SERIAL}}
:{{cmdroot|cp <username>.bir /etc/bioapi/pam/$SERIAL}}
:If not, you might just try
:{{cmdroot|SERIAL<nowiki>={5550454b-2054-464d-2f45-535320425350}</nowiki>}}
:as this value is hardcoded into the UPEK docs.

===Configuring pam===
The following part is distribution specific. On {{Ubuntu}} or SuSE you can modify {{path|/etc/pam.d/common-auth}} (on {{Gentoo}} and {{Fedora}} it is {{path|/etc/pam.d/system-auth}}) to look like this:

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth required pam_unix.so nullok_secure

----
{{path|/etc/pam.d/system-auth}} for '''Gentoo'''-Users:

auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth required pam_unix.so nullok_secure
auth required pam_env.so
auth sufficient pam_unix.so likeauth nullok
auth required pam_deny.so
account required pam_unix.so
password required pam_cracklib.so difok=2 minlen=8 dcredit=2 credit=2 retry=3
password sufficient pam_unix.so nullok md5 shadow use_authtok
password required pam_deny.so
session required pam_limits.so
session required pam_unix.so
----

With this modification pam immediately starts to use the fingerprint reader to do local authorization (e.g. sudo/gdm use the fingerprint reader).

''Note:'' With a system-auth like above, '''Gentoo''' will give you 'account expired' errors.
CREATE {{path|/etc/pam.d/common-auth}} like so.

account required pam_unix.so
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
password sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi/pam/
auth required pam_unix.so nullok_secure
session required pam_limits.so
session required pam_unix.so

{{WARN|If su/sudo expects to receive the root password (SuSE 10), you need to have fingerprint settings for root (that is, copy in a root.bir as well as a your-username.bir). Otherwise, they get a segmentation fault. Which is a little unfortunate, given that you need to su or sudo to change your settings...}}

For some applications (kdm, SuSE 10 KDE screen saver), you'll need to enter an empty password (or select the correct user and then enter an empty password) in order to get the fingerprint prompt. kdm didn't give any visual indication it was going to the fingerprint reader, other than the cursor stopped blinking, but I swiped, and it let me in.

Note that sshd may pick up the fingerprint settings from {{path|/etc/pam.d/common-auth}}. I didn't want that, so I removed the "auth include common-auth" line from {{path|/etc/pam.d/sshd}} and replaced it with the lines that were originally in my {{path|/etc/pam.d/common-auth}}. That way most local services use the fingerprint reader, but sshd does not.

Another way to do this is to create a file ({{path|/etc/pam.d/bioapi|}} for example) which contains the {{cmd|pam_bioapi.so|}} lines, and explicitly {{cmd|@include|}} this '''before''' {{path|/etc/pam.d/common-auth|}} in the files for services which should use the fingerprint reader. In this case you should leave {{path|/etc/pam.d/common-auth|}} alone.

{{NOTE|This was discovered through trial and success, if it is plain wrong, wikorrect it, please.}}

On {{Fedora}}, you may need to add {{path|/usr/local/lib}} to your LD_LIBRARY path so that the libraries referenced from <tt>pam_bioapi.so</tt> get picked up properly. Also the original 'session' terms in {{path|/etc/pam.d/system-auth}} need to be kept.

On {{Fedora}}4 or {{Aurox}}11, you may need to add {{path|/usr/local/lib}} to ldconfig configuration.
:{{cmdroot|echo '/usr/local/lib' > /etc/ld.so.conf.d/bioapi.conf}}
:{{cmdroot|ldconfig}}
If you see bioapi libs
:{{cmdroot|ldconfig -p | grep bioapi}}
then it should work.

Now gdm should pop up an (ugly) image to swipe your finger and... magic - you can login without a password. If you use kdm, there is no pop up. In xdm, enter your username and a blank password, then swipe (there is no popup).

You can do some useful testing with [http://pamtester.sourceforge.net/ {{cmd|pamtester|}}], which calls the pam modules as if it were a program of your choice. Examples:
:{{cmdroot|pamtester xdm yourusername authenticate}}
:{{cmduser|pamtester xscreensaver yourusername authenticate}}
where {{cmd|yourusername|}} is your username. Note that {{cmd|pamtester|}} should run as root if and only if the program in question does.

==Make xscreensaver use the scanner==
*Get the needed xscreensaver sources:
:{{cmduser|wget http://www.jwz.org/xscreensaver/xscreensaver-4.23.tar.gz}}
:{{cmduser|tar xzf xscreensaver-4.23.tar.gz}}
:{{cmduser|cd xscreensaver-4.23}}
:{{cmduser|wget http://nax.hn.org/pub/bioapi/xscreensaver-4.22_alternativeAuth.diff}}
*After reviewing the patch (it's small and straightforward), do
:{{cmduser|patch -p1 < xscreensaver-4.22_alternativeAuth.diff}}<br />The patch prevents xscreensaver from opening an authentification window and dispatches the authentification request to another program, in our case <tt>pam</tt> and <tt>pam_bioapi</tt>. It should apply with some offset, don't mind that. If it says something about rejected though, then there's a problem.
*Compile with
:{{cmduser|./configure --with-pam && make}}<br />
*If you recieve an error like "undefined reference to `XmuPrintDefaultErrorMessage'" then install the libxmu-dev package and run the previous line again
*and then install as root with
:{{cmduser|su -c make install}} .
*Make sure that the newly compiled xscreensaver is used:
:{{cmduser|which xscreensaver}} should return
:{{cmdresult|/usr/local/bin/xscreensaver}} .
:*In case it doesn't, try
::{{cmduser|1=export PATH=/usr/local/bin:$PATH}}<br />and retry.
*Kill the running instance of xscreensaver:
:{{cmduser|xscreensaver-command -exit}}
*Make sure you have the following line in your {{path|~/.xscreensaver}}:
alternativeAuth: True
*Now edit {{path|/etc/pam.d/xscreensaver}} to include the following line (If you're on {{Ubuntu}} Breezy and you already changed {{path|/etc/pam.d/common-auth}} you should not need to do this.):
auth sufficient pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam/
*Start the new xscreensaver
:{{cmduser|xscreensaver}}<br />There should be a splash screen with version 4.23.
*Now try:
:{{cmduser|xscreensaver-command -lock}}

If you have questions or problems with this procedure, ask: t43fingerprint (at) badcode.de .

===Package for Debian sid===

If you're running {{Debian}} sid (the unstable branch) you can also try the patched .deb-package (built from current Debian sources fetched with {{cmd|apt-get source|}}) from [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_fingerprint_reader this page], which also has Debian-specific instructions on how to setup the fingerprint reader. Use it on your own risk.

==Troubleshooting and Hints==
# After installing the driver, don't forget to reboot!
## This might not be necessary. it worked here without having to reboot.
# To see if the fingerprint device is know on the USB bus do:
:{{cmdroot|lsusb}}
:as root and you should see a line like:
:{{cmdresult|Bus 003 Device 004: ID 0483:2016 SGS Thomson Microelectronics}}
:The bus and device number can be different. This should work without the driver installed. If the device does not show up, you have a hardware problem/quirk, Rebooting or removing/inserting USB kernel modules might fix this.
# For some installation, after installing the driver as in section [[#Installing the driver|Installing the driver]] and makingÂ´sure the device is recognized, try to test it by going to {{path|NonGUI_Sample}} directory and run {{cmdroot|./Sample}}, one get segmentation fault. In this case, try getting the Beta1 instead of Beta2 of the driver and installing it
# There was some confusion about the /etc/bioapi1.10/pam{5550454b-2054-464d-2f45-535320425350} path, this has been fixed in the howto, if you have problems, check the section again, the path needs to have the '-' in them
# When something goes wrong look at the tail of {{path|/var/log/auth.log}}. (on {{Fedora}} it is {{path|/var/log/secure}}) Specifically if you see an entry saying something like
pam_bioapi[10480]: Unable to load BioAPI BSP with UUID of {5550454b-2054-464d-2f45-535320425350}, BioAPI error <nowiki>#</nowiki>194d.
Check whether your {{path|/proc/bus/usb}} directory permissions are set up as in the
section [[#Installing the driver|Installing the driver]].
# To get the xscreensaver compiled you might need a bunch of header files (depending on which xscreensaver features you want), in my case I need the following:
#*python-gtk2-dev
#*libgstreamer0.8-dev
#*xlibs-dev
# Sometimes {{path|$HOME/.xscreensaver}} got overwritten, try changing it to read-only.
# If after suspending to RAM and resume, lsusb no longer have "SGS Thomson Microelectronics" entry, try adding a line
:{{cmdroot|/etc/init.d/hotplug restart}}
to your {{path|/etc/acpi/resume.sh}} file
#If after resume lsusb shows the device but xscreensaver does not ask for fingerprint for login, you might want to check the permission of the usb bus in the appropriate {{path|/proc/bus/usb/}} entry. If necessesary you might need to add a line to {{path|/etc/acpi/resume.sh}} as in section [[#Installing the driver|Installing the driver]] to set the permission right.
-----
If it still doesn't work, ask me for help (and make sure all usefull stuff makes it back into this wiki :)
to get a starting point as to where your problem is please include the output of:

:{{cmduser|lsusb}}

:{{cmdroot|ldconfig -p <nowiki>|</nowiki> grep bioapi}}

:{{cmdroot|updatedb && locate bioapi}}

t43fingerprint (at) badcode.de

(15.12.2005: small Gentoo-update! {darcline (at) gmx.net} with a now fully operational Thinkpad X41 running Gentoo and E17)
Thank you badcode!

(20.12.2005: small Suse-update! {marten.gustafson (at) gmail.com} now with a fully operational Thinkpad T43 running Suse 10)
Thanks!

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-01-07T23:52:56Z

Tvon: /* Related Links */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver.

=== ThinkPads this card may be found in ===
* {{Z60t}}

=== Related Links ===
* [http://www.madwifi.org MadWifi project page]
* [http://madwifi.org/ticket/263 MadWifi ticket #263]

[[Category:Components]]

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-01-07T23:52:40Z

Tvon:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver.

=== ThinkPads this card may be found in ===
* {{Z60t}}

=== Related Links ===
[http://www.madwifi.org MadWifi project page]
[http://madwifi.org/ticket/263 MadWifi ticket #263]

[[Category:Components]]

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-01-07T23:51:19Z

Tvon:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver.

=== ThinkPads this card may be found in ===
* {{Z60t}}

=== Related Links ===
[http://www.madwifi.org MadWifi project page]

[[Category:Components]]

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-01-07T23:50:57Z

Tvon: /* Linux WiFi driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver. Known success with madwifi-ng from SVN trunk.

=== ThinkPads this card may be found in ===
* {{Z60t}}

=== Related Links ===
[http://www.madwifi.org MadWifi project page]

[[Category:Components]]

ThinkPad 11a/b/g Wireless LAN Mini Express Adapter

2006-01-07T23:28:18Z

Tvon: /* Related Links */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad 11a/b/g Wireless LAN Mini Express Adapter ===
This is a WiFi Adapter that is installed in a Mini-PCI Express slot

=== Features ===
* Chipset: Atheros AR5006EX
* Integrated Mac Processor and Radio Chip: Atheros 5424
* IEEE Standards: 802.11a, 802.11b, 802.11g
* PCI ID: ??
</div>
|style="vertical-align:top" |
[[image:mini-pci-wifi-card.gif|Mini-PCI WiFi Adapter]]
|}

=== IBM Partnumbers ===
IBM Option PN (US): 40Y7026

=== Linux WiFi driver ===
Try the [[Madwifi]] driver.

=== ThinkPads this card may be found in ===
* {{Z60t}}

=== Related Links ===
[http://www.madwifi.org MadWifi project page]

[[Category:Components]]

Madwifi

2006-01-05T00:25:01Z

Tvon: Added lines for SVN. I think CVS no longer updated (unless they have a svn->cvs sync setup)

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)

=== Packages ===
*daily cvs snapshots: http://madwifi.otaku42.de
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}

=== CVS ===
(obsolete?)
:{{cmduser|cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi}}

=== SVN ===

Full instructions can be found [http://madwifi.org/wiki/UserDocs/GettingMadwifi on the MadWiFi Wiki].

* madwifi-ng:
:{{cmduser|svn checkout http://svn.madwifi.org/trunk madwifi-ng}}
* madwifi-old (same as CVS above?):
:{{cmduser|svn checkout http://svn.madwifi.org/branches/madwifi-old madwifi-old}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://www.madwifi.org/wiki MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]
* [http://www.ath-driver.org/ OpenSource Atheros driver for Linux]

[[Category:Drivers]]

Madwifi

2006-01-03T23:59:46Z

Tvon: /* Packages */

== Multiband Atheros Driver for WiFi ==
Linux driver for 802.11a/b/g universal NIC cards - Cardbus, PCI, or miniPCI - using Atheros chip sets.

The following adapters sold by IBM use the Atheros chips:
* [[IBM Dual-Band 11a/b Wi-Fi Wireless Mini PCI Adapter]]
* [[IBM 11b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
* [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
* [[ThinkPad 11a/b/g Wireless LAN Mini Express Adapter]]
* IBM 802.11a Wireless LAN Cardbus Adapter
* IBM 11 a/b/g Wireless Cardbus Adapter

=== Project Homepage ===
http://www.madwifi.org (old page: http://sourceforge.net/projects/madwifi)

=== Packages ===
*daily cvs snapshots: http://madwifi.otaku42.de
*{{Debian}} Packages: http://www.marlow.dk/site.php/tech/madwifi
*{{Debian}} Packages: http://www.users.tpg.com.au/sigm/misc/madwiki.txt
*{{Fedora}} Packages(1): http://rpm.livna.org
*{{Fedora}} Packages(2): http://www.atrpms.net/name/madwifi/
*{{Ubuntu}} Package: {{cmduser|sudo apt-get install linux-restricted-modules-`uname -r`}}

=== CVS ===
:{{cmduser|cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi co madwifi}}

=== Installation ===

*Make sure that you've got sysctl support and the net/radio enabled (wireless extensions) in your kernel. Install the driver with make & make install
* further more you like to install the wireless tools from [http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html wireless tools]. Make sure the versions fit together by
:{{cmduser|iwconfig --version}}

Setting up [[wpa_supplicant]] with wpa-psk.

=== Status ===
in development, usable

=== OpenSource HAL ===
The "official" driver consists of an opensource wrapper with binary HAL (Hardware Abstraction Layer). This HAL is not a binary firmware like with the Intel Wireless chips, but a piece of code that needs to runs in the Linux kernel.
The vendors reasoning behind this is, that since the Atheros chip could be tuned to any frequency, and hence interfere with systems operating in those frequencies, that we simply need to accept this binary module.<br>
Obviously this binary HAL is unacceptable to the Linux kernel developers, and the Atheros driver in this state will never become part of the official kernel.<br>
Some OpenBSD developers facing the same issue, reverse engineered the binary HAL and have produced an OpenSource version. Hopefully a driver based on this might be included with the Linux kernel at some point in time, and picked up by the mainstream distributions.

=== Related links ===
* [http://www.madwifi.org/wiki MadWiFi Wiki]
* [http://team.vantronix.net/ar5k/ OpenSource Atheros HAL]
* [http://www.ath-driver.org/ OpenSource Atheros driver for Linux]

[[Category:Drivers]]