diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.xml b/en_US.ISO8859-1/books/handbook/config/chapter.xml index fdad1fd1bf..fb65f35aa7 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.xml @@ -698,13 +698,13 @@ dc1: [ITHREAD] Alternatively, statically compile support for the NIC into a custom kernel. Refer to /usr/src/sys/conf/NOTES, - /usr/src/sys/arch/conf/NOTES and the - manual page of the driver to determine which line to add - to the custom kernel configuration file. For more - information about recompiling the kernel, refer to - . If the - NIC was detected at boot, the kernel - does not need to be recompiled. + /usr/src/sys/arch/conf/NOTES + and the manual page of the driver to determine which line + to add to the custom kernel configuration file. For more + information about recompiling the kernel, refer to . If the NIC + was detected at boot, the kernel does not need to be + recompiled. @@ -1512,10 +1512,10 @@ cron.* /var/log/cron A, named logserv.example.com, will collect logging information for the local network. Host - B, named logclient.example.com, will - be configured to pass logging information to the logging - server. + B, named logclient.example.com, + will be configured to pass logging information to the logging + server. Log Server Configuration @@ -2856,75 +2856,72 @@ kern.maxvnodes: 100000 APM Software Interface, which allows management of power levels. - There are four major problems in APM. - First, power management is done by the vendor-specific - BIOS, separate from the operating system. - For example, the user can set idle-time values for a hard - drive in the APM BIOS - so that, when exceeded, the BIOS spins - down the hard drive without the consent of the operating - system. Second, the APM logic is embedded - in the BIOS, and it operates outside the - scope of the operating system. This means that users can - only fix problems in the APM - BIOS by flashing a new one into the - ROM, which is a dangerous procedure with - the potential to leave the system in an unrecoverable state - if it fails. Third, APM is a - vendor-specific technology, meaning that there is a lot of - duplication of efforts and bugs found in one vendor's - BIOS may not be solved in others. Lastly, - the APM BIOS did not - have enough room to implement a sophisticated power policy - or one that can adapt well to the purpose of the - machine. + There are four major problems in APM. + First, power management is done by the vendor-specific + BIOS, separate from the operating system. + For example, the user can set idle-time values for a hard drive + in the APM BIOS so that, + when exceeded, the BIOS spins down the hard + drive without the consent of the operating system. Second, the + APM logic is embedded in the + BIOS, and it operates outside the scope of + the operating system. This means that users can only fix + problems in the APM + BIOS by flashing a new one into the + ROM, which is a dangerous procedure with the + potential to leave the system in an unrecoverable state if it + fails. Third, APM is a vendor-specific + technology, meaning that there is a lot of duplication of + efforts and bugs found in one vendor's BIOS + may not be solved in others. Lastly, the APM + BIOS did not have enough room to implement a + sophisticated power policy or one that can adapt well to the + purpose of the machine. - The Plug and Play BIOS - (PNPBIOS) was unreliable in - many situations. PNPBIOS is 16-bit - technology, so the operating system has to use 16-bit - emulation in order to interface with - PNPBIOS methods. &os; provides an - APM driver as APM should - still be used for systems manufactured at or before the year - 2000. The driver is documented in &man.apm.4;. + The Plug and Play BIOS + (PNPBIOS) was unreliable in many situations. + PNPBIOS is 16-bit technology, so the + operating system has to use 16-bit emulation in order to + interface with PNPBIOS methods. &os; + provides an APM driver as + APM should still be used for systems + manufactured at or before the year 2000. The driver is + documented in &man.apm.4;. - - ACPI - + + ACPI + - - APM - + + APM + The successor to APM is the Advanced Configuration and Power Interface (ACPI). - ACPI is a standard written by an - alliance of vendors to provide an interface for - hardware resources and power management. It is a key - element in Operating System-directed configuration - and Power Management as it provides more control - and flexibility to the operating system. + ACPI is a standard written by an alliance of + vendors to provide an interface for hardware resources and power + management. It is a key element in Operating + System-directed configuration and Power Management + as it provides more control and flexibility to the operating + system. - This chapter demonstrates how to configure - ACPI on &os;. It then offers some tips on - how to debug ACPI and how to submit a - problem report containing debugging information so that - developers can diagnosis and fix ACPI - issues. + This chapter demonstrates how to configure + ACPI on &os;. It then offers some tips on + how to debug ACPI and how to submit a problem + report containing debugging information so that developers can + diagnosis and fix ACPI issues. Configuring <acronym>ACPI</acronym> - In &os; the &man.acpi.4; driver is loaded by default at system - boot and should - not be compiled into the kernel. This - driver can not be unloaded after boot because the system - bus uses it for various hardware interactions. - However, if the system is experiencing problems, - ACPI can be disabled altogether - by rebooting after - setting hint.acpi.0.disabled="1" in + In &os; the &man.acpi.4; driver is loaded by default at + system boot and should not be compiled + into the kernel. This driver can not be unloaded after boot + because the system bus uses it for various hardware + interactions. However, if the system is experiencing + problems, ACPI can be disabled altogether + by rebooting after setting + hint.acpi.0.disabled="1" in /boot/loader.conf or by setting this variable at the loader prompt, as described in . @@ -2937,34 +2934,38 @@ kern.maxvnodes: 100000 ACPI can be used to put the system into - a sleep mode with acpiconf, the - flag, and a number from 1 to 5. Most users - only need 1 (quick suspend to + a sleep mode with acpiconf, the + flag, and a number from + 1 to 5. Most users only + need 1 (quick suspend to RAM) or 3 (suspend to RAM). Option 5 performs - a soft-off which is the same as running halt -p. + a soft-off which is the same as running + halt -p. - Other options are available using sysctl. Refer to - &man.acpi.4; and &man.acpiconf.8; for more information. + Other options are available using + sysctl. Refer to &man.acpi.4; and + &man.acpiconf.8; for more information. Common Problems + ACPI 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 bus enumeration - while a laptop might have cooling and battery management - support as well. Laptops also have suspend and resume, with - their own associated complexity. + (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 bus + enumeration 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 @@ -2972,9 +2973,9 @@ kern.maxvnodes: 100000 in memory that specify things like the APIC map (used for SMP), config registers, and simple configuration values. Additionally, a bytecode table, - the Differentiated System Description - Table DSDT, specifies a - tree-like name space of devices and methods. + the Differentiated System Description Table + DSDT, 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 @@ -3017,25 +3018,24 @@ kern.maxvnodes: 100000 RAM (STR) states, S1-S3, and one suspend to disk state (STD), called - S4. STD can be implemented in two separate - ways. The S4BIOS is a + S4. STD can be + implemented in two separate ways. The + S4BIOS is a BIOS-assisted suspend to disk and S4OS is implemented - entirely by the operating system. The normal state the system - is in when plugged in but not powered up is - soft off (S5). - + entirely by the operating system. The normal state the + system is in when plugged in but not powered up is + soft off (S5). - Use sysctl hw.acpi to check - for the suspend-related items. These example results are from a + Use sysctl hw.acpi to check for the + suspend-related items. These example results are from a Thinkpad: hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.s4bios: 0 Use acpiconf -s to test - S3, - S4, and + S3, S4, and S5. An of one (1) indicates S4BIOS support instead @@ -3074,20 +3074,19 @@ hw.acpi.s4bios: 0 console, a Firewire port and cable for using &man.dcons.4;, and kernel debugging skills. - To help isolate the problem, unload as many drivers - as possible. If it works, narrow down which - driver is the problem by loading drivers until it fails - again. Typically, binary drivers like - nvidia.ko, display drivers, and - USB will have the most problems while - Ethernet interfaces usually work fine. If drivers can be - properly loaded and unloaded, automate this by putting the - appropriate commands in + To help isolate the problem, unload as many drivers as + possible. If it works, narrow down which driver is the + problem by loading drivers until it fails again. Typically, + binary drivers like nvidia.ko, display + drivers, and USB will have the most + problems while Ethernet interfaces usually work fine. If + drivers can be properly loaded and unloaded, automate this + by putting the appropriate commands in /etc/rc.suspend and - /etc/rc.resume. - Try setting to - 0 if the display is messed up after - resume. Try setting longer or shorter values for + /etc/rc.resume. Try setting + to 0 + if the display is messed up after resume. Try setting + longer or shorter values for to see if that helps. @@ -3120,9 +3119,8 @@ hw.acpi.s4bios: 0 interrupt storm. Chipsets may have problems based on boot, how the BIOS configures interrupts before correctness of the APIC - (MADT) table, and routing of the - System Control Interrupt - (SCI). + (MADT) table, and routing of the System + Control Interrupt (SCI). interrupt storms @@ -3163,8 +3161,8 @@ hw.acpi.s4bios: 0 console in or setting up a dump partition. To get a backtrace in DDB, use tr. When - handwriting the backtrace, get at least the last five - and the top five lines in the trace. + handwriting the backtrace, get at least the last five and + the top five lines in the trace. Then, try to isolate the problem by booting with ACPI disabled. If that works, isolate @@ -3178,12 +3176,12 @@ hw.acpi.s4bios: 0 First, try setting hw.acpi.disable_on_poweroff="0" in - /boot/loader. This keeps ACPI - from disabling various events during the shutdown process. - Some systems need this value set to 1 - (the default) for the same reason. This usually fixes the - problem of a system powering up spontaneously after a - suspend or poweroff. + /boot/loader. This keeps + ACPI from disabling various events during + the shutdown process. Some systems need this value set to + 1 (the default) for the same reason. + This usually fixes the problem of a system powering up + spontaneously after a suspend or poweroff. @@ -3196,9 +3194,9 @@ hw.acpi.s4bios: 0 ASL - Some BIOS vendors provide incorrect - or buggy bytecode. This is usually manifested by kernel - console messages like this: + Some BIOS vendors provide incorrect or + 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), AE_NOT_FOUND @@ -3206,18 +3204,16 @@ hw.acpi.s4bios: 0 Often, these problems may be resolved by updating the BIOS to the latest revision. Most console messages are harmless, but if there are other problems like - the battery status is not working, these messages are a - good place to start looking for problems. The bytecode, - known as AML, is compiled from a source - language called ASL. The - AML is found in the table known as the - DSDT. To get a copy of the system's - ASL, use &man.acpidump.8;. Include both - , to show the contents of the fixed tables, - and , to disassemble the - AML. Refer to - for an example - syntax. + the battery status is not working, these messages are a good + place to start looking for problems. The bytecode, known as + AML, is compiled from a source language + called ASL. The AML is + found in the table known as the DSDT. To + get a copy of the system's ASL, use + &man.acpidump.8;. Include both , to show + the contents of the fixed tables, and , to + disassemble the AML. Refer to for an example syntax. The simplest first check is to recompile the ASL to check for errors. Warnings can @@ -3296,9 +3292,9 @@ hw.acpi.s4bios: 0 &prompt.root; iasl your.asl - Adding the flag forces creation - of the AML, even if there are errors - during compilation. Some errors, such as missing return + Adding the flag forces creation of + the AML, even if there are errors during + compilation. Some errors, such as missing return statements, are automatically worked around by the interpreter. @@ -3342,8 +3338,8 @@ acpi_dsdt_name="/boot/DSDT.aml" (everything). The level is a bitmask so multiple options can be set at once, separated by spaces. In practice, a serial console should be used to log the output - so it is not lost as the console message buffer flushes. - A full list of the individual layers and levels is found in + so it is not lost as the console message buffer flushes. A + full list of the individual layers and levels is found in &man.acpi.4;. Debugging output is not enabled by default. To enable it, @@ -3420,8 +3416,8 @@ debug.acpi.level="ACPI_LV_ERROR" - - + + Debugging &os; <acronym>ACPI</acronym> @@ -3452,26 +3448,26 @@ debug.acpi.level="ACPI_LV_ERROR" - - ACPI - problems - + + ACPI + problems + - ACPI provides a method for - 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 &os;'s kernel subsystems, and bugs in the - &intel; ACPI-CA interpreter continue to - appear. + ACPI provides a method for + 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 &os;'s + kernel subsystems, and bugs in the &intel; + ACPI-CA interpreter continue to + appear. - This section is intended to help users assist the &os; - ACPI maintainers in identifying the root - cause of problems and in debugging and developing a - solution. + This section is intended to help users assist the &os; + ACPI maintainers in identifying the root + cause of problems and in debugging and developing a + solution. Before submitting a problem, ensure the latest @@ -3512,10 +3508,10 @@ debug.acpi.level="ACPI_LV_ERROR" The URL to a pasted version of the ACPI Source Language (ASL). Do - not send the - ASL directly to the list as it can be - very large. Generate a copy of the - ASL by running this command: + not send the ASL + directly to the list as it can be very large. Generate a + copy of the ASL by running this + command: &prompt.root; acpidump -dt > name-system.asl @@ -3536,6 +3532,5 @@ debug.acpi.level="ACPI_LV_ERROR" PR without emailing &a.acpi.name; first as it is likely that the problem has been reported before. -