Re: why linux can't see my memory
On 1/5/14, Scott Ferguson <scott.ferguson.debian.user@gmail.com> wrote:
>
>
> shadowing(??)
>
>
> dmidecode will give you the information Miles (and others) need if you
> can get a Live CD to boot.
> Most of the Debian/Debian-based ones will take the kernel parameter
> "mem=$amountM" as mentioned elsewhere in this thread (where $amount is
> megabytes found during POST and "M" must be upper-case)
>
> e.g. for Knoppix:-
> knoppix mem=1024M (gives W.I.M.P. requires minimum of 120MB of RAM)
>
> or:-
> knoppix 2 mem=1024M (gives you runlevel 2, text-mode, single-user root,
> runs in <50MB RAM)
>
> dmidecode needs to be run by root, it's output is lengthy so best post
> it to a pastebin and link to it in your post.
>
> If you use Knoppix in run-level 2 you can setup networking with:-
> knoppix-networkmanager
>
> Email the dmidecode report to yourself (as root):-
> dmidecode | mail longwind2009@gmail.com -s "dmidecode report"
>
>
>
> Also - check your BIOS to see how much RAM is being allocated to the
> built-in video card (aperture is different and doesn't rob the system of
> RAM).
>
>
I have said "mem=" option doesn't work
Its result is nearly the same as I don't enter boot option "mem="
After reading (loading) kernel, the machine reboot
(apparently it has memory problem)
according lili.conf manual, "mem=" is passed to kernel by lilo
I have tested "mem=" with 2 Linux installation CD
Will Live CD make difference?
I can't boot Linux, so I can't run dmidecode
I use a AGP card, so I have not thought shared video memory might cause trouble
I will check now
Reply to: