Technical issues/questions of an intermediate or advanced nature.
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#1
by Ed_P » 20 Apr 2024, 05:27
Code: Select all
guest@porteus:~$ dmesg
dmesg: read kernel buffer failed: Operation not permitted
guest@porteus:~$

What does that mean?

Why am I getting it?
Code: Select all
~# uname -a
Linux porteus.example.net 6.6.20-porteus #1 SMP PREEMPT_DYNAMIC Tue Mar 5 20:06:09 MSK 2024 x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux
~# cat /etc/porteus/*
001-core.xzm:20240301
002-xorg.xzm:20240301
002-xtra.xzm:20240301
003-cinnamon.xzm:20231229
initrd.xz:20230923
~# ls -l /mnt/live/memory/images
000-kernel.xzm : Mar 5 12:26
001-core.xzm : Mar 1 06:24
002-xorg.xzm : Mar 1 06:29
002-xtra.xzm : Mar 1 06:34
003-cinnamon.xzm : Dec 29 00:05
07-printing-x86_64-2023-02-04.xzm : Feb 4 2023
Dell6.4.10-wifi.xzm : Aug 18 2023
Dellsound.xzm : May 14 2022
changes : Apr 19 21:17
firefox-122.0-x86_64-en-US.xzm : Jan 27 23:51
wmctrl-1.07-x86_64-2salix15.0.xzm : Feb 6 11:54
ISO: /ISOs/Porteus/Porteus-CINNAMON-v5.01-x86_64.iso
Ed_P
-
Blaze
- DEV Team

- Posts: 3996
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
-
Contact:
Post#2
by Blaze » 20 Apr 2024, 05:49
Run dmesg as root user
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#3
by Ed_P » 20 Apr 2024, 06:37
Oh, Wow!!

I thought the error was what I saw flashing by when I booted. Did not connect it to dmesg itself.
Thank you
Blaze.
Ed_P
-
i3slkiller
- Contributor

- Posts: 129
- Joined: 03 Feb 2020, 18:51
- Distribution: Debian 12, Porteus 5.01
- Location: Poland
Post#4
by i3slkiller » 20 Apr 2024, 18:20
You can also do this:
Code: Select all
sudo sysctl -w kernel.dmesg_restrict=0
then root is not required for dmesg
i3slkiller
-
Ed_P
- Contributor

- Posts: 8908
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Post#5
by Ed_P » 21 Apr 2024, 05:21
i3slkiller wrote: ↑20 Apr 2024, 18:20
Code: Select all
sudo sysctl -w kernel.dmesg_restrict=0
then root is not required for dmesg
Code: Select all
guest@porteus:~$ sudo sysctl -w kernel.dmesg_restrict=0
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
For security reasons, the password you type will not be visible.
Password:
kernel.dmesg_restrict = 0
guest@porteus:~$ dmesg
[ 0.000000] Linux version 6.6.13-porteus ([email protected]) (gcc (GCC) 13.2.0, GNU ld version 2.41-slack151) #1 SMP PREEMPT_DYNAMIC Mon Jan 22 18:56:22 AEST 2024
[ 0.000000] Command line: BOOT_IMAGE=(loop)/boot/syslinux/vmlinuz from=/ISOs/Porteus/Porteus-CINNAMON-v5.1-x86_64.iso volume=33 reboot=cold extramod=/porteus5.0/Modules noload=kde;jinn;lxqt;xfce;lxde;mate;open;dat.xzm;menu2
[ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
[ 0.000000] BIOS-provided physical RAM map:
:
:
:

Definitely effective.
Thanks
i3slkiller.
Ed_P