Unsolved
This post is more than 5 years old
11 Posts
0
2415
December 1st, 2016 11:00
"Redirect console after boot"
So we use this option to access the SAC for Windows servers. It is also nice because you can see PXE attempts. I don't know what kind of magic this option uses, but I can not get GRUB to respond over console when this option is on. We would like to have our entire fleet use this option, but right now I see no way to make GRUB or a getty work with this. Anyone have any luck being able to communicate with a host with this option enabled? To be exact I can see console messages, but can't send any keystrokes.
No Events found!
DELL-Josh Cr
Moderator
•
9.6K Posts
•
42.2K Points
0
December 1st, 2016 16:00
Hi,
Have you edited the grub config to support console connections? What distro and version are you using?
luketidd
11 Posts
0
December 2nd, 2016 07:00
Just a moment, this isn't bog standard. "Redirect Console After Boot" does some funny things. A standard GRUB config that works with "redirect console after boot" will not work with it enabled. Please try to replicate and you will see.
A standard serial out configuration for GRUB is visible over serial console with "redirect console after boot" enabled, but it can not be communicated with. It does not respond to key presses over serial.
This is a typical relevant configuration from /etc/default/grub:
GRUB_TERMINAL=console
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8"
In trying to guess what this option is doing, I assumed it might work over text mode, so forcing GRUB and the kernel to abandon any KMS or graphics modes still appears over console, but similarly no key presses are reaching GRUB:
GRUB_TERMINAL=console
GRUB_GFXPAYLOAD_LINUX=text
Has anyone actually successfully communicated with GRUB with this BIOS option enabled on a poweredge?
luketidd
11 Posts
0
December 8th, 2016 12:00
I guess this is impossible. It's a shame no one understands what "Redirect Console After Boot". It must be really nonstandard.