| Summary: | Unstable wireless connection with iwlwifi | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pavel Kreuzt <pkreuzt> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, lewyssmith, marja11 |
| Version: | 8 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Pavel Kreuzt
2022-02-13 18:03:51 CET
Thank you for reporting I this a new problem,have it been working better earlier on the same system? You can try new firmwares Bug 30038 and kernel Bug 30030 Is there something interesting in the journal? CC:
(none) =>
fri Before last kernel update (I think) it worked, but not perfect. It took some time to connect after boot already. Things got worse after that. On dmesg output I can see this sequence: [ 3430.216071] wlp3s0: deauthenticated from [redacted] (Reason: 3=DEAUTH_LEAVING) [ 4082.374878] wlp3s0: authenticate with [redacted] [ 4082.382067] wlp3s0: send auth to [redacted] (try 1/3) [ 4082.422683] wlp3s0: authenticated [ 4082.423337] wlp3s0: associate with [redacted] (try 1/3) [ 4082.425804] wlp3s0: RX AssocResp from [redacted] (capab=0x1511 status=0 aid=1) [ 4082.427408] wlp3s0: associated [ 4082.463656] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [ 4082.484089] wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by [redacted] Journal shows this at boot feb 13 16:27:37 Tartar.Hades network[1706]: Activando interfaz enp4s0: [ OK ] feb 13 16:27:39 Tartar.Hades network[1706]: Activando interfaz vboxnet0: feb 13 16:27:39 Tartar.Hades network[4665]: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device vboxnet0 does not seem to be present, delaying initialization. feb 13 16:27:39 Tartar.Hades network[1706]: [FALLÓ ] feb 13 16:27:40 Tartar.Hades network[1706]: Activando interfaz wlp3s0: feb 13 16:27:40 Tartar.Hades network[5872]: Error for wireless request "Set Encode" (8B2A) : feb 13 16:27:40 Tartar.Hades network[5872]: SET failed on device wlp3s0 ; Invalid argument. feb 13 16:27:40 Tartar.Hades network[5875]: Successfully initialized wpa_supplicant feb 13 16:27:40 Tartar.Hades kernel: NET: Registered PF_PACKET protocol family feb 13 16:27:40 Tartar.Hades network[5880]: RTNETLINK answers: Device or resource busy feb 13 16:27:40 Tartar.Hades network[1706]: [ OK ] feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd-sysctl[5901]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Control process exited, code=exited, status=1/FAILURE feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Failed with result 'exit-code'. feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Unit process 4643 (ifplugd) remains running after unit stopped. feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Unit process 5879 (wpa_supplicant) remains running after unit stopped. feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Unit process 5882 (ifplugd) remains running after unit stopped. feb 13 16:27:40 Tartar.Hades systemd[1]: Failed to start LSB: Bring up/down networking. feb 13 16:27:40 Tartar.Hades systemd[1]: network.service: Consumed 2.552s CPU time. feb 13 16:27:40 Tartar.Hades systemd[1]: Reached target Network. feb 13 16:27:40 Tartar.Hades systemd[1]: Reached target Network is Online. And further feb 13 16:28:20 Tartar.Hades systemd[1]: systemd-hostnamed.service: Succeeded. feb 13 16:28:54 Tartar.Hades systemd[1]: Stopping WPA Supplicant daemon... feb 13 16:28:54 Tartar.Hades systemd[1]: wpa_supplicant.service: Succeeded. feb 13 16:28:54 Tartar.Hades systemd[1]: Stopped WPA Supplicant daemon. feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: authenticate with [redacted] feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: send auth to [redacted] (try 1/3) feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: authenticated feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: associate with [redacted] (try 1/3) feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: RX AssocResp from [redacted] (capab=0x1511 status=0 aid=1) feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: associated feb 13 16:29:05 Tartar.Hades kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by [redacted] feb 13 16:29:05 Tartar.Hades kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready feb 13 16:29:33 Tartar.Hades systemd[1]: network.service: Found left-over process 4643 (ifplugd) in control group while starting unit. Ignoring. feb 13 16:29:33 Tartar.Hades systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. feb 13 16:29:33 Tartar.Hades systemd[1]: network.service: Found left-over process 5879 (wpa_supplicant) in control group while starting unit. Ignoring. feb 13 16:29:33 Tartar.Hades systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. feb 13 16:29:33 Tartar.Hades systemd[1]: network.service: Found left-over process 5882 (ifplugd) in control group while starting unit. Ignoring. feb 13 16:29:33 Tartar.Hades systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. feb 13 16:29:33 Tartar.Hades systemd[1]: network.service: Found left-over process 19012 (dhclient) in control group while starting unit. Ignoring. feb 13 16:29:33 Tartar.Hades systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. feb 13 16:29:33 Tartar.Hades systemd[1]: Starting LSB: Bring up/down networking... feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). feb 13 16:29:33 Tartar.Hades systemd-sysctl[24071]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). feb 13 16:29:33 Tartar.Hades network[24036]: Activando interfaz loopback: feb 13 16:29:33 Tartar.Hades network[24158]: 127.0.0.1 feb 13 16:29:33 Tartar.Hades network[24174]: ● squid.service - Squid Web Proxy Server feb 13 16:29:33 Tartar.Hades network[24174]: Loaded: loaded (/usr/lib/systemd/system/squid.service; disabled; vendor preset: disabled) feb 13 16:29:33 Tartar.Hades network[24174]: Active: inactive (dead) feb 13 16:29:33 Tartar.Hades network[24174]: Docs: man:squid(8) feb 13 16:29:33 Tartar.Hades network[24036]: [ OK ] feb 13 16:29:33 Tartar.Hades network[24036]: Activando interfaz enp0s20u11: feb 13 16:29:33 Tartar.Hades network[24187]: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device enp0s20u11 does not seem to be present, delaying initialization. feb 13 16:29:33 Tartar.Hades network[24036]: [FALLÓ ] feb 13 16:29:34 Tartar.Hades network[24036]: Activando interfaz enp4s0: feb 13 16:29:34 Tartar.Hades network[24242]: Sorry, there is already an instance of ifplugd for enp4s0 running. feb 13 16:29:34 Tartar.Hades network[24036]: [FALLÓ ] feb 13 16:29:34 Tartar.Hades network[24036]: Activando interfaz vboxnet0: feb 13 16:29:34 Tartar.Hades network[24273]: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device vboxnet0 does not seem to be present, delaying initialization. feb 13 16:29:34 Tartar.Hades network[24036]: [FALLÓ ] feb 13 16:29:34 Tartar.Hades kernel: wlp3s0: deauthenticating from [redacted] by local choice (Reason: 3=DEAUTH_LEAVING) feb 13 16:29:34 Tartar.Hades network[24036]: Activando interfaz wlp3s0: feb 13 16:29:34 Tartar.Hades network[24351]: Error for wireless request "Set Encode" (8B2A) : feb 13 16:29:34 Tartar.Hades network[24351]: SET failed on device wlp3s0 ; Invalid argument. feb 13 16:29:34 Tartar.Hades network[24312]: Another wpa_supplicant instance is already running for device wlp3s0 feb 13 16:29:34 Tartar.Hades network[24354]: RTNETLINK answers: Device or resource busy feb 13 16:29:34 Tartar.Hades network[24312]: Sorry, there is already an instance of ifplugd for wlp3s0 running. feb 13 16:29:34 Tartar.Hades network[24036]: [FALLÓ ] feb 13 16:29:34 Tartar.Hades network[24365]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24366]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24367]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24368]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24369]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24370]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24371]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24372]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades network[24373]: RTNETLINK answers: File exists feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd-sysctl[24374]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Control process exited, code=exited, status=1/FAILURE feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Failed with result 'exit-code'. feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Unit process 4643 (ifplugd) remains running after unit stopped. feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Unit process 5879 (wpa_supplicant) remains running after unit stopped. feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Unit process 5882 (ifplugd) remains running after unit stopped. feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Unit process 19012 (dhclient) remains running after unit stopped. feb 13 16:29:34 Tartar.Hades systemd[1]: Failed to start LSB: Bring up/down networking. feb 13 16:29:34 Tartar.Hades systemd[1]: network.service: Consumed 2.533s CPU time. feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: authenticate with [redacted-the 2.4G MAC from same AP] feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: send auth to [redacted-the 2.4G MAC from same AP] (try 1/3) feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: authenticated feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: associate with [redacted-the 2.4G MAC from same AP] (try 1/3) feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: RX AssocResp from [redacted-the 2.4G MAC from same AP] (capab=0x1431 status=0 aid=3) feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: associated feb 13 16:29:39 Tartar.Hades kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready feb 13 16:29:39 Tartar.Hades kernel: wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by [redacted-the 2.4G MAC from same AP] feb 13 16:29:54 Tartar.Hades mandi[6285]: skipping known address: 192.168.1.100 feb 13 16:30:07 Tartar.Hades kernel: wlp3s0: disassociated from [redacted-the 2.4G MAC from same AP] (Reason: 33=DISASSOC_QAP_NO_BANDWIDTH) feb 13 16:30:07 Tartar.Hades kernel: wlp3s0: authenticate with [redacted-the 2.4G MAC from same AP] feb 13 16:30:07 Tartar.Hades kernel: wlp3s0: send auth to [redacted-the 2.4G MAC from same AP] (try 1/3) feb 13 16:30:07 Tartar.Hades kernel: wlp3s0: [redacted-the 2.4G MAC from same AP] denied authentication (status 34) feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: authenticate with [redacted-the 2.4G MAC from same AP] feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: send auth to [redacted-the 2.4G MAC from same AP] (try 1/3) feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: authenticated feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: associate with [redacted-the 2.4G MAC from same AP] (try 1/3) feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: RX AssocResp from [redacted-the 2.4G MAC from same AP] (capab=0x1431 status=0 aid=3) feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: associated feb 13 16:30:08 Tartar.Hades kernel: wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by [redacted-the 2.4G MAC from same AP] For some reason it tries to authenticate to the wrong BSSID (router is dualband with same net name). In Drakroam I already had specified 5G band only in advanced options. Sorry to have left you. I wonder whether this has any connection (pun not intended) to '5G' - whether things started getting worse with that, or whether you previously had no problems with it. In any case, please give any information you can about the WiFi hardware and connection. For example: $ inxi -i [you may want to hide certain address fields] the relevant section of 'ifconfig' [same caution] CC:
(none) =>
lewyssmith (In reply to Lewis Smith from comment #3) > Sorry to have left you. I wonder whether this has any connection (pun not > intended) to '5G' - whether things started getting worse with that, or > whether you previously had no problems with it. > > In any case, please give any information you can about the WiFi hardware and > connection. For example: > $ inxi -i [you may want to hide certain address fields] > the relevant section of 'ifconfig' [same caution] @ Pavel Ping? Keywords:
(none) =>
NEEDINFO months later, no reply, so closing Status:
NEW =>
RESOLVED |