Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Trouble Setting Up Sun Ultra 10 - Displaying Garbage Post 302558689 by frhan2u on Sunday 25th of September 2011 02:16:34 AM
Old 09-25-2011
Trouble Setting Up Sun Ultra 10 - Displaying Garbage

Hello there,

I am new to this forum as well as to the UNIX world. Recently graduated with a degree in Computing and just started learning UNIX & bought 3 Sun Ultra 10 Servers. I was trying to set the Servers up so I can use them; the Servers don't have a VGA card. My laptop, which I would be using as a console, does not have a VGA/Serial out so I bought a USB to Serial cable to connect it (with the laptop and) with the Server's DB25 port (which has an adapter to convert it to RJ45). I tried the connection with a straight cable, roll over cable (RJ45 both ends) and another roll over cable (RJ45 at one end and female serial at the other); Since I have Windows 7 on my laptop hence there is no Hyper Terminal, so instead downloaded Putty Extra to communicate with the Server.

But, whenever I connect the Server(s), they either don't display anything or display garbage on screen. As I have 3 Servers, I tried it with all of them with the same result, changed the Adapters on the back of the Servers, changed my USB to Serial cable, plugged in cable into different ports of the server and etc, with same result!

Any help would be highly appreciated because I am really stuck here Smilie

Also, attaching a picture of the back of the server, as well as the cables I am using, in case I am using them with the wrong port on the server/wrong cable (though.. have tried all different combinations!).

In the Image:

1 = the port of the server I am connecting with (DB25 with an adapter to convert it to RJ45)
2 = USB to Serial cable I am using to connect my laptop to (number 5 and then to) the Server
3 = Extra Console/Roll Over cable I bought, with a female serial on one end and a RJ 45 connector on the other
4 = an extra adapter I got with the Servers (the pin settings on this are slightly different to the one(s) already in the Server (number 1)
5 = connect this adapter to my (number 2) USB to Serial cable and then have used both straight & roll over cables to connect to number 1, but the result is either empty screen or garbage on the screen.

Thanks for reading this!
Trouble Setting Up Sun Ultra 10 - Displaying Garbage-2011-09-25-065016-jpegjpg
 

9 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Sun Ultra 2 Solaris 8

Sparc Ultra2: Notes prtdiag: System Configuration: Sun Microsystems sun4u Sun Ultra 2 UPA/SBus (2 X UltraSPARC-II 296MHz) System clock frequency: 99 MHz Memory size: 768 Megabytes ========================= CPUs ========================= Run Ecache CPU CPU... (0 Replies)
Discussion started by: tnorth
0 Replies

2. Solaris

sun ultra or sun sparkstation

am wonder wich sun computer is better, a sun ultra or sun sparkstation, and what is the difference (7 Replies)
Discussion started by: nobody
7 Replies

3. Solaris

sun ultra

Hi Guys, I have a 2nd hand Sun ultra-5, I wanted to know how to be able to run it as a normal window. I do not have any experience whatsoever with solaris/unix. Does anyone can give me a clue where to start. When I switch it goes to: unix console login: pa$$word: #UNIX sendmail : enable to... (0 Replies)
Discussion started by: lingosa
0 Replies

4. UNIX for Dummies Questions & Answers

Trouble getting serial output from Ultra 10

Hi, Iam trying to get make a serial connection to an Ultra 10 from my laptop. I've set the output to goto ttya in the nvram parameters. Iam using a db9 converter at the laptop end and a db25 converter at the ultra 10 end-I know the adapters are fine and so is the cable. Iam just not able to get it... (3 Replies)
Discussion started by: pulse77
3 Replies

5. Solaris

sun ultra 10 monitor

hi all, it seem hard to see on a regular monitor the ultra 10 converter to rgb so that it can go to a pc monitor. do u know how can i fix the monitor properly? it's not easy to see on the monitor there's so many lines. thanks in advance. (2 Replies)
Discussion started by: itik
2 Replies

6. Solaris

LOM on SUN ultra 10

Hi experts is it possible to install lom on sun ultra 10 box? can you guys help me in undertanding lom as i tried goggling , couldn't get good stuff. Please :) (6 Replies)
Discussion started by: kumarmani
6 Replies

7. Shell Programming and Scripting

setting and displaying variables

Hello, I need a little help. 1. Edit /etc/profile so that all users are greeted upon login. 2. For the root account, set the prompt to something like "Danger!! root is doing stuff in \w", preferably in a bright color such as red or pink or in reverse video mode. Thanks for help. (4 Replies)
Discussion started by: zhshqzyc
4 Replies

8. Red Hat

dhcp not setting dns and changing to garbage

I have 2 problems. Dhcp is not setting dns and after I manually set my dns it changes to garbage. I literally just used command to set dns which is a good copy of resolv.conf: sudo cp /home/bob/Desktop/scripts_9-12-2011/resolv.conf /etc/resolv.confHere is a copy of my resolv.conf. #... (5 Replies)
Discussion started by: cokedude
5 Replies

9. UNIX for Dummies Questions & Answers

Trouble displaying parameters passed into a for loop

#!/bin/bash function check_num_args() { if ; then echo "Please provide a file name" else treat_as_file $* fi } function treat_as_file() { numFiles=$# for((i=1;i<=$numFiles;i++));do echo $i ... (3 Replies)
Discussion started by: kikilahooch
3 Replies
modem(7)						 Miscellaneous Information Manual						  modem(7)

NAME
modem - Describes guidelines for using modems DESCRIPTION
The Tru64 UNIX system enables you to use a variety of modems for point-to-point connections to systems that are not in close proximity to each other. These connections can be Serial Line Internet Protocol (SLIP), Point-to-Point Protocol (PPP), and UNIX-to-UNIX Copy Program (UUCP) connections. In addition, these connections can be basic dial-out/dial-in connections (for example, to log in to a remote system to perform remote system administration). This section presents general guidelines for using modems on Tru64 UNIX systems for all types of connections. See Network Administration for specific information on SLIP, PPP, and UUCP connections. Using the Correct Modem Cables In order to connect a modem to the serial port of your system, you must use the correct cable. If you do not, you might experience signal loss, resulting in the software not functioning properly. The following table lists the cables you should use. The cable connector is either 25-pin or 9-pin, depending on the type of serial port on your system. See the hardware documentation for your system if you are unsure about the type of serial port. Note OPEN DECconnect cables do not provide a sufficient number of wires for full modem control. You should not use them for connecting modems to the system. ------------------------------------------------------------------------------ Cable Number Description ------------------------------------------------------------------------------ BC22E-xx 16-wire modem cable (Male DB25 pin to female DB25 pin cable) BC22F-xx 25-wire modem cable (Male DB25 pin to female DB25 pin cable) BC29P-xx Male DB25 pin to female DB9 pin cable PC modem cable Male DB25 pin to female DB9 pin cable In the previous table, xx denotes the cable length. For example, BC22E-10 is a ten-foot cable. Configuring a System for Dial-In Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Edit the /etc/remote file and create an entry similar to the kdebug entry. For example, if your modem is connected to tty00 and you are going to use a baud rate of 38400 to access the modem, create an entry similar to the following: b38400:dv=/dev/tty00:br#38400:pa=none Note Some modems set their baud rate to the serial port rate. Be sure to access the modem using the same baud rate that you are going to specify to getty or uugetty. Otherwise, you might not be able to log in because of a mismatch in baud rates. See ports(7) if you are unsure which port your modem is connected to. Use the tip command to access the modem as follows: tip b38400 The tip utility responds with a connected message. You can now communicate with the modem. If your modem is using the AT command language, enter the following command: at<Return> If the modem is not in quiet mode, it responds with an OK message. Set the modem up for dial-in access. The following table lists the AT commands required. Most of these command settings are the default settings. -------------------------------------------------------------------------- Command Description -------------------------------------------------------------------------- at&c1 Normal Carrier Detect (CD) operation. Tells the modem to not raise Carrier Detect until it see Carrier Detect from the other modem. at&d2 Normal Data Terminal Ready (DTR) operation. This is important in that it tells the modem to hang up the line when DTR drops. For example, when the user logs off the system. atq1 Sets the modem into quiet mode. Result codes are not sent to the system. ate0 Echo off. This prevents the modem from echoing back the login prompt issued by the getty process. ats0=n Specifies the number of rings to wait before answering. If n = 0 (zero), the modem will not answer. at&w0 Saves the current modem settings in NVRAM. The operating system supports both hardware and software flow control. If the system supports hardware flow control, set the modem and the serial line up to use hardware flow control by using the appropriate commands. If hardware flow control is not supported, you should use software flow control. Edit the /etc/inittab file and create an entry for the modem. If you want to use the modem line in non-shared mode, create an entry similar to the following: modem:23:respawn:/usr/sbin/getty /dev/tty00 M38400 vt100 If you want to use the modem line in shared mode (for dial-out and dial-in connections), use uugetty instead of getty and create an entry similar to the following: modem:23:respawn:/usr/lib/uucp/uugetty -r -t 60 tty00 38400 With uugetty, you will be able to use the tip and cu utilities, but might not be able to use third-party utilities because of dif- ferences in file locking. Note If you want to use the uugetty utility, you must install the UNIX-to-UNIX Copy Facility subset. As root, start the getty or uugetty process by entering the following command: init q The getty or uugetty process starts, then goes to sleep, waiting for someone to dial into the system. Configuring Your System for Dial-Out Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Verify that there is an entry for the modem name specified with the modemtype subcommand in the /etc/acucap file. If your modem does not have an entry in the /etc/acucap file, do the following: Copy an entry similar to that of your modem. The following entry is for a US Robotics modem for use in shared mode with tip: us|US|US Robotics (28.8 fax/data modem): :cr:hu:ls:re:ss=AT ATE1Q0&C0X0&A0 :sr=OK: :sd#250000:di=ATD:dt= : :dd#50000:fd#50:os=CONNECT:ds=d+++dATZ dATS0=2 : :ab=d+++dATZ dATS0=2: Be sure the entry includes at least the AT commands in the following table. The other modem settings can remain as they are. ------------------------------------- Command Description ------------------------------------- ate1 Turns on echoing. atq0 Displays the result codes. Modify the modem attributes to match your modem's attributes and include the debug option (db). With debugging turned on, the modem will provide you with additional information with which to tune the modem attributes in the file. See acucap(4) for more informa- tion. Create an entry in the /etc/remote for the system you want to call. Among the information you can supply is the Tru64 UNIX device, baud rate, and /etc/acucap that defines your modem. The following two entries are for the modem specified in step 1a. tip38400:tc=us38400 us38400|38400 Baud dial out via US Robotics modem: :el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D: :dv=/dev/tty00:br#38400:ps=none:at=us:du: In the previous example, the first line is an entry that points to the us38400 entry specifying shared capabilities for modems. The second line is the first line of the us38400 entry. The third line defines end-of-line characters, and input and output end-of-file marks. The fourth line defines the UNIX device to open for the connection, the baud rate, the parity, the name of the /etc/acucap file entry, and the dial-up line. See remote(4) for more information. If you use getty to provide access to the system from a modem and a getty process is already running, do the following: Edit the /etc/inittab file and put a comment character (#) at the beginning of the modem entry. Issue the init q command to terminate the getty process. Use the tip command, specifying the -baud_rate flag and the telephone number to dial out as follows: tip -38400 8881234 In this example, tip strips off the minus sign (-) from the baud rate and concatenates the tip command name and the baud rate to create the string tip38400. Then, tip searches the /etc/remote file for the entry matching the string. The entry in the /etc/remotes file, points the capability information in the us38400 entry to initialize the modem. By specifying the telephone number on the command line, you can share the same modem attributes for outgoing connections that have different telephone numbers. When you log off the remote system and exit tip, the modems saved settings are restored, readying the modem for the next user. If used in shared mode, the modem is available for dial-in access. RELATED INFORMATION
Commands: cu(1), tip(1), getty(8), uugetty(8). Files: acucap(4), inittab(4), remote(4). Devices: ports(7). Network Administration delim off modem(7)
All times are GMT -4. The time now is 06:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy