[prism54 driver] Can't connect to AP on channel 13

Bug #9034 reported by Martijn vdS
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Invalid
Medium
Ben Collins

Bug Description

One of my neighbors bought an AP, and put it on channel 6, next to mine. Because
this brings down my data rates considerably, I decided to move to another
channel. Because most products in Europe don't support channel 13 even if they
can, I figured it'd be safe.

After switching my AP to channel 13, I suddenly couldn't connect to it anymore.
My card (SMC 2835W, prism54) started "channel-hopping": every time I ran
iwconfig, the channel would be different, and it didn't seem to be possible to
connect to the network.

"iwlist eth0 scan" DOES tell me there's an ap on channel 13 available, and if I
use another card (SMC2632-V2, using atmel_cs) I can connect to it (after running
'iwpriv eth0 regdomain europe', because it defaults to US for some reason)

Revision history for this message
Matt Zimmerman (mdz) wrote :

Does it work if you force the card to channel 13? (iwconfig ... chan 13)

Revision history for this message
Martijn vdS (martijn) wrote :

No, it keeps cycling

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

is this fixed in new kernels by any chance?

Revision history for this message
Ben Collins (ben-collins) wrote :

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Revision history for this message
Ben Collins (ben-collins) wrote :

Closing, inactive.

Revision history for this message
Aleksandr (akonstantinov) wrote :

I confirm that this problem still exists in linux-2.6.17.11 .
I'm having this problem right now with SM2835W card.
I also tried all firmwares i could find up to 1.0.4.3 .

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.