[07:02] <lotuspsychje> tjaalton: think this commit could be related to the flickering bug? https://bbs.archlinux.org/viewtopic.php?id=244115
[09:05] <tjaalton> lotuspsychje: so if you blacklist that module, do you get the same issue on 4.18?
[09:06] <lotuspsychje> tjaalton: 4.18 works without flickering, should i try a blacklist on 5.0.0.25?
[09:07] <tjaalton> lotuspsychje: my point was does 4.18 regress
[09:07] <tjaalton> 5.3 has 62b1b3b3b6d3ef3
[09:07] <tjaalton> 62b1b3b3b6d3ef3 r8169: don't activate ASPM in chip if OS can't control ASPM
[09:07] <tjaalton> maybe that "fixed" it for you
[09:08] <lotuspsychje> or on 4.19 it also flickers, i could try a blacklist there?
[09:08] <tjaalton> that commit was added in 4.20
[09:08] <lotuspsychje> tjaalton: so that doesnt prove why 5.0 doesnt work?
[09:09] <tjaalton> maybe not
[09:11] <lotuspsychje> i could try blacklisting it on 4.19 and 5.0 ill see what happens ok cant harm to try
[09:12] <tjaalton> and you have that hw?
[09:12] <lotuspsychje> yes
[09:12] <tjaalton> as in, is the module loaded now
[09:12] <tjaalton> ok
[09:12] <lotuspsychje> whats command again for modules
[09:12] <tjaalton> lsmod
[09:13] <lotuspsychje> description: Wireless interface
[09:13] <lotuspsychje>        product: Wireless-AC 9260
[09:14] <lotuspsychje> iwlwifi
[09:14] <tjaalton> there you go
[09:15] <lotuspsychje> ill test it a bit later, ill ping you after ok
[09:15] <tjaalton> lsmod|grep r8169
[09:15] <tjaalton> r8169 is ethernet, not wireless
[09:39] <lotuspsychje> tjaalton: so this is another bug then?
[09:40] <lotuspsychje> lotuspsychje@Rootbox:~$ lsmod|grep r8169
[09:40] <lotuspsychje> r8169                  81920  0
[10:33] <tjaalton> loaded but not used, lspci -k should show if you have the hw
[10:33] <tjaalton> though having it loaded usually means that..
[10:45] <jeremy31> Is the used by result accurate?  I am using USB wifi and I see ath9k_htc              77824  0
[11:07] <tjaalton> ah, it shows how many modules use it..