OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Donald White (dbwhite_at_asu.edu)
Date: Fri Feb 21 2003 - 20:48:09 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    I don't have a UP2000, but I had a 164sx that behaved very much like what you
    describe. I looked at SCSI problems for a day or so, changing terminators, cables,
    disks, controllers. You name it, I changed it. I finally replaced the SDRAM DIMMS
    and everything worked again. I was completely looking in the wrong place because
    the SCSI subsystem was indicating the error.

    Robert M. Riches Jr. wrote:
    > My UP2000 is behaving strangely. After I replaced a noisy CPU
    > fan, SRM wouldn't come up. The fan is spinning and giving the
    > system enough of a tach signal for the PWRGOOD LED to come on
    > and for SRM to try to come up.
    >
    > The problem seems to be centered around the single-ended SCSI
    > chain. Normally, I have two hard disks on the LVD chain along
    > with a Plextor wide CD drive and Yamaha CD burner on the
    > single-ended chain. At Michal's insistence :-) many months ago
    > I turned off all drive termination and put an Ultra-160 LVD/SE
    > standalone terminator on the end of each chain.
    >
    > Whether I get the SRM prompt on power-up depends now on what
    > I have plugged into the single-ended SCSI connector:
    >
    > - nothing plugged in to the motherboard: memory test is
    > slower than normal, but the system can boot and run Linux.
    > (Otherwise, I couldn't type in this plea for help.)
    >
    > - cable plugged in to MB, with or without terminator:
    > memory test hangs (or takes more than 2X as long as it
    > normally does).
    >
    > - Plextor and terminator on chain: memory test hangs but
    > if I interrupt it "sh dev" sees the Plextor.
    >
    > - Yamaha and terminator on chain: don't get the "Testing
    > the System" message, which normally comes right after
    > the message about initializing GCT/FRU...
    >
    > Doing the deductions, it appears the Yamaha is preventing the
    > "Testing the System" message. However, that doesn't explain
    > why the memory test hangs or takes much longer than usual. I'm
    > running SRM 5.8.81 if that matters.
    >
    > If the whole problem is the Yamaha burner, why does memory test
    > take so much longer than usual depending on whether stuff is
    > connected to the SCSI chain? Why should a possibly bad CD
    > burner prevent the "Testing the System" message? Shouldn't
    > that just cause the burner (and maybe other things on that
    > chain) to fail to show up for "sh dev"?
    >
    > Any suggestions?
    >
    > Thanks.
    >
    > Robert Riches
    > rm.richesverizon.net
    >
    >
    >
    > _______________________________________________
    > Axp-list mailing list
    > Axp-listredhat.com
    > https://listman.redhat.com/mailman/listinfo/axp-list

    _______________________________________________
    Axp-list mailing list
    Axp-listredhat.com
    https://listman.redhat.com/mailman/listinfo/axp-list