| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 24 Nov 2013 17:36:54 +0100 (CET) From: devzero@....de To: linux-kernel@...r.kernel.org Subject: Grub2 skips standard linux initialization code ? Hi, regarding https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/930447 Grub2 "accidentally" heals a problem for systems which cannot boot PAE enabled kernels. This happens because grub2 apparently jumps into the kernel at a different entry point, so CPUID checking (check for PAE for example) apparently does not occur. Here are some 100 affected users (including me) which cannot boot recent Ubuntu (not even lubuntu, which is meant for that) Installation disk on their older hardware, which makes installation a pain. This is because Pentium M cpu´s for example often can do PAE, but they incorrectly report. The ubuntu installer disc does "traditional" boot via syslinux, whereas the installed system boots via grub2. That explains why you can upgrade from ubuntu 12.04 to 13.10 and have a workable system, but you cannot freshly install 13.10. The most absurd thing is: You cannot even install Lubuntu or Xubuntu, which is especially designed to be used on older hardware. I guess Pentium M is a process which is still widely used. My question is: 1. Why does Grub2 think it`s good to skip x86 linux initializiation code? Is that good or bad? 2. Besides that, wouldn`t it be extremly helpful to add a quirk or skip routine to the kernel initialization code? (kernelparam: "no-pae-ceck" for example). regards roland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists