>Number:         35169
>Category:       install
>Synopsis:       Some install notes fixes
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    install-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Dec 02 18:15:00 +0000 2006
>Originator:     dieter roelants
>Release:        NetBSD 4.0
>Organization:
>Environment:
>Description:
	- While reading install/12957 it was suggested
	(http://mail-index.netbsd.org/port-i386/2006/11/27/0000.html)
	that all notes, marked with '[PCMCIA]' should go and be
	replaced with a more generic explanation about removable
	devices.
	- I noticed the HTML output concatenates 'NetBSD' and '4.0',
	which is ugly.
	- The IP addresses for ftp.NetBSD.org are wrong.
>How-To-Repeat:
>Fix:
Index: common/main
===================================================================
RCS file: /cvsroot/src/distrib/notes/common/main,v
retrieving revision 1.320
diff -u -r1.320 main
--- common/main	29 Nov 2006 04:34:37 -0000	1.320
+++ common/main	2 Dec 2006 18:07:15 -0000
@@ -68,8 +68,8 @@
 .Pp
 .
 This document describes the installation procedure for
-.Nx \*V
-on the
+.Nx
+\*V on the
 .Em \*M
 platform.
 It is available in four different formats titled
@@ -109,8 +109,8 @@
 .Pp
 This section contains some brief notes describing what you need to
 install
-.Nx \*V
-on a machine of the \*M architecture.
+.Nx
+\*V on a machine of the \*M architecture.
 .Bl -bullet
 .It
 Fetch the
@@ -401,8 +401,8 @@
 across fifteen distinct CPU families,
 and is being ported to more.
 The
-.Nx \*V
-release contains complete binary releases for many different
+.Nx
+\*V release contains complete binary releases for many different
 system architectures.
 (A few ports are not fully supported at this time 
 and are thus not part of the binary distribution.
@@ -443,8 +443,8 @@
 .Pp
 It is impossible to completely summarize a year of development that
 went into the
-.Nx \*V
-release.
+.Nx
+\*V release.
 Some highlights include:
 .
 .Ss2 Kernel
@@ -611,8 +611,8 @@
 .Pp
 .
 The root directory of the
-.Nx \*V
-release is organized as follows:
+.Nx
+\*V release is organized as follows:
 .ie \n[FOR_RELEASE] \{\
 .Pp
 .Pa .../NetBSD-\*V/
@@ -625,8 +625,8 @@
 Last minute changes.
 .It Li MIRRORS
 A list of sites that mirror the
-.Nx \*V
-distribution.
+.Nx
+\*V distribution.
 .It Li README.files
 README describing the distribution's contents.
 .It Li TODO
@@ -640,8 +640,8 @@
 .Pp
 In addition to the files and directories listed above, there is one
 directory per architecture, for each of the architectures for which
-.Nx \*V
-has a binary distribution.
+.Nx
+\*V has a binary distribution.
 .Pp
 The source distribution sets can be found in subdirectories of the
 .Pa source
@@ -669,8 +669,8 @@
 .showsize 5 20
 .It Sy src
 This set contains all of the base
-.Nx \*V
-sources which are not in
+.Nx
+\*V sources which are not in
 .Sy gnusrc ,
 .Sy sharesrc ,
 or
@@ -678,8 +678,8 @@
 .showsize 37 176
 .It Sy syssrc
 This set contains the sources to the
-.Nx \*V
-kernel for all architectures;
+.Nx
+\*V kernel for all architectures;
 .Xr config 1 ;
 and
 .Xr dbsym 8 .
@@ -811,7 +811,8 @@
 .Nx
 may wish to bear the
 following problems and compatibility issues in mind when upgrading to
-.Nx \*V .
+.Nx
+\*V .
 .
 .Ss2 Issues affecting an upgrade from NetBSD 1.6
 The following issues can generally be resolved by extracting the
Index: common/sysinst
===================================================================
RCS file: /cvsroot/src/distrib/notes/common/sysinst,v
retrieving revision 1.77
diff -u -r1.77 sysinst
--- common/sysinst	25 Nov 2006 22:53:35 -0000	1.77
+++ common/sysinst	2 Dec 2006 18:07:15 -0000
@@ -33,14 +33,6 @@
 .\"
 .
 .
-.de (pcmcia
-.	Bl -tag -width x[PCMCIA]x
-.It [ Tn PCMCIA ]
-..
-.de pcmcia)
-.	El
-..
-.
 .
 .\" Define strings for partition references:
 .\"	\*[part_raw]	`raw' partition (usually `c' or `d')
@@ -95,197 +87,18 @@
 .
 .if !\n[acorn26]:\n[acorn32]\n[atari]:\n[mac68k]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[newsmips]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k] \{\
 .It
-.To 2 "Possible PCMCIA issues"
-.Em Possible Tn PCMCIA Em issues
-.Pp
-Machines with
-.Tn PCMCIA
-slots may have problems during installation.
-If you do not have
-.Tn PCMCIA
-on your machine
-.Tn ( PCMCIA
-is only really used on laptop machines),
-you can skip this section, and ignore the
-.Dq Bq Tn PCMCIA
-notes.
-If you do have
-.Tn PCMCIA
-in your machine, you can safely ignore this section and the
-.Dq Bq Tn PCMCIA
-the first time, as you are likely to not have problems.
-Should troubles
-occur during floppy boot, they may be
-.Tn PCMCIA
-specific.
-You should then re-read this section and try again,
-following the instructions in the
-.Dq Bq Tn PCMCIA
-notes.
-.Pp
-This section explains how to work around the installation problem.
-.Pp
-The kernel keeps careful track of what interrupts
-and I/O ports are in use during autoconfiguration.
-It then allows the
-.Tn PCMCIA
-devices to pick unused interrupts and I/O ports.
-Unfortunately, the
-.Tn Li INSTALL
-kernel may not detect all devices in your system.
-This may be because the
-.Tn Li INSTALL
-kernel only supports the minimum set of devices to install
-.Nx
-on your system, or it may be that
-.Nx
-does not have support for the device causing the conflict.
-.Pp
-For example, suppose your laptop has a
-soundblaster device built in; the
-.Tn Li INSTALL
-kernel has no sound support.
-The
-.Tn PCMCIA
-code might allocate your soundblaster's
-.Tn IRQ
-and I/O ports to
-.Tn PCMCIA
-devices, causing them not to work, or to lock up the system.
-This is especially bad if one of the devices in question is your ethernet card.
-.Pp
-The kernel attempts to probe for available interrupts that are
-usable by the
-.Tn PCIC
-.Tn ( PCMCIA
-interrupt controller), which 
-should alleviate interrupt conflicts;
-however, I/O port conflicts are still possible.
-.Pp
-This problem will impact some, but not all, users of
-.Tn PCMCIA .
-If this problem is affecting you, watch the
-.Dq Bq Tn PCMCIA
-notes that will appear in this document.
-.if \n[i386] \{\
-.Pp
-It can be difficult to distinguish an interrupt conflict from
-an I/O space conflict.
-There are no hard-and-fast rules, but
-interrupt conflicts are more likely to lock up the machine,
-and I/O space conflicts are more likely to result in misbehavior
-(e.g. a network card that cannot send or receive packets).
-.Pp
-The kernel selects a free interrupt according to a mask of allowable
-interrupts, stored in the kernel global variable
-.Va pcic_isa_intr_alloc_mask .
-This mask is a logical-or of power-of-2s of allowable interrupts:
-.(disp
-IRQ  Val     IRQ  Val     IRQ  Val      IRQ  Val
-  0  0x0001    4  0x0010    8  0x0100    12  0x1000
-  1  0x0002    5  0x0020    9  0x0200    13  0x2000
-  2  0x0004    6  0x0040   10  0x0400    14  0x4000
-  3  0x0008    7  0x0080   11  0x0800    15  0x8000
-.disp)
-.Pp
-For example, 0x0a00 allows both IRQ 9 and IRQ 11.
-By default, the
-.Tn Li INSTALL
-kernel permits all IRQs other than IRQs 5 and 7, so the corresponding
-mask is 0xff5f.
-The
-.Tn Li GENERIC
-kernel, however, allows all IRQs.
-(The presumption here is that IRQ 10 may be assigned to a device that the
-.Tn Li GENERIC
-kernel
-supports, but that the
-.Tn Li INSTALL
-does not.)
-Because of support for interrupt probing, it is no
-longer necessary to exclude IRQs 3 and 5 explicitly; if they are
-in use, they should not be assigned to
-.Tn PCMCIA .
-.Pp
-The kernel selects IO space by assigning cards IO space within a
-predefined range.
-The range is specified as a base and size,
-specified by the kernel global variables
-.Va pcic_isa_alloc_iobase
-and
-.Va pcic_isa_alloc_iosize .
-For systems with 12-bit addressing (most systems), the kernel defaults to a
-base of 0x400 and a size of 0xbff (a range of 0x400-0xfff).
-For systems with 10-bit addressing, the kernel defaults to a
-base of 0x300 and a size of 0xff (range of 0x300-0x3ff).
-.Pp
-Unfortunately, these ranges may conflict with some devices.
-In the event of a conflict, try a base of 0x330 with a size of 0x0bf (range
-of 0x330-0x3ff).
-.Pp
-In order to work around this at installation time, you may
-interrupt the 5 second countdown when booting the
-.Tn Li INSTALL
-kernel, and use
-.Ic boot Fl d ,
-in order to enter
-.Xr ddb 4
-(the in-kernel debugger), and then use the
-.Ic write
-command to alter the variable values:
-.Pp
-.Dl db\*> Ic "write pcic_isa_intr_alloc_mask 0x0a00"
-.Dl "pcic_isa_intr_alloc_mask            0xff5f = 0xa00"
-.Dl db\*> Ic "write pcic_isa_alloc_iobase 0x330"
-.Dl "pcic_isa_alloc_iobase               0x400 = 0x330"
-.Dl db\*> Ic "write pcic_isa_alloc_iosize 0x0bf"
-.Dl "pcic_isa_alloc_iosize               0xbff = 0xbf"
-.Dl db\*> Ic "continue"
-.Pp
-Note that, since some floppy images may not have symbol information in
-the kernel, you may have to consult the matching
-.Pa .symbols
-file in the
-.Pa binary/kernel
-directory in the installation tree.
-Find the pcic_ symbols used above,
-look at the hexadecimal value in the first column, and write, for
-example (if
-.Va pcic_isa_intr_alloc_mask
-is equal to c0513e3c):
+.To 2 "Possible hardware problems"
+.Em Possible hardware problems
 .Pp
-.Dl db\*> Ic "write 0xc0513e3c 0x0a00"
-.Pp
-.
-After installation, this value can be permanently written to the kernel image
-directly with:
-.Pp
-.Dl # Ic "cp /netbsd /netbsd.bak"
-.Dl # Ic "gdb --write /netbsd"
-.Dl (gdb) Ic "set pcic_isa_intr_alloc_mask=0x0a00"
-.Dl (gdb) Ic "set pcic_isa_alloc_iobase=0x330"
-.Dl (gdb) Ic "set pcic_isa_alloc_iosize=0x0bf"
-.Dl (gdb) Ic "quit"
-.Dl #
-.Pp
-or you could specify these value when configuring your kernel, e.g.:
-.(disp
-options PCIC_ISA_INTR_ALLOC_MASK=0x0a00
-options PCIC_ISA_ALLOC_IOBASE=0x330
-options PCIC_ISA_ALLOC_IOSIZE=0x0bf
-.disp)
-.Pp
-If you can
-get your
-.Tn PCMCIA
-card to work using this hack, you may also ignore the
-.Bq Tn PCMCIA
-notes later in this document.
-.Pp
-We hope to provide a more elegant solution to this problem in a future
-.Nx
-release.
-.\} \" \n[i386]
+Should you encounter hardware problems during installation, try
+rebooting after unplugging removable devices you don't need for
+installation.
+Non-removable devices can be disabled with
+.Ic userconf
+(use
+.Ic boot
+.Fl c
+to enter it).
 .\} \" !\n[acorn26]:\n[atari]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[newsmips]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k]
 .if \n[mac68k] \{\
 .It
@@ -729,14 +542,6 @@
 .To 2 "Booting NetBSD"
 .Em Booting NetBSD
 .
-.if !\n[acorn26]:\n[acorn32]\n[atari]:\n[cats]:\n[mac68k]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[newsmips]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k] \{\
-.(pcmcia
-Unplug your
-.Tn PCMCIA
-devices, so that they won't be found by
-.Nx .
-.pcmcia)
-.\} \" !\n[acorn26]:\n[atari]:\n[cats]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k]
 .ie \n[mac68k] \{\
 .Pp
 Prior to attempting to boot
@@ -933,12 +738,6 @@
 .It
 .To 2 "Network configuration"
 .Em Network configuration
-.if !\n[acorn26]:\n[acorn32]:\n[atari]:\n[cats]:\n[mac68k]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[newsmips]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k] \{\
-.(pcmcia
-You can skip this section, as you will only get data
-from floppy in the first part of the install.
-.pcmcia)
-.\} \" !\n[acorn26]:\n[atari]:\n[cats]:\n[mac68k]:\n[macppc]:\n[mvme68k]:\n[news68k]:\n[newsmips]:\n[pmax]:\n[sgimips]:\n[sparc]:\n[sparc64]:\n[x68k]
 .Pp
 If you will not use network operation during the installation,
 but you do want your machine to be configured for networking once
@@ -1685,46 +1484,6 @@
 .It
 .To 2 "Getting the distribution sets"
 .Em Getting the distribution sets
-.if \n[i386] \{\
-.(pcmcia
-.
-Load a kernel tar file (i.e. the
-.Pa kern-GENERIC.tgz
-set file)
-on to your hard disk, for example by mounting the
-hard disk first, copying the
-.Pa kern-GENERIC.tgz
-file from floppy and unpacking it.
-Example:
-.Pp
-.Dl # Ic "mount /dev/wd0a /mnt"
-.Dl # Ic "cd /mnt"
-.Pp
-.D1 Em "repeat the following 3 steps until all kern.* files are there"
-.Dl # Ic "mount -t msdos /dev/fd0a /mnt2"
-.Dl # Ic "cp /mnt2/kern.* ."
-.Dl # Ic "umount /mnt2"
-.Dl # Ic "cat kern.* \&| tar zxpvf -"
-.Pp
-Then halt the machine using the
-.Ic halt
-command.
-Power the machine down, and re-insert all the
-.Tn PCMCIA
-devices.
-Remove any floppy from the floppy drive.
-Start the machine up.
-After booting
-.Nx ,
-you will
-be presented with the main
-.Ic sysinst
-menu.
-Choose the option to re-install sets.
-Wait for the file system checks that it will do to finish, and then proceed
-as described below.
-.pcmcia)
-.\}
 .Pp
 The
 .Nx
@@ -1988,7 +1747,8 @@
 .Em Finalizing your installation
 .Pp
 Congratulations, you have successfully installed
-.Nx \*V .
+.Nx
+\*V .
 .if \n[cats] \{\
 .Pp
 To finalize the installation of
Index: common/xfer
===================================================================
RCS file: /cvsroot/src/distrib/notes/common/xfer,v
retrieving revision 1.53
diff -u -r1.53 xfer
--- common/xfer	25 Nov 2006 21:07:32 -0000	1.53
+++ common/xfer	2 Dec 2006 18:07:15 -0000
@@ -708,10 +708,10 @@
 installation, the IPv4 address of
 .Sy ftp.NetBSD.org
 is
-.Li 204.152.184.75
+.Li 204.152.184.36
 and the IPv6 address is
-.Li 2001:4f8:4:7:2e0:81ff:fe21:6563
-(as of June, 2004).
+.Li 2001:4f8:1:c:230:48ff:fe31:43f2
+(as of December, 2006).
 .Pp
 Once you have this information, you can proceed to the next
 step in the installation or upgrade process.