Additional sgimips FAQ entry

Hi,
the attached diff adds a new item to the sgimips FAQ
documenting an issue I
ran into while installing NetBSD on an O2. This is not a
particularly big
one, but I had wished this information would have been
somewhere when I 
tried to install for the first time.

Regards,
Daniel
 
-- 
Daniel Sieger
Faculty of Technology
Bielefeld University
wwwhomes.uni-bielefeld.de/dsieger
Index: faq.xml
============================================================
=======
RCS file: /cvsroot/htdocs/Ports/sgimips/faq.xml,v
retrieving revision 1.7
diff -b -u -r1.7 faq.xml
--- faq.xml	17 Dec 2006 23:10:09 -0000	1.7
+++ faq.xml	17 Dec 2006 23:34:33 -0000
 -267,6
+267,28 
 
 </sect3>
 
+<sect3 id="installing-on-o2">
+<title>Notes about installing on an O2</title>
+<para>
+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
+<programlisting># cu -l
/dev/ttyXX</programlisting> where XX is the 
+serial port used on your remote machine (usually
+<filename>/dev/tty00</filename> or
+<filename>/dev/tty01</filename>). 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
+<programlisting>> setenv console
serial</programlisting>
+Afterwards, you can just follow the normal installation
procedure
+described in the <ulink
+url="ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-&relea
se.latest;/sgimips/INSTALL.html#Preparing%20your%20System%20
for%20NetBSD%20installation">NetBSD/sgimips
+&release.latest; Install Notes</ulink>.
+</para>
+</sect3>
+
 </sect2>
 
 <sect2 id="other">

On Mon, 18 Dec 2006, Daniel Sieger wrote:
> the attached diff adds a new item to the sgimips FAQ
documenting an issue I
> ran into while installing NetBSD on an O2. This is not
a particularly big
> one, but I had wished this information would have been
somewhere when I
> tried to install for the first time.

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?


  - Hubert

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.

Regards,
Daniel

-- 
Daniel Sieger
Faculty of Technology
Bielefeld University
wwwhomes.uni-bielefeld.de/dsieger
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)
 .It
 Video hardware
 .It
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
 .Pp
+.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
+.Pp
+.Dl "# cu -l /dev/ttyXX
+.Pp
+where XX is the serial port used on your remote machine
(usually
+.Pa /dev/tty00
+or
+.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
+.Pp
+.Dl "> setenv console serial
+.Pp
+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.
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>
     </itemizedlist>
   </portsection>

On Mon, 18 Dec 2006, Daniel Sieger wrote:
> 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.

I've committed your changes. Please drop me a note when the
O2's 
framebuffer is supported. 

Thanks!


  - Hubert