short description of problem: Since Fedora 11 you are unable to build a custom kernel for an i686 machine which does not support PAE. OK, you are able to do it, but you need to mess unnecessarily with some config files which for some reason are deliberately designed to "know better", that anybody wants PAE anyway. long description of problem: There are a lot of i686 machines out there, which don't support PAE. Any 1. generation Pentium M's, some later PM's, some Intel Atoms... I use an IBM Thinkpad x31, a X32 and T42, which all have this "problem". As I understand it, this is one of the reasons why Fedora distributes i686-non-PAE kernels and i686-PAE kernels. But, for some reason, the kernel spec file always 'forces' you to build a PAE-Kernel for all i686 machines. If you change that, you find out, that the Makefile.conf includes a section dedicated to non-PAE i686 machines, but it deliberately is set up to ignore any "config-i686"-config files and uses /dev/null instead. I sort of understood this in Fedora 11. i686-PAE for anything x86-32 with PAE support and i586 if they can't handle PAE. Now you removed the i586 part without replacing it, but officially support i686-non-PAE machines... This makes no sense to me. How does who ever builds the kernel packages build the default i686-non-PAE kernel without changing these files? Why are you forced to build a PAE kernel, which just won't boot on any non-PAE machine? Why are you shipping non-PAE kernels then? Version-Release number of selected component (if applicable): all Kernels sources for Fedora 11 and 12 How reproducible: always Steps to Reproduce: (not applicable) Actual results: kernel spec and makefile are configured to force you to build a i686-PAE kernel for any i686 target Expected results: kernel spec and makefile should allow non-PAE i686 kernels, maybe with some non-PAE option, just like the now useless PAE option build a PAE kernel instead of a non-PAE kernel Additional info: none
Hallo, I have the same problem to build a custom i686 non-pae kernel under Fedora 12, is there any help on how I can build a custom kernel please ?
I have a requirement to run a research OS named Ethos as a Xen DomU kernel. Ethos does not yet support 64-bit or 32-bit PAE. I'd like to more easily build Michael Young's Xen Dom0 kernels without PAE. Once Fedora supports Xen Dom0 kernels again (hopefully, around 2.6.34 or so), I'd like to see non-PAE kernels again.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.