Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
On Mon, 13 Oct 2008, Vivek Ayer wrote: I'm getting zilch. I'm starting to suspect that I got ripped off on this cable. I could be just as wrong. I just need to test this cable with a windows machine via hyperterminal to absolutely make sure it's not working. Serial cables can be a PAIN - there's no way to verify the connections without a breakout box that shows the signals. If you don't have one, google the pinouts and check for -V on pins 2 and 3 where they meet one of the machines. Lee
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Alright guysthe serial cable was indeed bad. I finally got the ok prompt. Only one problem. I can't type anything at the ok prompt. I can terminate cu and get back in, but when I'm in, I can't type anything. If I let it come up to a SunOS login, I can type stuff. This is really weird. I used terminal type vt100 or sun on the computer accessing the Sun. Help appreciated Vivek On Tue, Oct 14, 2008 at 7:39 AM, L. V. Lammert [EMAIL PROTECTED] wrote: On Mon, 13 Oct 2008, Vivek Ayer wrote: I'm getting zilch. I'm starting to suspect that I got ripped off on this cable. I could be just as wrong. I just need to test this cable with a windows machine via hyperterminal to absolutely make sure it's not working. Serial cables can be a PAIN - there's no way to verify the connections without a breakout box that shows the signals. If you don't have one, google the pinouts and check for -V on pins 2 and 3 where they meet one of the machines. Lee
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Vivek Ayer wrote: ... I type cu -l /dev/tty00 -s 9600 and it says Connected. So I turn on the Blade and nothing comes up on the console. I know that Sun workstations work really well with serial port. I plugged the cable into serial port A... I'm not sure about the Blades but the T1000's have two serial ports, only one is for the console. Check your hardware guide. regards -Lars
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
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..
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
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. 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..
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
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..
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
On Sun, Oct 12, 2008 at 11:42 PM, Vivek Ayer [EMAIL PROTECTED] wrote: So assuming the cable is the right cable, in short, what would I have to do to install OpenBSD on a sparc64 from a i386 console? If your devaliases are set up correctly type: boot cdrom with an install cd in. -- Best Regards Edd http://students.dec.bournemouth.ac.uk/ebarrett
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
I'm getting zilch. I'm starting to suspect that I got ripped off on this cable. I could be just as wrong. I just need to test this cable with a windows machine via hyperterminal to absolutely make sure it's not working. On Mon, Oct 13, 2008 at 10:04 AM, Stuart Henderson [EMAIL PROTECTED] wrote: 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..
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
On 17:41:49 Oct 13, Vivek Ayer wrote: I'm getting zilch. I'm starting to suspect that I got ripped off on this cable. I could be just as wrong. I just need to test this cable with a windows machine via hyperterminal to absolutely make sure it's not working. You can create a null modem cable yourself. Or you could buy one off a good hardware store. ;) You can test very well with two PCs connected back to back using one of the serial port communication programs like cu(1), minicom(1) or tip(1). -Girish
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
I'm probably going to return this cable. Actually I could just ask the IT guys at our uni about the serial cable, since these two beauties were lying in their salvage bin. On Mon, Oct 13, 2008 at 7:31 PM, Girish Venkatachalam [EMAIL PROTECTED] wrote: On 17:41:49 Oct 13, Vivek Ayer wrote: I'm getting zilch. I'm starting to suspect that I got ripped off on this cable. I could be just as wrong. I just need to test this cable with a windows machine via hyperterminal to absolutely make sure it's not working. You can create a null modem cable yourself. Or you could buy one off a good hardware store. ;) You can test very well with two PCs connected back to back using one of the serial port communication programs like cu(1), minicom(1) or tip(1). -Girish
Best Way to get OpenBSD installed on Sun Blade 1000/2000
Hi guys, So, I'm having some trouble getting OpenBSD installed on two UltraSPARCs that are perfectly functional it seems. I tried the monitor + keyboard, but found that to be a hassle as Sun requires you use their keyboard and monitor which I don't have. Anyways, so I believe I have a Null Modem Serial Cable (Someone wrote Null on the cable). But the cable is short, so I got a regular extension cable to hook up to it. Previously, I hooked up a regular monitor and I'd get the Sun startup sequence at times only to read no keyboard found, using /dev/ttya for in and out So I figured serial is to way to go about installing stuff. I have a P3 766 web server running OpenBSD with a monitor and keyboard attached to it. It has one serial port (which I assume is /dev/tty00, not /dev/cua00) and I hook this cable up to 1 of 4 serial ports (2 are builtin, 2 are in an external PCI daughterboard). I hook it up before I power on the Blade and then at the OpenBSD console, I type cu -l /dev/tty00 -s 9600 and it says Connected. So I turn on the Blade and nothing comes up on the console. I know that Sun workstations work really well with serial port. I plugged the cable into serial port A. So assuming the cable is the right cable, in short, what would I have to do to install OpenBSD on a sparc64 from a i386 console? Thanks a bunch, Vivek
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Vivek Ayer wrote: So assuming the cable is the right cable, in short, what would I have to do to install OpenBSD on a sparc64 from a i386 console? I've used the miniroot method on Sun Netra's with good results. See this URL: http://openbsd.org/sparc.html -- View this message in context: http://www.nabble.com/Best-Way-to-get-OpenBSD-installed-on-Sun-Blade-1000-2000-tp19946248p19946644.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Well...i have the install43.iso cd. I don't think choosing the media is my problem. What's the quickest way to see a OpenPROM ok prompt on a foreign machine? What commands do I use (e.g., cu, tip, etc.)? If I can get an ok prompt, I'm golden. As of now, I just a white screen come saying keyboard not detecting, using /dev/ttya for input and output. Then the screen goes blank because I assume Solaris goes to a really high resolution that my monitor can't handle. If the keyboard (and monitor?) isn't plugged in, it goes straight to serial. But I know serial output comes after even after I boot up the machine. It's just that all I see is Connected in my openbsd terminal. I even looked at this website for help: http://slashboot.org/articles/8/Building_a_Sparc64_server_with_OpenBSD_3.8.html Thanks, Vivek On Sun, Oct 12, 2008 at 3:38 PM, new_guy [EMAIL PROTECTED] wrote: Vivek Ayer wrote: So assuming the cable is the right cable, in short, what would I have to do to install OpenBSD on a sparc64 from a i386 console? I've used the miniroot method on Sun Netra's with good results. See this URL: http://openbsd.org/sparc.html -- View this message in context: http://www.nabble.com/Best-Way-to-get-OpenBSD-installed-on-Sun-Blade-1000-2000-tp19946248p19946644.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Vivek Ayer wrote: Well...i have the install43.iso cd. I don't think choosing the media is my problem. What's the quickest way to see a OpenPROM ok prompt on a foreign machine? What commands do I use (e.g., cu, tip, etc.)? If I can get an ok prompt, I'm golden. I normally connect via a Windows hyper terminal to my Sun boxes... To get an ok prompt from a Windows hyper terminal press: 'Ctrl'+'Break' That's equivalent to 'Stop-A' on a Solaris keyboard. -- View this message in context: http://www.nabble.com/Best-Way-to-get-OpenBSD-installed-on-Sun-Blade-1000-2000-tp19946248p19947124.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Do you get to see anything before you press Ctrl+Break. All I see from OpenBSD is a Connected even after I've powered on the Sun. Do you get to see POST messages, etc? Thanks, Vivek On Sun, Oct 12, 2008 at 4:47 PM, new_guy [EMAIL PROTECTED] wrote: Vivek Ayer wrote: Well...i have the install43.iso cd. I don't think choosing the media is my problem. What's the quickest way to see a OpenPROM ok prompt on a foreign machine? What commands do I use (e.g., cu, tip, etc.)? If I can get an ok prompt, I'm golden. I normally connect via a Windows hyper terminal to my Sun boxes... To get an ok prompt from a Windows hyper terminal press: 'Ctrl'+'Break' That's equivalent to 'Stop-A' on a Solaris keyboard. -- View this message in context: http://www.nabble.com/Best-Way-to-get-OpenBSD-installed-on-Sun-Blade-1000-2000-tp19946248p19947124.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Vivek Ayer wrote: Do you get to see anything before you press Ctrl+Break. Yep... looks like this: Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard OpenBoot 3.10.27 ME, 1024 MB memory installed, Serial #14272968. Ethernet address 8:0:20:d9:c9:c8, Host ID: 80d9c9c8. Boot device: disk File and args: OpenBSD IEEE 1275 Bootblock 1.1 .. OpenBSD BOOT 1.2 Trying bsd... -- View this message in context: http://www.nabble.com/Best-Way-to-get-OpenBSD-installed-on-Sun-Blade-1000-2000-tp19946248p19947474.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
Vivek Ayer wrote: 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. Good luck. -Brynet
Re: Best Way to get OpenBSD installed on Sun Blade 1000/2000
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, 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? 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. Thanks guys, Vivek On Sun, Oct 12, 2008 at 6:18 PM, Brynet [EMAIL PROTECTED] wrote: Vivek Ayer wrote: 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. Good luck. -Brynet
