Bug 117618 - Trouble to wireless network-IBM T42P atheros a/b/g
Summary: Trouble to wireless network-IBM T42P atheros a/b/g
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: RC 1
Hardware: i686 All
: P5 - None : Major
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-17 05:41 UTC by Ron Terry
Modified: 2006-02-09 16:44 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Terry 2005-09-17 05:41:43 UTC 
Either takes extremliy long time to connect (10 miniutes +) or does not connect
at all.  Wireless signal is strong (3' from AP).

I was finally able to get it to connect to my home wireless network but it would
never connect to onenet (Novell Provo campus).

I was able to connect to onenet and home network in NLD9 on the same laptop
without problems.

This problem started happening in SUSE 9.3 as well.  It worked just fine at
first but started having problems about 4 months after install.  I suspect it
was something to do with a YOU update.

UPDATE:
It seems to be connecting to my home network consistantly now that it has
connected once.  The problem may be related to the initial association with an AP.
Comment 1 Ron Terry 2005-09-19 14:17:43 UTC 
The problem seems to be with onenet (Provo Campus).  It will not connect.  I am
wondering if it is a problem with 802.11b networks.
Comment 2 Stefan Behlert 2005-09-27 14:05:46 UTC 
Is this problem still persistent in the final RC4?
Comment 3 Joachim Gleissner 2005-10-17 10:21:46 UTC 
Could you test whether setting the card to 802.11b only ('iwpriv ath0 mode 2') helps?
Comment 4 Stefan Behlert 2005-11-24 10:54:15 UTC 
Anything new here?
Comment 5 Joachim Gleissner 2006-02-09 16:44:05 UTC 
No further information -> closing as invalid. Please reopen in case the problem still exists.