• Configuration System Failed To Initialize
• Driver Failed Error

Written by Nate Lawson. With contributions from Peter Schultz and Tom Rhodes. ACPI is a fundamentally new way of discovering devices, managing power usage, and providing standardized access to various hardware previously managed by the BIOS. Progress is being made toward ACPI working on all systems, but bugs in some motherboards' ACPI Machine Language ( AML) bytecode, incompleteness in FreeBSD's kernel subsystems, and bugs in the Intel® ACPI-CA interpreter continue to appear.

Installed FreeBSD 10. Can't start X on virtual private server using. 0xfebf0000/4096, BIOS @ 0x?????/65536 Missing output drivers. Configuration failed.

This document is intended to help you assist the FreeBSD ACPI maintainers in identifying the root cause of problems you observe and debugging and developing a solution. Thanks for reading this and we hope we can solve your system's problems. Note: Before submitting a problem, be sure you are running the latest BIOS version and, if available, embedded controller firmware version. For those of you that want to submit a problem right away, please send the following information to:.

Description of the buggy behavior, including system type and model and anything that causes the bug to appear. Also, please note as accurately as possible when the bug began occurring if it is new for you. The output after boot -v, including any error messages generated by you exercising the bug. The output from boot -v with ACPI disabled, if disabling it helps fix the problem.

Output from sysctl hw.acpi. This is also a good way of figuring out what features your system offers.

URL where your ACPI Source Language ( ASL) can be found. Do not send the ASL directly to the list as it can be very large. Generate a copy of your ASL by running this command: # acpidump -dt name- system.asl (Substitute your login name for name and manufacturer/model for system. Example: njl-FooCo6000.asl) Most of the developers watch the but please submit problems to to be sure it is seen. Please be patient, all of us have full-time jobs elsewhere. If your bug is not immediately apparent, we will probably ask you to submit a PR via. When entering a PR, please include the same information as requested above.

This will help us track the problem and resolve it. Do not send a PR without emailing first as we use PRs as reminders of existing problems, not a reporting mechanism. It is likely that your problem has been reported by someone before. ACPI is present in all modern computers that conform to the ia32 (x86), ia64 (Itanium), and amd64 (AMD) architectures. The full standard has many features including CPU performance management, power planes control, thermal zones, various battery systems, embedded controllers, and bus enumeration. Most systems implement less than the full standard. For instance, a desktop system usually only implements the bus enumeration parts while a laptop might have cooling and battery management support as well.

Laptops also have suspend and resume, with their own associated complexity. An ACPI-compliant system has various components. The BIOS and chipset vendors provide various fixed tables (e.g., FADT) in memory that specify things like the APIC map (used for SMP), config registers, and simple configuration values.

Additionally, a table of bytecode (the Differentiated System Description Table DSDT) is provided that specifies a tree-like name space of devices and methods. The ACPI driver must parse the fixed tables, implement an interpreter for the bytecode, and modify device drivers and the kernel to accept information from the ACPI subsystem. For FreeBSD, Intel has provided an interpreter ( ACPI-CA) that is shared with Linux and NetBSD. The path to the ACPI-CA source code is src/sys/contrib/dev/acpica. The glue code that allows ACPI-CA to work on FreeBSD is in src/sys/dev/acpica/Osd. Finally, drivers that implement various ACPI devices are found in src/sys/dev/acpica.

ACPI has three suspend to RAM ( STR) states, S1- S3, and one suspend to disk state ( STD), called S4. S5 is “soft off” and is the normal state your system is in when plugged in but not powered up.

S4 can actually be implemented two separate ways. S4 BIOS is a BIOS-assisted suspend to disk. S4 OS is implemented entirely by the operating system. Start by checking sysctl hw.acpi for the suspend-related items. Here are the results for a Thinkpad: hw.acpi.supportedsleepstate: S3 S4 S5 hw.acpi.s4bios: 0 This means that we can use acpiconf -s to test S3, S4 OS, and S5. If s4bios was one ( 1), we would have S4 BIOS support instead of S4 OS. When testing suspend/resume, start with S1, if supported.

This state is most likely to work since it does not require much driver support. No one has implemented S2 but if you have it, it is similar to S1. The next thing to try is S3. This is the deepest STR state and requires a lot of driver support to properly reinitialize your hardware. If you have problems resuming, feel free to email the list but do not expect the problem to be resolved since there are a lot of drivers/hardware that need more testing and work. To help isolate the problem, remove as many drivers from your kernel as possible. If it works, you can narrow down which driver is the problem by loading drivers until it fails again.

Typically binary drivers like nvidia.ko, X11 display drivers, and USB will have the most problems while Ethernet interfaces usually work fine. If you can properly load/unload the drivers, you can automate this by putting the appropriate commands in /etc/rc.suspend and /etc/rc.resume. There is a commented-out example for unloading and loading a driver. Try setting hw.acpi.resetvideo to zero ( 0) if your display is messed up after resume. Try setting longer or shorter values for hw.acpi.sleepdelay to see if that helps. Another thing to try is load a recent Linux distribution with ACPI support and test their suspend/resume support on the same hardware. If it works on Linux, it is likely a FreeBSD driver problem and narrowing down which driver causes the problems will help us fix the problem.

Note that the ACPI maintainers do not usually maintain other drivers (e.g sound, ATA, etc.) so any work done on tracking down a driver problem should probably eventually be posted to the list and mailed to the driver maintainer. If you are feeling adventurous, go ahead and start putting some debugging s in a problematic driver to track down where in its resume function it hangs. Finally, try disabling ACPI and enabling APM instead.

If suspend/resume works with APM, you may be better off sticking with APM, especially on older hardware (pre-2000). It took vendors a while to get ACPI support correct and older hardware is more likely to have BIOS problems with ACPI. Most system hangs are a result of lost interrupts or an interrupt storm.

Chipsets have a lot of problems based on how the BIOS configures interrupts before boot, correctness of the APIC ( MADT) table, and routing of the System Control Interrupt ( SCI). Interrupt storms can be distinguished from lost interrupts by checking the output of vmstat -i and looking at the line that has acpi0. If the counter is increasing at more than a couple per second, you have an interrupt storm. If the system appears hung, try breaking to DDB ( CTRL+ ALT+ ESC on console) and type show interrupts. Your best hope when dealing with interrupt problems is to try disabling APIC support with hint.apic.0.disabled='1' in loader.conf. Panics are relatively rare for ACPI and are the top priority to be fixed. The first step is to isolate the steps to reproduce the panic (if possible) and get a backtrace.

Follow the advice for enabling options DDB and setting up a serial console (see ) or setting up a partition. You can get a backtrace in DDB with tr. If you have to handwrite the backtrace, be sure to at least get the lowest five (5) and top five (5) lines in the trace. Then, try to isolate the problem by booting with ACPI disabled.

If that works, you can isolate the ACPI subsystem by using various values of debug.acpi.disable. See the manual page for some examples. The most common problem is the BIOS vendors providing incorrect (or outright buggy!) bytecode.

This is usually manifested by kernel console messages like this: ACPI-1287:. Error: Method execution failed SB.PCI0.LPC0.FIGD.STA (Node 0xc3f6d160), AENOTFOUND Often, you can resolve these problems by updating your BIOS to the latest revision. Most console messages are harmless but if you have other problems like battery status not working, they are a good place to start looking for problems in the AML. The bytecode, known as AML, is compiled from a source language called ASL. The AML is found in the table known as the DSDT.

Configuration System Failed To Initialize

To get a copy of your ASL, use. You should use both the -t (show contents of the fixed tables) and -d (disassemble AML to ASL) options. See the section for an example syntax. The simplest first check you can do is to recompile your ASL to check for errors. Warnings can usually be ignored but errors are bugs that will usually prevent ACPI from working correctly. To recompile your ASL, issue the following command: # iasl your.asl. In the long run, our goal is for almost everyone to have ACPI work without any user intervention.

At this point, however, we are still developing workarounds for common mistakes made by the BIOS vendors. The Microsoft® interpreter ( acpi.sys and acpiec.sys) does not strictly check for adherence to the standard, and thus many BIOS vendors who only test ACPI under Windows® never fix their ASL. We hope to continue to identify and document exactly what non-standard behavior is allowed by Microsoft's interpreter and replicate it so FreeBSD can work without forcing users to fix the ASL. As a workaround and to help us identify behavior, you can fix the ASL manually. If this works for you, please send a of the old and new ASL so we can possibly work around the buggy behavior in ACPI-CA and thus make your fix unnecessary. Here is a list of common error messages, their cause, and how to fix them.

After you customize your.asl, you will want to compile it, run: # iasl your.asl You can add the -f flag to force creation of the AML, even if there are errors during compilation. Remember that some errors (e.g., missing Return statements) are automatically worked around by the interpreter.

DSDT.aml is the default output filename for iasl. You can load this instead of your BIOS's buggy copy (which is still present in flash memory) by editing /boot/loader.conf as follows: acpidsdtload='YES' acpidsdtname='/boot/DSDT.aml' Be sure to copy your DSDT.aml to the /boot directory. The ACPI driver has a very flexible debugging facility. It allows you to specify a set of subsystems as well as the level of verbosity. The subsystems you wish to debug are specified as “layers” and are broken down into ACPI-CA components (ACPIALLCOMPONENTS) and ACPI hardware support (ACPIALLDRIVERS). The verbosity of debugging output is specified as the “level” and ranges from ACPILVERROR (just report errors) to ACPILVVERBOSE (everything).

The “level” is a bitmask so multiple options can be set at once, separated by spaces. In practice, you will want to use a serial console to log the output if it is so long it flushes the console message buffer. A full list of the individual layers and levels is found in the manual page. Debugging output is not enabled by default. To enable it, add options ACPIDEBUG to your kernel configuration file if ACPI is compiled into the kernel. You can add ACPIDEBUG=1 to your /etc/make.conf to enable it globally.

Driver Failed Error

If it is a module, you can recompile just your acpi.ko module as follows: # cd /sys/modules/acpi/acpi && make clean && make ACPIDEBUG=1 Install acpi.ko in /boot/kernel and add your desired level and layer to loader.conf. This example enables debug messages for all ACPI-CA components and all ACPI hardware drivers ( CPU, LID, etc.). It will only output error messages, the least verbose level. Debug.acpi.layer='ACPIALLCOMPONENTS ACPIALLDRIVERS' debug.acpi.level='ACPILVERROR' If the information you want is triggered by a specific event (say, a suspend and then resume), you can leave out changes to loader.conf and instead use sysctl to specify the layer and level after booting and preparing your system for the specific event. The sysctls are named the same as the tunables in loader.conf.

Big embarrasing mistake. I am using one monitor and 2 computers connected by a KVM switch. When I was checking on the video card I switched to the computer NOT running Arch Linux and got the info for the wrong one.

The video card on the Arch machine is an Intel i815 and after a little research found that I just needed to set driver = 'i810' and boardname = 'i815'. I manually edited the xorg.conf.new file and then had to get rid of an error about twm and xterm not being defined downloaded the modules for the window manager (decided to go with icewm) and for xterm.

Now, it works. You actually gave me the clue I needed to track down the changes to xorg.conf.new by asking if there was any problem with other distros. I wouldn't have thought of looking at the xorg.conf files for them if you hadn't asked that. Sorry for being a dunce, Thanks very much.