Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Fedora Core 5, Ubuntu 6.06 (Breezy), testing Solaris 10
Have you used ndiswrapper to install it yet? (Your system can pick up the card as hardware but you can't use it unless you've used ndiswrapper to configure the drivers.) Ndiswrapper on suse should be included.
check out a program called mad-wifi. It is a frontend program that can help you setup different profiles for your adapter. If it recognizes it though just try dhclient or dhcpcd <wireless interface name>
We need more technical info than just what the GUI tells you. Some points that haven't been considered so far -
What is the chipset of the wireless card? You do NOT necessarily need ndiswrapper or madwifi to connect the wireless card to your network. I am writing this response on a Thinkpad T42 using the wireless card, and have neither of those programs installed. After the card has been around for a while, the modules and drivers for it often get included into the kernel. The ipw2200 modules that power my wireless NIC have been included in the kernel since 2.6.14. In that way, having an older laptop helps you, as it increases the chances that the required componets already exist. Ndiswrapper is popular because it allows you to use windows drivers to power your card. Please give us the output of the command "lspci". Some distros require you to be root for that to work. We are looking for the info about your wireless card. For example, the last line of my lspci are
Since you don't have Suse autodetecting your card, you may need to build the modules for your card, and put them into the kernel. I suggest you take a look at http://tuxmobil.org/mylaptops.html to see if your particular laptop has had a linux install with functional wireless done on it. They usually write up how to accomplish it.
Please do as jstephens84 asked. We need to see what your computer sees, and the Yast utilty doesn't tell us what we want to know. If lspci -v lists nothing as your regular user, than please run it as root.
02:04.0 Ethernet controller: Linksys, A Division of Cisco Systems [AirConn] INPR
OCOMM IPN 2220 Wireless LAN Adapter (rev 01)
Subsystem: AMBIT Microsystem Corp. Unknown device 0305
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at 3800 [size=32]
Memory at e020a000 (32-bit, non-prefetchable) [size=32]
Memory at e0209000 (32-bit, non-prefetchable) [size=2K]
Capabilities:  Power Management version 2
That is what we were looking for. All the postings I see on google.com/linux with INPROCOMM IPN 2220 Wireless LAN Adapter show it only works under linux with ndiswrapper, where the windows driver gets loaded into the linux kernel.
In order to accomplish this, you'll need to hunt down the Suse rpm for ndiswrapper. I would guess such a thing exists, although I don't know as I avoid rpm distros as if they were diseases. You may need to get full kernel sources, change the size of the kernel stacks, and other things. The benefit of candy distros like Suse in a case like this is yast or whatever package manager you use will probably accomplish all of this for you. You'll also need the windows drivers for the card. Install ndiswrapper, and follow the instructions that google points you at.
The ipw2200 modules that power my wireless NIC have been included in the kernel since 2.6.14. In that way, having an older laptop helps you, as it increases the chances that the required componets already exist. For example, the last line of my lspci are
I am really struggling to make the ipw2200 work on my VAIO with Slackware. Can you tell me what you had to do to make it work, or any information that might be helpful regarding this wireless card? Thanks in advance.
Sure! The easiest thing would be to make sure you have a recent kernel. Seeing that you're a current slacker means you could be anywhere from 2.4.31 up to the newest of the 2.6 series. The ipw2200 became part of the standard kernel in 2.6.14, so as long as your kernel is more recent than that, you should be most of the way there.
The first time I connected, I had to modprobe both for the ipw2200 module, along with the much more generic ieee80211 module. The order was important though, you had to modprobe the ieee80211 first, then modprobe the ipw2200.
I've also had very good luck with the wireless tools package. It provides the iwconfig utility. You can find the page about wireless tools (and downloads) here
Once that is done, you can do something like dhclient eth1 (or whatever slackware calls your card. It could be the eth1, sit0, irda0 etc. You can also modify the file where your ethernet cards are identified, and add an entry for the wireless card, then restart networking.
If that doesn't do it, I would think the kernel might need to be recompiled making sure you have all the drivers for the chip included as modules or built directly into the kernel.