acpi

i repared acpi writing in /etc/default/grub at line GRUB_CMDLINE_LINUX_DEFAULT=libata.noacpi=1 and then write update-grub

acpi

i was able to repair the acpi drivers and i don’t get errors at startup

thermal acpi drivers

My laptop support pwm and starts the fans but when i start the system it gives me acpi errors that i put below [ 0.356880] ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20200925/exresop-66) [ 0.356951] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands

Fwd: acpi

-- Mensaje reenviado - De: Aleix Piulachs Fecha: El jue, 25 may 2023 a las 21:26 Asunto: Re: acpi Para: Alex these are the startup errors [0.356880] ACPI Error:Needed type [Reference], found [Integer] (___ptrval___) (20200925/exresop-66) [0.356951] ACPI Error

Re: acpi

On Thu, 25 May 2023 20:55:02 +0200 Aleix Piulachs wrote: > When i start the computer it gives me acpi errors What error specifically? -- Current PGP KeyID: 0AFB427F1800FD89751C4035292228735AE707FF https://blueselene.com/pgp-archive/0AFB427F1800FD89751C4035292228735AE707FF/key.

acpi

When i start the computer it gives me acpi errors

Re: acpi bios error: could not resolve symbol in Tuxedo Aura 15

), 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

acpi bios error: could not resolve symbol in Tuxedo Aura 15

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

Re: Obscure error messages from ACPI BERT in dmesg

Hi, Semih Ozlem wrote: > whenever I logon and have more than a few pages in > firefox open, suddenly my memory usage (memory is 3.7 GiB as displayed by > ubuntu system monitor) is around 70 and 80 percent. If I open a few more > pages it jumps. If it reaches 100 % the computer freezes. Well,

Obscure error messages from ACPI BERT in dmesg

Hi, i don't get to cursing at vim and sshd of Debian 10 because i am still stuck with hardware issues. My newest problem is a message at boot time about some problem that was recorded in the ACPI Boot Error Record Table during the previous uptime. Google and uefi.org tell me that BERT

Re: ACPI Errors

Well that's unfortunate, thanks for the information though. Regards, Jonathan ‐‐‐ Original Message ‐‐‐ On Monday, May 11, 2020 1:54 AM, Sven Hartge wrote: > Jonathan Oshita jkosh...@protonmail.com wrote: > > > I've been having the following error messages about

Re: ACPI Errors

Jonathan Oshita wrote: > I've been having the following error messages about 'ACPI' in my > 'kern.log' and haven't been able to figure out how to resolve them. > The system boots successfully after displaying the errors, but any > error message is usually a concern of mine. ACPI er

ACPI Errors

Hello, I've been having the following error messages about 'ACPI' in my 'kern.log' and haven't been able to figure out how to resolve them. The system boots successfully after displaying the errors, but any error message is usually a concern of mine. Is this something I should be worried

Erreur ACPI avec une radeon sur un PC Intel

soud aussi le problème de la même manière) Après lecture des logs il semble qu'il y ait des erreurs ACPI lors de du chargement ou du déchargement du driver de la carte graphique additionnelle AMD : $ modprobe -r radeon ... [  134.810044] ACPI Error: Aborting method \AMD3._ON due to previous

Re: Question regarding an ACPI BIOS Error (bug)

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 :-(

Re: Question regarding an ACPI BIOS Error (bug)

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 >

Re: Question regarding an ACPI BIOS Error (bug)

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

Re: Question regarding an ACPI BIOS Error (bug)

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

Re: Question regarding an ACPI BIOS Error (bug)

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

Re: Question regarding an ACPI BIOS Error (bug)

he number in square brackets at the start of the line is the time (in seconds) since the kernel started. At less than a second after startup, you're unlikely to have any user-space components loaded yet and, besides, the kernel is what is responsible for talking to ACPI. > > [    0.410073] A

Question regarding an ACPI BIOS Error (bug)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, I've been redirected to this list while using reportbug. I would gladly accept some help regarding the determination of the Debian package responsible for those traces during boot: [    0.410073] ACPI: Added _OSI(Processor Device

Re: Cant boot without ACPI=off after BIOS was updated

On Du, 08 mar 20, 09:02:30, Sebastián Carloza R wrote: > Hi > > My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows did > it automatically in an update. I have a Dual Boot with Debian 10.3 and > windows 10. From that moment I have to boot with ACPI = off, to loa

Re: Cant boot without ACPI=off after BIOS was updated

On 08.03.2020 17:02, Sebastián Carloza R wrote: > Hi > > My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows > did it automatically in an update. I have a Dual Boot with Debian 10.3 > and windows 10. From that moment I have to boot with ACPI = off, to > load D

Cant boot without ACPI=off after BIOS was updated

Hi My PC's (ASUS X571GD) BIOS was updated (to BIOS 306). I think Windows did it automatically in an update. I have a Dual Boot with Debian 10.3 and windows 10. From that moment I have to boot with ACPI = off, to load Debian. I don't know what's the package I would have to report

Re: noapi acpi=off

That was kinda easy. ...BUT I found that .deb file at https://packages.debian.org/buster/all/firmware-misc-nonfree/download I had the wifi pane up immediately with a list of networks. I even rebooted. BUT it says configuring interface but won't connect. I am also having to connect using a

Re: noapi acpi=off

On Tue, Jan 21, 2020 at 02:30:10PM +, zahid wrote: > So now I just want to > > " to get this firmware package and install it  [ /lib/firmware/rt2870.bin > firmware-misc-nonfree > ] " > > what are the instructions I need to follow to

Re: noapi acpi=off

Thank for your response, I want to avoid using  "netinst with non-free firmware" because that would mean a reinstall again. and I would have to install other software al over again. So now I just want to " to get this firmware package and install it  [ /lib/firmware/rt2870.bin

Re: noapi acpi=off

On Tue, Jan 21, 2020 at 11:15:34AM +, Zahid Rahman wrote: > During installation I got a prompt to install rtl_nic/rtl8168h-2.fw > rt2870.bin from media. > I was installing using net install so I skipped it. Awesome. Knowing the exact filename of the firmware that you need makes it *super*

Re: noapi acpi=off

ave the latest version of debian and it is logging on and off > ok , what are the acpi setting, kernel parameters. > > You can find this out by pressing 'e' when the grub screen is showing. > > I should have taken note when I had debian installed. > > > I recommend to use def

Re: noapi acpi=off

On 21.01.2020 10:21, Zahid Rahman wrote: > So if you have  the latest version of debian and it is logging on and > off ok ,  what are  the acpi setting,  kernel parameters. > > You can find this out by pressing 'e' when the grub screen is showing. > > I should have taken note

Re: noapi acpi=off

So if you have the latest version of debian and it is logging on and off ok , what are the acpi setting, kernel parameters. You can find this out by pressing 'e' when the grub screen is showing. I should have taken note when I had debian installed. On Tue, 21 Jan 2020, 05:13 Zahid Rahman

Re: noapi acpi=off

only work, go to login screen in recovery mode due to this acpi issue. So now I am using open suse. That operating system is compensating for the corrupted BIOS table and has wifi driver. For some reason open opensuse.org is extremely fast compare to all linux operating system. On Mon, 20

Re: noapi acpi=off

On Mon, Jan 20, 2020 at 03:03:44PM +, Zahid Rahman wrote: I would appreciate if some one can tell me the precise kernel parameter values so the laptop will turm off and I promise to turn off software updates after that. FEDORA 31. You've sent this to the Debian User list, for Debian

noapi acpi=off

Hi, The idea to introduce this acpi change in the software updates across linux platforms, I think was a very bad. It has meant that either I can't login or I am staring at a purple, or black blank screen depending on the linux flavour. or the system is hanging and won't turn off. Anyway

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

quick note, the bug report has been filed: 919227

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

Il 09/01/19 00:07, Michael Lange ha scritto: Just because it is old does not necessarily mean that no one bothers. Sorry, that's not what I meant: I wanted to say the kernel is so old that it probably doesn't really matter if it is the debian or the upstream version I am using. That is,

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

ht, however there was quite a big rewrite of ACPI > in 4.10 and I wouldn't rule it out completely. I forgot to mention that the lid did not stop working here between 4.9 and 4.10. Actually here it works with a Siduction 4.16 kernel, but does not with the Liquorix 4.19. Just for the fun of it

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

Il 07/01/19 20:09, Michael Lange ha scritto: Since the error message looks different from yours I guess that this is probably a completely different issue, though. Most likely you're right, however there was quite a big rewrite of ACPI in 4.10 and I wouldn't rule it out completely. I

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

Hi, On Fri, 4 Jan 2019 20:11:53 +0100 Andrea Borgia wrote: (...) > > dmesg has this interesting warning: > ACPI: button: The lid device is not compliant to SW_LID. oddly, here with my Lenovo Ideapad 100s the lid switch stopped working, too. However, this is totally different hardware

Re: kernel regression from stable to testing (acpi lid / EEEpc 1215p)

on snapshot.debian.org: 4.9.0-7: OK (last known working, see previous msg) 4.10.0-trunk: fails 4.11.0-2: fails 4.14.0-1: fails 4.19.0-1: fails (first failure detected, see previous msg) (those versions which are failing all have the "SW_LID" warning) In Documentation/acpi/acpi-lid.txt, I saw

kernel regression from stable to testing (acpi lid / EEEpc 1215p)

(4.19.0-1), or really any "testing" kernel from december onwards (when I upgraded), this is the situation: * the sleep keycombo Fn+F1 works * pm-suspend works * pm-hibernate works If I observe the state of /proc/acpi/button/lid/LID/state from a remote shell and close the lid, it s

Re: Re: ACPI BIOS ERROR

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

Re: Re: ACPI BIOS ERROR

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?

Re: How to Fix ACPI Error : Namespace lookup failure

On 2018-11-10 19:31, finn wrote: Greetings, Whenever I boot up my PC I'm getting this error `sudo dmesg` [ 12.432182] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [ 12.432241] ACPI Error: Method parse/execution

How to Fix ACPI Error : Namespace lookup failure

Greetings, Whenever I boot up my PC I'm getting this error `sudo dmesg` [ 12.432182] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [ 12.432241] ACPI Error: Method parse/execution failed [\_SB.PCI0.B0D4._TMP

ACPI wrong battery information (kernel 4.18)

Hi, I've made a fresh installation of debian testing on my ASUS eeepc x101. ACPI reports wrong battery informations. If I type acpi -V: $ acpi -V Battery 0: Discharging, 100%, 4200:00:00 remaining Battery 0: design capacity 4300 mAh, last full capacity 4200 mAh = 97% Adapter 0: off-line Thermal

Re: ACPI BIOS ERROR

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

Re: ACPI BIOS ERROR

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

Re: ACPI BIOS ERROR

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

Re: ACPI BIOS ERROR

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

Re: ACPI BIOS ERROR

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,

Re: ACPI BIOS ERROR

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.

Re: ACPI BIOS ERROR

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.

Re: ACPI BIOS ERROR

steve wrote: > Should I open a ticket in the BTS? you have latest BIOS installed?

ACPI BIOS ERROR

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

Re: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

Aug 27, 2018, 2:57 AM by b...@fineby.me.uk: > On Mon, 27 Aug 2018 03:49:14 +0200 (CEST) > local10 <> loca...@tutanota.com > > wrote: > > The two things are unrelated. The error on boot is "annoying but > harmless", according what I've read, after a *very* cursory

Re: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

On Mon, 27 Aug 2018 03:49:14 +0200 (CEST) local10 wrote: Hello local10, >Am getting the following errors on boot and, probably due to the >errors, KDE cannot start (kde-plasma-desktop package was installed). The two things are unrelated. The error on boot is "annoying but harmless", according

Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

Hi, Am getting the following errors on boot and, probably due to the errors, KDE cannot start (kde-plasma-desktop package was installed). The snapshot was from August 20, 2018 was used for buster installation. Any ideas? Thanks Aug 26 21:31:55 tstsrv kernel: [    0.032672] ACPI: Added _OSI

Re: how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world From: davidson Sent: Saturday, 11 August 2018 8:02 PM To: debian-user@lists.debian.org Subject: how to change default locale [was Re: How to Fix ACPI Error : Namespace

Re: how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

https://www.mycause.com.au/page/183259/a-smile-will-change-a-day-love-that-changed-my-world From: davidson Sent: Saturday, 11 August 2018 8:02 PM To: debian-user@lists.debian.org Subject: how to change default locale [was Re: How to Fix ACPI Error : Namespace

how to change default locale [was Re: How to Fix ACPI Error : Namespace lookup failure]

On Sun, 5 Aug 2018, genius wrote: Q: how to change the Language option . my system default language is English , now I want to change it into Chinese.. If there is some connection between the original subject line of your message ("Re: How to Fix ACPI Error : Namespace lookup fa

Re: How to Fix ACPI Error : Namespace lookup failure

Q: how to change the Language option . my system default language is English , now I want to change it into Chinese..

Re: ACPI Error on boot

not fetch firmware file > 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 > > Could the other ACPI Errors be related to this missing firmware? No. And in the specific case of ath10k, which actually searches for firmware in descending preference order, it is sort of normal to get these annoying

Re: ACPI Error on boot

ly the only way to make ACPI "errors" go away, although it often seems to be the case that the errors reported are themselves erroneous, log noise rather than real trouble. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Liv

Re: ACPI Error on boot

firmware: failed to load > ath10k/QCA6174/hw3.0/firmware-5.bin (-2) > [9.311107] ath10k_pci :03:00.0: Direct firmware load for > ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 > [9.33] ath10k_pci :03:00.0: could not fetch firmware file > 'ath10k/QCA61

Re: ACPI Error on boot

his error, thanks a lot, what is referred here as firmware is the bios of the computer - upgrade. the missing atheros firmware is not related to the ACPI error - you can install the missing firmware either via debian package or from the vendor. install: $ apt-cache search firmware-atheros firmware-atheros

Re: ACPI Error on boot

> I think what he means could be said in other words for example like "Is > there any negative effect when the machine boots that you believe is > related to this error message?" > I am also getting notices of missing firmware, that is the only other thing I have noticed, thanks,

Re: ACPI Error on boot

On Thu, 12 Apr 2018 11:40:15 -0500 Anil Duggirala wrote: > On Thu, Apr 12, 2018, at 8:31 AM, to...@tuxteam.de wrote: > > > Is there any negative effect on your boot you link to this > > message? > > > > I do not understand the wording of this question, could you

Re: ACPI Error on boot

> have you updated BIOS to latest version from machine > vendor? > I have not, I will see if there is a newer version. I am running Debian Stretch on a Dell 3580 Latitude machine. I have not tried anything so far to fix this error, thanks a lot,

Re: ACPI Error on boot

ith error -2 [9.33] ath10k_pci :03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Could the other ACPI Errors be related to this missing firmware? Do you also recommend updating my BIOS? thanks,

Re: ACPI Error on boot

On Thu, Apr 12, 2018, at 8:31 AM, to...@tuxteam.de wrote: > Is there any negative effect on your boot you link to this > message? > I do not understand the wording of this question, could you please rephrase it? I did not link anything to my O post. The only negative effect I see is the error

Re: ACPI Error on boot

Anil Duggirala wrote: ... > Can someone please help me out, or let me know why Im not getting any help > with this, lack of details about machine, debian versions, things tried, etc, and for me being busy with other things for a while to even begin to look at this message to begin with.

Re: ACPI Error on boot

On Thu, 12 Apr 2018, Anil Duggirala wrote: > On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote: > > I am getting an error on boot in my dual boot Win 10-Debian 9 system, > > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/ > > exmutex-393) > &g

Re: ACPI Error on boot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Apr 12, 2018 at 08:09:08AM -0500, Anil Duggirala wrote: > On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote: > > hello, > > I am getting an error on boot in my dual boot Win 10-Debian 9 system, > > ACPI Error: Canno

Re: ACPI Error on boot

On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote: > hello, > I am getting an error on boot in my dual boot Win 10-Debian 9 system, > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/ > exmutex-393) > ACPI Error: Method parse/execution failed [\_SB.PCI0

ACPI Error on boot

hello, I am getting an error on boot in my dual boot Win 10-Debian 9 system, ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/exmutex-393) ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node 9346529f5960), AE_AML_MUTEX_NOT_ACQUIRED (20160831/psparse-543

ACPI Error at boot time

I am getting two errors almost always at boot time: ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/exmutex-393) ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node 8cf9129f5898), AE_AML_MUTEX_NOT_ACQUIRED (20160831/psparse-543) I am dual booting Win 10

stable-backports kernel 4.14.3 ACPI errors with new Gigabyte EFI motherboard

Hi - Am using debian9, just upgraded my system to a gigabyte Z370 + intel core-i7-8700k, bootup is EFI. System works fine, but bootup is really slowed down because of the following ACPI errors. In digging around, looks like the issue is gigabyte needs to fix their bios, have put in a support

Re: Sense APM, problemes amb ACPI

Hola. A mí me dona el mateix error a la arrencada (ACPI error, method parse/execution failed), pero si arrenco amb el kernel 4.8.0.1 no me dona cap error. Ho has provat?. Salut, Pep El 20/10/17 a les 11:38, Narcis Garcia ha escrit: Un ordinador amb Debian 9 em dóna aquestes alertes

Re: Sense APM, problemes amb ACPI

administrator should fix this against automated addresses collectors. El 20/10/17 a les 12:55, Josep Lladonosa ha escrit: > On 20 October 2017 at 11:38, Narcis Garcia <debianli...@actiu.net> wrote: >> Un ordinador amb Debian 9 em dóna aquestes alertes: >> >> ACPI BIOS Warning

Re: Sense APM, problemes amb ACPI

administrator should fix this against automated addresses collectors. El 20/10/17 a les 12:51, Pep ha escrit: > Hola. > > A mí me dona el mateix error a la arrencada (ACPI error, method > parse/execution failed), pero si arrenco amb el kernel 4.8.0.1 no me > dona cap error. >

Sense APM, problemes amb ACPI

Un ordinador amb Debian 9 em dóna aquestes alertes: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Address but zero Length: 0x0050/0x0 (20160831/tbfadt-658) ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0, using default 8 (20160831/tbfadt

Re: Problemas con ACPI

arrancar el equipo recibo errores de ACPI, os pego la salida de consola: $ sudo dmesg | grep ACPI | grep -i error [sudo] password for asim: [    1.745663] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [    1.745942] ACPI Error: Method parse/execution failed

Re: Problemas con ACPI

El 18/09/17 a las 20:43, Quijote Libre escribió: Buenas trades Estoy con Debian statble con escritorio mate, sólo con los repositorios main y al arrancar el equipo recibo errores de ACPI, os pego la salida de consola: $ sudo dmesg | grep ACPI | grep -i error [sudo] password for asim

Problemas con ACPI

Buenas trades Estoy con Debian statble con escritorio mate, sólo con los repositorios main y al arrancar el equipo recibo errores de ACPI, os pego la salida de consola: $ sudo dmesg | grep ACPI | grep -i error [sudo] password for asim: [    1.745663] ACPI Error: [DSSP] Namespace lookup

Re: "ACPI error" depuis passage à Stretch

/www.academie-francaise.fr/cloturer-la-seance>) et visiblement tu as depose le bug au mauvais endroit: aupres d'un paquet permettant d'effectuer des actions en se basant sur ACPI plutot qu'au niveau de la gestion ACPI en elle meme, qui se trouve dans le noyau. -- Bien cordialement, Stephane Ascoet

Re: "ACPI error" depuis passage à Stretch

Bonsoir à tous. Mon rapport de bogue a été clôturé. Voici la réponse du mainteneur (en anglais bien sûr) : >This may be a kernel problem, or a hardware one (which to me looks most >likely), but certainly not related to the tool acpi you reported it >against. Therefore I close the repo

Re: "ACPI error" depuis passage à Stretch

Le Thu, 6 Jul 2017 10:35:44 +0200 Alain Rpnpif <rpn...@free.fr> a écrit: > Le 5 juillet 2017, Benoit B a écrit : > > > Idem pour moi, > > > > ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond > > end of object (length 0x5) (20160831/exoparg

Re: "ACPI error" depuis passage à Stretch

Le 5 juillet 2017, Benoit B a écrit : > Idem pour moi, > > ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond > end of object (length 0x5) (20160831/exoparg2-427) > [ 14.235257] ACPI Error: Method parse/execution failed > [\_SB.PCI0.GFX0._DOD] (Nod

Re: "ACPI error" depuis passage à Stretch

Idem pour moi, ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x5) is beyond end of object (length 0x5) (20160831/exoparg2-427) [ 14.235257] ACPI Error: Method parse/execution failed [\_SB.PCI0.GFX0._DOD] (Node 9317bb0ab500), AE_AML_PACKAGE_LIMIT (20160831/psparse-543) [ 14.235269

Re: Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

Olivier F. R. Dierick wrote: > acpi=off I don't know about the kernel http://www.thinkwiki.org/wiki/Category:R40e but you better check if your ATI will be supported with the recent X server ;) regards

Thinkpad R40e can't boot Debian 9.0.0 netinst image without acpi=off

Hi, I wanted to file a bug report, but I don't know which package the issue belongs to. The computer is a IBM Thinkpad R40e. Currently Debian 8 is installed. Ever since Debian 8 was installed on the harddrive I had to add acpi=off to the kernel options, otherwise the computer does not boot

"ACPI error" depuis passage à Stretch

7). Voici les messages extraits du journal : ACPI Error: Evaluating _BCM failed (20160831/video-354) ACPI Error: Method parse/execution failed [\_SB.PCI0.VGA.LCDD._BCM] (Node 8eb9fb0af668), AE_AML_BUFFER_LIMIT (20160831/psparse-543) ACPI Error: Method parse/execution failed [\_SB.PCI0

Re: How to Fix ACPI Error : Namespace lookup failure

On Thu, Apr 20, 2017 at 02:57:20AM +, 慕 冬亮 wrote: Dear all, After I reverted BIOS back to default setting, I found some following error messages related to ACPI: [    0.847234] ACPI: Thermal Zone [THM] (25 C) [    0.847347] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace

How to Fix ACPI Error : Namespace lookup failure

Dear all, After I reverted BIOS back to default setting, I found some following error messages related to ACPI: [0.847234] ACPI: Thermal Zone [THM] (25 C) [0.847347] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) [0.847605] ACPI

Question on /proc/acpi/wakeup

Wakeup capable devices are listed in /proc/acpi/wakeup. For example, in my sytem I've got: ~ solitone@alan:~$ cat /proc/acpi/wakeup Device S-state Status Sysfs node PEG0 S3*disabled ECS4*disabled platform:PNP0C09:00 HDEF

Re: intel_pstate vs acpi-cpufreq freq scale

After some discussion with Liquorix people (who are still not convinced by intel_pstate) http://techpatterns.com/forums/viewtopic.php?p=12509#12509 I'm going to try out the new 'schedutils' option with acpi-cpufreq See how it goes eh. Regards, Julian On 16 January 2017 at 23:49, Julian Brooks

Re: intel_pstate vs acpi-cpufreq freq scale

Dear Luis, Many thanks for your input and guidance here. 'Have you tried to see if this happens with debian's official kernel?' Doh! Of course. Yes I have now, and intel_pstate is active - yay. Complete newb with any kind of kernel config/tweaking/rebuilding - need to do some reading-up.

Re: intel_pstate vs acpi-cpufreq freq scale

On lunes, 16 de enero de 2017 1:13:09 (CET) Julian Brooks wrote: > Hi all, Hi Julian, > Fresh install of Sid, with > liquorix 4.9-3 (2017-01-07) x86_64 kernel (for RT audio work). > Have also installed linrunner's TLP. Have you tried to see if this happens with debian's official kernel? > My

intel_pstate vs acpi-cpufreq freq scale

of intel_pstate for frequency scaling but I can't seem to load the kernel module at boot. TLP (and other sources) are telling me the system has acpi-cpufreq running the frequency scaling. Have tried adding 'intel_pstate=enable' to grub (+ update-grub), no change (liquorix should load intel_pstate

  1   2   3   4   5   6   7   8   9   10   >