[SOLVED] ACPI errors on boot

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Locked
User avatar
danny_h69
Level 1
Level 1
Posts: 4
Joined: Thu Jul 20, 2017 8:03 am
Location: Australia

[SOLVED] ACPI errors on boot

Post by danny_h69 » Wed Aug 16, 2017 10:02 pm

Hi everyone. I am still very "green" when it comes to Linux (pun sort of intended) so please be patient.

I have previously run Linux Mint 18.1 Serena 64bit Cinnamon on this new SSD on the same machine without (these) issues. I have a separate SSD that has Win10 installed. The system boots and I can select the linux drive without any problems. The home folder is encrypted. I recently changed to Sonya and now that on boot the Mint logo comes up with the section to enter the password to setup the crypt (un-encrypt). Of note is that the logo and field appears large (using on-board graphics?) I am unable to enter anything into the field. I then have to re-start the machine and select the linux drive (via boot menu) and then the first option.

I then get the ACPI errors (listed below) before a command line that then lets me enter the encryption password. The disk d-encrypts happily and then onto welcome screen etc. The system then seems to work well.

Result of: inxi -F && dmesg | grep -i error (I found the query on another site with a similar problem but with no solution...)

Code: Select all

daniel@Minty ~ $ inxi -F && dmesg | grep -i error
System:    Host: Minty Kernel: 4.10.0-30-generic x86_64 (64 bit)
           Desktop: Cinnamon 3.4.6  Distro: Linux Mint 18.2 Sonya
Machine:   System: Gigabyte product: N/A
           Mobo: Gigabyte model: Z77X-UD5H
           Bios: American Megatrends v: F16h date: 07/11/2016
CPU:       Quad core Intel Core i7-3770K (-HT-MCP-) cache: 8192 KB 
           clock speeds: max: 3900 MHz 1: 1599 MHz 2: 1671 MHz 3: 1607 MHz
           4: 1621 MHz 5: 1624 MHz 6: 1623 MHz 7: 1837 MHz 8: 1616 MHz
Graphics:  Card: NVIDIA GK107 [GeForce GTX 650]
           Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 650/PCIe/SSE2
           GLX Version: 4.5.0 NVIDIA 384.59
Audio:     Card-1 Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Card-2 NVIDIA GK107 HDMI Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.0-30-generic
Network:   Card-1: Intel 82579V Gigabit Network Connection driver: e1000e
           IF: eno1 state: down mac: 94:de:80:61:78:7b
           Card-2: Qualcomm Atheros AR8161 Gigabit Ethernet driver: alx
           IF: enp7s0 state: up speed: 1000 Mbps duplex: full
           mac: 94:de:80:61:78:6b
Drives:    HDD Total Size: 2525.5GB (9.2% used)
           ID-1: /dev/sda model: CT250BX100SSD1 size: 250.1GB
           ID-2: /dev/sdb model: Crucial_CT275MX3 size: 275.1GB
           ID-3: /dev/sdc model: ST2000DM001 size: 2000.4GB
Partition: ID-1: / size: 221G used: 13G (6%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 472M used: 388M (87%) fs: ext2 dev: /dev/sdb1
           ID-3: swap-1 size: 34.31GB used: 0.00GB (0%) fs: swap dev: /dev/dm-3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 36C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 277 Uptime: 40 min Memory: 1763.0/32130.1MB
           Client: Shell (bash) inxi: 2.2.35 
[    1.166429] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.166513] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff935d7e0dc1e0), AE_NOT_FOUND (20160930/psparse-543)
[    1.166632] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.166724] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff935d7e0dcd48), AE_NOT_FOUND (20160930/psparse-543)
[    1.166830] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.166902] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff935d7e0dcc58), AE_NOT_FOUND (20160930/psparse-543)
[    1.167007] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.167076] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff935d7e0dc2f8), AE_NOT_FOUND (20160930/psparse-543)
[    1.167667] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.167741] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff935d7e0dc2f8), AE_NOT_FOUND (20160930/psparse-543)
[    1.167841] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.167911] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff935d7e0dcc58), AE_NOT_FOUND (20160930/psparse-543)
[    1.168779] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.168873] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff935d7e0dc1e0), AE_NOT_FOUND (20160930/psparse-543)
[    1.188180] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160930/psargs-359)
[    1.188286] ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff935d7e0dcd48), AE_NOT_FOUND (20160930/psparse-543)
[   17.804662] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
daniel@Minty ~ $
I was going to just re-install Serena, but I thought I'd give the forum a try first. :)

Ideally I just want to be able to select the linux drive and have the mint logo and logon screen come up and work from there. Any thoughts?

Regards,

Dan.
Last edited by danny_h69 on Sat Aug 19, 2017 4:49 am, edited 2 times in total.

User avatar
catweazel
Level 19
Level 19
Posts: 9505
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: ACPI errors on boot

Post by catweazel » Wed Aug 16, 2017 10:10 pm

Code: Select all

System: Host: Minty Kernel: 4.10.0-30-generic x86_64 (64 bit)
It's your kernel. Either drop it back to pre 4.9 or go up to 4.11 and try that, or if everything is running ok, ignore it.

https://bugzilla.redhat.com/show_bug.cgi?id=1413342
https://bugzilla.kernel.org/show_bug.cgi?id=192111
https://bugs.mageia.org/show_bug.cgi?id=20090
¡uʍop ǝpısdn sı buıɥʇʎɹǝʌǝ os ɐıןɐɹʇsnɐ ɯoɹɟ ɯ,ı

User avatar
danny_h69
Level 1
Level 1
Posts: 4
Joined: Thu Jul 20, 2017 8:03 am
Location: Australia

Re: ACPI errors on boot

Post by danny_h69 » Thu Aug 17, 2017 9:37 pm

Thanks Catweazel. I'll try that today...

Ahh, that's a show that brings back memories... and probably gives our ages away. :)

Cheers

Dan

User avatar
danny_h69
Level 1
Level 1
Posts: 4
Joined: Thu Jul 20, 2017 8:03 am
Location: Australia

Re: ACPI errors on boot

Post by danny_h69 » Sat Aug 19, 2017 4:48 am

Ok. Tried changing kernels, but didn't work. I had some suspicion that there was some sort of error or conflict with the graphics card drivers. When I chose the Linux distro/drive the Linux Mint logo and encryption password field looked like it was using very basic graphics and wouldn't allow me to enter anything into the field. The other ACPI errors came up after a couple of attempts to login.

I was running the current nVidia drivers, so I reverted back to the xserver-xorg-video-nouveau driver and rebooted. Lo and behold, correct graphics resolution and a usable password field. Entered passwords and hey presto logged in no problems.

I could have left it there, but I wanted to be able to use the nVidia drivers.

Here's the solution I found that worked. https://community.linuxmint.com/tutorial/view/176

Basically I opened the /etc/default/grub file using Nemo to gain elevated privileges.

Added "nouveau.blacklist=1" to the line "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Should look something like this: "GRUB_CMDLINE_LINUX_DEFAULT="nouveau.blacklist=1 quiet splash" acpi=force apm=power_off"

Saved the grub file then rebooted. Then reverted back to nVidia drivers and rebooted again. Now it works! Excellent... one step closer to giving Microgreed the flick once and for all.

Hope this helps someone else out there.

Cheers

Dan

User avatar
[vanicci]
Level 1
Level 1
Posts: 4
Joined: Tue Mar 20, 2018 12:42 pm
Location: United Kingdom

Re: [SOLVED] ACPI errors on boot

Post by [vanicci] » Tue Mar 20, 2018 1:26 pm

Hi Dan, glad that you fix the problem.

I'm currently experiencing the same problem and I am not a programmer so it's rather challenging for me to understand the steps that you had to go through.

I have a question about this:
"Basically I opened the /etc/default/grub file using Nemo to gain elevated privileges.
Added "nouveau.blacklist=1" to the line "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Should look something like this: "GRUB_CMDLINE_LINUX_DEFAULT="nouveau.blacklist=1 quiet splash" acpi=force apm=power_off"
Saved the grub file then rebooted. Then reverted back to nVidia drivers and rebooted again. Now it works! Excellent... one step closer to giving Microgreed the flick once and for all."


Where do you "open" the /etc/default/grub file? Do I need to go to Boot Manager?

I am trying to explore Linux Mint dual booting my old laptop (bought Nov 2015) as I heard many great things about Linux. Since I am just starting to learn Python I would like to play around with Linux Mint for the first time.

My machine is: https://goo.gl/XKkn9u
ACER Aspire F5-571 15.6" Laptop - Intel® Core™ i3-5005U (5th Generation) - 4GB Ram - 1TB HDD - DVD/RW - Windows 10

So I installed Linux Mint 18.3 Sylvia into my USB using Rufus (followed a tutorial online).

At first, I used [UEFI] as the "Boot Mode" but when I ran it, it was just black screen and nothing else.

I read somewhere to change it to [Legacy], so I did.

When I started booting the USB, I just see all these "ACPI errors."

See screenshot here:
https://ibb.co/ky3jxx

I also tried changing the USB ports - it didn't work.
I even bought a new USB and installed "fresh" - didn't work neither.

If you can just direct me where to "open" the /etc/default/grub file and the rest of the steps, that would be much appreciated.

Regards,
[vanicci]
I am a New Linux User. Trying to gain my knowledge in mastering the system with your guidance. Thank you! :)

User avatar
Moem
Level 19
Level 19
Posts: 9357
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: [SOLVED] ACPI errors on boot

Post by Moem » Tue Mar 20, 2018 1:41 pm

[vanicci] wrote:
Tue Mar 20, 2018 1:26 pm
Hi Dan, glad that you fix the problem.

I'm currently experiencing the same problem and I am not a programmer so it's rather challenging for me to understand the steps that you had to go through.
The poster hasn't been back here since their problem was solved, so you might be better off posting a new thread. Threads that are marked as solved don't always attract as much attention.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

User avatar
[vanicci]
Level 1
Level 1
Posts: 4
Joined: Tue Mar 20, 2018 12:42 pm
Location: United Kingdom

Re: [SOLVED] ACPI errors on boot

Post by [vanicci] » Tue Mar 20, 2018 4:18 pm

Thank you, Moem! I just created a new thread. :)
I am a New Linux User. Trying to gain my knowledge in mastering the system with your guidance. Thank you! :)

jak_jak221
Level 1
Level 1
Posts: 1
Joined: Sat Aug 31, 2019 4:27 pm

Re: [SOLVED] ACPI errors on boot

Post by jak_jak221 » Sat Aug 31, 2019 4:39 pm

I had a similar problem like this. After entering emergency mode and running journalctl -xb I received ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364). This happened after I had cloned my disk using dd. After running the system in recovery mode I discovered an error stating that the previous UUID assigned to the disk that contains the clone could no longer be found. I commented out the line in the fstab file and restarted the computer. The system ran as normal. While dd did clone the data from the original disk to the new disk, it also carried over the UUID and since the fstab file contained the old UUID the computer couldn't find it and launched into emergency mode. Watch out for this if you are new to dd.

Locked

Return to “Installation & Boot”