After switching to latest linux-hardened, problem with running powertop

I just switched to linux-hardened installed via akm and I am having trouble with powertop:

sudo powertop 
modprobe cpufreq_stats failedFailed to mount debugfs!
exiting...
sudo modprobe cpufreq_stats
modprobe: FATAL: Module cpufreq_stats not found in directory /lib/modules/5.9.14.a-1-hardenedx86?64 GNU&Linux
uname -a
Linux eos-cinnamon 5.9.14.a-1-hardened #1 SMP PREEMPT Sat, 12 Dec 2020 18:25:31 +0000 x86_64 GNU/Linux
inxi -Fxxxz

System: Kernel: 5.9.14.a-1-hardened x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: Cinnamon 4.8.2 tk: GTK 3.24.24
info: plank wm: muffin dm: LightDM 1.30.0 Distro: EndeavourOS
Machine: Type: Laptop System: LENOVO product: 82A2 v: Yoga Slim 7 14ARE05 serial: Chassis: type: 10
v: Yoga Slim 7 14ARE05 serial:
Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN �������������������������������� serial: UEFI: LENOVO
v: DMCN34WW date: 08/17/2020
Battery: ID-1: BAT1 charge: 32.3 Wh condition: 60.5/60.7 Wh (100%) volts: 15.6/15.4 model: Sunwoda L19D4PF4 type: Li-poly
serial: status: Discharging cycles: 60
CPU: Info: 8-Core model: AMD Ryzen 7 4800U with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 57504
Speed: 1397 MHz min/max: 1400/1800 MHz boost: disabled Core speeds (MHz): 1: 1397 2: 1397 3: 1397 4: 1397 5: 1397
6: 1396 7: 1397 8: 1397 9: 1397 10: 1397 11: 1397 12: 1396 13: 1397 14: 1396 15: 1397 16: 1397
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 03:00.0
chip ID: 1002:1636
Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 1-4:4 chip ID: 04f2:b6cb serial:
Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
s-dpi: 96
OpenGL: renderer: AMD RENOIR (DRM 3.39.0 5.9.14.a-1-hardened LLVM 11.0.0) v: 4.6 Mesa 20.3.0 direct render: Yes
Audio: Device-1: Advanced Micro Devices [AMD/ATI] vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 03:00.1
chip ID: 1002:1637
Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Lenovo
driver: snd_rn_pci_acp3x v: kernel bus ID: 03:00.5 chip ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 03:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.9.14.a-1-hardened
Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 01:00.0 chip ID: 8086:2723
IF: wlan0 state: up mac:
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 983.68 GiB used: 59.80 GiB (6.1%)
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFS001TD9TNG-L3A0B size: 953.87 GiB speed: 31.6 Gb/s lanes: 4
serial: rev: 80050C10 scheme: GPT
ID-2: /dev/sda type: USB vendor: Generic model: MassStorageClass size: 29.81 GiB serial: rev: 2402
scheme: GPT
Partition: ID-1: / size: 50.00 GiB used: 17.87 GiB (35.7%) fs: btrfs dev: /dev/nvme0n1p4
ID-2: /home size: 50.00 GiB used: 17.87 GiB (35.7%) fs: btrfs dev: /dev/nvme0n1p4
Swap: ID-1: swap-1 type: partition size: 10.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p10
ID-2: swap-2 type: zram size: 512.0 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors: System Temperatures: cpu: 32.9 C mobo: N/A gpu: amdgpu temp: 32.0 C
Fan Speeds (RPM): N/A
Info: Processes: 408 Uptime: 2h 02m wakeups: 1697 Memory: 15.08 GiB used: 4.70 GiB (31.2%) Init: systemd v: 247
Compilers: gcc: 10.2.0 Packages: pacman: 1036 Shell: Bash v: 5.1.0 running in: gnome-terminal inxi: 3.1.09

Please tell me if I need to provide more info.
I would appreciate to get any help to resolve this.

Have you installed the headers as well?

1 Like

Yes, I have. I installed both the kerne and the headers using akm:

Then I assume it has something to do with Restricting module loading, see here:

1 Like

Right. I took a look at that before but I couldn’t know for sure if this particular module was not included. I was at the Github page as well but frankly that is way above my head.

1 Like

I found this:

Could this be “incorporated” somehow into the kernel without breaking the whole thing?

I’m guessing, as linux-hardened (in stable repos) is newer than linux, that could cause issues?
If you convert pacman.conf to use all testing repos, does it still cause trouble?

Would that mean that I need to upgrade all the packages to the versions in testing?

Don’t.
I just tested it and it didn’t help…

1 Like

Thanks!
I was about to!
:relieved:

1 Like

I am actually running also testing repos, and for a long time they have been without problems. But admittedly they are slightly more prone to problems than stable repos.

1 Like

I thought to make a snapshot of the system and switch over but since you have already tested and the issue persists with the hardened perhaps I won’t do this for now.

I am beginning to think that the failed module might have to do with the “Restricting module loading” that was mentioned above by Leon.

1 Like

Switching back to linux, powertop runs normally.

Another thing, while in hardened, I tried to add my user to wireshark group but I couldn’t. I got something like the following: ncdu didn’t terminate correctly: signal [11]

Back in linux, no problem adding my user to this group.

Are you part of the Testing team too? If not, join it, then you can help Sign Off packages that work. :wink:

Are there any admission conditions?
Not that I am technically apt to do so, but I’ve got a machine I could dedicate to this. Just for fun and if it could be of any help, then even much better.

Not really, just a general ability to spot broken things:

More testers is always better. :wink:

1 Like

General ability to breaking things! That’s me!
:sweat_smile:

1 Like

No, I’m using testing repo mostly to see what’s coming, and if there are any problems ahead. I also try to actually use the testing repos to be at the bleeding edge…

But thanks for the suggestion, I’ll look into it. :smile:

4 Likes

In order to switch to Testing repo, do I need to just un-comment those related entries in pacman.conf? Or I need to comment out those related to the “Stable” as well? Extra and multilib included?

:drop_of_blood: :hocho:

Simply uncomment those testing repos. As they are written before the stable repos in pacman.conf, they ”override” the stable repos. Note that stable repos should not be commented out.

1 Like