On 2023-01-11 14:14, Andrei Borzenkov wrote:
I wonder when you are going to finally show dmesg output. You seriously believe that repeatedly posting "it does not work, it does not work" is going anywhere?
When I run dmesg and grep on the driver name, I get this for the Ethernet driver: E520:~ #dmesg|grep r8169 [ 8.191415] r81690000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 8.202975] libphy: r8169: probed [ 8.203572] r81690000:02:00.0 eth0: RTL8168e/8111e, f0:de:f1:8c:dc:99, XID 2c2, IRQ 27 [ 8.203579] r81690000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [ 10.956226] RTL8211DN Gigabit Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq= As you can see, there is info on it. However, when I try for WiFi: #dmesg|grep 8192 [ 0.036668] setup_percpu: NR_CPUS:8192nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 [ 0.038908] percpu: Embedded 63 pages/cpu s221184 r8192d28672 u262144 [ 0.038921] pcpu-alloc: s221184 r8192d28672 u262144 alloc=1*2097152 [ 0.141669] rcu: RCU restricting CPUs from NR_CPUS=8192to nr_cpu_ids=8. [ 0.827238] MPTCP token hash table entries: 8192(order: 5, 196608 bytes, linear) There doesn't appear to be anything related.