To Help ALL,
First an explanation of why ACPI errors occur in Linux, and why it can USUALLY be ignored
Second, if hundreds of errors happen on boot like my Hp OmenX Bleeding Edge Laptop, I will show you a trick for Grub (the boot loader) to ignore them, and boot normally
Third, I am posting this as I just upgraded my kernel, and all my «Errors:
Quote:
ACPI:3400 Unsupported Event»
have disappeared, and I will show you how to upgrade your kernel.
ACPI Errors — Microsoft’s Fault!!
-
It’s supposed to be a standard that any operating system can properly implement. However, in typical Microsoft fashion, MS operating systems do not follow or properly implement the ACPI standard. Instead, MS gives motherboard manufacturers their own improperly implemented ACPI code for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS windows but all for other operating systems like linux there can be problems.
Because of MS’s market dominance, the faulty ACPI implementation from MS has become the de facto industry standard. As a result, Linux and other non-MS operating systems have to reverse engineer the faulty ACPI implementation from MS. That’s why you can see problems in Linux with ACPI related functionality like suspend to RAM, hibernate, etc.
-
Apparently, the ACPI related code in certain newer Linux kernels has a problem with the typical BIOS/UEFI ACPI implementation on certain motherboards which is why we’re getting those error messages. Even though I get those error messages at the beginning of the boot process, I’ve had no problems with suspend/resume or any other ACPI related issues.
-
I have seen advice to not run in BIOS legacy mode by disabling UEFI but to run in UEFI mode instead with secure boot disabled. I haven’t bothered with it myself since I have several operating systems already installed with BIOS legacy mode and I would have to reinstall everything if I wanted to switch to UEFI mode.
(UEFI Mode is working GREAT for my install)
Hp / ACPI Errors
ACPI — Advanced Configuration & Power Interface
To avoid seeing ERROR «acpi int3400 unsupported event» ERRORS…
In the file /etc/default/grub
Add to the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" the parameters
acpi=off or noacpi acpi=strict
So that after your edit it looks, for example, like this
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=strict"
For me, acpi=strict is working best. You can also try acpi=force, and pnpacpi=off worked For another HP Spector user.
To edit the file you need to open it with root permission, for example by running
sudo -H gedit /etc/default/grub
After editing, update the configuration by running
sudo update-grub
and regenerate the initrd:
sudo update-initramfs -u
and then restart to see the effect
The latest kernel 4.19.5 has ELIMINATED ALL my problematic acpi:3400 errors
Install UKUU:
UKUU — Ubuntu Kernel Update Utility: Manage and Install Newest Bleeding Edge Kernels
sudo add-apt-repository ppa:teejee2008/ppa
sudo apt update && sudo apt install ukuu
and after run UKUU and it will offer to install or uninstall any and of course the newest (stable or not so stable) KERNEL.
IT ALWAYS LEAVES your last working kernel as a backup should the new one not work as well as you would like.
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
ACPI BIOS Error (bug): [SOLVED]
When I start up my Desktop with Linux Mint 20.1 I get these messages:
Is this just a bug which will go away after some future update?
What is it looking for?
dmesg gives:
[ 1.011765] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.011788] fbcon: Taking over console
[ 1.011792] No Local Variables are initialized for Method [_GTF]
[ 1.011792] No Arguments are initialized for method [_GTF]
[ 1.011794] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.011802] ata5.00: ATAPI: TSSTcorp CDDVDW SH-S223B, SB01, max UDMA/100
[ 1.011855] Console: switching to colour frame buffer device 128×48
[ 1.012200] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012208] No Local Variables are initialized for Method [_GTF]
[ 1.012209] No Arguments are initialized for method [_GTF]
[ 1.012211] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012424] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012430] No Local Variables are initialized for Method [_GTF]
[ 1.012431] No Arguments are initialized for method [_GTF]
[ 1.012432] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012441] ata2.00: ATA-8: ST500DM002-1BD142, KC45, max UDMA/133
[ 1.012443] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32)
[ 1.012533] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.012539] No Local Variables are initialized for Method [_GTF]
[ 1.012540] No Arguments are initialized for method [_GTF]
[ 1.012541] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.012549] ata5.00: configured for UDMA/100
[ 1.013829] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.013892] No Local Variables are initialized for Method [_GTF]
[ 1.013893] No Arguments are initialized for method [_GTF]
[ 1.013894] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 1.014219] ata2.00: configured for UDMA/133
[ 1.015831] ata1.00: ATA-10: CT480BX500SSD1, M6CR022, max UDMA/133
[ 1.015833] ata1.00: 937703088 sectors, multi 1: LBA48 NCQ (depth 32), AA
[ 1.021653] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[ 1.021695] No Local Variables are initialized for Method [_GTF]
[ 1.021696] No Arguments are initialized for method [_GTF]
[ 1.021698] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
Has this got anything to do with it?
Its a warning before the Error but not flagged up on the screen on startup;
[ 0.639660] r8169 0000:04:00.0: can’t disable ASPM; OS doesn’t have ASPM control
[ 0.641211] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (PMIO) (20190816/utaddress-204)
[ 0.641217] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641220] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/utaddress-204)
[ 0.641223] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641224] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/utaddress-204)
[ 0.641228] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641229] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000051F (LED) (20190816/utaddress-204)
[ 0.641233] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/utaddress-204)
[ 0.641237] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 0.641237] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 0.642074] libphy: r8169: probed
[ 0.642085] i801_smbus 0000:00:1f.3: enabling device (0001 -> 0003)
[ 0.642219] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 0.642370] r8169 0000:04:00.0 eth0: RTL8168evl/8111evl, 94
[ 0.642372] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 0.659537] ahci 0000:00:1f.2: version 3.0
80:57:80:e8, XID 2c9, IRQ 29My system details:
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Graphics card = nvidia GEFORCE 210
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa Mate desktop» (64bit)
Memory = 12GB
What is it and what do I need to do?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug):
Post
by Catchpole » Wed Feb 24, 2021 3:24 am
Hi SimpleLinuxUser,
I forgot to mention that everything is working OK.
However the startup is delayed whilst it deals with the fault so I’d like a solution to speed things up.
Being an engineer I pay attention to details and this «bug» is bugging me. I like things to be neat and tidy.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
t42
- Level 9
- Posts: 2539
- Joined: Mon Jan 20, 2014 6:48 pm
Re: ACPI BIOS Error (bug):
Post
by t42 » Wed Feb 24, 2021 3:29 am
Catchpole wrote: ↑
Wed Feb 24, 2021 3:24 am
However the startup is delayed whilst it deals with the fault so I’d like a solution to speed things up.
Being an engineer I pay attention to details.
«However the startup is delayed» — how much?
Did you check a possibility of the motherboard BIOS update?
-=t42=-
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug):
Post
by Catchpole » Wed Feb 24, 2021 4:51 am
Hi t42,
I’ll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
Did you check a possibility of the motherboard BIOS update?
I don’t know if I dare do a bios update but It’s a thought. If anything goes wrong I can upgrade the board with a new one. 
What problems would I have upgrading the motherboard (MB) with respect to the operating system? I wouldn’t want to have to do another clean install when I’ve just done it recently!
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
t42
- Level 9
- Posts: 2539
- Joined: Mon Jan 20, 2014 6:48 pm
Re: ACPI BIOS Error (bug):
Post
by t42 » Wed Feb 24, 2021 5:16 am
Catchpole wrote: ↑
Wed Feb 24, 2021 4:51 am
I’ll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
These three commands may help
Code: Select all
systemd-analyze
systemd-analyze critical-chain
systemd-analyze blameCatchpole wrote: ↑
Wed Feb 24, 2021 4:51 am
What problems would I have upgrading the motherboard (MB) with respect to the operating system?
BIOS update can mess with computer on the far low level than OS. Usually motherboard is unbootable if something goes wrong and you need to prepare procedure to revert to the previews firmware.
-=t42=-
-
AndyMH
- Level 20
- Posts: 11043
- Joined: Fri Mar 04, 2016 5:23 pm
- Location: Wiltshire
Re: ACPI BIOS Error (bug):
Post
by AndyMH » Wed Feb 24, 2021 5:21 am
Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug):
Post
by Catchpole » Wed Feb 24, 2021 7:42 am
Hi t42,
The results of your commands are:
Code: Select all
user@computer:~$ systemd-analyze
Startup finished in 3.454s (kernel) + 3.083s (userspace) = 6.537s
graphical.target reached after 3.049s in userspace
user@computer:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @3.049s
└─multi-user.target @3.049s
└─networkd-dispatcher.service @2.310s +738ms
└─basic.target @2.263s
└─sockets.target @2.263s
└─uuidd.socket @2.263s
└─sysinit.target @2.260s
└─apparmor.service @2.055s +97ms
└─local-fs.target @2.054s
└─boot-efi.mount @2.040s +13ms
└─systemd-fsck@dev-disk-byx2duuid-9934x2d6DD8.service @1.781s +258ms
└─dev-disk-byx2duuid-9934x2d6DD8.device @1.780s
user@computer:~$ systemd-analyze blame
1.811s apt-daily-upgrade.service
1.434s dev-sda2.device
738ms networkd-dispatcher.service
563ms udisks2.service
374ms accounts-daemon.service
306ms ubuntu-system-adjustments.service
304ms systemd-journal-flush.service
258ms systemd-fsck@dev-disk-byx2duuid-9934x2d6DD8.service
248ms avahi-daemon.service
237ms NetworkManager.service
230ms ufw.service
229ms systemd-logind.service
225ms upower.service
223ms polkit.service
222ms ModemManager.service
205ms keyboard-setup.service
190ms gpu-manager.service
183ms thermald.service
182ms e2scrub_reap.service
177ms systemd-journald.service
175ms wpa_supplicant.service
166ms systemd-udevd.service
158ms systemd-modules-load.service
152ms systemd-udev-trigger.service
151ms systemd-resolved.service
It seems to be just a matter of mili-seconds delay to the overall progress.
So after reading the link from AndyMH, I think I’ll just leave it as it is and avoid making a mistake in the pursuit of a triviality that makes things worse.
The result of the inquiry is: leave it alone. I think that means [SOLVED]. (Or does it?)
I’ll mark it as [SOLVED]
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug): [SOLVED]
Post
by Catchpole » Sat Feb 27, 2021 8:36 am
Hi t42,
Catchpole wrote: ↑
Wed Feb 24, 2021 9:51 am
I’ll have to time the delay. Timing it on the screen is easy enough but the total delay will be harder to measure.
As I didn’t time the startup when the system was working OK I can only make a guess as to the total delay.
However, when I switched the computer on I used to do a couple of things and by the time I had finished them it was jut the right time to sign in.
So from the time of switching on and after doing the same couple of things, the total time delay now is about 20 second later to get to the sign in screen.
As for the bios upgrade:
There is only one upgrade from the «F1» bios version to version «F3c» but its a «beta».
F3c
2.85 MB
2014/03/04
DownloadBeta BIOS
Improve High-End Display card compatibility==============================================
F2
2.82 MB
2013/03/19
DownloadFirst Release
So unfortunately there is still a problem and I was a little hasty accepting the data from the error log and in adding the [SOLVED] marker!
You live and learn.
I’ve set «ACHI» and UEFI, turned off «Secure Boot» and made sure «CSM» is disabled.
If I’ve done all I can with the bios I guess I’ll have to live with it or get a new motherboard. (unless there’s another solution)
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug): [SOLVED]
Post
by Catchpole » Sun Feb 28, 2021 8:54 am
A re-run of the commands suggested by: t42
Code: Select all
systemd-analyze
systemd-analyze critical-chain
systemd-analyze blamegives:
Code: Select all
28th Feb 2021 11:39hrs
user@computer:~$ systemd-analyze
Startup finished in 3.302s (kernel) + 35.977s (userspace) = 39.279s
graphical.target reached after 28.153s in userspace
user@computer:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @28.153s
└─multi-user.target @28.153s
└─postfix.service @28.146s +6ms
└─postfix@-.service @24.114s +4.029s
└─network-online.target @24.107s
└─NetworkManager-wait-online.service @17.438s +6.668s
└─NetworkManager.service @17.169s +266ms
└─dbus.service @17.165s
└─basic.target @17.147s
└─sockets.target @17.147s
└─uuidd.socket @17.147s
└─sysinit.target @17.143s
└─apparmor.service @17.030s +112ms
└─local-fs.target @17.029s
└─run-user-1000-gvfs.mount @35.402s
└─run-user-1000.mount @32.935s
└─swap.target @524ms
└─swapfile.swap @391ms +133ms
└─systemd-remount-fs.service @361ms +28ms
└─systemd-journald.socket @343ms
user@computer:~$ systemd-analyze blame
18.731s fstrim.service
16.606s dev-sda2.device
6.668s NetworkManager-wait-online.service
4.029s postfix@-.service
1.056s man-db.service
925ms networkd-dispatcher.service
757ms udisks2.service
538ms logrotate.service
511ms apt-daily-upgrade.service
485ms ubuntu-system-adjustments.service
482ms apt-daily.service
451ms systemd-logind.service
449ms accounts-daemon.service
349ms systemd-journal-flush.service
323ms networking.service
290ms ModemManager.service
266ms NetworkManager.service
260ms fwupd-refresh.service
245ms avahi-daemon.service
238ms polkit.service
237ms systemd-resolved.service
228ms ufw.service
214ms upower.service
This gives much longer delay than when it was first run.
I can’t understand why it didn’t pick up the time delay in the first instance.
Does the fstrim.service take 18 seconds to complete?
I’ve done some reading around but can’t find a solution.
Can anyone point me in the right direction?
Last edited by Catchpole on Mon Mar 01, 2021 3:23 am, edited 1 time in total.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
-
Catchpole
- Level 4
- Posts: 338
- Joined: Sat Dec 24, 2011 4:15 am
- Location: Leeds UK
Re: ACPI BIOS Error (bug): [SOLVED]
Post
by Catchpole » Sun Feb 28, 2021 10:17 am
I’ve found the cause of the problem at last!!
It was my graphics card — nvidia GEFORCE 210 That was causing the conflict.
Using the «Driver Manager» I changed the driver from the «recommended» proprietary driver to the Ubuntu one offered instead.
Now its back to its normal speed that I had before with the Mint 19.1 Operating System.
Perhaps Mint 20.1 will catch up with some future updates in the near future.
Thanks to everyone for your help.
Desktop Computer:
Motherboard = Gigabyte GA-H61M-USB3V
CPU = Intel i3-3240 3.4GHz
Monitor = BENQ BL2411PT rev 00-012-AL
Mint 20.1 Ulyssa «Mate desktop» (64bit)
Memory = 12GB
Imperio писал(а): ↑
11 фев 2018, 09:56
Держал шифт во время загрузки, ничего не произошло. Когда вижу меню загрузки пробовал f6 наживать, тоже ничего не изменяется. А как вызвать меню или консоль чтобы прописать эти параметры?
ну и зачем нажимать шифт или ф6 ?
так понимаю из подчёркнутого в ыше в цитате и ранее сказанного
Imperio писал(а): ↑
11 фев 2018, 08:20
Выбирал «compatibility mode», даже загрузка окон происходит. …..
меню у вас отображается
и что нажимать для его редакции (для редактирования выбранной строки меню ) ,емнип, написано в самом меню (в стандартно установленном с системой груб2 это буковка «e» , в меню унетбутина — [Tab]
Впрочем что за меню и какого загрузчика у вас открывается вы скрываете , так же как скрываете с какого девайса вы грузитесь (DVD или USBфлешка , или …. или… ) , и какой программой делали загрузочный девайс. Впрочем вы скрываете и что у вас за ноут(что за железо, что на нём установлено, как размечен и отформатирован HDD) и какой именно минт вы пытаетесь загрузитьустановить,
Как вариант, если у вас загрузочная флешка и не можете найти «кнопку» включения редактирования строки меню , можно попробовать отредактировать её на стороннем компутере в текстовом редакторе , для чего надо будет найти файл с меню на этой флешке.
но … вы же загружаете ноут
Imperio писал(а): ↑
11 фев 2018, 08:20
Выбирал «compatibility mode», даже загрузка окон происходит. Но не видит диска.
имхо, поиски кнопки для редактирования меню не нужны … уже всё найдено -> «compatibility mode»
такшта можно делать установку … ну и потом танцы с бубном по настройкеустановке драйверов отладке …..
Когда я ставил винду на этот ноут, я на установочную флэшку копировал драйвер. Папка, которую я сохранил, зовется «USB3.0_Intel_USB_3.0_xHC_Driver_Skylake_MR2_PV_4.0.2.42_4.0.2.42_0x2c4e2f04». Установщик виндов без драйвера тоже не видел диск.
может кто и подскажет , какое значение для определения винта на ПК имеет установка драйвера для USB 3.0 … ( или для графики ли он какой или там не один драйвер в папке а несколько… для борда)
«Не ты выбираешь Linux, а Linux выбирает тебя»
(с)Себастьян Перейра, торговец чёрным деревом
Здравствуйте, друзья!
Более или менее наладил основные модули системы, и пришла пора заняться «шероховатостями».
Сразу после установки Debian в качестве дополнительной операционной системы при загрузке стали появляться ошибки ACPI BIOS Error.
[attach=1]
[ 1.544838] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.544917] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUMD (20180810/psparse-516)
[ 1.545265] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[ 1.545343] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT3._GTF, AE_MOT_FOUND (20180810/psparse-516)
[ 1.545861] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT0._GTF.DSSP]. AE_NOT_FOUND (2O180810/psargs-330)
[ 1.545938] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[ 1.557381] ACPI BIOS Error (bug): Could not resolve [_SB.PCI0.SAT0.SPT3._GTF.DSSP]. AE_MOT_FOUMD (20180810/psargs-330)
[ 1.557459] ACPI Error: Method parse/execution failed S_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516)
debian: clean, 148702/1966080 files, 1460624/7864013 blocks
Что особенно странно, эти ошибки возникают и при загрузке старенькой Ubuntu 16.04. До установки Debian этих ошибок не было, Ubuntu грузилась спокойно.
[attach=2]
[ 1.374560] ACPI Еrror: [DSSP] Namespace lookup failure, AE_NOT_F0UND (20170831/psargs-364)
[ 1.374628] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170831/psparse-550)
[ 1.375048] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 1.375118] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT3. GTF, AE_NOT_FOUND (20170831/psparse-550)
[ 1.375426] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 1.375493] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPTO._GTF, AE_NOT_FOUND (20170831/psparse-550)
[ 1.390666] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 1.390733] ACPI Error: Method parse/execution failed _SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20170831/psparse-550)
root: clean, 248619/3276800 files, 1875678/13107200 blocks
Обновлял grub, не помогает.
Уже успел начитаться в интернете, что если все работает, то и не стоит по этому поводу напрягаться. Может и так, но почему несколько лет ошибок не было, linux-система загружалась спокойно, а тут без видимых оснований (манипуляции внутри системного блока) они взяли и возникли?
ЗЫ. Может все-таки загрузчик?
Quite harmless; but check if you can upgrade your bios in case a new one is proposed for your model brand.
As a result, of your response. I will not worry about the error message anymore. Thanks so much.
With respect to updating my bios, a friend made the same suggestion to do so. I have searched for how to do update the bios, but I am at a loss for how to accomplish doing so. Can you provide some direction on how to do it. This is the link I went to initially: https://help.ubuntu.com/community/BIOSUpdate
Here is output from dmidecode:
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
# SMBIOS implementations newer than version 3.2.0 are not
# fully supported by this version of dmidecode.
Table at 0x4FA89000.Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: AMI
Version: F.28
Release Date: 04/08/2019
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 13312 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25″/1.2 MB floppy services are supported (int 13h)
3.5″/720 kB floppy services are supported (int 13h)
3.5″/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 15.28
Firmware Revision: 10.47Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: HP
Product Name: HP Spectre x360 Convertible 15-df0xxx
Version:
Serial Number: 5CD9035ZD6
UUID: 39444335-3330-5a35-4436-365a33304435
Wake-up Type: Power Switch
SKU Number: 4WW36UA#ABA
Family: 103C_5335KV HP SpectreHandle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: HP
Product Name: 8518
Version: 10.47
Serial Number: PHSKL048JBT20V
Asset Tag: Base Board Asset Tag
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Base Board Chassis Location
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: HP
Type: Convertible
Lock: Not Present
Version: Chassis Version
Serial Number: Chassis Serial Number
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: Not SpecifiedHandle 0x0004, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Mouse
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse PortHandle 0x0005, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Keyboard
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard PortHandle 0x0006, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Micro SD
Internal Connector Type: None
External Reference Designator: Micro SD
External Connector Type: Mini Centronics Type-14
Port Type: OtherHandle 0x0007, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HDMI
Internal Connector Type: None
External Reference Designator: HDMI
External Connector Type: None
Port Type: Video PortHandle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Audio Jack
Internal Connector Type: None
External Reference Designator: Audio Jack
External Connector Type: Mini Jack (headphones)
Port Type: Audio PortHandle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Right USB 3.1 GEN2
Internal Connector Type: None
External Reference Designator: Right Type C
External Connector Type: Access Bus (USB)
Port Type: USBHandle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Right USB 3.1 GEN2
Internal Connector Type: None
External Reference Designator: Right Type C
External Connector Type: Access Bus (USB)
Port Type: USBHandle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Right USB 3.1 GEN1
Internal Connector Type: None
External Reference Designator: Right Type A
External Connector Type: Access Bus (USB)
Port Type: USBHandle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Access Bus (USB)
Port Type: USBHandle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB4
External Connector Type: Access Bus (USB)
Port Type: USBHandle 0x000E, DMI type 9, 17 bytes
System Slot Information
Designation: J6B2
Type: x16 PCI Express
Current Usage: In Use
Length: Long
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:01.0Handle 0x000F, DMI type 11, 5 bytes
OEM Strings
String 1: $HP$
String 2: ABS 70/71 79 7A 7B 7C
String 3: BCU_Y
String 4: BATT_CARE
String 5: FBYTE#3K6b7B7N7WaBaHapaqasawbVbhbzcbd6dUdpdqfPhZj6 .5h;BUILDID#18
String 6: WW2S5T604#SABA#DABA;
String 7:
String 8:
String 9:
String 10:
String 11:
String 12:
String 13:Handle 0x0010, DMI type 22, 26 bytes
Portable Battery
Location: Primary
Manufacturer: 333-27-09-A
Name: SU06084XL
Design Capacity: 84080 mWh
Design Voltage: 11550 mV
SBDS Version: 1.1
Maximum Error: Unknown
SBDS Serial Number: 0469
SBDS Manufacture Date: 2018-11-09
SBDS Chemistry: LION
OEM-specific Information: 0x0008050AHandle 0x0011, DMI type 32, 20 bytes
System Boot Information
Status: No errors detectedHandle 0x0012, DMI type 34, 11 bytes
Management Device
Description: LM78-1
Type: LM78
Address: 0x00000000
Address Type: I/O PortHandle 0x0013, DMI type 28, 22 bytes
Temperature Probe
Description: LM78A
Location: Motherboard
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: UnknownHandle 0x0014, DMI type 36, 16 bytes
Management Device Threshold Data
Lower Non-critical Threshold: 1
Upper Non-critical Threshold: 2
Lower Critical Threshold: 3
Upper Critical Threshold: 4
Lower Non-recoverable Threshold: 5
Upper Non-recoverable Threshold: 6Handle 0x0015, DMI type 35, 11 bytes
Management Device Component
Description: Default string
Management Device Handle: 0x0012
Component Handle: 0x0013
Threshold Handle: 0x0014Handle 0x0016, DMI type 27, 15 bytes
Cooling Device
Temperature Probe Handle: 0x0013
Type: Power Supply Fan
Status: OK
Cooling Unit Group: 1
OEM-specific Information: 0x00000000
Nominal Speed: Unknown Or Non-rotating
Description: Cooling Dev 1Handle 0x0017, DMI type 36, 16 bytes
Management Device Threshold Data
Lower Non-critical Threshold: 1
Upper Non-critical Threshold: 2
Lower Critical Threshold: 3
Upper Critical Threshold: 4
Lower Non-recoverable Threshold: 5
Upper Non-recoverable Threshold: 6Handle 0x0018, DMI type 35, 11 bytes
Management Device Component
Description: Default string
Management Device Handle: 0x0012
Component Handle: 0x0016
Threshold Handle: 0x0017Handle 0x0019, DMI type 27, 15 bytes
Cooling Device
Temperature Probe Handle: 0x0013
Type: Power Supply Fan
Status: OK
Cooling Unit Group: 1
OEM-specific Information: 0x00000000
Nominal Speed: Unknown Or Non-rotating
Description: Not SpecifiedHandle 0x001A, DMI type 36, 16 bytes
Management Device Threshold Data
Lower Non-critical Threshold: 1
Upper Non-critical Threshold: 2
Lower Critical Threshold: 3
Upper Critical Threshold: 4
Lower Non-recoverable Threshold: 5
Upper Non-recoverable Threshold: 6Handle 0x001B, DMI type 35, 11 bytes
Management Device Component
Description: Default string
Management Device Handle: 0x0012
Component Handle: 0x0019
Threshold Handle: 0x001AHandle 0x001C, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard IGD
Type: Video
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:02.0Handle 0x001D, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 32 GB
Error Information Handle: Not Provided
Number Of Devices: 2Handle 0x001E, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x001D
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: SODIMM
Set: None
Locator: Bottom — Slot 1 (left)
Bank Locator: BANK 0
Type: DDR4
Type Detail: Synchronous
Speed: 2667 MT/s
Manufacturer: Samsung
Serial Number: 94A66FB5
Asset Tag: 9876543210
Part Number: M471A1K43DB1-CTD
Rank: 1
Configured Memory Speed: 2400 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 VHandle 0x001F, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x001D
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: SODIMM
Set: None
Locator: Bottom — Slot 2 (right)
Bank Locator: BANK 2
Type: DDR4
Type Detail: Synchronous
Speed: 2667 MT/s
Manufacturer: Samsung
Serial Number: 94A66F00
Asset Tag: 9876543210
Part Number: M471A1K43DB1-CTD
Rank: 1
Configured Memory Speed: 2400 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 VHandle 0x0020, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x003FFFFFFFF
Range Size: 16 GB
Physical Array Handle: 0x001D
Partition Width: 2Handle 0x0021, DMI type 43, 31 bytes
TPM Device
Vendor ID:
Specification Version: 2.0 Firmware Revision: 7.63
Description: INFINEON Characteristics:
Family configurable via platform software support
OEM-specific Information: 0x00000000Handle 0x0022, DMI type 221, 26 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:00.3, MAC address 00:07:00:47:50:00
NIC 2: PCI device 00:00.2, MAC address 00:00:00:9A:00:03Handle 0x0023, DMI type 221, 26 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:00.3, MAC address 00:07:00:47:50:00
NIC 2: PCI device 00:00.2, MAC address 00:00:00:00:00:03Handle 0x0024, DMI type 221, 89 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:01.4, MAC address 00:07:00:47:50:00
NIC 2: PCI device 03:00.2, MAC address FF:FF:FF:FF:FF:04
NIC 3: PCI device ff:00.0, MAC address FF:FF:30:00:05:00
NIC 4: Not Installed
NIC 5: Not Installed
NIC 6: Disabled
NIC 7: Disabled
NIC 8: PCI device 0a:00.0, MAC address 00:13:00:00:00:00
NIC 9: PCI device 00:01.3, MAC address 07:00:00:00:00:0C
NIC 10: PCI device 06:00.0, MAC address 00:00:00:00:0D:00Handle 0x0025, DMI type 221, 54 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:00.7, MAC address 00:07:00:47:50:00
NIC 2: PCI device 00:00.2, MAC address 00:07:01:57:00:03
NIC 3: PCI device 07:00.0, MAC address 00:47:50:00:04:05
NIC 4: Not Installed
NIC 5: Disabled
NIC 6: PCI device 0b:00.0, MAC address 00:08:00:FF:FF:FFHandle 0x0026, DMI type 221, 12 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:00.1, MAC address 00:04:00:00:00:00Handle 0x0027, DMI type 7, 27 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 256 kB
Maximum Size: 256 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Parity
System Type: Unified
Associativity: 8-way Set-associativeHandle 0x0028, DMI type 7, 27 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 1024 kB
Maximum Size: 1024 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 4-way Set-associativeHandle 0x0029, DMI type 7, 27 bytes
Cache Information
Socket Designation: L3 Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 8192 kB
Maximum Size: 8192 kB
Supported SRAM Types:
Synchronous
Installed SRAM Type: Synchronous
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 16-way Set-associativeHandle 0x002A, DMI type 4, 48 bytes
Processor Information
Socket Designation: U3E1
Type: Central Processor
Family: Core i7
Manufacturer: Intel(R) Corporation
ID: EB 06 08 00 FF FB EB BF
Signature: Type 0, Family 6, Model 142, Stepping 11
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Voltage: 0.8 V
External Clock: 100 MHz
Max Speed: 8300 MHz
Current Speed: 2574 MHz
Status: Populated, Enabled
Upgrade: Socket BGA1528
L1 Cache Handle: 0x0027
L2 Cache Handle: 0x0028
L3 Cache Handle: 0x0029
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 4
Core Enabled: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance ControlHandle 0x002B, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x001FFFFFFFF
Range Size: 8 GB
Physical Device Handle: 0x001E
Memory Array Mapped Address Handle: 0x0020
Partition Row Position: 1Handle 0x002C, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00200000000
Ending Address: 0x003FFFFFFFF
Range Size: 8 GB
Physical Device Handle: 0x001F
Memory Array Mapped Address Handle: 0x0020
Partition Row Position: 1Handle 0x002D, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 2D 00 31 00 00 00 00 00 00 00 00 00 00 00
F8 00 84 9D 00 00 00 00 01 00 00 00 00 00 0C 00
15 05 14 00 00 00 00 00 FE 00 FF FF 00 00 00 00
00 00 00 00 22 00 00 00 76 50 72 6F 00 00 00 00Handle 0x002E, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 5
en|US|iso8859-1
fr|FR|iso8859-1
es|ES|iso8859-1
zh|TW|unicode
zh|CN|unicode
Currently Installed Language: en|US|iso8859-1Handle 0x002F, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Intel Dual Band Wireless-AC 9560 802.11 AC 2×2 WiFi + BT 5 Combo Adapter
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:00.0Handle 0x0030, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Realtek PCIE CardReader
Type: Other
Status: Enabled
Type Instance: 1
Bus Address: 0000:01:00.0Handle 0x0031, DMI type 221, 89 bytes
HP BIOS iSCSI NIC PCI and MAC Information
NIC 1: PCI device 01:01.4, MAC address 00:FF:FF:FF:FF:FF
NIC 2: PCI device 00:00.2, MAC address FF:FF:FF:FF:FF:03
NIC 3: PCI device ff:00.4, MAC address FF:FF:FF:FF:05:06
NIC 4: Not Installed
NIC 5: Not Installed
NIC 6: Disabled
NIC 7: Not Installed
NIC 8: PCI device 0c:00.0, MAC address 00:00:09:00:01:20
NIC 9: PCI device 0e:01.5, MAC address 01:04:03:00:00:0F
NIC 10: DisabledHandle 0x0032, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Ctrl0Port1
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Primary HDD Bay
External Connector Type: SAS/SATA Plug Receptacle
Port Type: SATAHandle 0x0033, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Ctrl0Port4
Internal Connector Type: SAS/SATA Plug Receptacle
External Reference Designator: Secondary HDD Bay
External Connector Type: SAS/SATA Plug Receptacle
Port Type: SATAHandle 0x0034, DMI type 27, 15 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Nominal Speed: Unknown Or Non-rotating
Description: Cooling Dev 1Handle 0x0035, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 35 00 00 00Handle 0x0036, DMI type 14, 23 bytes
Group Associations
Name: Firmware Version Info
Items: 6
0x0022 (OEM-specific)
0x0023 (OEM-specific)
0x0024 (OEM-specific)
0x0025 (OEM-specific)
0x0026 (OEM-specific)
0x0031 (OEM-specific)Handle 0x0037, DMI type 14, 8 bytes
Group Associations
Name: $MEI
Items: 1
0x002B (OEM-specific)Handle 0x0038, DMI type 219, 106 bytes
HP ProLiant Information
Power Features: 0x45010401
Omega Features: 0x06a00002
Misc. Features: 0x00000000
iCRU: No
UEFI: NoHandle 0x0039, DMI type 127, 4 bytes
End Of TableBy the way, I went to AMI’s website and all of the update firmware options are for Windows.
Please remember i am a newbie to linux and just trying to read up as much as possible.
Thanks in advance for your continued support.
Kevin
Originally Posted by dino99
Содержание
- Ошибка ACPI BIOS Error
- [РЕШЕНО]Ошибки ACPI Error при загрузке базовой системы
- Linux Mint Forums
- [SOLVED] ACPI BIOS Error
- [SOLVED] ACPI BIOS Error
Ошибка ACPI BIOS Error
Данная ошибка вылазит при попытке запуска Ubuntu с флешки(он поработает секунд 5 после зависает и ноутбук выключается), вылазит при установке mint и elementaryOS, но их у меня получилось установить, однако при запуске светится логотип пол минуты и после тоже выключается, ошибка все та же. Фото ошибки по ссылке https://otvet.imgsmail.ru/download/270186982_950796e25c1bedd6f2296c86c4c0da20_800.jpg
и будет сидеть с одним ядром процессора из всех, збс
В биосе ничего такого нету, а при запуске установщика и отключении не помогло
С Live образа Linux Mint загрузиться можешь?
Выполни в эмуляторе терминала:
Выложи вывод сюда (или вставь в первое свое сообщение).
Ругается на USB порты. Скорее всего, usb-3 или usb-c. Попробуй засунуть флешку в usb-2 порт. Или, если возможно, отключить в биосе usb-3/usb-с.
Возможно, неправильно задается ОС в acpi. Попробуй загрузиться с параметрами ядра acpi_osi=! acpi_osi=’Windows 2016′
Думаю ядро старовато. Хорошо бы 5.4. Да еще двойная графика nvidia… Ты уверен что тебе нужен линукс?
Я читал что линукс не придирчив к железу, неужели проблема в этом?
Плюс я видел точно такие же ноутбуки, но с linux
линукс не придирчив к железу
сразу по формулировке понятно, что читал ты что-то вроде гламурного говнобложека для домохозяек
Надо было брать ноутбуки с linux. А не этот, на котором написано, что нужен «windows 10 pro для деловых»
Подскажите, как поменять параметры ядра acpi_osi, я не уверен, что делаю правильно.Mint установлен, но логотип висит минуту и потом выключается, может где то можно посмотреть текст ошибки?
Подскажите, как поменять параметры ядра acpi_osi
Тебе, во-первых, нужно более свежее ядро 5.4, это точно, у тебя процессор новее ядра. И не надо будет устанавливать acpi_osi.
Mint я не знаю, не помогу.
У тебя проц определяется как
Topology: Quad Core model: Intel Core i5-8300H bits: 64 type: MT MCP
arch: Kaby Lake rev: A L2 cache: 8192 KiB
Product Collection 8th Generation Intel® Core™ i5 Processors
Code Name Products formerly Coffee Lake
нет никакого «определяется», это вывод какой-то утилиты от васянов, которая вообще неизвестно откуда информацию берёт
во вторых четырёхядерные кофелейки(одна из их ревизий) это и есть тупо перемаркированные кабилейки
во вторых четырёхядерные кофелейки(одна из их ревизий) это и есть тупо перемаркированные кабилейки
Не придирчив в смысле не требует особо мощного. Это правда, та же Lubuntu 18.04 со старта потребляет менее 300 мегабайт оперативной памяти, что очень неплохо для 64-битной ОС. А вот новое железо в нём зачастую так себе работает.
Попробуй дистрибутив с наиболее свежим ядром. Я рекомендую Fedora Xfce или Mate.
нет никакого «определяется», это вывод какой-то утилиты от васянов, которая вообще неизвестно откуда информацию берёт
Если ядро ошибается, то остается только верить Анонимусу.
васян, плез. у тебя изначально была какая-то inxi, которая неизвестно иткуда информацию берёт
это только ты говоришь, что «ядро ошибается». ядро 5.0 вышло 3 March 2019, когда 8300H вышел Q2’18 а значит скорее всего ошибаешься тут ты
Давай попросим ТС привести вывод cat /proc/cpuinfo или методом, которому Ты доверяешь (есть оффтопиковые CPU-Z, Aida64 и юниксовый CPU-X).
в другом источнике пишут, что April 3, 2018
ну вот, у ядра был целый год, чтобы добавить поддержку
я просто знаю, что четырёхядерные кофелейки могут оказаться перемаркированным кебилейком
Спасибо за рекомендацию. Мате 19.10 запустилась, хотя и грузится она заметно медленнее, чем Мint при установке и в live-режиме. Так и должно быть, или это тоже какая-то проблема?
Это типичный пример ошибки DSDT. Решить можно несколькими способами:
О том как исправить DSDT не написано разве что на ближайшем заборе. Рядом на форуме полно таких тем. Используй уже поиск по форуму. У меня в бложике об этом написано несколько раз. Есть даже решения конкретных проблем.
Источник
[РЕШЕНО]Ошибки ACPI Error при загрузке базовой системы
Объясните пожалуйста, что это и если возможно, как это можно вылечить.
Заранее спасибо.
hathory
Объясните пожалуйста, что это и если возможно, как это можно вылечить.
hathory
А вот с «таблицы DSDT» совсем непонятно, мне технических знаний не хватает, биолог я по образованию.
У меня как то выскочила ошибка MCE, пришлось установить mcelog для контроля и в загрузочных логах стали выскакивать сообщения
Но на работу это не влияет и вообщем то сообщения, как пишут, безобидные. Посмотрел внимательнее твои сообщения.
Первые три относятся к Embeded Controller, подключенному к LPC bus (Low Pin Count bus) — что это за контроллер, нужно разбираться конкретно.
hathory
[ 0.366426] ACPI Error: No handler for Region [EC___] (ffff9b76470bf678) [EmbeddedContro1] (20160831/evreg ion-166)
[ 0.366431] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160831 L/exfldio-299)
[ 0.366435] ACPI Error: Method parse/execution failed [_SB.PCIO.LPCB.EC._REG I (Node ffff3b76470c0bl8), AE_NOT_EXIST (20160831/psparse-543)
hathory
ACPI Error: [_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NJT_FOUND (2016083l/psargS-359)
ACPI Error: Method parse/execution failed [_SB.PCIO.PEGO.PEGP.DD 02._BCL] (Node ffff9b76470flafO), AE_N0T_FOUND (20160831/psparse-543)
Что конкретно это означает — нужно смотреть саму таблицу, но смысла в этом не вижу, если все работает.
© 2006-2022, Русскоязычное сообщество Arch Linux.
Название и логотип Arch Linux ™ являются признанными торговыми марками.
Linux ® — зарегистрированная торговая марка Linus Torvalds и LMI.
Источник
Linux Mint Forums
Welcome to the Linux Mint forums!
[SOLVED] ACPI BIOS Error
[SOLVED] ACPI BIOS Error
Post by SoyDodger » Sun Mar 22, 2020 3:46 am
Running Mint 19.3, Kernel 5.x and I’ve tried reverting to earlier versions, no luck.
I hadn’t shut the computer down for a few days. It had run a few updates and restarted afterward just fine. This morning I started getting this message after boot: 
Trying an earlier kernel gave me the following: 
Followed by the ACPI stuff again, but there is also an issue of mint-vg not found:
The «mint-vg not found» part bugs me as I had this before. Did a clean install from new media, and now it’s happened again. I can’t get into the system so I don’t know how to run fsck, or what that is. Not sure what busybox is.
_____ _____ _____ _____ _____ _____
Just to give you some background, as you probably know, ACPI is the power regulation code in your motherboard’s BIOS/UEFI:
It’s suppose to be a standard that any operating system can properly implement. However, in typical Microsoft fashion, MS operating systems do not follow or properly implement the ACPI standard. Instead, MS gives motherboard manufacturers their own improperly implemented ACPI code for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS windows but all for other operating systems like linux there can be problems. Because of MS’s market dominance, the faulty ACPI implementation from MS has become the de facto industry standard. As a result, linux and other non-MS operating systems have to reverse engineer the faulty ACPI implementation from MS. That’s why you can see problems in linux with ACPI related functionality like suspend to ram, hibernate, etc.
Apparently, the ACPI related code in certain newer linux kernels has a problem with the typical BIOS/UEFI ACPI implementation on certain motherboards which is why we’re getting those error messages. Even though I get those error messages at the beginning of the boot process, I’ve had no problems with suspend/resume or any other ACPI related issues. Here’s another guy with the same problem so you are not alone:
The advice there was to not run in BIOS legacy mode by disabling UEFI but to run in UEFI mode instead with secure boot disabled.
This device is formerly Windows 10 and I had problems with drive formatting when I swapped over to EXT4 so I thought it may be that. I went back to my Mint installation and made sure I was using UEFI with secure boot disabled and fast boot disabled. Still no go.
Any suggestions on how to fix this issue?
PS. Apologies in advance if the images are too small to be readable, it hit the site limit of 640×480.
Источник