#1708: problem with 802.11a mode (kernel panic with v0.9.3.3 and no-function
with
svn-3077)
-------------------------------------------+--------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version: v0.9.3.3
Resolution: | Keywords:
Patch_attached: 0 |
-------------------------------------------+--------------------------------
Old description:
> System: 64bits Gentoo (amd64), kernel 2.6.23 or 2.6.22, gcc 4.2.2,
> wireless card: 3COM 3CRDAG675 (pci).
> Problem: using stable v0.9.3.3 ath_pci in _master_ mode the selection of
> any 5GHz-channel (i.e. trying to use 802.11a) causes kernel panic after
> 5-10 seconds and complete blockage of the system. Using svn-3077 version
> the selection of 802.11a channels has no effect (channel simply does not
> change, may be it is a temporary workaround for the known problem?). In
> 802.11g the setup works without problems. Do not know if it is relevant
> if the card in master or managed mode. I was updating from kernel 2.6.14
> and unknown madwifi version (where all worked fine) as the problem first
> arises. Due to the problem no unattended/unmanaged boot was possible
> before I recognized that the problem was because of 802.11a. Not really a
> critical problem for me, but may be a problem for those people who can
> not boot after kernel update.
New description:
System: 64bits Gentoo (amd64), kernel 2.6.23 or 2.6.22, gcc 4.2.2,
wireless card: 3COM 3CRDAG675 (pci).
Problem: using stable v0.9.3.3 ath_pci in _master_ mode the selection of
any 5GHz-channel (i.e. trying to use 802.11a) causes kernel panic after
5-10 seconds and complete blockage of the system. Using r3077 version the
selection of 802.11a channels has no effect (channel simply does not
change, may be it is a temporary workaround for the known problem?). In
802.11g the setup works without problems. Do not know if it is relevant
if the card in master or managed mode. I was updating from kernel 2.6.14
and unknown madwifi version (where all worked fine) as the problem first
arises. Due to the problem no unattended/unmanaged boot was possible
before I recognized that the problem was because of 802.11a. Not really a
critical problem for me, but may be a problem for those people who can not
boot after kernel update.
--
Ticket URL: <http://madwifi.org/ticket/1708#comment:1>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
