issues.</para>

      issues.  Several people have also documented their experiences

      with FreeBSD on specific laptop models on webpages which are not

      part of the FreeBSD documentation.  You might very well find some

      information if you type the name of your laptop model and the

      word <quote>FreeBSD</quote> into a search engine of your

      choice.</para>

  <sect1>    

  <sect1>

    <para>Recent versions of <application>XFree86</application> work with most display adapters

    <para>Recent versions of <application>XFree86</application> work

      available on laptops these days.  Acceleration may not be

      with most display adapters available on laptops these days.

      supported, but a generic SVGA configuration should work.</para>

      Acceleration may not be supported, but a generic SVGA

      configuration should work.</para>

    <para>Check your laptop documentation for which card you have,

      and check in the <application>XFree86</application> documentation (or setup program) 

    <para>Check your laptop documentation for which card you have, and

      to see whether it is specifically supported.  If it is not, use

      check in the <application>XFree86</application> documentation

      a generic device (do not go for a name which just looks

      (or setup program) to see whether it is specifically supported.

      similar).  In <application>XFree86</application> version 4, you can try your luck

      If it is not, use a generic device (do not go for a name which

      with the command <userinput>XFree86 -configure</userinput>

      just looks similar).  In <application>XFree86</application>

      which auto-detects a lot of configurations.</para>

      version 4, you can try your luck with the command

      <userinput>XFree86 -configure</userinput> which auto-detects a

      lot of configurations.</para>

      resources for <application>XFree86</application> focus on CRT monitors; getting a

      resources for <application>XFree86</application> focus on CRT

      suitable modeline for an LCD display may be tricky.  You may

      monitors; getting a suitable modeline for an LCD display may be

      be lucky and not need to specify a modeline, or just need to

      tricky.  You may be lucky and not need to specify a modeline, or

      specify suitable HorizSync and VertRefresh ranges.  If that

      just need to specify suitable HorizSync and VertRefresh ranges.

      does not work, the best option is to check web resources

      If that does not work, the best option is to check web resources

      use <application>XFree86</application>) and copy a modeline posted by someone for similar 

      use <application>XFree86</application>) and copy a modeline

      hardware.</para>

      posted by someone for similar hardware.</para>

      devices, which is rather problematic in X (since the middle 

      devices, which is rather problematic in X (since the middle

      button is commonly used to paste text); you can map a 

      button is commonly used to paste text); you can map a

      simultaneous left-right click in your X configuration to 

      simultaneous left-right click in your X configuration to a

      a middle button click with the line</para>

      middle button click with the line 

      <programlisting>Option "Emulate3Buttons"</programlisting> in

    <programlisting>

      the <filename>XF86Config</filename> file in the

      Option "Emulate3Buttons"

      <literal>InputDevice</literal> section (for XFree86 version 4;

    </programlisting>

      for version 3, put just the line

      <literal>Emulate3Buttons</literal>, without the quotes, in the

    <para>in the <filename>XF86Config</filename> file in the <literal>InputDevice</literal> 

      section (for XFree86 version 4; for version 3, put just the line 

      <literal>Emulate3Buttons</literal>, without the quotes, in the 

  <sect1> 

  </sect1>

  <sect1>

    <para> 

    <para>

      Unfortunately, this almost always means they are 

      Unfortunately, this almost always means they are

      <quote>winmodems</quote> whose

      <quote>winmodems</quote> whose functionality is implemented in

      functionality is implemented in software, for which only windows

      software, for which only windows drivers are normally available

      drivers are normally available (though a few drivers are beginning 

      (though a few drivers are beginning to show up for other

      to show up for other operating systems).  If that is the case, you

      operating systems; for example, if your modem has a Lucent LT

      need to buy an external modem: the most compact option is

      chipset it might be supported by the <filename

      probably a PC Card (PCMCIA) modem, discussed below, but 

      role="package">comms/ltmdm</filename> port).  If that is the

      serial or USB modems may be cheaper.  Generally, regular 

      case, you need to buy an external modem: the most compact option

      modems (non-winmodems) should work fine.   

      is probably a PC Card (PCMCIA) modem, discussed below, but

      serial or USB modems may be cheaper.  Generally, regular modems

      (non-winmodems) should work fine.

  </sect1> 

  </sect1>

  <sect1> 

  <sect1>

    <para> Most laptops come with PCMCIA (also called PC Card)

    <para>Most laptops come with PCMCIA (also called PC Card)

    <para>FreeBSD currently supports 16-bit PCMCIA cards, but not

    <para>FreeBSD 4.x supports 16-bit PCMCIA cards, and FreeBSD 5.x

      32-bit (<quote>CardBus</quote>) cards.   A database of supported 

      supports both 16-bit and 32-bit (<quote>CardBus</quote>) cards.

      cards is in the file <filename>/etc/defaults/pccard.conf</filename>.  

      A database of supported cards is in the file

      Look through it, and preferably buy cards listed there.  Cards not

      <filename>/etc/defaults/pccard.conf</filename>.  Look through

      listed may also work as <quote>generic</quote> devices: in 

      it, and preferably buy cards listed there.  Cards not listed may

      particular most modems (16-bit) should work fine, provided they 

      also work as <quote>generic</quote> devices: in particular most

      are not winmodems (these do exist even as PC Cards, so watch out).  

      modems (16-bit) should work fine, provided they are not

      If your card is recognised as a generic modem, note that the

      winmodems (these do exist even as PC Cards, so watch out).  If

      default <filename>pccard.conf</filename> file specifies a delay time of 10 seconds

      your card is recognised as a generic modem, note that the

      (to avoid freezes on certain modems); this may well be

      default <filename>pccard.conf</filename> file specifies a delay

      over-cautious for your modem, so you may want to play with it,

      time of 10 seconds (to avoid freezes on certain modems); this

      reducing it or removing it totally.</para>

      may well be over-cautious for your modem, so you may want to

      play with it, reducing it or removing it totally.</para>

    <para>Some parts of <filename>pccard.conf</filename> may need 

      editing.  Check the irq line, and be sure to remove any number 

    <para>Some parts of <filename>pccard.conf</filename> may need

      already being used: in particular, if you have an on board sound 

      editing.  Check the irq line, and be sure to remove any number

      card, remove irq 5 (otherwise you may experience hangs when you 

      already being used: in particular, if you have an on board sound

      insert a card).  Check also the available memory slots; if your 

      card, remove irq 5 (otherwise you may experience hangs when you

      card is not being detected, try changing it to one of the other 

      insert a card).  Check also the available memory slots; if your

      card is not being detected, try changing it to one of the other

      release.  If you have problems, try upgrading your system.</para>

      release. If you have problems, try upgrading your system.</para>

  </sect1> 

  <sect1> 

  </sect1>

  <sect1>

    <para>To enable this, you may need to compile a kernel with

    <para>To make things a little more complex, there are two existing

      power management support (<literal>device apm0</literal>) or

      standards for power management: APM and ACPI, the latter

      add the option <literal>enable apm0</literal> to 

      superseding the former and including more features, but also

      <filename>/boot/loader.conf</filename>, and

      introducing more problems.</para>

      also enable the &man.apmd.8; daemon at boot time (line

      <literal>apm_enable="YES"</literal> in

    <para>Some laptops support both APM and ACPI (to a certain

      <filename>/etc/rc.conf</filename>).  The apm commands are

      degree), others just support one of them, so chances are that

      listed in the &man.apm.8; manual page.  For instance,

      you have to experiment with both of them to have reliable power

      <command>apm -b</command> gives you battery status (or 255 if

      management on your laptop.</para>

      not supported), <command>apm -Z</command> puts the laptop on

      standby, <command>apm -z</command> (or zzz) suspends it.  To

    <note>

      shutdown and power off the machine, use <command>shutdown -p</command>.

      <para>You cannot have APM and ACPI enabled at the same time,

      Again, some or all of these functions may not work very well

        even if your laptop has support for both of them.</para>

      or at all.  You may find that laptop suspension/standby works

    </note>

      in console mode but not under X (that is, the screen does not

      come on again; in that case, switch to a virtual console

    <sect2>

      (using Ctrl-Alt-F1 or another function key) and then execute

      <title>APM</title>

      the &man.apm.8; command.

    </para>

      <para>The APM (Advanced Power Management) BIOS provides support

        for various power management features like standby, suspend,

        hibernation, CPU clock slow down etc. and is available

        under FreeBSD 4.x and FreeBSD 5.x.</para>

      <para>To enable APM, you can compile a kernel with power

        management support (<literal>device apm0</literal> on FreeBSD

        4.x and <literal>device apm</literal> on FreeBSD 5.x) or

        simply load the APM kernel module at boot time by adding

        <literal>enable&nbsp;apm0</literal> (FreeBSD 4.x) or

        <literal>apm_load="YES"</literal> (FreeBSD 5.x) to

        <filename>/boot/loader.conf</filename>.</para>

      <para>On FreeBSD 5.x, you also have to set

        <programlisting>hint.apm.0.disabled="0"</programlisting> in

        <filename>/boot/device.hints</filename>.</para>

      <para>You can start APM at boot time by having

        <programlisting>apm_enable="YES"</programlisting> in

        <filename>/etc/rc.conf</filename>.  You may also want start

        the &man.apmd.8; daemon by adding

        <programlisting>apmd_enable="YES"</programlisting> to

        <filename>/etc/rc.conf</filename>, which takes care of

        various APM events that are posted to the BIOS, so you can

        have your laptop suspend/resume by pressing some function

        key on the keyboard or by closing/opening the lid.</para>

      <para>The APM commands are listed in &man.apm.8;.  For instance,

        <command>apm -b</command> gives you battery status (or 255 if

        not supported), <command>apm -Z</command> puts the laptop on

        standby, <command>apm -z</command> (or <command>zzz</command>)

        suspends it.  To shutdown and power off the machine, use

        <command>shutdown -p</command>.  Again, some or all of these

        functions may not work very well or at all.</para>

      <para>You may find that laptop suspension/standby works in

        console mode but not under X (that is, the screen does not

        come on again); if you are running FreeBSD 5.x, one solution

        for this might be to put

        <programlisting>options SC_NO_SUSPEND_VTYSWITCH</programlisting>

        in your kernel config file and recompile your kernel.  Another

        workaround is to switch to a virtual console (using

        Ctrl-Alt-F1 or another function key) and then execute

        &man.apm.8;.  You can automate this with &man.vidcontrol.1;,

        if you are running &man.apmd.8;.  Simply edit

        <filename>/etc/apmd.conf</filename> and change it to

        this:</para>

      <programlisting>apm_event SUSPENDREQ {

	exec "vidcontrol -s 1 < /dev/console";

	exec "/etc/rc.suspend";

}

apm_event USERSUSPENDREQ {

	exec "vidcontrol -s 1 < /dev/console";

	exec "sync && sync && sync";

	exec "sleep 1";

	exec "apm -z";

}

apm_event NORMRESUME, STANDBYRESUME {

	exec "/etc/rc.resume";

	exec "vidcontrol -s 9 < /dev/console";

}</programlisting>

    </sect2>

    <sect2>

      <title>ACPI</title>

      <para>ACPI (Advanced Configuration and Power Management

        Interface) provides not only power management but also

        platform hardware discovery (superseding PnP and PCI BIOS).

        ACPI is only available under FreeBSD 5.x and is enabled by

        default, so you don't have to do anything special to get it

        running.  You can control ACPI behaviour with

        &man.acpiconf.8;.</para>

      <para>Unfortunately, vendors often ship their laptops with

        broken ACPI implementations, thus having ACPI enabled

        sometimes causes more problems than being useful, up to the

        point that you cannot even boot FreeBSD on some machines with

        ACPI enabled.</para>

      <para>If ACPI is causing problems, you might check if your

        laptop vendor has released a new BIOS version that fixes some

        bugs.  Since the FreeBSD ACPI implementation is still very

        evolving code, you might also want to upgrade your system;

        chances are that your problems are fixed.</para>

      <para>If you want to disable ACPI simply add

        <programlisting>hint.acpi.0.disabled="1"</programlisting> to

        <filename>/boot/device.hints</filename>.  You can disable ACPI

        temporarily at the boot loader prompt by issueing

        <literal>unset acpi_load</literal> if you are having problems

        booting an ACPI enabled machine.</para>

    </sect2>

    <sect2>

      <title>Display Power Management</title>

      <para>The X window system (<application>XFree86</application>)

      also includes display power management (look at the &man.xset.1;

      manual page, and search for <quote>dpms</quote> there).  You may

      want to investigate this.  However, this, too, works

      inconsistently on laptops: it often turns off the display but

      does not turn off the backlight.</para>

    <para>The X window system (<application>XFree86</application>) also includes display power

    </sect2>

      management (look at the &man.xset.1; manual page, and search for

      <quote>dpms</quote> there).  You may want to investigate this.  However, this, 

      too, works inconsistently on laptops: it

      often turns off the display but does not turn off the

      backlight.</para>