[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to tftp to Indy



> Can it be a hardware problem, e.g. bad RAM?

OK, I think we're having the car/noise/mechanic situation again :)

I just pulled the top 32MB of RAM out of it and it booted the kernel OK.
Swapped the RAM out with another 32MB I had laying around in another
production box, and both work fine.  I'm guessing the Indy may be a bit
less tolerant of the timing on the RAM than the other machine (BeBox).

> Or is it on of those
> infamous V1.7 R4600? The first lines of dmesg output would tell that
> (if they print).

It looks like the problem's solved, but out of curiosity: what was the
issue with 1.7-rev 4600s?

> Do both of your Indy's behave the same way?

Yep.  Guess neither one liked that memory.  I feel really dumb right
now.

- Cameron.



Reply to: