Ideas about?: Unknown kernel command line params

I like to watch the boot-up sequence, so I tap ESC key so I can watch the messages.
I noticed a “unknown” message, but it scrolled by a little too quick, so captured a “dmesg > d.txt” after KDE Plasma login. I only found one occurrence of “unknown”, but I don’t think this is related to what I saw scrolling away.
( EDIT:::: this is what I was looking for (I rebooted since posting):
dmesg: unknown level ‘warning’)

Anyway, I think this one needs to be fixed: here’s a snippet from dmesg.txt file …
.
Any thoughts about the error below would be great … all seems to be working fine, so not sure what parameter is bad with the “BOOT_IMAGE+…” line.

[0.01] Built 1 zonelists, mobility grouping on.  Total pages: 16489154
[0.03] Policy zone: Normal
[0.04] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.3.9-1-default root=UUID=xxxxdffe-6f22-49b3-b556-999fxxxxxxxx splash=silent resume=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_500GB_xxxxxx0K730463Z-part4 quiet security=apparmor

[0.07] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-6.3.9-1-default splash=silent", will be passed to user space.

.
And this is after boot-up and login (KDE Plasma):

# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-6.3.9-1-default root=UUID=xxxxdffe-6f22-49b3-b556-999fxxxxxxxx 
 splash=silent   resume=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_500GB_xxxxxx0K730463Z-part4 
 quiet  security=apparmor

.
And here’s a partial file list (hopefully what I’m showing is important parts):

# ls -al /boot
total 180768
dr-xr-xr-x 1 root root     1246 Jun 25 20:33 .
drwxr-xr-x 1 root root      182 Mar 30  2022 ..
drwxr-xr-x 3 root root    16384 Dec 31  1969 efi
drwxr-xr-x 1 root root       98 Jun 25 20:33 grub2
lrwxrwxrwx 1 root root       22 Jun 25 20:25 initrd -> initrd-6.3.9-1-default
-rw------- 1 root root 46093756 Jul  4 18:09 initrd-6.2.10-1-default
-rw------- 1 root root 46227890 Jul  4 18:09 initrd-6.3.2-1-default
-rw------- 1 root root 46334315 Jul  4 18:09 initrd-6.3.7-1-default
-rw------- 1 root root 46330965 Jul  4 18:09 initrd-6.3.9-1-default

lrwxrwxrwx 1 root root       23 Jun 25 20:25 vmlinuz -> vmlinuz-6.3.9-1-default
lrwxrwxrwx 1 root root       43 Apr 14 22:32 vmlinuz-6.2.10-1-default -> ../usr/lib/modules/6.2.10-1-default/vmlinuz
lrwxrwxrwx 1 root root       42 May 18 20:54 vmlinuz-6.3.2-1-default -> ../usr/lib/modules/6.3.2-1-default/vmlinuz
lrwxrwxrwx 1 root root       42 Jun 16 22:15 vmlinuz-6.3.7-1-default -> ../usr/lib/modules/6.3.7-1-default/vmlinuz
lrwxrwxrwx 1 root root       42 Jun 25 20:25 vmlinuz-6.3.9-1-default -> ../usr/lib/modules/6.3.9-1-default/vmlinuz

Slightly hilarious…

I grepped my dmesg output to provide some contrast, maybe a hint to fix yours … but I have the EXACT same error message that you have …

I will check my other machines to see if they have the error or not. :+1:

1 Like

Everybody gets that message. It’s the kernel reporting cmdline parameters that it knows nothing about, which it is passing to userspace for handling. If you want the message gone, I’m not sure what can be done. My Grub stanzas have no BOOT_IMAGE= parameters, but the kernel finds them anyway.

2 Likes

( RESOLVED )
.
I just finished installing openSuse MicroOS. Specs below.
I am currently running this in a VirtualBox VM.
(I’m currently in it now, and typing this reply)

So far, so good. I will run it for a few days and see how it goes.
If all goes fine, I will replace my “native” Tumbleweed installs and replace with openSuse MicroOS KDE Plasma installs.
.
.
Okay, and so to stay on topic that I created … I checked this FRESH install (barely two hours old - installed just after downloading) …

I see the EXACT SAME kernel error on this FRESH install of MicroOS.
Yes, it IS hilarious :+1:

Thanks for the replies !!

Operating System: openSUSE MicroOS 20230704
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.9-1-default (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 3.8 GiB of RAM
Graphics Processor: llvmpipe
1 Like

Hmmm. So far, 2 machines out of four have it here. Is this related to something like: “when it was installed” that’s what was used?

Are all running openSUSE? Not all distros have it.

Yes, all TW, and run “dup” daily … never noticed this “error” until this post

This is a quit common notification on all linux distribution and no error.

2 Likes

from kernel GIT

wow … nice find … from two years ago … and Linus is committer and apparently signed off on it :slight_smile: