), but in fact everything works perfectly.
вс, 27 дек. 2020 г. в 04:48, Rainer Dorsch :
>
> Hi,
>
> I have a Tuxedo Aura 15 and after installing Debian bullseye, I see during
> boot a few
>
> acpi bios error: could not resolve symbol
>
> messages.
>
> See ht
Hi,
I have a Tuxedo Aura 15 and after installing Debian bullseye, I see during
boot a few
acpi bios error: could not resolve symbol
messages.
See https://nc.d5x.de/s/3BYL8Fg88Xb5GRJ for a "screenshot".
Does anybody understand what these messages want to tell me (so far I di
fwupd is worth noting: https://en.wikipedia.org/wiki/Fwupd
and not only does it manage PC firmwares (UEFI) but peripheral cards
firmwares too
but it is far from widely adopted :-(
On Sb, 28 mar 20, 14:40:54, G.W. Haywood wrote:
>
> Perhaps you should read
>
> https://www.debian.org/doc/manuals/debian-faq/choosing.en.html#s3.1
>
> but do please note that this document is out of date - it refers to
> "Stretch" as the stable distribution, instead of "Buster", which has
>
Hi there,
On Sat, 28 Mar 2020, rba777 wrote:
...
[ 0.457794] ACPI BIOS Error (bug): Failure creating named object
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
...
Using apt and apt
Jude DaShiell wrote:
>
> Does any Linux app exist to let systems know when bios updates become
> available for the bios running on those systems?
No. It would require a mechanism supported by each manufacturer,
and they tend not to even be consistent on their own websites.
Server manufacturers
On Sat, 28 Mar 2020, Darac Marjal wrote:
> Date: Sat, 28 Mar 2020 06:55:55
> From: Darac Marjal
> To: debian-user@lists.debian.org
> Subject: Re: Question regarding an ACPI BIOS Error (bug)
>
>
> On 28/03/2020 09:35, rba...@protonmail.ch wrote:
> > Hi all, I've been re
I: Added _OSI(Linux-HPI-Hybrid-Graphics)
These aren't errors; these ones are just informative.
> [ 0.457794] ACPI BIOS Error (bug): Failure creating named object
> [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
> [ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name
] ACPI BIOS Error (bug): Failure creating named object
[\_GPE._E47], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457811] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
[ 0.457813] ACPI: Skipping parse of AML opcode: OpcodeName unavailable
(0x0014
Le 07-12-2018, à 17:34:20 -0500, Tyler McLean a écrit :
Having this same exact series of error messages on boot and the first time
i press a key after boot. fresh debian install, latest BIOS. super
annoying. did you ever resolve this?
No, I guess it's a firmware bug, so only chance is
Having this same exact series of error messages on boot and the first time
i press a key after boot. fresh debian install, latest BIOS. super
annoying. did you ever resolve this?
Le 24-09-2018, à 09:36:48 +0200, deloptes a écrit :
steve wrote:
I disable some ACPI settings in the BIOS and it reduced the waiting
time.
don't know someone has to debug it - might be something is reported on ACPI
that exists, but service can not be started. I would look forward to enable
steve wrote:
> I disable some ACPI settings in the BIOS and it reduced the waiting
> time.
don't know someone has to debug it - might be something is reported on ACPI
that exists, but service can not be started. I would look forward to enable
more logging in this context - might be kernel
Le 24-09-2018, à 08:12:37 +0200, deloptes a écrit :
steve wrote:
Machine stop 15 seconds during boot, then goes on.
This does not mean that it stops for that reason.
I disable some ACPI settings in the BIOS and it reduced the waiting
time.
Are you using systemd?
Yes.
I recall
steve wrote:
> Machine stop 15 seconds during boot, then goes on.
This does not mean that it stops for that reason. Are you using systemd? I
recall systemd waiting for something to start or complete.
It might be this or something else. IMO those BIOS related messages are
harmless
regards
Le 23-09-2018, à 15:20:40 +0200, deloptes a écrit :
steve wrote:
Yes I have.
in such a case you can try to track it via bug request, although some of
those are bois/firmware related and mostly not harmful.
Or the harm is very subtle and I don't see it.
do you have error description,
steve wrote:
> Yes I have.
in such a case you can try to track it via bug request, although some of
those are bois/firmware related and mostly not harmful.
do you have error description, because if it is a bug, it should be visible
some how.
Le 22-09-2018, à 20:23:28 +0200, deloptes a écrit :
steve wrote:
Should I open a ticket in the BTS?
you have latest BIOS installed?
Yes I have.
steve wrote:
> Should I open a ticket in the BTS?
you have latest BIOS installed?
Hi,
Almost sure nobody will have a solution, but for the sake of it, I'll
document it here.
dmesg | grep -i error
[0.004000] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all
errors
[0.196456] ACPI BIOS Error (bug): Failure creating [\_SB.INTS],
AE_ALREADY_EXISTS
20 matches
Mail list logo
