Subject: Re: Additional sgimips FAQ entry
To: Hubert Feyrer <>
From: Daniel Sieger <dsieger@TechFak.Uni-Bielefeld.DE>
List: netbsd-docs
Date: 12/18/2006 23:25:12
Content-Type: multipart/mixed; boundary="Md/poaVZ8hnGTzuv"
Content-Disposition: inline

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 18, 2006 at 09:13:06PM +0100, Hubert Feyrer wrote:
> I think this should better go into the official install docs... can you=
> have a look at src/distrib/notes/sgimips (etc.) and provide a patch for=
> that, so we have everything in one place?

Sounds reasonable. sgimips-notes.diff adds these notes to the "Preparing
your System for NetBSD installation" section and explicitly mentions the
lack of O2 frambuffer suport in the "Unsupported devices" section.
sgimips-index.diff also explicitly mentions the lack of support for the
framebuffer in the NetBSD/sgimips port index page.


Daniel Sieger
Faculty of Technology
Bielefeld University

Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="sgimips-notes.diff"

Index: hardware
RCS file: /cvsroot/src/distrib/notes/sgimips/hardware,v
retrieving revision 1.12
diff -b -u -r1.12 hardware
--- hardware	3 Sep 2006 19:19:14 -0000	1.12
+++ hardware	18 Dec 2006 21:54:28 -0000
@@ -119,7 +119,7 @@
 .Ss2 Unsupported devices
 .(bullet -offset indent
-Some graphics adapters
+Some graphics adapters (e.g. the O2 framebuffer)
 Video hardware
Index: prep
RCS file: /cvsroot/src/distrib/notes/sgimips/prep,v
retrieving revision 1.6
diff -b -u -r1.6 prep
--- prep	1 Mar 2005 00:23:59 -0000	1.6
+++ prep	18 Dec 2006 21:54:28 -0000
@@ -52,5 +52,25 @@
 .Dl # Ic sysctl -w net.inet.ip.anonportmin=16384
 .Dl # Ic sysctl -w net.inet.ip.anonportmax=32767
+.Ic Note about installing on a O2:
+Unfortunately, the O2 graphics hardware is not supported yet. Thus,
+you have to use a serial console to boot and install
+NetBSD. Disconnect the keyboard from your target machine. Connect the
+O2 with a standard DB9 serial cable to a remote machine. After
+powering up the O2 you can connect to the serial console with
+.Dl "# cu -l /dev/ttyXX
+where XX is the serial port used on your remote machine (usually
+.Pa /dev/tty00
+.Pa /dev/tty01
+). Enter the Command Monitor from the System Maintenance Menu. In
+order to boot the kernel properly you also have to modify the PROM
+environment with
+.Dl "> setenv console serial
+Afterwards, just continue with the normal installation procedure.
 .\" The O2 internal MACE Ethernet chip isn't supported yet, so to boot the O2
 .\" and mount nfsroot, you will need an external NIC in the PCI slot.

Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="sgimips-index.diff"

Index: index.xml
RCS file: /cvsroot/htdocs/Ports/sgimips/index.xml,v
retrieving revision 1.17
diff -b -u -r1.17 index.xml
--- index.xml	14 Nov 2006 23:19:27 -0000	1.17
+++ index.xml	18 Dec 2006 21:59:33 -0000
@@ -199,7 +199,7 @@
       <listitem>R10000 Power Indigo2 (IP28) (on-going)</listitem>
       <listitem>Octane (IP30) (required mips64 toolchain)</listitem>
       <listitem>L2 cache on machines with R4600 CPU</listitem>
-      <listitem>framebuffers not listed above</listitem>
+      <listitem>Framebuffers not listed above (e.g. the O2 (IP32) framebuffer)</listitem>
       <listitem>etc. etc.</listitem>


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.4 (SunOS)