Hello,

I have two linux boxes A and B. Each of them have serial ports (ttyS0 on both) and these ports are connected using null modem serial cable. "A" box is always on and it has getty process on its ttyS0 (I need this getty for serial communication). If I reboot box B, it doesn't boot default entry - just displays grub os select table. After some investigation I realized that getty process on A sends some data to grub on B while it's booting and grub behaves the same way as if some key is pressed during timeout period - it doesn't boot default and waits for interactive user response. I need to reboot B remotely so its no good for me. (disabling getty on A solves the problem, but I need that getty).

Is it possible to disable any grub serial communications to solve my problem ?

thanks
Vilius

69 "reads" of this thread, and no answers, so here are my suggestions:

I don't know which version of grub you are using, "legacy" or grub2 AKA "1.97" (Confusing, or what?)

Anyway, try setting grub on box B not to display a menu, or wait for input.

Otherwise, disable ttyS0 on A until box B has booted, then re-enable it. (Or simply disconnect the cable while box B is booting?)

I think grub just listens to Standard Input ( stdin ). AFAIK you cannot alter this.

Any splashimage comments? If so remove them and try again.

Hi,

I'm running 0.97 legacy grub.
How do I do that exactly ?

thanks
Vilius

First, make sure you have a "rescue CD" or some other means of booting, in case you mess up, and grub refuses to boot at all.

As root, edit the file /boot/grub/menu.lst
Uncomment the line ## hiddenmenu so it reads just hiddenmenu

Under the time out bit, set the timeout to zero
Save the file, reboot.

Hello,

Well it was not grubs fault. In the end I found out that it was B computer bios configured to output to serial port(remote access), after disabling that everything went ok.

V