We believe that your issue has been closed by the upload of
Version 1.1.33 of grml-etc from Michael Prokop <mika@grml.org>.
The explanation is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 27 Feb 2010 02:28:29 +0100
Source: grml-etc
Binary: grml-etc
Architecture: source all
Version: 1.1.33
Distribution: unstable
Urgency: low
Maintainer: Michael Prokop <mika@grml.org>
Changed-By: Michael Prokop <mika@grml.org>
Description: 
 grml-etc   - ecetera files for the grml system
Changes: 
 grml-etc (1.1.33) unstable; urgency=low
 .
   * /etc/inittab*: Use normal getty instead of mgetty and several
     baud rate settings to let getty figure out which mode should be
     used. Use '#grmlserial#' to mark the beginng of the lines that
     should be activated through grml-autoconfig when booting with
     serial/console bootoption (providing more flexibility for the
     user). Thanks to Zoran Dzelajlija for the detailled bugreport
     and suggestions. [Closes: issue485]
Checksums-Sha1: 
 22a1001a6b2d1868ffbaed43ddae15d93b76acc9 830 grml-etc_1.1.33.dsc
 289709b6296dcd0bb95d7d5dacd80aa19ab4d844 158481 grml-etc_1.1.33.tar.gz
 5472af225c58330e96520b4d7241bc5dfd377648 160164 grml-etc_1.1.33_all.deb
Checksums-Sha256: 
 52e297faa4b3e9fb135bf841bfb48465abca4d74f3a876a9c61c0a19a5e03320 830 grml-etc_1.1.33.dsc
 8c8c079fabbf127071725b7e513624f7d7d200d15070d710470cebc7f924d25d 158481 grml-etc_1.1.33.tar.gz
 f6428bbca7ca01698aa15fb420d9018fa3331b3ed06b2132e2da6da37b53e718 160164 grml-etc_1.1.33_all.deb
Files: 
 f71609d346dab33425e1d7b1e7dc5851 830 grml optional grml-etc_1.1.33.dsc
 92c408b279f1bd5b2be56276f2f17562 158481 grml optional grml-etc_1.1.33.tar.gz
 fb8e51697aec934d1f519cca66ef8ebe 160164 grml optional grml-etc_1.1.33_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLiHba2N9T+zficugRAjPHAJ4yRUNQzKFehc+WYGWuDku25tNJDgCfYhso
ZuIp3z1evLHz5yicXqqAYAQ=
=fDIg
-----END PGP SIGNATURE-----

Thanks for your detailled bugreport/feature request - nice ideas!
We'll take care of it and see what we can do. :)

regards,
-mika-

obvious typo in kernel cmdline; it's supposed to read
"grml console=tty1 console=ttyS1,115200n8"
Also attaching a screenshot of what the serial looks
after the system's booted.

Booting grml64-medium_0.1.iso on an HP Proliant DL380G5 machine
with virtual serial port (acting as a terminal connected to COM2 @ 115200),
using this command line: "grml console=tty 1console=ttyS1,115200n8", makes
kernel and boot log be displayed on ttyS1, up to the point where
mgetty is started on ttyS1, when it stops working.

A few points:
1) mgetty doesn't work on this machine. normal getty does.
   To make the serial console work, I had to comment out the
   mgetty line for ttyS1, uncomment the default debian's inittab
   line (which also works fine on machines with physical serial
   ports) and fix the speed:

T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100

   then init q, kill off mgetty and bash on ttyS1.  getty appeared.
   FWIW, I haven't needed anything other than default getty to make
   serial console (via null-modem cable or HP's virtual serial port),
   work since sarge or woody (and I haven't messed with serial ports
   before that).

2) It would be nice if any and all devices in console=...
   parameters were automatically added to /etc/securetty (/dev/ttyS1
   is NOT present by default), so that root may log in from there.

   Doing http://bts.grml.org/grml/issue474 (grml-quickconfig
   to appear on serial if the user booted w/ serial console) could be
   an alternative or a nice addition to that.  Since the kernel gives
   the last console=... as userspace (init) stdint/stdout/stderr, and
   init dumps all its output there, it would be least surprising to
   make grml-quickconfig appear on that very same tty.  That's probably
   what the user is looking at.

If these are implemented, the user won't have to do anything on the
tty1 VGA console to boot up to a usable grml enviroment on serial.