02-21-2010
TTY Issue with Sunblade 150
I purchased a Sunblade 150 from Ebay. It had 512MB RAM and 80GB hard disk. I recently purchased additional RAM and another 80GB disk, and installed them. The RAM goes through POST without issues. I just can't get beyond the OK prompt. I am using the serial console.
I have been unable to make the on-board graphics work, and do not have a SUN mouse and keyboard. I am content with the serial console. Using the serial console, I can see the machine going through all its various tests...prior to shutting it down, I went to OBP and set the diagnostics flag to true. Everything appears copasetic
Except that I cannot send any data to the serial console. I dug out my RS-232 tester, and it does appear to have a problem. The CD (Carrier Detect), DSR (Data Set Ready), RTS (Ready to Send), DTR (Data Terminal Ready), CTS (Clear to Send), and RD (Receive Detect) lights are lit as normal, however, the TD (Transmit Detect) is not lit.
To check the cable, I connected it to my RS6000/B50 server. All 7 lights come on as expected and everything works. The problem therefore is not my cable, nor is it the XP system that I am using PuTTY to make the connection with. This cable did work prior to the installation of RAM and hard disk. I was able to install Solaris 10 via the serial console without event.
I had to purchase new IDE cables for the upgrade--the ones that came with it were far too short.
This makes no sense to me at all. Should I remove the RAM? I did try it with the 2nd Hard Disk disconnected, but the problem returned.
Why is the Sunblade not asserting TD? Everything else seems just fine.
I read elsewhere that I cannot use a standard mouse and keyboard with this thing. Further, the on-board video is deader than Elvis--at least there is a rumor that Elvis lives. Could these issues be related?
10 More Discussions You Might Find Interesting
1. Solaris
hii alll
i have a problem with my sunblade100. when i switch on, no display comes but if i ping from a remote machine its pinging,but iam not able to telent to that sun server,what can be the problem,how can i sort ot this issue
2 thing in usb iam not able to use STOP N (to clear the... (3 Replies)
Discussion started by: solaris8in
3 Replies
2. Debian
I have tried to install the Debian distribution for SPARC processor, but is a pian in the neck trying to boot from cdrom or floppy.
Please can somebody to help me to know the easiest way to boot and install Debian on a SUNBLADE 100 system? or wich is the best way to installed on this system, I... (2 Replies)
Discussion started by: GEIER
2 Replies
3. Solaris
Hi all,
I am a newbies here,
Have question regards large hard disk install in SunBlade system.
Can SunBlade 150 support 2 x 160GB (internal IDE) ?
Want to make sure before buy the hard disks.
Anyone had experiences configure large hard disk in SunBlade 150 before ?
In the SunBlade 150... (2 Replies)
Discussion started by: ong.kianseng
2 Replies
4. Solaris
Hi guys,
I have a SunBlade 2000 that I am trying to configure. It has been configured previously with an IP address, hostname, DNS and so forth. I want to configure it with a new IP address. How can I achieve this? It has been one of the most difficult tasks for me as I am not really... (6 Replies)
Discussion started by: Arkayev
6 Replies
5. UNIX for Dummies Questions & Answers
Hi everyone this is my first post
I have used linux a couple of times and was impressed, so i bought an old sunblade 1000, just to learn something new.
I cannot get the thing to work! I have tried to install solaris 10 and several types of linux. I am beginning to wonder if i was sold a... (3 Replies)
Discussion started by: Kawakaze
3 Replies
6. Solaris
Greetings,
I was in the mood of upgrading my sunblade100 in my bedroom, since I recuperated some RAM from intel servers, and found myself with what seems to not work (I was hoping to pass from 256Mb to 2GB... and then upgrading to solaris 10...)
after this failure I tried with just one 512 MB,... (2 Replies)
Discussion started by: vbe
2 Replies
7. Solaris
Good Morning,
I took a mirror drive from one Solaris 9 machine and used it to set up another. After syncing another mirror on the second machine I restarted but I don't get a login screen.
I see a message:The X-server cannot be started on display :0
Also during startup I see:... (8 Replies)
Discussion started by: Stellaman1977
8 Replies
8. UNIX for Beginners Questions & Answers
Good Afternoon,
I'm setting up a SunBlade 2500 using ufsrestoreand have gotten to the point where I have restored the root and usr partitions. However, the machine keeps rebooting, never really coming up. Looking at vfstab, it looks pretty empty- shouldn't I see entries like... (22 Replies)
Discussion started by: Stellaman1977
22 Replies
9. Shell Programming and Scripting
In bash, you can do something like this:
#!/bin/bash
echo -n "What is your name? " > /dev/tty
read thename < /dev/tty
How can I do the same in python?
I have a python script that has the following content:
#!/usr/bin/python2.7
import getpass
import sys
import telnetlib
import... (2 Replies)
Discussion started by: SkySmart
2 Replies
10. UNIX for Beginners Questions & Answers
Hi.
I have a Microsystems SunBlade 150
shell# cat /etc/release
Solaris 8 2/02 s28s_u7wos_08a SPARC
shell# uname -a
SunOS HOSTNAME 5.8 Generic_108528-14 sun4u sparc SUNW,Sun-Blade-100
shell# prtconf -F
/pci@1f,0/SUNW,m64B@13:m640
When I join to the only account the server try to... (5 Replies)
Discussion started by: siegroup
5 Replies
LEARN ABOUT X11R4
systemd-cryptsetup-generator
SYSTEMD-CRYPTSETUP-GENERATOR(8) systemd-cryptsetup-generator SYSTEMD-CRYPTSETUP-GENERATOR(8)
NAME
systemd-cryptsetup-generator - Unit generator for /etc/crypttab
SYNOPSIS
/lib/systemd/system-generators/systemd-cryptsetup-generator
DESCRIPTION
systemd-cryptsetup-generator is a generator that translates /etc/crypttab into native systemd units early at boot and when configuration of
the system manager is reloaded. This will create systemd-cryptsetup@.service(8) units as necessary.
systemd-cryptsetup-generator implements systemd.generator(7).
KERNEL COMMAND LINE
systemd-cryptsetup-generator understands the following kernel command line parameters:
luks=, rd.luks=
Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.luks= is honored only by initial RAM disk
(initrd) while luks= is honored by both the main system and the initrd.
luks.crypttab=, rd.luks.crypttab=
Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any devices configured in /etc/crypttab
(luks.uuid= will still work however). rd.luks.crypttab= is honored only by initial RAM disk (initrd) while luks.crypttab= is honored
by both the main system and the initrd.
luks.uuid=, rd.luks.uuid=
Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in
/etc/crypttab. This option may be specified more than once in order to set up multiple devices. rd.luks.uuid= is honored only by
initial RAM disk (initrd) while luks.uuid= is honored by both the main system and the initrd.
If /etc/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the
device will have the name "luks-UUID".
If /etc/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.
luks.name=, rd.luks.name=
Takes a LUKS super block UUID followed by an "=" and a name. This implies rd.luks.uuid= or luks.uuid= and will additionally make the
LUKS device given by the UUID appear under the provided name.
rd.luks.name= is honored only by initial RAM disk (initrd) while luks.name= is honored by both the main system and the initrd.
luks.options=, rd.luks.options=
Takes a LUKS super block UUID followed by an "=" and a string of options separated by commas as argument. This will override the
options for the given UUID.
If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in
/etc/crypttab.
rd.luks.options= is honored only by initial RAM disk (initrd) while luks.options= is honored by both the main system and the initrd.
luks.key=, rd.luks.key=
Takes a password file name as argument or a LUKS super block UUID followed by a "=" and a password file name.
For those entries specified with rd.luks.uuid= or luks.uuid=, the password file will be set to the one specified by rd.luks.key= or
luks.key= of the corresponding UUID, or the password file that was specified without a UUID.
rd.luks.key= is honored only by initial RAM disk (initrd) while luks.key= is honored by both the main system and the initrd.
SEE ALSO
systemd(1), crypttab(5), systemd-cryptsetup@.service(8), cryptsetup(8), systemd-fstab-generator(8)
systemd 237 SYSTEMD-CRYPTSETUP-GENERATOR(8)