[SUMMARY] E3000 only boots when a a SUN keyboard is hooked up

From: matthew.d.romero@ac.com
Date: Thu Jul 22 1999 - 16:39:42 CDT


Thanks to everyone who sent in suggestions. It turned out to be a matter of
reseting all the OBP settings back to the factory settings. For those who don't
know this is done by getting to the ok prompt and typing set-defaults. This
will reset all your OBP settings.

Thanks again.

--Matt

matthew.d.romero@ac.com
07/22/99 05:22 PM GMT

To: sun-managers@sunmanagers.ececs.uc.edu
cc: (bcc: Matthew D. Romero)
Subject: E3000 only boots when a a SUN keyboard is hooked up

Guru's,

I have a bit of a perplexing problem, and I want toknow if anyone has seen this.

I have an E3000 running 2.5, that's hooked up to a WYSE terminal and keyboard.
When I try and boot the machine it gets through POST, and goes into booting up
the OS. It runs for about 10 - 20 seconds, and it just hangs. The lights are
in a normal On Off Flashing state. I had changed something in the kernel and I
thought that was the problem. So I tried to boot off of the CDROM. When I got
to the ok prompt, I ran a boot cdrom. It would go for a couple of seconds, and
seem to halt at exactly the same place as the normal boot up. This blew me
away, because if it was the kernel mods., they have nothing to do with booting
from the cdrom. Next I tried avoiding the /etc/system entirely. At the ok
prompt I gave the boot command "boot -as", and when it asked about /etc/system I
gave it /dev/null. I was able to boot up into single user mode and remove the
changes I made in /etc/system. Then I tried booting from this point and I hit
the same snag, it hung in the booting of the OS. Just for grins, I tried
hooking up a SUN keyboard to the box and it came right up. Ran through POST and
booted up like a champ. Only problem is I can't keep theSUN keyboard hooked up
to it. I need to figure out why I can't boot up the box while it's hooked up to
the WYSE Terminal only. I even did a setenv for the input and output devices
setting them both to ttya which is where the WYSE Terminal is hooked up.

 These are the only errors I am seeing in /var/adm/messages;

WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):
Mar 5 14:31:47 harpo unix: Connected command timeout for Target 3.0
Mar 5 14:31:48 harpo unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000 (fas0):
Mar 5 14:31:48 harpo unix: Target 3 reducing sync. transfer rate
Mar 5 14:31:48 harpo unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@0,0 (sd0):
Mar 5 14:31:48 harpo unix: SCSI transport failed: reason 'reset': retrying
command
Mar 5 14:31:48 harpo unix:
Mar 5 14:31:48 harpo unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@1,0 (sd1):
Mar 5 14:31:48 harpo unix: SCSI transport failed: reason 'reset': retrying
command
Mar 5 14:31:48 harpo unix:
Mar 5 14:31:48 harpo unix: WARNING: /sbus@3,0/SUNW,fas@3,8800000/sd@3,0 (sd3):
Mar 5 14:31:48 harpo unix: SCSI transport failed: reason 'timeout': retrying
command
Mar 5 14:31:48 harpo unix:
Mar 5 14:31:55 harpo unix: <CD-ROM Disc for SunOS Solaris_2.5.1 Installation
>
Mar 5 14:35:13 harpo unix: sysctrl(0): ignoring debug enter sequence
Mar 5 14:35:17 harpo last message repeated 6 times

It looks like the I/O board is having problems, but I don't have anything hooked
up to it, only the Ethernet connection.

Any Ideas would be much appreciated
TIA, will summarize.

--Matt



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:23 CDT