Search Linux Wireless

Re: Regression in commit 0d528d8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/11/2013 02:47 PM, Felix Fietkau wrote:
On 2013-10-11 9:42 PM, Larry Finger wrote:
On 10/10/2013 04:35 PM, Felix Fietkau wrote:
I don't recall any necessary extra actions introduced by this patch.
Please compare the rate selection info passed to the driver before and
after this patch, by dumping info->control.rates.

I dumped the structure returned by ieee80211_get_tx_rate(hw, info) and found the
same values for the case that worked and the one that failed. The values were:
flags 0xc, bitrate 0xa, hw_value 0x0, and hw_value_short 0x0.
I guess then we need to take another look at what exactly happens when
the connection fails, I have no idea how that commit can affect rtlwifi.

With NetworkManager, the interface authenticates and associates normally, but it seems that DHCP never completes. I will fire up my trusty machine that handles kismet and get a dump of what is on the air.

Larry


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux