SEO

I have a wyse 370 terminal that is hanging an Ultra-II when I turn the
terminal off.

The sun goes to the ok prompt when the terminal attached to ttya is
switched off..

How can i resolve this?

here is the eeprom output:

tpe-link-test?=true
scsi-initiator-id=7
keyboard-click?=false
keymap: data not available.
sbus-probe-list=e01
ttyb-rts-dtr-off=true
ttyb-ignore-cd=true
ttya-rts-dtr-off=true
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
mfg-mode=off
diag-level=max
#power-cycles=136
system-board-serial#=xxxxxxxx
system-board-date=345fb396
fcode-debug?=false
output-device=screen
input-device=keyboard
load-base=16384
boot-command=boot
auto-boot?=true
watchdog-reboot?=false
diag-file: data not available.
diag-device=disk
boot-file: data not available.
boot-device=disk:a disk0 disk1
local-mac-address?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
silent-mode?=false
use-nvramrc?=false
nvramrc: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
hardware-revision: data not available.
last-hardware-update: data not available.
diag-switch?=false

In comp.unix.solaris BN <BN@bn.como> wrote:
> I have a wyse 370 terminal that is hanging an Ultra-II when I turn the
> terminal off.

> The sun goes to the ok prompt when the terminal attached to ttya is
> switched off..

> How can i resolve this?

Disable (or better, activate the alternate sequence) for aborts. It's
not explicitly listed, but the alternate sequence is the 3 characters:
<enter> <~> <ctrl-b>

man kbd for instructions on changing it immediately and for future
reboots.

> here is the eeprom output:

Won't matter.

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

BN wrote:
> I have a wyse 370 terminal that is hanging an Ultra-II when I turn the
> terminal off.
>
> The sun goes to the ok prompt when the terminal attached to ttya is
> switched off..
>
> How can i resolve this?
>
> here is the eeprom output:
>
> tpe-link-test?=true
> scsi-initiator-id=7
> keyboard-click?=false
> keymap: data not available.
> sbus-probe-list=e01
> ttyb-rts-dtr-off=true
> ttyb-ignore-cd=true
> ttya-rts-dtr-off=true
> ttya-ignore-cd=true
> ttyb-mode=9600,8,n,1,-
> ttya-mode=9600,8,n,1,-
> mfg-mode=off
> diag-level=max
> #power-cycles=136
> system-board-serial#=xxxxxxxx
> system-board-date=345fb396
> fcode-debug?=false
> output-device=screen
> input-device=keyboard
> load-base=16384
> boot-command=boot
> auto-boot?=true
> watchdog-reboot?=false
> diag-file: data not available.
> diag-device=disk
> boot-file: data not available.
> boot-device=disk:a disk0 disk1
> local-mac-address?=false
> ansi-terminal?=true
> screen-#columns=80
> screen-#rows=34
> silent-mode?=false
> use-nvramrc?=false
> nvramrc: data not available.
> security-mode=none
> security-password: data not available.
> security-#badlogins=0
> oem-logo: data not available.
> oem-logo?=false
> oem-banner: data not available.
> oem-banner?=false
> hardware-revision: data not available.
> last-hardware-update: data not available.
> diag-switch?=false

At power-off, the terminal probably sends a break. A break will put the
sun machine to the ok prompt. I've seen this happen with PC's used as
terminals.
One workaround would be to detach the serial cable before you switch the
terminal off. There might be other (and far better) solutions for this
behaviour though, but I don't know them.

--
Best regards,
Jeroen Besse
(to contact me: the nospam address actually exists)

Jeroen Besse wrote On 09/27/05 19:44,:

> One workaround would be to detach the serial cable before you switch the
> terminal off. There might be other (and far better) solutions for this
> behaviour though, but I don't know them.


Detaching the cable can also look like a break to the serial port.
Better to use the "alt-break" sequence.

On 2005-09-28 01:44, Jeroen Besse wrote:
-snip-
>
> At power-off, the terminal probably sends a break. A break will put the
> sun machine to the ok prompt. I've seen this happen with PC's used as
> terminals.

I know the Hyperterminal application found on Win2000 caused a break
when the application was closed. Teraterm worked fine on same PC:s.

> One workaround would be to detach the serial cable before you switch the
> terminal off. There might be other (and far better) solutions for this
> behaviour though, but I don't know them.
>

Since 'break' is just a short pulse on the serial port, it can be caused
by a glitch when you remove/insert the cable as well as by the keyboard.

Found this link at sunhelp:
http://www.sunhelp.org/pipermail/sun...ne/011193.html

(set abort_enable=0 in /etc/system and use alternate break sequence.)

This used to work; though there are some odd cases where break is still
enabled, i.e. during reboot, since OBP still reacts to it.

/Rolf

Rolf Blom <allspam@round.bin> writes:
>
>Found this link at sunhelp:
>http://www.sunhelp.org/pipermail/sun...ne/011193.html
>
>(set abort_enable=0 in /etc/system and use alternate break sequence.)
>

No. Do NOT do this. It hasn't been necessary since 2001 or 2002.

Use the 'disable' or 'alternate' keywords as described in the man page
for the kbd command.

>
>This used to work; though there are some odd cases where break is still
>enabled, i.e. during reboot, since OBP still reacts to it.
>

The config file you describe (/etc/system) is read by the kernel.
How could its effects be felt when the kernel is not in control
of the computer? (i.e. at the OBP prompt and during early boot steps)

The same is true of the settings described by 'man kbd'.

-Greg
--
Do NOT reply via e-mail.
Reply in the newsgroup.