On 2008/10/13 09:57, Vivek Ayer wrote: > I didn't understand this part. > > "you want to send a BREAK over the serial line. from cu, you do > this by typing ~# at the start of a line (i.e. press enter first). > If you're connecting over SSH, you need to escape the first tilde > since it's also used by SSH: ~~#" > > I issue the "cu" command, it says Connected and after that I can't > really type anything. I get no cursor after I see "Connected" Is that > normal? Do I send BREAK only if I see POST messages from the Blade? Or > should I go ahead and type "~#" even if I see no cursor. Also, this > won't be over ssh.
Just try it, you won't break anything. But if there's absolutely no output, you probably need to check your cable first. > > Please Clarify. > > Thanks a bunch > > On Mon, Oct 13, 2008 at 12:56 AM, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > On 2008-10-13, Vivek Ayer <[EMAIL PROTECTED]> wrote: > >> does length affect the pinout? I mean I even tried just hooking up the > >> null modem cable placing the two PC's backs to each other. It should > >> work in that case, right? I'm not at the computer now, but I'll try > >> the Ctrl+break. So the procedure would go: > >> > >> 1. hookup short null modem cable to each end ((only) one 9-pin female > >> on P3 and one 25-pin male on Blade Serial Port A (not B or others?)), > >> 2. the blade will be off, > >> 3. then on the P3 issue the command as root: cu -l /dev/tty00 (assume > >> this over cua00?) -s 9600, > > > > shouldn't make a difference here, but cua is intended for > > connecting out. > > > >> 4. it should say connected on the P3, > >> 5. then power on the Sun w/o keyboard and monitor, > >> 6. wait for 30-60 seconds > >> 7. should see POST messages in terminal > >> 8. Hit Ctrl+Break? > > > > you want to send a BREAK over the serial line. from cu, you do > > this by typing ~# at the start of a line (i.e. press enter first). > > If you're connecting over SSH, you need to escape the first tilde > > since it's also used by SSH: ~~# > > > >> 9. and I'm set with the OK> prompt? > >> > >> When exactly do I hit Ctrl+Break? Also, before I issue "cu", when I > >> login to the P3 running OBSD, what do I set as the terminal type: > >> VT100 or Sun? Correct my procedure if it's wrong. > > > > doesn't matter. > > > > if you don't see the startup messages, verify the cable really is > > wired correctly, and/or plug in your rs232 tester (what do you mean > > you don't have one ;-) and check the lines. > > > >>>> But the cable is short, so I got a regular extension cable to > >>>> hook up to it. > >>> > >>> It might be advisable to get a longer null modem cable, as you know.. > >>> the different between a null modem and strait through cable is the > >>> pinout. > > > > there's no problem to plug a normal modem cable into a null modem > > cable to make it longer..
