| To: | "Chen, Yukun" <yukun.chen@xxxxxxxxx> |
|---|---|
| Subject: | RE: Failed to enter KDB on terminal program via key sequence "Ctrl-A" |
| From: | Jim Houston <jim.houston@xxxxxxxxxxx> |
| Date: | 02 Nov 2004 21:37:19 -0500 |
| Cc: | Keith Owens <kaos@xxxxxxx>, kdb@xxxxxxxxxxx |
| In-reply-to: | <16A54BF5D6E14E4D916CE26C9AD3057574636B@pdsmsx402.ccr.corp.intel.com> |
| Organization: | |
| References: | <16A54BF5D6E14E4D916CE26C9AD3057574636B@pdsmsx402.ccr.corp.intel.com> |
| Reply-to: | jim.houston@xxxxxxxxxxx |
| Sender: | kdb-bounce@xxxxxxxxxxx |
On Tue, 2004-11-02 at 21:14, Chen, Yukun wrote: > Keith > I use SLES9 SP1. I have tried the method u mentioned > but it still dose not work. I think it might be a bug of suse > distribution and I will report them it. > > Thanx a lot for your help:) > > Aaron Hi Aaron, Unless something has changed, the serial port has to be open for it to have the interrupt enabled and this is necessary to notice the Ctrl-A or other magic kdb string. I don't think kdb does anything to force the serial port to be opened. Enabling a login on the serial port might make the difference. Jim Houston - Concurrent Computer Corp. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Failed to enter KDB on terminal program via key sequence "Ctrl-A", Chen, Yukun |
|---|---|
| Next by Date: | Re: Failed to enter KDB on terminal program via key sequence "Ctrl-A", Keith Owens |
| Previous by Thread: | RE: Failed to enter KDB on terminal program via key sequence "Ctrl-A", Chen, Yukun |
| Next by Thread: | Re: Failed to enter KDB on terminal program via key sequence "Ctrl-A", Keith Owens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |