From owner-svn-doc-head@FreeBSD.ORG Sat May 24 15:52:10 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A3C0D1E; Sat, 24 May 2014 15:52:10 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 260C3264F; Sat, 24 May 2014 15:52:10 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4OFqA38064581; Sat, 24 May 2014 15:52:10 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4OFqANM064580; Sat, 24 May 2014 15:52:10 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201405241552.s4OFqANM064580@svn.freebsd.org> From: Benedict Reuschling Date: Sat, 24 May 2014 15:52:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44938 - head/en_US.ISO8859-1/articles/laptop X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2014 15:52:10 -0000 Author: bcr Date: Sat May 24 15:52:09 2014 New Revision: 44938 URL: http://svnweb.freebsd.org/changeset/doc/44938 Log: Whitespace fixes, translators can ignore these. Modified: head/en_US.ISO8859-1/articles/laptop/article.xml Modified: head/en_US.ISO8859-1/articles/laptop/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/laptop/article.xml Sat May 24 15:39:44 2014 (r44937) +++ head/en_US.ISO8859-1/articles/laptop/article.xml Sat May 24 15:52:09 2014 (r44938) @@ -1,15 +1,17 @@ -
- FreeBSD on Laptops - +
+ + FreeBSD on Laptops FreeBSD works fine on most laptops, with a few caveats. - Some issues specific to running FreeBSD on laptops, relating - to different hardware requirements from desktops, are - discussed below. + Some issues specific to running FreeBSD on laptops, relating + to different hardware requirements from desktops, are + discussed below. @@ -24,57 +26,59 @@ $FreeBSD$ - FreeBSD is often thought of as a server operating system, but - it works just fine on the desktop, and if you want to use it on - your laptop you can enjoy all the usual benefits: systematic - layout, easy administration and upgrading, the ports/packages - system for adding software, and so on. (Its other benefits, - such as stability, network performance, and performance under - a heavy load, may not be obvious on a laptop, of course.) - However, installing it on laptops often involves problems which - are not encountered on desktop machines and are not commonly - discussed (laptops, even more than desktops, are fine-tuned for - µsoft.windows;). This article aims to discuss some of these - issues. Several people have also documented their experiences - with &os; on specific laptop models on webpages which are not - part of the &os; documentation. You might very well find some - information if you type the name of your laptop model and the - word &os; into a search engine of your - choice. Additionally there is a &os;-specific online database - which aims to give information on hardware issues with laptops, - The &os; - Laptop Compatibility List. - - If you want to communicate with other &os; laptop users, - check out the &a.mobile.name; list. You can also get additional - information about using Laptops on &os; at - http://tuxmobil.org/mobile_bsd.html. + FreeBSD is often thought of as a server operating system, but + it works just fine on the desktop, and if you want to use it on + your laptop you can enjoy all the usual benefits: systematic + layout, easy administration and upgrading, the ports/packages + system for adding software, and so on. (Its other benefits, such + as stability, network performance, and performance under a heavy + load, may not be obvious on a laptop, of course.) However, + installing it on laptops often involves problems which are not + encountered on desktop machines and are not commonly discussed + (laptops, even more than desktops, are fine-tuned for + µsoft.windows;). This article aims to discuss some of these + issues. Several people have also documented their experiences + with &os; on specific laptop models on webpages which are not part + of the &os; documentation. You might very well find some + information if you type the name of your laptop model and the word + &os; into a search engine of your choice. + Additionally there is a &os;-specific online database which aims + to give information on hardware issues with laptops, The &os; Laptop + Compatibility List. + + If you want to communicate with other &os; laptop users, check + out the &a.mobile.name; list. You can also get additional + information about using Laptops on &os; at http://tuxmobil.org/mobile_bsd.html. &xorg; - Recent versions of &xorg; work with most display adapters - available on laptops these days. Acceleration may not be - supported, but a generic SVGA configuration should work. - - Check your laptop documentation for which card you have, - and check in the &xorg; documentation - to see whether it is specifically supported. If it is not, use - a generic device (do not go for a name which just looks - similar). You can try your luck - with the command Xorg -configure - which auto-detects a lot of configurations. + Recent versions of &xorg; work + with most display adapters available on laptops these days. + Acceleration may not be supported, but a generic SVGA + configuration should work. + + Check your laptop documentation for which card you have, and + check in the &xorg; documentation to + see whether it is specifically supported. If it is not, use a + generic device (do not go for a name which just looks similar). + You can try your luck with the command Xorg + -configure which auto-detects a lot of + configurations. The problem often is configuring the monitor. Common - resources for &xorg; focus on CRT monitors; getting a - suitable modeline for an LCD display may be tricky. You may - be lucky and not need to specify a modeline, or just need to - specify suitable HorizSync and VertRefresh ranges. If that - does not work, the best option is to check web resources - devoted to configuring X on laptops (these are often - Linux oriented sites but it does not matter because both systems - use &xorg;) and copy a modeline posted by someone for similar - hardware. + resources for &xorg; focus on CRT + monitors; getting a suitable modeline for an LCD display may be + tricky. You may be lucky and not need to specify a modeline, or + just need to specify suitable HorizSync and + VertRefresh ranges. If that does not work, + the best option is to check web resources devoted to configuring + X on laptops (these are often Linux oriented sites but it does + not matter because both systems use + &xorg;) and copy a modeline posted by + someone for similar hardware. Most laptops come with two buttons on their pointing devices, which is rather problematic in X (since the middle @@ -82,55 +86,53 @@ simultaneous left-right click in your X configuration to a middle button click with the line - - Option "Emulate3Buttons" - + Option "Emulate3Buttons" - in xorg.conf in the InputDevice - section. + in xorg.conf in the + InputDevice section. Modems - - Laptops usually come with internal (on-board) modems. + + Laptops usually come with internal (on-board) modems. Unfortunately, this almost always means they are - winmodems whose - functionality is implemented in software, for which only &windows; - drivers are normally available (though a few drivers are beginning - to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the comms/ltmdm port). If that is the case, you + winmodems whose functionality is implemented in + software, for which only &windows; drivers are normally + available (though a few drivers are beginning to show up for + other operating systems; for example, if your modem has a Lucent + LT chipset it might be supported by the + comms/ltmdm port). If that is the case, you need to buy an external modem: the most compact option 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. - + probably a PC Card (PCMCIA) modem, discussed below, but serial + or USB modems may be cheaper. Generally, regular modems + (non-winmodems) should work fine. PCMCIA (PC Card) Devices - Most laptops come with PCMCIA (also called PC Card) - slots; these are supported fine under FreeBSD. Look through - your boot-up messages (using &man.dmesg.8;) and see whether these were - detected correctly (they should appear as - pccard0, - pccard1 etc on devices like - pcic0). + Most laptops come with PCMCIA (also called PC Card) slots; + these are supported fine under FreeBSD. Look through your + boot-up messages (using &man.dmesg.8;) and see whether these + were detected correctly (they should appear as + pccard0, pccard1 etc + on devices like pcic0). &os; 4.X supports 16-bit PCMCIA cards, and - &os; 5.X supports both 16-bit and - 32-bit (CardBus) cards. A database of supported - cards is in the file /etc/defaults/pccard.conf. - Look through it, and preferably buy cards listed there. Cards not - listed may also work as generic devices: in + &os; 5.X supports both 16-bit and 32-bit + (CardBus) cards. A database of supported cards + is in the file /etc/defaults/pccard.conf. + Look through it, and preferably buy cards listed there. Cards + not listed may also work as generic devices: in particular most modems (16-bit) should work fine, provided they - are not winmodems (these do exist even as PC Cards, so watch out). - If your card is recognised as a generic modem, note that the - default pccard.conf specifies a delay time of 10 seconds - (to avoid freezes on certain modems); this may well be - over-cautious for your modem, so you may want to play with it, - reducing it or removing it totally. + are not winmodems (these do exist even as PC Cards, so watch + out). If your card is recognised as a generic modem, note that + the default pccard.conf specifies a delay + time of 10 seconds (to avoid freezes on certain modems); this + may well be over-cautious for your modem, so you may want to + play with it, reducing it or removing it totally. Some parts of pccard.conf may need editing. Check the irq line, and be sure to remove any number @@ -138,20 +140,20 @@ card, remove irq 5 (otherwise you may experience hangs when you insert a card). Check also the available memory slots; if your card is not being detected, try changing it to one of the other - allowed values (listed in the manual page &man.pccardc.8;). - + allowed values (listed in the manual page + &man.pccardc.8;). - If it is not running already, start the &man.pccardd.8; daemon. - (To enable it at boot time, add + If it is not running already, start the &man.pccardd.8; + daemon. (To enable it at boot time, add pccard_enable="YES" to /etc/rc.conf.) Now your cards should be detected when you insert and remove them, and you should get log messages about new devices being enabled. - There have been major changes to the pccard code - (including ISA routing of interrupts, for machines where - &os; is not able to use the PCI BIOS) before the &os; 4.4 - release. If you have problems, try upgrading your system. + There have been major changes to the pccard code (including + ISA routing of interrupts, for machines where &os; is not able + to use the PCI BIOS) before the &os; 4.4 release. If you + have problems, try upgrading your system. @@ -203,33 +205,32 @@ /etc/rc.conf. You may also want start the &man.apmd.8; daemon by adding apmd_enable="YES" to - /etc/rc.conf, 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. - - The APM commands are listed in the &man.apm.8; manual page. - For instance, apm -b gives you battery - status (or 255 if not supported), apm -Z - puts the laptop on standby, apm -z (or - zzz) suspends it. To shutdown and power - off the machine, use shutdown -p. Again, - some or all of these functions may not work very well or at - all. + /etc/rc.conf, 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. + + The APM commands are listed in the &man.apm.8; manual + page. For instance, apm -b gives you + battery status (or 255 if not supported), apm + -Z puts the laptop on standby, apm + -z (or zzz) suspends it. To + shutdown and power off the machine, use shutdown + -p. Again, some or all of these functions may not + work very well or at all. 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 &os; 5.X, one solution for this might be to put options - SC_NO_SUSPEND_VTYSWITCH - in your kernel configuration file and recompile your kernel. - Another workaround is to switch to a virtual console (using - CtrlAltF1 - 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 - /etc/apmd.conf and change it to - this: + SC_NO_SUSPEND_VTYSWITCH in your kernel + configuration file and recompile your kernel. Another + workaround is to switch to a virtual console (using CtrlAltF1 + 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 /etc/apmd.conf + and change it to this: apm_event SUSPENDREQ { exec "vidcontrol -s 1 < /dev/console"; @@ -274,26 +275,25 @@ apm_event NORMRESUME, STANDBYRESUME { If you want to disable ACPI simply add hint.acpi.0.disabled="1" to - /boot/device.hints. You can disable - ACPI temporarily at the boot loader prompt by issuing + /boot/device.hints. You can disable ACPI + temporarily at the boot loader prompt by issuing unset acpi_load if you are having problems booting an ACPI enabled machine. &os; 5.1-RELEASE and later come with a boot-time menu that controls how &os; is booted. One of the proposed options is to turn off ACPI. So - to disable ACPI just select 2. Boot &os; with ACPI - disabled in the menu. + to disable ACPI just select 2. Boot &os; with + ACPI disabled in the menu. Display Power Management - The X window system (&xorg;) also includes display power - management (look at the &man.xset.1; manual page, and search for - dpms 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. + The X window system (&xorg;) + also includes display power management (look at the + &man.xset.1; manual page, and search for dpms + 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. -