03-26-2008
I am surprised to read such a remark.
Linux has the biggest amount of wireless drivers on earth now. After all, most of the cell phones and stand-alone wireless devices today are using Linux as their core OS, with a kiosk browser based front end for navigation.
Add your hardware (IBM) which have thrown its 800 lbs. weight behind Linux in full force, and you have your driver waiting for you out there to get it.
Even if it is not there, just declaring that 'Linux is short of a driver for a wireless IBM card' is enough to ignite many Linux programmers world wide to rise up to that challenge, and respond to you, personally.
Passing the ideology, going technical; What is your card?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Im running mandrake 9.0 and i just got a Lucent/orinoco PC24E-H-FC. I beleive it was originaly made by lucent but then made by Orinoco.. But anyways i just cant get connected. Ive tried 3 differemt drivers. My wireless access point router is a Linksys. I just cant figure this out ive talked on... (3 Replies)
Discussion started by: jason1234
3 Replies
2. Linux
I just recently bought a HP Pavilion zt3020us and it had came with an internal WiFi NIC (Intel(R) PRO/Wireless LAN 2100 3B Mini PCI Adapter) and I was wondering where I could go to find a device driver for it under Mandrake 9.1 Linux. (2 Replies)
Discussion started by: N0C717
2 Replies
3. Windows & DOS: Issues & Discussions
I have a wireless setup in my house and i connect my laptop thru the wireless setup ..
The problem is that one of my other friends has a wireless setup too and his wireless signal comes to my house too ..
The effect is that it drops my service after sometime and connects to it .. then drops... (3 Replies)
Discussion started by: DPAI
3 Replies
4. Linux
I am running FC4:
Linux maincomp 2.6.13-1.1532_FC4smp
I recently changed the OS from windows XP, and have a feeling that for some reason my wireless network card is slower on Fedora Core 4. The Belkin PCI 802.11b card was automatically detected and configured by FC4 when I installed the OS,... (0 Replies)
Discussion started by: dangral
0 Replies
5. Linux
I'm trying to get my wireless card up. I've been at it for a while now and something just isn't quite working right. I'm not getting any wireless signal. I'm using FC4 with a stack 16 kernel and ndiswrappr to load my drivers.
here are the outputs that i get.
Alittle bit about my... (3 Replies)
Discussion started by: byblyk
3 Replies
6. Solaris
I need to install a driver for my RT2500 PCI wireless network card on my Solaris 10.
So I went to the ralink website (the manufacturer of the network card), and downloaded the linux (well supposedly the unix driver) binary file. Burned it to dvd, and copied from the dvd to my solaris computer.... (3 Replies)
Discussion started by: Xannen
3 Replies
7. IP Networking
I'm not what this is called so I don't exactly know what to search for to do my homework.:D But I have two IBM T40's and only one wireless internet card. I don't have to money to buy another wireless card, so my question is this: Can I use the card on one system and use an ethenet cable linked... (2 Replies)
Discussion started by: Texasone
2 Replies
8. Red Hat
Hello,
I'm extremely new to Linux. I've been a windows admin for years stupid me, should have got into Linux way back. So now playing catch up. I was hoping someone could help me get started. I've been online reading but getting confused a lot of info and very different from windows.
I... (0 Replies)
Discussion started by: kidsusuki
0 Replies
9. Programming
Hi all,
In my program, I am trying to use ioctl to turn on/off the wireless card, using SIOCSIFFLAGS (I am new to it but somebody said it is the most traditional way). However, it seems that I didn't set the flag correctly since the wireless is always on (I have root permission). If any one... (2 Replies)
Discussion started by: tetelee
2 Replies
10. Hardware
hi
Howto identify wireless network card using Live CD? (2 Replies)
Discussion started by: ccc
2 Replies
LEARN ABOUT SUNOS
iwevent
IWEVENT(8) Linux Programmer's Manual IWEVENT(8)
NAME
iwevent - Display Wireless Events generated by drivers and setting changes
SYNOPSIS
iwevent
DESCRIPTION
iwevent displays Wireless Events received through the RTNetlink socket. Each line displays the specific Wireless Event which describes what
has happened on the specified wireless interface.
This command doesn't take any arguments.
DISPLAY
There are two classes of Wireless Events.
The first class is events related to a change of wireless settings on the interface (typically done through iwconfig or a script calling
iwconfig). Only settings that could result in a disruption of connectivity are reported. The events currently reported are changing one of
the following setting :
Network ID
ESSID
Frequency
Mode
Encryption
All those events will be generated on all wireless interfaces by the kernel wireless subsystem (but only if the driver has been converted
to the new driver API).
The second class of events are events generated by the hardware, when something happens or a task has been finished. Those events include :
New Access Point/Cell address
The interface has joined a new Access Point or Ad-Hoc Cell, or lost its association with it. This is the same address that is
reported by iwconfig.
Scan request completed
A scanning request has been completed, results of the scan are available (see iwlist).
Tx packet dropped
A packet directed at this address has been dropped because the interface believes this node doesn't answer anymore (usually maximum
of MAC level retry exceeded). This is usually an early indication that the node may have left the cell or gone out of range, but it
may be due to fading or excessive contention.
Custom driver event
Event specific to the driver. Please check the driver documentation.
Registered node
The interface has successfully registered a new wireless client/peer. Will be generated mostly when the interface acts as an Access
Point (mode Master).
Expired node
The registration of the client/peer on this interface has expired. Will be generated mostly when the interface acts as an Access
Point (mode Master).
Spy threshold crossed
The signal strength for one of the addresses in the spy list went under the low threshold or went above the high threshold.
Most wireless drivers generate only a subset of those events, not all of them, the exact list depends on the specific hardware/driver com-
bination. Please refer to driver documentation for details on when they are generated, and use iwlist(8) to check what the driver supports.
AUTHOR
Jean Tourrilhes - jt@hpl.hp.com
SEE ALSO
iwconfig(8), iwlist(8), iwspy(8), iwpriv(8), wireless(7).
net-tools 23 June 2004 IWEVENT(8)