06-02-2003
By default the suns will assume that you are using some kind of terminal if no keyboard is connected to the box. All output/input will be sent trough com port 1 .
Do as tio tony suggested. Use a terminal or a terminal program such as reflection or minicom (on unix) and connect a null modem cable to the sparcs first com port.
The suns use special keyboards becuase the mouse is connected to the keyboard and so the keyboard and mouse share the same PS2 connector in the sparc. So a PC keyboard will not work!
/Peter
8 More Discussions You Might Find Interesting
1. Cybersecurity
Hello,
I in the process of installing a firewall. I'm new to this topic and would like to know if someone can point me in the right direction.
I'm running Solaris 8.
Thanks in advance. (2 Replies)
Discussion started by: sunoracle
2 Replies
2. HP-UX
I am new to HP-UX. I have a external SCSI drive with HP-UX on it. I was trying to clone it to another external scsi drive. I added the new drive to existing LVM. Then I used dd command. But it failed with I/O error. Now I cannot boot it from original drive. It's saying panic: LVM: Configuration... (11 Replies)
Discussion started by: forhad
11 Replies
3. SCO
hi
I've boot OpenServer Release 5.0.7 from a setup CD and started "Execute a shell on ramdisk filesystem".
Howto change keyboard from american to swiss german? (0 Replies)
Discussion started by: ccc
0 Replies
4. Solaris
I have a Solaris 10 Sparc box that has suddenly stopped allowing users to ssh into the box. I've connected a laptop and can access the box as root using a serial connector. While performing the command svcs -xv, this is my output:
maintenance 13:29:49 svc:/system/basicreg:default... (4 Replies)
Discussion started by: goose25
4 Replies
5. Solaris
Hello,
Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies
6. Solaris
We have a Solaris 10 system with a solaris 9 branded zone. Trying to create a new lo interfaces i ended up rebooting the zone. The zone will not come up, it ran fine before i tried this. When i run the zoneadm -z zone-s9 boot command i get
"zoneadm: zone 'zone-s9': lo0:2: could not bring... (4 Replies)
Discussion started by: oly_r
4 Replies
7. SCO
HI All,
I have an old SCO-UNIX machine which I support a long standing client / friend with.
I don't use it very often, and is kept switched off. All was well 2 weeks ago, but when I tried to boot today all I get is a continuous set of long beeps but no booting. I have checked inside... (4 Replies)
Discussion started by: andy sleight
4 Replies
8. Solaris
What's the cheapest box to study for the Solaris tests with? The obvious answer is a T1000, but IIRC they have no CD/DVD and have to be jumpstarted. What's cheap that can run Solaris 11 and that doesn't require anything but itself? (5 Replies)
Discussion started by: jnojr
5 Replies
LEARN ABOUT NETBSD
wsmuxctl
WSMUX(4) BSD Kernel Interfaces Manual WSMUX(4)
NAME
wsmux -- console keyboard/mouse multiplexor for wscons
SYNOPSIS
wskbd* at ... mux 1
wsmouse* at ... mux 0
pseudo-device wsmux
DESCRIPTION
The wsmux is a pseudo-device driver that allows several wscons(4) input devices to have their events multiplexed into one stream.
The typical usage for this device is to have two multiplexors, one for mouse events and one for keyboard events. All wsmouse(4) devices
should direct their events to the mouse mux (normally 0) and all keyboard devices, except the console, should direct their events to the key-
board mux (normally 1). A device will send its events to the mux indicated by the mux locator. If none is given the device will not use a
multiplexor. The keyboard multiplexor should be connected to the display, using the wsconscfg(8) command. It will then receive all key-
strokes from all keyboards and, furthermore, keyboards can be dynamically attached and detached without further user interaction. In a simi-
lar way, the window system will open the mouse multiplexor and receive all mouse events; mice can also be dynamically attached and detached.
If a wskbd(4) or wsmouse(4) device is opened despite having a mux it will be detached from the mux.
It is also possible to inject events into a multiplexor from a user program.
FILES
For each mux device, /dev/wsmuxN there is a control device /dev/wsmuxctlN. The control device has a minor number 128 greater than the regu-
lar mux device. It can be used to control the mux even when it is open, e.g., by wsmuxctl(8).
/dev/wsmouse a.k.a. /dev/wsmux0
/dev/wskbd a.k.a. /dev/wsmux1
/usr/include/dev/wscons/wsconsio.h
SEE ALSO
wscons(4), wsdisplay(4), wskbd(4), wsmouse(4), moused(8), wsconscfg(8), wsconsctl(8), wsfontload(8), wsmoused(8), wsmuxctl(8)
BSD
July 26, 1999 BSD