| 1 |
Hello, Mick. |
| 2 |
|
| 3 |
On Mon, Apr 10, 2017 at 22:46:14 +0100, Mick wrote: |
| 4 |
> On Monday 10 Apr 2017 21:24:21 Alan Mackenzie wrote: |
| 5 |
|
| 6 |
> > Another idea I've had is that I've got duff RAM. The various bootable |
| 7 |
> > images that crash don't always crash in _exactly_ the same places. And |
| 8 |
> > the BIOS mouse and keyboard freezing up don't inspire confidence. I do |
| 9 |
> > hope it's not the RAM; I'd probably have to remove the processor cooler |
| 10 |
> > just to be able to get at the RAM sticks. :-( |
| 11 |
> > |
| 12 |
> > > HTH. |
| 13 |
|
| 14 |
> A quick test would be to remove one RAM module at a time and try to boot like |
| 15 |
> that. If you succeed you have the culprit module in your hand. If not, rinse |
| 16 |
> and repeat. |
| 17 |
|
| 18 |
I did this. The machine didn't hang when it only had one RAM stick in - |
| 19 |
either RAM stick, it didn't matter. The slot on the MB it was in didn't |
| 20 |
make a difference, either. |
| 21 |
|
| 22 |
What solved this problem was updating the BIOS. As I said in my reply |
| 23 |
to Alan G., the MB I bought was really duff. I've almost got Gentoo |
| 24 |
installed on it, now. |
| 25 |
|
| 26 |
> -- |
| 27 |
> Regards, |
| 28 |
> Mick |
| 29 |
|
| 30 |
-- |
| 31 |
Alan Mackenzie (Nuremberg, Germany). |
Archives