> 
> When booting from the serial port, the console device is configured as the
> dz serial line 3, and console I/O is done directly to the serial port.
> When booting from the keyboard, the console device is configured as the dz
> serial line 0 (which is the keyboard), but nothing else is done, so now
> console I/O is done directly to the keyboard serial port.  All console
> output is written to the keyboard, no doubt confusing it greatly.  Console
> input would be reading the raw keycodes from the keyboard, which is rather
> useless.  And the final straw will be when /dev/console is opened because
> it will set the baud rate to 9600.  Apparently the ROM monitor never
> resets the keyboard port, and the only way to clear it is to cycle power.
> 
> A quick and dirty work-around I did so I didn't have to cycle power all
> time was to modify the dz driver to skip setting the parameters for line
> 0.  This stopped all the beeping of the keyboard and disabling the
> keyboard and let me concentrate on the rest of the console problems.
> 
Hm, this means that the graphic device don't manage to steal the 
console early during boot? That could explain all troubles people 
have had.

-- Ragge