Acpi error aborting method sb osc

Forum rules Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

newgreen

Level 1
Level 1
Posts: 8
Joined: Fri Jul 10, 2020 6:09 pm

ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Newbie needing help after upgrading from Linux mint 19.3 to Linux Mint 20
Issue while booting
Dual boot Win 7 / Linux Mint 20 system
Followed upgrade instructions,
After upgrade to LM20, system boots, Grub boot select screen appears
After pressing enter key on keyboard to select Linux mint 20, I get the following message on the screen (see below). Message repeats 3 times dimmer each time for a total of about 8 seconds or so and then Linux mint 20 starts normally.

Code: Select all

[    0.408038] ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] .
AE_NOT_FOUND (20190816/psargs-330)
ACPI BIOS Error: Aborting method _SB._OSC due to previous error AE_NOT_FOUND (20190816/psargs-529)

Does anyone know what this message even mean and how to fix this?
Any help with this would be appreciated.

Thank you

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

User avatar

arvy

Level 6
Level 6
Posts: 1227
Joined: Sat Mar 26, 2016 11:22 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by arvy » Fri Jul 10, 2020 6:56 pm

ACPI errors of that nature abound in various OEM implementations and they are generally harmless apart from the (usually brief) «hiccup» during the start-up process. See here for just a few other examples and here. Their «meaning» is often nothing more than just a quick report of OEM sloppiness and, unless they give rise to some actual operational problems, they seldom get corrected by firmware updates. LM 20’s default config seems to make them somewhat more visible than its predecessor. If you want to pursue the issue in greater depth, see Debugging ACPI.

System: Asus ROG Maximus XI Code mobo, Intel i9-9900K CPU, Nvidia GTX1080 GPU, 32 GB DDR4-3600 RAM, Sumsung Pro 2x512GB NVMe & 3x1TB SSD, Multiboot

newgreen

Level 1
Level 1
Posts: 8
Joined: Fri Jul 10, 2020 6:09 pm

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by newgreen » Fri Jul 10, 2020 7:17 pm

Thanks for the info, but this problem wasn’t there before the upgrade to LM20. I was running LM19.3 with most up to date kernel and latest updates with no boot issues. After the upgrade to LM20, now this appears; very strange. If this was a real firmware or BIOS problem, I would expect the issue to be there with previous versions of Linux Mint, which it wasn’t. Something to do with the upgrade to LM20, what, I don’t know.

User avatar

arvy

Level 6
Level 6
Posts: 1227
Joined: Sat Mar 26, 2016 11:22 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by arvy » Fri Jul 10, 2020 7:30 pm

Well, if you choose to believe that your system’s ACPI BIOS error was actually created or falsified (rather than just more aggressively detected and reported) by LM 20, I suppose there’s no real substantive harm in that either. I’ve told you where to find debugging information if you want it.

System: Asus ROG Maximus XI Code mobo, Intel i9-9900K CPU, Nvidia GTX1080 GPU, 32 GB DDR4-3600 RAM, Sumsung Pro 2x512GB NVMe & 3x1TB SSD, Multiboot

User avatar

arvy

Level 6
Level 6
Posts: 1227
Joined: Sat Mar 26, 2016 11:22 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by arvy » Fri Jul 10, 2020 9:47 pm

You’re making a mountain out of a molehill, but if you insist — _SB._OSC is used to convey platform-wide OSPM capabilities (a term defined in the ACPI specification) to the platform firmware for power management purposes, more specifically in order to meet firmware requirements for the D3cold power sub-state. More than you ever wanted to know (or certainly more that I ever wanted to know) about the technical details of device power management and its firmware requirements can be found here according to Microsoft’s self-proclaimed «expertise» on the subject.

System: Asus ROG Maximus XI Code mobo, Intel i9-9900K CPU, Nvidia GTX1080 GPU, 32 GB DDR4-3600 RAM, Sumsung Pro 2x512GB NVMe & 3x1TB SSD, Multiboot

newgreen

Level 1
Level 1
Posts: 8
Joined: Fri Jul 10, 2020 6:09 pm

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by newgreen » Fri Jul 10, 2020 11:12 pm

I do like to try and at least have some basic understanding of what’s going on, so I thank you for the info you provided. Further, I did look at the links you provided and I’ll dig a little deeper into the pages you provided. If I’m unable to resolve the actual error message/system hang, do you know of a way to suppress or ‘MUTE» / bypass the checking and reporting of this error so as:
1) it doesn’t slow down the boot time by 8 seconds
2) it doesn’t display it.

Ideally, I’d like to eliminate this by way of editing the code in a file without messing up the Grub dual boot menu at boot time?

As I mentioned before, I had installed a couple of prior versions of Linux Mint and have never experienced any 8 second hang or error messages at boot time. It goes beyond just an error message when the system hangs for 8 seconds and boot time is slowed down. I have Linux Mint 19.3 on another machine and for now, I’ll stick with that.

In my view, whatever the reason for this, if other versions of Mint can suppress/overcome/not check for this and not hang the system at startup, it makes LM20 boot process look and feel very sloppy. If this error is of little significance to the working of the OS, then I don’t want LM20 to hang the system to check for this error. On the other hand, if this error is of significance with it’s implications currently unknown or unclear to me, then a fix is required to fix this.

Thanks for the several replies you posted!

User avatar

arvy

Level 6
Level 6
Posts: 1227
Joined: Sat Mar 26, 2016 11:22 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by arvy » Fri Jul 10, 2020 11:39 pm

Well, did you try any of the kernel loading parameters suggested in that debugging link that I gave you? The first one («acpi=off») will confirm that it really is (or isn’t) an ACPI issue and, if it is, you can narrow it down from there.

System: Asus ROG Maximus XI Code mobo, Intel i9-9900K CPU, Nvidia GTX1080 GPU, 32 GB DDR4-3600 RAM, Sumsung Pro 2x512GB NVMe & 3x1TB SSD, Multiboot

newgreen

Level 1
Level 1
Posts: 8
Joined: Fri Jul 10, 2020 6:09 pm

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by newgreen » Sat Jul 11, 2020 4:01 am

Yes, after pressing «e» key on my keyboard while at at the Grub menu screen, another screen appeared. I used my down arrow key to go to the «Linux» line, and at the end of the line, I added the following:

Then, I pressed F10 to continue, and I got another error message instead of the original one:

Code: Select all

[   0.506649] NMI: PCI system error (SERR) for reason a1 on CPU 0.
[   0.506650] Dazed and confused, but trying to continue

After some seconds at that error message, the boot sequence continued and Linux Mint 20 appear to start normally.

«Dazed and confused but trying to continue» ? I think I’m a little «Dazed and confused but trying to continue» to solve this problem, if I can add a little humour to this :)

Anyway, no further along on this at this point.

Thanks

User avatar

arvy

Level 6
Level 6
Posts: 1227
Joined: Sat Mar 26, 2016 11:22 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by arvy » Sat Jul 11, 2020 6:13 am

I’m sorry, but you said that you wanted to pursue the issue and so I’ve given you a link to the debugging procedures that will let you do that. Each one of them explains, at least briefly, its own significance and it’s up to you to draw the appropriate logical conclusions as applicable to your case. The first one («acpi=off») is not intended to be regarded as any kind of complete or final answer. As I said, it just confirms that the issue really does originate in your system’s ACPI implementation. It has done exactly that (nothing more) based on the criteria as stated for itself (i.e., if the error is the same with ACPI enabled and disabled, this may not be an ACPI issue). So you are, in fact, that much «further along» at least.

Carry on with the other debugging procedures at your own discretion, but take careful note of what each says about itself if you want to be able to draw any useful conclusions from the exercise. And note also that none of them is actually going to fix any OEM firmware issue, although one of them may let you suppress its detection and error display without being too obtrusive in other respects.

System: Asus ROG Maximus XI Code mobo, Intel i9-9900K CPU, Nvidia GTX1080 GPU, 32 GB DDR4-3600 RAM, Sumsung Pro 2x512GB NVMe & 3x1TB SSD, Multiboot

smbulius

Level 1
Level 1
Posts: 3
Joined: Mon Nov 16, 2020 2:36 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by smbulius » Fri Apr 09, 2021 2:01 pm

Same problem on my PC. I installed Linux Mint, Ubuntu, Debian. In all OS is same problem (kernel 4.x to 5.x versions). I didn’t try the older version of kernels >4.x.

MB: Gigabyte x299 WU8 CPU: i9 10gen. BIOS: the latest version.

Please share experiences on how this problem can be solved!

Could this be the reason that the system is not working KVM (Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled)??? My Linux Mint show that VT-X is Disabled, but on BIOS is enabled. Windows 10 works great, but Linux Mint dont alow VTx?!?

legacypowers

Level 4
Level 4
Posts: 276
Joined: Sat Dec 19, 2020 8:53 am

Re: ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1] After Upgrading to LM20

Post

by legacypowers » Thu Dec 09, 2021 3:50 pm

smbulius wrote: ↑

Fri Apr 09, 2021 2:01 pm


Could this be the reason that the system is not working KVM (Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled)??? My Linux Mint show that VT-X is Disabled, but on BIOS is enabled. Windows 10 works great, but Linux Mint dont alow VTx?!?

Highly doubt so, on 5 linux box that i have at home 3 of them spit those errors at boot time, don’t bother with it.

Terminal — zsh wrote:
╭─legacy@forums.linuxmint.com
╰─➜ _

If that makes any difference I’m using TLP for better battery life alongside with KDE power management tools, but the configs are pretty much default with all the settings commented out:

# ------------------------------------------------------------------------------
# /etc/tlp.conf - TLP user configuration
# See full explanation: https://linrunner.de/en/tlp/docs/tlp-configuration.html
#
# New configuration scheme (TLP 1.3). Settings are read in the following order:

# 1. Intrinsic defaults
# 2. /etc/tlp.d/*.conf - Drop-in customization snippets
# 3. /etc/tlp.conf     - User configuration (this file)
#
# Notes:
# - In case of identical parameters, the last occurence has precedence
# - This also means, parameters enabled here will override anything else
# - IMPORTANT: all parameters here are disabled, remove the leading '#'
#   to enable them; shown values may be suggestions rather than defaults
# - Default *: intrinsic default that is effective when the parameter is missing
#     or disabled by a leading '#'; use PARAM="" to disable an intrinsic default
# - Default <none>: do nothing or use kernel/hardware defaults

# ------------------------------------------------------------------------------
# tlp - Parameters for power saving

# Set to 0 to disable, 1 to enable TLP.
# Default: 1

#TLP_ENABLE=1

# Operation mode when no power supply can be detected: AC, BAT.
# Concerns some desktop and embedded hardware only.
# Default: <none>

#TLP_DEFAULT_MODE=AC

# Operation mode select: 0=depend on power source, 1=always use TLP_DEFAULT_MODE
# Note: use in conjunction with TLP_DEFAULT_MODE=BAT for BAT settings on AC.
# Default: 0

#TLP_PERSISTENT_DEFAULT=0

# Power supply class to ignore when determining operation mode: AC, BAT.
# Note: try on laptops where operation mode AC/BAT is incorrectly detected.
# Default: <none>

#TLP_PS_IGNORE=BAT

# Seconds laptop mode has to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
# Default: 0 (AC), 2 (BAT)

#DISK_IDLE_SECS_ON_AC=0
#DISK_IDLE_SECS_ON_BAT=2

# Dirty page values (timeouts in secs).
# Default: 15 (AC), 60 (BAT)

#MAX_LOST_WORK_SECS_ON_AC=15
#MAX_LOST_WORK_SECS_ON_BAT=60

# Note: CPU parameters below are disabled by default, remove the leading #
# to enable them, otherwise kernel defaults will be used.
#
# Select a CPU frequency scaling governor.
# Intel Core i processor with intel_pstate driver:
#   powersave(*), performance.
# Other hardware with acpi-cpufreq driver:
#   ondemand(*), powersave, performance, conservative, schedutil.
# (*) is recommended.
# Use tlp-stat -p to show the active driver and available governors.
# Important:
#   powersave for intel_pstate and ondemand for acpi-cpufreq are power
#   efficient for *almost all* workloads and therefore kernel and most
#   distributions have chosen them as defaults. If you still want to change,
#   you should know what you're doing!
# Default: <none>

#CPU_SCALING_GOVERNOR_ON_AC=powersave
#CPU_SCALING_GOVERNOR_ON_BAT=powersave

# Set the min/max frequency available for the scaling governor.
# Possible values depend on your CPU. For available frequencies see
# the output of tlp-stat -p.
# Default: <none>

#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0

# Set Intel CPU energy/performance policies HWP.EPP and EPB:
#   performance, balance_performance, default, balance_power, power
# Values are given in order of increasing power saving.
# Notes:
# - Requires an Intel Core i processor
# - HWP.EPP requires kernel 4.10 and intel_pstate driver
# - EPB requires kernel 5.2 or module msr and x86_energy_perf_policy
#   from linux-tools
# - When HWP.EPP is available, EPB is not set
# Default: balance_performance (AC), balance_power (BAT)

#CPU_ENERGY_PERF_POLICY_ON_AC=balance_performance
#CPU_ENERGY_PERF_POLICY_ON_BAT=balance_power

# Set Intel CPU P-state performance: 0..100 (%).
# Limit the max/min P-state to control the power dissipation of the CPU.
# Values are stated as a percentage of the available performance.
# Requires an Intel Core i processor with intel_pstate driver.
# Default: <none>

#CPU_MIN_PERF_ON_AC=0
#CPU_MAX_PERF_ON_AC=100
#CPU_MIN_PERF_ON_BAT=0
#CPU_MAX_PERF_ON_BAT=30

# Set the CPU "turbo boost" feature: 0=disable, 1=allow
# Requires an Intel Core i processor.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
# Default: <none>

#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0

# Minimize number of used CPU cores/hyper-threads under light load conditions:
#   0=disable, 1=enable.
# Default: 0 (AC), 1 (BAT)

#SCHED_POWERSAVE_ON_AC=0
#SCHED_POWERSAVE_ON_BAT=1

# Kernel NMI Watchdog:
#   0=disable (default, saves power), 1=enable (for kernel debugging only).
# Default: 0

#NMI_WATCHDOG=0

# Change CPU voltages aka "undervolting" - Kernel with PHC patch required.
# Frequency voltage pairs are written to:
#   /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
# Default: <none>.

#PHC_CONTROLS="F:V F:V F:V F:V"

# Disk devices; separate multiple devices with spaces.
# Devices can be specified by disk ID also (lookup with: tlp diskid).
# Note: DISK parameters below are effective only when this option is configured.
# Default: "nvme0n1 sda"

#DISK_DEVICES="nvme0n1 sda"

# Disk advanced power management level: 1..254, 255 (max saving, min, off).
# Levels 1..127 may spin down the disk; 255 allowable on most drives.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the hardware default for the particular disk.
# Default: 254 (AC), 128 (BAT)

#DISK_APM_LEVEL_ON_AC="254 254"
#DISK_APM_LEVEL_ON_BAT="128 128"

# Hard disk spin down timeout:
#   0:        spin down disabled
#   1..240:   timeouts from 5s to 20min (in units of 5s)
#   241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# See 'man hdparm' for details.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the hardware default for the particular disk.
# Default: <none>

#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"

# Select I/O scheduler for the disk devices.
# Multi queue (blk-mq) schedulers:
#   mq-deadline(*), none, kyber, bfq
# Single queue schedulers:
#   deadline(*), cfq, bfq, noop
# (*) recommended.
# Separate values for multiple disks with spaces. Use the special value 'keep'
# to keep the kernel default scheduler for the particular disk.
# Notes:
# - Multi queue (blk-mq) may need kernel boot option 'scsi_mod.use_blk_mq=1'
#   and 'modprobe mq-deadline-iosched|kyber|bfq' on kernels < 5.0
# - Single queue schedulers are legacy now and were removed together with
#   the old block layer in kernel 5.0
# Default: keep

#DISK_IOSCHED="mq-deadline mq-deadline"

# AHCI link power management (ALPM) for disk devices:
#   min_power, med_power_with_dipm(*), medium_power, max_performance.
# (*) Kernel >= 4.15 required, then recommended.
# Multiple values separated with spaces are tried sequentially until success.
# Default:
#  - "med_power_with_dipm max_performance" (AC)
#  - "med_power_with_dipm min_power" (BAT)

#SATA_LINKPWR_ON_AC="med_power_with_dipm max_performance"
#SATA_LINKPWR_ON_BAT="med_power_with_dipm min_power"

# Exclude host devices from AHCI link power management.
# Separate multiple hosts with spaces.
# Default: <none>

#SATA_LINKPWR_BLACKLIST="host1"

# Runtime Power Management for AHCI host and disks devices:
#   on=disable, auto=enable.
# EXPERIMENTAL ** WARNING: auto may cause system lockups/data loss.
# Default: <none>

#AHCI_RUNTIME_PM_ON_AC=on
#AHCI_RUNTIME_PM_ON_BAT=on

# Seconds of inactivity before disk is suspended.
# Note: effective only when AHCI_RUNTIME_PM_ON_AC/BAT is activated.
# Default: 15

#AHCI_RUNTIME_PM_TIMEOUT=15

# PCI Express Active State Power Management (PCIe ASPM):
#   default(*), performance, powersave, powersupersave.
# (*) keeps BIOS ASPM defaults (recommended)
# Default: <none>

#PCIE_ASPM_ON_AC=default
#PCIE_ASPM_ON_BAT=default

# Set the min/max/turbo frequency for the Intel GPU.
# Possible values depend on your hardware. For available frequencies see
# the output of tlp-stat -g.
# Default: <none>

#INTEL_GPU_MIN_FREQ_ON_AC=0
#INTEL_GPU_MIN_FREQ_ON_BAT=0
#INTEL_GPU_MAX_FREQ_ON_AC=0
#INTEL_GPU_MAX_FREQ_ON_BAT=0
#INTEL_GPU_BOOST_FREQ_ON_AC=0
#INTEL_GPU_BOOST_FREQ_ON_BAT=0

# Radeon graphics clock speed (profile method): low, mid, high, auto, default;
# auto = mid on BAT, high on AC.
# Default: default

#RADEON_POWER_PROFILE_ON_AC=default
#RADEON_POWER_PROFILE_ON_BAT=default

# Radeon dynamic power management method (DPM): battery, performance.
# Default: <none>

#RADEON_DPM_STATE_ON_AC=performance
#RADEON_DPM_STATE_ON_BAT=battery

# Radeon DPM performance level: auto, low, high; auto is recommended.
# Note: effective only when RADEON_DPM_STATE_ON_AC/BAT is activated.
# Default: auto

#RADEON_DPM_PERF_LEVEL_ON_AC=auto
#RADEON_DPM_PERF_LEVEL_ON_BAT=auto

# WiFi power saving mode: on=enable, off=disable; not supported by all adapters.
# Default: off (AC), on (BAT)

#WIFI_PWR_ON_AC=off
#WIFI_PWR_ON_BAT=on

# Disable wake on LAN: Y/N.
# Default: Y

#WOL_DISABLE=Y

# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables, >=1 enables power saving (recommended: 1).
# Default: 0 (AC), 1 (BAT)

#SOUND_POWER_SAVE_ON_AC=0
#SOUND_POWER_SAVE_ON_BAT=1

# Disable controller too (HDA only): Y/N.
# Note: effective only when SOUND_POWER_SAVE_ON_AC/BAT is activated.
# Default: Y

#SOUND_POWER_SAVE_CONTROLLER=Y

# Power off optical drive in UltraBay/MediaBay: 0=disable, 1=enable.
# Drive can be powered on again by releasing (and reinserting) the eject lever
# or by pressing the disc eject button on newer models.
# Note: an UltraBay/MediaBay hard disk is never powered off.
# Default: 0

#BAY_POWEROFF_ON_AC=0
#BAY_POWEROFF_ON_BAT=0

# Optical drive device to power off
# Default: sr0

#BAY_DEVICE="sr0"

# Runtime Power Management for PCI(e) bus devices: on=disable, auto=enable.
# Default: on (AC), auto (BAT)

#RUNTIME_PM_ON_AC=on
#RUNTIME_PM_ON_BAT=auto

# Exclude PCI(e) device adresses the following list from Runtime PM
# (separate with spaces). Use lspci to get the adresses (1st column).
# Default: <none>

#RUNTIME_PM_BLACKLIST="bb:dd.f 11:22.3 44:55.6"

# Exclude PCI(e) devices assigned to the listed drivers from Runtime PM.
# Default when unconfigured is "amdgpu nouveau nvidia radeon" which
# prevents accidential power-on of dGPU in hybrid graphics setups.
# Separate multiple drivers with spaces.
# Default: "amdgpu mei_me nouveau nvidia pcieport radeon", use "" to disable
# completely.

#RUNTIME_PM_DRIVER_BLACKLIST="amdgpu mei_me nouveau nvidia pcieport radeon"

# Set to 0 to disable, 1 to enable USB autosuspend feature.
# Default: 1

#USB_AUTOSUSPEND=1

# Exclude listed devices from USB autosuspend (separate with spaces).
# Use lsusb to get the ids.
# Note: input devices (usbhid) are excluded automatically
# Default: <none>

#USB_BLACKLIST="1111:2222 3333:4444"

# Bluetooth devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 0

#USB_BLACKLIST_BTUSB=0

# Phone devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude (enable charging).
# Default: 0

#USB_BLACKLIST_PHONE=0

# Printers are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 1

#USB_BLACKLIST_PRINTER=1

# WWAN devices are excluded from USB autosuspend:
#   0=do not exclude, 1=exclude.
# Default: 0

#USB_BLACKLIST_WWAN=0

# Include listed devices into USB autosuspend even if already excluded
# by the blacklists above (separate with spaces). Use lsusb to get the ids.
# Default: <none>

#USB_WHITELIST="1111:2222 3333:4444"

# Set to 1 to disable autosuspend before shutdown, 0 to do nothing
# Note: use as a workaround for USB devices that cause shutdown problems.
# Default: 0

#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=0

# Restore radio device state (Bluetooth, WiFi, WWAN) from previous shutdown
# on system startup: 0=disable, 1=enable.
# Note: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
#   are ignored when this is enabled.
# Default: 0

#RESTORE_DEVICE_STATE_ON_STARTUP=0

# Radio devices to disable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
# Default: <none>

#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"

# Radio devices to enable on startup: bluetooth, wifi, wwan.
# Separate multiple devices with spaces.
# Default: <none>

#DEVICES_TO_ENABLE_ON_STARTUP="wifi"

# Radio devices to disable on shutdown: bluetooth, wifi, wwan.
# Note: use as a workaround for devices that are blocking shutdown.
# Default: <none>

#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"

# Radio devices to enable on shutdown: bluetooth, wifi, wwan.
# (to prevent other operating systems from missing radios).
# Default: <none>

#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"

# Radio devices to enable on AC: bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_ENABLE_ON_AC="bluetooth wifi wwan"

# Radio devices to disable on battery: bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_DISABLE_ON_BAT="bluetooth wifi wwan"

# Radio devices to disable on battery when not in use (not connected):
#   bluetooth, wifi, wwan.
# Default: <none>

#DEVICES_TO_DISABLE_ON_BAT_NOT_IN_USE="bluetooth wifi wwan"

# Battery charge thresholds (ThinkPad only).
# May require external kernel module(s), refer to the output of tlp-stat -b.
# Charging starts when the remaining capacity falls below the
# START_CHARGE_THRESH value and stops when exceeding the STOP_CHARGE_THRESH
# value.

# Main / Internal battery (values in %)
# Default: <none>

#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80

# Ultrabay / Slice / Replaceable battery (values in %)
# Default: <none>

#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80

# Restore charge thresholds when AC is unplugged: 0=disable, 1=enable.
# Default: 0

#RESTORE_THRESHOLDS_ON_BAT=1

# Battery feature drivers: 0=disable, 1=enable
# Default: 1 (all)

#NATACPI_ENABLE=1
#TPACPI_ENABLE=1
#TPSMAPI_ENABLE=1

# ------------------------------------------------------------------------------
# tlp-rdw - Parameters for the radio device wizard

# Possible devices: bluetooth, wifi, wwan.
# Separate multiple radio devices with spaces.
# Default: <none> (for all parameters below)

# Radio devices to disable on connect.

#DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
#DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
#DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"

# Radio devices to enable on disconnect.

#DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""

# Radio devices to enable/disable when docked.

#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""

# Radio devices to enable/disable when undocked.

#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""

Using Ubuntu 22.04 on kernel 5.15.0-37-generic, I suddenly get numerous errors during boot.

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20210730/psargs-330)
ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

After this started appearing, the suspend function started acting weird. When entering suspend, it turns off the display, immediately turns back on and stays on. If I suspend again, it does it successfully. But upon wake up, it doesn’t prompt for a password, it just goes straight to the desktop.

I found an older kernel bug report, which patched it in 5.12, but it seems it was reverted back. https://bugzilla.kernel.org/show_bug.cgi?id=213023

  • #1

I have a Dell Poweredge 2950 and when I boot I get this:

[ 0.255247] ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size
[ 0.812413] ACPI BIOS Error (bug): Could not resolve symbol [_SB._OSC.CDW1], AE_NOT_FOUND (20190816/psargs-330)
[ 0.812489] ACPI Error: Aborting method _SB._OSC due to previous error (AE_NOT_FOUND) (20160816/psparse-531)
[ 1.540833] ERST: Failed to get Error Log Address Range.

Now I have only encountered this issue when using 6.3 that I am aware of, I was able to roll back to an earlier version of Proxmox and get it to boot but after
a dist-upgrade again it may boot once or twice but then I will get this, I was running this in a cluster but had to remove it. I am going to try installing 6.2 and see if I encounter these errors but from what I can tell this happened after the newest kernel update, and I can’t boot because it just hangs after that message. Any help would be greatly appreciated because I am trying to run 2 nodes and using a proxmox backup server and I prefer to keep all my systems up to date.

Alwin

Alwin

Proxmox Retired Staff


  • #2

I am going to try installing 6.2 and see if I encounter these errors but from what I can tell this happened after the newest kernel update

You can just install an older kernel, no need to reinstall the host.

[ 0.255247] ACPI: SPCR: Unexpected SPCR Access Width. Defaulting to byte size

Do you have some serial console port redirection (SPCR) configured? Also check that the BIOS is up-to-date and if there is some serial port settings.

  • #3

You can just install an older kernel, no need to reinstall the host.

Do you have some serial console port redirection (SPCR) configured? Also check that the BIOS is up-to-date and if there is some serial port settings.

I would install an older kernel but can’t even get into the OS, the only shell I can get to is the GRUB shell, like I said it freezes at boot right away, there is no way to get to the BASH prompt…..

BIOS is the latest revision, I have already checked, and I have messed with the SCPR, tried all settings possible, in the bios but doesn’t get me passed this issue, like I stated before, everything booted fine until the latest kernel update, I have to reinstall because I can’t get to the BASH shell

Alwin

Alwin

Proxmox Retired Staff


  • #4

I would install an older kernel but can’t even get into the OS, the only shell I can get to is the GRUB shell, like I said it freezes at boot right away, there is no way to get to the BASH prompt…..

GRUB doesn’t show the previous kernel? Else you can try to boot with the 6.2 ISO. If you start it in debug mode and abort the wizard, it will drop you on a full shell.

  • #5

That’s exactly what I was going to do, boot live and try the debug mode with 6.2 to try to drop into a shell, I am at school now so won’t be able to try this until later. Grub doesn’t show the previous kernel now after using it before and applying another update, and then I ran apt autoremove and apt autoclean, and it must have taken that kernel out when I did that. I’m just confused why this happened after the kernel update, if I know why I may be able to fix it plus like I stated I like to keep everything up to date so if I am using an older kernel and update again won’t it update to the new kernel?

Alwin

Alwin

Proxmox Retired Staff


  • #6

I am using an older kernel and update again won’t it update to the new kernel?

You should be able to keep the specific kernel package with apt-mark hold pve-kernel-<version>. Anyway, you can install the older kernel again, they are kept on the repository.

  • #7

Thank you, I was able to get proxmox back up and running again, I appreciate your help!!

  • #8

I was able to find a workaround that allows me to use the new kernel that I wanted to post here in case anyone ran into this issue, you can turn acpi off by modifying the grub file.

in shell run:
nano /etc/default/grub

Change line:
GRUB_CMDLINE_LINUX_DEFAULT=»quiet»
to
GRUB_CMDLINE_LINUX_DEFAULT=»quiet acpi=off»
save with ctrl-x, then Y, and enter

run in shell:
update-grub
reboot

This makes it skip acpi and will boot normally.

Please mark this thread as closed!
Again, Thank you for everything!

Last edited: Dec 9, 2020

  • #9

I was able to find a workaround that allows me to use the new kernel that I wanted to post here in case anyone ran into this issue, you can turn acpi off by modifying the grub file.

in shell run:
nano /etc/default/grub

Change line:
GRUB_CMDLINE_LINUX_DEFAULT=»quiet»
to
GRUB_CMDLINE_LINUX_DEFAULT=»quiet acpi=off»
save with ctrl-x, then Y, and enter

run in shell:
update-grub
reboot

This makes it skip acpi and will boot normally.

Please mark this thread as closed!
Again, Thank you for everything!

Unfortunately adding acpi=off just broke my proxmox on debian install. will not boot — lots of errors on a black screen with no response. ACPI options in BIOS only suspend to ram or disable.

It is a dual boot pc — windows still working but the debian is completely unaccessible. Any fix to remove acpi=off from the linux grub even if I can’t access it normally?

Thanks

update: found the edit option
https://askubuntu.com/questions/160036/how-do-i-disable-acpi-when-booting

Can access proxmox and works but lost access to my debian gui —
black screen with acpi bios error (bug) could not resolve symbol

Last edited: Aug 4, 2022

I installed Linux Mint 21 on my HP laptop. I got some errors I don’t know how to solve. The first 2 days after installation, I had the following errors:

This is the error I was getting after I boot the system: https://i.imgur.com/AX95fTC.jpg

This is the error that was appearing immediately after the first error shown in the above image: https://i.imgur.com/UPhbRwz.jpg

This is the error I was getting after I press the Power Off button and the system began to shut down: https://i.imgur.com/6wj8u4Z.jpg

The last error disappeared by itself; now the system doesn’t show any messages when shutting down.

The following line:

[          0.163290] x86/cpu: VMX (outside TXT) disabled by BIOS

Was solved when I enabled the virtualization option in the BIOS: https://i.imgur.com/ENzbo9g.jpg

However, the rest of the errors remained unsolved:

[         0.232719] ACPI BIOS Error (bug): Could not resolve symbol [SB.OSC.CDW1], AE_NOT_FOUND (20210730/psargs-330)
[         0.232848] ACPI Error: Aborting method _SB._OSC due to previous error (AE_NOT_FOUND)   (20210730/psparse-529)

Does anyone know how to solve those errors? I heard I need to change the ACPI option. The problem is that I don’t have access to the advanced settings in the BIOS menu — InsydeH20 Setup Utility. And I don’t know how to get access to the advanced settings menu (the ACPI options are inside the advanced settings menu).

Also, I will be thankful if someone explains to me what causes those errors. I didn’t have such errors when i used Linux Mint 20.3 and when the kernel wasn’t version 5 (or above). The problems started appearing in Linux Mint 21 and kernel 5 (and above).

Содержание

  1. Шо, опять? Ядро 5.6 и ACPI.
  2. Linux Mint Forums
  3. [Solved] ACPI errors during boot
  4. [Solved] ACPI errors during boot
  5. Re: ACPI errors during boot
  6. Re: ACPI errors during boot
  7. Re: ACPI errors during boot
  8. Re: ACPI errors during boot
  9. Re: ACPI errors during boot
  10. Re: ACPI errors during boot
  11. Re: [Solved] ACPI errors during boot
  12. Re: [Solved] ACPI errors during boot
  13. Linux Mint Forums
  14. [SOLVED] ACPI errors and graphics card drivers issues
  15. [SOLVED] ACPI errors and graphics card drivers issues
  16. Re: ACPI errors and graphics card drivers issues
  17. Re: ACPI errors and graphics card drivers issues
  18. Re: ACPI errors and graphics card drivers issues
  19. Re: ACPI errors and graphics card drivers issues
  20. Re: ACPI errors and graphics card drivers issues
  21. Re: ACPI errors and graphics card drivers issues
  22. Re: ACPI errors and graphics card drivers issues
  23. Re: ACPI errors and graphics card drivers issues
  24. Re: ACPI errors and graphics card drivers issues
  25. Re: ACPI errors and graphics card drivers issues
  26. Re: ACPI errors and graphics card drivers issues
  27. Re: ACPI errors and graphics card drivers issues
  28. Re: ACPI errors and graphics card drivers issues
  29. Re: ACPI errors and graphics card drivers issues
  30. Re: ACPI errors and graphics card drivers issues
  31. Re: ACPI errors and graphics card drivers issues

Шо, опять? Ядро 5.6 и ACPI.

При переходе на 5.6 после выхода из саспенда dmesg спамит, и много чего перестаёт работать:

На 5.5 такого не было.

Куда деваться то со своим «старым» (P8Z68) железом?

Куда деваться то со своим «старым» (P8Z68) железом?

На свалку. У меня на лаптопе еще не такое происходить стало со временем, и всем пофиг на мои баг-репорты. Так что либо придумывай собственные костыли, либо меняй железку.

Как? i7-2600K на свалку?

Разбить? Пол-литру!? Вдребезги? Да я тебя!

не знаю про i7, но на i5 2400 даже сайты уже притормаживают, а на всяком дне типа i5 2410m не стесняясь тормозят в полную силу.

Зачем ты суспендишь десктоп?

ryzen 5 2600/b450 aorus elite

это появилось на 5 ядре, на 4.xx (точно не помню на каком именно), такого не было

У 2600K райзены первого поколения по синглкору посасывают, тащемт.

Я даже растерялся… А почему бы мне его не суспендить?

Каждый день пользуюсь. Наверное, чтоб просто клацнуть кнопкой и сразу начать пользоваться?

Если его не суспендить тоже можно просто сразу пользоваться, лол.

Предлагаешь не выключать?

Ну а сколько он там жрёт? В простое частота падает до 800мгц или сколько там.

Нет, конечно. Это пока «нытик-тред».

оставайся на 4.19

Могут сказать точно, что жрёт 80+ Ватт, так он ещё и не бесшумный.

а есть вообще разумный довод использовать максимально свежее ядро ?

А лучше обновится до Darwin Kernel Version 19.4.0

а есть вообще разумный довод использовать максимально свежее ядро ?

Вообще, конечно, нет.

_GTF — acpi функция переводящая (s)ata порт в состояние по умолчанию (или просто — инициализация).

DSSP — это какой-то флаг, на который ссылается эта функция, и который не установлен. Баг acpi/bios.

Скорее всего, в предыдущих версиях ядра из-за жалоб на эту ошибку, эта функция не вызывалась, а ядро само инициализировало sata-порты (сделали заглушку для конкретной материнки). После очередной чистки кода от старья эту заглушку выкинули и честно дергают acpi-функцию

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Смотря что считать за проблему с дисками, точно есть проблемы с кедами, последний раз начали крашится ksshaskpass и system settings и может ещё что, обратил внимание только на это, ну и общая отзывчивость системы падает — в этом плане проблемы с дисками несомненно есть.

Ты привел только одну ошибку. И эта acpi-функция в основном простая заглушка, которая ничего не делает, максимум установит еще какой-нибудь флаг, ничего не значащий для работающей системы, чисто внутренняя для acpi, что типа порт инициализирован.

Думаю, у тебя скорее всего поломалось где-то в другом месте. Иначе у тебя при нормальном старте (не пробуждении из suspend) так же глючила система из-за дисков.

Думаю, у тебя скорее всего поломалось где-то в другом месте.

Всё может быть. Но мне кажется, что это всё-таки в ядре дело. На 5.5 не глючит так после выхода из сна.

Куда деваться то со своим «старым» (P8Z68) железом?

Ладно со старым, у меня с новым за последний год дважды спящий режим ломали.

глючит так после выхода из сна.

Это нормальное состояние вплоть до того, что при смене минорной версии (версиии патча) могут поломать засыпание. Потому что это неважная часть линукса, могут глобально перелопатить логику засыпания между патчами с соответствующими последствиями.

Конечно, всё бывает в первый раз. Но не припомню такие проблемы, системнику 8-10 лет.

Но не припомню такие проблемы, системнику 8-10 лет.

Купи себе модный (китайский) ноутбук/нетбук/планшет — будет что припомнить, что забывать не будешь успевать 🙂

Кто-то еще выключает компьютеры, кроме тех, кто собирает шумные ящики?

  1. скорее не связанные вещи, вот у меня с 5.3

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)

  1. саспенды всегда работали, работают, будут работать с линуксами через одно место. Проще не использовать, тем более, еcли у тебя корабасный десктоп. Выключай на ночь и нормально.

Так было и так будет всегда: кривые, не соответствующие стандартам прошивки на платах Asus. Поэтому в ядре фиксить это никогда не будут.

Впрочем, они почти везде кривые в потребительском железе. Из того, что можно купить за разумные деньги «для дома, для семьи» – только с Supermicro не бывает проблем. Ну, или смотрите списки сертифицированного оборудования, например, redhat.

Как я понимаю ты позорище опенсорса имеешь ввиду сайты как браузер, а не как сервер?

Как сервер www, ppp, ftp, samba, dns, router, и ррочая и прочая даже первый пень до сих пор работоспособным будет.
(и особенно первый, второй и третий пни, так как у них биос в съёмном ПЗУ, а не на флеше, их сейчас как золото беззондовое хранить нужно)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[Solved] ACPI errors during boot

[Solved] ACPI errors during boot

Post by zenmaker » Fri May 20, 2022 10:48 am

During boot get these ACPI errors especially AE NOT found.

So I have 2 ssd and 2 hdd, one ssd is transcend and has windows install and 2 partitions.
The other ssd has linux mint and is crucial, uses ext4 and bios for grub.

The error seem to be related to the transcend ssd no error throws up for other disks in the journal. It feels like some grub or boot mbr issue though have tried reinstalling grub but still get the message.

is it a bad error to have.
during boot these errors show up

Re: ACPI errors during boot

Post by rene » Fri May 20, 2022 10:57 am

Re: ACPI errors during boot

Post by zenmaker » Sat May 21, 2022 6:43 am

The thing was i didnt have this error before, when i was using ubuntu 21.10, hated 22.04 due to snap and stuff and was distro hopping, from debian to fedora to pop but settled on mint.

Its just annoying to see that, im sure its some issue with boot managers on how they are reading the windows disk.

Re: ACPI errors during boot

Post by rene » Sat May 21, 2022 8:34 am

It’s definitely not — but Mint 20.x is on a Ubuntu 20.04 base, i.e., significantly older than 21.10 and.or 22.04, and you are explicitly using the standard 5.4 kernel series.

If you’re sure that 21.10 and/or 22.04 did not show you the ACPI messages you may try upgrading to the 5.13 series: Upgrade Manager -> View -> Linux kernels; pick the newest 5.13 series kernel and reboot into it. Although it doesn’t tend to happen, as a matter of the in the linked tutorial post described BIOS kernel interaction a kernel-sides update may have also fixed (or more likely, simply silenced) this on your system after all.

If not you’d «need» to follow the advise given there as to replacing quiet with loglevel=3 — which for all I know might in fact be something newer Ubuntu releases do OOTB at the moment, although I doubt it.

Re: ACPI errors during boot

Post by zenmaker » Mon May 23, 2022 6:31 am

Hi thanks for the help, so i tested out ubuntu 21.10 impish and jammy on live usb to make sure, funnily impish is the only version it doesnt appear i think its cause of their splash logo probably has the fix you mentioned, while in jammy the errors throw up before logo shows up.

So ended up using loglevel=3 on mint and is now nice and quiet boot, and i can show off to my windows friends how superior linux is without all those errors throwing up on boot

Again thanks for the help and your time much appreciate it.

Re: ACPI errors during boot

Post by Reddog1 » Mon May 23, 2022 8:21 pm

The kernel developers, in their great wisdom, decided to print lower log-level errors on the boot screen, and this has led to a heap of questions about why the acpi errors are occurring. Some other distributions have set the log level=3 out-of-the-box in order to avoid this nuisance.

Please set the topic as [solved]

Re: ACPI errors during boot

Post by rene » Tue May 24, 2022 7:07 am

Re: [Solved] ACPI errors during boot

Post by Reddog1 » Tue May 24, 2022 10:23 pm

Yes, you are right, it is a decision made by the distribution (and those with the distribution that make determinations about the kernel). Anytime errors are shown at boot, it is definitely going to cause consternation, especially among new users. As I mentioned, some distributions have specifically set the /etc/default/grub to not print that log-level of messages.

Here is the stock grub line from an arch-based distro:

GRUB_CMDLINE_LINUX_DEFAULT=»quiet loglevel=3 nowatchdog nvme_load=YES»

Re: [Solved] ACPI errors during boot

Post by rene » Wed May 25, 2022 6:14 am

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] ACPI errors and graphics card drivers issues

[SOLVED] ACPI errors and graphics card drivers issues

Post by Lock3 » Sat Aug 15, 2020 5:50 pm

It’s my first post here, so hello everyone.
I’ve just installed for the first time Linux Mint 64 bits in dual-boot with Windows 10 both in legacy mode.

The dual-boot works fine and so does Mint except that I have these ACPI errors on boot :

Moreover, it is impossible to install the Nvidia drivers which are recommended in the driver manager. When I try to do it, the system doesn’t recognize my graphics card anymore and the image is only managed by the CPU. I specify that I have an RTX 2070.

Secure boot is disabled as well as fast boot on windows 10.

I browsed the forum and tried to modify GRUB without success. Is this a kernel problem?

Thank you in advance for your answers

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sat Aug 15, 2020 6:05 pm

(if you type: the letter F is a capital letter, and don’t omit the space after inxi!)

Copy/paste the output in your next message.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 3:23 am

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 4:22 am

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 5:20 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

It still doesn’t work.

When I installed Mint I chose «Something Else» in the installer option and I have created a partition in ext4 an / for mount. Do I have to create a swap partition like older version of ubuntu ? Or this is irrelevant for this subject ?

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 5:59 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

That’s indeed irrelevant.

You might try a kernel update from the Canonical Kernel Team PPA:
https://easylinuxtipsproject.blogspot.c . t.html#ID8
(item 8 )

That should give you the latest kernel from the 5.4 series, which hopefully contains improvements that are relevant for your problem.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 8:36 am

I did as you said and switched to the 5.4.0-44 and unfortunately it doesn’t change anything.

I experience some weird crashes too : I tried to open Rhythmbox or the firewall and it’s stop the current session and send me back to the login screen. (It happens before the kernel update)

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 12:46 pm

So I tried the tip with

I still have the ACPI errors and the graphic card still doesn’t work.

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 1:03 pm

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 1:42 pm

This beta bios was made only for spectre vulnerability on CPU wich I am already protected.

Many users had issues with this Bios and I will not take my chance with it I think.

It’s a shame beacause Mint works flawlessly on my laptop and it seems to have many issues with a dual boot on legacy mode. Perhaps should I try to convert all the os on EFI mode ? Is it possible anyway without reinstalling the two OS ?

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 1:43 pm

When the Nvidia driver loads properly, you will see nvidia in both the device driver and the display driver.

Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI
driver: nvidia v: 450.57 bus ID: 01:00.0

Display: x11 server: X.Org 1.20.8 driver: fbdev,modesetting,nouveau
unloaded: vesa resolution: 640×480

I don’t see it loaded or unloaded in the display drivers, so I’m going to suggest the driver did not install properly. I don’t what method you used to install it, but Pjotr’s website has a section on NVIDIA: how to install the latest video card drivers and roblm has tips for installing on LM20 in this post (scroll to the section in big blue letters — Mint 20 Nvidia Driver Installation Update).

Hopefully information in one of those two places (or both) can help you.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 2:21 pm

I tried the first step already without success unfortunately.

I will try the second one with driver directly downloaded from nvidia website.

Thanks for answering guys.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 6:32 pm

The second one was better than the others

Driver nvidia-450 has worked flawlessly with the roblm installation technique (with the driver downloaded on nvidia website) after

, every program on Mint worked fine, no crashes. UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 8:26 pm

UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 4:59 am

Yes I removed the nomodeset.

I tried a fresh install again this morning, but again it’s like Mint can’t find the GPU nivdia-driver after or during the boot sequence.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 5:30 am

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

Re: ACPI errors and graphics card drivers issues

Post by SMG » Mon Aug 17, 2020 12:09 pm

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

That sounds similar to what was happening to several people in this thread. Maybe reading through the thread will help. As I understand it, it is not that something is preventing the driver from starting, but rather something is not telling the driver to start at the correct time in the start-up sequence. I know there is a way to fix this (since several people in the thread were able to do it), but I don’t currently have the knowledge level to be able to guide something through the correct steps for doing it.

Perhaps someone with more knowledge than I currently have will be able to help

Источник

Not first time, but recent _OSC patch along with recent thermald release shows problems with Dell DSDT code. Tested with lastest BIOS release 1.7.2 and kernel 5.16.16 with patches from #341

ACPI BIOS Error (bug): Could not resolve symbol [_TZ.ETMD], AE_NOT_FOUND (20211217/psargs-330)

No Local Variables are initialized for Method [_OSC]
Initialized Arguments for Method [_OSC]:  (4 arguments defined for method invocation)
   Arg0:   0000000054be46e0 <Obj>           Buffer(16) 5D A8 3B B2 B7 C8 42 35
   Arg1:   000000002a80f409 <Obj>           Integer 0000000000000001
   Arg2:   00000000c5c9b15c <Obj>           Integer 0000000000000002
   Arg3:   000000002a983728 <Obj>           Buffer(8) 00 00 00 00 05 00 00 00

ACPI Error: Aborting method _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)

It seems variable is used in SSDT2 in _OSC method:

                        If ((CAP1 & One))
                        {
                            If ((CAP1 & 0x02))
                            {
                                _SB.AAC0 = 0x6E
                                _TZ.ETMD = Zero
                            }
                            Else
                            {
                                _SB.AAC0 = ATRP /* _SB_.IETM.ATRP */
                                _TZ.ETMD = One
                            }

                            If ((CAP1 & 0x04))
                            {
                                _SB.APSV = 0x6E
                            }
                            Else
                            {
                                _SB.APSV = PTRP /* _SB_.IETM.PTRP */
                            }
                            
                            If ((CAP1 & 0x08))
                            {
                                _SB.ACRT = 0xD2
                            }
                            Else
                            {
                                _SB.ACRT = YTRP /* _SB_.IETM.YTRP */
                            }
                        }
                        Else
                        {
                            _SB.ACRT = YTRP /* _SB_.IETM.YTRP */
                            _SB.APSV = PTRP /* _SB_.IETM.PTRP */
                            _SB.AAC0 = ATRP /* _SB_.IETM.ATRP */
                            _TZ.ETMD = One
                        }

But it has no definition in DSDT and any of the SSDT’s. I wonder as this type of problem can be see in almost all XPS and/or Precision models is anyone tests this ? I guess Windows is using same mechanisms right ?

I already use custom DSDT to fix Dell slopiness in _Q66 methods so maybe I will try to defint missing varable just to see what will bork next. I wonder is anyone here have access to anyone at Dell to report this kind of problems ? I tired in the past rto use their’s support forum, but in most cases they simply remove and block this kind of posts.

#
2 года, 6 месяцев назад

Темы:

1

Сообщения:

5

Участник с: 14 июля 2020

Суть проблемы:
Имеется китайский ноутбук сомнительного происхождения. Пытаюсь запустить на нём Arch Linux с USB-флешки (записана руфусом в DD-режиме). Система не запускается — отображаются ошибки по типу:

ACPI Error: Aborting method *** due to previous error (AE_AML_LOOP_TIMEOUT)

Подобные сообщения высвечиваются каждые 30 секунд, и дальше процесс не идёт. Ошибки отображаются как в Legacy, так и в UEFI. Нагуглив проблему, понял, что её можно решить установкой значений ACPI OSI (acpi_osi=), однако мой подбор значений не увенчался успехом (пробовал начиная с «Windows 2009» и до 2019, также вместе с параметром acpi_osi=!). С параметром acpi=off система стартует, но без работающей клавиатуры (не функционирует совсем).
Что странно, другие дистрибутивы (Ubuntu-based и Федора) запускаются с параметром acpi=off с работающей клавиатурой, но только в Legacy-режиме, в UEFI тоже ничего не запускается.

Действительно ли в этой ситуации проблема в параметре acpi_osi, или я не туда копаю?

MamkinHaker

#
2 года, 6 месяцев назад

Темы:

3

Сообщения:

65

Участник с: 24 июня 2020

Для того чтобы ваша система смогла загрузиться с только что записанной флешки нужно отключить UEFI Secure Boot. Этот режим позволяет загружаться только подписанным операционным системам, а подписанными являются только ОС от Microsoft. Поэтому для Linux этот режим надо отключать

AMD Ryzen™5 2600, AMD RX570, AMD Radeon R7Perfomance

vasek

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

47

Сообщения:

11417

Участник с: 17 февраля 2013

dorissimus
(acpi_osi=), однако мой подбор значений не увенчался успехом (пробовал начиная с «Windows 2009» и до 2019, также вместе с параметром acpi_osi=!)

Пробовал и acpi_osi=Linux? …. хотя, думаю, вряд ли это поможет.

dorissimus
С параметром acpi=off система стартует, но без работающей клавиатуры

Попробуй дополнительно к acpi=off прописать nolapic — не поможет, можно пробовать и другие … одного рецепта для всех нет.

EDIT 1 — В части параметров acpi, можно пробовать вместо acpi=off и

более мягкие другие, типа: acpi=strict или acpi=copy_dsdt или acpi=rsdt … и можно добавить nolapic

Уточнение в части

dorissimus
пробовал начиная с «Windows 2009» и до 2019

Нужно смотреть, что прописано конкретно в DSDT, например, мой случай

 }
 If (_OSI ("Windows 2006"))
{
      OSYS = 0x07D6
}
If (_OSI ("Windows 2009"))
{
       OSYS = 0x07D9
}

Но, повторюсь, надежды на этот osi мало

Ошибки не исчезают с опытом — они просто умнеют

dorissimus

#
2 года, 6 месяцев назад

Темы:

1

Сообщения:

5

Участник с: 14 июля 2020

vasek
Нужно смотреть, что прописано конкретно в DSDT, например, мой случай

Да, я просмотрел у себя, и у меня прописано многовато значений…

				If(_OSI("Linux"))
				{
					Store(0x03E8, OSYS)
				}
				If(_OSI("Windows 2001"))
				{
					Store(0x07D1, OSYS)
				}
				If(_OSI("Windows 2001 SP1"))
				{
					Store(0x07D1, OSYS)
				}
				If(_OSI("Windows 2001 SP2"))
				{
					Store(0x07D2, OSYS)
				}
				If(_OSI("Windows 2001.1"))
				{
					Store(0x07D3, OSYS)
				}
				If(_OSI("Windows 2006"))
				{
					Store(0x07D6, OSYS)
				}
				If(_OSI("Windows 2009"))
				{
					Store(0x07D9, OSYS)
				}
				If(_OSI("Windows 2012"))
				{
					Store(0x07DC, OSYS)
				}
				If(_OSI("Windows 2013"))
				{
					Store(0x07DD, OSYS)
				}
				If(_OSI("Windows 2015"))
				{
					Store(0x07DF, OSYS)
				}

Пока попробовал nolapic добавить — не заработало. Я так понял, здесь можно только случайно подбирать параметры acpi, пока не запустится…

vasek

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

47

Сообщения:

11417

Участник с: 17 февраля 2013

dorissimus
Я так понял, здесь можно только случайно подбирать параметры acpi, пока не запустится…

Не зная причины, остается только так … nolapic помогает частенько, но не всегда.
Можно установить Arch и не с установочного archiso — есть OS, не помню как называаются, с которых можно установить Arch — поищи на нашем форуме, было несколько топиков на этот счет … или кто подскажет, кто помнит …

Ошибки не исчезают с опытом — они просто умнеют

dorissimus

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

1

Сообщения:

5

Участник с: 14 июля 2020

vasek

dorissimus
Я так понял, здесь можно только случайно подбирать параметры acpi, пока не запустится…

Не зная причины, остается только так … nolapic помогает частенько, но не всегда.
Можно установить Arch и не с установочного archiso – есть OS, не помню как называаются, с которых можно установить Arch — поищи на нашем форуме, было несколько топиков на этот счет … или кто подскажет, кто помнит …

Ну, манжаро кстати ведёт себя абсолютно также. То есть запускаются на этом чуде только убунту-минт/федора-сьюс, да и то только в Legacy BIOS и с выключенным acpi. Так что, возможно, тут от ядра зависит.

UPD: ещё возможно дело в неправильно работающем Secure Boot. Он отключён в биосе (его и включить нельзя), но система, видимо, этого не понимает. По крайней мере, это объясняет, почему некоторые дистры запускаются только в Legacy BIOS, но всё равно непонятно, как это решать.

vasek

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

47

Сообщения:

11417

Участник с: 17 февраля 2013

dorissimus
Так что, возможно, тут от ядра зависит.

Скорее всего здесь все вместе: и ядро и железо и что то другое.

PSdorissimus, интересно, попробуй загрузись с systemrescuecd — сделан на основе Arch, если запусить потом startx, то загрузится XFCE
И еще, что то не соображу, будет ли отличие в загрузке в случае загрузки непосредственно с Live USB или с образа установочного CD, размещенного в корне установленной системы (через Grub2).

EDIT 1 — интересно узнать, что за клавиатура? — тачпад, внешняя — USB? … что за железо ? … возможно приведены не все логи (что то пропущено интересное)

Ошибки не исчезают с опытом — они просто умнеют

vasek

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

47

Сообщения:

11417

Участник с: 17 февраля 2013

Можно еще попробовать вписать полный комплект параметров загрузки ядра для клавиатуры, надежды мало, но не попробовать грех
i8042.reset i8042.nomux i8042.nopnp i8042.noloop i8042.notimeout i8042.direct ….. как добавка к acpi=off nolapic

Ошибки не исчезают с опытом — они просто умнеют

dorissimus

#
2 года, 6 месяцев назад

Темы:

1

Сообщения:

5

Участник с: 14 июля 2020

vasek
попробуй загрузись с systemrescuecd

Те же проблемы, что и на арче, увы.

vasek
будет ли отличие в загрузке в случае загрузки непосредственно с Live USB или с образа установочного CD, размещенного в корне установленной системы (через Grub2)

На ноутбуке стоит только windows, так что вряд ли можно проверить.

vasek
интересно узнать, что за клавиатура?

Клавиатура от ноутбука. Железо — Maibenben xiaomai 5 pro (если не ошибся), присутствует дискретная nvidia.
В логах, собственно, только повторяется одна ошибка, но вот

Параметры с i8042 попробовал, что-то не заработали.

vs220

#
2 года, 6 месяцев назад

(отредактировано

2 года, 6 месяцев назад)

Темы:

22

Сообщения:

8090

Участник с: 16 августа 2009

dorissimus
неправильно работающем Secure Boot

Для других Xiaomi рекомендуют

It is actually very easy getting the Arch Installation Medium to boot properly. Prior to booting the Arch installation ISO enter the UEFI menu by pressing F2 during Boot.

Security -> set password
Security -> Disable Secure Boot
reset the password by setting the password again but letting the «New Password» fields blank
Installation of Arch can proceed normally…..

Или это не опечатка XIAOMAI и мимикрия другого китайца под бренд?

Зарегистрироваться или войдите чтобы оставить сообщение.

I have the following Error codes when loading Linux Mint 21 Mate on my HP 6000 MT PRO Desktop

Mind you I have no errors when booting Windows 10 on same desktop… Anyone have any suggestions….these errors do not cause any problem that I can see from the operation of the PC but, they should not be there. Is there anything I can check in Bios settings, and if so where, I checked under security (system security) and found nothing concerning TPM Chip      Help greatly appreciated in advance.

0.210444] x86/cpu: VMX (outside TXT) disabled by Bios

0.3647241 acpi LMXCPU:00: Invalid PBLK length [7]

0.364763] acpi LmxCPU: 01: Invalid PBLK Length [7]

0. 365089] acpi bios error (bug): _SB.PC10._OSC: excess arguements-ASL doc

lared 5, acpi requires 4 (20210730/nsarguements-162

0.365198]ACPI Bios error (bug): failure creating named object [_SB.PC10._osc.CAPD], already

exists (20210730/dsfield-184)

[ 0.365240] ACPI Error: AE_Already_ exists, CreateBufferField failure(2021073)0/dswload2-477)

0.3653151] acpi error: Aborting Method _SB.PC10._osc due to previous error(AE_Already_exists) (20210730/psparse-529)

[ 1.343963] ima: Error Communicating to TPM chip

[ 1.347222] “ “ “ “ “ “

[ 1.348889] “ “ “ “ “ “

[ 1. 350501] “ “ “ “ “ “

[ 1.352325] “ “ “ “ “ “

[ 1.354977] “ “ “ “ “ “

[ 1.356780] “ “ “ “ “ “

[ 1.358572] “ “ “ “ “ “

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Acpi bios error при установке windows 10
  • Acpi bios error при установке linux
  • Acpi bios error windows 10 при загрузке ноутбука
  • Acpi bios error supermicro
  • Acpi bios error failure creating named object ubuntu

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии