Serial Port command to Cisco 678
Tom Condon
tomc
Tue Dec 7 21:19:30 PST 2004
On Monday 06 December 2004 13:42, David Bandel carved in granite:
> Well, I can't help you with minicom, but kermit, yes:
>
> If you have ckermit installed, just call up kermit:
> at the kermit prompt, you'll need to issue the following commands:
> set line /dev/ttyS0
> set carrier-watch off
> connect
>
> a couple of Enters should allow kermit to autobaud and connect.
Hmm. As usual, I know too little to know what is wrong. Only that I
get nothing in response to <CR>s.
> Now this is all assuming:
>
> you haven't disabled your serial ports in BIOS
> you have loaded the serial module (in 2.6.x the module has been
> renamed to generic_serial)
>
> you may also have to run the setserial command to activate the
> serial ports correctly.
Running setserial I get:
gungadin:~ # setserial /dev/ttyS1
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
gungadin:~ # setserial /dev/ttyS0
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
gungadin:~ # setserial /dev/ttyS2
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
So, from this I would decuce that I have two serial ports, 0 & 1. I
would guess that they are set up to work or setserial wouldn't give
me information on them. However, perhaps that is my problem. If
more info is required on the serial ports, how would I devine it?
Thanks for the clues so far, and any further suggestions you might
have.
In Harmony's Way and In A Chord,
Tom ;-})
Tom Condon
Proud Member of the Kitsap Chordsmen
Registered Linux User #154358
You Can't Catch A Virus From Plain Text Email
More information about the Linux-users
mailing list