Re: Ultra 10 - no output to monitor

In article <slrnflhhd9.f6g.dnichols@xxxxxxxxxxxxxxxxxx>,
DoN. Nichols <dnichols@xxxxxxxxxxx> wrote:
On 2007-12-07, Flatulous Maximus <none@xxxxxxxxxxx> wrote:

Okay DoN, your advice to pull any PCI cards did the trick. I pulled
the SymBios 22801 SCSI card.

Great! Always reduce the system to the minimum for diagnostics,
and add one thing at a time to see what makes it stop working.

Also, I set the screen resolution to
1152x900x66 in the OBP. It starts up normally now with the Sun 17"
monitor and keyboard attached. I booted the Solaris 8 CD and got all
the way to the # prompt. The only thing it complained about was
having no Ethernet connection and no hard drive. So, this CPU I
bought on eBay appears to be perfectly fine. The SCSI card was
apparently the source of the Data Access Error on start up.

Or -- perhaps the seating of the card was not quite right. You
might try re-installing it just to be sure.

So, my next question is, how do I get the SCSI card to work in this
Ultra 10 without conflict so I can make use of the Seagate 18.2 GB
SCSI drive and install the OS?

Well ... that *is* one of the cards supplied by Sun. They call
it either the 375-0005 (without F-code) or 375-0013 (with F-code). Look
for the sun barcode label on it to see which you have. In any case, it
should work and not halt the system if it is properly seated. Of
course, a bad card could halt the system even with it properly seated.


Don, I'm about to SCSI-fy an Ultra 5 so have been checking what's what
in the FEH. The options lists for the U5_10 lists the 375-0005 card,
and the *** for that card lists 375-0005 as "without F-code." and
gives the Symbios (now LSI) 22801 reference. The listing for the
375-0013 with F-code notes "not released."

No indication whether the Sun-barcoded LSI22801 differs from the
generic Pee Cee version. The LSIlogic data page lists the card as
"for Intel systems" and doesn't mention Sparcs. I do have a 375-0006
dual differential card, and it's clearly marked Symbios and 22802.

On U5_10, flashing the eeprom up to 3.31 if it's lower than that fixes
an awful lot of stuff. Probably worth doing on all machines. I just
flashed a 375-0066 board from 3.15 to 3.31 using a 333 CPU so that I
could get a 440 CPU to work.

Note that you also want to check that the riser card which
provides the PCI slots is properly seated in the system board.

Yes, this is critical. To the OP, I'd suggest you plug the SCSI HBA
back in, making sure the connector seats completely. You may have to
take the riser board mounting screws out and/or bend *** metal to
get full seating.

Do a probe-scsi-all with the board-only installed (no disk). You
should get a report. If that works OK, plug in the disk and disk
power, and repeat the probe-scsi-all. If you get the ident string
from the disk displayed, then you can try an install. Do a
boot cdrom -s and when you get a console prompt, run format. If you
get a lot of messages about the disk not being properly labelled, use
the format label command to label it. Once you finish assuring the
disk is labelled, you can control-D from the command prompt to get the
install to continue.

I would prefer to use the SCSI drive
over an IDE drive and I have an external Sun SCSI tape drive I would
like to use with it also. I will Google the SCSI issue, but any
suggestions would be appreciated.

I *think* that the Ultra-5/10 won't boot from that card in an
unless you have the F-code version of the card. But I'm not sure. I've
nknever tried to boot an Ultra-10 or and Ultra 5 from a SCSI card. When
I'm using one of those, I'm after the inexpensive disk drives. You'll
probably have to boot from an internal IDE drive, and then access the
SCSI drive once the system is booted.

As I said, the FEH gives the 375-0005 non F-code version as an option
for U5_10 and notes the 375-0013 number as not released.

Later systems, such as the Ultra-60 have the drivers in the OBP,
but not the Ultra-5/10.

It's been years since I put a SCSI boot disk in a U10, but there were
several aftermarket (not Sun) boards that would work with the OBP.
Once again, I'll suggest getting it flashed up to 3.31.


Hank
.

Quantcast