so i would confirm the suspicion that the problem must be related to the bootloader somehow.
but the question is if syslinux makes the kernel fail boot or if grub has something "inside" which avoids the kernel fail to boot.
if PAE cpu flag is not available in some processor`s CPUID, i wonder why the kernel can boot. does linux kernel not check for cpu flags and does it detect pae capability differently (i.e. more reliable?)
i did a comparison of the installer`s kernel .config with the kernel .config of my working system - and they appear nearly identical:
3c3 VERSION_ SIGNATURE= "Ubuntu 3.11.0- 12.19-generic 3.11.3" VERSION_ SIGNATURE= "Ubuntu 3.11.0- 13.20-generic 3.11.6" USB_ZERO_ HNPTEST= y
< # Linux/i386 3.11.0-12-generic Kernel Configuration
---
> # Linux/i386 3.11.0-13-generic Kernel Configuration
68c68
< CONFIG_
---
> CONFIG_
5435c5435
< CONFIG_USB_OTG=y
---
> # CONFIG_USB_OTG is not set
5703d5702
< CONFIG_
6717a6717
> CONFIG_DM_RAID45=m
so i would confirm the suspicion that the problem must be related to the bootloader somehow.
but the question is if syslinux makes the kernel fail boot or if grub has something "inside" which avoids the kernel fail to boot.
if PAE cpu flag is not available in some processor`s CPUID, i wonder why the kernel can boot. does linux kernel not check for cpu flags and does it detect pae capability differently (i.e. more reliable?)