After many many considerations I went for EFI-boot in faovour of good old BIOS-boot using syslinux. The fall back solution is still BIOS-boot using extlinux.
Problem is that with the very same (carefully verified) initramfs and kernel all my 16GB ram shows up in BIOS boot while only 4GB (well, 3.5) shows up booting from EFI.
Any hint on the reason to this? My world does not depend on EFI-boot, the BOIS boot works very well and will be my primary until this is sorted out, but it would be good to understand.
Some facts;
Motherboard is ASUSTeK SABERTOOTH 990FX R2.0 Rev 1.xx
BIOS is dated Date: 05/04/2016 and version 2901 that seems to be the latest version.
# uname -a
Linux kalle 4.13.12-gentoo #6 SMP PREEMPT Thu Dec 14 07:42:52 CET 2017 x86_64 AMD FX(tm)-9590 Eight-Core Processor AuthenticAMD GNU/Linux
I have tried several combinations of legacy modes including no legacy support (CSM disabled).
Question
erikr
After many many considerations I went for EFI-boot in faovour of good old BIOS-boot using syslinux. The fall back solution is still BIOS-boot using extlinux.
Problem is that with the very same (carefully verified) initramfs and kernel all my 16GB ram shows up in BIOS boot while only 4GB (well, 3.5) shows up booting from EFI.
Any hint on the reason to this? My world does not depend on EFI-boot, the BOIS boot works very well and will be my primary until this is sorted out, but it would be good to understand.
Some facts;
Motherboard is ASUSTeK SABERTOOTH 990FX R2.0 Rev 1.xx
BIOS is dated Date: 05/04/2016 and version 2901 that seems to be the latest version.
# uname -a
Linux kalle 4.13.12-gentoo #6 SMP PREEMPT Thu Dec 14 07:42:52 CET 2017 x86_64 AMD FX(tm)-9590 Eight-Core Processor AuthenticAMD GNU/Linux
I have tried several combinations of legacy modes including no legacy support (CSM disabled).
Edit header to cancel topic.
Link to comment
Share on other sites
10 answers to this question
Recommended Posts