Re: Installation fails after "done, booting the kernel."

[Thomas Herrmann <THerrmann@ADwin.de>]

Martin,

On May 31, 1:50 pm, Martin Michlmayr <t...@cyrius.com> wrote:
> Try adding earlyprintk to the kernel parameter and you might get more
> debugging output.

excellent hint. This is where it gets stuck:

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-31)
(ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Tue Mar
8 10:56:14 UTC 2011
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE),
cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate FreeAgent DockStar
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200n8 base-
installer/initramfs-tools/driver-policy=most earlyprintk
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6,
262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072
bytes)
[    0.000000] Memory: 256MB 256MB = 512MB total
[    0.000000] Memory: 512000KB available (3516K code, 583K data, 124K
init, 0K highmem)

AFAIK the dockstar has only 128MB of RAM, so if the kernel wants to
use 512MB it will crash. I am just wondering how the linux kernel
determines the amount of RAM; I did set arcNumber=2998 and
mainlineLinux=yes properly. How does the kernel know the value of
"arcNumber"? Does it read it from the uboot config from flash?

Regards,
Thomas