Mailing List Archive

console redirect issue
Hello all,

I have a dell 1750. If I don't do console redirect from the bios all works ok. If I
enable console redirect to the serial port, all comes up, but once up I can't use the
console as a terminal. I must restart conserver deamon process then I'm ok.. Is there an
option or something I'm missing?

thanks,
Keith
Re: console redirect issue [ In reply to ]
On Wed, 7 Jul 2004, Keith Patton wrote:

> Hello all,
>
> I have a dell 1750. If I don't do console redirect from the bios all works ok. If I
> enable console redirect to the serial port, all comes up, but once up I can't use the
> console as a terminal. I must restart conserver deamon process then I'm ok.. Is there an
> option or something I'm missing?
>

What OS is the host running?
If linux, what boot loader?
If Grub, disable the "redirection after post" option in BIOS as grub
tries to grab the serial port which it can't do cause the BIOS has
it.
Else, make sure that your serial line in /etc/grub.conf does not have
--console in it, else if you tap the keyboard during the bootloader
or boot stages that's where the console will end up (on the
keyboard/VGA device, instead of the serial console where you want
it).

HTH,

-n
--
-------------------------------------------
nathan hruby <nhruby@uga.edu>
uga enterprise information technology services
production systems support
metaphysically wrinkle-free
-------------------------------------------
Re: console redirect issue [ In reply to ]
thanks for the reply,

Sorry for leaving this out, both systems are linux/ console, and remote box ( dell
)..and using grub..


We have "redirection after boot" disabled, no place for "redirection after post"

Currently we have, all the redirection disabled in the bios, and let grub do the
redirection. All works fine..just no bios redirect..

If we turn on "redirection to serial 1", after boot still disabled, all comes up find
but it screws up conserver daemon process. After the remote is alive, we can restart the
daemon and then it works...Therefore, by restarting the daemon on the console we work
again, indicates to us that the bios settings may be correct because you can then login.

-Keith




nathan r. hruby wrote:
> On Wed, 7 Jul 2004, Keith Patton wrote:
>
>
>>Hello all,
>>
>> I have a dell 1750. If I don't do console redirect from the bios all works ok. If I
>>enable console redirect to the serial port, all comes up, but once up I can't use the
>>console as a terminal. I must restart conserver deamon process then I'm ok.. Is there an
>>option or something I'm missing?
>>
>
>
> What OS is the host running?
> If linux, what boot loader?
> If Grub, disable the "redirection after post" option in BIOS as grub
> tries to grab the serial port which it can't do cause the BIOS has
> it.
> Else, make sure that your serial line in /etc/grub.conf does not have
> --console in it, else if you tap the keyboard during the bootloader
> or boot stages that's where the console will end up (on the
> keyboard/VGA device, instead of the serial console where you want
> it).
>
> HTH,
>
> -n
Re: console redirect issue [ In reply to ]
On Wed, Jul 07, 2004 at 10:02:06AM -0500, Keith Patton wrote:
> If we turn on "redirection to serial 1", after boot still disabled,
> all comes up find but it screws up conserver daemon process. After the
> remote is alive, we can restart the daemon and then it
> works...Therefore, by restarting the daemon on the console we work
> again, indicates to us that the bios settings may be correct because
> you can then login.

does the daemon become unresponsive, or just that console? if you can
still connect to the console, does it come back to life after you do a
'^Ecd' and then '^Eco' (which just downs the console and brings it back
up). if so, then something weird is going on within the state of that
one console, which helps debug where the problem is.

i assume that will be the case. but, whatever the case, we'll need to
turn on the debugging flags, log all this data, and wade through it to
see what's going on and why it's getting confused. add "-DDD" to the
conserver command line and make sure you're redirecting the output to a
file. it'll make a *HUGE* pile out output.

oh...another thought. how are you connecting the serial port to the
conserver host? is it a local serial port or via a terminal server? it
could be a software flow control issue too...if one side is set to
accept software flow control, you could get a ctrl-s in one of the
directions and hang up the entire thing. if you have software flow
control enabled anywhere, try turning it off to see if that helps (and
if resetting the console with ^Ecd/^Eco works as well, that could
explain it...the drop of the connection resetting the line and the flow
control). anyway, something else to think about before wading through
huge amounts of debug output.

Bryan