Problem with Cisco wireless card under Suse Linux 10.1

Hello,

Could anyone please help me out in the following problem?

Hardware:

* IBM laptop Thinkpad T30 Type 2366-B1U S/N 78-HFTB9 08/02

* Cisco PCMCIA card Aironet 340 11 Mbps 2.4GHz DS


System software:

* dual boot machine Windows XP and Linux

* Suse Linux 10.1, 'uname -rv' says '2.6.16.21-0.25-default #1 Tue Sep
19 07:26:15 UTC 2006', all patches duly downloaded and installed;
using KDE

* infos from YaST/Network Devices/Cisco 340 Series Wireless LAN Adapter:
Hardware Details:
Hardware Configuration Name: bus-pcmcia-0.0
Module Name: airo_cs
(that is what it came up with at the installation of Suse)


Symptoms:

* under Suse Linux, I cannot get wireless connection to local WLAN;
KWiFiManager shows excelent signal strength, KNetworkManager shows
that the little blue progress bar for the connection process stops at
about 2/3 of full length, SSID of local WLAN is recognized in both
cases

* under Windows XP wireless connection looks okay


What can I do to make the wireless card work under Suse Linux?

In you reply, please be specific as I am not a Linux expert at all.

Thank you for your time and help,

Starl8gazer

(E-Mail Removed) wrote:
> Hello,
>
> Could anyone please help me out in the following problem?
>
> Hardware:
>
> * IBM laptop Thinkpad T30 Type 2366-B1U S/N 78-HFTB9 08/02
>
> * Cisco PCMCIA card Aironet 340 11 Mbps 2.4GHz DS
>
>
> System software:
>
> * dual boot machine Windows XP and Linux
>
> * Suse Linux 10.1, 'uname -rv' says '2.6.16.21-0.25-default #1 Tue Sep
> 19 07:26:15 UTC 2006', all patches duly downloaded and installed;
> using KDE
>
> * infos from YaST/Network Devices/Cisco 340 Series Wireless LAN Adapter:
> Hardware Details:
> Hardware Configuration Name: bus-pcmcia-0.0
> Module Name: airo_cs
> (that is what it came up with at the installation of Suse)
>
>
> Symptoms:
>
> * under Suse Linux, I cannot get wireless connection to local WLAN;
> KWiFiManager shows excelent signal strength, KNetworkManager shows
> that the little blue progress bar for the connection process stops at
> about 2/3 of full length, SSID of local WLAN is recognized in both
> cases
>
> * under Windows XP wireless connection looks okay
>
>
> What can I do to make the wireless card work under Suse Linux?
>
> In you reply, please be specific as I am not a Linux expert at all.
>
> Thank you for your time and help,
>
> Starl8gaze

That's the problem with Linux when it comes right down do it, no damn
support. I got nothing against Linux I got Suse myself, but if you want
support you got to pay, which is not unlike MS.

> That's the problem with Linux when it comes right down do it, no damn
> support. I got nothing against Linux I got Suse myself, but if you want
> support you got to pay, which is not unlike MS.

I assume thats why the OP posted here for sensible answers unlike your
idiotic reply.

Dave

On Fri, 01 Dec 2006 07:18:30 +0000, gort <(E-Mail Removed)> wrote in
<(E-Mail Removed)>:

>
>> That's the problem with Linux when it comes right down do it, no damn
>> support. I got nothing against Linux I got Suse myself, but if you want
>> support you got to pay, which is not unlike MS.
>
>I assume thats why the OP posted here for sensible answers unlike your
>idiotic reply.

The only thing idiotic is childish name calling.

Support is in fact a significant issue with Linux.

--
Best regards, FAQ for Wireless Internet: <http://Wireless.wikia.com>
John Navas FAQ for Wi-Fi: <http://wireless.wikia.com/wiki/Wi-Fi>
Wi-Fi How To: <http://wireless.wikia.com/wiki/Wi-Fi_HowTo>
Fixes to Wi-Fi Problems: <http://wireless.wikia.com/wiki/Wi-Fi_Fixes>

(E-Mail Removed) wrote:
> Hello,
>
> Could anyone please help me out in the following problem?
>
> Hardware:
>
> * IBM laptop Thinkpad T30 Type 2366-B1U S/N 78-HFTB9 08/02
>
> * Cisco PCMCIA card Aironet 340 11 Mbps 2.4GHz DS
>
>
> System software:
>
> * dual boot machine Windows XP and Linux
>
> * Suse Linux 10.1, 'uname -rv' says '2.6.16.21-0.25-default #1 Tue Sep
> 19 07:26:15 UTC 2006', all patches duly downloaded and installed;
> using KDE
>
> * infos from YaST/Network Devices/Cisco 340 Series Wireless LAN Adapter:
> Hardware Details:
> Hardware Configuration Name: bus-pcmcia-0.0
> Module Name: airo_cs
> (that is what it came up with at the installation of Suse)
>
>
> Symptoms:
>
> * under Suse Linux, I cannot get wireless connection to local WLAN;
> KWiFiManager shows excelent signal strength, KNetworkManager shows
> that the little blue progress bar for the connection process stops at
> about 2/3 of full length, SSID of local WLAN is recognized in both
> cases
>
> * under Windows XP wireless connection looks okay
>
>
> What can I do to make the wireless card work under Suse Linux?
>
> In you reply, please be specific as I am not a Linux expert at all.
>
> Thank you for your time and help,
>
> Starl8gazer
That sounds like the radio part is ok.
We need to know a little bit more, though.
Presumably you have configured an IP address/netmask or is it DHCP?
What does iwconfig eth1 (I'm blindly assuming eth0 is the ethernet port
and eth1 is the wireless port) say?
Are you using WEP?

Werner

gort wrote:
>>That's the problem with Linux when it comes right down do it, no damn
>>support. I got nothing against Linux I got Suse myself, but if you want
>>support you got to pay, which is not unlike MS.
>
>
> I assume thats why the OP posted here for sensible answers unlike your
> idiotic reply.
>
> Dave

How sad, let us see some of that technical expertise out of you,
partner, in the wireless NG about Linux. The fact remains there is no
abundant support for Linux and it's a problem, for the average Job Blow
home user. And if you have to post to a Linux NG, then you're most
likely going to be called a bunch of names for making the post, which is
not unlike you have done here.

>
> How sad, let us see some of that technical expertise out of you,
> partner, in the wireless NG about Linux. The fact remains there is no
> abundant support for Linux and it's a problem, for the average Job Blow
> home user. And if you have to post to a Linux NG, then you're most
> likely going to be called a bunch of names for making the post, which is
> not unlike you have done here.

Ok aside from your silliness, why don't you ask the OP which chipset is
actually on the wireless card as there are well know ones for which
excellent solutions exist. Most problems with wireless and linux CAN be
solved unlike your sweeping inaccurate statement. Support exists in lots of
places for linux users, man pages and newsgroups like these are just 2. I
have had lots of excellent support over the years and given plenty back.
THe fact remains that twats like you put off people from getting to grips
with linux by spreading FUD ( do you work for a large Redmond based company
by any chance?).
Stick to windows, it very user friendly HA HA.

Dave

gort wrote:
>>How sad, let us see some of that technical expertise out of you,
>>partner, in the wireless NG about Linux. The fact remains there is no
>>abundant support for Linux and it's a problem, for the average Job Blow
>>home user. And if you have to post to a Linux NG, then you're most
>>likely going to be called a bunch of names for making the post, which is
>>not unlike you have done here.
>
>
> Ok aside from your silliness, why don't you ask the OP which chipset is
> actually on the wireless card as there are well know ones for which
> excellent solutions exist. Most problems with wireless and linux CAN be
> solved unlike your sweeping inaccurate statement. Support exists in lots of
> places for linux users, man pages and newsgroups like these are just 2. I
> have had lots of excellent support over the years and given plenty back.
> THe fact remains that twats like you put off people from getting to grips
> with linux by spreading FUD ( do you work for a large Redmond based company
> by any chance?).
> Stick to windows, it very user friendly HA HA.
>
> Dave

Why don't you ask the questions and give the support instead of running
your mouth on this or are you're too superior like most tend to think
they are, when it comes to using Linux, just like you're showing here,
once again?

Linux is not user friendly and it's a problem for the platform from the
average Joe Blow home user, prespective. It has to be corrected, because
they are not going to come to NG's and ask questions. They will pick up
the phone to ask a 3rd party vendor about some software they are tyring
to use or install on the Linux platform, only to get the response, we
don't support Linux.

You need to go hurt yourself on your computer and drop dead, partner.

Anyway, I am already tired of you and your mouth.

You're just another lunatic home user running Linux.

adios muchacho

> Anyway, I am already tired of you and your mouth.
>
> You're just another lunatic home user running Linux.
>
> adios muchacho

Yes I was just about to tell you to fuck off and go back to playing with
Uncle Bill

<plank> - soft logical <plonk>

You should have your mama change your Pamper, give you your bottle with
Riddlin and Prozac to calm you down - you're loose out of the play
pin, and she can then put you in street traffic, where you can play,
wirelessly. You don't have to drop dead that way. It will be painless
for you when the MAC truck hits you, ridding your tricycle with red
wagon in tow.

You can call Sir Hollywood News Clippings Willy/aka Billy to come and
get you, if they can scrape you off the street, partner.