Stardust-kyun
commented
3 years ago Found a solution to both- changed the network interface to wlp4s0 and changed the battery to BAT0.
I got the battery solution by running ls -1 /sys/class/power_supply/, which outputs
AC BAT0 hidpp_battery_0
The config file used BAT1, so I assumed that changing it to BAT0 would work, which it did.
I got the network solution by running ip a, which output
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 68:f7:28:d9:90:f1 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 10:4a:7d:a0:e0:60 brd ff:ff:ff:ff:ff:ff inet 10.0.1.127/24 brd 10.0.1.255 scope global dynamic noprefixroute wlp4s0 valid_lft 84468sec preferred_lft 84468sec inet6 2601:242:c002:3610:31d5:a32f:bc2f:1145/64 scope global dynamic noprefixroute valid_lft 345589sec preferred_lft 345589sec inet6 fe80::335b:324b:7820:805e/64 scope link noprefixroute valid_lft forever preferred_lft forever
I noticed that it had wlp4s0 in it, and when changing wlp3s0 to wlp4s0, it fixed.
I've been having some errors with polybar 9's modules, specifically the network and battery modules. These are the errors that show when launched:
error: Disabling module "network" (reason: Invalid network interface "wlp3s0")error: Disabling module "battery" (reason: No suitable way to get current charge state)Because of this, neither modules appear. Any help would be appreciated.