Realtek ethernet problems r8168-dkms and r8169

Kernels & Hardware, configuring network, installing services

Realtek ethernet problems r8168-dkms and r8169

Postby bmickey » 2018-10-31 04:23

Hi I was wondering if someone could help me interpret the output in my computers syslog.

I typically don't use my ethernet but recently I have started to and its giving me a large amount of problems.
It will work for a couple minutes and then I will lose connection to whatever web pages I'm looking at.
This is my ethernet controller,

Code: Select all
 lshw -C network
  *-network                 
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:3b:00.0
       logical name: enp59s0
       version: 15
       serial: a4:4c:c8:5c:c3:52
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.6 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
       resources: irq:139 ioport:d000(size=256) memory:dd304000-dd304fff memory:dd300000-dd303fff


I've been searching the internet and while I find that there seems to be no shortage of problems with Realtek I can't find anything about a resolution with debian.

I had r8168-dkms installed but it was slow and kept losing its connection. Then I read that I should purge r8168-dkms and it would use the default r8169 in the kernel so I did. But while that is indeed much faster when its working it suffers from the same issue as r8168 and keeps dropping the connection.

Here is the syslog info - it was basically the exact same when I had r8168 installed.
    265 Oct 31 00:08:10 debian NetworkManager[560]: <info> [1540958890.0885] policy: set 'Wired connection' (enp59s0) as default for IPv4 routing and DNS
    266 Oct 31 00:08:10 debian NetworkManager[560]: <info> [1540958890.0928] device (enp59s0): Activation: successful, device activated.
    267 Oct 31 00:08:10 debian nm-dispatcher: req:3 'up' [enp59s0]: new request (1 scripts)
    268 Oct 31 00:08:10 debian nm-dispatcher: req:3 'up' [enp59s0]: start running ordered scripts...
    269 Oct 31 00:09:07 debian kernel: [ 2.421141] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    270 Oct 31 00:09:07 debian kernel: [ 2.421146] r8169 0000:3b:00.0: can't disable ASPM; OS doesn't have ASPM control
    271 Oct 31 00:09:07 debian kernel: [ 2.434035] r8169 0000:3b:00.0 eth0: RTL8168h/8111h at 0xffff99d9419fd000, a4:4c:c8:5c:c3:52, XID 14100800 IRQ 139
    272 Oct 31 00:09:07 debian kernel: [ 2.434037] r8169 0000:3b:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
    273 Oct 31 00:09:07 debian kernel: [ 2.525958] r8169 0000:3b:00.0 enp59s0: renamed from eth0
    274 Oct 31 00:09:07 debian NetworkManager[568]: <info> [1540958947.5326] devices added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:3b:00.0/net/enp59s0, iface: enp59s0)
    275 Oct 31 00:09:07 debian NetworkManager[568]: <info> [1540958947.5327] device added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:3b:00.0/net/enp59s0, iface: enp59s0): no ifupdown configuration found.
    276 Oct 31 00:09:07 debian NetworkManager[568]: <info> [1540958947.7313] manager: (enp59s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
    277 Oct 31 00:09:07 debian NetworkManager[568]: <info> [1540958947.7323] device (enp59s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
    278 Oct 31 00:09:09 debian kernel: [ 3.955088] IPv6: ADDRCONF(NETDEV_UP): enp59s0: link is not ready
    279 Oct 31 00:09:09 debian kernel: [ 3.955570] r8169 0000:3b:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw
    280 Oct 31 00:09:09 debian kernel: [ 4.003072] r8169 0000:3b:00.0 enp59s0: link down
    281 Oct 31 00:09:09 debian kernel: [ 4.003074] r8169 0000:3b:00.0 enp59s0: link down
    282 Oct 31 00:09:09 debian kernel: [ 4.003169] IPv6: ADDRCONF(NETDEV_UP): enp59s0: link is not ready
    283 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7194] device (enp59s0): link connected
    284 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7200] device (enp59s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
    285 Oct 31 00:09:10 debian kernel: [ 6.941799] r8169 0000:3b:00.0 enp59s0: link up
    286 Oct 31 00:09:10 debian kernel: [ 6.941805] IPv6: ADDRCONF(NETDEV_CHANGE): enp59s0: link becomes ready
    287 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7220] device (enp59s0): Activation: starting connection 'Wired connection' (21309954-2d99-41fe-bb20-5f629cf3ef6b)
    288 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7222] device (enp59s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
    289 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7226] device (enp59s0): state change: prepare -> config (reason 'none') [40 50 0]
    290 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7229] device (enp59s0): state change: config -> ip-config (reason 'none') [50 70 0]
    291 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7234] dhcp4 (enp59s0): activation: beginning transaction (timeout in 45 seconds)
    292 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7282] dhcp4 (enp59s0): dhclient started with pid 1064
    293 Oct 31 00:09:10 debian dhclient[1064]: DHCPREQUEST of 192.168.1.6 on enp59s0 to 255.255.255.255 port 67
    294 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7909] dhcp4 (enp59s0): address 192.168.1.6
    295 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7909] dhcp4 (enp59s0): plen 24 (255.255.255.0)
    296 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7909] dhcp4 (enp59s0): gateway 192.168.1.1
    297 Oct 31 00:09:10 debian avahi-daemon[528]: Joining mDNS multicast group on interface enp59s0.IPv4 with address 192.168.1.6.
    298 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7909] dhcp4 (enp59s0): server identifier 192.168.1.1
    299 Oct 31 00:09:10 debian avahi-daemon[528]: New relevant interface enp59s0.IPv4 for mDNS.
    300 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7910] dhcp4 (enp59s0): lease time 86400
    301 Oct 31 00:09:10 debian avahi-daemon[528]: Registering new address record for 192.168.1.6 on enp59s0.IPv4.
    302 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7910] dhcp4 (enp59s0): nameserver '192.168.1.1'
    303 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7910] dhcp4 (enp59s0): state changed unknown -> bound
    304 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7919] device (enp59s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
    305 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7924] device (enp59s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
    306 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7927] device (enp59s0): state change: secondaries -> activated (reason 'none') [90 100 0]
    307 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.7988] policy: set 'Wired connection' (enp59s0) as default for IPv4 routing and DNS
    308 Oct 31 00:09:10 debian NetworkManager[568]: <info> [1540958950.8508] device (enp59s0): Activation: successful, device activated.
    309 Oct 31 00:09:10 debian nm-dispatcher: req:3 'up' [enp59s0]: new request (1 scripts)
    310 Oct 31 00:09:10 debian nm-dispatcher: req:3 'up' [enp59s0]: start running ordered scripts...
    311 Oct 31 00:09:12 debian avahi-daemon[528]: Joining mDNS multicast group on interface enp59s0.IPv6 with address fe80::a64c:c8ff:fe5c:c352.
    312 Oct 31 00:09:12 debian avahi-daemon[528]: New relevant interface enp59s0.IPv6 for mDNS.
    313 Oct 31 00:09:12 debian avahi-daemon[528]: Registering new address record for fe80::a64c:c8ff:fe5c:c352 on enp59s0.*.

I can see that there's some issue with dhcp and its trying to switch between ipv4 and ipv6 but I don't really knows whats going.

Thank you.
bmickey
 
Posts: 15
Joined: 2018-01-20 20:42

Re: Realtek ethernet problems r8168-dkms and r8169

Postby bw123 » 2018-10-31 13:48

I didn't see the problem, but have you tried disabling ipv6 and see if that helps?

I don't understand what you mean by, "... lose connection to whatever web pages I'm looking at."
User avatar
bw123
 
Posts: 3572
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Segfault » 2018-10-31 14:31

It generally helps alot if you diagnose the problem instead of trying random repairs. For instance, when you lost connection, did you run ethtool to see if there still is functioning physical connection?
Segfault
 
Posts: 808
Joined: 2005-09-24 12:24

Re: Realtek ethernet problems r8168-dkms and r8169

Postby bw123 » 2018-10-31 14:56

Another random thing I might try is another dns server.
User avatar
bw123
 
Posts: 3572
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Segfault » 2018-10-31 15:49

RANT
Look at all that DNS complexity. Linux used to be strong because it was simple. You put your nameservers into resolv.conf and they stayed there until you changed your mind. Now a certain company is flooding Linux with all these "improvements", systemd, PulseAudio, avahi, whatnot. Result, Linux is getting Windows-like. Configuration changes unexpectedly, things that used just to work don't work any more, system that didn't need any maintenance suddenly has a life in its own and demands tinkering by admin to keep it working. Phooey. I keep my boxes simple. No DHCP for desktops and servers. Period.
Segfault
 
Posts: 808
Joined: 2005-09-24 12:24

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Head_on_a_Stick » 2018-10-31 18:35

Segfault wrote:You put your nameservers into resolv.conf and they stayed there until you changed your mind.

For systemd-networkd & systemd-resolved a static resolv.conf will not be touched:
systemd-resolved(8) wrote:Alternatively, /etc/resolv.conf may be managed by other packages, in which case systemd-resolved will read it for DNS configuration data. In this mode of operation systemd-resolved is consumer rather than provider of this configuration file.

@OP: sounds like a power saving issue, please post the output of
Code: Select all
/sbin/iwconfig

If the command can't be found then install the wireless-tools package.
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8315
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Realtek ethernet problems r8168-dkms and r8169

Postby stevepusser » 2018-10-31 18:49

These kind of Realtek wired NICs often complain about missing firmware in dmesg, too, but then seem to work anyway.

If you do see those messages in the dmesg output, installing the non-free firmware-realtek will get rid of them...maybe even fix your original issue.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, tlp-ui, wine-staging 3.21, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10250
Joined: 2009-10-06 05:53

Re: Realtek ethernet problems r8168-dkms and r8169

Postby bmickey » 2018-10-31 19:02

Segfault wrote:It generally helps alot if you diagnose the problem instead of trying random repairs. For instance, when you lost connection, did you run ethtool to see if there still is functioning physical connection?


I did run ethtool and there was no connection. Also I didn't try any random repairs I simply installed the free version of the module which is included in the kernel as the r8168-dkms maintainer recommends. This recommendation was also in the details from
Code: Select all
~$ apt show r8168-dkms
Package: r8168-dkms
Version: 8.043.02-1
Priority: extra
Section: non-free/kernel
Source: r8168
Maintainer: Andreas Beckmann <anbe@debian.org>
Installed-Size: 1,135 kB
Depends: dkms (>= 2.1.0.0)
Homepage: https://github.com/mtorromeo/r8168
Download-Size: 88.0 kB
APT-Sources: http://deb.debian.org/debian stable/non-free amd64 Packages
Description: dkms source for the r8168 network driver
 r8168 is the Linux device driver released for RealTek RTL8111B/RTL8168B,
 RTL8111/RTL8168, RTL8111C/RTL8111CP/RTL8111D(L), RTL8168C/RTL8111DP/RTL8111E,
 RTL8168E/RTL8111F/RTL8411, RTL8111G/RTL8111GUS/RTL8411B(N), RTL8118AS
 Gigabit Ethernet controllers with PCI-Express interface.
 .
This driver should only be used for devices not yet supported by the
 in-kernel driver r8169. Please see the README.Debian for instructions how
 to report bugs against r8169 that made it necessary to use r8168-dkms.
 .
 Installation of the r8168-dkms package will disable the in-kernel r8169
 module. To re-enable r8169, the r8168-dkms package must be purged.
 .
 This package provides the dkms source code for the r8168 kernel modules.
 Kernel source or headers are required to compile these modules.


I guess I should have mentioned that but I was trying not to make a huge initial post.
Also like you said in your later rant things have gotten complicated in linux, especially networking stuff
and I'm not even sure whats being used for networking now and what isn't cause theres multiple network interfaces in /etc/
I was going to read this but I'm not even sure whats relevant anymore.
https://wiki.debian.org/NetworkConfiguration

I wish debain doc was like the arch-wiki.
bmickey
 
Posts: 15
Joined: 2018-01-20 20:42

Re: Realtek ethernet problems r8168-dkms and r8169

Postby bmickey » 2018-10-31 19:07

Thank you guys for the suggestions I will look more into the recommendations and the problem and get back to you.
bmickey
 
Posts: 15
Joined: 2018-01-20 20:42

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Segfault » 2018-10-31 21:15

I did run ethtool and there was no connection.

No connection means bad cable, bad ethernet port or bad NIC itself.
Segfault
 
Posts: 808
Joined: 2005-09-24 12:24

Re: Realtek ethernet problems r8168-dkms and r8169

Postby stevepusser » 2018-10-31 22:20

Rephrasing my question in a different way, maybe will get an answer this time: :?:

What do you get with the output of (as sysadmin)

Code: Select all
dmesg | grep firmware
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, tlp-ui, wine-staging 3.21, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10250
Joined: 2009-10-06 05:53

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Segfault » 2018-10-31 22:24

r8169 kernel driver is functional without firmware, loading firmware only adds some power saving feature if I recall correctly. I's say firmware (or lack thereof) is not the problem here.
Segfault
 
Posts: 808
Joined: 2005-09-24 12:24

Re: Realtek ethernet problems r8168-dkms and r8169

Postby bmickey » 2018-11-06 20:15

Hey so, I'm sorry I posted this thread and haven't been able to do any checking of the Ethernet stuff. I have to write a kernel module for school so I haven't been home and honestly I have no idea what I'm doing. I'm working on a VM though so I'm not messing with my own computer.

I only use wifi at school so I can't check any of the stuff.
However as of the past few days my wifi has been behaving similarly to my Ethernet so I'm beginning to suspect this has nothing to do with Realtek.

Head_on_a_Stick wrote:
Segfault wrote:You put your nameservers into resolv.conf and they stayed there until you changed your mind.

For systemd-networkd & systemd-resolved a static resolv.conf will not be touched:
systemd-resolved(8) wrote:Alternatively, /etc/resolv.conf may be managed by other packages, in which case systemd-resolved will read it for DNS configuration data. In this mode of operation systemd-resolved is consumer rather than provider of this configuration file.

@OP: sounds like a power saving issue, please post the output of
Code: Select all
/sbin/iwconfig

If the command can't be found then install the wireless-tools package.


Here's my iwconfig output before I lost internet connection.
Code: Select all
/sbin/iwconfig
enp59s0   no wireless extensions.

wlp60s0   IEEE 802.11  ESSID:"RUWireless Secure" 
          Mode:Managed  Frequency:5.26 GHz  Access Point: F4:CF:E2:AC:9F:BC   
          Bit Rate=173.3 Mb/s   Tx-Power=11 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=57/70  Signal level=-53 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:3   Missed beacon:0

lo        no wireless extensions.


You can see that power management is enabled like suggested.

Here is the output after I lost internet.
Code: Select all
/sbin/iwconfig
wlp60s0   IEEE 802.11  ESSID:"RUWireless Secure" 
          Mode:Managed  Frequency:5.26 GHz  Access Point: F4:CF:E2:AC:9F:BC   
          Bit Rate=173.3 Mb/s   Tx-Power=11 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=59/70  Signal level=-51 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:3  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

enp59s0   no wireless extensions.


Heres the output from dmesg and it says its limiting power,
Code: Select all
dmesg | egrep -i 'wlp60s0'
[    2.611431] iwlwifi 0000:3c:00.0 wlp60s0: renamed from wlan0
[    3.402301] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
[    3.572846] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
[    3.759277] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
[    3.839850] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
[    7.214599] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
[    7.267151] wlp60s0: authenticate with f4:cf:e2:ac:9f:bc
[    7.278468] wlp60s0: send auth to f4:cf:e2:ac:9f:bc (try 1/3)
[    7.283082] wlp60s0: authenticated
[    7.284842] wlp60s0: associate with f4:cf:e2:ac:9f:bc (try 1/3)
[    7.286523] wlp60s0: RX AssocResp from f4:cf:e2:ac:9f:bc (capab=0x111 status=0 aid=16)
[    7.288247] wlp60s0: associated
[    7.345828] wlp60s0: Limiting TX power to 11 dBm as advertised by f4:cf:e2:ac:9f:bc
[    7.497633] IPv6: ADDRCONF(NETDEV_CHANGE): wlp60s0: link becomes ready




Regarding the firmware...
stevepusser wrote:Rephrasing my question in a different way, maybe will get an answer this time: :?:

What do you get with the output of (as sysadmin)

Code: Select all
dmesg | grep firmware



Code: Select all
dmesg | grep firmware
[    0.037123] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    2.381580] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.385162] iwlwifi 0000:3c:00.0: firmware: failed to load iwlwifi-8265-26.ucode (-2)
[    2.385166] iwlwifi 0000:3c:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
[    2.385175] iwlwifi 0000:3c:00.0: firmware: failed to load iwlwifi-8265-25.ucode (-2)
[    2.385178] iwlwifi 0000:3c:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2
[    2.385185] iwlwifi 0000:3c:00.0: firmware: failed to load iwlwifi-8265-24.ucode (-2)
[    2.385189] iwlwifi 0000:3c:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
[    2.385196] iwlwifi 0000:3c:00.0: firmware: failed to load iwlwifi-8265-23.ucode (-2)
[    2.385198] iwlwifi 0000:3c:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2
[    2.388830] bluetooth hci0: firmware: direct-loading firmware intel/ibt-12-16.sfi
[    2.388833] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[    2.391382] iwlwifi 0000:3c:00.0: firmware: direct-loading firmware iwlwifi-8265-22.ucode
[    2.391826] iwlwifi 0000:3c:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[    2.394436] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_01.bin
[    2.412680] [drm] GuC firmware load skipped
[    3.348870] r8169 0000:3b:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw
[    3.863186] Bluetooth: hci0: Waiting for firmware download to complete
[    3.875887] bluetooth hci0: firmware: direct-loading firmware intel/ibt-12-16.ddc                                                                                   


The wifi has been doing the same thing it will work when I boot up then probably like after 2 minutes my internet connection is gone.
Then I do
Code: Select all
systemctl restart NetworkManager

and it works after that.
This problem never happened with ethernet or wifi until about a month ago and I never turned power management on nor do I know how to even do that.
bmickey
 
Posts: 15
Joined: 2018-01-20 20:42

Re: Realtek ethernet problems r8168-dkms and r8169

Postby stevepusser » 2018-11-06 20:30

The usual suggestion is to turn power management off if you have random disconnects, since that's usually on by default. That's done by specifying the parameter in a [modulename].conf file someplace in /etc...a little googling will show you where. The exact parameter syntax is usually displayed in the output of

Code: Select all
modinfo [modulename]
as sysadmin

but I don't see any power saving params for the r8169 module.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, tlp-ui, wine-staging 3.21, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10250
Joined: 2009-10-06 05:53

Re: Realtek ethernet problems r8168-dkms and r8169

Postby Head_on_a_Stick » 2018-11-06 20:47

Disable the power management with
Code: Select all
/sbin/iw dev wlp60s0 set power_save off

Make the change permanent with a udev rule:
Code: Select all
# /etc/udev/rules.d/70-wifi-powersave.rules
ACTION=="add", SUBSYSTEM=="net", KERNEL=="wlp60s0", RUN+="/sbin/iw dev %k set power_save off"
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8315
Joined: 2014-06-01 17:46
Location: /dev/chair

Next

Return to System configuration

Who is online

Users browsing this forum: No registered users and 1 guest

fashionable