os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add a comment from John Reece <reece@ix.netcom.com> about toggling NumLock

Browse source 
in the BIOS for the PS/2 mouse.

Add <tt// around FIPS.
This commit is contained in:
Ollivier Robert 1996-02-11 14:02:52 +00:00
parent 827b1b2b29
commit 28308db56f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=254
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
FAQ/freebsd-faq.sgml
View file

@ -4,7 +4,7 @@
<title>Frequently Asked Questions for FreeBSD 2.X <title>Frequently Asked Questions for FreeBSD 2.X
<author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/ <author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/
<date> $Id: freebsd-faq.sgml,v 1.32 1996-01-31 14:25:49 mpp Exp $ <date> $Id: freebsd-faq.sgml,v 1.33 1996-02-11 14:02:52 roberto Exp $
<abstract> <abstract>
This is the FAQ for FreeBSD systems version 2.X All entries are This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted. assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted.
@ -386,7 +386,7 @@ Any entries with a &lt;XXX&gt; are under construction.
<tt>tools/</tt> subdirectory on the FreeBSD CDROM or on the <tt>tools/</tt> subdirectory on the FreeBSD CDROM or on the
various FreeBSD ftp sites, to be quite useful. various FreeBSD ftp sites, to be quite useful.
FIPS allows you to split an existing DOS partition into two <tt/FIPS/ allows you to split an existing DOS partition into two
pieces, preserving the original partition and allowing you to pieces, preserving the original partition and allowing you to
install onto the second free piece. You first ``defrag'' your install onto the second free piece. You first ``defrag'' your
DOS partition, using the DOS 6.xx <tt/DEFRAG/ utility or the DOS partition, using the DOS 6.xx <tt/DEFRAG/ utility or the
@ -868,8 +868,9 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
where the presence of the psm0 driver will cause the keyboard to where the presence of the psm0 driver will cause the keyboard to
lock up (which is why this driver is not present by default in the lock up (which is why this driver is not present by default in the
GENERIC kernel). This can sometimes be fixed by bouncing the GENERIC kernel). This can sometimes be fixed by bouncing the
NumLock key during the boot process. The real NumLock key during the boot process. Also suggest going into CMOS
fix is, of course, to merge the PS/2 mouse driver with syscons. setup and toggling any value for Numlock On/Off at boot time. The
real fix is, of course, to merge the PS/2 mouse driver with syscons.
Any volunteers? :) Any volunteers? :)
<sect1> <sect1>