:
:Joseph Garcia wrote:
: It connects and I can log in and enter commands. The problem pops up
: when receiving a lot of data quickly from the device (i.e. when I'm
: writing the configuration to the terminal).
:
:Maybe I'm completely missing the point here, but your
:description sounds like
Joseph Garcia wrote:
It connects and I can log in and enter commands. The problem pops up
when receiving a lot of data quickly from the device (i.e. when I'm
writing the configuration to the terminal).
Maybe I'm completely missing the point here, but your
description sounds like it could
:It's just a serial console cable to a cisco device. It's a PIX in this
:case. I'm using the cisco supplied blue roll over cable. Pretty much
:normal. It seems to work fine when using my notebook.
:
:So it can either be a) the hardware on the DragonFly box, or b)
:something in DragonFlyBSD.
Robert Clark wrote:
Make sure the Serial port is enabled in BIOS?
I've seen integrated-chipset-provided serial ports be disabled in BIOS
and still be probed and in used by the OS. The ghost ports would then
work depending on how the OS serviced them.
I've also seen multiple ports
COM1 - 3F8 IRQ4
COM2 - 2F8 IRQ3
COM3 - 3E8 IRQ4
COM4 - 2E8 IRQ3
[RC]
On Oct 19, 2006, at 1:02 PM, Joseph Garcia wrote:
Robert Clark wrote:
Make sure the Serial port is enabled in BIOS?
I've seen integrated-chipset-provided serial ports be disabled in
BIOS and still be probed and in used
:Okay, so I was working via the console port (i.e. DFly box connected to
: Firewall via serial port) of my PIX firewall and I kept getting these
:errors. These errors made it quite impossible to configure the firewall
:because I was unable to recieve the output from the PIX device.
:
:Error
Joseph Garcia wrote:
If I change that line in that file, do I only need to recompile the kernel?
Yes, even make quickkernel will do if nothing else has changed (and
there was no cleanup) since your last kernel compilation.
Matthew Dillon wrote:
:Okay, so I was working via the console port (i.e. DFly box connected to
: Firewall via serial port) of my PIX firewall and I kept getting these
:errors. These errors made it quite impossible to configure the firewall
:because I was unable to recieve the output from the
Matthew Dillon wrote:
Try changing FIFO_RX_MEDH to FIFO_RX_LOW around line 2281
of /usr/src/sys/dev/serial/sio/sio.c.
Also post your 'dmesg' output.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
I changed that line and I rebuilt the
:I changed that line and I rebuilt the kernel, installed the kernel, and
:rebooted. I tried it again, but I still have the same problems. Any
:other ideas?
:
:Joey
What is actually being run over this serial port? Just a console
session, or something else? What baud rate are you
Matthew Dillon wrote:
:I changed that line and I rebuilt the kernel, installed the kernel, and
:rebooted. I tried it again, but I still have the same problems. Any
:other ideas?
:
:Joey
What is actually being run over this serial port? Just a console
session, or something else? What
Make sure the Serial port is enabled in BIOS?
I've seen integrated-chipset-provided serial ports be disabled in
BIOS and still be probed and in used by the OS. The ghost ports would
then work depending on how the OS serviced them.
I've also seen multiple ports configured on the same
Okay, so I was working via the console port (i.e. DFly box connected to
Firewall via serial port) of my PIX firewall and I kept getting these
errors. These errors made it quite impossible to configure the firewall
because I was unable to recieve the output from the PIX device.
Error
13 matches
Mail list logo
