[opensuse-arm] wlan getting new hw-address every 5 minutes on raspberry pi 3
Hi, After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises: every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient. Dmesg spits out the following: [ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1306.576327] cfg80211: World regulatory domain updated: [ 1306.576341] cfg80211: DFS Master region: unset [ 1306.576341] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1306.576347] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576352] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576355] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576359] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1306.576366] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1306.576370] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576373] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1622.585603] cfg80211: World regulatory domain updated: [ 1622.585611] cfg80211: DFS Master region: unset [ 1622.585611] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1622.585618] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585623] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585626] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585634] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1622.585637] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1622.585641] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585644] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1938.587571] cfg80211: World regulatory domain updated: [ 1938.587604] cfg80211: DFS Master region: unset [ 1938.587604] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1938.587617] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587633] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587654] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587676] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1938.587687] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1938.587694] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587705] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2083.905735] fuse init (API version 7.23) [ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 2254.631815] cfg80211: World regulatory domain updated: [ 2254.631823] cfg80211: DFS Master region: unset [ 2254.631823] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 2254.631828] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631833] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631836] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631840] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631844] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 2254.631847] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 2254.631850] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631853] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ================================================================ ever going. What is going on here, and what can be done? Of course I did some googling, but I didn't find anything alike... Regards, Jogchum -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 11/08/2016 09:44 PM, Jogchum Reitsma wrote:
Hi,
After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises:
Would you mind to document this in the wiki, so that the next person who wants to try RPi3 doesn't have to search the list archive (or askes the question again).
every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient.
Dmesg spits out the following:
[ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1306.576327] cfg80211: World regulatory domain updated: [ 1306.576341] cfg80211: DFS Master region: unset [ 1306.576341] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1306.576347] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576352] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576355] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576359] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1306.576366] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1306.576370] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576373] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1622.585603] cfg80211: World regulatory domain updated: [ 1622.585611] cfg80211: DFS Master region: unset [ 1622.585611] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1622.585618] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585623] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585626] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585634] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1622.585637] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1622.585641] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585644] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1938.587571] cfg80211: World regulatory domain updated: [ 1938.587604] cfg80211: DFS Master region: unset [ 1938.587604] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1938.587617] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587633] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587654] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587676] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1938.587687] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1938.587694] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587705] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2083.905735] fuse init (API version 7.23) [ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 2254.631815] cfg80211: World regulatory domain updated: [ 2254.631823] cfg80211: DFS Master region: unset [ 2254.631823] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 2254.631828] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631833] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631836] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631840] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631844] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 2254.631847] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 2254.631850] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631853] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
================================================================
ever going.
What is going on here, and what can be done? Of course I did some googling, but I didn't find anything alike...
I think the best would be to open a bug in bugzilla for this. Maybe you want to attache the wpa_supplicant log as well. Not sure about this, I'm rather a wifi noop. Thanks, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Matthias, Op 09-11-16 om 13:24 schreef Matthias Brugger:
On 11/08/2016 09:44 PM, Jogchum Reitsma wrote:
Hi,
After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises:
Would you mind to document this in the wiki, so that the next person who wants to try RPi3 doesn't have to search the list archive (or askes the question again).
I'm not sure where to put this in the wiki. The only specific place seems to me https://en.opensuse.org/HCL:Raspberry_Pi3 but that's just a bit about where to get the images, and how to install them. Seems somewhat inapporpriate to me to put is there.
every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient.
Dmesg spits out the following:
[ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1306.576327] cfg80211: World regulatory domain updated: [ 1306.576341] cfg80211: DFS Master region: unset [ 1306.576341] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1306.576347] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576352] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576355] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576359] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1306.576366] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1306.576370] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576373] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1622.585603] cfg80211: World regulatory domain updated: [ 1622.585611] cfg80211: DFS Master region: unset [ 1622.585611] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1622.585618] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585623] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585626] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585634] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1622.585637] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1622.585641] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585644] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1938.587571] cfg80211: World regulatory domain updated: [ 1938.587604] cfg80211: DFS Master region: unset [ 1938.587604] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1938.587617] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587633] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587654] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587676] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1938.587687] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1938.587694] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587705] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2083.905735] fuse init (API version 7.23) [ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 2254.631815] cfg80211: World regulatory domain updated: [ 2254.631823] cfg80211: DFS Master region: unset [ 2254.631823] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 2254.631828] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631833] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631836] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631840] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631844] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 2254.631847] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 2254.631850] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631853] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
================================================================
ever going.
What is going on here, and what can be done? Of course I did some googling, but I didn't find anything alike...
I think the best would be to open a bug in bugzilla for this. Maybe you want to attache the wpa_supplicant log as well. Not sure about this, I'm rather a wifi noop.
I'll await the dialogue with Stefan before issuing a bugreport.
Thanks, Matthias
I'm not sure where to put -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 11/09/2016 05:52 PM, Jogchum Reitsma wrote:
Hi Matthias,
Op 09-11-16 om 13:24 schreef Matthias Brugger:
On 11/08/2016 09:44 PM, Jogchum Reitsma wrote:
Hi,
After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises:
Would you mind to document this in the wiki, so that the next person who wants to try RPi3 doesn't have to search the list archive (or askes the question again).
I'm not sure where to put this in the wiki. The only specific place seems to me
https://en.opensuse.org/HCL:Raspberry_Pi3
but that's just a bit about where to get the images, and how to install them. Seems somewhat inapporpriate to me to put is there.
As there already exists a "Tips for openSUSE Tumbleweed (upstream)" maybe under a new section: Tips for non-upstream openSUSE Tumbleweed
every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient.
Dmesg spits out the following:
[ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1306.576327] cfg80211: World regulatory domain updated: [ 1306.576341] cfg80211: DFS Master region: unset [ 1306.576341] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1306.576347] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576352] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576355] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576359] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1306.576362] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1306.576366] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1306.576370] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1306.576373] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1622.585603] cfg80211: World regulatory domain updated: [ 1622.585611] cfg80211: DFS Master region: unset [ 1622.585611] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1622.585618] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585623] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585626] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585630] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1622.585634] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1622.585637] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1622.585641] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1622.585644] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 1938.587571] cfg80211: World regulatory domain updated: [ 1938.587604] cfg80211: DFS Master region: unset [ 1938.587604] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 1938.587617] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587633] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587654] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587666] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 1938.587676] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 1938.587687] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 1938.587694] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 1938.587705] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 2083.905735] fuse init (API version 7.23) [ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 2254.631815] cfg80211: World regulatory domain updated: [ 2254.631823] cfg80211: DFS Master region: unset [ 2254.631823] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 2254.631828] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631833] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631836] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631840] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 2254.631844] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 2254.631847] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 2254.631850] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 2254.631853] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
================================================================
ever going.
What is going on here, and what can be done? Of course I did some googling, but I didn't find anything alike...
I think the best would be to open a bug in bugzilla for this. Maybe you want to attache the wpa_supplicant log as well. Not sure about this, I'm rather a wifi noop.
I'll await the dialogue with Stefan before issuing a bugreport.
Thanks, Matthias
I'm not sure where to put
What do you mean? In bugzilla? This should be openSUSE -> openSUSE Tumbleweed Component: Network Hardware: aarch64 and put in the summary a prefix like "RPi3:" Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op 09-11-16 om 18:07 schreef Matthias Brugger:
On 11/09/2016 05:52 PM, Jogchum Reitsma wrote:
Hi Matthias,
Op 09-11-16 om 13:24 schreef Matthias Brugger:
Would you mind to document this in the wiki, so that the next person who wants to try RPi3 doesn't have to search the list archive (or askes the question again).
I'm not sure where to put this in the wiki. The only specific place seems to me
https://en.opensuse.org/HCL:Raspberry_Pi3
but that's just a bit about where to get the images, and how to install them. Seems somewhat inapporpriate to me to put is there.
I'm not sure where to put
What do you mean? In bugzilla?
No, I meant where in the wiki to put it, but you answered that already. For the bugzilla report I suggested to await the dialogue with Stefan in this thread, so we can pinpoint it more precisely before entering the bug. I know where to put it in bugzilla.
This should be openSUSE -> openSUSE Tumbleweed Component: Network Hardware: aarch64 and put in the summary a prefix like "RPi3:"
Regards, Matthias
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Dienstag, 8. November 2016 21:44:11 CET Jogchum Reitsma wrote:
Hi,
After succeeding in getting wifi enabled on the pi 3 (see my previous posting 6th of nov., 20:31 WET, and follow ups) the next problem arises: every 5 minutes the wifi connection gets another hw-address, and hence another ip address... Rather inconvenient.
May be an effect of mac address randomization. Can you post output of - journalctl -b -u NetworkManager - journalctl -b -u wpa_supplicant - rpm -qi NetworkManager - rpm -qi wpa_supplicant - contents of /etc/NetworkManager/system-connections/ for the relevant connection The last one may contain network credentials! Kind regards, Stefan -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Stefan, The results: - journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning) nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.8196] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.8391] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:09:28 nohostname NetworkManager[548]: <info> [1478707768.3478] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:09:28 nohostname NetworkManager[548]: <info> [1478707768.4907] device (wlan0): supplicant interface state: associating -> associated nov 09 17:09:29 nohostname NetworkManager[548]: <info> [1478707769.3616] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:09:29 nohostname NetworkManager[548]: <info> [1478707769.3896] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:14:43 nohostname NetworkManager[548]: <info> [1478708083.8001] device (wlan0): set-hw-addr: set MAC address to 0A:A7:4F:EE:ED:1F (scanning) nov 09 17:14:43 nohostname NetworkManager[548]: <info> [1478708083.8411] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:14:43 nohostname NetworkManager[548]: <info> [1478708083.8677] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:14:44 nohostname NetworkManager[548]: <info> [1478708084.3711] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:14:44 nohostname NetworkManager[548]: <info> [1478708084.4970] device (wlan0): supplicant interface state: associating -> associated nov 09 17:14:45 nohostname NetworkManager[548]: <info> [1478708085.3868] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:14:45 nohostname NetworkManager[548]: <info> [1478708085.4151] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:19:59 nohostname NetworkManager[548]: <info> [1478708399.7729] device (wlan0): set-hw-addr: set MAC address to 4E:64:DC:FB:0D:B5 (scanning) nov 09 17:19:59 nohostname NetworkManager[548]: <info> [1478708399.7993] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:19:59 nohostname NetworkManager[548]: <info> [1478708399.8034] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:20:00 nohostname NetworkManager[548]: <info> [1478708400.2964] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:20:00 nohostname NetworkManager[548]: <info> [1478708400.3982] device (wlan0): supplicant interface state: associating -> 4-way handshake nov 09 17:20:00 nohostname NetworkManager[548]: <info> [1478708400.4309] device (wlan0): supplicant interface state: 4-way handshake -> completed
- journalctl -b -u wpa_supplicant journalctl -b -u wpa_supplicant -- Logs begin at do 1970-01-01 01:00:02 CET, end at wo 2016-11-09 17:37:04 CET. -- jan 01 01:00:11 nohostname systemd[1]: Starting WPA Supplicant daemon... jan 01 01:00:12 nohostname systemd[1]: Started WPA Supplicant daemon.
- rpm -qi NetworkManager rpm -qi NetworkManager Name : NetworkManager Version : 1.4.2 Release : 1.2 Architecture: aarch64 Install Date: do 03 nov 2016 09:06:44 CET Group : Productivity/Networking/System Size : 7051697 License : GPL-2.0+ Signature : RSA/SHA256, wo 26 okt 2016 19:46:30 CEST, Key ID b88b2fd43dbdc284 Source RPM : NetworkManager-1.4.2-1.2.src.rpm Build Date : wo 26 okt 2016 19:44:35 CEST Build Host : armbuild24 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.gnome.org/projects/NetworkManager/ Summary : Network Link Manager and User Applications Description : NetworkManager attempts to keep an active network connection available at all times. The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is intended to replace default routes, obtain IP addresses from a DHCP server, and change name servers whenever it sees fit. Distribution: openSUSE Tumbleweed
- rpm -qi wpa_supplicant rpm -qi wpa_supplicant Name : wpa_supplicant Version : 2.6 Release : 1.1 Architecture: aarch64 Install Date: do 03 nov 2016 09:05:36 CET Group : Productivity/Networking/Other Size : 2494425 License : BSD-3-Clause and GPL-2.0+ Signature : RSA/SHA256, vr 14 okt 2016 04:10:40 CEST, Key ID b88b2fd43dbdc284 Source RPM : wpa_supplicant-2.6-1.1.src.rpm Build Date : vr 14 okt 2016 04:09:51 CEST Build Host : armbuild21 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://hostap.epitest.fi/wpa_supplicant/ Summary : WPA supplicant implementation Description : wpa_supplicant is an implementation of the WPA Supplicant component, i.e., the part that runs in the client stations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wlan driver. Distribution: openSUSE Tumbleweed
- contents of /etc/NetworkManager/system-connections/ for the relevant connection
This is an existing, but empty dir.
The last one may contain network credentials!
Kind regards,
Stefan
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote:
Hi Stefan,
The results:
- journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:)
nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning)
This is odd. Obviously it has connected to the network successfully. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously. You may try disabling mac randomization temporarily. Anyway, I think this is worth an upstream bug report. Kind regards, Stefan -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op 09-11-16 om 18:20 schreef Brüns, Stefan:
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote:
<...> This is odd. Obviously it has connected to the network successfully. Yes, I can ping it, and ssh to the wlan ip address, until a new address is given. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously.
You may try disabling mac randomization temporarily. OK. Where can I do that?
Anyway, I think this is worth an upstream bug report.
Which upstream should I send the bugreport? Never swam that high... Thanks! regards, Jogchum Reitsma -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 09.11.2016 um 12:20 schrieb Brüns, Stefan <Stefan.Bruens@rwth-aachen.de>:
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote: Hi Stefan,
The results:
- journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:)
nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning)
This is odd. Obviously it has connected to the network successfully. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously.
You may try disabling mac randomization temporarily.
Anyway, I think this is worth an upstream bug report.
Could you please try again with a really strong power supply first? Thanks, Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op 09-11-16 om 23:27 schreef Alexander Graf:
Am 09.11.2016 um 12:20 schrieb Brüns, Stefan <Stefan.Bruens@rwth-aachen.de>:
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote: Hi Stefan,
The results:
- journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:)
nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning) This is odd. Obviously it has connected to the network successfully. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously.
You may try disabling mac randomization temporarily.
Anyway, I think this is worth an upstream bug report. Could you please try again with a really strong power supply first?
Thanks,
Alex
Power supply until now was 5.2 V, 2A; what should it be? regards, Jogchum
5.2 V, 2 A; -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 10.11.2016 um 13:34 schrieb Jogchum Reitsma <j.reitsma@hccnet.nl>:
Op 09-11-16 om 23:27 schreef Alexander Graf:
Am 09.11.2016 um 12:20 schrieb Brüns, Stefan <Stefan.Bruens@rwth-aachen.de>:
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote: Hi Stefan,
The results:
- journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:)
nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning) This is odd. Obviously it has connected to the network successfully. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously.
You may try disabling mac randomization temporarily.
Anyway, I think this is worth an upstream bug report. Could you please try again with a really strong power supply first?
Thanks,
Alex
Power supply until now was 5.2 V, 2A; what should it be?
2A should work, but dropping out wifi is a pretty common symptom of an unreliable power supply. I just want to make sure we're not chasing ghosts ;). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op 09-11-16 om 18:20 schreef Brüns, Stefan:
On Mittwoch, 9. November 2016 17:44:16 CET Jogchum Reitsma wrote:
Hi Stefan,
The results:
- journalctl -b -u NetworkManager (there is much more output, but I take it this is what you mean:)
nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.7727] device (wlan0): set-hw-addr: set MAC address to 8E:07:9D:1E:8C:93 (scanning) nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8066] device (wlan0): supplicant interface state: completed -> disabled nov 09 17:04:11 nohostname NetworkManager[548]: <info> [1478707451.8078] device (wlan0): supplicant interface state: disabled -> scanning nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.3294] device (wlan0): supplicant interface state: scanning -> associating nov 09 17:04:12 nohostname NetworkManager[548]: <info> [1478707452.4836] device (wlan0): supplicant interface state: associating -> associated nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3429] device (wlan0): supplicant interface state: associated -> 4-way handshake nov 09 17:04:13 nohostname NetworkManager[548]: <info> [1478707453.3706] device (wlan0): supplicant interface state: 4-way handshake -> completed nov 09 17:09:27 nohostname NetworkManager[548]: <info> [1478707767.7887] device (wlan0): set-hw-addr: set MAC address to 56:74:0F:44:0E:15 (scanning) This is odd. Obviously it has connected to the network successfully. The scanning actions may be background scans, but it should re-set the mac address to the one successfully used with the access point previously.
You may try disabling mac randomization temporarily.
Anyway, I think this is worth an upstream bug report.
Kind regards,
Stefan
Anyone who can tell me where to disable mac address randomization? Also for a link to upstream where I can post a bug report. Thanks! -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Alexander Graf -
Brüns, Stefan -
Jogchum Reitsma -
Matthias Brugger