I have the gigafast WF728-AEX, which doesn't seem to work with the
p54pci drivers, I was previously using it with my Thinkpad T23 under
Gentoo (gentoo kernels 2.6.29 and 2.6.30), and could only use the
1.0.4.3 firmware, now, I am using it under Ubuntu 9.04
(2.6.28-15-generic kernel) on the same computer, and find that I have
to load the prism54 driver to make it work.
I noticed that you were considering this to be depricated, I hope that
you can help me to make p54pci work!
Thanks
James
On Thu, Oct 8, 2009 at 9:28 AM, Larry Finger <[email protected]> wrote:
> On 10/07/2009 04:00 PM, James Grossmann wrote:
>>
>> I have the gigafast WF728-AEX, which doesn't seem to work with the
>> p54pci drivers, I was previously using it with my Thinkpad T23 under
>> Gentoo (gentoo kernels 2.6.29 and 2.6.30), and could only use the
>> 1.0.4.3 firmware, now, I am using it under Ubuntu 9.04
>> (2.6.28-15-generic kernel) on the same computer, and find that I have
>> to load the prism54 driver to make it work.
>> I noticed that you were considering this to be depricated, I hope that
>> you can help me to make p54pci work!
>
> As it works with 2.6.29 and 2.6.30 kernels, but not with 2.6.28, it seems
> likely that you need a later version of the driver. Does Ubuntu have a
> package for compat-wireless? If so, install it. If not, you will need to
> install from source.
James, please do test with a new driver and appropriate firmware and
let us know if it worked or not.
Luis
On Saturday 31 October 2009 15:11:37 James Grossmann wrote:
> [ 4200.794299] cfg80211: Calling CRDA to update world regulatory
> domain
> [ 4200.857330] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
> (level, low) -> IRQ 11
> [ 4200.857408] p54pci 0000:03:00.0: firmware: requesting isl3886pci
> [ 4201.432596] phy0: p54 detected a LM86 firmware
> [ 4201.432604] p54: rx_mtu reduced from 3240 to 2376
> [ 4201.432610] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
> [ 4201.432616] phy0: cryptographic accelerator WEP:YES, TKIP:YES,
> CCMP:YES
> [ 4202.293254] phy0: EEPROM is damaged... you may not be able to use
> all channels with this device.
^^^ = that's the culprit.
do you think, you can get this EEPROM dump?
Just move the attach _patch_ into your compat-wireless' main directory.
Afterward, you have to execute:
patch -p1 < p54-dump-eeprom-to-dmesg.diff
and rebuild & reload the driver and retrieve the data
from dmesg.
> [ 4202.293286] phy0: [iqauto calibration data] is/are missing for
> channel:2 [2417 MHz].
> [ 4202.293293] phy0: [iqauto calibration data] is/are missing for
> channel:3 [2422 MHz].
> [ 4202.293300] phy0: [iqauto calibration data] is/are missing for
> channel:4 [2427 MHz].
> [ 4202.293306] phy0: [iqauto calibration data] is/are missing for
> channel:5 [2432 MHz].
> [ 4202.293313] phy0: [iqauto calibration data] is/are missing for
> channel:6 [2437 MHz].
> [ 4202.293320] phy0: [iqauto calibration data] is/are missing for
> channel:8 [2447 MHz].
> [ 4202.293326] phy0: [iqauto calibration data] is/are missing for
> channel:9 [2452 MHz].
> [ 4202.293333] phy0: [iqauto calibration data] is/are missing for
> channel:10 [2457 MHz].
> [ 4202.293340] phy0: [iqauto calibration data] is/are missing for
> channel:11 [2462 MHz].
> [ 4202.293346] phy0: [iqauto calibration data] is/are missing for
> channel:12 [2467 MHz].
> [ 4202.293356] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
> [ 4202.293787] phy0: Selected rate control algorithm 'minstrel'
> [ 4202.295616] Registered led device: p54-phy0::assoc
> [ 4202.295657] Registered led device: p54-phy0::tx
> [ 4202.295703] Registered led device: p54-phy0::rx
> [ 4202.295744] Registered led device: p54-phy0::radio
> [ 4202.295758] p54pci 0000:03:00.0: is registered as 'phy0'
> [ 4202.378618] udev: renamed network interface wlan0 to wlan1
> [ 4202.509483] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 4202.724125] phy0: frequency change to channel 2 failed.
> [ 4202.724138] phy0: frequency change to channel 3 failed.
> [ 4202.724145] phy0: frequency change to channel 4 failed.
> [ 4202.724151] phy0: frequency change to channel 5 failed.
> [ 4202.724157] phy0: frequency change to channel 6 failed.
> [ 4202.780179] phy0: frequency change to channel 8 failed.
> [ 4202.780193] phy0: frequency change to channel 9 failed.
> [ 4202.780199] phy0: frequency change to channel 10 failed.
> [ 4202.780206] phy0: frequency change to channel 11 failed.
> [ 4202.780212] phy0: frequency change to channel 12 failed.
> [ 4208.212168] phy0: frequency change to channel 2 failed.
> [ 4208.212180] phy0: frequency change to channel 3 failed.
> [ 4208.212187] phy0: frequency change to channel 4 failed.
> [ 4208.212193] phy0: frequency change to channel 5 failed.
> [ 4208.212199] phy0: frequency change to channel 6 failed.
> [ 4208.276097] phy0: frequency change to channel 8 failed.
> [ 4208.276112] phy0: frequency change to channel 9 failed.
> [ 4208.276119] phy0: frequency change to channel 10 failed.
> [ 4208.276125] phy0: frequency change to channel 11 failed.
> [ 4208.276132] phy0: frequency change to channel 12 failed.
> [ 4208.524788] phy0: frequency change to channel 6 failed.
> [ 4208.524949] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
> choice (reason=3)
> [ 4208.525084] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
> [ 4208.724191] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 2)
[...]
Regards,
Chr
On 10/07/2009 04:00 PM, James Grossmann wrote:
> I have the gigafast WF728-AEX, which doesn't seem to work with the
> p54pci drivers, I was previously using it with my Thinkpad T23 under
> Gentoo (gentoo kernels 2.6.29 and 2.6.30), and could only use the
> 1.0.4.3 firmware, now, I am using it under Ubuntu 9.04
> (2.6.28-15-generic kernel) on the same computer, and find that I have
> to load the prism54 driver to make it work.
> I noticed that you were considering this to be depricated, I hope that
> you can help me to make p54pci work!
As it works with 2.6.29 and 2.6.30 kernels, but not with 2.6.28, it
seems likely that you need a later version of the driver. Does Ubuntu
have a package for compat-wireless? If so, install it. If not, you
will need to install from source.
Larry
No help with the compat drivers:
[ 4185.320334] Unloaded prism54 driver
[ 4200.794299] cfg80211: Calling CRDA to update world regulatory
domain
[ 4200.857330] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
(level, low) -> IRQ 11
[ 4200.857408] p54pci 0000:03:00.0: firmware: requesting isl3886pci
[ 4201.432596] phy0: p54 detected a LM86 firmware
[ 4201.432604] p54: rx_mtu reduced from 3240 to 2376
[ 4201.432610] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
[ 4201.432616] phy0: cryptographic accelerator WEP:YES, TKIP:YES,
CCMP:YES
[ 4201.661701] cfg80211: World regulatory domain updated:
[ 4201.661710] (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 4201.661718] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 4201.661724] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[ 4201.661731] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[ 4201.661738] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 4201.661745] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 4202.293254] phy0: EEPROM is damaged... you may not be ableto use
all channels with this device.
[ 4202.293286] phy0: [iqauto calibration data] is/are missing for
channel:2 [2417 MHz].
[ 4202.293293] phy0: [iqauto calibration data] is/are missing for
channel:3 [2422 MHz].
[ 4202.293300] phy0: [iqauto calibration data] is/are missing for
channel:4 [2427 MHz].
[ 4202.293306] phy0: [iqauto calibration data] is/are missing for
channel:5 [2432 MHz].
[ 4202.293313] phy0: [iqauto calibration data] is/are missing for
channel:6 [2437 MHz].
[ 4202.293320] phy0: [iqauto calibration data] is/are missing for
channel:8 [2447 MHz].
[ 4202.293326] phy0: [iqauto calibration data] is/are missing for
channel:9 [2452 MHz].
[ 4202.293333] phy0: [iqauto calibration data] is/are missing for
channel:10 [2457 MHz].
[ 4202.293340] phy0: [iqauto calibration data] is/are missing for
channel:11 [2462 MHz].
[ 4202.293346] phy0: [iqauto calibration data] is/are missing for
channel:12 [2467 MHz].
[ 4202.293356] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
[ 4202.293787] phy0: Selected rate control algorithm 'minstrel'
[ 4202.295616] Registered led device: p54-phy0::assoc
[ 4202.295657] Registered led device: p54-phy0::tx
[ 4202.295703] Registered led device: p54-phy0::rx
[ 4202.295744] Registered led device: p54-phy0::radio
[ 4202.295758] p54pci 0000:03:00.0: is registered as 'phy0'
[ 4202.378618] udev: renamed network interface wlan0 to wlan1
[ 4202.509483] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 4202.724125] phy0: frequency change to channel 2 failed.
[ 4202.724138] phy0: frequency change to channel 3 failed.
[ 4202.724145] phy0: frequency change to channel 4 failed.
[ 4202.724151] phy0: frequency change to channel 5 failed.
[ 4202.724157] phy0: frequency change to channel 6 failed.
[ 4202.780179] phy0: frequency change to channel 8 failed.
[ 4202.780193] phy0: frequency change to channel 9 failed.
[ 4202.780199] phy0: frequency change to channel 10 failed.
[ 4202.780206] phy0: frequency change to channel 11 failed.
[ 4202.780212] phy0: frequency change to channel 12 failed.
[ 4208.212168] phy0: frequency change to channel 2 failed.
[ 4208.212180] phy0: frequency change to channel 3 failed.
[ 4208.212187] phy0: frequency change to channel 4 failed.
[ 4208.212193] phy0: frequency change to channel 5 failed.
[ 4208.212199] phy0: frequency change to channel 6 failed.
[ 4208.276097] phy0: frequency change to channel 8 failed.
[ 4208.276112] phy0: frequency change to channel 9 failed.
[ 4208.276119] phy0: frequency change to channel 10 failed.
[ 4208.276125] phy0: frequency change to channel 11 failed.
[ 4208.276132] phy0: frequency change to channel 12 failed.
[ 4208.524788] phy0: frequency change to channel 6 failed.
[ 4208.524949] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
choice (reason=3)
[ 4208.525084] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
[ 4208.724191] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 2)
[ 4208.924197] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 3)
[ 4209.124181] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx timed out
[ 4213.712173] phy0: frequency change to channel 2 failed.
[ 4213.712186] phy0: frequency change to channel 3 failed.
[ 4213.712193] phy0: frequency change to channel 4 failed.
[ 4213.712199] phy0: frequency change to channel 5 failed.
[ 4213.712205] phy0: frequency change to channel 6 failed.
[ 4213.768179] phy0: frequency change to channel 8 failed.
[ 4213.768193] phy0: frequency change to channel 9 failed.
[ 4213.768199] phy0: frequency change to channel 10 failed.
[ 4213.768206] phy0: frequency change to channel 11 failed.
[ 4213.768212] phy0: frequency change to channel 12 failed.
[ 4214.016190] phy0: frequency change to channel 6 failed.
[ 4214.016941] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
[ 4214.217439] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 2)
[ 4214.416177] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 3)
[ 4214.616183] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx timed out
On Sat, Oct 31, 2009 at 8:26 AM, Luis R. Rodriguez <[email protected]> wrote:
> Please keep the CC list here. This type of report is rare and we need
> it archived. Please try using wireless-testing or compat-wireless:
>
> http://wireless.kernel.org/en/users/Download
>
> ?Luis
>
> On Sat, Oct 31, 2009 at 6:15 AM, James Grossmann <[email protected]> wrote:
>> Attempted under Ubuntu 9.10, using their kernel 2.6.31-14-generic.
>> Unfortunately it still does not work, is it possible to load the
>> fullmac firmware through p54pci? ?just a thought...
>> Here's my relevant dmesg:
>> [ ? 15.369250] pcmcia_socket pcmcia_socket0: cs: IO port probe
>> 0x100-0x3af: clean.
>> [ ? 15.370157] pcmcia_socket pcmcia_socket0: cs: IO port probe
>> 0x3e0-0x4ff: excluding 0x4d0-0x4d7
>> [ ? 15.370585] pcmcia_socket pcmcia_socket0: cs: IO port probe
>> 0x820-0x8ff: clean.
>> [ ? 15.370956] pcmcia_socket pcmcia_socket0: cs: IO port probe
>> 0xc00-0xcf7: clean.
>> [ ? 15.371596] pcmcia_socket pcmcia_socket0: cs: IO port probe
>> 0xa00-0xaff: clean.
>> [ ? 15.776624] p54pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [ ? 15.776653] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
>> (level, low) -> IRQ 11
>> [ ? 15.776675] p54pci 0000:03:00.0: setting latency timer to 64
>> [ ? 15.776789] p54pci 0000:03:00.0: firmware: requesting isl3886pci
>> [ ? 15.916240] cfg80211: World regulatory domain updated:
>> [ ? 15.916252] ?(start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)
>> [ ? 15.916260] ?(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
>> 2000 mBm)
>> [ ? 15.916267] ?(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
>> 2000 mBm)
>> [ ? 15.916274] ?(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
>> 2000 mBm)
>> [ ? 15.916280] ?(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
>> 2000 mBm)
>> [ ? 15.916287] ?(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
>> 2000 mBm)
>> [ ? 16.048573] phy0: p54 detected a LM86 firmware
>> [ ? 16.048582] p54: rx_mtu reduced from 3240 to 2376
>> [ ? 16.048588] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
>> [ ? 16.048594] phy0: cryptographic accelerator WEP:YES, TKIP:YES,
>> CCMP:YES
>> [ ? 16.328427] Intel ICH 0000:00:1f.5: enabling device (0000 -> 0001)
>> [ ? 16.328448] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI
>> 11 (level, low) -> IRQ 11
>> [ ? 16.328477] Intel ICH 0000:00:1f.5: setting latency timer to 64
>> [ ? 16.917291] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
>> [ ? 17.140101] intel8x0_measure_ac97_clock: measured 52127 usecs (2506
>> samples)
>> [ ? 17.140111] intel8x0: clocking to 48000
>> [ ? 17.265086] phy0: Selected rate control algorithm 'minstrel'
>> [ ? 17.266862] Registered led device: p54-phy0::assoc
>> [ ? 17.266906] Registered led device: p54-phy0::tx
>> [ ? 17.266951] Registered led device: p54-phy0::rx
>> [ ? 17.266992] Registered led device: p54-phy0::radio
>> [ ? 17.267007] p54pci 0000:03:00.0: is registered as 'phy0'
>> [ ? 17.292918] udev: renamed network interface wlan0 to wlan1
>> [ ? 30.512797] EXT3 FS on sda5, internal journal
>> [ ? 31.876640] kjournald starting. ?Commit interval 5 seconds
>> [ ? 31.876989] EXT3 FS on sda7, internal journal
>> [ ? 31.877000] EXT3-fs: mounted filesystem with writeback data mode.
>> [ ? 32.829400] type=1505 audit(1256993753.257:9):
>> operation="profile_replace" pid=853 name=/sbin/dhclient3
>> [ ? 32.830401] type=1505 audit(1256993753.257:10):
>> operation="profile_replace" pid=853
>> name=/usr/lib/NetworkManager/nm-dhcp-client.action
>> [ ? 32.830965] type=1505 audit(1256993753.257:11):
>> operation="profile_replace" pid=853
>> name=/usr/lib/connman/scripts/dhclient-script
>> [ ? 32.837982] type=1505 audit(1256993753.265:12):
>> operation="profile_replace" pid=855
>> name=/usr/lib/cups/backend/cups-pdf
>> [ ? 32.839224] type=1505 audit(1256993753.265:13):
>> operation="profile_replace" pid=855 name=/usr/sbin/cupsd
>> [ ? 32.844175] type=1505 audit(1256993753.273:14):
>> operation="profile_replace" pid=856 name=/usr/sbin/mysqld-akonadi
>> [ ? 32.847992] type=1505 audit(1256993753.273:15):
>> operation="profile_replace" pid=857 name=/usr/sbin/tcpdump
>> [ ? 37.182116] RPC: Registered udp transport module.
>> [ ? 37.182124] RPC: Registered tcp transport module.
>> [ ? 37.410106] Installing knfsd (copyright (C) 1996
>> [email protected]).
>> [ ? 40.921453] svc: failed to register lockdv1 RPC service (errno 97).
>> [ ? 40.923471] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
>> recovery directory
>> [ ? 40.988229] NFSD: starting 90-second grace period
>> [ ? 41.914184] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ ? 41.938395] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ ? 42.970111] [drm] Initialized drm 1.1.0 20060810
>> [ ? 42.978943] pci 0000:01:00.0: power state changed by ACPI to D0
>> [ ? 42.978965] pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11
>> (level, low) -> IRQ 11
>> [ ? 42.979601] [drm] Initialized savage 2.4.1 20050313 for
>> 0000:01:00.0 on minor 0
>> [ ? 43.052134] phy0: frequency change failed
>> [ ? 43.052155] phy0: frequency change failed
>> [ ? 43.052163] phy0: frequency change failed
>> [ ? 43.052170] phy0: frequency change failed
>> [ ? 43.052177] phy0: frequency change failed
>> [ ? 43.116051] phy0: frequency change failed
>> [ ? 43.116070] phy0: frequency change failed
>> [ ? 43.116077] phy0: frequency change failed
>> [ ? 43.116085] phy0: frequency change failed
>> [ ? 43.116092] phy0: frequency change failed
>> [ ? 63.664124] phy0: frequency change failed
>> [ ? 63.664154] phy0: frequency change failed
>> [ ? 63.664162] phy0: frequency change failed
>> [ ? 63.664170] phy0: frequency change failed
>> [ ? 63.664177] phy0: frequency change failed
>> [ ? 63.724148] phy0: frequency change failed
>> [ ? 63.724174] phy0: frequency change failed
>> [ ? 63.724182] phy0: frequency change failed
>> [ ? 63.724189] phy0: frequency change failed
>> [ ? 63.724197] phy0: frequency change failed
>> [ ? 69.288818] ondemand governor failed, too long transition latency
>> of HW, fallback to performance governor
>> [ ? 93.668072] phy0: frequency change failed
>> [ ? 93.668093] phy0: frequency change failed
>> [ ? 93.668101] phy0: frequency change failed
>> [ ? 93.668108] phy0: frequency change failed
>> [ ? 93.668115] phy0: frequency change failed
>> [ ? 93.724065] phy0: frequency change failed
>> [ ? 93.724086] phy0: frequency change failed
>> [ ? 93.724094] phy0: frequency change failed
>> [ ? 93.724101] phy0: frequency change failed
>> [ ? 93.724108] phy0: frequency change failed
>> [ ?109.068537] ondemand governor failed, too long transition latency
>> of HW, fallback to performance governor
>> [ ?115.912103] phy0: frequency change failed
>> [ ?115.912120] phy0: frequency change failed
>> [ ?115.912128] phy0: frequency change failed
>> [ ?115.912135] phy0: frequency change failed
>> [ ?115.912142] phy0: frequency change failed
>> [ ?115.968099] phy0: frequency change failed
>> [ ?115.968112] phy0: frequency change failed
>> [ ?115.968120] phy0: frequency change failed
>> [ ?115.968127] phy0: frequency change failed
>> [ ?115.968134] phy0: frequency change failed
>> [ ?116.368824] phy0: frequency change failed
>> [ ?116.371618] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 1
>> [ ?116.568114] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 2
>> [ ?116.769380] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 3
>> [ ?116.968120] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx timed out
>> [ ?121.456176] phy0: frequency change failed
>> [ ?121.456193] phy0: frequency change failed
>> [ ?121.456201] phy0: frequency change failed
>> [ ?121.456208] phy0: frequency change failed
>> [ ?121.456215] phy0: frequency change failed
>> [ ?121.512156] phy0: frequency change failed
>> [ ?121.512169] phy0: frequency change failed
>> [ ?121.512177] phy0: frequency change failed
>> [ ?121.512184] phy0: frequency change failed
>> [ ?121.512191] phy0: frequency change failed
>> [ ?121.912200] phy0: frequency change failed
>> [ ?121.915107] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
>> [ ?122.112177] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
>> [ ?122.312156] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
>> [ ?122.512154] wlan1: authentication with AP 00:xx:xx:xx:xx:xx timed
>> out
>> [ ?127.000168] phy0: frequency change failed
>> [ ?127.000184] phy0: frequency change failed
>> [ ?127.000192] phy0: frequency change failed
>> [ ?127.000199] phy0: frequency change failed
>> [ ?127.000206] phy0: frequency change failed
>> [ ?127.056164] phy0: frequency change failed
>> [ ?127.056173] phy0: frequency change failed
>> [ ?127.056181] phy0: frequency change failed
>> [ ?127.056188] phy0: frequency change failed
>> [ ?127.056195] phy0: frequency change failed
>> [ ?127.460382] phy0: frequency change failed
>>
>> and it continues like that until I remove the module.
>>
>>
>> On Tue, Oct 27, 2009 at 1:37 PM, Luis R. Rodriguez <[email protected]> wrote:
>>> On Thu, Oct 8, 2009 at 9:28 AM, Larry Finger <[email protected]> wrote:
>>>> On 10/07/2009 04:00 PM, James Grossmann wrote:
>>>>>
>>>>> I have the gigafast WF728-AEX, which doesn't seem to work with the
>>>>> p54pci drivers, I was previously using it with my Thinkpad T23 under
>>>>> Gentoo (gentoo kernels 2.6.29 and 2.6.30), and could only use the
>>>>> 1.0.4.3 firmware, now, I am using it under Ubuntu 9.04
>>>>> (2.6.28-15-generic kernel) on the same computer, and find that I have
>>>>> to load the prism54 driver to make it work.
>>>>> I noticed that you were considering this to be depricated, I hope that
>>>>> you can help me to make p54pci work!
>>>>
>>>> As it works with 2.6.29 and 2.6.30 kernels, but not with 2.6.28, it seems
>>>> likely that you need a later version of the driver. Does Ubuntu have a
>>>> package for compat-wireless? If so, install it. If not, you will need to
>>>> install from source.
>>>
>>> James, please do test with a new driver and appropriate firmware and
>>> let us know if it worked or not.
>>>
>>> ?Luis
>>>
>>
>
Please keep the CC list here. This type of report is rare and we need
it archived. Please try using wireless-testing or compat-wireless:
http://wireless.kernel.org/en/users/Download
Luis
On Sat, Oct 31, 2009 at 6:15 AM, James Grossmann <[email protected]> wrote:
> Attempted under Ubuntu 9.10, using their kernel 2.6.31-14-generic.
> Unfortunately it still does not work, is it possible to load the
> fullmac firmware through p54pci? just a thought...
> Here's my relevant dmesg:
> [ 15.369250] pcmcia_socket pcmcia_socket0: cs: IO port probe
> 0x100-0x3af: clean.
> [ 15.370157] pcmcia_socket pcmcia_socket0: cs: IO port probe
> 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> [ 15.370585] pcmcia_socket pcmcia_socket0: cs: IO port probe
> 0x820-0x8ff: clean.
> [ 15.370956] pcmcia_socket pcmcia_socket0: cs: IO port probe
> 0xc00-0xcf7: clean.
> [ 15.371596] pcmcia_socket pcmcia_socket0: cs: IO port probe
> 0xa00-0xaff: clean.
> [ 15.776624] p54pci 0000:03:00.0: enabling device (0000 -> 0002)
> [ 15.776653] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
> (level, low) -> IRQ 11
> [ 15.776675] p54pci 0000:03:00.0: setting latency timer to 64
> [ 15.776789] p54pci 0000:03:00.0: firmware: requesting isl3886pci
> [ 15.916240] cfg80211: World regulatory domain updated:
> [ 15.916252] (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> [ 15.916260] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> [ 15.916267] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
> 2000 mBm)
> [ 15.916274] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
> 2000 mBm)
> [ 15.916280] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> [ 15.916287] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> [ 16.048573] phy0: p54 detected a LM86 firmware
> [ 16.048582] p54: rx_mtu reduced from 3240 to 2376
> [ 16.048588] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
> [ 16.048594] phy0: cryptographic accelerator WEP:YES, TKIP:YES,
> CCMP:YES
> [ 16.328427] Intel ICH 0000:00:1f.5: enabling device (0000 -> 0001)
> [ 16.328448] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI
> 11 (level, low) -> IRQ 11
> [ 16.328477] Intel ICH 0000:00:1f.5: setting latency timer to 64
> [ 16.917291] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
> [ 17.140101] intel8x0_measure_ac97_clock: measured 52127 usecs (2506
> samples)
> [ 17.140111] intel8x0: clocking to 48000
> [ 17.265086] phy0: Selected rate control algorithm 'minstrel'
> [ 17.266862] Registered led device: p54-phy0::assoc
> [ 17.266906] Registered led device: p54-phy0::tx
> [ 17.266951] Registered led device: p54-phy0::rx
> [ 17.266992] Registered led device: p54-phy0::radio
> [ 17.267007] p54pci 0000:03:00.0: is registered as 'phy0'
> [ 17.292918] udev: renamed network interface wlan0 to wlan1
> [ 30.512797] EXT3 FS on sda5, internal journal
> [ 31.876640] kjournald starting. Commit interval 5 seconds
> [ 31.876989] EXT3 FS on sda7, internal journal
> [ 31.877000] EXT3-fs: mounted filesystem with writeback data mode.
> [ 32.829400] type=1505 audit(1256993753.257:9):
> operation="profile_replace" pid=853 name=/sbin/dhclient3
> [ 32.830401] type=1505 audit(1256993753.257:10):
> operation="profile_replace" pid=853
> name=/usr/lib/NetworkManager/nm-dhcp-client.action
> [ 32.830965] type=1505 audit(1256993753.257:11):
> operation="profile_replace" pid=853
> name=/usr/lib/connman/scripts/dhclient-script
> [ 32.837982] type=1505 audit(1256993753.265:12):
> operation="profile_replace" pid=855
> name=/usr/lib/cups/backend/cups-pdf
> [ 32.839224] type=1505 audit(1256993753.265:13):
> operation="profile_replace" pid=855 name=/usr/sbin/cupsd
> [ 32.844175] type=1505 audit(1256993753.273:14):
> operation="profile_replace" pid=856 name=/usr/sbin/mysqld-akonadi
> [ 32.847992] type=1505 audit(1256993753.273:15):
> operation="profile_replace" pid=857 name=/usr/sbin/tcpdump
> [ 37.182116] RPC: Registered udp transport module.
> [ 37.182124] RPC: Registered tcp transport module.
> [ 37.410106] Installing knfsd (copyright (C) 1996
> [email protected]).
> [ 40.921453] svc: failed to register lockdv1 RPC service (errno 97).
> [ 40.923471] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
> recovery directory
> [ 40.988229] NFSD: starting 90-second grace period
> [ 41.914184] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 41.938395] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 42.970111] [drm] Initialized drm 1.1.0 20060810
> [ 42.978943] pci 0000:01:00.0: power state changed by ACPI to D0
> [ 42.978965] pci 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11
> (level, low) -> IRQ 11
> [ 42.979601] [drm] Initialized savage 2.4.1 20050313 for
> 0000:01:00.0 on minor 0
> [ 43.052134] phy0: frequency change failed
> [ 43.052155] phy0: frequency change failed
> [ 43.052163] phy0: frequency change failed
> [ 43.052170] phy0: frequency change failed
> [ 43.052177] phy0: frequency change failed
> [ 43.116051] phy0: frequency change failed
> [ 43.116070] phy0: frequency change failed
> [ 43.116077] phy0: frequency change failed
> [ 43.116085] phy0: frequency change failed
> [ 43.116092] phy0: frequency change failed
> [ 63.664124] phy0: frequency change failed
> [ 63.664154] phy0: frequency change failed
> [ 63.664162] phy0: frequency change failed
> [ 63.664170] phy0: frequency change failed
> [ 63.664177] phy0: frequency change failed
> [ 63.724148] phy0: frequency change failed
> [ 63.724174] phy0: frequency change failed
> [ 63.724182] phy0: frequency change failed
> [ 63.724189] phy0: frequency change failed
> [ 63.724197] phy0: frequency change failed
> [ 69.288818] ondemand governor failed, too long transition latency
> of HW, fallback to performance governor
> [ 93.668072] phy0: frequency change failed
> [ 93.668093] phy0: frequency change failed
> [ 93.668101] phy0: frequency change failed
> [ 93.668108] phy0: frequency change failed
> [ 93.668115] phy0: frequency change failed
> [ 93.724065] phy0: frequency change failed
> [ 93.724086] phy0: frequency change failed
> [ 93.724094] phy0: frequency change failed
> [ 93.724101] phy0: frequency change failed
> [ 93.724108] phy0: frequency change failed
> [ 109.068537] ondemand governor failed, too long transition latency
> of HW, fallback to performance governor
> [ 115.912103] phy0: frequency change failed
> [ 115.912120] phy0: frequency change failed
> [ 115.912128] phy0: frequency change failed
> [ 115.912135] phy0: frequency change failed
> [ 115.912142] phy0: frequency change failed
> [ 115.968099] phy0: frequency change failed
> [ 115.968112] phy0: frequency change failed
> [ 115.968120] phy0: frequency change failed
> [ 115.968127] phy0: frequency change failed
> [ 115.968134] phy0: frequency change failed
> [ 116.368824] phy0: frequency change failed
> [ 116.371618] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 1
> [ 116.568114] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 2
> [ 116.769380] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx try 3
> [ 116.968120] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx timed out
> [ 121.456176] phy0: frequency change failed
> [ 121.456193] phy0: frequency change failed
> [ 121.456201] phy0: frequency change failed
> [ 121.456208] phy0: frequency change failed
> [ 121.456215] phy0: frequency change failed
> [ 121.512156] phy0: frequency change failed
> [ 121.512169] phy0: frequency change failed
> [ 121.512177] phy0: frequency change failed
> [ 121.512184] phy0: frequency change failed
> [ 121.512191] phy0: frequency change failed
> [ 121.912200] phy0: frequency change failed
> [ 121.915107] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
> [ 122.112177] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
> [ 122.312156] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx
> [ 122.512154] wlan1: authentication with AP 00:xx:xx:xx:xx:xx timed
> out
> [ 127.000168] phy0: frequency change failed
> [ 127.000184] phy0: frequency change failed
> [ 127.000192] phy0: frequency change failed
> [ 127.000199] phy0: frequency change failed
> [ 127.000206] phy0: frequency change failed
> [ 127.056164] phy0: frequency change failed
> [ 127.056173] phy0: frequency change failed
> [ 127.056181] phy0: frequency change failed
> [ 127.056188] phy0: frequency change failed
> [ 127.056195] phy0: frequency change failed
> [ 127.460382] phy0: frequency change failed
>
> and it continues like that until I remove the module.
>
>
> On Tue, Oct 27, 2009 at 1:37 PM, Luis R. Rodriguez <[email protected]> wrote:
>> On Thu, Oct 8, 2009 at 9:28 AM, Larry Finger <[email protected]> wrote:
>>> On 10/07/2009 04:00 PM, James Grossmann wrote:
>>>>
>>>> I have the gigafast WF728-AEX, which doesn't seem to work with the
>>>> p54pci drivers, I was previously using it with my Thinkpad T23 under
>>>> Gentoo (gentoo kernels 2.6.29 and 2.6.30), and could only use the
>>>> 1.0.4.3 firmware, now, I am using it under Ubuntu 9.04
>>>> (2.6.28-15-generic kernel) on the same computer, and find that I have
>>>> to load the prism54 driver to make it work.
>>>> I noticed that you were considering this to be depricated, I hope that
>>>> you can help me to make p54pci work!
>>>
>>> As it works with 2.6.29 and 2.6.30 kernels, but not with 2.6.28, it seems
>>> likely that you need a later version of the driver. Does Ubuntu have a
>>> package for compat-wireless? If so, install it. If not, you will need to
>>> install from source.
>>
>> James, please do test with a new driver and appropriate firmware and
>> let us know if it worked or not.
>>
>> Luis
>>
>
sorry I forgot about that, I'm using a wrt54gs 1.0 with dd-wrt
(legacy, if I remember correctly -- DD-WRT v24 (05/20/08) vpn - build
9517M Eko ) firmware. Uptime of 4 days, it has had its problems, but
not so much of recent, the wireless was crashing fairly often a while
back, but I last rebooted it before that 2 months ago.
I've been using it without any wep/wpa of recent, I ran into some
access devices that were fighting with it, and in the small town I
live in, I doubt anyone else knows enough about computers to hack
wifi...I hope...haven't seen anything in the logs.
Hope that's helpful
James
On Fri, Nov 6, 2009 at 3:45 PM, Christian Lamparter
<[email protected]> wrote:
> On Friday 06 November 2009 21:52:42 James Grossmann wrote:
>> my caps lock & scroll lock leds are not blinking, and yet the computer
>> is frozen. ?(I'm not the best at terminology, I guess that might not
>> be defined as a hard lock.) ?I get no odd messages in my syslog. ?I am
>> using Ubuntu right now, so I'm guessing that they have all the
>> prettyness going that they can, covering the important messages, but
>> as it's not an actual oops, I'm not certain that's hurting us.
>
> Ubuntu's kernel team provide some helpful texts about getting more
> informations out of the crashes: (a bit of a hassle)
> https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe
> https://help.ubuntu.com/community/DebuggingSystemCrash
>
> but maybe you can save you some time:
> 1. if possible update your compat-wireless
> ? a crash bug (affects compat-wireless, wireless-testing and even -rcX series)
> ? has been fixed. This bug is known to strike on configurations with a
> ? high number of auth/assoc/deauth - cycles.
>
> ? ? ? ?http://thread.gmane.org/gmane.linux.kernel/908831/focus=41872
>
> 2. Quintin Pitts had/has problems with the reliability of his
> ? p54pci <-> pci-bus and wrote a patch:
> ? ? ? http://patchwork.kernel.org/patch/53004/raw/
>
> ? ?unfortunately for him, his pci-bridge is known to be faulty,
> ? ?but maybe he found some real bugs after all.
>
> 3. replace firmware:
> ? ? ? ?http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.13.1.0.arm
> ? ? ? ?http://daemonizer.de/prism54/prism54-fw/fw-softmac/lmac_2.7.0.0.arm
>
>> I am using network-manager, so it does reconnect, however, I find that
>> to be less than optimal.
> yeah, normally you can see such phenomena when you have a funky AP and
> enable wifi powersaving... but this is unlikely, as the ps is disabled
> (can be enabled with iwconfig wlanX power on) for this reason.
>
> can you please tell me more about your AP?
> e.g: Product Name, Vendor, firmware revision,
> is it 802.11 a/b/g/n, is WEP/WPA(2) enabled, or is it just an open ap?
>
attached is the dmesg:
On Sat, Oct 31, 2009 at 3:24 PM, Christian Lamparter
<[email protected]> wrote:
> On Saturday 31 October 2009 15:11:37 James Grossmann wrote:
>> [ 4200.794299] cfg80211: Calling CRDA to update world regulatory
>> domain
>> [ 4200.857330] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
>> (level, low) -> IRQ 11
>> [ 4200.857408] p54pci 0000:03:00.0: firmware: requesting isl3886pci
>> [ 4201.432596] phy0: p54 detected a LM86 firmware
>> [ 4201.432604] p54: rx_mtu reduced from 3240 to 2376
>> [ 4201.432610] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
>> [ 4201.432616] phy0: cryptographic accelerator WEP:YES, TKIP:YES,
>> CCMP:YES
>
>> [ 4202.293254] phy0: EEPROM is damaged... you may not be able to use
>> all channels with this device.
> ^^^ = that's the culprit.
>
> do you think, you can get this EEPROM dump?
> Just move the attach _patch_ into your compat-wireless' main directory.
> Afterward, you have to execute:
> patch -p1 < p54-dump-eeprom-to-dmesg.diff
>
> and rebuild & reload the driver and retrieve the data
> from dmesg.
>
>> [ 4202.293286] phy0: [iqauto calibration data] is/are missing for
>> channel:2 [2417 MHz].
>> [ 4202.293293] phy0: [iqauto calibration data] is/are missing for
>> channel:3 [2422 MHz].
>> [ 4202.293300] phy0: [iqauto calibration data] is/are missing for
>> channel:4 [2427 MHz].
>> [ 4202.293306] phy0: [iqauto calibration data] is/are missing for
>> channel:5 [2432 MHz].
>> [ 4202.293313] phy0: [iqauto calibration data] is/are missing for
>> channel:6 [2437 MHz].
>> [ 4202.293320] phy0: [iqauto calibration data] is/are missing for
>> channel:8 [2447 MHz].
>> [ 4202.293326] phy0: [iqauto calibration data] is/are missing for
>> channel:9 [2452 MHz].
>> [ 4202.293333] phy0: [iqauto calibration data] is/are missing for
>> channel:10 [2457 MHz].
>> [ 4202.293340] phy0: [iqauto calibration data] is/are missing for
>> channel:11 [2462 MHz].
>> [ 4202.293346] phy0: [iqauto calibration data] is/are missing for
>> channel:12 [2467 MHz].
>
>> [ 4202.293356] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
>> [ 4202.293787] phy0: Selected rate control algorithm 'minstrel'
>> [ 4202.295616] Registered led device: p54-phy0::assoc
>> [ 4202.295657] Registered led device: p54-phy0::tx
>> [ 4202.295703] Registered led device: p54-phy0::rx
>> [ 4202.295744] Registered led device: p54-phy0::radio
>> [ 4202.295758] p54pci 0000:03:00.0: is registered as 'phy0'
>> [ 4202.378618] udev: renamed network interface wlan0 to wlan1
>> [ 4202.509483] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 4202.724125] phy0: frequency change to channel 2 failed.
>> [ 4202.724138] phy0: frequency change to channel 3 failed.
>> [ 4202.724145] phy0: frequency change to channel 4 failed.
>> [ 4202.724151] phy0: frequency change to channel 5 failed.
>> [ 4202.724157] phy0: frequency change to channel 6 failed.
>> [ 4202.780179] phy0: frequency change to channel 8 failed.
>> [ 4202.780193] phy0: frequency change to channel 9 failed.
>> [ 4202.780199] phy0: frequency change to channel 10 failed.
>> [ 4202.780206] phy0: frequency change to channel 11 failed.
>> [ 4202.780212] phy0: frequency change to channel 12 failed.
>> [ 4208.212168] phy0: frequency change to channel 2 failed.
>> [ 4208.212180] phy0: frequency change to channel 3 failed.
>> [ 4208.212187] phy0: frequency change to channel 4 failed.
>> [ 4208.212193] phy0: frequency change to channel 5 failed.
>> [ 4208.212199] phy0: frequency change to channel 6 failed.
>> [ 4208.276097] phy0: frequency change to channel 8 failed.
>> [ 4208.276112] phy0: frequency change to channel 9 failed.
>> [ 4208.276119] phy0: frequency change to channel 10 failed.
>> [ 4208.276125] phy0: frequency change to channel 11 failed.
>> [ 4208.276132] phy0: frequency change to channel 12 failed.
>> [ 4208.524788] phy0: frequency change to channel 6 failed.
>> [ 4208.524949] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
>> choice (reason=3)
>> [ 4208.525084] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
>> [ 4208.724191] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 2)
> [...]
>
> Regards,
> ? ? ? ?Chr
>
On Friday 06 November 2009 21:52:42 James Grossmann wrote:
> my caps lock & scroll lock leds are not blinking, and yet the computer
> is frozen. (I'm not the best at terminology, I guess that might not
> be defined as a hard lock.) I get no odd messages in my syslog. I am
> using Ubuntu right now, so I'm guessing that they have all the
> prettyness going that they can, covering the important messages, but
> as it's not an actual oops, I'm not certain that's hurting us.
just a update:
I can confirm the freeze with ubuntu 9.10 (2.6.31-14 & 2.6.31-15-generic)
+ compat-wireless + p54pci (either as backport module or compiled from git).
The original modules (shipped with 2.6.31-14/15) are fine though..?!
Regards,
Chr
On Friday 06 November 2009 19:45:53 James Grossmann wrote:
> Here's the iwconfig:
> wlan1 IEEE 802.11bg ESSID:"newton"
> Mode:Managed Frequency:2.462 GHz Access Point: 00:xx:xx:xx:xx:xx
> Bit Rate=48 Mb/s Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Power Management:off
> Link Quality=50/70 Signal level=-60 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> I was unable to run the iperf as the client on the laptop
> (it hard locked the computer twice),
huu, that's really bad. especially, since a new release is around the corner.
Do you think you can catch the oops/bug report?
(switch to virtual terminal Alt-Ctrl-F1 and start iperf -c there)
> I ran it as server and received the
> following at a fair distance from the router (a couple of rooms, same
> as the iwconfig above)
> Client connecting to 192.168.1.3, TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.1.5 port 47866 connected with 192.168.1.3 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.4 sec 14.6 MBytes 11.7 Mbits/sec
>
> Same test across the room from the router:
> iperf -c 192.168.1.3
> ------------------------------------------------------------
> Client connecting to 192.168.1.3, TCP port 5001
> TCP window size: 16.0 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.1.5 port 47867 connected with 192.168.1.3 port 5001
> [ ID] Interval Transfer Bandwidth
> [ 3] 0.0-10.0 sec 21.4 MBytes 17.9 Mbits/sec
>
> wlan1 IEEE 802.11bg ESSID:"newton"
> Mode:Managed Frequency:2.462 GHz Access Point: 00:xx:xx:xx:xx:xx
> Bit Rate=54 Mb/s Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Power Management:off
> Link Quality=70/70 Signal level=-37 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Here's a little bit more I've been getting in my dmesg:
> [ 91.453279] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local choice (reason=3)
> [ 91.453421] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
> [ 91.457825] wlan1: direct probe responded
> [ 91.457839] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
> [ 91.462748] wlan1: authenticated
> [ 91.462808] wlan1: associate with AP 00:xx:xx:xx:xx:xx (try 1)
> [ 91.465574] wlan1: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x401
> status=0 aid=2)
> [ 91.465584] wlan1: associated
> [ 91.467208] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [ 101.500094] wlan1: no IPv6 routers present
> [ 101.893294] ondemand governor failed, too long transition latency
> of HW, fallback to performance governor
> [ 773.648180] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
> [ 773.649900] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
> [ 773.654069] wlan1: direct probe responded
> [ 773.654082] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
> [ 773.655939] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
Reason 7 => Class 3 (usually data frames) frame from non-assoc station.
Either, your STA timed out (due to lack of traffic?) or the AP lost
the connection state for some strange reason (reset?).
Regards,
Chr
Christian Lamparter wrote:
> On Thursday 12 November 2009 19:56:30 Tim Gardner wrote:
>> Christian Lamparter wrote:
>>> On Friday 06 November 2009 21:52:42 James Grossmann wrote:
>>>> my caps lock & scroll lock leds are not blinking, and yet the computer
>>>> is frozen. (I'm not the best at terminology, I guess that might not
>>>> be defined as a hard lock.) I get no odd messages in my syslog. I am
>>>> using Ubuntu right now, so I'm guessing that they have all the
>>>> prettyness going that they can, covering the important messages, but
>>>> as it's not an actual oops, I'm not certain that's hurting us.
>>> just a update:
>>>
>>> I can confirm the freeze with ubuntu 9.10 (2.6.31-14 & 2.6.31-15-generic)
>>> + compat-wireless + p54pci (either as backport module or compiled from git).
>>> The original modules (shipped with 2.6.31-14/15) are fine though..?!
>> The Ubuntu Karmic linux-backports-modules package is based on
>> compat-wireless-2.6.32-rc4. I'm wondering if its something specific to
>> the p54pci driver? I'm using iwlagn (4965) from that package with no
>> problems (so far).
>
> I put a ath5k card into the same machine and tried with the same
> compat-wireless modules. Surprise, surprise: no problems...
>
> The affected device works fine with the current wireless-testing(pulled today)
> and a vanilla 2.6.31.6 + compat-wireless (from today's git).
>
> I've no idea what voodoo is going on here, maybe there is
> something wrong in compat-wireless pci glue code (if there's any?!)
>
>> Its not clear what version of stable compat-wireless you've tried.
>> Does compat-wireless-2.6.32-rc6 exhibit the same problem?
> "compiled from git", which should be compat-wireless-2009-11-12.tar.bz2
> and therefore -rc6.
>
Just to be clear, the current wireless-testing is not at all the same as
2.6.32-rc6. Its my understanding that wireless-testing is John's
crack-of-the-day merge window test repository.
Anyway, I'm updating the Ubuntu LBM package to use
compat-wireless-2.6.32-rc6 which should be out by tomorrow. This
combination should closely resemble vanilla 2.6.31.6 + compat-wireless.
rtg
--
Tim Gardner [email protected]
On Thursday 12 November 2009 19:56:30 Tim Gardner wrote:
> Christian Lamparter wrote:
> > On Friday 06 November 2009 21:52:42 James Grossmann wrote:
> >> my caps lock & scroll lock leds are not blinking, and yet the computer
> >> is frozen. (I'm not the best at terminology, I guess that might not
> >> be defined as a hard lock.) I get no odd messages in my syslog. I am
> >> using Ubuntu right now, so I'm guessing that they have all the
> >> prettyness going that they can, covering the important messages, but
> >> as it's not an actual oops, I'm not certain that's hurting us.
> > just a update:
> >
> > I can confirm the freeze with ubuntu 9.10 (2.6.31-14 & 2.6.31-15-generic)
> > + compat-wireless + p54pci (either as backport module or compiled from git).
> > The original modules (shipped with 2.6.31-14/15) are fine though..?!
>
> The Ubuntu Karmic linux-backports-modules package is based on
> compat-wireless-2.6.32-rc4. I'm wondering if its something specific to
> the p54pci driver? I'm using iwlagn (4965) from that package with no
> problems (so far).
I put a ath5k card into the same machine and tried with the same
compat-wireless modules. Surprise, surprise: no problems...
The affected device works fine with the current wireless-testing(pulled today)
and a vanilla 2.6.31.6 + compat-wireless (from today's git).
I've no idea what voodoo is going on here, maybe there is
something wrong in compat-wireless pci glue code (if there's any?!)
> Its not clear what version of stable compat-wireless you've tried.
> Does compat-wireless-2.6.32-rc6 exhibit the same problem?
"compiled from git", which should be compat-wireless-2009-11-12.tar.bz2
and therefore -rc6.
Regards,
Chr
On Friday 06 November 2009 21:52:42 James Grossmann wrote:
> my caps lock & scroll lock leds are not blinking, and yet the computer
> is frozen. (I'm not the best at terminology, I guess that might not
> be defined as a hard lock.) I get no odd messages in my syslog. I am
> using Ubuntu right now, so I'm guessing that they have all the
> prettyness going that they can, covering the important messages, but
> as it's not an actual oops, I'm not certain that's hurting us.
Ubuntu's kernel team provide some helpful texts about getting more
informations out of the crashes: (a bit of a hassle)
https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe
https://help.ubuntu.com/community/DebuggingSystemCrash
but maybe you can save you some time:
1. if possible update your compat-wireless
a crash bug (affects compat-wireless, wireless-testing and even -rcX series)
has been fixed. This bug is known to strike on configurations with a
high number of auth/assoc/deauth - cycles.
http://thread.gmane.org/gmane.linux.kernel/908831/focus=41872
2. Quintin Pitts had/has problems with the reliability of his
p54pci <-> pci-bus and wrote a patch:
http://patchwork.kernel.org/patch/53004/raw/
unfortunately for him, his pci-bridge is known to be faulty,
but maybe he found some real bugs after all.
3. replace firmware:
http://daemonizer.de/prism54/prism54-fw/fw-softmac/2.13.1.0.arm
http://daemonizer.de/prism54/prism54-fw/fw-softmac/lmac_2.7.0.0.arm
> I am using network-manager, so it does reconnect, however, I find that
> to be less than optimal.
yeah, normally you can see such phenomena when you have a funky AP and
enable wifi powersaving... but this is unlikely, as the ps is disabled
(can be enabled with iwconfig wlanX power on) for this reason.
can you please tell me more about your AP?
e.g: Product Name, Vendor, firmware revision,
is it 802.11 a/b/g/n, is WEP/WPA(2) enabled, or is it just an open ap?
On Friday 06 November 2009 18:00:54 James Grossmann wrote:
> It connects up with the patch!
> I'll attach a dmesg for any info you might be able to glean from that.
> THANKS!
it's a start, but there are some serious implications.
but first: what is your signal (dBm) reading (iwconfig / iw dev wlanX info)?
I'm asking this because your device is only fine-tunable for
channel 1, 7, 13 & 14 with the current data points.
some performance figures would be nice as well.
e.g.: iperf (tcp) should be > 18Mbit/s,
if you are close & free line of sight
second: what should we do about these devices?
Surely, the best thing would be to simply reprogram the eeprom,
but this (being complicated work) requires soldering skills/tools,
a steady hand and enough boredom. Therefor this is likely the least
ideal option to put into the WIKI @ wireless.kernel.org .
Any suitable ideas?
Regards,
Chr
---
> [ 5593.622225] cfg80211: Calling CRDA to update world regulatory
> domain
> [ 5593.756965] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
> (level, low) -> IRQ 11
> [ 5593.757087] p54pci 0000:03:00.0: firmware: requesting isl3886pci
> [ 5593.799682] cfg80211: World regulatory domain updated:
> [ 5593.799693] (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> [ 5593.799701] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> [ 5593.799708] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
> 2000 mBm)
> [ 5593.799714] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
> 2000 mBm)
> [ 5593.799721] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 5593.799728] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 5593.826106] phy0: p54 detected a LM86 firmware
> [ 5593.826115] p54: rx_mtu reduced from 3240 to 2376
> [ 5593.826121] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
> [ 5593.826127] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
> [ 5593.943095] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
>
> [ 5593.943532] phy0: Selected rate control algorithm 'minstrel'
> [ 5593.945386] Registered led device: p54-phy0::assoc
> [ 5593.945426] Registered led device: p54-phy0::tx
> [ 5593.945466] Registered led device: p54-phy0::rx
> [ 5593.945507] Registered led device: p54-phy0::radio
> [ 5593.945521] p54pci 0000:03:00.0: is registered as 'phy0'
> [ 5593.973148] udev: renamed network interface wlan0 to wlan1
> [ 5594.105670] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 5601.380939] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
> choice (reason=3)
> [ 5601.381046] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
> [ 5601.385723] wlan1: direct probe responded
> [ 5601.385738] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
> [ 5601.387961] wlan1: authenticated
> [ 5601.388049] wlan1: associate with AP 00:xx:xx:xx:xx:xx (try 1)
> [ 5601.390237] wlan1: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x401
> status=0 aid=2)
> [ 5601.390246] wlan1: associated
> [ 5601.391891] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [ 5612.024163] wlan1: no IPv6 routers present
>
Christian Lamparter wrote:
> On Friday 06 November 2009 21:52:42 James Grossmann wrote:
>> my caps lock & scroll lock leds are not blinking, and yet the computer
>> is frozen. (I'm not the best at terminology, I guess that might not
>> be defined as a hard lock.) I get no odd messages in my syslog. I am
>> using Ubuntu right now, so I'm guessing that they have all the
>> prettyness going that they can, covering the important messages, but
>> as it's not an actual oops, I'm not certain that's hurting us.
> just a update:
>
> I can confirm the freeze with ubuntu 9.10 (2.6.31-14 & 2.6.31-15-generic)
> + compat-wireless + p54pci (either as backport module or compiled from git).
> The original modules (shipped with 2.6.31-14/15) are fine though..?!
>
> Regards,
> Chr
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
The Ubuntu Karmic linux-backports-modules package is based on
compat-wireless-2.6.32-rc4. I'm wondering if its something specific to
the p54pci driver? I'm using iwlagn (4965) from that package with no
problems (so far).
Its not clear what version of stable compat-wireless you've tried. Does
compat-wireless-2.6.32-rc6 exhibit the same problem?
rtg
--
Tim Gardner [email protected]
On Friday 06 November 2009 20:37:00 James Grossmann wrote:
> Doing it from the console doesn't seem to give a kernel oops... it
> just locks up the computer such that I can't even change the caps lock
> status. It starts the connection, and then the activity light on the
> card goes on and the computer is locked up.
well, there are other ways to capture the oops, but I don't think
your laptop has a serial console or a real reset button?!
does your caps lock & scroll lock LED blink? (they should)
does the kernel reboot itself (after ~10 seconds), if you add
panic=10
to the kernel-parameters in grub configuration?
do you have some sort of bootsplash or frame buffer console?
(e.g. KMS/vesa/etc...) because these advanced features can make it
really hard to get the message to the screen before it goes black.
is there nothing in /var/log/syslog after a crash?
> With regard to the losing connection/timing out, I'm seeing that a
> fair amount, when I have data transferring (watching an active ssh
> connection, or streaming audio), and especially when I'm not doing
> anything...
well, there could be several different things, I hope you're using
services like Network-manager, wpa_supplicant to manage your connection.
Because they will automatically reconnect as soon as the link dies.
what could be interesting: iw dev wlanX scan / iwlist wlanX scan
dump from your AP... especially the TSF/tsf value,
(it's a hexadecimal value which acts like a uptime for the AP)
Regards,
Chr
Here's the iwconfig:
wlan1 IEEE 802.11bg ESSID:"newton"
Mode:Managed Frequency:2.462 GHz Access Point: 00:xx:xx:xx:xx:xx
Bit Rate=48 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=50/70 Signal level=-60 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I was unable to run the iperf as the client on the laptop (it hard
locked the computer twice), I ran it as server and received the
following at a fair distance from the router (a couple of rooms, same
as the iwconfig above)
Client connecting to 192.168.1.3, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.5 port 47866 connected with 192.168.1.3 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.4 sec 14.6 MBytes 11.7 Mbits/sec
Same test across the room from the router:
iperf -c 192.168.1.3
------------------------------------------------------------
Client connecting to 192.168.1.3, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.5 port 47867 connected with 192.168.1.3 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 21.4 MBytes 17.9 Mbits/sec
wlan1 IEEE 802.11bg ESSID:"newton"
Mode:Managed Frequency:2.462 GHz Access Point: 00:xx:xx:xx:xx:xx
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=-37 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Here's a little bit more I've been getting in my dmesg:
[ 91.453279] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
choice (reason=3)
[ 91.453421] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
[ 91.457825] wlan1: direct probe responded
[ 91.457839] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
[ 91.462748] wlan1: authenticated
[ 91.462808] wlan1: associate with AP 00:xx:xx:xx:xx:xx (try 1)
[ 91.465574] wlan1: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x401
status=0 aid=2)
[ 91.465584] wlan1: associated
[ 91.467208] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 101.500094] wlan1: no IPv6 routers present
[ 101.893294] ondemand governor failed, too long transition latency
of HW, fallback to performance governor
[ 773.648180] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
[ 773.649900] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
[ 773.654069] wlan1: direct probe responded
[ 773.654082] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
[ 773.655939] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
On Fri, Nov 6, 2009 at 11:48 AM, Christian Lamparter
<[email protected]> wrote:
> On Friday 06 November 2009 18:00:54 James Grossmann wrote:
>> It connects up with the patch!
>> I'll attach a dmesg for any info you might be able to glean from that.
>> ?THANKS!
>
> it's a start, but there are some serious implications.
>
> but first: what is your signal (dBm) reading (iwconfig / iw dev wlanX info)?
>
> I'm asking this because your device is only fine-tunable for
> channel 1, 7, 13 & 14 with the current data points.
>
> some performance figures would be nice as well.
> e.g.: iperf (tcp) should be > 18Mbit/s,
> ? ? ?if you are close & free line of sight
>
> second: what should we do about these devices?
>
> Surely, the best thing would be to simply reprogram the eeprom,
> but this (being complicated work) requires soldering skills/tools,
> a steady hand and enough boredom. Therefor this is likely the least
> ideal option to put into the WIKI @ wireless.kernel.org .
> Any suitable ideas?
>
> Regards,
> ? ? ? ?Chr
>
> ---
>> [ 5593.622225] cfg80211: Calling CRDA to update world regulatory
>> domain
>> [ 5593.756965] p54pci 0000:03:00.0: PCI INT A -> Link[LNKA] -> GSI 11
>> (level, low) -> IRQ 11
>> [ 5593.757087] p54pci 0000:03:00.0: firmware: requesting isl3886pci
>> [ 5593.799682] cfg80211: World regulatory domain updated:
>> [ 5593.799693] ?(start_freq - end_freq @ bandwidth),
>> (max_antenna_gain, max_eirp)
>> [ 5593.799701] ?(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
>> 2000 mBm)
>> [ 5593.799708] ?(2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi,
>> 2000 mBm)
>> [ 5593.799714] ?(2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
>> 2000 mBm)
>> [ 5593.799721] ?(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> [ 5593.799728] ?(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>> [ 5593.826106] phy0: p54 detected a LM86 firmware
>> [ 5593.826115] p54: rx_mtu reduced from 3240 to 2376
>> [ 5593.826121] phy0: FW rev 2.13.12.0 - Softmac protocol 5.9
>> [ 5593.826127] phy0: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES
>> [ 5593.943095] phy0: hwaddr 00:xx:xx:xx:xx:xx, MAC:isl3880 RF:Frisbee
>>
>> [ 5593.943532] phy0: Selected rate control algorithm 'minstrel'
>> [ 5593.945386] Registered led device: p54-phy0::assoc
>> [ 5593.945426] Registered led device: p54-phy0::tx
>> [ 5593.945466] Registered led device: p54-phy0::rx
>> [ 5593.945507] Registered led device: p54-phy0::radio
>> [ 5593.945521] p54pci 0000:03:00.0: is registered as 'phy0'
>> [ 5593.973148] udev: renamed network interface wlan0 to wlan1
>> [ 5594.105670] ADDRCONF(NETDEV_UP): wlan1: link is not ready
>> [ 5601.380939] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local
>> choice (reason=3)
>> [ 5601.381046] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
>> [ 5601.385723] wlan1: direct probe responded
>> [ 5601.385738] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
>> [ 5601.387961] wlan1: authenticated
>> [ 5601.388049] wlan1: associate with AP 00:xx:xx:xx:xx:xx (try 1)
>> [ 5601.390237] wlan1: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x401
>> status=0 aid=2)
>> [ 5601.390246] wlan1: associated
>> [ 5601.391891] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>> [ 5612.024163] wlan1: no IPv6 routers present
>>
>
On Thu, Nov 12, 2009 at 11:37 AM, Christian Lamparter
<[email protected]> wrote:
> On Thursday 12 November 2009 19:56:30 Tim Gardner wrote:
>> Christian Lamparter wrote:
>> > On Friday 06 November 2009 21:52:42 James Grossmann wrote:
>> >> my caps lock & scroll lock leds are not blinking, and yet the computer
>> >> is frozen. (I'm not the best at terminology, I guess that might not
>> >> be defined as a hard lock.) I get no odd messages in my syslog. I am
>> >> using Ubuntu right now, so I'm guessing that they have all the
>> >> prettyness going that they can, covering the important messages, but
>> >> as it's not an actual oops, I'm not certain that's hurting us.
>> > just a update:
>> >
>> > I can confirm the freeze with ubuntu 9.10 (2.6.31-14 & 2.6.31-15-generic)
>> > + compat-wireless + p54pci (either as backport module or compiled from git).
>> > The original modules (shipped with 2.6.31-14/15) are fine though..?!
>>
>> The Ubuntu Karmic linux-backports-modules package is based on
>> compat-wireless-2.6.32-rc4. I'm wondering if its something specific to
>> the p54pci driver? I'm using iwlagn (4965) from that package with no
>> problems (so far).
>
> I put a ath5k card into the same machine and tried with the same
> compat-wireless modules. Surprise, surprise: no problems...
>
> The affected device works fine with the current wireless-testing(pulled today)
> and a vanilla 2.6.31.6 + compat-wireless (from today's git).
>
> I've no idea what voodoo is going on here, maybe there is
> something wrong in compat-wireless pci glue code (if there's any?!)
Should be easy to debug, the compat 2.6.31 code is in
compat/compat-2.6.32.[ch] and since there is no 2.6.33 yet that is
all. That and of course any ifdef which applies on the
compat/patches/.
>> Its not clear what version of stable compat-wireless you've tried.
>> Does compat-wireless-2.6.32-rc6 exhibit the same problem?
> "compiled from git", which should be compat-wireless-2009-11-12.tar.bz2
> and therefore -rc6.
Well no, I believe what Tim means is the stable compat-wireless
releases which are not based on master git on compat-wireless. These
are based on a branch for the specific stable kernel. The stable
compat-wireless releases use hpa's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
and I checkout specific 2.6.3x.y branches. So for 2.6.32 I just use
master though which is based on Linus' tree and the latest *stable*
2.6.32-rcx.
Luis
Doing it from the console doesn't seem to give a kernel oops... it
just locks up the computer such that I can't even change the caps lock
status. It starts the connection, and then the activity light on the
card goes on and the computer is locked up.
With regard to the losing connection/timing out, I'm seeing that a
fair amount, when I have data transferring (watching an active ssh
connection, or streaming audio), and especially when I'm not doing
anything...
Thanks,
James
On Fri, Nov 6, 2009 at 1:14 PM, Christian Lamparter
<[email protected]> wrote:
> On Friday 06 November 2009 19:45:53 James Grossmann wrote:
>> Here's the iwconfig:
>> wlan1 ? ? IEEE 802.11bg ?ESSID:"newton"
>> ? ? ? ? ? Mode:Managed ?Frequency:2.462 GHz ?Access Point: 00:xx:xx:xx:xx:xx
>> ? ? ? ? ? Bit Rate=48 Mb/s ? Tx-Power=20 dBm
>> ? ? ? ? ? Retry ?long limit:7 ? RTS thr:off ? Fragment thr:off
>> ? ? ? ? ? Power Management:off
>> ? ? ? ? ? Link Quality=50/70 ?Signal level=-60 dBm
>> ? ? ? ? ? Rx invalid nwid:0 ?Rx invalid crypt:0 ?Rx invalid frag:0
>> ? ? ? ? ? Tx excessive retries:0 ?Invalid misc:0 ? Missed beacon:0
>>
>> I was unable to run the iperf as the client on the laptop
>> (it hard locked the computer twice),
> huu, that's really bad. especially, since a new release is around the corner.
>
> Do you think you can catch the oops/bug report?
> (switch to virtual terminal Alt-Ctrl-F1 and start iperf -c there)
>
>> I ran it as server and received the
>> following at a fair distance from the router (a couple of rooms, same
>> as the iwconfig above)
>> Client connecting to 192.168.1.3, TCP port 5001
>> TCP window size: 16.0 KByte (default)
>> ------------------------------------------------------------
>> [ ?3] local 192.168.1.5 port 47866 connected with 192.168.1.3 port 5001
>> [ ID] Interval ? ? ? Transfer ? ? Bandwidth
>> [ ?3] ?0.0-10.4 sec ?14.6 MBytes ?11.7 Mbits/sec
>>
>> Same test across the room from the router:
>> iperf -c 192.168.1.3
>> ------------------------------------------------------------
>> Client connecting to 192.168.1.3, TCP port 5001
>> TCP window size: 16.0 KByte (default)
>> ------------------------------------------------------------
>> [ ?3] local 192.168.1.5 port 47867 connected with 192.168.1.3 port 5001
>> [ ID] Interval ? ? ? Transfer ? ? Bandwidth
>> [ ?3] ?0.0-10.0 sec ?21.4 MBytes ?17.9 Mbits/sec
>>
>> wlan1 ? ? IEEE 802.11bg ?ESSID:"newton"
>> ? ? ? ? ? Mode:Managed ?Frequency:2.462 GHz ?Access Point: 00:xx:xx:xx:xx:xx
>> ? ? ? ? ? Bit Rate=54 Mb/s ? Tx-Power=20 dBm
>> ? ? ? ? ? Retry ?long limit:7 ? RTS thr:off ? Fragment thr:off
>> ? ? ? ? ? Power Management:off
>> ? ? ? ? ? Link Quality=70/70 ?Signal level=-37 dBm
>> ? ? ? ? ? Rx invalid nwid:0 ?Rx invalid crypt:0 ?Rx invalid frag:0
>> ? ? ? ? ? Tx excessive retries:0 ?Invalid misc:0 ? Missed beacon:0
>>
>> Here's a little bit more I've been getting in my dmesg:
>> [ ? 91.453279] wlan1: deauthenticating from 00:xx:xx:xx:xx:xx by local choice (reason=3)
>> [ ? 91.453421] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
>> [ ? 91.457825] wlan1: direct probe responded
>> [ ? 91.457839] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
>> [ ? 91.462748] wlan1: authenticated
>> [ ? 91.462808] wlan1: associate with AP 00:xx:xx:xx:xx:xx (try 1)
>> [ ? 91.465574] wlan1: RX AssocResp from 00:xx:xx:xx:xx:xx (capab=0x401
>> status=0 aid=2)
>> [ ? 91.465584] wlan1: associated
>> [ ? 91.467208] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
>> [ ?101.500094] wlan1: no IPv6 routers present
>> [ ?101.893294] ondemand governor failed, too long transition latency
>> of HW, fallback to performance governor
>
>> [ ?773.648180] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
>> [ ?773.649900] wlan1: direct probe to AP 00:xx:xx:xx:xx:xx (try 1)
>> [ ?773.654069] wlan1: direct probe responded
>> [ ?773.654082] wlan1: authenticate with AP 00:xx:xx:xx:xx:xx (try 1)
>> [ ?773.655939] wlan1: deauthenticated from 00:xx:xx:xx:xx:xx (Reason: 7)
>
> Reason 7 => Class 3 (usually data frames) frame from non-assoc station.
> Either, your STA timed out (due to lack of traffic?) or the AP lost
> the connection state for some strange reason (reset?).
>
> Regards,
> ? ? ? ?Chr
>
my caps lock & scroll lock leds are not blinking, and yet the computer
is frozen. (I'm not the best at terminology, I guess that might not
be defined as a hard lock.) I get no odd messages in my syslog. I am
using Ubuntu right now, so I'm guessing that they have all the
prettyness going that they can, covering the important messages, but
as it's not an actual oops, I'm not certain that's hurting us.
I am using network-manager, so it does reconnect, however, I find that
to be less than optimal.
Thanks,
James
On Fri, Nov 6, 2009 at 2:33 PM, Christian Lamparter
<[email protected]> wrote:
> On Friday 06 November 2009 20:37:00 James Grossmann wrote:
>> Doing it from the console doesn't seem to give a kernel oops... it
>> just locks up the computer such that I can't even change the caps lock
>> status. It starts the connection, and then the activity light on the
>> card goes on and the computer is locked up.
> well, there are other ways to capture the oops, but I don't think
> your laptop has a serial console or a real reset button?!
>
> does your caps lock & scroll lock LED blink? (they should)
>
> does the kernel reboot itself (after ~10 seconds), if you add
> panic=10
> to the kernel-parameters in grub configuration?
>
> do you have some sort of bootsplash or frame buffer console?
> (e.g. KMS/vesa/etc...) because these advanced features can make it
> really hard to get the message to the screen before it goes black.
>
> is there nothing in /var/log/syslog after a crash?
>
>> With regard to the losing connection/timing out, I'm seeing that a
>> fair amount, when I have data transferring (watching an active ssh
>> connection, or streaming audio), and especially when I'm not doing
>> anything...
> well, there could be several different things, I hope you're using
> services like Network-manager, wpa_supplicant to manage your connection.
> Because they will automatically reconnect as soon as the link dies.
>
> what could be interesting: iw dev wlanX scan / iwlist wlanX scan
> dump from your AP... especially the TSF/tsf value,
> (it's a hexadecimal value which acts like a uptime for the AP)
>
> Regards,
> ? ? ? ?Chr
>
On Thu, Nov 12, 2009 at 11:54 AM, Tim Gardner <[email protected]>
> Anyway, I'm updating the Ubuntu LBM package to use
> compat-wireless-2.6.32-rc6 which should be out by tomorrow.
rc7 was just released, and so was compat-wireless-2.6.32-rc7.
Luis