Subject: Re: multia firmware problem
To: Wim Vandeputte <firstname.lastname@example.org>
From: Scott Lipcon <email@example.com>
Date: 05/17/1999 14:38:08
I don't have the proper serial cables handy, so I'll have to wait - I
tried unplugging the keyboard, and the screen stayed black entirely -
no SRM line at the bottom. I'll get another keyboard tomorrow or
tonight to try - the one I have is an AT keyboard, with a PS2->AT
converter. Hopefully I haven't damaged anything... I'll try a true ps2
keyboard and hope :)
As for the other suggestion - I pulled the battery today and checked it
with a voltmeter - its putting out a bit more than 4v. On a 4.5v
battery, I'd say that means its probably still good. It looked like it
was not the original part.
> On Sun, 16 May 1999, R. C. Dowdeswell wrote:
> > Well, I think that you should try a serial console (unplug the
> > keyboard for this). If that works, try replacing the keyboard.
> > I've noticed that the SRM console is really picky about the keyboards
> > that it recognises.
> Oh yes it can be very picky about the devices hooked up ps/2 ports, I've
> seen a lot of Multia's which do not detect anymore the hooked up ps/2
> keyboard, even if it works fine.
> One of the causes I found was somebody using a serial -> ps/2 converter
> for his mouse, thus 'breaking' (blowing?) something inside the machine.
> Now, even with the mouse and converter removed and with a fresh keyboard
> and mouse, the system will just assume there is nothing hooked up thus
> booting with 'serial console' only, leaving a blank screen.
> Is there a way Hardware/Software to avoid this?
> Putting in a fresh SRM does not solve the problem. Maybe a patched SRM?