Am Samstag, 26. M=E4rz 2005 02:13 schrieb David Brownlee:
>  	That is very strange. Could you look at the messages boot32
>  	gives (load an invalid kernel - README works quite well :)
>  	and see if they are any different between one of C/D and
>  	one of A/B?

I am very sorry for the delay. But the report is the same for both, the onl=
y=20
difference is in the physical memory blocks, but they differ from time to=20
time anyway (even if I take a fresh booted machine).

1x SIMM A (the one that fails)
=2D-----------------------------
Allocated 5802 memory pages, each of 4 kilobytes.

Getting memory configuration

=46ound ROM  (0) at 0x00000000 for  4096 k
=46ound I/O  (0) at 0x03000000 for  8192 k
=46ound I/O  (1) at 0x08000000 for 31072 k
=46ound DRAM (0) at 0x10000000 for 16384 k
=46ound DRAM (1) at 0x14000000 for 16384 k
=46ound VRAM (0) at 0x02000000 for  2048 k

Getting actual memorymapping; sorting .

=46ound physical memory blocks :
[0x1064d000-0x10ffffff] [0x14000000-0x1462afff] [0x146f1000-0x14d28fff]=20
[0x14d38000-0x14d5efff] [0x14de4000-0x14e21fff] [0x14e2d000-0x14e2dfff]=20
[0x14e38000-0x14e3afff] [0x14eaa000-0x14ed4fff]


1x SIMM C (the one that works)
=2D-----------------------------
Allocated 5802 memory pages, each of 4 kilobytes.

Getting memory configuration

=46ound ROM  (0) at 0x00000000 for  4096 k
=46ound I/O  (0) at 0x03000000 for  8192 k
=46ound I/O  (1) at 0x08000000 for 31072 k
=46ound DRAM (0) at 0x10000000 for 16384 k
=46ound DRAM (1) at 0x14000000 for 16384 k
=46ound VRAM (0) at 0x02000000 for  2048 k

Getting actual memorymapping; sorting .

=46ound physical memory blocks :
[0x1064d000-0x10ffffff] [0x14000000-0x1462afff] [0x146f1000-0x14d27fff]=20
[0x14d38000-0x14d5efff] [0x14dc7000-0x14dc7fff] [0x14de4000-0x14e20fff]
[0x14e2d000-0x14e2dfff] [0x14e38000-0x14e3afff] [0x14ea9000-0x14ecffff]
[0x14ed1000-0x14ed4fff] [0x14f59000-0x14f59fff]