[Resolved] Re: VNC + Boot w/o keyboard, video & mouse

[NoOp]

Matthew Kuiken wrote:
> NoOp wrote:
>> Brian Fahrlander wrote:
> <snip>
>>>     Yeah, here ya go. This is for the ServerFlags section:
>>>
>>> Option "AllowMouseOpenFail" True
>>>
>>>     Try that, first; it's probably all it is- I'm assuming there's
>>> actually some kind of video card in there (which might stop it) but the
>>> lack of a mouse no longer will, with that added.
>>>
>>>     If it does, let me know- we'll keep looking. In that case, send me a
>>> .log of the attempt.  You can mail me direct if you like- I expect to be
>>> up for another 8-10 hours or so.
>>>
>> 
>> Found a problem on one test machine - you were right and that one halts
>> at no keyboard present, so I'll need to reset it's bios. I'll be
>> bringing the actual server home to test tomorrow & will let you know
>> what I figure out. Thanks for all the assistance - gotta run Valentines
>> day/nigh & all :-)
> 
> I've been playing with Debian on the PS3 lately, and one of the pages 
> about it recommended that mousedev be added to /etc/modules  in order to 
> ensure that the module is loaded even if the mouse is not connected.  I 
> don't know if this will do anything different than the option above, but 
> it seems like a good idea to have the module loaded to ensure VNC can 
> use it properly.
> 
> -Matt
> 
> 



I feel dumb as a brick right now.

Turns out that the machine that I was doing the testing on had it's BIOS
set to halt on keyboard error. Brian was right all along regarding the
bios (thanks Brian!). As soon as I reset the bios to *not* halt on
keyboard error the machine pop right in, booted up, and I was able to
establish the VNC to it... it hadn't been updated in awhile and is now
downloading 45 updates :-)

Thanks again folks & apologies for stirring the pot with my "operator
headspace" error.