Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #224692
| From | Klaus Jantzen <k.d.jantzen@mailbox.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Buster boot messages |
| Date | 2020-07-10 19:30 +0200 |
| Message-ID | <Ar50t-2MA-7@gated-at.bofh.it> (permalink) |
| References | <AqW6R-5Fa-1@gated-at.bofh.it> <AqXPj-6Jo-1@gated-at.bofh.it> <Ar1Jg-FJ-17@gated-at.bofh.it> <Ar22B-11N-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 7/10/20 4:14 PM, Sven Hartge wrote: > Klaus Jantzen <k.d.jantzen@mailbox.org> wrote: >> On 7/10/20 11:48 AM, Sven Hartge wrote: >>> Klaus Jantzen <k.d.jantzen@mailbox.org> wrote: >>>> the first messages that appear on the screen during the boot process >>>> seem to be messages from the BIOS; >>>> they have a different format than the subsequent messages from buster >>>> and they begin with 'ACPI '. >>>> As they disappear so fast, I cannot read them. >>>> Where are these messages logged or what should I do to log these messages? >>> "journalctl -b" will have the messages from the most recent boot. >> Thanks for the pointer. >> These are the messages I was looking for: >> ========= >> AMD-Vi: Unable to write to IOMMU perf counter. >> ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (201810/psargs-330) >> ACPI Error: Method parse/execution failed \_SB.PCI0.GPP0.VGA.LCD._BCM, AE_NOT_FOUND (20180810/psparse-516) >> ACPI Error: Evaluating _BCM failed (20180810/video-370) >> Failed to start Show Plymouth Boot Screen. >> ====== >> Do I have a problem with my system? > No. The ACPI tables in PCs are usually shoddy and produce many warnings > by the strict parser in the Kernel. > > Windows also often experiences the same parse errors, but decides to > hide them deep in the Event Log. > > Both operations system work around the these errors, anticipating the > bad craftsmanship of the mainboard/system manufacturers. > > Unless you have very specific problems which you explicitly can link to > such errors, I would not worry. > > Sometimes a BIOS/Firmware update fixes some errors, but don't get your > hopes up. > > Grüße > Sven. > Thank you. That was helpful. -- K.D.J.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Buster boot messages Klaus Jantzen <k.d.jantzen@mailbox.org> - 2020-07-10 10:00 +0200
Re: Buster boot messages Zoltán Herman <zoltanhbz@gmail.com> - 2020-07-10 10:00 +0200
Re: Buster boot messages Sven Hartge <sven@svenhartge.de> - 2020-07-10 11:50 +0200
Re: Buster boot messages Klaus Jantzen <k.d.jantzen@mailbox.org> - 2020-07-10 16:00 +0200
Re: Buster boot messages Sven Hartge <sven@svenhartge.de> - 2020-07-10 16:20 +0200
Re: Buster boot messages Klaus Jantzen <k.d.jantzen@mailbox.org> - 2020-07-10 19:30 +0200
Re: Buster boot messages Brian <ad44@cityscape.co.uk> - 2020-07-10 12:00 +0200
csiph-web