| Summary: | WiFi connection goes down and up every once in a while in MATE | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | JMiahMan, kernel, marja11, tarakbumba |
| Version: | 6 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
Wanted journalctl log
dmesg |
||
|
Description
Kristoffer Grundström
2017-10-05 04:16:50 CEST
iwlwifi is the module I'm using. (In reply to Kristoffer Grundström from comment #0) > I'm using a ASUS N550JK laptop. > 5. The connection works just fine until you either reboot or wait a long > time. > It will go down and then within 5 seconds go up again. What do you mean with "wait a long time"? Wait while using the laptop and its wlan interface, or wait without doing anything with it? If the latter, then what do you mean with "within 5 seconds go up again"? Within 5 seconds after it stopped working, regardless of whether you touch it or not, or within 5 seconds after you touch it? Keywords:
(none) =>
NEEDINFO Waiting while using the laptop and its wlan interface. To me it looks like the Network interface breaks due to high usage. I use git and repo sync a lot and if I sync from github I get that problem, but not otherwise. After it goes down it comes back up again (reconnects) within 10 seconds. No error is displayed other than that the wlan interface is down and up after some time. (In reply to Kristoffer Grundström from comment #3) Thx for having answered my questions. > > No error is displayed other than that the wlan interface is down and up > after some time. Please create log.txt from just before till just after that happens, anyway :-) As root run (use the correct day+times): journalctl --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" > log.txt And then attach log.txt http://pastebin.ubuntu.com/25695605/ It was to big to add as an attachment here. You may also want to post your dmesg as well just: dmesg > dmesg-$(date +%F).log and then attach the log. CC:
(none) =>
JMiahMan (In reply to Kristoffer Grundström from comment #5) > http://pastebin.ubuntu.com/25695605/ > > It was to big to add as an attachment here. please compress it with xz and then attach it. Created attachment 9712 [details]
Wanted journalctl log
Created attachment 9713 [details]
dmesg
It could be the router as well, but it's brand new and I flashed it with the latest firmware available. I'll flash LEDE/OpenWrt to it to see if the problem goes away. (In reply to Kristoffer Grundström from comment #10) > It could be the router as well, but it's brand new and I flashed it with the > latest firmware available. > > I'll flash LEDE/OpenWrt to it to see if the problem goes away. I'm lazy enough to wait till you report back (so I'm not yet reading your attachments) ;-) Flashing the router with LEDE/OpenWrt seems to do the trick. Fawlty original firmware I guess. Closing as RESOLVED WORKSFORME as the issue was in the router and not in Mageia itself. If I made a boo boo because you experience the same issue, please go ahead and reopen it with new information. Resolution:
(none) =>
WORKSFORME |