It used to be that the dmesg were written to the log file
/var/log/dmesg.log. However in Mageia 8 this seems to have disappeared.
How can I get it back?
It used to be that the dmesg were written to the log file
/var/log/dmesg.log. However in Mageia 8 this seems to have disappeared.
How can I get it back?
On Wed, 04 May 2022 13:41:42 -0400, William Unruh <unruh@invalid.ca> wrote:
It used to be that the dmesg were written to the log file
/var/log/dmesg.log. However in Mageia 8 this seems to have disappeared.
How can I get it back?
It was dropped with the switch to systemd. It was used to capture as much of the
boot log as could be captured before rsyslog started. As there was no way to feed
those messages to the syslog daemon, they were kept in a separate file.
With systemd and it's journal, those messages (and more that were previously being
lost at boot) are all included in the journal. You can still use the dmesg command
to see those messages using a timestamp instead of date/time.
Hm, /var/log/dmesg was still there even after syslogd was implimented.
The problem with the journal is that some of the dmesg messages seem to
not be there if one for example does journalctl -k which is claimed in
some places to be the equivalent of dmesg.
dmesg -T will also produce a date/time which is definitely more useful
than "seconds since 1970"
Hm, /var/log/dmesg was still there even after syslogd was implimented.
The problem with the journal is that some of the dmesg messages seem to
not be there if one for example does journalctl -k which is claimed in
some places to be the equivalent of dmesg.
On Wed, 4 May 2022 21:30:10 -0000 (UTC), William Unruh wrote:
Hm, /var/log/dmesg was still there even after syslogd was implimented.
On Wed, 04 May 2022 20:20:12 -0400, Bit Twister <BitTwister@mouse-potato.com> wrote:
On Wed, 4 May 2022 21:30:10 -0000 (UTC), William Unruh wrote:
Hm, /var/log/dmesg was still there even after syslogd was implimented.
Now I'm more confused. I was looking to see where it was being created, to figure out exactly when it was dropped. It wasn't dropped.
/lib/systemd/system/mandriva-save-dmesg.service still exists and is enabled.
Running "systemctl start mandriva-save-dmesg.service" causes the file to
get updated.
I don't know why it isn't being run automatically. I'll ask around and open
a bug report, if it's not intentional.
# systemctl status mandriva-save-dmesg.service
● mandriva-save-dmesg.service - Save boot dmesg content
Loaded: loaded (/usr/lib/systemd/system/mandriva-save-dmesg.service; enabled; vendor preset: enabled)
Active: inactive (dead)
journalctl | grep save-dmesg
May 01 05:40:01 drakscanner[659325]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 01 05:40:08 drakscanner[659325]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 04 20:16:13 drakscanner[705679]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 04 20:16:19 drakscanner[705679]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
~]$ systemctl status mandriva-save-dmesg.service
● mandriva-save-dmesg.service - Save boot dmesg content
Loaded: loaded
(/usr/lib/systemd/system/mandriva-save-dmesg.service; enabled; vendor pres>
Active: inactive (dead)
[faeychild@unimatrix ~]$ journalctl | grep save-dmesg
I got a long pause here (4-5) seconds before the prompt returned with nothing
On 5/5/22 13:06, Bit Twister wrote:
# systemctl status mandriva-save-dmesg.service
● mandriva-save-dmesg.service - Save boot dmesg content
Loaded: loaded (/usr/lib/systemd/system/mandriva-save-dmesg.service; enabled; vendor preset: enabled)
Active: inactive (dead)
journalctl | grep save-dmesg
May 01 05:40:01 drakscanner[659325]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 01 05:40:08 drakscanner[659325]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 04 20:16:13 drakscanner[705679]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
May 04 20:16:19 drakscanner[705679]: running: /bin/systemctl --quiet is-enabled mandriva-save-dmesg.service
~]$ systemctl status mandriva-save-dmesg.service
● mandriva-save-dmesg.service - Save boot dmesg content
Loaded: loaded
(/usr/lib/systemd/system/mandriva-save-dmesg.service; enabled; vendor pres>
Active: inactive (dead)
[faeychild@unimatrix ~]$ journalctl | grep save-dmesg
I got a long pause here (4-5) seconds before the prompt returned with nothing
[faeychild@unimatrix ~]$
On Wed, 4 May 2022 21:30:10 -0000 (UTC), William Unruh wrote:
Hm, /var/log/dmesg was still there even after syslogd was implimented.
I am going to guess some systemd update did away /var/log/dmesg .
Clean mga8 install.
# cat /var/log/dmesg
cat: /var/log/dmesg: No such file or directory
I remember is was there because I had opened a mga7 bug report about its contents
did not show up in the journal.
The problem with the journal is that some of the dmesg messages seem to
not be there if one for example does journalctl -k which is claimed in
some places to be the equivalent of dmesg.
Looking pretty close to me.
$ journalctl -k
-- Logs begin at Fri 2022-04-29 06:33:13 CDT, end at Wed 2022-05-04 19:02:05 CD>
May 03 02:36:37 wb.home.test kernel: Linux version 5.15.35-desktop-2.mga8 (iurt>
May 03 02:36:37 wb.home.test kernel: Command line: BOOT_IMAGE=/boot/vmlinuz roo>
May 03 02:36:37 wb.home.test kernel: x86/fpu: x87 FPU will use FXSAVE
May 03 02:36:37 wb.home.test kernel: signal: max sigframe size: 1440
May 03 02:36:37 wb.home.test kernel: BIOS-provided physical RAM map:
May 03 02:36:37 wb.home.test kernel: BIOS-e820: [mem 0x0000000000000000-0x00000>
need a little less noise
$ journalctl -k --no-hostname
-- Logs begin at Fri 2022-04-29 06:33:13 CDT, end at Wed 2022-05-04 19:02:05 CD>
May 03 02:36:37 kernel: Linux version 5.15.35-desktop-2.mga8 (iurt@ecosse.magei>
May 03 02:36:37 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz root=LABEL=mga8 >
May 03 02:36:37 kernel: x86/fpu: x87 FPU will use FXSAVE
May 03 02:36:37 kernel: signal: max sigframe size: 1440
May 03 02:36:37 kernel: BIOS-provided physical RAM map:
May 03 02:36:37 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000098bff] >
Note to lurkers, if you are in the systemd-journal group you do not have
to get to a root prompt to view the system jounal.
It used to be that the dmesg were written to the log file
/var/log/dmesg.log. However in Mageia 8 this seems to have disappeared.
How can I get it back?
In my case I was looking at the debugging of wpa_supplicant and a number
of dmesg messages came from the wireless card number. They were not in journalctl -k, which I think just give you the kernel messages,
and dmesg has more than just kernel messages.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 53:52:28 |
Calls: | 6,712 |
Files: | 12,243 |
Messages: | 5,355,274 |