For the last few days, when I start my laptop, before I get to the actual login screen, I get a message, about 10 lines long, something about a missing packets.

It flashes by so fast, I can't really read it. Then I am at the login screen.

Where would such a message be logged?

I looked in sys.log, kern.log, boot.log, dmesg, but I can't see anything similar.

The laptop seems to be working OK.

You've looked at the places I would have suggested.

It could well be that this is nothing to worry about. At time of boot, the kernel probes for all sorts of stuff. It's not unusual for some items to return a not-found message.

It's a long shot, but you could try recording the boot process with a cellphone or other device, then reviewing the recording.

1 members found this post helpful.

Good idea, I'll do that! Thanks!

Please let us know what happens!

These 2 photos report a BIOS bug, I believe.

Like I said, this started a few days ago, not exactly sure when.

My laptop still works fine.

Is there anything I should/could do?

Attached Thumbnails

   

ACPI errors seldom signify anything. A lot of ACPI software is sloppily written and not according to the international ACPI standard. Windows doesn't mind that but the Linux kernel tends to get sniffy about it.

I also have ACPI errors, the computer boots and works without any problems. Another user reported similar errors and everything works okay.

On this thread. https://www.linuxquestions.org/quest...ic-4175711968/

Thanks for the advice everyone!

I looked up ACPI errors here

Trying to fix that is way beyond my abilities. And everything is working.

"If it ain't broke, don't fix it!" is a laudable maxim!

If everything else is working, I think that is the best choice.

Over the last 10-12 years - the first 4 or 5 especially, before settling down with Puppy - I don't think I've seen a single distro anywhere that will boot without the kernel complaining about something at boot.

i know very little about the kernel, beyond a layman's understanding of its basic operation - but I would imagine there must be some kind of error-detection threshold built-in. The kernel finds x, y or z isn't present, or initialized, or doing what it would LIKE to see.....but it allows boot to proceed anyway. Otherwise I rather suspect that no machine, anywhere, would ever be able to boot the thing.....


Mike.

Option -b

1 members found this post helpful.

Isn't that what the dmesg command does?

Not quite.
dmesg dislays the kernel messages where journalctl displays all system logged messages

1 members found this post helpful.

Some distros dump the kernel's message ring to a file called boot or similar as soon as booting is complete. This could be done with systemd distros too if klogd is set up to use journald's optional output socket. I suppose it depends on the developers.