>> root@fury:/etc/init# update-grub
>> Invalid output terminal "serial console"
... this is an error... it's supported in documentation and works in ubuntu 11
*** Notice GRUB_TERMINAL was changed to GRUB_TERMINAL_INPUT
- ENABLED, com1, vt100, 115200, redirect after console *****DISABLED*****
-- yes / motherboard serial access
-- yes / serial grub console access
-- serial console shift key *does not* work to display menu
-- serial console tapping ESC multiple times quickly will allow menu to be displayed
-- no / no physical console displayable menu... BUT if you hit ESC it will appear on physical console
---- this is different than Ubuntu 8 and 11 which allows you to simultaneously control the grub menu from serial or console
In other words... it "kind-of" works. You can get serial administration working fairly well at the cost of slight physical grub console access being limited (but ultimately working).
Assuming you are running a remote server environment... one could argue this is acceptable as the majority of the administration is done remotely anyways... so as long as the remote serial administration is solid... this is a plausible solution.
Ubuntu 10.04 Re-Test ------- ------- ------- -
-------
- ENABLED, com1, vt100, 115200, redirect after console *****DISABLED*****
Grub (NON WORKING CONFIG) ------- ------ TIMEOUT= 5 TIMEOUT_ QUIET=true R=`lsb_ release -i -s 2> /dev/null || echo Debian` LINUX_DEFAULT= "quiet" LINUX=" console= tty1 console= ttyS0,115200n8" "serial console" #### THIS FAILS ### COMMAND= "serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
-------
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
GRUB_TERMINAL=
GRUB_SERIAL_
>> root@fury: /etc/init# update-grub
>> Invalid output terminal "serial console"
... this is an error... it's supported in documentation and works in ubuntu 11
Partially Working Ubuntu 10.04 Config ------- ------- ------- ------- ------- ------- --- TIMEOUT= 7 TIMEOUT_ QUIET=false R=`lsb_ release -i -s 2> /dev/null || echo Debian` LINUX_DEFAULT= "quiet" LINUX=" console= tty1 console= ttyS0,115200n8" INPUT=" serial console" COMMAND= "serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"
-------
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
GRUB_TERMINAL_
GRUB_SERIAL_
*** Notice GRUB_TERMINAL was changed to GRUB_TERMINAL_INPUT
- ENABLED, com1, vt100, 115200, redirect after console *****DISABLED*****
-- yes / motherboard serial access
-- yes / serial grub console access
-- serial console shift key *does not* work to display menu
-- serial console tapping ESC multiple times quickly will allow menu to be displayed
-- no / no physical console displayable menu... BUT if you hit ESC it will appear on physical console
---- this is different than Ubuntu 8 and 11 which allows you to simultaneously control the grub menu from serial or console
In other words... it "kind-of" works. You can get serial administration working fairly well at the cost of slight physical grub console access being limited (but ultimately working).
Assuming you are running a remote server environment... one could argue this is acceptable as the majority of the administration is done remotely anyways... so as long as the remote serial administration is solid... this is a plausible solution.