khym@azeotrope.org wrote:
> Oh, that's almost certainly unrelated then. This problem has nothing to
> do with whether a monitor is attached. I remember you mentioning this
> problem now... someone else mentioned that NetBSD may have a problem
> with the screen size that's reported when you don't have a monitor hooked
> up--and that seems like a likely explanation to me. Serial console seems
> like your best bet for figuring this one out. For example, if NetBSD
> thinks your screen resolution is 0x0 when you don't have a monitor,
> it's likely that the code that tries to write to the screen will crash.

I am sorry if I was unclear - I was not trying to imply the problem was 
with video.  My troubleshooting had been very rudimentary thus far.  All 
I had time to do was pull it out of my rack (detaching from network) so 
that I could connect a monitor.  My assumption was that I had an 
intermittent booting problem.  However, it always "worked fine" with a 
monitor, but I could not telnet/ssh in when it went back on the shelf. 
This is consistent with the mc0 problem mentioned.  I never tested 
network connectivity when I had a monitor attached.

Tim
-- 
Tim & Alethea
christtrek.org