If you are further through the install than I thought (it sounded like it did this as soon as the kernel started to boot in your original post), perhaps you are able to switch to VT2 where there is a console and run some commands? If you are running the GUI installer, hit Ctrl-Alt-F2 and you should find a root command prompt. Run
- Code: Select all
dmesg | grep Memory
and see how much memory is being reported by those. The bug report that toracat
found does look promising - did the workaround of specifying mem= on the kernel command line not help? There seemed to be mentions of a 64 bit install in that bug.