In article <[EMAIL PROTECTED]> you write:
>On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote:
>
> > > Hmm, last time I checked, they were just 'serial ports'.
> >
> > Nope. The significance is determined by the software, and you're stuck
> > with the fact that the first serial port is
>
>
> On Sun, 26 Dec 1999, Daniel C. Sobral wrote:
>
> > Leif Neland wrote:
> > >
> > > > Just configure it correctly. Don't tell it to talk to a serial device
> > > > that will be sending it gibberish.
> > >
> > > A hack would be to have the loader emit ATE0 to protect itself from
> > > echo
On Sun, 26 Dec 1999, Daniel C. Sobral wrote:
> Leif Neland wrote:
> >
> > > Just configure it correctly. Don't tell it to talk to a serial device
> > > that will be sending it gibberish.
> >
> > A hack would be to have the loader emit ATE0 to protect itself from
> > echoing modems.
>
> AFAIK
>
> Leif Neland wrote:
> >
> > > Just configure it correctly. Don't tell it to talk to a serial device
> > > that will be sending it gibberish.
> >
> > A hack would be to have the loader emit ATE0 to protect itself from
> > echoing modems.
>
> AFAIK, it would not protect against all modems. I
Leif Neland wrote:
>
> > Just configure it correctly. Don't tell it to talk to a serial device
> > that will be sending it gibberish.
>
> A hack would be to have the loader emit ATE0 to protect itself from
> echoing modems.
AFAIK, it would not protect against all modems. I think Winmodems, for
On Wed, 22 Dec 1999, Daniel C. Sobral wrote:
> Justin Hawkins wrote:
> >
> > I think (I am not positive on this) that if the boot loader talks to a
> > modem in command mode with echo on, it gets confused and won't boot any
> > further. Is this a known problem?
>
> I'd say this is an expected
Justin Hawkins wrote:
>
> Where is the 'boot' option documented - I couldn't find it in
> loader.conf(5). What does it do - does it disable all input, or does it
> create a failsafe where is does something sensible in case garbage is
> received over the serial line/keyboard.
loader(8). Also, aut
On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote:
> > Hmm, last time I checked, they were just 'serial ports'.
>
> Nope. The significance is determined by the software, and you're stuck
> with the fact that the first serial port is the console port. End of
> story. (Note: if
> > "Swapping them internally" would probably involve about 30 seconds of
> > work. It's not hard, really. 8)
>
> Yes I know I could have done that. Then reconfigured my getty's, my
> minicom etc. It's the principle of the thing - I prefer to bend the
> software to my will rather than have to o
On Tue, 21 Dec 1999, Mike Smith wrote:
> "Swapping them internally" would probably involve about 30 seconds of
> work. It's not hard, really. 8)
Yes I know I could have done that. Then reconfigured my getty's, my
minicom etc. It's the principle of the thing - I prefer to bend the
software to
> I've recently had .. ahem .. fun trying to get my headless FreeBSD box to
> spit messages at the console. I've got the kernel doing it right, but not
> the boot loaders. The boot loader will print to the serial device - but it
> won't load my kernel :-( I haven't exhausted all oppurtunities here
On Wed, 22 Dec 1999, Daniel C. Sobral wrote:
> Justin Hawkins wrote:
> >
> > I understand it's not really a bug and perhaps is not worth the code
> > effort. A note in the handbook might not go astray - I am sure a lot of
> > people who need a COM2 console will have modem on COM1.
>
> A note o
Justin Hawkins wrote:
>
> I understand it's not really a bug and perhaps is not worth the code
> effort. A note in the handbook might not go astray - I am sure a lot of
> people who need a COM2 console will have modem on COM1.
A note on the handbook and/or man pages can certainly be done. I'd be
On Wed, 22 Dec 1999, Daniel C. Sobral wrote:
> I'd say this is an expected result, not a known problem. It is doing
> exactly what it is being told to (gibberish). Junk in, junk out. :-)
Sure.
> > Is there enough room in there for some code, which checks for this? IE if
> > the first line outp
Justin Hawkins wrote:
>
> I think (I am not positive on this) that if the boot loader talks to a
> modem in command mode with echo on, it gets confused and won't boot any
> further. Is this a known problem?
I'd say this is an expected result, not a known problem. It is doing
exactly what it is b
Hi there,
I've recently had .. ahem .. fun trying to get my headless FreeBSD box to
spit messages at the console. I've got the kernel doing it right, but not
the boot loaders. The boot loader will print to the serial device - but it
won't load my kernel :-( I haven't exhausted all oppurtunities h
16 matches
Mail list logo
