X86: How do I use COM1 as /dev/console?

X86: How do I use COM1 as /dev/console?

Post by Patrick Nozisk » Thu, 13 Mar 1997 04:00:00



We have an appliction where we need to run Solaris 2.4/5 on "video-less"
x86 PCs, but we cannot figure out how to get the boot program to use COM1
or COM2 as /dev/console. We have already configured the BIOS in these
machines to send POST output to COM1, but we se no place where we can
configure bootstrap code to treat COM1 as /dev/console, like we can do
with SCO UNIX.

Any ideas?
Thanks
Pat

 
 
 

X86: How do I use COM1 as /dev/console?

Post by Phillip Wagstr » Fri, 14 Mar 1997 04:00:00



Quote:>We have an appliction where we need to run Solaris 2.4/5 on "video-less"
>x86 PCs, but we cannot figure out how to get the boot program to use COM1
>or COM2 as /dev/console. We have already configured the BIOS in these
>machines to send POST output to COM1, but we se no place where we can
>configure bootstrap code to treat COM1 as /dev/console, like we can do
>with SCO UNIX.

>Any ideas?
>Thanks
>Pat

        You need to do the following steps.

1) attach the terminal to COM1
2) edit your /etc/system file and add the entry
      "set console=1"
3) halt and reboot the system

Note:  The system banner will still be displayed to the origional console, but it will redirect to COM1 immediately afterwards.

This only works with COM1, any other COM port isn't supported.

        To change this back...
1) enter a "b -a" at the boot interpreter
2) When it asks for default boot environment settings (default is /etc/system) enter
        /dev/null
3) edit /etc/system and remove "set console=1"
4) halt and reboot.

Hope it helps,
Phil

---
     ______
    /_____/\
   /____ \\ \                       /------------------------------------\
  /_____\ \\ /   "Play with         | The opinions expressed are my own  |
 /_____/ \/ / /    boundaries,      | and not those of Sun Microsystems  |
/_____/ /   \//\    Not within."    /------------------------------------\
\_____\//\   / /                    | Phillip A. Wagstrom, SSE           |
 \_____/ / /\ /                     | Sun Microsystems, Inc.  SunService |

   \_____\ \\                       | Ph. 415.336.9860  FAX 415.336-9610 |
    \_____\/                        \------------------------------------/

 
 
 

X86: How do I use COM1 as /dev/console?

Post by John Bens » Sat, 15 Mar 1997 04:00:00


     In an x86 system with no video hardware at
all, what happens to the secondary boot interpreter?
Can it be made to talk out com1?  Otherwise,
you can't get there from here.  The system can be
switched to com1 only after it is done being booted,
and it won't boot.


      John Benson
      Space Science and Engineering
      University of WIsconsin

>    You need to do the following steps.
>1) attach the terminal to COM1
>2) edit your /etc/system file and add the entry
>      "set console=1"
>3) halt and reboot the system
>Note:  The system banner will still be displayed to the origional console, but it will redirect to COM1 immediately afterwards.
>This only works with COM1, any other COM port isn't supported.
>    To change this back...
>1) enter a "b -a" at the boot interpreter
>2) When it asks for default boot environment settings (default is /etc/system) enter
>    /dev/null
>3) edit /etc/system and remove "set console=1"
>4) halt and reboot.
>Hope it helps,
>Phil
>---
>     ______
>    /_____/\
>   /____ \\ \                       /------------------------------------\
>  /_____\ \\ /   "Play with         | The opinions expressed are my own  |
> /_____/ \/ / /    boundaries,      | and not those of Sun Microsystems  |
>/_____/ /   \//\    Not within."    /------------------------------------\
>\_____\//\   / /                    | Phillip A. Wagstrom, SSE               |
> \_____/ / /\ /                     | Sun Microsystems, Inc.  SunService |

>   \_____\ \\                       | Ph. 415.336.9860  FAX 415.336-9610 |
>    \_____\/                        \------------------------------------/

 
 
 

X86: How do I use COM1 as /dev/console?

Post by Phillip Wagstr » Sat, 15 Mar 1997 04:00:00



Quote:>     In an x86 system with no video hardware at
>all, what happens to the secondary boot interpreter?
>Can it be made to talk out com1?  Otherwise,
>you can't get there from here.  The system can be
>switched to com1 only after it is done being booted,
>and it won't boot.

        This has to be set-up in the hardware.  Presumably if you're going to do this, you have a bios that will support taking I/O from COM1 instead.  If the POST messages are going to a non-existant console, then yes, this won't work.
        The console directive in the /etc/system file will tell the OS what to use as
its console.  The secondary boot interpreter gets its info from the BIOS... if you
can't change the BIOS setting then I wouldn't recommend doing this.

Regards,
Phil


>      John Benson
>      Space Science and Engineering
>      University of WIsconsin

>>        You need to do the following steps.

>>1) attach the terminal to COM1
>>2) edit your /etc/system file and add the entry
>>      "set console=1"
>>3) halt and reboot the system

>>Note:  The system banner will still be displayed to the origional console, but it will redirect to COM1 immediately afterwards.

>>This only works with COM1, any other COM port isn't supported.

>>        To change this back...
>>1) enter a "b -a" at the boot interpreter
>>2) When it asks for default boot environment settings (default is /etc/system) enter
>>        /dev/null
>>3) edit /etc/system and remove "set console=1"
>>4) halt and reboot.

>>Hope it helps,
>>Phil

---
     ______
    /_____/\
   /____ \\ \                       /------------------------------------\
  /_____\ \\ /   "Play with         | The opinions expressed are my own  |
 /_____/ \/ / /    boundaries,      | and not those of Sun Microsystems  |
/_____/ /   \//\    Not within."    /------------------------------------\
\_____\//\   / /                    | Phillip A. Wagstrom, SSE           |
 \_____/ / /\ /                     | Sun Microsystems, Inc.  SunService |

   \_____\ \\                       | Ph. 415.336.9860  FAX 415.336-9610 |
    \_____\/                        \------------------------------------/
 
 
 

1. >/dev/msglog 2<>/dev/msglog </dev/console

In inittab, some entry is entitled with ">/dev/msglog 2<>/dev/msglog
</dev/console",  what is that used for? Why need it followed by the
standard entry?

Such as
Example--Default inittab File
The following example shows an annotated default inittab file:
 1 ap::sysinit:/sbin/autopush -f /etc/iu.ap
 2 ap::sysinit:/sbin/soconfig -f /etc/sock2path
 3 fs::sysinit:/sbin/rcS sysinit   >/dev/msglog 2<>/dev/msglog
</dev/console
 4 is:3:initdefault:
 5 p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog
2<>/dev/...
 6 sS:s:wait:/sbin/rcS              >/dev/msglog 2<>/dev/msglog
</dev/console
 7 s0:0:wait:/sbin/rc0              >/dev/msglog 2<>/dev/msglog
</dev/console
 8 s1:1:respawn:/sbin/rc1           >/dev/msglog 2<>/dev/msglog
</dev/console
 9 s2:23:wait:/sbin/rc2             >/dev/msglog 2<>/dev/msglog
</dev/console
 10 s3:3:wait:/sbin/rc3             >/dev/msglog 2<>/dev/msglog
</dev/console
 11 s5:5:wait:/sbin/rc5             >/dev/msglog 2<>/dev/msglog
</dev/console
 12 s6:6:wait:/sbin/rc6             >/dev/msglog 2<>/dev/msglog
</dev/console
 13 fw:0:wait:/sbin/uadmin 2 0      >/dev/msglog 2<>/dev/msglog
</dev/console
 14 of:5:wait:/sbin/uadmin 2 6      >/dev/msglog 2<>/dev/msglog
</dev/console
 15 rb:6:wait:/sbin/uadmin 2 1      >/dev/msglog 2<>/dev/msglog
</dev/console
 16 sc:234:respawn:/usr/lib/saf/sac -t 300
 17 co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console
login: "
    -T terminal-type -d /dev/console -l console -m ldterm,ttcompat  

in
http://docs.sun.com/db/doc/805-7228/6j6q7uepg?a=view

2. FD-1670/80 SCSI Controller

3. Dial on demand Help Request

4. Console on /dev/tty00? Sol. 2.1 for x86

5. Large disks without BIOS upgrade (linux lacks a driver?)

6. Unix COM1 to Winodws COM1 Connection

7. Sound Blaster PCI512

8. Q: using /dev/fb0 for console IO

9. serial console com1 problem

10. console on com1

11. System console to COM1

12. Using the mouse port as a kernal console (can it be done)?