Hide Forgot
Description of problem: One of my servers is unable to boot F15 vmlinuz via grub, as described in sections 11.1 and 11.2 of the installation guide. Version-Release number of selected component (if applicable): Fedora 15 How reproducible: Always Steps to Reproduce: Copied F15 vmlinuz and initrd.img off the DVD [root@octopus ~]# cd /boot [root@octopus boot]# ls -al pxeboot total 100548 drwxr-xr-x. 2 root root 1024 May 25 07:29 . dr-xr-xr-x. 7 root root 3072 May 25 01:59 .. -rw-r--r--. 1 root root 98678344 May 25 07:04 initrd.img -rwxr-xr-x. 1 root root 3867920 May 25 07:04 vmlinuz [root@octopus boot]# sha256sum pxeboot/* 1415bd6b55a41c6000089149e47ab45d988e31975e2e752ed1ab4285d816e729 pxeboot/initrd.img 5c7ba62ea93413e58dcbb0106b9e15ff640f4548ad2cdb05e911561a0438fd37 pxeboot/vmlinuz [root@octopus boot]# tail grub/menu.lst [ ... ] title update root (hd0,0) kernel /pxeboot/vmlinuz initrd /pxeboot/initrd.img Actual results: Making this selection from the grub menu results in a blank screen with a blinking cursor, no error message and no activity. System only responds to a three-fingered salute. Expected results: Boot F15 anaconda. Additional info: Appears to be hardware specific, I was able to start the same vmlinuz on another machine. I was able to start the same vmlinuz on this machine via a network boot. To make sure I wasn't imagining things, I installed F14's vmlinuz and initrd.img into /boot/pxeboot, on the same machine, and was able to boot them using the same grub config. Results: grub -> F14 vmlinuz: boots grub -> F15 vmlinuz: does not boot network -> F15 vmlinuz: boots grub -> F15 vmlinuz, different hardware: boots vmlinuz appears to fail very early in the boot process, before any of the usual boot messages begin to scroll.
Created attachment 500858 [details] Output of /proc/cpuinfo on target harware
Created attachment 500859 [details] Output of lspci on target harware
Created attachment 500860 [details] Output of dmidecode on target harware
Created attachment 500861 [details] Output of regular F15 kernel booting on target hardware, after succesful install via the network The bug is still reproducible after a successful F15 install - if I try to boot the F15 vmlinuz again, it still fails.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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